Industrial & Manufacturing
›
Industrial Manufacturing & Robotics
›
Plant Startup & Expansion
Plant Commissioning
Complex deployments where integration, safety, and operational handoff determine production success.
Example organizations in this space:
Emerson
Siemens
Honeywell
Burns & McDonnell
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Pre-Sales
Qualify and diagnose before investing in a full engagement scoping.
-
Qualification
Confirm timeline to mechanical completion, decision authority, urgency, and the buyer's immediate commissioning resource gaps before a full diagnostic.
Qualification Questions
Mechanical completion and urgency
- To make the best use of your time, what is your current best estimate for the mechanical completion date or window?
- How many weeks from today do you expect mechanical completion?
- What is the primary schedule driver or constraint that could compress or extend that window?
Decision authority and stakeholders
- Who is the ultimate decision maker for selecting commissioning support on this project (role, not name)?
- Who else will materially influence the decision or contract terms (roles or teams)?
Immediate commissioning resource gaps
- Which commissioning roles or capabilities are currently missing or under-resourced on your team?
- If you could address one gap first to reduce schedule or safety risk, which would it be?
Budget and immediate next step
- Is there an allocated budget or an approval path identified for bringing in external commissioning support?
- To decide whether a full diagnostic is warranted, would you like to schedule a 45-minute call to review these answers and next steps?
-
Outcome Discovery
Map systems approaching mechanical completion, critical equipment types, safety and schedule risks, stakeholders, and success signals for handover.
Discovery Questions
A quick scene setter: Where are we right now?
- Tell me briefly where you are in the run-up to mechanical completion and your target handover date.
- Which major systems on your site are scheduled to reach mechanical completion in the next 6 to 8 weeks?
- How many discrete system handovers do you expect to run in parallel during your peak commissioning window?
- Who on your team currently owns the commissioning schedule and who has final sign-off authority for system acceptance?
Where the schedule is most fragile
- If a single delayed tag pushed your first energization out by two weeks, which system delay would cause the largest cascade of schedule or regulatory risk?
- Walk me through the three root causes of delay you have seen on this project so far, with examples of what triggered each one.
- How often have construction punch items forced retesting of completed systems on projects you have run in the last two years?
- Which schedule buffer, if any, do you have between mechanical completion and planned system energization?
- Which single schedule risk, if it materializes, would make you stop mobilizing the commissioning team immediately?
Hidden safety and performance risks we should not ignore
- Which piece of equipment or operating procedure causes you the most concern for safety or process integrity during first energization?
- Describe any recent near misses, vendor returns, or failed factory tests that relate to equipment planned for early commissioning.
- On a scale from 1 to 5, how confident are you that the current instrument loop documentation and calibration status will support functional testing without rework?
- Do you have named safety representatives and a documented permit-to-work process available for simultaneous energized testing across multiple crews?
- Which contingency would you require before allowing energized testing to proceed if a critical vendor-delivered part is late?
Stakeholders who will make or break the handover
- Name the roles that must give formal acceptance for each major system and identify who currently occupies those roles on your side.
- How accessible are your permanent operations staff for training and shadowing during commissioning, in terms of headcount available per shift?
- Who needs to be present for vendor interface meetings and who will be able to approve vendor remedial work on site?
- What escalation path is used when commissioning issues threaten the commercial handover date, and who sits at the top of that path?
- Which stakeholder objection, if raised late in testing, would force a retest or delay formal acceptance?
Evidence that will convince you to accept a system
- Which single test result, document, or metric would make you comfortable signing acceptance for a system?
- List the minimum set of artifacts you require at handover for each system (for example: loop sheets, test logs, vendor certificates, SOPs).
- How do you prefer performance acceptance to be measured, by steady-state throughput, emission limits, or other metrics?
- If a system meets the documented functional tests but shows degraded performance during a performance run, what outcome will you accept?
- Which acceptance condition would cause you to refuse handover outright?
Other options you are weighing right now
- Which alternatives to engaging an external commissioning team are you actively considering?
- What would have to be demonstrably true about your current approach for you to stay with it rather than change partners?
- Has anyone on your team proposed solving commissioning without an outside partner, and if so what plan did they present?
- How do the cost and timeline estimates from other vendors or internal plans compare to your internal target for this project?
- Which advantage offered by another option would be most persuasive for you to switch away from the current plan?
Operational readiness and gating constraints
- Which missing permit, site access approval, or vendor clearance would stop mobilization immediately if unresolved?
- Who owns the instrument loop lists and tag validation on your side, and are those lists locked for commissioning?
- Do you have the minimum headcount available in your operations team to accept handover on the planned date, and if not, what is the gap?
- Are there regulatory approvals or third-party witness tests that must occur before you can accept system commissioning?
- Which infrastructure or logistics dependency is at highest risk of failing (examples: spare-part availability, vendor field engineer arrival, site access windows)?
- If we identify a gating constraint today, what internal decision process and timeline would unblock it?
Commercial and governance realities that move decisions
- Who on your side must approve contract terms, insurance, and safety governance to enable mobilization?
- Describe the quickest path to purchase on your side, including the typical procurement lead time for services like this.
- Which contractual requirement would cause you to pause negotiations or require escalation?
- If the first contracted scope proves the approach and schedule, who could approve expanding the scope without restarting procurement?
- What single commercial condition would make you sign and mobilize within two weeks?
Bringing it together: must-have success signals and immediate next steps
- Which operational success signals must be proven in the first 30 days after energization for you to call the engagement a success?
- Describe the one acceptance metric that, if missed, would require a full repeat of the performance test.
- How quickly do you expect issues found during initial runs to be resolved by vendors or site teams, in days?
- Who on your team should we bring into a decision call if we surface a gating safety issue during pre-energization?
- What concrete next step would most accelerate alignment between your team and the seller after this discovery conversation?
-
-
Solution Experience
Walk through how the commissioning engagement will deliver safe, on-schedule startup — system-by-system sequences, vendor interfaces, and operator training in the buyer's context.
Solution Experience
- Solution Experience Session
- Confirm the current state and what it is costing you
- You confirm the stated current state and accept the quantified consequences (safety risk, rework, schedule slip) as accurate.
- Deliver a system-specific commissioning sequence and timeline for the reviewed system, including named vendor interface points and vendor return thresholds, before the follow-up session.
- You confirm the demonstrated system sequence removes the key risks for the reviewed system and is realistic within your mechanical completion window.
- Walk through the commissioning sequence for your highest-risk system
- Map applicable procedure library items to the reviewed equipment and provide sample procedures for you to validate.
- Show vendor interface and remediation workflow
- You confirm the operator training and named-owner handover approach will achieve operational readiness, or identify specific gaps to close before mobilization.
- Provide confirmed mechanical completion windows and any site access or permit constraints for the reviewed system.
- Outline operator training and handover sequence
- Share the list of permanent operations staff to be trained and their availability windows for scheduling training and handover shifts.
- You agree on the specific evidence required before a go/no-go decision, such as procedure samples and a mobilization timeline.
- Validate this maps to what you described needing
- Solution Experience Session
- Solution Experience Deck
- Solution Experience Brief
- meeting
- slides
- document
-
Solution Scope
Define which systems, equipment, procedures, team qualifications, deliverables, timelines, responsibilities, and out-of-scope items are included.
Scope Configuration
- Execute equipment-specific startup procedures
- Instrument loop calibration and checkout
- Control system functional testing and sequence checkout
- Electrical system energization and relay testing
- Piping flushing, chemical cleaning, and leak testing
- No-load rotation and vibration monitoring for rotating equipment
- Compressor and turbine load ramp and performance startup
- Boiler and heater light-off with combustion tuning
- First-fill, controlled process introduction and stabilization
- Run vendor-witnessed equipment tests on-site
- Execute performance tests and produce acceptance report
- Operations handover training and turnover documentation
Scope Questions
Execute equipment-specific startup procedures
- Which equipment manufacturers and model numbers (motor/compressor/heat exchanger tags) require use of vendor-provided startup procedures?
- How many pre-approved procedure templates from your procedure library map directly to installed equipment tag numbers on the P&ID (piping and instrumentation diagram)?
- Do you have final as-built P&IDs and instrument index available to reference procedure step numbers and tag lists?
- Provide the commissioning procedure ID or reference (e.g., CP-xxxx) you want used for major rotating equipment and high-pressure vessels.
- Who will approve redline updates to a procedure during field verification (provide role and contact for procedure sign-off)?
- Are there site-specific work control requirements (for example lockout/tagout (LOTO) permit numbers or hot work permit references) that must be embedded in each startup procedure?
Instrument loop calibration and checkout
- Which instrument loop list (loop check pack) revision will you provide as the baseline for calibration and loop checkout?
- How many field instruments (pressure, temperature, flow, level) are on the loop list and require on-site calibration?
- Do you have instrument manufacturers and serial numbers documented for transmitters and I/O modules to confirm spare part and calibration kit compatibility?
- Identify any fieldbus or HART device configuration requirements or tag-level parameter values that must be set during loop checkout (for example range, damping, square root extraction).
- Are there factory calibration certificates or vendor calibration labs required for critical safety instrumented system (SIS) devices before loop closure?
- When is instrument I/O mapping to the control system finalized (provide milestone date tied to mechanical completion)?
Control system functional testing and sequence checkout
- Which distributed control system (DCS) or programmable logic controller (PLC) I/O list revision will be used for functional test mapping?
- How many control sequences or batch recipes require step-by-step functional testing during commissioning (reference sequence IDs or recipe names)?
- Do you have sequence logic narratives or sequence of operations documents for each major process train to use as the test script baseline?
- Provide the required integration points for vendor skids or package units (for example interlock I/O tags, setpoint handshakes, and permissive signals).
- Are safety instrumented functions (SIFs) included in the functional testing scope and do you require witnessed proof tests before handover?
- Who will provide final approval of sequence completion (role and contact) and what documentation will serve as evidence (for example signed functional test pack)?
Electrical system energization and relay testing
- Which single-line diagrams (SLD) and switchgear panel schedules will be the authority for energization steps (provide drawing numbers or revision)?
- How many motor control centers (MCCs), transformers, and main distribution panels require staged energization and insulation resistance tests?
- Do you require primary injection or secondary relay testing witnessed by commissioning and electrical vendor representatives?
- Are there site electrical safety rules and arc flash boundaries (provide arc flash study reference) that must appear in the energization procedure?
- Describe the acceptance threshold for relay pickup/dropout timing and coordination used to declare the panel energized (for example milliseconds or coordination curves).
- Who coordinates utility tie-in or grid operator notifications for bulk power transfer and what lead time is required?
Piping flushing, chemical cleaning, and leak testing
- Which piping circuits require chemical cleaning or passivation (provide line numbers or P&ID references)?
- What flushing medium and chemical specifications are mandated (for example inhibited glycol, sodium bisulfite, citric acid) and do you have SDS sheets available?
- How many hydrostatic or pneumatic pressure tests are planned and what test pressures and hold times are specified on the test pack?
- Do you require microbiological or particulate cleanliness verification for process lines (for example ISO cleanliness levels or particle counts)?
- Who will own remediation for test failures (piping weld repair, gasket replacement) and what punchlist workflow must be used to track rework?
- Are vendor warranty conditions tied to completion of flushing and preservation steps (for example requirement to witness passivation before handover)?
No-load rotation and vibration monitoring for rotating equipment
- Which rotating equipment tag numbers require initial no-load rotation and baseline vibration capture (provide tag list or count)?
- Do you have required vibration alarm/trip thresholds or allowable runout limits from the vendor manual or API standards to use for monitoring?
- How will oil sampling and bearing temperature baselines be recorded (for example lab certificate, inline oil sensor readings)?
- Who performs shaft alignment verification and are laser alignment certificates required for acceptance?
- Are remote or wired route points (vibration sensor tag IDs and locations) included in the instrument loop list for trending in the control historian?
- When must baseline no-load vibration spectra be captured relative to mechanical completion (provide a target window in days)?
Compressor and turbine load ramp and performance startup
- Which compressor and turbine units require vendor witness during first load ramp (provide unit tag numbers and vendor test pack reference)?
- How many staged load steps are defined in the vendor performance curve and will each step require signed data sheets?
- Do you have guaranteed performance points (flow, head, efficiency) in the purchase order that must be met during the performance ramp?
- Provide the allowable temperature, vibration, and lube-oil limits from the OEM manual that define an abort condition during ramp.
- Who will coordinate vendor return visits if a unit fails to meet ramp criteria and how should vendor corrective actions be documented?
- Are performance instrumentation calibration certificates required prior to load runs (for example flowmeter calibration traceable to a lab)?
Boiler and heater light-off with combustion tuning
- Which boilers and fired heaters are in scope and what are their burner control package model numbers and combustion air fan tags?
- Do you have permitted emission limits or stack test requirements that must be met during initial light-off (provide permit reference)?
- Are your fuel system hookups (gas, oil, dual-fuel) verified with vendor checklists and local utility approvals before light-off?
- Provide the combustion tuning acceptance thresholds (CO, O2, NOx ppm targets) or reference the required emissions standard.
- Who will execute or witness stack analyzer readings and where will those readings be logged (for example stack test report template)?
- Are refractory or catalyst activation procedures included in the light-off sequence and do they require temperature soak hold times documented in the procedure?
First-fill, controlled process introduction and stabilization
- Which process trains or vessels are designated for first-fill and controlled introduction (provide tag list or P&ID references)?
- How will first-fill volumes and feed rates be validated (for example mass-balance, calibrated flowmeters, or batch receipts)?
- Do you require chemical analysis confirmation (for example concentration or pH lab certificate) before progressing beyond initial stabilization?
- Provide the stabilization acceptance criteria (for example percent deviation from steady-state on key product quality parameters and the acceptable time window).
- Who will be the named process owner responsible for authorizing handover from stabilization to production trials (provide role and contact)?
- Are there environmental, safety, or permit conditions that restrict first-fill timing (for example wastewater discharge limits or confined space entry windows)?
Run vendor-witnessed equipment tests on-site
- Which vendor tests are contractually required to be witnessed on-site (for example vibration acceptance, performance run, bearing acceptance) and what are the vendor test pack IDs?
- How much advance notice do vendors require to mobilize witnesses and what are their minimum on-site durations?
- Do vendors require isolation of other systems or dedicated utilities during the witness test (for example dedicated compressed air or fuel lines)?
- Who will sign the vendor witness certificates on completion and what format is acceptable (for example vendor signature on ATP sheet or signed test report)?
- Are there site visitor or access requirements for vendor staff (badging, safety orientation, medical clearances) that we must schedule before witness events?
- Identify any travel, accommodation, or tool crib coordination constraints that could affect vendor witness scheduling (for example single gate access hours).
-
Mutual Commit
Finalize commercial and safety terms, acceptance criteria, insurance and governance, and confirm readiness to mobilize for field execution.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Commercial Terms Exhibit
- Safety Addendum
- Acceptance Criteria & Handover Certificate
- Insurance Requirements & Certificate of Insurance
- Mobilization & Readiness Confirmation
- Change Control & Governance Agreement
-
Deployment
Operationalize rollout with readiness checks, execution, and outcome validation.
-
Pre-Deployment Readiness
Capture concrete readiness facts the field team needs — mechanical completion windows, site access, permits, vendor return logistics, and named operations owners.
Pre-Deployment Questions
Environment and site access
- List each site included in this deployment (site name and physical location; we use this to assign field teams and travel logistics)
- For each listed site, provide the mechanical completion window (start date and end date) the buyer expects for system handover (so we can schedule on-site checks and mobilization)
- Primary site access and security requirements (select all that apply; these determine arrival procedures and lead times for badges/escorts)
Permits, vendors & logistics
- Are required permits and authorizations for pre-commissioning, testing, and energization issued per site? (answer lets us sequence work and flag blockers)
- If permits or vendor approvals are pending, list the permit/approval type, the responsible party, and the expected issue date (so we can plan conditional activities)
- Vendor return and on-site support logistics: will equipment vendors be available on-site for remediation/assistance during the first 4 weeks post-mechanical completion?
- If vendors are committed on-site, list each vendor contact, role, and committed on-site date window (we use this to align vendor visits with failed-test remediation)
People and ownership
- Named operations owner for handover (name, role, and best phone contact; this person will accept operator training and final handover)
- Operations team coverage during deployment (select the option that matches planned operator support during field execution)
- Approval authority for mobilization (name and role of the person who will issue go/no-go to mobilize field crews)
Timing and constraints
- List any firm blackout / no-work windows (dates/times per site when testing, energization, or vendor work is prohibited; we must schedule around these)
- Is there a confirmed earliest mobilization date and latest demobilization date for the seller field team?
-
Commissioning Configuration
Lock execution inputs the team will use — approved procedures, instrument loop lists, test checklists, vendor contacts, spare-part plans, and shift coverage.
Configuration Details
Commissioning Configuration — Execution Inputs (Deployment step)
- Primary approved procedure library location (enter a URL or UNC/file-path the execution system will read; e.g., "https://repo.company/share/commissioning/procedures" or "\\share\commissioning\procedures"). Default: keep blank if you will provide at mobilization.
- Procedure versioning policy consumed during Site Execution (select one). Default is the first option.
Instrumentation & Loop Lists
- Master instrument loop-list file location (enter a URL or file path to the single master file the field teams will use; format: path to a file the deployment system can fetch).
- Canonical loop-list format consumed by execution (select one). If your format is not listed, choose 'Other' and provide format name in the next question.
Test Checklists & Templates
- Primary functional-test checklist package location (enter URL or file path to the checklist set the Site Execution step will use).
- Energized-test checklist variant to apply during Pre-Energization & Handover (select one). Default is the first option.
- If you selected 'Custom' above, enter the custom checklist template name exactly as it appears in the procedure library (leave blank if not applicable).
Vendors, Spares & Coverage
- Primary vendor contact roster location (enter URL or file path to the master vendor-contact file the deployment process will reference).
- Spare-parts kit strategy the execution team will enforce (select one). Default is the first option.
- Primary named operations owner role for handover (enter role/title exactly as used in your org; e.g., "Operations Shift Supervisor"). This value is used on the Handover Sign-Off checklist.
-
Site Execution
Plan and execute pre-commissioning, functional and energized testing, performance runs, and operator training with named owners and a sequenced schedule.
-
Pre-Energization & Handover Sign-Off
Mandatory go/no-go gate: verify safety checklists, successful test evidence, vendor remediation, and operator readiness before energization and formal handover.
Checklist items
- Obtain written Permission-to-Energize (PTE)
- Confirm Lockout/Tagout (LOTO) removal and clearance
- Receive completed pre-energization safety checklists for each system
- Accept final functional and loop test reports
- Verify closure or accepted mitigation of all pre-energization non-conformances assigned to vendors
- Receive operator training completion and competency sign-offs
- Accept alarm, trip and emergency shutdown (ESD) validation report
- Confirm critical spares and vendor support logistics
- Document energization sequence, nominated energization lead, and crew roster
- Accept control system I/O mapping and HMI acceptance report
-
-
Success
Confirm operational acceptance against success signals, capture lessons learned, and maintain a shared channel for open issues, vendor returns, and enhancements.
Success Reviews
- Go-Live Health Check (Week 1-4)
- 30-Day Performance Review (Week 4-10)
- 90-Day Operational Realization Review
- Quarterly Operational Review (Ongoing)
Issues & Enhancements
- Update the spare-parts inventory plan with any one-time replenishments required to support the next remediation sprint.
- Present 90-day outcomes vs targets
- Produce a documented status for each handover success signal showing met/partially met/unmet and associated remediation actions.
- Agree a time-bound remediation sprint to close all high-severity defects and vendor returns referenced in the outcome data.
- Confirm operations owners are named for ongoing monitoring and that the shared issues channel will be the single source of truth.
- Issue a 90-day status report linking evidence to each success signal and publish remediation sprint backlog.
- Schedule targeted vendor return visits and list required acceptance evidence for each visit in the shared tracker.
- Consolidate lessons learned notes into the shared document for the annual session.
- Trend review for core metrics
- Ensure operator training proficiency and issue resolution times remain at or move toward Solution Scope targets.
- Reduce the count of persistent high-impact issues by defining focused remediation work for the next quarter.
- Maintain a clear vendor return schedule and spare-part plan to prevent repeat failures.
- Publish the quarter backlog with priorities, required acceptance evidence, and resolution target dates.
- Open a tracked workstream for any detailed review root causes identified and set a checkpoint in 30 days.
- Confirm scope and success signals owners
- Handover evidence and test packets verified as accessible in the shared workspace.
- All high-severity open issues and vendor returns identified and assigned remediation actions with target dates.
- Operator onboarding status confirmed and any immediate training gaps scheduled for closure within two weeks.
- Publish a one-page handover completeness checklist and attach missing documents to the shared channel.
- Create remediation tickets for each open vendor return with target on-site date and specimen acceptance evidence required.
- Schedule follow-up site walk or remote session for any items requiring clarification within 7 calendar days.
- Present first 30-day data
- Determine whether functional test pass rate and operator training proficiency rate are trending toward the Solution Scope targets and document any shortfalls.
- Produce a prioritized remediation plan to close open critical remediations within the agreed window.
- Confirm that incumbent commissioning activities are formally retired or documented as read-only to prevent parallel work streams.
- Publish a prioritized list of open critical remediation tickets with target close dates and required acceptance evidence.
- Update the training roster and schedule targeted refresh sessions for operators below the proficiency threshold.
- Record the incumbent wind-down status in the shared tracker and escalate any remaining overlaps for immediate closure.
- Validate handover artefacts and test evidence
- Root-cause diagnosis for metric gaps
- Document status per acceptance criterion
- Detailed review persistent blockers
- Agree remediation sprint and owners
- Early operational signals review
- Vendor returns and spare-parts readiness
- Incumbent wind-down checkpoint
- Capture preliminary lessons learned
- Prioritize next quarter backlog
- Open issues and vendor returns triage
- Agree corrective actions and timelines
- Agree immediate remediation actions
- Confirm path to next gate