We develop a manufacturing execution system built for your factory — making the shop floor visible in real time, from work orders to OEE, scrap to shifts, running on a PLC/SCADA bridge and shop-floor terminals.
Production Tracking & MES (Manufacturing Execution System) is the software layer that closes the gap between planned production and what actually happens on the shop floor. It pushes work orders down to the floor, collects data from machines and operators, and brings OEE, downtime, scrap, waste and quality data to the screen in real time. Your ERP plans production; the MES measures how that plan plays out on the floor and feeds it back. The two complete each other — without one, the other is only half a system.
Off-the-shelf MES packages usually force your production flow into the mould the software accepts. Yet in sectors such as carpet, machinery, textiles and food, every loom, every line and every shift has rules of its own: machine speed, lot size, scrap logic, quality control points, recipes and counting methods vary from company to company. Custom development fits the software to your process — not you to the software.
At Pan Innovation House we build shop-floor screens simple enough for an operator to use with gloves on, and dashboards that let a manager take the pulse of the line at a glance. Thanks to an API-first architecture, your MES talks to your existing ERP, accounting and hardware. The source code we write and your data are handed over to you as defined in the contract; third-party and open-source components remain subject to their own licences. As the system grows, new lines, machines and reports can also be added by another team.
Production facilities in carpet, machinery, textiles or food that want to see what is happening at each machine on a live dashboard rather than via Excel and phone calls — managing downtime, scrap and OEE with data, not guesswork.
Mid-sized manufacturers whose production plan looks fine in the ERP but doesn't hold on the floor, and who want clarity on how work orders reach operators and where and how long delays occur on each machine.
Exporting companies that must offer overseas customers traceability by lot, batch and shift, and keep quality control records and scrap rates ready for audit.
Facilities with PLCs, SCADA or machines running in isolation that have never brought this data into one manageable system — and want a modern MES layer on top without throwing away existing hardware.
We push work orders — opened in the ERP or in the MES — down to the floor by machine and operator; start, pause and complete are recorded with a single touch on the shop-floor terminal. Plan and actual production are shown side by side.
We calculate OEE from its availability, performance and quality components, and categorise downtime causes (breakdown, changeover, waiting for material, shift) to show exactly where each loss comes from. Target-versus-actual comparison is standard.
We record scrap and waste during production with reason codes, and digitise measurement and accept/reject records at quality control points. Traceability by batch and lot lets you get to the root of defective production.
We read counter, speed, temperature and status data from machines over OPC UA, Modbus or MQTT, and build a two-way bridge to your existing SCADA system. Wherever possible, we replace manual data entry with automatic data.
We develop simple, fast, error-proof interfaces for touch terminals positioned at each machine. Barcode and RFID scanning, shift handover, break and downtime reporting are designed so they never wear the operator down.
We show the line's live status, shift targets and deviations on large-screen dashboards, and generate WebSocket-based instant alerts and notifications when downtime or scrap thresholds are crossed. Managers see the same picture remotely.
We automatically generate production, scrap and downtime reports by shift, line and machine, and feed actual production back into the ERP and cost calculations. We open the data to BI tools, enabling long-term trend analysis.
We observe your production line on site, mapping the machines, shift patterns, scrap and quality logic, and the existing PLC/SCADA and ERP infrastructure. Together we decide which data will be collected automatically and which manually.
We design the data model for work orders, machines, shifts, lots and quality data, and finalise the API-first integration plan for the ERP and machine bridges. Hardware protocols and terminal requirements are fixed at this step.
Before rolling out across the factory, we develop iteratively on a single line or machine group. We mature the shop-floor terminal, dashboard and machine bridge under real production conditions, with operator feedback.
We roll the pilot-proven system out to other lines in stages, and train operators and managers on the floor. The transition is managed with a parallel-running period, without stopping production.
After go-live we provide monitoring, maintenance defined in the contract and continuous development for new line, machine and report requests. Every change goes through a review step before it goes live.
No. The ERP plans production and manages stock and costs; the MES measures how that plan actually plays out on the floor and feeds it back. The two complete each other. Your existing ERP (Logo, SAP or a custom system) stays in place. The custom layer connects to your ERP through the routes its vendor supports (API, service layer or an approved import); it does not write directly into the ERP's database tables. The route depends on the version and licence and is agreed in writing during discovery.
In most cases, yes. We can read machine data over common protocols such as OPC UA, Modbus and MQTT, and bridge to your existing SCADA system. For older machines that provide no data, visibility comes from counters, barcodes or operator entry on shop-floor terminals; this is not as detailed as data from sensors.
We do not give a firm figure before discovery; presenting made-up prices and timelines goes against our principles. Cost and duration depend on the number of lines, the depth of machine integration, terminal requirements and reporting scope. After the shop-floor discovery we share the scope and a staged budget transparently.
Yes. The source code we write and your data are handed over to you as defined in the contract; third-party and open-source components remain subject to their own licences. When you later want to add a new line, machine or report, you can also continue development with your own team if you prefer.
Yes — that is our priority. We first go live on a single pilot line, and only after validation roll out to the other lines in stages. During the transition your existing method runs in parallel with the new system for a period; this reduces the risk of production stopping.
Yes. After go-live we provide maintenance, monitoring and continuous improvement; the maintenance scope and response times are defined in the contract. For new requirements, additional reports and new line integrations, we keep developing; every delivery goes through a review step before it goes live.
We listen to what you need and tell you whether custom development or an off-the-shelf product fits better. The first 30-minute call is free; the scope of an on-site discovery, and its fee if any, is agreed in writing during that call.
We design the whole chain from sensor to cloud: device firmware, MQTT-based telemetry, edge processing and a remote monitoring panel. Your machines, production line and field equipment come together in a single data stream — and the source code we write is handed over to you.
Details →We collect a machine's vibration, temperature, current and cycle data, learn its normal operating signature, and catch deviations from that signature before failure occurs. An alert becomes a maintenance work order; the machine's history and the parts used accumulate in the same record.
Details →We build camera-based visual inspection on the production line: surface defects, colour and shade variation, missing parts, label verification and dimensional checks. The work does not begin as a software installation — it begins with feasibility and sample testing.
Details →We generate demand forecasts from order history, seasonality and stock data, and link that forecast to your production and purchasing plans. We sequence work under capacity constraints, calculate safety stock and measure how accurate the forecast actually was.
Details →We build a system that collects labour data from the shift plan to the time-and-attendance terminal, from overtime to piece-rate incentives, and prepares the file that goes to payroll matched against production records. Who has earned what is visible clearly enough that objections become unnecessary.
Details →We build a system that collects meter and field data and allocates energy to lines, machines and products. The basis for your annual declaration is ready, and a product's true energy cost stops being an estimate.
Details →
