Hand over to commissioning.
From engineering documents to a commissioning-ready package keyed by system
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 + JSON for the commissioning tool
| 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.
- 01
Establish system boundaries
Upload 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).
- 02
Filter the I/O list per system
Loops fully inside the system populate the per-system loop folder index. Cross-boundary loops carry an interface-scope flag.
- 03
Slice the cable schedule
Cable schedule rows carrying tags in the system filter into the per-system cable book. JB schedule follows the cable filter.
- 04
Group the equipment list
Equipment tags filter per system. Package skids preserve the parent-skid grouping inside their system.
- 05
Generate MC and RFSU sheets
Per-system check sheet templates populate with the loop, equipment, and instrument tags. The commissioning engineer fills field-verified status as the system progresses.
- 06
Hand over the package
Excel workbook per system + 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?
Cross-boundary loops carry an explicit interface-scope flag. The two affected systems each receive the loop with the boundary marked; the commissioning sequence must align the two systems' MC dates for the interface. Loops crossing more than two systems are flagged for re-scoping.
Can the per-system packages feed Bechtel BCMS or Worley CompEx?
Yes. JSON export per system carries the loop, equipment, and instrument tag list in the column shape these commissioning databases import. Custom shapes for in-house tools are configurable through the API or MCP server.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.