NCTune Software

Shop Floor Time

Work as it happens, recorded directly on the shop floor.

Operators record the operation, time, quantity and downtime where they occur. Shop Floor Time organises these events into a view that helps reconstruct the actual production flow without later copying data from notes and memory.

Working product demo · pilot scope agreed individually

Shop Floor Time operator terminal with an active operation and production route
Active operation and production routeReal operator screen

The problem

Production happens now. The data arrives later.

When a shift is reconstructed only after the work is finished, information loses its order and context. Shop Floor Time moves reporting to the moment when the operator performs the operation.

Recorded after the event

Time and quantities are entered later instead of being captured as the operation progresses.

Fragmented context

Paper, spreadsheets and memory do not always connect an event with the correct machine, person and work order.

Incomplete downtime record

The reason and comment can become separated from the time and place where the stop occurred.

A report instead of a timeline

The final summary shows a result but may not reveal the order of work, pauses and events.

From operator to data

Every event retains the full context of the work.

The information is not created as a separate report. It becomes the next step in the operator's work and stays connected to the operation, time and result.

  1. OperatorOpens the work view

    Works in the context of the assigned workstation and active user.

  2. OperationSelects the correct stage

    The view shows the work order, machine and production route.

  3. EventRecords progress

    Setup, production, pause, downtime or completion form the work timeline.

  4. ResultReports quantity or reason

    Good parts, scrap and downtime data remain attached to the correct operation.

  5. DashboardOrganises the record

    Events enter a view that can be filtered and exported.

On the shop floor

What does the operator do?

The terminal focuses on the current task. The operator sees the active operation and production route, then records events and results without entering the wider reporting dashboard.

Starts and changes the stageSetup, production, pause, downtime and completion.
Reports the resultGood parts and scrap stay connected to the correct operation.
Adds the event reasonDowntime retains its time, reason and comment within the work context.
Operator terminal with an active operation, production route and reported quantities
Operator terminal · working demonstration with fictional data

For supervision

Shop-floor events form a clear view of production progress.

The dashboard does not replace production planning. It organises what operators recorded during work: operations, time, quantities, scrap and downtime.

Shop Floor Time dashboard with work-order progress, quantities, scrap and downtime
Work-order progress, quantities and downtime in one viewReal dashboard screen

Filters instead of manual merging

Time range, work order and operation status narrow the view to the required production flow.

Quantity with quality context

Good parts and scrap remain part of the operation record rather than a separate note.

Export selected data

The visible records can be exported to CSV when the process requires a further analysis step.

Downtime analysis with reason, machine, operator, start time, duration and comment
Downtime analysis · demonstration data

Event context

Downtime is more than just a duration.

The record connects the reason with the machine, operator, work order, start, duration and comment. A supervisor can return to the specific event instead of reconstructing it from several sources.

Product scope

Capabilities organised around the workflow.

Shop Floor Time separates the operator's focused view from the supervisor's wider reporting view while preserving one shared event context.

On the shop floor

Touch-friendly terminal

The current operation, route and actions needed at the workstation.

Work progress

Setup, production, pauses, downtime and completion.

Quantities

Good parts and scrap assigned to the operation being performed.

Event data

Full context

Time, operator, machine, work order, operation and work stage.

Downtime reasons

Reason, start, duration and comment within one event record.

Continuity

Pending entries can be kept locally and retried when communication returns.

For supervision

Reporting dashboard

Work-order progress, quantities, scrap and downtime.

Filtering

Time, work orders, operators, machines and operation statuses.

CSV export

Selected records can be passed to the next stage of analysis.

Product tour

See the route from terminal to dashboard in 60 seconds.

This short, silent tour shows the operator terminal, reporting dashboard and downtime analysis. All visible information is demonstration data.

01:00No audioReal UI
Download the PDF product sheet

Implementation

You do not need to start with the entire shop floor.

The first rollout can cover one workstation, production cell or operator group. Usability and the value of the recorded data are checked before the scope expands.

  1. DiscoveryMap operations, events, reasons and the information needed by supervisors.
  2. Demo or limited scopeConfigure the terminal and dashboard for the agreed process and user group.
  3. ImplementationAfter reviewing usability and data quality, agree refinements, training and the next scope.
Browser-based terminalThe operator view can run on a touch terminal, industrial PC or suitably prepared tablet.
Separate rolesThe operator uses a focused screen while supervisors work with the reporting dashboard.
Acceptance criteriaThe data scope and pilot evaluation method are agreed before any wider rollout.

FAQ

Questions before the first demo.

Does Shop Floor Time replace a MES or calculate full OEE?

No. It is a focused tool for operator event capture, time registration and practical production reporting, not a complete MES or OEE platform.

What can an operator record?

Setup, production, pauses, downtime, good quantities, scrap and the relevant job, operation, machine and operator context.

What happens if the workstation loses its connection?

Pending entries can remain in a local queue and be retried after communication is restored. Exact offline behaviour is verified during the pilot.

How can managers use the information?

They can review KPIs, filter operational records, inspect downtime and production history, and export selected data to CSV.

Is the product available now?

NCTune Shop Floor Time is in active development. Guided demos and pilot implementations are available for a representative machine, cell or production area.

Contact

Would you like to test production reporting in one real area?

Describe the workstation, operator flow and reporting challenge. We will propose a practical demo or pilot scope.

Contact form

Describe your current reporting flow

A short description of the process and missing information is enough to begin.

When you send the form, you provide data so we can handle your enquiry. Details are available in the Privacy Policy.