AI debugging platform for every machine on your line.

Edmund is an AI debugging platform that reads your PLCs, HMIs, schematics, manuals, alarms, and maintenance journals. Unifies all of your data sources into one platform with a reliable maintenance workflow.

Book a demo → Read a case study

edmundai.app/workspace/assembly-line-4

Find a servo drive and explain its activation conditions in the PLC program.

Found the servo control block FB 1343 Faulhaber MCBL. The drive is enabled when it is online, not cancelled, and a motion command (Home / Jog / Positioning) requests it.

SCL Line4_V20_Export/Devices/S7-1500_ET200MP/Motor Control/FB 1343 Faulhaber MCBL

142//Go Hall Zero
143IF #GoHallZero AND NOT #Cancel AND NOT #Stop THEN
144    IF NOT #status.enabled THEN
145        #state.enable.start := true;
146    END_IF;
147    #state.goHallZero.start := true;
148    #status.done := false;
149END_IF;

FB 1343 Faulhaber MCBL · L143 St-31 Spindling 1 RS232 communication

Where is -94B1 wired, and where do I find it in the cabinet?

-94B1 is the product-detect photocell (SICK WL12-2P430) on conveyor 3. It's wired to input %I4.3 on DI module -A4, through terminal X1:11–12 in cabinet +SK3.

=CMM+SK3 · PLC I/O · sheet 3 +SK3 · terminal plan X1 Device list · -94B1

Ask Edmund, try “where is -94B1 wired?” ⌘ K

Trusted by leading European manufacturers 13 production groups · 4 countries

You have a CMMS. You have an MES. You have Copilot.
So why do faults still take hours to fix?

€30,000–€60,000

An hour of unplanned downtime on a tier-2 automotive line.

We bet your last downtime took more hours than you would have liked.

Three things a Plant Director sees in the first quarter.

Edmund's first users are technicians on the floor. Its first KPI movers are the people running the plant.

25–30%

time saved on troubleshooting

Provably lower MTTR.

Mean time to repair gets shorter, and the difference shows in OEE. Numbers you can defend in a quarterly review without hand-waving about "improving processes."

441hrs / yr

returned to senior technicians per plant

Senior technicians don't have to be the bottleneck.

An ordinary technician picks up where a PLC specialist used to be needed.

700 €k / plant / yr

saved across the cohort

Reliability numbers that hold up in a board review.

Every fault has a documented root cause. The board review stops being "we're working on it" and starts being "this is the third Tuesday relay sticking; here's the procurement plan."

The fix is ten minutes.
The hunt is an hour.

When a line stops, the problem usually isn't the repair itself — it's diagnosing the right problem. Your data already has the answer, scattered across PLC projects, schematics, alarms, journals, and people's heads, but none of it connects. Edmund significantly shortens the diagnostic step.

MTTR · diagnosis vs repair

Without Edmund

Diagnosis ~50 min

Repair ~10 m

With Edmund

Diagnosis ~10 m

Repair ~10 m

Saved ~40 min

Diagnosis eats the budget.

Across our deployments, the part swap is rarely the bottleneck. The hour you lose is upstream, figuring out which part, why it failed, and whether it'll come back next quarter.

The answer lives in your data. The connections between it don't.

PLC projects, EPLAN drawings, alarm history, maintenance journals, and what's only in the head of the senior technician — separate systems, separate handoffs, no map between them.

Technicians want to fix, not investigate.

A traceable answer beats a confident guess. Edmund hands the technician the cause and the next step, with citations, so the only thing left to do is the wrench work.

All your plant data and signals, in one platform.

Edmund reads and connects every data source, from PLC programs to handwritten journals, into a single source of truth.

/01 PLC · vendor-agnostic

Understands PLC projects and code from every vendor on your floor.

Edmund parses TIA Portal, Allen-Bradley, and Omron projects (plus anything that compiles to IEC 61131-3) into the same searchable model. Returns blocks, line numbers, call sites, never a paraphrase. A technician can navigate code they didn't write.

More vendors coming soon:

Chat TIA Portal · SCL PLC

SCL PLC Program Block Example

Messages

Find a servo drive and explain its activation conditions in the PLC program

Searching programs · servo drive enable / activation logicProgram logic

Found the servo control block FB 1343 Faulhaber MCBL. The drive is enabled when it is online, not cancelled, and a motion command (Home / Jog / Positioning) requests it:

SCL Line4_V20_Export_20251215_232755/Devices/S7-1500_ET200MP-Station_1/Motor Control/FB 1343 Faulhaber MCBL

