Skip to content
Product data & engineeringWater & EnvironmentMachinery & Plant EngineeringConveying & IntralogisticsEnergy & Utilities+3

Match schematic, IO list and PLC program

demi matches addresses and signals across schematic, IO list and PLC program and finds every mismatch before commissioning.

Today

Schematic, IO list and PLC program are made by different people and drift further apart with every change. A sensor is moved to another terminal but the program still reads the old address; an input is wired and never read; a signal has one name in the drawing and another in the code. At commissioning or the next retrofit, technicians then spend days tracing signals on the machine.

An example

Arnstein is retrofitting the leak test station for its AH aluminum housings, which has been changed many times since commissioning nine years ago. Before the retrofit week the agent matches 52 schematic pages, the IO list with 386 signals and the symbol table of the PLC program. It finds 19 inputs that are wired but never read in the program, two addresses assigned twice, a proximity switch called “part present” in the drawing and “gripper open” in the program, and a pressure sensor measuring 0–10 bar according to the IO list but scaled to 0–16 bar in the program. Maintenance settles these points at the cabinet before the line is shut down.
Fictional company, typical workflow.

Your data, wherever it lives

Today schematics sit in the electrical CAD system or as PDFs in the machine file, the IO list in a spreadsheet and the PLC program exports in project folders on the network drive, often in several versions. demi reads and understands these documents and links every signal by tag and address across all three sources, with your access rights. The AI then matches a machine in minutes instead of days, and your technicians decide what gets corrected.

Where the data lives today

  • CAD & drawings
  • PDFs
  • Folders & drives
  • Office files
  • PLM
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: electrical CAD, IO lists as spreadsheets, PLC program exports on the network drive and machine files in the PLM. demi replaces nothing and links every signal by device tag and address: page and terminal in the schematic, row in the IO list, variable and references in the program.

  2. 2 · PermitPermission Layer

    Drawings and programs are visible to electrical engineering, PLC programming, commissioning and maintenance of the machine concerned. demi changes neither drawing nor program; changes are made by the responsible electrical engineer or programmer, and mismatches on safety-related signals are assessed by the person responsible for functional safety. Every assessment is recorded.

  3. 3 · ActIntelligence Layer

    The matching itself follows fixed rules: address against address, tag against tag, measuring range against scaling. The agent reads the drawings, PDFs included, and the program exports and explains each mismatch in words, for example that a normally closed contact is evaluated in the program as normally open. It flags unclear assignments instead of guessing.

How it runs

  1. 1

    Schematic, IO list and the PLC program export with symbol table and cross-references come together.

  2. 2

    The agent links every signal by tag and address across all three sources.

  3. 3

    It finds dead inputs, unwired variables, duplicate addresses, different names and mismatched measuring ranges.

  4. 4

    Each mismatch comes with schematic page, terminal, IO list row and program location.

  5. 5

    Electrical engineering and PLC programming settle every point and correct drawing, list or program.

What changes

  • Mismatches found at the desk, not at a stopped machine

  • Shorter commissioning and retrofits

  • Schematic, IO list and program agree again

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+173 hfreed per year

Assumptions and calculation

demi matches schematic, IO list and PLC program per machine; you settle the mismatches.

8 h → 5.6 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

6 machines × 8 h × 30% × 1.0 (manual) × 12 months = 173 h

Value per year, before demi costs

Freed per year+173 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$11,245

gained per year

173 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Where does demi get the PLC program from?

From exports of the programming environment: symbol table, cross-reference list and program sources as text or XML files, stored on the network drive or in the machine file. demi needs no access to the running controller. The agent only reads; it writes nothing to the controller.

What exactly does the agent find?

Inputs and outputs that are wired but not used in the program, and variables without wiring. Also duplicate addresses, signals with different names in drawing and program, normally closed and normally open contacts evaluated differently from how they are drawn, and analog signals with a different measuring range or scaling.

Does demi change the PLC program?

No. The agent shows each mismatch with every location; corrections are made by electrical engineering and PLC programming. It flags mismatches on safety-related signals separately, and they are assessed by the person responsible for functional safety.

Does it help with old machines without a current IO list?

Yes. If the IO list is missing or outdated, the agent rebuilds it from schematic and program and marks every place where the two disagree. So before the retrofit you have a list in which every row shows its source.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases