Shop floor control patterns in Dynamics 365 Supply Chain Management

Shop floor control is where a manufacturing ERP either earns its keep or gets ignored. If operators can start a job, report quantity, and log scrap in a few taps on a shared tablet, the production data in the system is real and the costing is trustworthy. If they cannot, supervisors key it in at the end of the shift from paper, and the ERP becomes a slightly delayed record of what a whiteboard already knew. Supply Chain Management has a genuine shop-floor layer; this guide covers what it does, how to configure it so operators tolerate it, and where a dedicated MES still wins.

Two ways to feed back production

There are two modes for reporting production in Supply Chain Management, and choosing between them is the first decision.

Journal-based feedback. Supervisors or operators post route card and job card journals for time and quantity, picking lists for material, and report-as-finished journals for output. Simple, no clock-in concept, and no shop-floor terminal. Fine for small operations with few operations per order and a supervisor who owns the data.

Manufacturing execution (the production floor execution interface). Workers sign in on a shared device, see their jobs, start and stop them, register quantities and scrap, and the system computes elapsed time, splits it across parallel jobs, and generates the journals automatically. Costing gets actual labour hours from actual registrations. This is the mode meant by "shop floor control", and it is what the rest of this guide is about.

The production floor execution interface

The current interface is a touch-first, configurable app that runs in a browser on a tablet or a mounted screen at the workstation. Workers badge in with a badge ID or pick their name, and the screen shows the job list for their resource or resource group. Available tabs cover starting jobs, reporting progress, reporting as finished, registering indirect activities such as maintenance or meetings, and viewing job details including attached documents and BOM lines.

Configuration lives in a few places:

• Configurations of the interface decide which tabs and buttons appear per device or per production unit. The strongest advice is to remove everything a station does not need. A screen with four large buttons is used; a screen with twenty is bypassed.
• Calculation parameters and registration workflows on the production parameters and time-and-attendance parameters decide whether multiple jobs can run in parallel on one worker (bundled jobs), whether time is split evenly or by estimate, whether approval is required before registrations are transferred, and how rounding works.
• Production units and resource groups map physical areas to devices, so a worker at the paint line sees paint-line jobs.

What operators register is deliberately small: start, quantity good, quantity scrapped with a reason, finished. Material consumption is usually auto-flushed on start or finish rather than registered by the operator, which is right for most discrete shops and wrong for process shops where actual consumption varies — those use the pick-list registration or a weighing integration.

Time and attendance, and where payroll is not

The same registrations feed the Time and attendance module, which computes worked hours, breaks, overtime, and flex balances against profiles and pay agreements, and produces pay items for export. It is a capable time-capture system for a factory workforce.

What it is not is payroll. Supply Chain Management does not calculate or pay wages. The pay items are exported to a payroll system, and the mapping from pay agreement to that system's codes is an implementation task that takes longer than expected because every union agreement has a special case. If the manufacturer does not need time and attendance for payroll — only for job costing — the module can run in a lighter configuration where registrations are approved for costing but pay calculation is ignored.

Machine data and IoT

Operators are one source of truth; machines are another. The Sensor Data Intelligence add-in ingests IoT signals into Supply Chain Management for scenarios such as machine status, production delays, and quality deviations, and can raise notifications or create records from them. It is a lightweight bridge, not a historian or SCADA system. Manufacturers with serious machine data run it into an industrial platform first and surface only the operationally relevant events into the ERP.

When to use a dedicated MES

Supply Chain Management's shop-floor layer covers execution reporting well. It does not do detailed work-instruction management with revision control at the station, electronic batch records with full 21 CFR Part 11 signature trails, real-time OEE from machine signals, or genealogy at the level regulated industries require. Those are the domain of a manufacturing execution system.

For that case there is a first-party MES integration framework: production orders and their operations are published to the MES, and the MES sends back start, quantity, scrap, material consumption, and finish messages through defined message types and a queue. It means the ERP owns planning and costing while the MES owns execution, without a custom integration. The framework covers the common messages; anything exotic still needs extension work.

The rule of thumb: if the shop needs to know what is running and how much came out, use the built-in floor execution. If the shop needs to control how it is made — instructions, interlocks, signatures, machine parameters — put an MES in front and integrate.

Business Central manufacturers

Business Central has no shop-floor terminal. Output journals, consumption journals, and capacity ledger entries are posted by people, and it works for a shop where a supervisor keys in the day's output. Manufacturers wanting operator-level start/stop, badge sign-in, and a tablet at every station use a shop-floor ISV from AppSource, of which there are several mature ones. Evaluate them on how they post to BC — direct capacity and output entries against production order routing lines is right; a nightly batch of journal lines is a red flag — and on how they handle a job that spans a shift change.

Rollout advice

Pilot on one line with the smallest possible interface. Measure two things: the share of production orders whose actual time comes from registrations rather than estimates, and the gap between reported and physically counted output. When both are stable, add the next line. Manufacturers that switch the whole plant to floor execution on day one with a full-featured screen generally switch it off again by week three.