Shop Floor Tracking Software: What to Look For (and When to Build)

“Where is order 4471?” Someone walks to cutting, checks with assembly and rings the supervisor. The job is waiting for a part, but the office still thinks it is in progress.

The information exists on the floor. It has not reached the people who need to plan around it.

Shop floor tracking software records the progress of work through production — the job, its stage, the station, quantities completed and the events that explain what is happening. When operators or connected equipment keep those records current, the office can investigate a delay without rebuilding the picture through conversations.

Choosing a system means looking beyond whether it can log a job. It needs to fit your routing, work on suitable hardware, preserve useful records and remain practical during a busy shift.

This buyer’s guide compares focused tracking tools, ERP modules, MES and custom systems. It explains what to test, how to assess pricing and how to prove a manageable first workflow before committing to wider coverage.

A useful floor view connects the current status to the job and the reason for a delay. Illustration from OpsMavix.

Key Takeaways

• Shop floor tracking provides a record of job progress; how current that record is depends on capture methods, connectivity and update timing.
• Test the operator workflow during real work. Fast, understandable updates matter more than a long feature list.
• Distinguish processing, waiting, setup and rework. Time between two timestamps is not automatically productive labour time.
• Check routing, partial quantities, holds and corrections using your own examples before selecting a system.
• Compare licensing at the operator, device and shift coverage you need. Per-user pricing is one consideration, not a universal cause of failure.
• A focused tracker, ERP module, MES or custom build may fit. Choose against the depth of control and integration required.
• Pilot one route, reconcile its records and agree ongoing maintenance before expanding.

In this guide:

• What the software records
• What to look for first
• Licensing and floor coverage
• Build versus buy
• A worked job-tracking example
• The shape of a focused system
• Where ERP and MES fit
• How to test before committing
• Frequently asked questions
• How OpsMavix can help

1. What Shop Floor Tracking Software Actually Does

The core function is to record what happens as a job moves through its production route and make that information available to the appropriate people.

An operator identifies a job, starts an operation, records a pause or finishes a quantity. The record links the event to the job, stage, time and relevant identity or equipment.

A supervisor can then see the current state and investigate the history behind it.

Status and timing answer different questions

A status saying “at assembly” does not establish whether assembly is active, waiting for material or paused for inspection. Agree the states that matter to your workflow.

A tracker is not automatically a scheduling engine

A job board can show queues and dates without calculating machine capacity or selecting the next job automatically.

Likewise, recording elapsed time does not automatically provide reliable labour costing, material traceability or quality release controls.

Separate the basic visibility requirement from capabilities that need additional data and rules. See what a production monitoring system is for the wider visibility concept.

Be clear about the source of updates

Some systems rely on operator entry. Others use machine signals, imports or a combination.

A running machine signal does not necessarily identify the job or prove that an acceptable quantity was produced. Manual job updates do not necessarily describe the machine’s actual state.

Define how those sources relate before presenting one combined picture.

2. What to Look For, in Priority Order

Use these checks to assess the proposed workflow, rather than comparing feature counts alone.

First: capture that works during the shift

Watch an operator identify a job and record an event. Count the taps, scans and required fields.

Can they do it with the protective equipment and working conditions relevant to the station? Can they recognise the correct job among similar references? Is it clear whether the update succeeded?

A short interaction still needs enough information to be reliable. Removing every field can make capture quick while leaving the record ambiguous.

Second: hardware and connectivity

Confirm the actual tablets, terminals, scanners or phones supported. Check the scanner’s input method, screen size, browser or operating-system requirements and where the device will be located.

Existing hardware can reduce purchase costs, but compatibility and suitability need testing. A shared terminal far from the work may encourage delayed entry.

If offline working is required, test it explicitly. Confirm how events are stored, synchronised and reconciled after a connection returns.

Third: routing and quantity handling

Use a job that includes partial completion, an alternative stage or rework. Check whether the software represents it without inventing misleading statuses.

If a batch splits between two stations, can the record distinguish the quantities? If one stage finishes but quality approval is outstanding, can the job remain correctly blocked?

Some packaged products can support these requirements through configuration. Establish what is standard and what needs extensions.

Fourth: meaningful reporting

Prioritise reports that answer a specific question: which jobs are blocked, how long work waits at a station or which operations repeatedly exceed the plan.

Ask how each measure is calculated. Display refresh times and missing updates rather than treating an incomplete record as a complete result.

Fifth: coverage, integration and total cost

Price the system for the people, devices, shifts and sites that will actually use it. Include implementation, hardware, training, connections and ongoing maintenance.

Integration matters where production updates affect materials, orders, costs or dispatch. A usable floor interface and correct downstream records should be evaluated together.

3. How Licensing Affects Shop Floor Coverage

