How to Choose a System Integrator for a Plant Project
How do you choose a system integrator for a plant project?
Choose a system integrator by asking for evidence of relevant work, a clear functional design specification, an agreed testing approach and usable handover documents. Compare proposals against the same scope, including shutdown constraints, acceptance criteria and support after handover. Before appointing anyone, establish who will do the work, what your plant must provide and how unresolved problems will be handled. When comparing quotes, see the costs often missed in a control system budget.
What should you define before requesting proposals?
Prepare a short project brief before comparing suppliers. Describe the operating problem, the equipment involved and the outcome your team needs to accept.
Include:
- Scope: equipment, controls, screens and interfaces included, plus explicit exclusions.
- Site constraints: access, production windows, shutdown availability and existing equipment that must remain.
- Responsibilities: who supplies drawings, process knowledge, electrical work and access to connected systems.
- Acceptance: the operating behaviour and records needed before you sign off.
- Uncertainty: missing drawings, unavailable software or equipment whose condition still needs checking.
Ask each bidder to identify what needs investigation before committing to a price or schedule. Where uncertainty is material, consider a defined assessment before agreeing the implementation scope.
For a retrofit, use the same shutdown assumptions across every proposal. Our guide to planning a PLC retrofit around a shutdown window provides a useful starting point. See which plant process to automate first.
What questions should you ask each integrator?
Ask for concrete explanations and sample deliverables, with confidential information removed.
| Ask this | Look for in the answer |
|---|---|
| Who will design, program, test and commission the system? | Named project roles, availability and arrangements for absence |
| What will you inspect before finalising the design? | A site assessment tied to the project's uncertainties |
| How will you confirm what operators need? | Input from operations and maintenance, followed by documented review |
| How will you handle changes? | Written effects on scope, price, testing and schedule before work proceeds |
| What happens if commissioning cannot finish? | An agreed decision point, responsibilities and recovery plan |
| What will we receive at handover? | A specific deliverables list, ownership terms and acceptance checks |
| Who supports us afterwards? | Defined coverage, contact routes and escalation arrangements |
Have the proposed delivery lead attend the technical discussion. Give them a realistic operating scenario and ask them to explain how they would turn it into a design and test.
How should you check references?
Seek references for work with comparable constraints: an existing plant, limited shutdown access, unfamiliar equipment or an interface involving another supplier. Ask why the reference is relevant to your project.
With the reference's permission, discuss:
- Did the people proposed actually deliver the work?
- Were scope changes explained before additional work began?
- Did operators and maintenance staff participate in testing?
- What remained unresolved at handover?
- Were the software, drawings and backups usable afterwards?
- How did the integrator respond when a problem appeared?
Respect confidentiality. Do not ask for another customer's source code, credentials or sensitive plant details. If a direct reference is unavailable, request a redacted specification, test record or handover index. Treat these as evidence of the proposed working method; they do not establish customer satisfaction.
What should the functional design specification contain?
Require a functional design specification, or FDS, that describes the system behaviour your team will review and accept. Agree who writes it, who approves it and how changes are recorded.
For the equipment in scope, ask it to cover operating modes, sequences, permissions, alarms, interlocks, setpoints and interfaces. Include abnormal conditions: a missing signal, failed device, lost connection, interrupted sequence and restart after power returns.
Make vague phrases testable. Replace “automatic restart provided” with the agreed conditions for restart, operator actions, equipment checks and situations where restart must remain blocked.
Have operations and maintenance review the document before programming proceeds. Where safety-related design is involved, require a qualified assessor to define or review the relevant requirements and validation approach.
Our guide to what a functional design specification should contain can help you structure that review.
How should the integrator prove the system works?
Ask for the testing plan with the proposal. Agree which checks happen before delivery, which require installed equipment and who witnesses acceptance.
For factory acceptance testing, establish what will be simulated and what cannot be proven away from the plant. For site acceptance testing, define the checks needed on the installed system and the conditions required to perform them.
Illustrative example: a transfer pump should stop when the receiving vessel reaches its agreed high-level condition. Ask the integrator to propose checks for that stop, a missing level signal, interruption during transfer and the permitted restart sequence. Record expected behaviour before testing.
Require a test record with expected results, observed results, witnesses, defects and retest evidence. Agree how an unsuccessful test affects acceptance. An outstanding defect should have an owner and a resolution condition; it should not disappear behind a general “commissioning complete” statement.
Review the commissioning recovery plan separately. Identify when to stop work, who makes that decision and what must be checked before returning equipment to service.
What documentation and access should you receive?
Put the handover list in the contract and check it before final acceptance. For the agreed scope, consider:
- Editable controller and operator-interface projects, with required software versions identified.
- Current electrical drawings, equipment lists and input/output lists.
- The approved FDS, interface descriptions and configuration records.
- Completed tests, resolved defects and any explicitly accepted outstanding items.
- Backups, restoration instructions and evidence of the agreed restoration check.
- Operating instructions, maintenance guidance and training records.
- Licence ownership, renewal responsibilities and secure transfer of necessary access.
Ask your maintenance team to review the package. Have them locate the current backup and explain the restoration procedure.
Agree remote access separately, including approval, permitted users, logging and revocation.
What support should you agree after handover?
Separate defect correction from ongoing support and future changes. Ask what each arrangement includes, when coverage begins and how long it lasts.
Define support hours, the first contact, escalation routes and the information your team should provide. Distinguish an acknowledgement or response commitment from a repair commitment. Ask how on-site attendance, spare parts and third-party dependencies will be handled.
Walk through an out-of-hours breakdown scenario. Establish who investigates first, what access they need and what happens if the assigned engineer is unavailable.
What common mistakes and red flags should you watch for?
Avoid selecting on headline price before reconciling exclusions. Use the same comparison sheet for design, hardware, installation, testing, training, documentation and support.
Investigate proposals that:
- Promise a firm outcome while leaving critical site conditions unexamined.
- Describe testing without expected results or acceptance responsibilities.
- Leave software ownership, licences or access unclear.
- Treat drawings and backups as optional handover extras.
- Offer support without stating coverage or exclusions.
- Describe safety-related changes without qualified assessment.
Treat these as questions to resolve before appointment, not automatic proof of poor work. A small, bounded change may need a shorter specification and test plan. Keep the documents proportionate while retaining clear behaviour, acceptance and recovery requirements.
What else should plant teams ask?
Must the integrator have worked in our exact industry?
Assess the knowledge your project requires. Ask them to explain comparable equipment, process constraints and operating risks, and identify where specialist input is needed. Do not accept a broad experience claim without relevant evidence.
Should we appoint the lowest bidder?
Compare complete scope and responsibilities first. Ask each bidder to price or explain gaps before deciding. Choose against your agreed criteria, including delivery capability and the support your plant needs.
Who should approve the final selection?
Include the people accountable for production, maintenance, project delivery and relevant technical risks. Resolve conflicting expectations before appointment, then carry those decisions into the specification and acceptance plan.
Preparing a plant project? Explore our automation services, or contact us to discuss the scope, site constraints and handover requirements.