By need · ManufactINS
OEE software that shows where the time goes
ManufactINS is OEE software for factories in Egypt, Saudi Arabia, the UAE and the GCC: it works out availability, performance and quality for each machine from your machine downtime and output records. It shows the hours lost to stops, slow running and defects, and ranks stop reasons by the time they cost — in Arabic and English.
How the OEE software works
- Bring in the shift recordsOne line per machine per shift — planned production time, downtime and its reason, ideal cycle time, units produced and good units — uploaded from Excel or CSV, Arabic or English headers.
- Planned stops kept outA planned stop comes out of planned production time instead of counting as a loss, and support equipment is shown apart from production machines.
- OEE per machineAvailability is run time over planned time, performance is ideal cycle time times units over run time, quality is good units over units produced — multiplied together, machine by machine.
- Where the time goesHours lost to stops, to slow running and to defects side by side, so you know which of the three to attack first.
- Downtime by reasonStop reasons ranked by hours lost — the Pareto that tells maintenance and production where to start — while operators keep reporting new stops from their phones.
- Connected in the pilotMachine and PLC data are connected in the pilot, through your gateway or historian, so OEE runs on machine data as well as shift records. Your plant systems are connected during the pilot — MES (SAP DM, Siemens Opcenter, Tulip), historian and SCADA (OSIsoft PI, Ignition, OPC-UA), maintenance (SAP PM, IBM Maximo, Fiix), your ERP and spreadsheet exports.
Set up in your pilot
- OEE by shift and by product is set up in the pilot.
- Your own stop-reason log replaces the demonstration plants’ labelled sample loss profile in the pilot.
In Egypt, Saudi Arabia, the UAE and the GCC
Egypt
Screens, reports and exports in Arabic and English, so the same OEE review works on the floor and in the boardroom; operators report stops in Arabic.
Saudi Arabia
A Riyadh plant reads its shifts on Riyadh time with a Friday–Saturday weekend; the OEE arithmetic is the same in every country.
UAE and the GCC
A plant can run on Dubai time, in Arabic or English. Nothing UAE-specific is needed for OEE, and none is built.
How to choose
- Where the data comes fromMachine signals, operator entries or uploaded records — and what happens when a signal drops. A number you cannot trace is a number nobody acts on.
- The definitionCheck how planned stops, ideal cycle time and rework are treated; two tools can give two OEE figures from the same shift.
- Loss drill-downOne OEE number changes nothing; you need hours lost by category and by stop reason.
- Effort on the floorReporting a stop should take seconds on a phone, in the operator’s language.
Frequently asked questions
What is OEE software?
OEE software measures how much of the planned production time a machine actually spends making good parts at full speed: availability, performance and quality, multiplied together.
How is OEE calculated in ManufactINS?
Per machine: availability = run time ÷ planned production time (planned stops removed), performance = ideal cycle time × units produced ÷ run time, quality = good units ÷ units produced, and OEE = availability × performance × quality.
Is there free OEE software?
You can start with a spreadsheet of shift records — the same records ManufactINS reads — and see OEE worked out on them in a pilot agreed with the Epsilon team.
Does it read data from our machines directly?
Yes, once connected in the pilot: machine and PLC data come in through your gateway or historian (OPC-UA, Ignition, OSIsoft PI). Until then OEE is worked out from shift records.
Can it show OEE by shift or by product?
Yes, in the pilot: OEE by shift and by product is set up in the pilot. From the first day OEE is shown per machine, with the hours lost and the stop reasons behind it.
Does it work in Arabic?
Yes. Every screen, report and export works in Arabic, right to left, and in English. Operators can type or speak commands in Egyptian Arabic on Live Operations, and the Document Reader reads Arabic and English, printed or handwritten.
The modules that do it
- OEEAvailability, performance and quality by machine, line, shift and product, with loss drill-down.
- MachinesEvery asset with status, telemetry, health score and the maintenance behind it.
- Shop FloorLive floor — lines, machines, output, scrap and downtime as they happen.
- Upload centerBring an order in from its own files — customer PO and terms, production plan, cost, materials, operators, production reports, inspection and dispatch — new or already in production.
- ReportsGenerate a report for the plants in scope — a stored HTML, CSV and Excel file with its run ID, scope, time and delivery evidence.
Related pages
- Machine downtime tracking software, from the stop to the causeStops reported from the floor, worked by maintenance, ranked by reason, with MTBF and MTTR from your work orders.
- MES software for the shop floor — and the decisions above itThe MES core most plants start with — jobs, clock-in, downtime, NCRs, order routes — alongside a full MES where one runs.
- Factory management software for one plant or severalOne view of production, people, machines, quality and decisions, plant by plant or across plants.
Request a guided demo
ManufactINS is not self-serve: the Epsilon AI team walks you through it on sample data, then arranges individual, time-limited access. Sending the request never creates an account. In English and Arabic.
Request a guided demo