About
Two careers, one problem, eleven years of work.
Where it came from
I have worked as a Factory Operations Manager and as a software developer. Both jobs showed me the same problem from different sides. On the factory side, procedures, spreadsheets and software existed but did not work together: the management system was written down carefully, and the software knew nothing about it. On the software side, every new application rebuilt the same foundations in a slightly different way.
I started building operational systems for factories eleven years ago, in 2015. The first was EMMo, which made production information easier to see. Each system after it answered a question the previous one had raised, and the goal grew: connect the main factory processes, give people clear responsibilities, and help managers decide what to improve first. EMM is the method those years produced. EMMa Operations is the application built from it, and the first to bring in current technology and AI. This is not a project of a few months.
Who it is for
Factories where the information already exists but sits in separate systems, meetings and spreadsheets. Where procedures were written for an audit, process maps do not match daily reality, nobody is quite sure who is responsible, and important knowledge lives only with a few experienced people.
Those factories rarely have the time or the people to design a complete digital system from zero. That is why EMMa starts from a standard factory model and asks to be checked against your reality instead of invented from nothing. The model used to build and demonstrate it is one example — injection molding and assembly, three shifts, five days a week — not a limit. EMMa has no fixed number of production areas, shifts or products, and no assumed industry: you set up the shape of your own plant.
What it is not
EMMa is a connected operating system for the factory. It includes work normally found across MES, planning, quality, maintenance, HR and management-system tools, but its main purpose is to connect the work between them. It is not an MES, and it does not replace your ERP. It exists to support a decision, not only to store a record.
Creator
Lucian Bumb
Creator of the Efficiency Management Method
Company
Elgibe Solutions SRL
EMMa Operations becomes available on 15 October 2026. Until then this site explains the method and the product. The videos follow on the release date.
Two kinds of experience
The same person asks both sets of questions.
Most factory software is built by people who know software, or specified by people who know factories. Working on both sides means one person asks both sets of questions about the same screen — and has to answer them together.
As an operations manager
- Will people understand how to use it?
- Does it match the real process?
- Is it clear who is responsible?
- Can we see what actually happened?
- Does the software help the factory, or does the factory have to adapt to the software?
As a software developer
- Can the code be maintained?
- Is the security boundary clear?
- Can it be tested?
- Can it grow without becoming chaotic?
- Can another developer understand it?
That second set of questions is why I built CodingWithEase, the .NET framework EMMa runs on. It applies factory thinking to software: standardise what repeats, prevent the mistake rather than warn about it, catch problems early, and improve the framework instead of every application separately. EMMa Operations is the largest application built on it.
Welcome to the House of EMMa.
If you manage a factory and want to connect people, processes and daily work in one system, let’s talk.