Commissioning is where an on-time construction project quietly becomes a late startup project. The concrete cured on schedule, equipment landed on time, contractors handed off — and then the plant runs at a fraction of design throughput for six months while every discipline discovers what nobody quite finished. A working plant commissioning checklist walks the disciplines in sequence — mechanical completion, electrical energization, instrumentation loop check, controls (PLC, SCADA, MES), safety systems and PHA closeout, and — critically — data readiness so the plant runs with visibility from day one rather than blind for its first two quarters. The last item is where most projects fail, because construction contracts rarely make it anyone's job.
iFactory / Greenfield plant commissioning
Commission Every Discipline — Including Data Readiness — Before First Product
Structured commissioning checklist covering mechanical, electrical, instrumentation, controls, safety, and data readiness — so the plant starts with full visibility instead of running blind for the first quarter of production.
3
Instrumentation loop check
6
Data readiness → MES / historian
MES + historian
ready at go-live
The Problem in Greenfield Commissioning
A typical greenfield plant project runs commissioning as a construction-team-to-operations-team handoff. Construction hands over mechanical completion; operations receives the plant and begins startup. Six weeks in, operators discover instrumentation loops that were never fully commissioned. Three months in, the MES integration that was supposed to run from day one is still being configured because historian tags were never mapped. Six months in, the plant is producing but nobody has the operational data to run continuous improvement — because the data infrastructure was never commissioned alongside the physical infrastructure. Meanwhile the construction contract closed months ago and resources to fix data readiness are no longer on site.
Where Commissioning Actually Slips
Greenfield commissioning failure modes are consistent across process, discrete, and hybrid manufacturing. Each is a specific commissioning-checklist gap.
Loop check thin
Instrumentation loop checks run on sample basis rather than 100%. Startup discovers loops that read incorrect ranges, transmitters miswired, alarms untested. Weeks of engineering time absorbed post-startup.
Controls unfinished
PLC and SCADA logic tested in isolation but not integrated with MES or historian. Batch execution manual, historian tags missing, control-room views incomplete. Operations runs on partial information.
Safety incomplete
Process hazard analysis (PHA) actions not closed pre-startup. Interlocks tested but not validated in operating conditions. Safety cases open at go-live — high regulatory and insurance exposure.
Data blind
MES, historian, and OEE reporting not commissioned as part of the project. Plant runs six months producing product without operational data — improvement conversations impossible.
What Good Looks Like in Commissioning
A working commissioning discipline holds six gates in sequence — each with defined completion criteria and each preventing the next gate from opening until closed.
Mechanical Gate
Mechanical completion with punch list closed to a documented threshold. Equipment installed, aligned, lubricated, and ready for energization. Vendor sign-off captured.
Punch list to threshold
Electrical Gate
Electrical energization with megger testing, motor rotation verification, protection settings loaded. All motors bumped and verified. Utility supply stable.
Meggered, rotated, verified
Instrument Gate
100% instrumentation loop check with range verification, alarm test, and interlock functional test. Not sample — every loop, every alarm.
100%, not sample
Controls + Data
PLC, SCADA, MES, and historian integrated and tested end-to-end. Control room views complete. Historian tags mapped. First product runs with full data capture, not blind.
Data ready at go-live
How iFactory AI Fits
iFactory AI overlays your project management, commissioning software, and target operational systems (MES, historian, LIMS, QMS) — providing the data readiness gate that construction-focused commissioning software rarely covers.
Gate Registry
Commissioning Layer
Every gate with defined completion criteria, evidence attachment, and cross-discipline sign-off. Gates that show incomplete cannot open the next gate without documented exception.
Loop Verification
Commissioning + Controls
100% instrumentation loop check tracked to individual loop. Range, alarm, and interlock verification captured with signed evidence per loop.
Data Readiness
Commissioning + MES
MES, historian, and OEE reporting configured and tested with production-representative data before go-live. Historian tag map complete. Reports validated against expected output.
PHA Closeout
Commissioning + Safety
Process hazard analysis actions tracked with evidence of closure. Interlocks validated in operating conditions. Safety case complete before first product.
Ask your project manager to produce the commissioning gate status for the next greenfield project 8 weeks before go-live. If the data readiness gate does not exist or is populated with "to be defined," the plant is on track to run blind. Book a commissioning review.
20-Week Commissioning Rollout on One Project
One greenfield or major expansion project in commissioning phase, twenty weeks. The pilot deploys the six-gate structure through the remaining commissioning window, closes each gate to evidence, and hands over a fully-instrumented plant.
Weeks 1–4
Gate Structure
Load project scope and existing punch list. Configure six-gate structure with per-discipline completion criteria. Baseline where the project currently stands on each gate.
Weeks 5–10
Mechanical + Electrical
Mechanical and electrical gates closed to evidence. Punch list reduced to documented threshold. Utility supply verified. Motor and rotating equipment verified.
Weeks 11–16
Instrument + Controls
100% loop check completed. Controls and MES integrated and tested end-to-end. First-batch simulation runs through the fully-configured stack.
Weeks 17–20
Safety + Data Gate
PHA closeout to documented actions. Data readiness gate closed with historian tags mapped and OEE reporting validated. Go-live authorized with full visibility.
Who Owns the KPI
Commissioning crosses project management, engineering, operations, IT, and safety. Each function owns a specific gate or the checklist becomes another checkbox exercise.
Project Manager
Gates closed on schedule with evidence
Owns the project outcome — the share of gates closed on schedule with full evidence. Gates that slip or close without evidence carry directly into operational shortfall.
Engineering Lead
Loop check 100% before go-live
Owns the instrumentation completeness — every loop verified with range, alarm, and interlock test. Sample-based check accepts hidden gaps.
Operations Lead
Ramp-up vs pro forma
Owns the startup outcome — the ramp to designed throughput vs the pro forma schedule. Slow ramp signals commissioning gaps that operations is absorbing.
IT / OT Lead
Data readiness at go-live
Owns the digital-operational readiness — MES, historian, and OEE reporting functional at go-live. Blind operation for the first quarter is a specific commissioning failure.
FAQ
What's the difference between commissioning and qualification — pharma has both?
In regulated environments (pharma, medical device, biotech), commissioning is the engineering activity that verifies equipment installed and operating as designed; qualification is the regulatory activity that formally documents installation qualification (IQ), operational qualification (OQ), and performance qualification (PQ) per FDA and EU GMP requirements. The ISPE Baseline Guide and ASTM E2500 support a science-and-risk-based approach that integrates commissioning and qualification activities where scope permits — reducing duplicate testing while preserving regulatory evidence. The workflow supports both models: pure commissioning for non-regulated environments, integrated C&Q for regulated environments per ASTM E2500 or client-specific standards.
How does the data readiness gate integrate with our MES and historian?
Data readiness requires that MES, historian, LIMS, and OEE reporting are configured, tag-mapped, and tested with production-representative data before first product runs. The gate specifically covers: historian tag map complete for all critical process variables; MES batch and order routing configured; OEE reporting functional with sample data producing expected output; control room views complete for supervisor and operator roles; alarms and event triggers tested against production scenarios. Where the plant runs Rockwell FactoryTalk, AVEVA Wonderware, Siemens Opcenter, PI System, or GE Proficy, the gate configures per those specific systems. What matters is not the platform — it is that the plant does not run blind for a quarter of production while data infrastructure catches up.
Book a demo to see the data gate framework.
Who typically owns the commissioning checklist — construction, engineering, or operations?
Best practice is that the commissioning manager reports to operations rather than to construction, with construction, engineering, and operations all named on the gate sign-offs. When commissioning reports to construction, the incentive is to close gates fast enough to hit construction completion milestones; when commissioning reports to operations, the incentive is to close gates thoroughly enough to prevent operational shortfall. The gate-based workflow supports whichever reporting structure the project uses but makes sign-off responsibilities explicit — no gate closes without the named discipline's evidence and sign-off. This structure protects against the classic pattern where construction hands over incomplete work under schedule pressure and operations absorbs the cost.
Stop letting plants run blind for their first quarter.
Design the Data Readiness Gate for the Next Project — Live
Bring your next greenfield or major expansion project's current commissioning plan and target operational systems (MES, historian, LIMS). We'll walk the six-gate structure, highlight where the data readiness gate belongs, and demonstrate the go-live visibility that changes.
