New control system
Define control narratives, I/O, sequences, alarms, operator interfaces, communications, and test criteria for a new process.
Industrial automation & process control
Plan new controls, modernize an existing system, troubleshoot faults, or connect water-treatment equipment to the wider plant architecture.
The initial discussion identifies missing documentation and determines whether remote preparation, a site review, or a larger modernization scope is appropriate.

Project fit
The first step is to understand whether the core need is new implementation, migration, fault diagnosis, or integration.
Define control narratives, I/O, sequences, alarms, operator interfaces, communications, and test criteria for a new process.
Review existing hardware, software access, backups, compatibility, spare capacity, shutdown windows, and a safe migration path.
Document symptoms, fault history, operating conditions, recent changes, and the boundary between controls and process equipment.
Define required data points, protocols, ownership, cybersecurity constraints, testing responsibilities, and handoff to other systems.
Controls scope
A reliable scope connects the process sequence, field devices, operator decisions, plant communications, testing, and documentation.
Sequences, interlocks, permissives, modes, alarms, equipment control, and process-specific logic.
Status, commands, setpoints, alarm context, trends, and screens organized around real operating tasks.
Instrumentation, remote I/O, drives, packaged equipment, supported protocols, and defined integration boundaries.
Tags, trends, events, historian requirements, reports, and escalation paths based on the plant architecture.
Test plans, simulations where appropriate, site acceptance, fallback steps, commissioning support, and issue tracking.
Prepare the first review
Send what is available. Gaps can be logged and resolved before implementation commitments are made.
Controls project discussion
Share the equipment, available documentation, known issues, integration requirements, and commissioning constraints. A specialist will help define the next review step.
Delivery approach
Exact activities depend on platform access, site conditions, safety requirements, and the approved project boundary.
Review the process, current controls, available documentation, site constraints, and the business reason for the change.
Agree on scope boundaries, control philosophy, interfaces, deliverables, test criteria, responsibilities, and change risks.
Develop against the approved scope, document assumptions, and complete the agreed bench or offline testing before site work.
Execute the site plan, record issues, confirm acceptance criteria, and provide the documentation and operator handover included in scope.
Connect the controls scope to the wider commercial water project.
Common questions
The information needed to evaluate upgrades, integration, troubleshooting, and commissioning work.