The system your operators run the plant with.

We turn plant documents into a working control system: the hierarchy from units down to individual devices, process mimics carrying P&ID symbols, alarm management, historian and shift reporting. The result is an application a shift operator learns in a day and uses for years.

• Survey of P&IDs, signal lists and electrical drawings, with an object census and the contradictions between documents brought out early
• Navigable plant hierarchy, with state propagating up to the top-level node
• Mimics with ISA-5.1 symbols: shape says the device type, colour says its state
• Per-device faceplates with commands, interlocks and the reason a device is held
• ISA-18.2 alarms: redundant priority cues, full life cycle, shelving and suppression logged
• Next-generation historian, trends with limits and measurement cursors
• Shift and production reports, exportable in the formats already in use

Water networks, district heating and generation fleets have a different problem from a single factory: many small sites, links that drop, hardware from vendors accumulated over the years. The control centre has to absorb all of that without the operator needing to know what brand sits behind each point.

• Telemetry hardware from different vendors brought under one data model
• Link loss handled as distinct from a process anomaly
• Network balances and district metered areas, with leak detection
• On-call management: who gets called, for which alarm, with what escalation
• Web and mobile access for on-call staff

Supervision knows the state of the plant; the ERP knows the orders; the laboratory knows the analyses; maintenance knows the interventions. The interfaces between these worlds are where projects stall, because usually nobody owns them. We treat them as a delivery in their own right, with an explicit and versioned data contract.

• Documented, versioned and testable REST and MQTT interfaces
• Production orders, progress declarations, actuals
• Laboratory results tied to batch and time window
• Maintenance orders raised from field state
• Data contract agreed before development, not inferred afterwards

Documentation is written in Markdown alongside the code, generated automatically and published to a portal. The same pages feed the help button inside the mimic: an operator asking for help on a screen reads exactly what is on the portal, in the language they are using. Updating a page updates the control-room help in the same instant.

• Operator and administrator manuals generated from the project
• Context help inside the HMI, bound to the active screen
• Every project language from a single catalogue
• Version register and conflict reporting between revisions

The automatic check binding a panel to its documentation page is defined as a project rule.

Most work does not start from a blank sheet: it starts from a system that has been running for ten years, grown in layers, often without the sources for everything it contains. Before rewriting, we take stock: what the system does today, which functions are genuinely in use, what would be lost. Then it migrates in stages, with the plant running.

• Functional census of the existing system before any rewrite
• Migration between successive platform versions
• Consolidation of applications born identical and drifted apart
• Historical archives preserved in full
• Reversible steps: the system stays operable at every stage

Not everyone who needs plant data sits at a control room workstation. The production manager, the maintenance technician in the field, the board: each needs a different view, opening in a browser with nothing to install. We build these as real web applications, not as supervisory screens awkwardly retrofitted.

• Web SCADA applications reachable from a browser, on desktop, tablet and phone
• Summary dashboards for management, production and maintenance, fed from the same archive as the supervisory system
• Built on the platform’s native web framework and, where a bespoke view is needed, in HTML5 and TypeScript
• Authentication, roles and action logging identical to the control room application
• Real-time updates over secure WebSocket, not polling on a timer

Not everyone is looking for a supplier to do the work for them. Many already have a capable team and want somebody who comes in where depth is needed: the architecture of a distributed system, a development standard that has to hold across dozens of contracts, a component the platform does not offer. In those cases we work alongside your team rather than in its place. That holds for plant owners, for machine builders and for integrators alike: what changes is the product the standard is cut around, not the way of working.

• Review of an existing project: structure, conventions, data model, performance, and what is being rebuilt from scratch on every contract
• Definition of a development standard cut to fit your product, reusable contract after contract
• Standards for machine builders and integrators: the same supervisory application repeated on every delivery, changing only what genuinely changes
• Design of distributed and redundant architectures, with the sizing verified
• Joint development of components and libraries that remain your property
• Code review and training for your developers
• Ongoing support on agreed days, including new platform versions