142//Go Hall Zero
143IF #GoHallZero AND NOT #Cancel AND NOT #Stop THEN
144    IF NOT #status.enabled THEN
145        #state.enable.start := true;
146    END_IF;
147    #state.goHallZero.start := true;
148    #status.done := false;
149END_IF;
150//Position abnullen
151IF #SetPositionNull AND #status.online THEN
152    #state.setPositionNull.start := true;
153END_IF;

Sources

0003 - Customer specific functions1

0004 - Process3

St-31 Spindling 12

Faulhaber5

RS232 communication2

FB 1343 Faulhaber MCBL S7-1500 Siemens_2020_08_03.scl

FB 1343 Faulhaber MCBL S7-1500 Siemens.scl✓ Cited

FB9001 Faulhaber MC5010 S (Murr RS232).scl

FB9002 Faulhaber CRC8.scl

calculateTargetPos.scl

/02 ePLAN · logical to physical

Turns a logical address into a physical spot.

A tag like -B34 resolves to the cabinet, the row, and the clamp position a technician can put a hand on. Closes the "where is it physically?" loop in seconds, not days.

Logical → physical Cabinet maps Wire-tracing

Supports PDF exports from:

Chat Conveyor3_Elektro.pdf · p. 217 EPLAN

Find -B34 in the cabinet

Messages

Where is -B34 wired, and where do I find it in the cabinet?

Searching schematics · Conveyor3_Elektro.pdfSchematic

-B34 is the light barrier receiver on conveyor 3. Its OSSD1 output runs on core 4 of cable -W34 to terminal -X9:4, then to input %I4.3 (A494/5.1). Terminal strip X9 is in +UH3.1.

Conveyor3_Elektro.pdf 217/ 402

EPLAN sheet 217: light barrier transmitter -B32 and receiver -B34, cable -W34, terminal strip -X9

%I4.3

Sources

Conveyor3_Elektro.pdf · page 217✓ Cited

Conveyor3_Elektro.pdf · page 231 · terminal strip X9

FB_Conv3_Control · line 48 · %I4.3

/03 SQL · live operational data

Tests the hypothesis against live data.

Pulls trends, historical measurements, and alarm logs in real time. Confirms or refutes a guess from PLC or EPLAN, surfaces patterns across shifts and lines, and returns a diagnostic conclusion with a recommended next step, not a CSV to read.

MES ERP Time-series 10+ DB connectors

Chat ZV-161 · IMM01 SQL

Suggestion · IMM01 consumption analysis

Owned by Petr

Messages

Period: week of Jan 12, 2026

Searching database

Running code

IMM01 (kWh) Over DateTime — Weekly Trend

IMM01(kWh)

Total hours per state (Jan 12–18, 2026)

OFF 63 h ON_NO_PROD 74 h PROD 31 h

/04 Documents · the most-used agent

Finds the page, the paragraph, the line.

Mechanical drawings, electrical schematics, manuals, datasheets, measurement protocols. Returns the exact citation, multilingual and visual when needed. The agent that turns up in every debugging workflow, checking the HMI, reviewing schematics, looking up a part spec, handing context to the next shift.

Drawings · schematics · PDF Manuals · datasheets Multilingual Cited every time

Supports PDF exports from:

Match SICK · WL12-2P430 PDF · p. 7

"Recommended cleaning interval for the WL12 in dust contamination class M is every 240 operating hours; failure to clean reliably degrades switching frequency below the 1 000 Hz nominal value."

SICK datasheet · rev 04/2024 Open page 7 ↗

Sources

PDFWL12-2P430 · datasheetp. 7

PDF+SK3 cabinet · sheet 217v. 3

MDMaintenance journal 2026-04-12#4729

/05 Maintenance journals · tribal knowledge

Saves the fix so the next person inherits it.

Captures what technicians know but rarely write down: the symptom, the root cause, the parameter change, the photo. Edmund parses handwritten notes and shift logs, surfaces repeat interventions, and turns one expert's hour-long debug into a repeatable solution anyone can follow.

Handwriting OCR Multilingual Photos · scans · PDFs

Maintenance Journal Line 4 · Conveyor 3 Journal

Conveyor 3 Edmund Add entry Manage

Search maintenance entries… Status Source Type

Name	Status	Creator	Last updated
Photocell stop, conveyor 3	Processed	M. Novák	04/25/2026
Light barrier lenses cleaned	Processed	T. Marek	04/12/2026
Photocell stop, conveyor 3	Processed	P. Doležal	04/08/2026
Photocell stop, conveyor 3	Processed	Night shift	04/03/2026

