Machines live in the field for decades; the engineers who wrote their control software don’t stay that long. An evidence-backed model turns a legacy product line back into something a support team can stand on.
An illustrative scenario — a composite of the situations we build for, not a customer reference.
An equipment manufacturer still supports machines shipped fifteen years ago. The control software — IEC 61131 logic with embedded C underneath — was written by developers who have long since moved on. Every escalation that reaches third-line support ends the same way: someone has to go read the code.
Now component obsolescence forces a redesign, and the requirement is exact: the replacement must behave like the original — including the behaviour nobody remembers deciding.
Each generation of the product line gets its own evidence-backed model — what this firmware, on this hardware, actually does.
Structured text and embedded C are modelled together, with the interfaces to drives, safety hardware and the HMI made explicit.
The model states what the replacement must do — as proven behaviour with citations, not as folklore from the support queue.
Each service release is re-checked against the model, so the record follows the product instead of trailing it.
From a synthetic machine & equipment oems system — we never show customer data.
Tell us what you run — an Orientation assessment takes days, not months.