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

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.

#GoHallZero starts it only while neither #Cancel nor #Stop is set, line 143.
When #status.enabled is off, it first sets #state.enable.start, lines 144 to 145.

Line4_V20_Export

S7-1500 · ET200MP

Code PreviewCopy pathOpen in PLC program

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

Load previous lines · lines 122–141

142//Go Hall Zero143IF #GoHallZero AND NOT #Cancel AND NOT #Stop THEN144    IF NOT #status.enabled THEN145        #state.enable.start := true;146    END_IF;147    #state.goHallZero.start := true;148    #status.done := false;149END_IF;

Load more lines from line 150

Robot R1 stopped at the pick and is just waiting. Why?

R1 is waiting in plcWaitVacuum for its vacuum switches. It stays at the pick until diVacuumReachedModules12 is on, and diVacuumReachedModules34 too when it picks with both circuits, line 66.

While it waits, doRobAtPick is on and doRobMoving off, lines 64 to 65.
Once the switches close, doRobAtPick drops and doRobMoving comes back, lines 67 to 68.

R1_Backup

IRC5 · T_ROB1

Code PreviewCopy pathOpen in robot program

RAPIDR1_Backup/RAPID/TASK1/PROGMOD/PLC_IF.mod

Load previous lines · lines 43–61

62PROC plcWaitVacuum(bool bBoth)63    ! the switches of the circuits it switched on64    SetDO doRobMoving,0;65    SetDO doRobAtPick,1;66    WaitUntil diVacuumReachedModules12=1 AND (NOT bBoth OR diVacuumReachedModules34=1);67    SetDO doRobAtPick,0;68    SetDO doRobMoving,1;69ENDPROC

Load more lines from line 70

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

Cited on page 3 of 12

100%3 / 12

How did IMM01 spend its energy the week of Jan 12? Anything wasteful?

Pulled IMM01 power from the MES historian for Jan 12–18, 2026 and bucketed it by machine state:

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

The machine drew power while idle for 74 h, more than double its 31 h of actual production. Trimming idle time is the fastest saving here.

MES database

energy_by_state

QueryCopy

SQLmes / energy_by_state

1SELECT state, ROUND(COUNT(*) / 4.0) AS hours2FROM energy_by_state3WHERE machine = 'IMM01'4  AND ts >= '2026-01-12' AND ts < '2026-01-19'5GROUP BY state6ORDER BY hours DESC;

State	Hours
ON_NO_PROD	74
OFF	63
PROD	31

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

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.

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.

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.

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.