Hand over to commissioning.
From engineering documents to a commissioning-ready package keyed by system
What this covers.
Handing over to commissioning is the engineering process of restructuring the project documents, I/O list, instrument index, cable schedule, JB schedule, loop diagrams, datasheets from per-discipline format to per-system commissioning packages. Commissioning works by system, utility, process unit, package, sub-system rather than by discipline. The per-discipline documents get re-sliced for the commissioning manager. Each system package carries the loop folder index, the cable run-out, the JB termination scope, and the field-verification check sheets. Mechanical completion, MC and ready-for-startup, RFSU cannot be declared without complete system packages.
Inputs.
- Engineering document set, I/O list, instrument index, cable, JB, loop diagrams, equipment list, datasheets
- System boundary table, which tags belong to which commissioning system
Outputs.
- Per-system package. I/O list, cable schedule, JB schedule, loop folders, equipment list, datasheets, all filtered to the system
- Per-system mechanical-completion, MC check sheet template
- Per-system ready-for-startup, RFSU check sheet template
- System interface scope. Tags where the system boundary cuts across a loop
- Export targets. Excel workbook per system plus JSON for the commissioning tool
Per-discipline vs. Per-system document structure
| Document | Engineering format | Commissioning format |
|---|---|---|
| I/O list | Full project by tag | Filtered per system, with loop folders |
| Cable schedule | Full project by cable number | Per system, by JB and run-out |
| Datasheets | Binder by vendor | Per system, by tag in the system |
| Loop diagrams | By loop type | Per system, by loop in the system |
| Equipment list | By tag, project-wide | Per system, with parent skid grouping |
| P&ID set | By drawing number | Per system, with the boundary marked |
Step by step.
- 01Establish system boundariesUpload the system boundary table. Each loop, equipment tag, and line number maps to one commissioning system. Cross-boundary loops flag for review, they require explicit interface scope.
- 02Filter the I/O list per systemLoops fully inside the system populate the per-system loop folder index. Cross-boundary loops carry an interface-scope flag.
- 03Slice the cable scheduleCable schedule rows carrying tags in the system filter into the per-system cable book. JB schedule follows the cable filter.
- 04Group the equipment listEquipment tags filter per system. Package skids preserve the parent-skid grouping inside their system.
- 05Generate MC and RFSU sheetsPer-system check sheet templates populate with the loop, equipment, and instrument tags. The commissioning engineer fills field-verified status as the system progresses.
- 06Hand over the packageExcel workbook per system plus JSON export for the commissioning tool, Bechtel BCMS, Worley CompEx, in-house. The handover is structured to the commissioning sequence.
Common questions
What happens when a loop crosses a system boundary.
Can the per-system packages feed Bechtel BCMS or Worley CompEx.
Related.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.