// the controlled workflow

Control drawings to a
controlled data pack.

A four-step controlled workflow from agreed drawings and naming rules to an engineer-approved, vendor-specific data pack — with every record linked back to its source evidence.

[01]workflow

Agreed drawings to an approved pack

  1. 01

    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.

  2. 02

    Generate the draft

    Extract draft PLC tags, descriptions, mappings and permitted alarm data with source references.

    For each in-scope page, the system produces draft records linked back to the drawing evidence. It does not invent missing information or complete incomplete sequences.

  3. 03

    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.

  4. 04

    Export controlled data

    Produce the agreed vendor-specific data pack for the tested downstream workflow.

    Only approved records are included. The output is a controlled draft data pack, not a deployed or final engineering deliverable.

[02]outputs

What the data pack contains

Tag Data Pack

Candidate PLC tags, descriptions, naming-rule results, source references, exceptions and agreed vendor-specific export.

Documentation Pack

FAT, SAT, or commissioning documentation generated from source-referenced project data, when validated for the customer workflow.

Code Block Pack

Custom STL/LDR/FBD/other code blocks built on extracted tags — alarms/interlocks/general, engineer-reviewed, never autonomous safety or process-alarm design.

[03]worked example

Schematic to approved record

A synthetic run through the workflow — from a fictional schematic source to a draft record, exception queue and approved export.

fig.01 · schematic source page
Drawing 04 — Digital input cardPage 04
Digital input card schematic with field rungs and extracted source evidence highlightedLIFT STATION 01 — DIGITAL INPUTS (SYNTHETIC)24V+BMX DDI 1602DI 16× 24 V DCPB-101PUMP 1 STARTW101I:0/0LS-100HIGH LEVEL SWITCHW102I:0/1PS-102LOW SUCTION PRESSW103I:0/2M-101STARTER RUN AUXW104I:0/3TS-110HIGH TEMP SWITCHW105I:0/4SPARESPARE INPUTW106I:0/5Source evidence — extracted row
Tag: LS-100Address: I:0/1Wire: W102
fig.02 · draft tag record
Tag
P1_LS100
Description
PUMP 1 HIGH LEVEL SWITCH
Signal type
Digital input
HMI label
PMP1 HI LVL
Suggested alarm
LAH
Source
Drawing 04 / ch. I:0/1
Confidence
High
Status
Draft
fig.03 · exception / review queue
Rule conflictSource: P1_LIT111

Instrument tag ending in 111 conflicts with the customer rule to reserve 110–119 for flow loops. Engineer review required.

Engineer review required
Missing labelSource: O:0/17

Address token found without a corresponding field descriptor. Requires confirmation before export.

Engineer review required
fig.04 · approved export
TagDescriptionTypeAddressStatus
P1_FIT100PUMP 1 SUCTION FLOW TRANSMITTERAnalog input%MW100Approved
P1_P101PUMP 1 STARTER RUN COMMANDDigital output%M0Approved
P1_LS100PUMP 1 HIGH LEVEL SWITCHDigital input%M1Approved
Export target: vendor-specific pack (XBD · XML)Version: 2026-08-27-draft-1Records approved: 3 of 4

Illustrative synthetic example — not a customer drawing.

PLC Automator does not deploy PLC code, connect to live OT systems or make unreviewed safety/process decisions.

Discuss a controlled pilotSee pricing