Business softwareCustom softwareSMEsIntegration
Production tracking software for small manufacturers
6 min read
Production tracking software replaces paper travelers and the shared shop floor spreadsheet with data entered at the workstation, usually on a tablet: work orders, quantities, scrap and machine stops. In return it shows machine load in real time and raises quality alerts while there is still time to act. For a small manufacturer, a focused custom tool makes sense when an off-the-shelf MES would force too much change, or when the goal is simply to see what is already happening on the floor.
This guide covers what such software should do, where the real complexity lies, and when a packaged system is the better answer.
The starting point: a plant that reports after the fact
In many small plants the work is done well but reported late. An operator writes the start time, the quantity, the scrapped parts and sometimes the reason for a stop on a paper sheet. A supervisor types those sheets into a shared spreadsheet that evening or the next morning. The schedule lives in another file, and nonconformances in a binder.
The same three problems show up every time:
- delays are discovered too late, usually when the customer calls;
- downtime is under-reported, because writing down a five-minute stoppage on paper is not worth the effort;
- the numbers never reconcile, because three documents describe the same shift in three different ways.
The issue is not a lack of data. It is the delay and the loss between the moment data is created and the moment someone can act on it. Our article on replacing Excel with a custom application lists the signs that a spreadsheet has reached its limits.
What production tracking software does
The example we describe on our home page fits in one line: shop floor entry on tablets, machine load dashboards, quality alerts. In practice that means five capabilities.
Workstation entry. The operator picks a work order, often by scanning a barcode, then records start, finish, good quantity and scrap. Each screen should take seconds to complete, standing up, possibly wearing gloves, in a noisy environment.
Downtime and its causes. A stopped machine is logged with a reason chosen from a short list: breakdown, setup, waiting for material, waiting for an operator, changeover. It is the most valuable data point and the one paper loses most often.
Load and progress. The office sees live which machines are running, which orders are late and what remains to be produced this week. No more walking the floor to find out where an order stands.
Quality alerts. A scrap rate above a threshold, a measurement out of tolerance, a run of nonconformances at the same station: the alert reaches the right person while the batch can still be saved.
Traceability. Which material lot, which machine, which operator, which settings. Being able to trace a defective part back is often a requirement from industrial customers.
The metric everyone asks for: OEE
Overall equipment effectiveness is the standard measure of how well a piece of equipment is used. The Lean Enterprise Institute defines it as the product of three rates: availability (losses from breakdowns and adjustments), performance (actual speed against design speed, including minor stops) and quality (scrap and rework). Its worked example: 90% availability, 95% performance and 99% quality give an OEE of 84.6%.
For a small manufacturer, the value is less the number itself than what it forces you to measure. A trustworthy OEE needs downtime logged with causes, accurate counts and recorded scrap, which is exactly what paper loses. Software that computes OEE from rough entries produces a figure that is precise and wrong.
Off-the-shelf MES or a custom application
The international ISA-95 standard describes a manufacturing business in levels: machines and controllers at the bottom, ERP (planning, purchasing, finance) at the top, and in between the manufacturing operations management level, where manufacturing execution systems (MES) sit. Production tracking software belongs to that middle level. The question is whether you need a full MES or a focused tool.
| Criterion | Off-the-shelf MES | Custom application |
|---|---|---|
| Scope | Broad, standard features | Focused on your needs |
| Rollout | Configuration, process changes | Designed around how you work |
| Cost model | Licences, often per seat or site | Build cost or subscription |
| Roadmap | Set by the vendor | Set by your priorities |
A packaged MES is the right choice when your processes look like the rest of your industry, the vendor knows your sector (food, plastics, machining), and you need heavy, regulated features: detailed scheduling, recipe management, compliance-grade traceability. You then benefit from what the vendor learned at other plants.
A custom application makes sense when the need is narrower (make production visible, stop the re-typing), when the way you produce does not fit the vendor's model, or when the tool must integrate tightly with systems you already run. Our guide to what a custom business application costs explains how that choice shows up in a budget.
Where the real difficulty lies
Production tracking looks simple on screen. Four topics make up its real complexity, and every quote should address them.
Shop floor ergonomics. Screens readable from a metre away, wide buttons, input that works with gloves, rugged tablets or fixed terminals. A screen designed at a desk fails on the floor.
Connectivity. Wi-Fi in an industrial building has dead zones. You need to decide what happens when a tablet drops off the network: block entry, or keep it and sync later. That decision shapes the technology choice, as we explain in web app, PWA or native app.
Integrations. Work orders often come from the ERP, and produced quantities must flow back to it. Some machines expose their counters, others do not. Each connection has to be designed with its failure cases: the ERP being down, a duplicate order, a counter reset.
Permissions. Operators enter, supervisors correct, quality signs off, management reads. When the company runs several shops or plants, each one sees only its own data, a topic we cover in multi-site back-office software.
A rollout method that works on the floor
- Start from today's paper forms. They show what the plant already knows how to measure. The first version replaces them, nothing more.
- Watch a real workstation. How long can an operator spend on an entry? Where does the tablet go? Who corrects a mistake?
- Pilot one line or one cell. A few machines reveal network, vocabulary and ergonomics problems before a full rollout.
- Measure before you optimise. OEE, alerts and dashboards come once the entries are reliable, not before.
Our guide to what to build first in an MVP applies the same discipline to any first release.
Where to start
Gather three completed production sheets, your tracking spreadsheet and the list of your machines: that is enough to describe the need. At LPR Studio we turn those documents into a free visual prototype, presented in a video call within 5 working days, showing both the operator screens and the office views. You see whether the tool fits your plant before committing to anything, and the three ways to pay for it are on our offers page.