How it works
From agreed drawings and rules to a controlled, engineer-reviewed data pack.
Define the job
Agree the drawing package, project rules, naming conventions and required export. The scope is fixed before any files are processed.
You choose which drawing types are in scope, the PLC and HMI/SCADA naming rules to apply, and the export format the downstream workflow expects.
Generate candidates
Extract candidate PLC tags, descriptions, mappings and permitted alarm data with source references.
For each in-scope page, the system produces candidate records linked back to the drawing evidence. It does not invent missing information or complete incomplete sequences.
Review exceptions
Engineers inspect uncertain, incomplete or non-conforming records before approval.
Ambiguous addresses, rule conflicts and missing labels are surfaced as review items. Each exception keeps a reference to the source evidence so engineers can decide quickly.
Export controlled data
Produce the agreed CSV/Excel data pack for the tested downstream workflow.
Only approved records are included. The output is a controlled candidate data pack, not a deployed or final engineering deliverable.
Product scope
Tag Data Pack
Candidate PLC tags, descriptions, naming-rule results, source references, exceptions and agreed CSV/Excel export.
Documentation inputs
Agreed data for HMI/SCADA mapping, registers and documentation seed files, when validated for the customer workflow.
Alarm Library mapping
Candidate use of the customer’s supplied and approved alarm templates—not autonomous safety or process-alarm design.
PLC Automator does not deploy PLC code, connect to live OT systems or make unreviewed safety/process decisions.