A control system integrator is the party that turns a P&ID and an I/O list into a running, tested, documented control system. Not the vendor who sells the controller, and not the EPC who owns the plant scope — the one in between who has to make both sides agree.
The problem this scope actually solves
Control system scope fails in predictable ways, and almost never because the controller was the wrong brand.
| Failure mode | What it costs |
|---|---|
| I/O list and cabinet design drift apart | Spare capacity disappears, cabinets get re-cut on site |
| Configuration done by someone who never sees the plant | Graphics that operators do not use, alarms nobody trusts |
| FAT treated as a demo instead of a test | Every defect found at site instead of in the workshop, at 10× the cost |
| No traceability from requirement to tag | Acceptance turns into an argument at the worst possible time |
What we deliver
| Phase | Work |
|---|---|
| Requirement review | I/O schedule reconciliation, controller sizing, network topology, spare capacity policy |
| Hardware design | Cabinet general arrangement, wiring and termination drawings, power and earthing, heat load |
| Software design | Controller configuration, interlock and sequence logic, operator graphics, alarm rationalisation, historian tag build |
| Integration | Third-party packages over Modbus, Profibus, Profinet, OPC UA, Ethernet/IP; MES and historian interfaces |
| Testing | Point-to-point test, internal pre-FAT, witnessed FAT, SAT, loop check |
| Documentation | As-built drawings, configuration backup, test records, O&M pack |
Platform coverage
| Vendor | Systems we configure |
|---|---|
| Yokogawa | CENTUM VP, CENTUM CS 3000, STARDOM, ProSafe-RS (SIS), FAST/TOOLS, CI Server |
| Siemens | SIMATIC PCS 7, WinCC, S7-300, S7-1200 / S7-1500 with TIA Portal |
| Rockwell Automation | ControlLogix, CompactLogix, Studio 5000, FactoryTalk View SE |
Roughly speaking: if the plant already runs one of these, we can extend it rather than argue for a replacement.
Safety systems
SIS work is kept separate from BPCS work on purpose — separate configuration, separate test protocol, separate sign-off. We configure ProSafe-RS to the SIL requirements stated in the client’s SRS. We do not write the SRS or set the SIL targets; that is the process safety engineer’s call, and a contractor who offers to do both should worry you.
How we prove it worked
| Deliverable | Evidence it produces |
|---|---|
| Point-to-point test record | Every terminal verified against the loop drawing, signed |
| Witnessed FAT report | Client-signed protocol with pass/fail per test case and a punch list |
| Loop check sheets | Field device to graphic, one line per loop |
| Configuration backup | Restorable project archive handed over at SAT |
Scope boundary
| We do | We do not |
|---|---|
| Control system hardware and software design | Process design, P&ID development, SIL determination |
| Cabinet build and factory testing | Field instrument supply, installation and calibration |
| Commissioning and startup support | Civil, structural, cable tray and field cabling |
Start a scope review
Send the platform, the I/O count and the required on-site date. Contact us — you will get an engineer, not a sales script.
Start a scope review
Send the platform, the I/O count and the required on-site date. You will get an engineer, not a sales script.