34 entries‹ 1 2 3 4 ›

/06 Data health · every source, one view

Shows what’s indexed, and whether every source is current.

Every project keeps a live count of indexed documents, journals, PLC programs, and connected sources, each with its status and last-sync time. A plant lead can confirm coverage at a glance and catch a source that’s gone stale before someone hits the gap mid-fault.

Coverage counts Per-source status Last-sync freshness

Project Dashboard Assembly line 4 Health

Documents547▲ 41 last 30d

Maintenance journals34▲ 2 last 30d

PLC programs4S7-1500 · TIA

Data sources3DB · files · OPC

Documents by category All active

547docs

Spare parts catalog211

Mechanical drawings128

Machine & component docs112

Schematic diagrams96

Last PLC sync · 6 days agoNewest journal · 2 days ago

/07 Robotics intelligence · ABB RAPID

Reads the robot program and its I/O, down to the channel.

ABB RAPID modules and the robot controller’s I/O, next to the PLC programs of the same line. Each signal comes with its address on the I/O module and the RAPID code that uses it. We are building it with an automotive supplier, on an end-of-line test cell.

RAPID modules I/O & signals Cross-references

More vendors coming soon:

Robots Line 4 · EOL test cell 11 ABB · IRC5

RAPID modules 68 I/O & signals 761

All signals 761PLC interface 437Field I/O 324Cross connected 105

SignalType

di_G2_OK Drivesdi_G2_Sel DI

di_G2_Sel Driven bydi_VariantB AND di_G2_OK DI

di_LoadStn_Clear DI

di_SafeStop TriggersQuickStop DI

di_VariantA Drivesdi_G1_Sel DI

di_VariantB Drivesdi_G2_Sel DI

di_G2_OK DI

DeviceWAGO_IO_RobotArmWAGO 750-306 · DeviceNet

Address13

Connections

Drives di_G2_Sel via Cross_di_G2_Sel

Cross-references

MainModule.modRead

rToolCheck · line 112

WaitDI di_G2_OK, 1;

What each one reads when a line stops

Edmund compared with general LLMs like ChatGPT and Copilot, and with competitors built for the same job.

Compare with

Sources it reads
	Edmund For maintenance teams 6 of 6 sources	General AI ChatGPT, Copilot, Gemini, Claude 6 of 6, partly	PLC copilot PLC troubleshooting 2 of 6 sources	CMMS copilot Maintenance AI agent 3 of 6 sources
PLC programs	EdmundTIA Portal, Allen-Bradley and Omron projects, answered with block and line	General AIText exports such as L5X or PLCopen XML	PLC copilotPLC, HMI and SCADA projects	CMMS copilotNot mentioned
Robot programs	EdmundABB RAPID modules and the controller’s I/O, down to the channel	General AIProgram text, if someone uploads it	PLC copilotNot mentioned	CMMS copilotNot mentioned
Electrical drawings	EdmundEPLAN and CAD exports, down to the clamp	General AIPDFs, with drawings discarded on ChatGPT below Enterprise	PLC copilotNot mentioned	CMMS copilotNot mentioned
Manuals and datasheets	EdmundManuals, datasheets and spare-parts catalogs, cited to the page	General AIUploaded files, within per-chat limits	PLC copilotNot mentioned	CMMS copilotManuals, PDFs, PowerPoint and Word files
Maintenance history	EdmundJournals and shift logs, handwriting included	General AIWhatever someone uploads	PLC copilotNot mentioned	CMMS copilotWork order history and historical repairs
Live plant data	EdmundMES, ERP and time-series databases, read-only	General AIExported data, uploaded as files	PLC copilotLive data, optional	CMMS copilotAlarm data, CMMS and EAM read-only
Answers and hosting
Checking an answer	EdmundA source for every answer, or a statement that there is none	General AICitations to files in the conversation, when there are any	PLC copilotTraces the signal through the control logic	CMMS copilotNot mentioned
Hosting	EdmundCloud, hybrid, on-premises or upload-only. AWS in the EU or the US, ISO 27001 and ISO 42001 compliant	General AIThe vendor’s cloud	PLC copilotCloud, hybrid, on-premises or upload-only	CMMS copilotGoogle Cloud, SOC 2 Type 2

See how Edmund helps technicians at the shopfloor.

01 03

Case: /01
Sector: Packaging
Operator: Amcor Flexibles
Site: Nový Bydžov, CZ

