PLC application logic, ISA-101 operator interfaces, instrumentation and control loops — designed, programmed and commissioned by the same engineers who will support them afterwards.
A control system fails at the seams — between the instrument and the controller, between the controller and the screen, between the screen and the person reading it. We take responsibility for all of them.
Application logic on MAC36 Pro, MAC36, AAC20 and other controllers — sequences, interlocks, alarm handling and safe behaviour on failure.
Operator interfaces designed to ISA-101 — built for a control room, not for a marketing screenshot. Grey by default, colour only where it means something.
Choosing the measuring point matters more than choosing the sensor. We specify both, then verify the signal is telling the truth.
A loop that oscillates costs energy, wears actuators and eventually gets switched to manual — at which point the automation has failed. We tune for stability under real disturbances, not for a textbook step response.
Nobody rips out a working controller because a protocol is inconvenient. We speak the field protocols and bridge the control layer to whatever runs above it.
Control data rarely stays in the control room. We push it where the business needs it — reporting, ERP, maintenance systems and asset registers such as our own Proton Passport.
The project is not finished when the code compiles. It is finished when the plant runs, the operators trust the screen, and someone can maintain it without calling the author at midnight.
We commission what we build, document it properly, and stay reachable for remote support afterwards.
Send us the scope — controllers, points, protocols, whatever you have. We will come back with a straight answer about effort and approach.