Shop Floor Execution governs the full lifecycle of a work order on the floor. It receives released orders from planning, explodes their routings into discrete operations, and dispatches each operation to the correct work centre with sequence, priority and scheduled dates. Operators pick up work from live dispatch lists, clock on and off operations, and record quantities completed, scrapped and reworked as they go.

The module drives barcode and scan stations at every material and reporting point: order travellers, operation tickets, material lots, containers and finished units all carry machine-readable identifiers that stations resolve instantly. It maintains a continuous, real-time production status: which orders are running, which are queued, which are held, and what each work centre is doing right now. Labour and machine time are tracked to the operation, work-in-progress is valued as it accumulates, and material is backflushed or issued against consumption. Every reported event updates cost and inventory at the moment it happens, so the floor is never a black box between order release and order close.

At the centre of the model is the work order: the authorisation to make a defined quantity of a product by a defined method. Each work order carries a routing, an ordered set of operations that describe the steps required, the work centre each step runs at, and the standard time each is expected to take. Operations are where execution actually lands, and everything the floor reports attaches to them.

Around operations sit the resources they consume. A work centre represents a station, machine or team with its own capacity, calendar and cost rates. Labour is recorded as the time people and machines spend on operations, while materials flow in as issues and flow out as completed quantities. As operations progress, value accumulates as work-in-progress, a running account of the labour, material and overhead committed to orders that are started but not yet finished. The relationships are simple to state and powerful in combination: orders decompose into operations, operations draw on work centres and material, and the sum of what those operations report becomes the cost of the goods produced and the movement of stock across the site.

The primary flow begins with order release. Planning hands over a firm work order, the module confirms material availability and routing, and the order becomes visible on the dispatch lists of its first operations. Supervisors sequence and prioritise work by centre, balancing due dates against setup and changeover. Operators then execute: they select an operation, clock on, scan the materials they consume, report quantities as they complete them, and clock off. Quantities completed at one operation become the queue for the next, so the order advances through its routing without manual handoff.

Parallel workflows handle the exceptions that define real production. Scrap and rework are reported against operations and routed to disposition, holds stop work at a point and record the reason, and material shortages raise signals back to planning and procurement. When the final operation reports its last good unit, the order completes: finished goods are received into inventory, remaining work-in-progress is cleared, and variances between standard and actual are settled. Throughout, live status boards and station terminals give supervisors and operators the same current picture of the floor.

The value of the module is in the rigour of what it captures and calculates. Labour reporting supports clock-based and elapsed time, multi-machine and multi-operator assignments, indirect and setup time, and the split of a single person's shift across concurrent operations. Time is measured against engineered standards, so the module continuously computes efficiency, utilisation and yield by operation, work centre and order. Overhead is applied by work centre rate, by labour or by machine basis, and absorbed into work-in-progress as operations report.

Costing runs at both standard and actual: the module accumulates actual labour, material and overhead against each order and settles the difference as rate, usage and efficiency variances at completion. Backflush consumption is driven off the bill of materials and completed quantity, with reverse postings when quantities are corrected. Full lot and serial traceability is maintained through every scan point, so any finished unit can be traced back to the specific material lots, operations, operators and machines that produced it, and any suspect lot can be traced forward to everything it touched. Quantity controls, tolerance checks and mandatory inspection gates prevent an order advancing past a step it has not genuinely cleared, and every reported transaction is stamped, attributed and immutable in the audit record.

Shop Floor Execution is the settlement point for the manufacturing side of Nashua 360. It receives released orders and material plans from Production Planning, and returns actual progress, consumption and completion dates so the plan stays anchored to reality. It draws routings, work centres and bills of materials from the engineering records in Product and Bill of Materials, and it issues and receives stock through Inventory and Warehouse Management, updating on-hand balances and locations at every scan.

Financially, the module posts work-in-progress, absorbed overhead and completed cost directly into Cost Accounting and the General Ledger, so period close reflects true production cost with no manual reconciliation. It raises inspection results and non-conformances into Quality Management, signals machine issues to Maintenance and Asset Management, and pushes shortages back to Procurement. Labour flows to Time and Attendance, and every metric it produces feeds Analytics. The result is a floor that is fully integrated rather than islanded, where a single reported event ripples correctly across planning, inventory, cost and the ledger.

AI Workers are first-class participants on the floor, not an overlay. A supervisor queries the module conversationally, asking which orders are behind, which work centre is the current bottleneck, or why an order's cost is running over standard, and the Worker answers from live execution data with the supporting figures. Workers execute actions within their authority: resequencing a dispatch list, placing or releasing a hold, splitting an operation across machines, or reprioritising against a changed due date.

They watch continuously for anomalies and exceptions, flagging efficiency collapses, scrap spikes, stalled operations, and material shortages before they cascade, and they alert the right person with context rather than a bare number. Workers extract structured data from travellers, inspection sheets and supplier documents at scan stations, resolving them into clean transactions. They offer decision support to supervisors, proposing sequences that minimise changeover or recover a late order, and they act as review and approval nodes in execution workflows: signing off scrap dispositions, authorising rework, or clearing an order to complete once every gate and tolerance is satisfied. Their judgements are recorded in the same immutable audit trail as any human action, fully attributable and reviewable.