How Edmund cut repair time 26% across Amcor's Nový Bydžov plant.

Maintenance knowledge sat in three places, hundreds of PDFs, handwritten logs, and the heads of technicians who'd spent decades on the floor. None of it was searchable. Edmund pulled all of it into one query box.

A junior technician answering a 2 a.m. fault alarm now reaches the same institutional knowledge a senior engineer could recall in seconds. Adoption was immediate, the interface was simple enough that technicians started using it on day one without prompting.

The standout feature was voice input. Instead of typing notes after a long shift, technicians dictate directly on the floor and Edmund writes the entry into the digital maintenance log automatically.

Read the full case →

26%

drop in repair time
440hrs

man-hours saved per plant, per year
90%

faster fault diagnosis
Day 1

adoption · no extra training

Case: /02
Sector: Metalworking
Operator: Moravia Cans
Site: Bojkovice, CZ

Moravia Cans: maintenance information at the point of repair

At its Bojkovice plant, Moravia Cans uses Edmund to support fault diagnosis and repair preparation. The company makes aluminum aerosol cans on high-speed forming and printing lines and has grown by 60% over the past three years.

Maintenance technicians can consult equipment documentation, review previous maintenance interventions and check spare parts availability through a single interface.

Alongside manuals and maintenance records, they can access operational data held in the plant's business systems, Microsoft SQL Server and the QAD ERP, without writing SQL queries or navigating database structures.

Read the full case →

10K+

data points connected through a single interface
24/7

access to technical documentation and recorded maintenance know-how
4

sources in one interface

Case: /03
Sector: Packaging
Operator: Model Obaly
Site: Opava, CZ

Using AI in maintenance can cut downtime by up to 30%

Technical documentation at Model Obaly was split across shared drives, service systems, inventory records and paper binders. Edmund helped digitise the paper documentation and connected all the sources in one interface that maintenance technicians can use right at the machine.

Edmund became the common starting point for diagnosis right at the machine. A maintenance technician talks the fault through with the system and can learn the root cause within a few seconds. If a spare part is needed, they find out straight away whether it is in stock and go to get it without a stop at the workshop. Instead of needless walking, switching between systems and phoning colleagues, they have the answer at hand.

Read the full case →

up to30%

potential for shorter breakdowns when using the system
300K+

pages of technical documentation digitised and made accessible
4

Czech locations · Opava live, two more being implemented

People running Edmund every day.

References from our customers

Now we have everything in one place, right at the machine. I enter the details of a fault and within a few seconds I see what it means, how it was solved in the past and whether we have the parts if we need them. I don’t have to switch between systems or look anything up. Finding root causes is faster, and when we use the system we have the potential for shorter breakdowns, on average by up to 30%. For me, the biggest benefit is that people can focus on the repair, not on searching for information.

Kamil Fedor

Country Maintenance Manager · Model Obaly

AI is the only tool that can systematically work with data from multiple sources. Using Edmund has led to a lower frequency of a specific failure, or even its complete elimination.

David Frajt

Head of Maintenance · MoraviaCANS

We've had a very positive experience with Edmund. The results have an immediate impact on the efficiency of our production processes.

Martin Bryknář

PLC Specialist · Amcor

441 hours

Saved on maintenance per year

New production lines and machines are coming to our plant, and we don't yet have the experience to diagnose them efficiently. At the same time, we can't grow the maintenance team to keep up. So we use Edmund AI as an "invisible co-worker": it fills the missing know-how, supports our technicians' decisions, and speeds up finding and fixing faults.

Ivo Vítek

Head of Maintenance · Innomotics

Industry 4.0 promised a lot but delivered very little. Edmund is genuinely making a difference.

Filip Škeřík

Head of automation · Festo

One brain for your whole plant.

Edmund links your PLC programs, schematics, robot programs, documents, live data and maintenance journals into one graph.

HomeLine 4Chat

Cell 11 keeps going into safe stop at night. Why?

Searching PLC programs

Searching electrical schematics

Reading robot programs

Reading maintenance journals

Type your message for Edmund here

01/PLC programs

Edmund finds the code in PLC projects.

FB_Cell11_Safety, line 48. %I4.3 is the safe run permit: when it drops, cell 11 stops.

Works with

Code preview

SCLLine4_V20_Export/Devices/S7-1500/Cells/FB_Cell11_Safety

44// Cell 11: safe run permit

45#SafeRun := #GuardOK

46 AND #EStopOK

47 AND #DoorClosed

