Process
Five stages. Five exits.
An automation project goes wrong in the gap between what was described and what was specified. So the specification comes first, the tests are written before the code, and every stage ends with a document you own and a point where you can walk away.
- Assess
- 1–3 weeks
- Design
- 2–6 weeks
- Implement
- 4–16 weeks
- Commission
- Your shutdown window
Assess
1–3 weeks
We walk the plant, read the drawings and watch a shift before proposing anything.
You end up holding
An assessment report with a costed shortlist and the option to stop.
- Site walk-down with production and maintenance, not just management
- Review of P&IDs, electrical drawings, existing code and alarm history
- Baseline measurement of the numbers the project will be judged on
- A written statement of what is worth automating and what is not
Design
2–6 weeks
The functional design specification is the contract. Nothing gets built ahead of it.
You end up holding
A signed FDS and test plan you own, usable by any integrator.
- Functional design specification, control philosophy and interlock matrix
- I/O and tag schedules, network architecture and segmentation plan
- Acceptance tests written now, so success is defined before the build
- Hardware selection with lead times and spares availability stated
Implement
4–16 weeks
Code, panels and screens are built and tested off-plant while you keep producing.
You end up holding
A FAT-passed system and a test record showing what was proved.
- Version-controlled PLC, HMI and gateway development
- Simulation and factory acceptance testing against the agreed test plan
- Panel build, wiring and pre-configuration of drives and instruments
- Weekly written progress against the test plan — no status theatre
Commission
Shutdown window
Installation is planned to your window, with a tested rollback at every stage.
You end up holding
A SAT sign-off, as-built documentation and trained operators.
- Loop checks and point-to-point verification before energising
- Staged cutover with a rehearsed way back to the previous system
- Site acceptance testing witnessed by your team
- Operator and maintenance training on the running plant
Support
Ongoing, by agreement
A run-in period, then whatever level of cover you actually need — including none.
You end up holding
Full handover. You can continue with us, your own team, or anyone else.
- Defined run-in period with named contacts and response times
- Source code, drawings and credentials handed over in full
- Optional retainer for changes, upgrades and remote diagnosis
- Annual obsolescence review if you want one
Five commitments that go in the contract
These are not a tone of voice. Each one is written into the engagement, and each is a thing you can hold us to.
You can stop at every stage
Each stage ends with a document you own. If you stop after the assessment, you keep a costed shortlist any integrator can quote against.
The design is the contract
Implementation is fixed against the signed functional design specification. Variations are priced in writing before they are done, not discovered on the invoice.
Tests are written first
Acceptance tests are agreed during design. That is what makes them a gate rather than a formality at the end.
Rollback is part of the plan
Every cutover stage has a rehearsed way back to the previous system, with a written go/no-go point in the shutdown window.
Handover is complete
Source code, HMI projects, tag lists, drawings and credentials, with no licence condition that forces you back to us.
Next step
Book the assessment
One to three weeks, a fixed fee, and a report with a costed shortlist. If the shortlist says do nothing, that is the report you get.