Understand legacy PLC code before you troubleshoot, modify or migrate it.
AO PLC Intelligence turns an uploaded PLC project into structured engineering evidence: project identification, code inventory, call/write activity, multiple-writer risks, investigation points and analysis coverage. It is designed to help an engineer understand an unfamiliar project faster — not to replace live-machine checks.
Snapshot: immediate automated analysis when the project format is supported. Paid audits are manually scoped and confirmed before engineering work starts.
From rapid code triage to modernisation discovery
Use the free Snapshot to establish what is in the project. Escalate only when you need engineer-led interpretation, a formal audit or migration planning.
PLC Intelligence Snapshot
Immediate structured overview for supported project formats.
- Project and controller identification
- Blocks, networks, calls and writes
- Multiple-writer and investigation counts
- Coverage, supported and unsupported areas
- Evidence confidence and engine version
Small PLC Audit
Focused engineering review of a smaller project or defined problem area.
- Snapshot evidence reviewed by an engineer
- Priority logic and risk investigation
- Defined scope agreed before work begins
- Written engineering outcome
Full Engineering Audit
Deeper review for larger or higher-risk PLC applications.
- Broader code and dependency review
- Structured findings and evidence trail
- Engineering assumptions identified
- Scope and deliverables confirmed manually
Legacy Modernisation Discovery
Front-end discovery before a legacy controls migration is committed.
- Legacy code and architecture understanding
- Migration unknowns and dependencies
- Risk and evidence register
- Modernisation scope developed with engineering review
Engineering metrics, not AI theatre
Code structure & activity
Controller and project identity, blocks, networks, calls, writes, multiple writers and investigation counts. The result model also records what the engine could and could not analyse.
Evidence confidence
Findings carry VERIFIED INFERRED or UNKNOWN evidence status so assumptions are separated from facts extracted from the project.
Private upload architecture
PLC source projects are treated as confidential engineering files. The browser uploads directly to private object storage using a short-lived permission scoped to one opaque pathname. The Automation Outlet application does not proxy the PLC project through a normal serverless request body and does not expose a permanent private object URL.
Uploaded projects are retained only for the configured analysis/retention period and can be deleted from the customer audit view. A local Windows analysis option is planned for organisations that cannot upload PLC source code.
Code evidence is not live-machine proof
PLC Intelligence analyses the supplied project. It cannot prove current I/O state, field wiring, mechanical condition, online values, safety validation, machine timing or whether the uploaded project exactly matches the controller currently running on site.
Run the free PLC Intelligence Snapshot
Upload a supported PLC project and create an audit job. If the current worker is connected, analysis begins automatically; otherwise the job remains queued safely until the analysis service processes it.
Upload PLC project