Problem territory · Controls visibility
Controls visibility without handover risk.
PLC, SCADA, BMS, and instrumentation engineered to be operated, defended, and inherited. The operator and the auditor see the same trusted data. The partner who signed the scope is the engineer who stands on-site at commissioning.
- Automation practice formalised
- 2022
- Regulated standard
- GAMP 5
- Operating offices
- 6
- Handover posture
- Auditable
Representative delivery posture. Scope, validation depth, and retained coverage are set per mandate in the written brief.
Mandate fit
Control narrative before code.
Automation is treated as operating infrastructure. The logic, alarm philosophy, roles, and records are fixed before the cabinet is touched.
- 01
Existing state read
Live logic, operator habits, and undocumented workarounds are captured first.
- 02
Role-controlled design
Alarm, access, historian, and validation requirements are written down.
- 03
Inherited cleanly
The next operator receives records they can defend during a shift or audit.
Delivered against
- GAMP 5
- IEC 61131
- IEC 62443
- ISA-95
- OPC UA
Capabilities
Six automation programmes under one partner.
The control narrative is written before the code. The role matrix is signed before commissioning. The handover is the documentation a regulator would accept.
01
Plant control + SCADA
PLC, HMI, and SCADA systems for water, energy, and process plant. Designed so the operator and the auditor see the same trusted data.
02
Instrumentation + metering
Flow, level, pressure, quality, and energy metering specified to the measurement the business actually needs to act on.
03
Building + estate automation
BMS, access control, and lighting integrated behind a single operator view. No rival apps, no orphan dashboards.
04
Regulated system integration
GAMP-aligned delivery for pharma and life-sciences clients. Validation packs, audit trails, and change control held by the partner who wrote them.
05
Legacy rescue + re-platforming
Unsupported controllers, orphaned HMIs, and undocumented logic re-engineered into a maintainable stack — without taking the line down.
06
Data + reporting pipelines
Historian, KPI reporting, and regulator-facing exports. Engineered to the same rigour as the plant itself, not bolted on afterwards.
A well-run plant is quiet. The control system is the reason — written down, signed off, and inherited by whoever operates next.
Evidence
Written before it is wired.
Four declarations, drawn from the firm’s own record. The standard is named, the practice date is stated, the handover posture is disclosed in writing before any controller is specified.
Record of practice
i — iv · as at 2026
- IStandard
GAMP 5
Validation-grade delivery for pharmaceutical and regulated clients
- IIFormalised
2022
Year the automation practice was formalised as a dedicated line within the firm (ASE itself was founded in 2003).
- IIIHandover
Auditable
Every system is handed over with the documentation a regulator would accept
- IVPosture
Retained
Stewardship is expected, not optional — no throw-over-the-fence handovers
Signed by the senior engineer of record at the close of every engagement. Kept on file, reissued on request.
Delivery
Audit. Philosophy. Build. Steward.
Four stages, one partner across all of them. No control system leaves us without the narrative, matrix, and records the next engineer will need.
Engagement cadence
i — iv · single partner
- IListen
Process audit
We walk the plant, read the existing logic, and document what is actually running before proposing any replacement.
1 – 2 weeks
- IIWrite
Control philosophy
Written control narrative, alarm philosophy, and role matrix signed off by the plant owner before code is written.
2 – 3 weeks
- IIIDeliver
Build + commission
FAT, SAT, validation, and phased cutover. The partner who signed the scope stands on-site at commissioning.
8 – 16 weeks
- IVHold
Stewardship
Retained support, change control, and quarterly reviews. The engineers who wrote the system are the engineers you call.
Retained
One partner signs across all four stages. No subcontracted handovers, no throw-over-the-fence handovers.
Next step
A partner-level controls review.
Thirty minutes with a senior partner. You leave with a written summary of the current system, the realistic path forward, and a direct line back to the partner.
- Current control stack — PLC, SCADA, BMS, historian.
- Known gaps, audit findings, or validation risks.
- Operating-team expectations and escalation rules.
- Written follow-up — or a clear decline, quickly.
Discretion on live systems is default. Nothing is published or referenced without written consent.