Brownfield and greenfield code development
PLC and SCADA software for new plants and old ones, written the way you want it.
Sound familiar?
Control software outlives the people who write it. On an existing plant it is often patched by several hands, lightly documented and risky to touch. On a new one, every supplier brings its own style, and you inherit the mix. Either way, the code has to run your process safely and stay supportable for decades.
How it works
We write to the standard you choose: yours, ours, or one we build with you. Existing code is analysed and documented before anything changes. New code is built from your specification. Both are version-controlled from the first line, tested against a simulated plant, and handed over with the documents and support your team needs.
What we do
Whether we extend a running plant or start from a blank page, you choose the standard the code is written to and how it is produced.
We write to your company coding standard, naming rules and block library, so the result looks like your own engineers wrote it. Your library blocks are reused, not copied and altered.
Industries: Aerospace, Airports, Automotive, Chemicals, Clean Water, Nuclear, Oil and Gas, Pharmaceutical, Power, Rail, Wastewater
Where you have no standard, we use ours: a consistent structure of equipment modules, state-based sequences, alarms and interlocks, laid out the same way on every project.
Industries: Agriculture, Building Services, Heat Treatment, Metals, Mining and Quarrying
We create a standard with you: structure, naming, block library, templates and coding rules, documented so every future supplier and engineer follows it too.
Industries: Building Services
Give us one well-written example of a motor, valve or sequence. We generate the rest of the project in the same form, so code is consistent and quicker to review.
Industries: Automotive, Baggage Handling, Food and Beverage, Warehousing
We analyse your existing code first: structure, sequences, I/O, alarms and interlocks. Missing documents are recovered from it, and changes are made under control.
Industries: Airports, Baggage Handling, Clean Water, Heat Treatment, Metals, Mining and Quarrying, Nuclear, Oil and Gas, Power, Rail, Wastewater
New systems start from an agreed functional specification. The software is built from it in a clear structure, so every function traces back to a requirement.
Industries: Aerospace, Agriculture, Chemicals, Food and Beverage, Pharmaceutical, Warehousing
An extension to a running line usually keeps your blocks and the structure already there. A new line beside it can be generated from your examples, so the two look and behave alike. We agree the mix at specification stage and record it in the software design specification.
Industries
An ISO 9001 certified quality system, designing to the standards your sector demands, plus any you specify.
Our promise
How we deliver
Development is one part of the job. Testing, commissioning, documentation and support come with it as standard.
Requirements, standards and risks agreed with you; on existing plant, the code analysed and documented first.
The coding standard, block library and templates fixed before development starts.
Code written or generated to that standard, version-controlled and peer reviewed as it grows.
Sequences, interlocks, alarms and faults tested against a simulated plant, then factory acceptance testing.
Installation, commissioning and site acceptance testing, planned around your operation.
Documentation, training and long-term support, with 24/7 cover under a support agreement.
In full
Most projects mix the two: new equipment on an existing plant, or a new line that must match the old one. The approach changes with the starting point; the standard of evidence does not.
The software is running and production depends on it. We change it without disturbing what works.
Nothing exists yet. We get the structure right from the start, so the system stays supportable for its whole life.
| Area | What we develop | How it is proven |
|---|---|---|
| PLC software | IEC 61131-3 code in ladder, function block diagram and structured text; statement list where the existing program uses it | Compiled clean, reviewed, sequence and interlock tests |
| Safety programs | Safety functions on safety PLCs and relays, written to your safety requirements specification | Safety requirements tests, independently reviewed |
| HMI and SCADA | Screens, alarms, trends, reports and operator commands, consistent with the PLC structure | Tested against the PLC running in simulation |
| Drives and devices | Drive, instrument, vision and robot interfaces, with parameters archived with the project | Interface tests and parameter records |
| Communications and data | PROFINET, EtherNet/IP, Modbus and OPC UA links, historians, reports and MES or ERP interfaces | Point-by-point communications tests |
| Version control | Every change committed with its reason, reviewed and traceable from the first line to handover | Change history handed over with the source |
Maps the blocks, sequences, loops, I/O and alarms of a TIA Portal project before we change it.
Produces I/O, alarm and cause-and-effect lists and a functional description from the code.
Builds I/O mapping, state machines, alarms and loops from an equipment list.
Each change is imported and compiled automatically before an engineer reviews it.
Programs run in PLCSIM Advanced with simulated inputs and process models.
Every PLC has its own repository; every change is reviewed before merging.
FAQ
Yes. If you have a coding standard or block library, we write to it. If you do not, we offer ours or build one with you.
Yes. We analyse it first and recover the I/O list, alarm list, cause-and-effect and a functional description.
You do. You receive the source, its history and the documents, so you can support it yourself or with any supplier.
Contact
Standards-led, fully documented control systems that you own and can support.
