Skip to main content
All customer stories

No maintenance question
goes unanswered.

Manual collections, maintenance records, and live ERP databases spread across disconnected systems. Edmund brought them together into one query interface, so technicians at the Bojkovice plant get a complete picture from a single question. No switching between tools or chasing colleagues for context.

Industry
Aluminum aerosol cans
Location
Bojkovice, Czech Republic
Customer
MORAVIA CANS a.s. · 480+ employees
Sources read
Manuals · Records · SQL · QAD · PowerBI
10K+
data points connected into one platform
24/7
expert knowledge on the shop floor
3
ERPs unified · SQL · QAD · PowerBI

The problem

MORAVIA CANS is one of Europe's specialist manufacturers of aluminum aerosol cans, known for patented embossing technology and high-speed production lines. With 480+ employees and 60% growth over three years, the Bojkovice factory runs sophisticated shaping and printing operations where uptime is everything. A single stoppage on a high-speed line is measured in cans-per-second, not minutes.

The information needed to keep those lines running sat in three disconnected places. Manual collections lived on shared drives. Maintenance records were threaded through local logs. And the live operational data, covering spare-parts availability, repair history, and production metrics, sat behind Microsoft SQL, QAD ERP, and PowerBI, each requiring its own login and, often, a colleague who knew where to look. Technicians chasing a fault spent more time switching between systems than diagnosing the line.

How we deployed

Edmund was wired directly into Moravia Cans' three primary sources: manual collections, maintenance records, and live ERP databases. Those feeds surface through a single AI interface on the shop floor. Connectors run against Microsoft SQL, QAD, and PowerBI, so technicians get production data alongside documentation in the same query window, without database expertise and without an IT ticket in the loop.

The deployment focused on the workflows where shift-by-shift continuity matters most: checking spare-parts availability before starting a repair, reviewing how a similar fault was solved last time, and pulling current production metrics to verify whether a line is drifting before it stops.

What Edmund read
  • ManualsVendor PDFs and internal procedure manuals from the shaping and printing lines
  • RecordsMaintenance logs, repair histories, and shift-handover notes, queryable in natural language
  • SQLMicrosoft SQL Server: production metrics, spare-parts inventory, traceability data
  • ERPQAD enterprise ERP, read live for parts availability and procurement status
  • BIPowerBI datasets: uptime, OEE, and throughput dashboards exposed to floor-level queries

What changed

The maintenance team at Bojkovice now works from one query interface instead of three. A technician on shift can check spare-parts availability, review repair history, or pull production metrics on the spot, without database expertise or IT support. The friction of switching between QAD, PowerBI, and the shared drive has disappeared from the daily routine.

The effect on continuity is just as important. When experienced technicians are off-shift, their know-how stays accessible: Edmund captures institutional knowledge and makes it available around the clock. Faster troubleshooting, smoother shift handovers, and more confident decisions at any hour. And no maintenance question goes unanswered, regardless of who's on the floor.

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 a.s.

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