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
§ 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 
Send us your hardest fault
- 01You send the fault
- 02A 20-minute call
- 03The root cause, within 24 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.
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;
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.
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.
How often should we clean the WL12 photocell on conveyor 3?
From the conveyor 3 manual (rev 04/2024):
"Clean the lenses of all photocells in the infeed section every 240 operating hours. Dust on a lens causes dropouts on the product-detect signal."
Conveyor 3 manual · rev 04/2024 Page 7
Your maintenance log shows the lens was last cleaned 312 h ago, past the 240 h interval. That lines up with the repeated photocell dropouts.
Has anyone fixed the Station 52 photocell before? What did they do?
Yes — the Station 52 photocell replacement (Tomáš Marek, Apr 23) sits at the top of the Line 4 journal, indexed alongside every recent fix:
NameStatusCreated
Station 52 – photocell replacementTomas MarekIndexedApr 23
Cell 7 – main panelTomas MarekIndexedApr 23
St 31/32 servo motor offlinePetr DolezalIndexedApr 15
WP transfer fault – station 13Jan HorakIndexedApr 14
Line commissioningTomas MarekIndexedApr 13
Cell 3 – calibrationPetr DolezalIndexedMar 26
34 entries‹ 1 2 3 4 ›
Open any entry for the full symptom, cause, and fix — so the next technician inherits it instead of rediscovering it.
For Assembly line 4 — what's indexed, and is everything current?
Assembly line 4 is fully indexed and every source is active:
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
A plant lead can confirm coverage at a glance — and catch a source that's gone stale before someone hits the gap mid-fault.
Ask Edmund, try "where is -94B1 wired?" ⌘ K
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.
Without Edmund
With Edmund
§03 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.
/01 PLC · every OEM
Reads the program of every machine on the line.
Siemens, Omron and Allen-Bradley projects from each OEM, plus anything that compiles to IEC 61131-3, 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: 
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:
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 Drawings · logical to physical
Finds the photo-eye behind the fault code.
A tag resolves to the cabinet and the terminal on the filler or the case packer. Finding where a signal is wired takes seconds instead of a search through the OEM’s drawing set.
Logical → physicalCabinet mapsWire-tracing
Supports PDF exports from: 
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.
%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 Live data · SQL and MES
Checks the guess against stops and rejects.
Stop reasons and reject counts from SQL and MES. Edmund confirms or rules out a cause across shifts and SKUs, and comes back with a next step.
MES ERP Time-series 10+ DB connectors 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 in the OEM manual.
Manuals for fillers, labelers, case packers and palletizers, change-part instructions and datasheets, answered with the exact page and paragraph.
Manuals · datasheetsDrawings · PDFCited every time
Supports PDF exports from:
"Clean the lenses of all photocells in the infeed section every 240 operating hours. Dust on a lens causes dropouts on the product-detect signal."
Conveyor 3 manual · rev 04/2024 Page 7
Sources
PDFConveyor 3 manualp. 7
PDF+SK3 cabinet · sheet 217v. 3
MDMaintenance journal 2026-04-12#4729
/05 Maintenance logs · what the shift learned
Keeps what night shift learned at changeover.
Work orders and handwritten shift logs become searchable. The last fix for the same fault comes back with the answer.
Handwriting OCRPhotos · scans · PDFs
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 | ||
| Photocell stop, conveyor 3 | Processed | P. Doležal | 04/16/2026 | ||
| Light barrier lenses cleaned | Processed | T. Marek | 04/12/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 which machines are covered, and what is out of date.
A live count of what is indexed for each machine, with the time of the last sync. The maintenance lead sees the gaps before someone hits one mid-fault.
Coverage countsPer-source statusLast-sync freshness
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, from the palletizer to the pick-and-place cell. 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 modulesI/O & signalsChannel map
More vendors coming soon: 
RAPID modules 68 I/O & signals 761
All signals 761PLC interface 437Field I/O 324Simulated 170
SignalTypeDeviceAddress
ai_002 AI WAGO_IO_RobotArm 18–29
ai_Calib_Force AI WAGO_IO_AcousticCabinet 35–46
ai_I_MOT1_ST2 AI WAGO_IO_ControlCabinet 67–78
ao_U_G22 AO WAGO_IO_AcousticCabinet 0–15
di0008 DI WAGO_IO_RobotCabinet 8
di01TA2 DI PLC_IO 33
ai_002 AI
DeviceWAGO_IO_RobotArmWAGO 750-306 · DeviceNet
Address18–29
Channel map
01234567 0 1 2 3 4 5 6 7
This signalUsedFree
60 of 432 channels used on this module
§04 Where to start
Send us your hardest fault.
The one that stops the line at changeover, or the code nobody on night shift can place. We diagnose it for free: describe it below, then pick a time for a 20-minute call.
What happens next
- 01You send the fault
A sentence or two about the fault, and your details.
- 02A 20-minute call
We agree which files we need. The 24 hours start when they arrive.
- 03The root cause, within 24 hours
Why the line stopped and which machine’s program and manual page it comes from, with the source for each step.
§05 Evidence
Results from packaging plants that run Edmund.
Corrugated and carton packaging, part of Model Group.
30%
lower MTTR
4
plants running Edmund
“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.”
§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 do we send for the hardest fault?
At first, the fault in a sentence or two and your details. On the call we agree which files matter, usually the PLC project or an export of it and the alarm log, and you hand them over. 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. It came out of an industrial consulting practice and today runs on 130+ machines across four countries.