Per-user licensing can increase costs as more operators gain access. Other products may offer device, concurrent-user, operator-specific or site arrangements. Confirm the actual terms rather than assuming that every SaaS product uses the same model.

The goal is enough permitted access for reliable capture across the intended workflow.

Separate a shared terminal from a shared identity

Several operators can use one physical terminal while identifying themselves individually, if the software supports that process.

If people record events under one generic identity, the record establishes that account’s activity. It does not reliably identify the individual operator.

That may be insufficient if you need operator-level review, approvals or labour records. Agree the identification requirement before choosing a licence mix.

Price realistic growth

Consider a hypothetical product charging £30 per named operator per month. Assume the same rate and full-year access for each operator:

These are invented rates for a pricing calculation, not a vendor quotation. They exclude VAT, implementation, equipment and additional services.

A site licence or device licence needs its own equivalent calculation. A custom build should include hosting, maintenance, third-party components and changes rather than being treated as cost-free after delivery.

Do not assume pricing explains every failed rollout

Coverage gaps can also come from slow capture, unclear responsibilities, unsuitable hardware, inconsistent routing and missing training.

Investigate why the records stopped being maintained. A cheaper licence does not resolve a difficult operator workflow.

4. Build vs Buy: Compare the Workflow Fit

Buying and building both require requirements, testing and adoption. The difference is where the capability comes from and who maintains it.

Buy when the product handles real cases well

A packaged tool can provide a useful starting point when its supported routing and capture model match the requirement.

Ask to see your examples rather than accepting a demonstration of the simplest route. Review what happens during rework, partial batches and corrections.

Configuration may be enough. Confirm its limits before concluding that a custom build is necessary.

Build when the unmet requirement matters

A custom system can target particular routes, terminology or handoffs. It also creates responsibility for development, testing and maintenance.

Identify the business value of the requirement. An unusual label may be easy to configure; a complex split-batch process may affect the whole data model.

Compare the cost of a well-defined custom solution with the configuration, extension and operating effort of suitable products. Unusual workflow alone does not establish that building will be cheaper.

Check handover and dependency costs

If ownership matters, confirm source-code rights, documentation, deployment access and third-party terms.

An owned build still depends on infrastructure and supporting components. Ask how another competent maintainer could operate it if the original relationship ends.

For the broader comparison, see operational systems vs ERP.

Floor capture is one part of the workflow. Its updates need to reach planning, supervision and the relevant office records.

5. A Worked Example: Tracking One Job Through the Floor

Consider a hypothetical job for 100 brackets moving through cutting, drilling and inspection.

The cutting operation begins at 09:00. At 09:40 it pauses because material is unavailable. Work resumes at 10:10 and finishes at 10:30. Cutting produces 98 acceptable parts and two scrap parts.

These figures illustrate a tracking design, not a customer outcome.

Interpret the time correctly

The start-to-finish interval is 90 minutes. Within that interval, 30 minutes are recorded as paused and 60 minutes as processing.

Recorded processing is not automatically direct labour time. An operator may supervise more than one machine, a machine may run unattended or several people may contribute.

If labour costing is required, define how labour attendance, setup and overlapping work are captured. Do not price future jobs from an unexplained elapsed-time figure.

Partial output needs a visible decision

The job requires 100 acceptable brackets, but only 98 have passed cutting. The system should preserve that difference.

A supervisor may authorise the 98 to continue while planning two replacements. Inspection and final release remain separate conditions.

Marking cutting complete should not imply that the entire order is ready for dispatch.

A missed event needs controlled correction

Suppose the operator forgets to record the resume event. The report will show a different picture.

Provide an authorised correction process that preserves who changed the record and why. Flag incomplete sequences for review rather than assuming that every timestamp represents complete evidence.

6. What a Right-Sized Shop Floor System Looks Like

A focused system has enough coverage to answer its intended questions without asking operators to maintain unnecessary detail.

That does not mean reducing every event to a single button. The required detail depends on the decisions and controls the business needs.

Start with a minimum usable scope

A first phase might include job identification, current operation, start or completion events, output quantities, hold reasons and a supervisor view.

If quality release or material traceability is essential, include it from the start. Those requirements cannot be postponed simply to make the pilot smaller.

Make exceptions visible

Useful exceptions may include jobs with no recent update, incomplete event sequences, work past its planned date, quantities that do not reconcile and records awaiting quality decisions.

Give each exception an owner. A dashboard warning helps only when someone can investigate and resolve it.

Connect only against defined rules

Agree which application owns the work order, routing, material issue and shipment status.

Specify what completion means and which downstream record should change. A repeated update should not post the same quantity twice.

The OpsMavix manufacturing production tracking approach centres on job visibility. The specific stations, records and connections need to be defined for each scope.

7. Where MES and ERP Modules Fit

