Skip to main content
§ For packaging plants

Cut down your diagnostics time
by 80%.

AI debugging platform for packaging lines. Edmund reads the PLC programs, drawings and OEM manuals of every machine on the line, plus your maintenance logs, and tells your technicians why the line stopped, with the source for every step.

Reads SiemensOmron
Send us your hardest fault
  1. 01You send the fault
  2. 02A 20-minute call
  3. 03The root cause, within 48 hours
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
Ask Edmund, try “where is -94B1 wired?”

Trusted by leading global manufacturers

§01 The bottleneck

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

$36,000

An hour of unplanned downtime at a consumer goods plant, on average (Siemens, The True Cost of Downtime 2024).

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

§02 Why downtime hurts

It takes ten minutes to repair the fault,
but an hour to diagnose it.

On a packaging line, clearing the jam takes minutes. Finding why it happened takes the rest of the hour: the sensor behind the fault code, and the page in the OEM manual that explains it. The answer is in your PLC programs, drawings, alarm history and maintenance logs, and in the heads of your senior people.

MTTR · diagnosis vs repair
Without Edmund
Diagnosis ~50 min
Repair ~10 m
With Edmund
Diagnosis ~10 m
Repair ~10 m
Saved ~40 min
−80% diagnostic time on every fault.
§03 Where to start

Send us your hardest fault.

The one your maintenance team is still trying to solve. We look into it for free: send the fault, your maintenance history or both, then pick a time for a 20-minute call.

One fault and that machine’s data

The fault, plus what you have for the machine: the PLC program, drawings, manual or alarm log. We show you how Edmund finds the root cause.

Please describe the fault in a sentence or two.
Please enter your name.
Please enter a valid work email.
Please enter a valid phone number, or leave it empty.
Please enter your company.

Your maintenance history

Work orders or downtime records, exported from your CMMS or a spreadsheet. We show you which faults cost you the most hours, and where Edmund would help.

Please enter your name.
Please enter a valid work email.
Please enter a valid phone number, or leave it empty.
Please enter your company.

Your data stays confidential. NDA available on request.
How we handle personal data

What happens next

  1. 01You send the fault

    The fault in a sentence or two, and the files if you have them at hand.

  2. 02A 20-minute call

    We go through it together and agree on any files we still need. The 48 hours start when we have them.

  3. 03The root cause, within 48 hours

    Why the line stopped and where the cause sits in the machine’s PLC program and OEM manual, with the source for each step. A maintenance history comes back as the faults that cost you the most hours, and where Edmund would help.

§04 Evidence

Results from manufacturing groups using Edmund

Flexible packaging plant in Nový Bydžov, part of Amcor plc (NYSE: AMCR). Measured over one year.

26%
faster repairs
€190K
a year back at the plant
Read the case study

Corrugated and solid board packaging, four Czech locations, part of the Swiss Model Group.

up to30%
potential for shorter breakdowns
300K+
pages of documentation at the machine
Read the case study
“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, Moravia Cans
Read the case study
§05 One platform

Every machine on the line, in one place.

Edmund reads each machine’s PLC program, electrical drawings and OEM manual, plus your maintenance log, and answers from all of them at once.

every OEM

Reads the program of every machine on the line.

Siemens, Omron and Allen-Bradley projects from each OEM in one searchable model. Edmund answers with the block and the line, so a technician can follow code an OEM wrote.

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
§06 Questions

What maintenance managers at packaging plants ask first.

Our lines mix machines from several OEMs. Does that matter?

No. Edmund reads each machine’s own program, drawings and manual, so a line built by five OEMs is five sets of sources in one search. Siemens, Omron and Allen-Bradley projects are read the same way.

What can we send?

Either of two things, or both. A fault with the data of that machine: the PLC project or an export of it, the drawings, the manual, the alarm log. And your maintenance history: work orders or downtime records from your CMMS or a spreadsheet. Attach the files to the form, up to 20 MB in total, or send them after the call. Missing pieces are fine: the answer says which sources it used.

Where does our data go?

Into Edmund on AWS, hosted in the EU (Ireland) or in the US, whichever you choose. It is encrypted and kept inside a single-tenant boundary for your company, and the language model runs under zero data retention, so nothing you send is kept for training.

Do we need to connect Edmund to the line?

Not for the first answer. It comes from the files you export. Live data from SQL or MES is connected later, if you want it, and Edmund only reads: nothing in your production systems gets changed.

Who is behind Edmund?

Edmund s.r.o., from Ostrava in the Czech Republic. The company came out of an industrial consulting practice, and Edmund now runs on 130+ machines across four countries.

Send us the fault that stopped your line last week.
Answer within 48 hours.

Send your hardest fault

This project was realised via financial support from Technological Incubation program

Financováno Evropskou unií · NextGenerationEU Národní plán obnovy Ministerstvo průmyslu a obchodu Czech Republic — The Country For The Future Technologická inkubace · CzechInvest