Legacy program in. Verified documentation out.
Send one export from a running PLC-5, SLC-500, MicroLogix or ControlLogix program. Get back a functional specification, a tag dictionary, a full cross-reference, an engineering review findings register and a factory acceptance test plan — analysed by software, verified by a controls engineer. Fixed price, fixed deadline, per program.
No site access. No changes to the controller. NDA on request.
One package, five documents, produced from a single export of the running program.
What the program does, routine by routine, organised by function. Interlocks, permissives and anything safety-relevant called out first. Every statement the analysis could not prove from the export alone is marked VERIFY and collected for review.
Every tag with its type, description, scope, and read and write counts, so nothing is migrated blind.
Where every signal is produced and consumed, across routines, including add-on instructions and indirect addressing.
Disabled logic, uncalled routines, suspect and unused tags, pending online edits, calls into missing routines — every item that needs a human ruling before migration.
Every boolean output the program writes, the conditions that drive it, and drafted test steps with setup, action and expected result.
A bound PDF for approval and sign-off, plus Markdown sources your team can edit and keep in version control.
You send the program export: a Studio 5000 or RSLogix 5000 .L5X, or an RSLogix 500 ASCII export with its symbol file. Nothing connects to your controller.
Deterministic analysis recovers the structure — every tag, reference, call, and every piece of dead or disabled logic. An AI documentation pass recovers the intent, with the full program as context so cross-routine behaviour is traced, not guessed.
A controls engineer checks the narrative against the logic. Anything unproven stays marked VERIFY. You receive the package with a one-page summary of what needs your ruling.
The free structural analysis comes first: you see the scope — programs, routines, rungs, tags, findings — before you spend anything.
Generated from publicly available programs. They contain no client data.
You have the export and a deadline, and the plant has no documentation. The package gives you a defensible scope and a FAT plan before you price the conversion.
The engineer who wrote the program has gone. Recover what it actually does before anyone decides how to replace it.
A documented estate of legacy controllers, one program at a time, with the review findings your insurer or auditor will ask about.
Email an export and we reply with the scope and a fixed price. Conversion packages — PLC-5 or SLC-500 to ControlLogix, with restructured code and FAT support — are quoted per system.