iFactoAppsNL

Shopfloor sessions and Production Employees

🌐 NL · Last reviewed: 27 May 2026

Shopfloor sessions and Production Employees

Shopfloor sessions capture work on the shop floor with start/stop timestamps, linked specs and routing lines, and per-employee timelines. Errors/warnings are optionally logged for auditing.

The session model

Field

Purpose

Shopfloor Session No.

Auto-numbered.

Type + No.

Work Centre or Machine Centre (capacity type).

Date-Time Started / Stopped

Session duration.

Current State

Mobile Production State enum (Started, Stopped, Finished, Paused).

Persons Active

Count of timelines with status Expected.

No. of Spec / Routing / Timeline lines

Derived counters.

Errors / Warnings / Info Messages

Session log per category.

Workflow

  1. Operator opens Shopfloor Session List and starts a session.

  2. DXSteel auto-attaches spec lines and routing lines.

  3. Operator logs time. With Time registration by persons = On, every operator gets their own timeline.

  4. During work: production labels are printed via Print Label.

  5. Operator finishes the session. With errors present, DXSteel blocks the finish.

  6. With Auto Finish Production Orders, the production order auto-closes.

Production Employees + Shopfloor Employees

  • Production Employee β€” link to the BC Employee master.

  • Shopfloor Employee β€” extension record for session assignment.

Session log

Each action within a session creates a log record. Filter by type (Error / Warning / Info) for troubleshooting. Error format: "Error Prod. Order %1, Spec. %2: %3".

Best practices

Enable Log Shopfloor Session in Processing Setup for traceability. Without the log, post-mortem analysis is hard.

For mobile dashboards: sessions provide the data feed for real-time production status. Pair with the Mobile Production State enum.

A session cannot finish while error log records exist. Resolve them first or accept them explicitly.

[Screenshot: Shopfloor session list with active session and per-operator timelines]