sub-modules
Shop Floor
Paper travelers end here — the order carries everything, the scan proves it.
Paper travelers lie: coffee-stained, outdated, initialed by whoever was nearest. Shop Floor replaces the packet with the order object itself — BOM snapshot, routing, quality checks, labor, and materials in one place, proven by scans at every step. What the operator sees is what engineering released, and what closes is what finance books.
Order lifecycle
Each stage below commits into the same order object — release through close with nothing tracked on the side.
data Viz
data View
section: stages
Release
Orders release with BOM and routing snapshots pinned, materials reserved, and operations sequenced with dependencies. Effectivity governs which revision applies.
Execute
Operations start, report time, consume materials, and record quality results with operator identity. Splits and merges preserve genealogy across resulting units.
Close
Completion posts costs to finance and updates inventory in one transaction. Yield, scrap, and OEE feed BI immediately with the evidence behind every number.
Execution guarantees
- Snapshot binding
- Released BOM and routing revisions pinned for the order lifetime
- Complete capture
- Operations, materials, labor, quality, and cost in one object
- Unbroken genealogy
- Serial and lot lineage preserved across splits, merges, and rework
- section
- capabilities
Execution by industry
Floor execution bends per industry — same order object, different quality and traceability stakes.
data Viz
data View
section: industries
Automotive and Aerospace
PPAP-linked operations with first-article evidence, SPC checks, and full genealogy for recall scope queries answered in seconds.
Food and Pharma
Batch records with recipe control, in-process checks, and deviation handling. Electronic signatures gate release steps per 21 CFR expectations.
Electronics
SMT lines with reel traceability, test-result linkage per unit, and failure analysis feeding back into process parameters.
Shop Floor questions
Section 1
How is scrap accounted for?
Scrap and rework record against the operation with reason, quantity, and cost impact. Yield analytics update immediately and flow to costing and planning.
Section 2
Can operations run out of sequence?
Only where the routing permits overlap or the supervisor authorizes a governed deviation with reason recorded. Dependencies otherwise gate start until predecessors complete.
Section 3
What about our veteran operators who know the job by heart?
Their knowledge becomes routing data instead of retiring with them. Veterans validate the standards once; every shift after that runs at veteran quality.
data View
section: faqs
content section
value: Completion is a single boundary: operations, materials, labor, quality, and cost commit together or not at all. Split and merge preserve genealogy across every resulting unit.
Section 6
Operation-level tracking with time capture and dependencies
Section 7
Material issue, return, consume, and backflush with genealogy
Section 8
Quality checks, scrap, rework, and yield analytics
Section 9
Serial and lot traceability from component to finished unit