48 AND "Cell11_LightCurtain"; // -B34 OSSD1, %I4.3

49IF NOT #SafeRun THEN

50 #Robot_SafeStop := TRUE;

51 #Alarm_SafeStop := TRUE;

52END_IF;

02/Electrical schematics

Understands the wiring in electrical and mechanical schematics.

%I4.3 leads to EPLAN sheet 217: the light curtain receiver -B34, wired through terminal X9:4.

Works with

Cell11_Elektro.pdf217/ 402

03/Robot programs

Edmund also understands robots.

The ABB robot in cell 11 reads di_VariantB at line 85: variant B loads at pLoadB with gripper G2.

Works with

RAPID modules68

I/O & signals761

Signals

Signal

Type

di_G2_OK

Drivesdi_G2_Sel

di_G2_Sel

Driven bydi_VariantB AND di_G2_OK

di_LoadStn_Clear

di_SafeStop

TriggersQuickStop

di_VariantA

Drivesdi_G1_Sel

di_VariantB

Drivesdi_G2_Sel

diPLC_Heartbeat

diPLC_MotorsOn

TriggersMotorOn

di_VariantBDI

Input

Device

PLC_IO

PROFINET Internal Device

Address

34

Connections

Drives

di_G2_Sel

viaCross_di_G2_Sel

Cross-references

MainModule.modRead

rLoad · line 85

IF di_VariantB = 1 THEN

04/Maintenance journal

And remembers what happened in the past.

Third safe stop in 30 days, all on night shift. Gripper G2 was replaced and pLoadB re-taught on 12 April.

Works with

Maintenance logsShift logs

Cell 11EdmundAdd entryManage

Entries in this journal

Search maintenance entries..StatusSource Type

Name

Status

Source Type

Safe stop, cell 11

M. Novák · 04/26/2026 2:40 AM

Processed

Manual

Safe stop, cell 11

Night shift · 04/22/2026 3:15 AM

Processed

Manual

Safe stop, cell 11

P. Doležal · 04/15/2026 1:55 AM

Processed

Manual

Gripper G2 replaced, pLoadB re-taught✓ Cited

T. Marek · 04/12/2026 10:20 AM

Processed

Manual

0 selected (4 total)Per page10

Edmund gives you a unified diagnostics platform, connected to all your data sources.

HomeLine 4Chat

Cell 11 keeps going into safe stop at night. Why?

That’s -B34, the light curtain receiver at cell 11’s loading station.

Cell11_Elektro.pdfp. 217

Its OSSD1 output feeds %I4.3, the safe run permit in FB_Cell11_Safety, line 48.

FB_Cell11_Safety.sclL48

All three stops came during variant B, which only runs on night shift.

MES · shift planApril

Variant B loads at pLoadB, re-taught when gripper G2 was replaced on 12 April. It now sits 38 mm closer to the loading station, so the gripper’s air hose cuts the curtain’s beams.

MainModule.modL85Gripper G2 replaced

What to check first 🔧

Re-teach pLoadB clear of the protective field. Then re-route the air hose on gripper G2.

Rate the answer

AI debugging platform for every machine on your line.

You have a CMMS. You have an MES. You have Copilot. So why do faults still take hours to fix?

Three things a Plant Director sees in the first quarter.

Provably lower MTTR.

Senior technicians don't have to be the bottleneck.

Reliability numbers that hold up in a board review.

The fix is ten minutes. The hunt is an hour.

Diagnosis eats the budget.

The answer lives in your data. The connections between it don't.

Technicians want to fix, not investigate.

All your plant data and signals, in one platform.

Understands PLC projects and code from every vendor on your floor.

Turns a logical address into a physical spot.

Tests the hypothesis against live data.

Finds the page, the paragraph, the line.

Saves the fix so the next person inherits it.

Shows what’s indexed, and whether every source is current.

Reads the robot program and its I/O, down to the channel.

What each one reads when a line stops

How Edmund cut repair time 26% across Amcor's Nový Bydžov plant.

Moravia Cans: maintenance information at the point of repair

Using AI in maintenance can cut downtime by up to 30%

People running Edmund every day.

One brain for your whole plant.

Edmund finds the code in PLC projects.

Understands the wiring in electrical and mechanical schematics.

Edmund also understands robots.

And remembers what happened in the past.

Edmund gives you a unified diagnostics platform, connected to all your data sources.

What to check first 🔧

You have a CMMS. You have an MES. You have Copilot.
So why do faults still take hours to fix?

The fix is ten minutes.
The hunt is an hour.