What is industrial commissioning?
Commissioning is the process of progressively verifying that an installation, asset, or system has been installed correctly, tested, and can perform its intended function. It connects construction, testing, acceptance, and handover to operations.
It is not simply a matter of switching on a machine. The software retains checks, results, deviations, evidence, and approvals from fabrication through handover, the formal transfer of scope to operations.
Which lifecycle should connect construction, testing, and start-up?
A commissioning lifecycle may follow fabrication → FAT → installation → mechanical completion → pre-commissioning → commissioning → SAT/SIT → start-up → performance → handover. Exact names and criteria must be adapted to the contract and project.
Each phase should define prerequisites, checks, evidence, and exit criteria. A global status such as “87% complete” does not replace evidence that the relevant system is ready for the next phase.
What is the difference between mechanical completion, pre-commissioning, and commissioning?
Mechanical completion verifies that what had to be built or installed has been completed against applicable documents: equipment, piping, wiring, instrumentation, and guards. Pre-commissioning then prepares systems through cleaning, flushing, electrical tests, calibration, loop checks, and no-load tests.
Commissioning progressively operates systems to verify sequences, alarms, interlocks, automation, and interactions. Start-up then represents entry into operational running, according to the project rules.
What is a FAT?
FAT means Factory Acceptance Test. It is performed at the manufacturer’s facility or before final installation to verify that equipment or a system meets its specification before shipment. It may cover components, communications, PLC logic, alarms, interlocks, and operator interfaces.
A FAT should not be reduced to `FAT = PASS`. Each test case should retain its result, evidence, comment, person, conditions, and any punch item so the decision remains readable after delivery.
What is a FIT?
FIT means Factory Integration Test. This optional stage verifies the integration of several systems before they arrive on site, for example a supplier PLC, a SCADA system, and a safety system.
A FIT can reveal an interface incompatibility earlier than a test performed after installation. It should nevertheless remain tied to the project scope and agreed criteria, and should not be presented as mandatory in every context.
What is a SAT?
SAT means Site Acceptance Test. It takes place after installation at the final site and verifies that field connections, real interfaces, communications, and expected functions remain compliant in the environment where the system will operate.
The principle is simple: FAT = verification before delivery; SAT = verification once installed. Software should link tests to the actual equipment and conditions rather than copying a factory acceptance result.
What is a SIT?
SIT means Site Integration Test. It verifies interactions between several systems present on the site: PLC, SCADA, MES, network, safety system, or other units.
An asset may pass its individual SAT and fail during an integration test. The system should therefore retain the scope, dependencies, results, and corrective actions associated with the SIT.
How should systems and subsystems be structured?
Systemization, structuring an installation into commissionable systems and subsystems, makes it possible to complete, test, and hand over manageable scopes progressively. Example: plant → compressed air → subsystems → equipment.
Each system can group equipment, tags, checklists, documents, tests, punch items, a completion certificate, and handover status. The project does not necessarily have to wait for the whole installation before transferring a ready scope.
What is an equipment tag?
A tag is the identifier used to find an asset or component across drawings, lists, inspections, tests, punch lists, commissioning, and future maintenance. Examples include `P-204` for a pump, `XV-304` for a motorized valve, or `PT-103` for a pressure transmitter.
An application becomes much more valuable when it reuses tags from the project reference system. Recreating different identifiers in commissioning software creates manual reconciliation at handover.
What is an ITR?
ITR means Inspection and Test Record. It may check a pump’s foundation, alignment, bolts, lubrication, rotation, electrical connection, and guards, for example.
Each ITR should retain the asset, checklist, measured values, result, operator, date, photos, comments, approval, and generated punch items. A punch item found during the record should remain linked to the check that revealed it.
How should an industrial punch list be managed?
A punch list groups incomplete work, defects, or deviations to correct before an acceptance or commissioning milestone. Each item should identify the tag or system, description, discipline, owner, priority, due date, location, photos, and correction evidence.
The software should retain the closeout approval and relevant milestone. It is not enough to mark an item “done”: the system should show who verified the correction and on what evidence.
Do all punch items block start-up?
No. A missing safety guard may block start-up, while a missing permanent label may sometimes be accepted temporarily if safe temporary identification is approved. Minor documentation may be required before final handover.
The important point is not to impose a universal A/B/C classification, but to link each punch item to the milestone it blocks, the project rule, and the authority that may accept an open item.
How should loop checks be managed?
A loop check verifies the full chain between a sensor, a PLC input/output, logic, SCADA, and the expected alarm. The record retains the instrument tag, I/O channel, range, injected value, observed value, alarms, and result.
When a cause-and-effect matrix exists, software can link each test to the expected relationship and track anomalies without separating loop sheets, functional tests, and corrective actions.
How should I/O be tracked?
I/O means Inputs / Outputs in an automated system. The model can distinguish DI, DO, AI, and AO, then link each point to the tag, channel, test, and relevant equipment.
A status such as `NOT TESTED → TESTED → FAILED → RETEST REQUIRED → PASSED` makes progress measurable point by point. It avoids inferring system readiness from a general impression.
How should alarms, interlocks, and cause-and-effect logic be verified?
An interlock is logic that prevents or triggers an action when specific conditions are present. The test should record the simulated condition, expected response, actual response, result, evidence, and any corrective action.
Alarms and the cause-and-effect matrix should remain linked to tags and the versions of applicable documents. Software organizes testing; it must not invent a functional validation without an actual result.
How should performance tests be managed?
A successful functional test does not prove that contractual performance has been achieved. A line may operate while remaining below a target of 120 units per minute or above a maximum scrap rate.
The record should retain the target, measured value, duration, conditions, material used, team, data, comments, and result. The system therefore separates works from meets the expected performance.
How should multi-vendor testing be coordinated?
A single test may depend on an OEM, automation integrator, electrician, installer, operator, and end customer. The software should distinguish who executes, who witnesses, and who approves.
Each blocker becomes explicit: missing prerequisite, vendor expected, customer approval, or open punch item. Responsibilities, invitations, and decisions stay attached to the test instead of living in separate exchanges.
What is the difference between a witness point and a hold point?
A witness point is a step where a designated party must have the opportunity to attend a check or test. A hold point is a step beyond which the process cannot continue without authorization under the quality plan or contract.
These terms should remain configurable by project. Software can manage invitations, attendance, refusals, evidence, and approvals, but must not invent the contractual scope of a control point.
How should failed-test history be preserved?
A failed test should never be overwritten by a later result. History should show attempt 1 → fail → corrective action → retest → pass, with every piece of evidence and decision.
This chronology makes it possible to understand the original problem, number of attempts, corrective action, and person who approved the resolution. It protects the value of the record after start-up.
Which documents should be linked to commissioning?
The scope may include drawings, P&IDs, datasheets, OEM manuals, procedures, certificates, ITRs, loop sheets, FAT/SAT reports, test results, redlines, and as-built documents. Each revision should be identifiable.
Commissioning software does not replace a DMS. It should use the correct revision of the correct document and link it to the relevant tag, system, test, or package.
What is the difference between redline and as-built?
A redline is a document annotated during work to represent changes actually made. An as-built document is the final updated version representing the installation as built.
The path may be `P&ID Rev C → site redlines → engineering update → P&ID As-Built Rev D`. Handover should not be considered complete if operations receives documentation that no longer matches the field.
What should a handover dossier contain?
Handover is the formal transfer of a system or asset from the project team to operations. A package should bring together the completion certificate, equipment, tests, accepted open punch items, documents, as-builts, manuals, spare parts, training, warranties, and asset data.
The dossier is therefore not only a file archive. It should let operations understand what is approved, what remains open, which data becomes operational, and who owns responsibility after transfer.
Why transfer asset data together with PDFs?
After handover, maintenance needs a usable asset: manufacturer, model, serial number, commissioning date, warranty, maintenance strategy, documents, and spare parts. A PDF manual alone does not provide this structure.
Tags, documents, and test history should therefore be able to feed an asset register. The software prepares the transfer; it should not create a second reference system that conflicts with the ERP or CMMS.
How should commissioning connect to a CMMS?
Before handover: `equipment P-204 → commissioning → passed`. After transfer: `asset P-204 → CMMS → maintenance plan → spare parts → warranty`. Useful data is transferred once.
The CMMS becomes the owner of work orders and maintenance plans after start-up. The commissioning system remains the owner of construction, testing, and acceptance evidence according to the defined scope.
How should commissioning connect to CAPEX?
CAPEX tracks budget, orders, spend, and projects. Commissioning tracks installation, verification, testing, acceptance, and start-up. The commissioning milestone can then trigger CAPEX closeout or the capitalization process.
The software should not decide accounting capitalization on its own. It should instead transmit the date, assets, costs, or evidence needed by the finance process according to ERP and accounting rules.
How should warranties be activated at handover?
The asset record can retain the contractual warranty start: SAT, commissioning, provisional acceptance, or another event defined by the contract. It should also retain duration, supplier, scope, and expiry date.
This data helps maintenance answer quickly: is this failure still covered? The link should remain traceable to the industrial warranty-management workflow.
Should commissioning include mobile, offline, and QR-code workflows?
In the field, teams should be able to scan an asset, open a checklist, enter a measurement, photograph a defect, create a punch item, sign a step, and consult a drawing. An offline mode can store work packages, tags, and useful documents before synchronization.
A QR code, DataMatrix, or NFC tag can open the asset status directly. It remains a way to access information: critical approvals and final synchronization must follow the project’s safety and control rules.
What does IEC 62381:2024 change for FAT, FIT, SAT, and SIT?
IEC 62381:2024 is the third edition, published on July 30, 2024, for automation systems in the process industry. It defines requirements and checklists for FAT, FIT, SAT, and SIT, with an optional FIT and detailed checklists that can be adapted to the project.
This standard does not automatically regulate all mechanical commissioning for an entire plant. It is a relevant reference for the automation systems in scope; software should therefore retain its applicability and project-specific adaptations.
How should thousands of tests and progress be managed reliably?
The model should avoid a flat list and follow project → system → subsystem → tag → task/ITR → test → result. Certificates, punch items, documents, and statuses are then calculated at the level where decisions are made.
Progress can distinguish mechanical completion, pre-commissioning, commissioning, passed tests, blocking punch items, and handover-ready dossiers. This prevents a manual percentage from hiding the last critical checks.
How can false “95% complete” statuses be avoided?
A project can remain at 95% for months when progress is declared manually. An objective view counts objects actually completed: expected and signed ITRs, completed FATs, open blocking punch items, and issued certificates.
Status should be explainable by tag, system, test, and evidence. The project lead sees more than a number: they can immediately find what prevents a system from being declared ready.
Which KPIs should be tracked for commissioning?
Useful indicators include mechanical completion, pre-commissioning completion, commissioning completion, first-pass yield, punch backlog, blocking punch, punch aging, retest rate, handover readiness, and document completeness.
The most useful KPI is not document volume, but the number of systems that can actually be handed over today. Indicators should lead to action: follow up a vendor, close a punch item, correct a test, or complete a dossier.
What role should AI play in commissioning?
AI can help convert old Word or Excel forms into checklists, classify punch items, summarize system deviations, identify missing documents, find similar defects, and prepare a handover report.
It should never decide `FAT = PASS`, `SAT = PASS`, or `READY FOR START-UP` on its own. Validation criteria remain deterministic and final decisions remain approved by responsible people.
Hexagon, Omega 365, or custom commissioning software?
Hexagon Smart Completions covers mechanical completion, pre-commissioning, commissioning, start-up/handover, ITRs, punch lists, and mobile/offline execution. Omega 365 Completion Management links systems, subsystems, tags, checklists, punch items, procedures, handover, and asset information.
Custom software becomes relevant when the process is much simpler or more specific, an ERP or CMMS already exists, historical forms are unusual, an OEM portal is needed, or several applications must be connected. A fit-gap should precede any attempt to rebuild a mature standard.
How much does industrial commissioning software cost?
Main factors include the number of tags, systems, disciplines, FAT/SAT activities, checklists, mobile/offline needs, punch lists, documents, QR/NFC, vendors, CMMS/ERP integrations, possible 3D/BIM, Excel migration, reporting, and handover.
Three scopes should be separated: FAT/SAT with checklists, evidence, signatures, and punch items; commissioning with tags, systems, ITRs, punch, pre-commissioning, commissioning, and handover; and completion management with engineering, construction, multi-contractor coordination, asset data, and maintenance handover. These scopes do not justify an artificial average.
How would Koragence structure a commissioning project?
Scoping starts with a system or asset that has actually been commissioned: FAT, field checklists, punch items, SAT, and final dossier. The goal is to identify the milestones, checks, owners, and evidence actually required.
Assets are then organized into equipment, subsystems, and systems to track objective progress and prepare progressive handovers. A first version can cover FAT/SAT, punch lists, and documents before adding field commissioning, mobile, CMMS, and asset handover.