The categories overlap. A focused tracker records selected events; an MES can provide a broader manufacturing execution layer; an ERP module may connect shop-floor updates with other business records.

IBM’s MES overview describes monitoring and control of manufacturing processes, with capabilities spanning work orders, quality, materials, equipment integration and reporting.

Consider MES when deeper control is required

Requirements may extend beyond knowing the job’s stage to detailed material traceability, quality records, production instructions or equipment integration.

Assess the particular product and implementation. MES offerings differ, and not every deployment has the same scale, pricing or operator interface.

For any mandatory quality or traceability requirement, agree the exact records and acceptance conditions. Selecting a category of software does not by itself establish that those requirements are met.

Consider the ERP module when it fits the existing records

If the ERP already owns jobs, inventory and costing, its supported floor functionality may avoid introducing an extra handoff.

Test the operator interaction and real exceptions. A good office transaction screen does not automatically provide a practical workstation interface.

Compare equivalent outcomes

Do not compare a simple status board with an execution system as though they deliver the same controls.

List the functions needed now and those expected later. Price and test the relevant scope of each option.

Whether tracking sits in a focused tool, ERP or MES, define how production events connect to other business records.

8. The Honest Test Before You Buy

Use a pilot to assess the work, data and commercial model together.

Watch operators use the actual workflow

Choose representative operators and working conditions. Include busy periods and the devices intended for deployment.

Measure capture time, missed updates and how much help is needed. Ask which fields or steps are unclear.

Test exceptions as well as completion

Include a pause, partial quantity, rework, a job amendment, a missed event and a connection interruption where relevant.

Check how the supervisor identifies each issue and restores a reliable state. If offline support is promised, include reconnection and repeated-event handling.

Reconcile the records

Compare recorded quantities and stages with the physical job. Review time definitions, corrections and whether office records receive the intended updates.

A polished dashboard is not enough if the underlying figures do not match the work.

Price full coverage and ongoing operation

Include all required users or devices, additional shifts, sites, hardware, hosting, support and maintenance. Confirm renewal, export and handover terms.

For custom work, agree responsibilities for dependency changes, integrations and future modifications.

Set acceptance conditions before rollout

Define what a successful first phase means: reliable capture, understandable statuses, reconciled quantities and usable exception handling.

Establish a baseline for status-chasing time, incomplete records and overdue work. Review the same measures after adoption, while accounting for changes in volume or job complexity.

Frequently Asked Questions

What is shop floor tracking software?

It records work as jobs move through production and makes progress visible. The scope may include stages, stations, quantities, event times, operators and blockers. How current the view is depends on how updates are captured and transmitted.

What should I look for first?

Test operator capture, device suitability, routing and quantity handling. Then assess reports, integration and total coverage costs. Use representative jobs rather than a feature checklist alone.

Does it measure actual labour time?

Only if the capture and calculation rules support that. Elapsed operation time can include waiting or unattended machine activity. Define how labour, setup, pauses and overlapping work are recorded.

Why do tracking systems stop being used?

Possible causes include difficult capture, poor workflow fit, unsuitable hardware, unclear responsibilities, inadequate training or insufficient access. Investigate the actual gaps rather than attributing every failure to one pricing model.

Is per-user SaaS unsuitable for the floor?

Not inherently. Compare the cost and permitted access against the coverage you need. Check operator, device or concurrent-access options where offered, and preserve the required individual identification.

Should we build or buy?

Buy when a suitable product supports the real workflow with manageable configuration and cost. Consider building when important unmet requirements justify the development and maintenance responsibility. Compare equivalent outcomes.

Do we need MES?

Possibly, if the requirements include broader execution, quality, traceability or equipment-control capabilities. A focused tracker may fit a narrower visibility need. Evaluate the specific scope rather than choosing by category alone.

Can we use existing tablets and scanners?

Potentially. Confirm compatibility, input methods, location, working conditions and connectivity through a pilot. Existing equipment may still need replacement if it does not support reliable capture.

Can we start with one production route?

Yes, if the first scope includes the controls and handoffs needed to work reliably. Choose a representative route, test exceptions and reconcile its records before extending coverage.

How OpsMavix Can Help

OpsMavix builds manufacturing production tracking systems around the job routes and records a business needs to manage.

We start by mapping the stages, identifying where updates go missing and defining what operators and supervisors need to record and see.

That can include:

• Job identification and workstation capture.
• Stages, output quantities and hold reasons.
• Clear definitions for recorded time.
• Supervisor views linked to job records.
• Controlled corrections and visible exceptions.
• Connections to relevant order and inventory records.
• A pilot using the intended devices and actual workflow.

If you cannot locate jobs without a call, or your timing records do not explain where work waits, book a free Operations Leak Audit. Bring a recent delayed job, its route and the records the team used to follow it. We can help trace the gap and assess whether a focused build or an existing product is the better fit.