{"id":80729,"date":"2026-09-17T08:16:37","date_gmt":"2026-09-17T11:16:37","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=80729"},"modified":"2026-09-17T08:16:37","modified_gmt":"2026-09-17T11:16:37","slug":"industrial-commissioning-pre-commissioning-startup-cold-hot-testing","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/industrial-commissioning-pre-commissioning-startup-cold-hot-testing\/","title":{"rendered":"Industrial Commissioning: Pre-Commissioning, Start-Up, Cold and Hot Testing"},"content":{"rendered":"\n

Industrial commissioning<\/strong> is the structured process that takes systems and units from construction completion to a demonstrated state of readiness, start-up, operation, and acceptance. Rather than treating handover as a single event, it organizes systemization<\/em>, mechanical completion, pre-commissioning, cold testing, start-up, hot commissioning, performance testing, documentation, and the transfer of responsibilities through verifiable milestones.<\/p>\n\n\n

A plant may show high physical progress and still not be ready to start. Individually completed equipment may coexist with incomplete interfaces, unproven interlocks, outstanding instrumentation items, untested protections, unavailable utilities, outdated documents, or safety constraints. For this reason, the transition from construction to operation must be controlled by readiness criteria and evidence, not merely by percentage of construction completed.<\/p>\n\n\n\n

This article focuses specifically on the industrial logic of systems completion<\/em> and start-up. For a cross-functional view of the process \u2014 from requirements, the commissioning plan, and FAT\/SAT through documentation, acceptance, and handover \u2014 see the Complete Guide to Commissioning<\/strong><\/a>, which serves as the technical hub for this topic.<\/p>\n\n\n\n

The central reference for this sequence is ABNT NBR IEC 62337:2020, which distinguishes construction completion, mechanical completion, pre-commissioning, cold commissioning, start-up, hot commissioning, start of production, performance testing, and acceptance. The value of this separation is to prevent outstanding items, risks, and responsibilities from being transferred between phases without a formal technical decision.<\/p>\n\n\n\n\n

Industrial commissioning and its position between construction, start-up, and acceptance<\/h2>\n\n\n\n

Commissioning is a requirements-driven verification and validation process. Its purpose is not merely to prove that equipment powers up, rotates, communicates, or responds to a command, but to demonstrate that the delivered system as a whole meets the intended functions, capacities, protections, interfaces, and operating conditions.<\/p>\n\n\n\n

ABNT NBR IEC 62337:2020 organizes the process into specific phases and milestones for electrical, instrumentation, and industrial process control systems. The sequence defined by the standard distinguishes construction completion, mechanical completion, pre-commissioning, cold commissioning, start-up, hot commissioning, start of production, performance testing, and plant acceptance. This separation is essential because each milestone transfers different responsibilities, risks, and custody conditions.<\/p>\n\n\n\n

For buildings and building systems, ASHRAE treats commissioning as a quality-focused process that follows requirements, design, construction, testing, training, and operation. Although terminology varies among industries, the underlying logic is the same: verifiable requirements, defined responsibilities, traceable evidence, and a formal acceptance decision.<\/p>\n\n\n\n

Commissioning is not a final inspection<\/h3>\n\n\n\n

Inspection verifies the conformity of materials, installation, identification, workmanship, records, and specific requirements. Commissioning uses this evidence but goes further into functional and integrated behavior. An inspection may confirm that a panel was installed according to the drawing; commissioning verifies whether protection, control, indication, interlocks, communications, alarms, and response to expected conditions work together as a system.<\/p>\n\n\n\n

It should also not be confused with construction supervision. Supervision follows contracted execution and verifies conformity, quantities, evidence, and obligations. Commissioning has a functional scope: it organizes procedures, sequences, test conditions, expected data, acceptance criteria, retests, and handover documentation.<\/p>\n\n\n\n

Pre-commissioning, commissioning, start-up, and acceptance<\/h3>\n\n\n\n

These terms should be defined in the contract because indiscriminate use creates conflicts of responsibility. The table below presents a technical separation consistent with ABNT NBR IEC 62337.<\/p>\n\n\n\n

Phase or milestone<\/td>Main purpose<\/td>Typical evidence<\/td><\/tr>
Construction completion<\/td>Confirm that physical installation was executed according to the design, specifications, and applicable requirements<\/td>inspection reports, installation records, and punch list<\/td><\/tr>
Mechanical completion<\/td>Confirm that a part, section, unit, or system has completed the pre-commissioning activities required to proceed<\/td>mechanical completion certificate and associated dossier<\/td><\/tr>
Pre-commissioning<\/td>Perform non-operational checks, cleaning, adjustments, calibrations, loop checks, and tests prior to operation<\/td>checklists, certificates, test reports, and corrective-action records<\/td><\/tr>
Cold commissioning<\/td>Operate and test using safe media or conditions that do not involve the actual process product<\/td>approved procedures, recorded data, and accepted results<\/td><\/tr>
Start-up<\/td>Mark the transition between cold commissioning and the introduction of actual process conditions or load<\/td>formal authorization, start-up plan, and operating records<\/td><\/tr>
Hot commissioning<\/td>Adjust and validate equipment and systems under actual process conditions<\/td>operating records, adjustments, alarms, interlocks, and performance data<\/td><\/tr>
Performance test<\/td>Demonstrate capacity, consumption, stability, and other contractual guarantees<\/td>performance report with data, analyses, tolerances, and conclusion<\/td><\/tr>
Plant acceptance<\/td>Formalize transfer of the plant to the owner while preserving warranties and remaining obligations<\/td>acceptance certificate or record and transfer of custody<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Physical completion of the work is not equivalent to mechanical completion, just as start-up is not equivalent to acceptance. Each milestone requires a defined set of conditions and documents. When these boundaries are not contractually defined, outstanding items migrate between phases, suppliers may claim premature completion of responsibility, and the owner may assume risks without sufficient evidence.<\/p>\n\n\n\n

The logic of systems and subsystems<\/h3>\n\n\n\n

Complex projects should not be commissioned solely by discipline or contract. The process must be organized around functional systems and subsystems with defined boundaries. A system may combine equipment, panels, networks, sensors, software, logic, utilities, and interfaces supplied by different companies.<\/p>\n\n\n\n

Systemization<\/em>, or decomposition into commissioning systems, makes progressive handovers possible. Instead of waiting for total project completion, areas and systems can advance as they meet established criteria. Each package must therefore identify physical and functional boundaries, applicable documents, responsible parties, dependencies, energy sources involved, required tests, and transfer conditions.<\/p>\n\n\n\n

This architecture should connect to the article on Engineering Construction Execution<\/a>, in which implementation is organized into executable packages and decision milestones. Commissioning begins to be prepared before those packages are complete, following engineering, procurement, quality, and documentation.<\/p>\n\n\n\n

\n

Commissioning does not begin when construction ends.<\/strong><\/p>\n\n\n\n

Requirements, interfaces, test criteria, and documents must be defined while there is still time to influence design and procurement.<\/p>\n\n\n\n

When a project requires an independent structure to organize systems, readiness gates, procedures, witnessing, retests, and acceptance criteria, the scope can be contracted as Engineering Commissioning<\/strong><\/a>, with involvement from planning through technical handover to operations.<\/p>\n<\/div>\n\n\n\n\n

How to structure the commissioning plan and process governance<\/h2>\n\n\n\n

The Commissioning Plan turns contractual and technical requirements into an executable strategy. It establishes what will be commissioned, in what sequence, by whom, with which documents, under what conditions, and according to which criteria.<\/p>\n\n\n\n

The plan should not be a generic description attached to the contract. It must reflect the project’s actual architecture, system breakdown, contracting models, criticality, interfaces, operating windows, risks, and the participation of the owner’s team.<\/p>\n\n\n\n

Scope, objectives, and boundaries<\/h3>\n\n\n\n

The first step is to define the systems included and excluded. For each system, equipment, subsystems, interfaces, utilities, software, communications, protections, alarms, interlocks, and associated documents should be identified.<\/p>\n\n\n\n

The purpose of each stage must also be clear. Some tests demonstrate installation conformity; others verify functionality; others prove integration, capacity, safety, autonomy, availability, or response to failures. Using the same name for tests with different purposes weakens the process.<\/p>\n\n\n\n

The scope matrix can associate the system, requirement, source document, verification method, responsible party, witness, evidence, and acceptance criterion. This traceability links the Detailed Engineering Design<\/a> to acceptance and prevents the test from being prepared solely on the basis of what the supplier decided to deliver.<\/p>\n\n\n\n

Systems, interfaces, and criticality matrix<\/h3>\n\n\n\n

The depth of commissioning should be proportional to the consequences of failure. Safety systems, critical power, automation, protection, supervision, fire protection, operational communications, and process continuity generally require more scenarios, witnessing, and evidence.<\/p>\n\n\n\n

Criticality may consider impacts on people, the environment, production, availability, quality, regulatory compliance, assets, data, and reputation. The classification is not intended to eliminate tests, but to define rigor, independence, coverage, and priority.<\/p>\n\n\n\n

Interfaces must appear as verifiable objects. It is not enough to test a generator, transfer switchboard, UPS, and critical load separately; the integrated sequence, response times, alarms, recovery, and behavior under abnormal conditions must be validated. The same applies to integration among fire detection, access control, HVAC, automation, power, supervision, and operating procedures.<\/p>\n\n\n\n

Organization, responsibilities, and technical independence<\/h3>\n\n\n\n

ABNT NBR IEC 62337 emphasizes the need to agree responsibilities between the contractor and the owner. In practice, the process may involve the owner and operations team, project management or EPCM, the construction contractor or EPC contractor, designers, suppliers, manufacturers, integrators, the commissioning team, construction supervision, Owner\u2019s Engineering, and authorities when applicable.<\/p>\n\n\n\n

The contractor is responsible for conformity within its scope and for correcting failures. The supplier is responsible for equipment, software, documentation, and support within its scope. The commissioning team organizes the process and verifies results. The owner defines requirements, provides the resources under its responsibility, and decides on acceptance. Owner\u2019s Engineering<\/a> acts independently to review criteria, witness tests, assess deviations, and technically support the owner’s decision.<\/p>\n\n\n\n

Independence is particularly important when the same company designs, supplies, installs, tests, and recommends acceptance of its own scope. This does not invalidate the contracting model, but it increases the need for objective criteria, independent witnessing, and traceability.<\/p>\n\n\n\n

Integrated schedule and constraint management<\/h3>\n\n\n\n

The commissioning schedule must be connected to engineering, procurement, manufacturing, installation, and operations. Each test package depends on released documents, installed equipment, completed inspections, calibrated instruments, available utilities, completed interfaces, classified outstanding items, and authorized safety conditions.<\/p>\n\n\n\n

Planning must show actual predecessors, not just desired dates. A test sequence may depend on energization, load availability, communication with external systems, manufacturer presence, an operating window, a permit, specialized resources, or environmental conditions.<\/p>\n\n\n\n

Project Controls<\/a> should integrate physical progress, documentation progress, and testing progress. A system with completed installation but without approved procedures or supplier data does not have the same maturity as another system whose dossier is complete.<\/p>\n\n\n\n

Procedures, test packages, and acceptance criteria<\/h3>\n\n\n\n

Each procedure should state its objective, scope, references, preconditions, initial configuration, resources, instruments, responsible parties, sequence, data to be recorded, acceptable limits, actions in case of failure, and completion condition.<\/p>\n\n\n\n

The content should be adapted to the risk. Energization, pressurization, movement, process introduction, or failure-simulation procedures require specific safety analysis and formal authorization. This article does not replace execution procedures, manufacturer manuals, applicable standards, or professional engineering responsibility.<\/p>\n\n\n\n

Package element<\/td>Expected content<\/td><\/tr>
Identification<\/td>system, subsystem, area, equipment, and revision<\/td><\/tr>
Technical basis<\/td>requirements, drawings, technical specifications, logic diagrams, data sheets, and manuals<\/td><\/tr>
Start conditions<\/td>installation, inspections, utilities, calibration, safety, and outstanding items<\/td><\/tr>
Method<\/td>verification sequence, stimuli, measurements, and records<\/td><\/tr>
Criteria<\/td>values, tolerances, times, states, and acceptable results<\/td><\/tr>
Responsibilities<\/td>preparation, execution, witnessing, approval, and release<\/td><\/tr>
Evidence<\/td>forms, trends, screenshots, certificates, photographs, and signatures<\/td><\/tr>
Failure and retest<\/td>treatment, correction, re-execution, and closeout<\/td><\/tr>
Transfer<\/td>final condition, accepted outstanding items, and custody<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Criteria should not be defined after the test. Results can only be evaluated consistently when the method, tolerances, and decision authority were agreed in advance.<\/p>\n\n\n\n

\n

The Commissioning Plan is a governance instrument.<\/strong><\/p>\n\n\n\n

It integrates systems, responsibilities, schedule, procedures, evidence, and decision criteria into a single strategy.<\/p>\n\n\n\n

Structure the process with Owner\u2019s Engineering<\/strong><\/a><\/p>\n<\/div>\n\n\n\n\n

Construction completion, mechanical completion, and pre-commissioning<\/h2>\n\n\n\n

The transition from construction to commissioning is one of the most critical stages of a project. Construction hands over systems that may still contain outstanding items; commissioning takes custody of equipment that will begin to be energized, moved, pressurized, connected, or operated. This change requires formal boundaries, documents, and responsibilities.<\/p>\n\n\n\n

Construction completion<\/h3>\n\n\n\n

After installation, the contractor must verify that equipment, materials, connections, identification, and installations conform to the design, specifications, manufacturer instructions, and applicable requirements.<\/p>\n\n\n\n

Records must identify the item, type of verification, date, result, observations, and responsible parties. Participation or witnessing by the owner does not transfer the contractor’s responsibility for conformity.<\/p>\n\n\n\n

Incomplete or defective items, or items requiring adjustment, must be recorded in a punch list. This list cannot be a parallel file without governance. Each item must be linked to the system, requirement, responsible party, deadline, criticality, evidence of correction, and any need for retesting.<\/p>\n\n\n\n

Mechanical completion by system<\/h3>\n\n\n\n

Mechanical completion is a formal milestone. It should be declared for a clearly identified part, section, unit, system, or subsystem, rather than as a generic statement that \u201cconstruction is finished.\u201d<\/p>\n\n\n\n

The mechanical completion certificate should be accompanied by a dossier that allows the owner to verify the declared condition. Applicable documents may include inspection reports, checklists, test certificates, calibrations, loop records, updated drawings, supplier documentation, punch lists, and authorizations.<\/p>\n\n\n\n

Acceptance of the certificate does not eliminate contractual obligations. Minor outstanding items may remain when they do not prevent the next stage, but they must be explicitly classified and controlled. Items affecting safety, function, integrity, interfaces, protection, measurement, or reliability should not be hidden behind an administrative conclusion.<\/p>\n\n\n\n

Pre-commissioning activities<\/h3>\n\n\n\n

Pre-commissioning brings together checks and tests performed before actual operation. Depending on the type of system, it may include cleaning, inspection, preservation, calibration, continuity checks, insulation testing, grounding verification, parameterization, rotation checks, alignment, direction checks, leak testing, loop checks, alarm and interlock tests, software verification, and documentation validation.<\/p>\n\n\n\n

ABNT NBR IEC 62337 presents specific activities for electrical systems, instrumentation, process control, rotating equipment, piping, utilities, and auxiliary systems. The list must be adapted to the project; it should not be copied without considering technology, risk, contract requirements, and manufacturer recommendations.<\/p>\n\n\n\n

IEC 62382:2024 defines the loop check as the set of verifications between completion of loop construction, including point-to-point checks, and the start of cold commissioning. This work is decisive in automation systems because it confirms continuity, polarity, scaling, direction of action, input\/output association, and final-element response.<\/p>\n\n\n\n

Energy control, safety, and custody<\/h3>\n\n\n\n

As systems advance, site conditions change. Equipment that was previously inert begins to contain electrical energy, pressure, motion, temperature, active software, or external communications. Handover must therefore include custody boundaries, switching authority, permits, lockouts, communication, and emergency response.<\/p>\n\n\n\n

The organization must know who can authorize energization, change a parameter, remove a lockout, perform switching, start a test, or declare a safe condition. The absence of these rules creates risks to people, equipment, and evidence.<\/p>\n\n\n\n

The transfer must also protect configurations that have already been validated. Subsequent changes to settings, logic, firmware, addressing, networks, protection systems, or software should follow formal change control because they may invalidate previously obtained results.<\/p>\n\n\n\n

Documentation maturity before proceeding<\/h3>\n\n\n\n

Documentation is not a closeout activity. Drawings, redlines, data sheets, certificates, manuals, spare-parts lists, logic diagrams, backups, reports, and parameters must be consolidated progressively.<\/p>\n\n\n\n

The dossier for each system should allow the technical history of the handover to be reconstructed: what was specified, installed, inspected, tested, corrected, and accepted. When this chain is broken, the owner receives an asset whose behavior may have been observed but has not been adequately demonstrated.<\/p>\n\n\n\n

The Requirements, Evidence, and Acceptance Criteria Management<\/a> solution organizes this traceability and connects source requirements to the evidence generated during execution and commissioning.<\/p>\n\n\n\n

\n

Physical completion is not equivalent to mechanical completion.<\/strong><\/p>\n\n\n\n

Each system transfer requires a dossier, certificates, classified outstanding items, and formal conditions to proceed.<\/p>\n\n\n\n

Learn about Punch List, RFI, and Nonconformance Management<\/strong><\/a><\/p>\n<\/div>\n\n\n\n\n

Cold commissioning, start-up, hot commissioning, and integrated testing<\/h2>\n\n\n\n

After mechanical completion and pre-commissioning, the system may advance to operational testing. The sequence must respect the contract, risks, technology, manufacturer instructions, and operating conditions. For processes that require a formal safety gate before start-up, the PSSR \u2014 Pre-Startup Safety Review<\/strong><\/a> verifies whether design, management of change, procedures, training, and field conditions support start-up release.<\/p>\n\n\n\n

Cold commissioning<\/h3>\n\n\n\n

During cold commissioning, equipment and installations are operated or tested without introducing the actual process product, using test media or controlled conditions. The objective is to verify behavior, sequences, controls, protections, and interfaces before exposing the system to full service conditions.<\/p>\n\n\n\n

In electrical and automation systems, the concept may include controlled energization, simulations, signal injection, logic testing, communications, control, interlocks, and actuation without full load or the actual process. The application must be technically defined for each system.<\/p>\n\n\n\n

The start-up milestone closes this phase and authorizes the transition to actual conditions. Start-up is not synonymous with complete commissioning: it marks a change of condition and requires risks, resources, procedures, and responsibilities to have been addressed.<\/p>\n\n\n\n

Hot commissioning and operational adjustments<\/h3>\n\n\n\n

During hot commissioning, the system begins operating with the actual product, load, or process conditions. This is the stage in which final adjustments may be required for control, stability, vibration, temperature, pressure, sequencing, alarms, and performance.<\/p>\n\n\n\n

Operating data must be defined in advance and recorded on controlled forms. Adjustments made during the process must be documented because they change the configuration that will be handed over to operations.<\/p>\n\n\n\n

Representatives of manufacturers and licensors may be required to supervise specific activities. Their presence does not replace owner governance or the need to record decisions, changes, and results.<\/p>\n\n\n\n

Functional testing and integrated testing<\/h3>\n\n\n\n

A functional test verifies whether a piece of equipment, subsystem, or function individually performs as expected. An integrated test verifies joint operation under complete operating scenarios.<\/p>\n\n\n\n

An integrated test should consider not only the normal scenario but also degraded conditions, loss of communication, power failure, protection operation, component unavailability, recovery after failure, mode changes, alarms, and operational response, as applicable.<\/p>\n\n\n\n

Test scenarios should be derived from requirements, risk analysis, operating modes, cause-and-effect logic, the interlock matrix, and operating procedures. Scenarios unrelated to a risk or requirement consume resources and may introduce hazards without producing useful evidence.<\/p>\n\n\n\n

The article on Integrated Systems Testing in Data Centers<\/a> shows how this logic can be applied to mission-critical environments, but the principles also apply to power, automation, telecommunications, electronic security, and industrial systems.<\/p>\n\n\n\n

FAT, FIT, SAT, SIT, TAF, TAC, and TIC<\/h3>\n\n\n\n

Terminology varies by language, industry, and contract. IEC 62381:2024 defines requirements and checklists for Factory Acceptance Test, Factory Integration Test, Site Acceptance Test, and Site Integration Test.<\/p>\n\n\n\n

In Brazil, the terms TAF, Teste de Aceita\u00e7\u00e3o em F\u00e1brica; TAC, Teste de Aceita\u00e7\u00e3o em Campo; and TIC, Teste de Integra\u00e7\u00e3o em Campo, are also common. The name alone does not define the scope. The contract must specify which functions, interfaces, conditions, documents, simulators, and criteria are included in each stage.<\/p>\n\n\n\n

Factory testing makes it possible to identify problems before shipment, when hardware, software, and documentation corrections generally have less impact. Site testing verifies the installed condition, connections, integration with other systems, and the actual environment. A satisfactory factory result does not eliminate site testing because transportation, installation, cabling, configuration, networks, and interfaces may introduce new variables.<\/p>\n\n\n\n

Failures, retests, and configuration control<\/h3>\n\n\n\n

Failing a test does not, by itself, mean failure of the process. Commissioning exists to reveal deviations before full operation. The problem arises when failures are not recorded, are corrected informally, or the test is repeated without controlling the cause.<\/p>\n\n\n\n

Each failure should generate a technical record identifying the affected requirement, observed condition, evidence, analysis, responsible party, correction, impact, and need for retesting. When a correction changes the design, logic, parameterization, or interface, documents and backups must be updated.<\/p>\n\n\n\n

The retest should verify the correction as well as possible side effects. Changing logic to solve one scenario may affect other states. Regression matrices and configuration control are therefore relevant in digital and integrated systems.<\/p>\n\n\n\n

\n

Testing isolated components does not demonstrate system performance.<\/strong><\/p>\n\n\n\n

Interfaces, degraded modes, alarms, interlocks, and recovery must be verified through scenarios consistent with the asset’s risks.<\/p>\n\n\n\n

Learn about Commissioning of Systems and Infrastructure<\/strong><\/a><\/p>\n<\/div>\n\n\n\n\n

Performance testing, outstanding items, documentation, and acceptance criteria<\/h2>\n\n\n\n

Functional commissioning demonstrates behavior. Performance testing demonstrates whether the installation achieves the capacities, consumption levels, stability, quality, autonomy, efficiency, or other guarantees established for the project.<\/p>\n\n\n\n

ABNT NBR IEC 62337 places the performance test after initial operation and before plant acceptance. The contract must define conditions, duration, methods, instruments, tolerances, responsibilities, and the consequences of an unsatisfactory result.<\/p>\n\n\n\n

Conditions for starting the performance test<\/h3>\n\n\n\n

A test produces valid evidence only when conditions correspond to the agreed basis. The system must operate in the intended mode, with suitable instrumentation, stable utilities, compatible inputs, available interfaces, and known environmental or operating conditions.<\/p>\n\n\n\n

The instrumentation used must have range, accuracy, traceability, and calibration compatible with what is being demonstrated. Results without defined uncertainty or tolerance can lead to technically weak conclusions.<\/p>\n\n\n\n

The procedure should specify stabilization period, duration, data collection frequency, treatment of abnormal data, losses, corrections, and calculation method. These aspects cannot be decided only after the results are known.<\/p>\n\n\n\n

Acceptance criteria and tolerances<\/h3>\n\n\n\n

Acceptance criteria should derive from requirements, the contract, standards, design, and guarantees. They may address capacity, availability, consumption, quality, response time, selectivity, autonomy, stability, temperature, noise, communications, redundancy, or other parameters.<\/p>\n\n\n\n

The statement \u201cit worked\u201d is not a sufficient technical criterion. The initial state, stimulus, expected response, limit, time, measurement method, and evidence must be defined.<\/p>\n\n\n\n

When tolerances exist, they must be recorded. Acceptance should not depend on later interpretation or selective comparison with the best result observed. The article on Engineering Acceptance Criteria<\/a> explores this structure in greater depth.<\/p>\n\n\n\n

Blocking and non-blocking outstanding items<\/h3>\n\n\n\n

Not every outstanding item has the same criticality. The process may adopt project-defined categories as long as the criteria are clear. A blocking item is one that affects safety, essential function, performance, compliance, integrity, an interface, or the ability to conduct a reliable test. A non-blocking item may be completed later without compromising the next stage.<\/p>\n\n\n\n

The classification must not be used to transfer risk without control. Every accepted outstanding item must have a responsible party, deadline, impact, closure condition, and compatible contractual retention or warranty when applicable.<\/p>\n\n\n\n

Punch List, RFI, and Nonconformance Management<\/a> prevents items from remaining scattered across meeting minutes and emails. It makes it possible to link a failure, requirement, system, action, retest, and acceptance.<\/p>\n\n\n\n

Final dossier and system manual<\/h3>\n\n\n\n

The final dossier should be structured by system. It may consolidate requirements and the traceability matrix, final design and revisions, supplier documentation, installation and mechanical-completion certificates, pre-commissioning checklists and reports, test procedures and results, calibration records, punch lists, adjustments, parameters, backups, as-built documentation, manuals, spare parts, training records, warranties, and the final report.<\/p>\n\n\n\n

The system manual should help operations understand architecture, operating modes, limits, alarms, interlocks, normal procedures, abnormal conditions, and maintenance. Delivering separate manufacturer manuals does not replace an integrated view of the asset.<\/p>\n\n\n\n

Training, assisted operation, and transfer of custody<\/h3>\n\n\n\n

Training must be linked to the team’s actual functions. Operators, maintainers, system administrators, and managers may require different content. Evidence should include the program, participants, materials, practical activities, assessment, and outstanding items.<\/p>\n\n\n\n

Assisted operation makes it possible to observe the asset under real use, consolidate adjustments, support the team, and verify behaviors that did not appear during short-duration testing. Its scope, duration, support, and completion criteria should be contractually defined.<\/p>\n\n\n\n

Plant acceptance transfers responsibility for preservation, custody, operation, and maintenance to the owner without eliminating warranties and remaining obligations. The Technical Acceptance Record<\/a> should document the object, evidence, reservations, outstanding items, responsibilities, and contractual effects.<\/p>\n\n\n\n

\n

Acceptance requires traceable evidence.<\/strong><\/p>\n\n\n\n

Results, tolerances, instruments, configuration, outstanding items, and responsibilities must support a defensible technical decision.<\/p>\n\n\n\n

Learn about the Requirements and Acceptance Criteria Management solution<\/strong><\/a><\/p>\n<\/div>\n\n\n\n\n

How to contract and conduct commissioning with technical independence<\/h2>\n\n\n\n

Commissioning should be contracted while there is still an opportunity to influence requirements, design, procurement, and planning. Bringing the team in only at the end reduces the process to handover testing and removes much of its preventive value.<\/p>\n\n\n\n

For simple projects, some activities may be performed by the execution team itself, provided that requirements and criteria are objective. For critical, multidisciplinary assets or projects with a high cost of failure, an independent structure linked to the owner is recommended.<\/p>\n\n\n\n

When commissioning should begin<\/h3>\n\n\n\n

The process can be structured from the Basic Design or Detailed Engineering Design phases. At this stage, the team reviews requirements, operating philosophy, testability, access, instrumentation, interfaces, criteria, and required documentation.<\/p>\n\n\n\n

During Technical Procurement<\/a>, requirements for FAT, SAT, documentation, manufacturer support, training, and warranties should be included in procurement packages. If these obligations are defined only after purchase, the owner loses leverage to require scope, schedule, and evidence.<\/p>\n\n\n\n

During execution, the team follows quality, completion, systemization, documentation, outstanding items, and preparation of the packages. It then coordinates or witnesses pre-commissioning, commissioning, integrated testing, performance testing, assisted operation, and acceptance.<\/p>\n\n\n\n

Contracting models<\/h3>\n\n\n\n

Commissioning may be integrated into EPC, EPCM, project management, Owner\u2019s Engineering, or specialized-services contracts. The model should distinguish responsibility for execution, verification, and acceptance.<\/p>\n\n\n\n

Under EPC, the main contractor normally coordinates suppliers and performs much of the testing, while the owner establishes requirements and witnesses milestones. Under EPCM<\/a>, coordination may integrate separate supply and construction contracts. Under Owner\u2019s Engineering, the independent team evaluates the process on behalf of the owner.<\/p>\n\n\n\n

The choice must consider internal maturity, number of contracts, criticality, interfaces, schedule, operational availability, and information-asymmetry risk.<\/p>\n\n\n\n

Deliverables of a consistent technical scope<\/h3>\n\n\n\n
Deliverable<\/td>Purpose<\/td><\/tr>
Commissioning strategy<\/td>define principles, systems, phases, governance, and approach<\/td><\/tr>
Commissioning Plan<\/td>consolidate scope, responsibilities, schedule, documents, and criteria<\/td><\/tr>
Systems and subsystems matrix<\/td>organize boundaries, dependencies, and handovers<\/td><\/tr>
Requirements and test matrix<\/td>link requirement, method, evidence, and acceptance<\/td><\/tr>
Test procedures<\/td>define execution, data, limits, responsibilities, and safety<\/td><\/tr>
Records and certificates<\/td>formalize completion, tests, corrections, and transfer<\/td><\/tr>
Punch list register<\/td>control deviations, responsible parties, deadlines, retests, and closeout<\/td><\/tr>
Test reports<\/td>present results, analyses, evidence, and conclusions<\/td><\/tr>
System dossier<\/td>consolidate technical and contractual documentation<\/td><\/tr>
Final report<\/td>demonstrate coverage, results, reservations, and recommendation<\/td><\/tr>
Acceptance record<\/td>formalize the decision, custody, outstanding items, and obligations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The scope should state the number of systems, estimated quantity of procedures, responsibility for execution, witnessing requirements, travel, instruments, specialists, and manufacturer support. Without these assumptions, commercial commissioning proposals become difficult to compare.<\/p>\n\n\n\n

A3A Engenharia’s role<\/h3>\n\n\n\n

A3A Engenharia<\/strong> provides planning, structuring, coordination, supervision, and independent validation of the commissioning of systems and infrastructure. The work may include requirements and design review, the Commissioning Plan, systems matrix, review of procedures, mechanical-completion follow-up, test witnessing, punch-list management, document review, integrated testing, acceptance criteria, and support for handover to operations.<\/p>\n\n\n\n

This role preserves the responsibilities of designers, manufacturers, and contractors for their respective scopes. A3A’s role is to ensure that the owner has sufficient criteria, evidence, and governance to make an informed decision.<\/p>\n\n\n\n

Well-conducted commissioning is not a final ceremony. It is the process that transforms requirements into verifications, verifications into evidence, and evidence into a defensible technical decision on operation and acceptance.<\/p>\n\n\n\n

\n

Technical independence protects the owner’s decision.<\/strong><\/p>\n\n\n\n

A3A Engenharia structures, monitors, and validates the process without replacing the responsibilities of designers, manufacturers, and contractors.<\/p>\n\n\n\n

Learn about A3A Engenharia’s commissioning services<\/strong><\/a><\/p>\n<\/div>\n\n\n\n

Technical references<\/summary>\n

[1] ASSOCIA\u00c7\u00c3O BRASILEIRA DE NORMAS T\u00c9CNICAS. ABNT NBR IEC 62337:2020 \u2014 Commissioning of electrical, instrumentation and industrial process control systems \u2014 Specific phases and milestones. Rio de Janeiro, 2020. Available at: view the corresponding international publication<\/a>.<\/p>\n\n\n\n

[2] INTERNATIONAL ELECTROTECHNICAL COMMISSION. IEC 62337:2012 \u2014 Commissioning of electrical, instrumentation and control systems in the process industry \u2014 Specific phases and milestones. Geneva, 2012. Available at: official IEC source<\/a>.<\/p>\n\n\n\n

[3] INTERNATIONAL ELECTROTECHNICAL COMMISSION. IEC 62381:2024 \u2014 Automation systems in the process industry \u2014 Factory acceptance test, factory integration test, site acceptance test and site integration test. Geneva, 2024. Available at: official IEC source<\/a>.<\/p>\n\n\n\n

[4] INTERNATIONAL ELECTROTECHNICAL COMMISSION. IEC 62382:2024 \u2014 Control systems in the process industry \u2014 Electrical and instrumentation loop check. Geneva, 2024. Available at: official IEC source<\/a>.<\/p>\n\n\n\n

[5] AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING ENGINEERS. Guideline 0-2019 \u2014 The Commissioning Process. Atlanta, 2019. Available at: official ASHRAE source<\/a>.<\/p>\n\n\n\n

[6] AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING ENGINEERS. ANSI\/ASHRAE\/IES Standard 202-2024 \u2014 The Commissioning Process Requirements for New Buildings and New Systems. Atlanta, 2024. Available at: official ASHRAE source<\/a>.<\/p>\n<\/details>\n\n\n\n

Frequently asked questions<\/summary>\n
What is commissioning in engineering?<\/strong>

It is the technical and documentary process that verifies and demonstrates whether systems, installations, and assets meet defined requirements, contractual criteria, and operating conditions.<\/p><\/div>

What is the difference between pre-commissioning and commissioning?<\/strong>

Pre-commissioning covers checks and tests performed before actual operation, such as inspections, calibrations, loop checks, and non-operational tests. Commissioning advances to controlled operation, integration, adjustments, and functional demonstration.<\/p><\/div>

Is commissioning the same as start-up?<\/strong>

No. Start-up is a transition milestone to actual operating conditions. Commissioning is broader and includes requirements, completion, pre-commissioning, testing, documentation, performance, and acceptance.<\/p><\/div>

What are cold commissioning and hot commissioning?<\/strong>

During cold commissioning, tests are performed without the actual process product, using controlled conditions or test media. During hot commissioning, equipment and systems operate under actual load or process conditions.<\/p><\/div>

When should commissioning begin?<\/strong>

It should be structured during the requirements and design phases so that it can influence testability, acceptance criteria, procurement, interfaces, documentation, and execution planning.<\/p><\/div>

What documents are required for acceptance after commissioning?<\/strong>

Depending on the scope, the package should include requirements, final design, completion certificates, test procedures and results, calibration records, outstanding items, as-built documentation, manuals, training records, warranties, the final report, and the acceptance record.<\/p><\/div><\/div>\n<\/details>\n\n\n\n

Additional technical resources<\/summary>\n\n

Whitepapers<\/h3>\n\n\n