Shop Floor Tracking (SFT)#

SFT is the runtime record of what’s happening on the shop floor — moving quantity from one operation to the next, logging operators, equipment, and scrap. Every SFT event ultimately updates the WO’s completed quantities and, at final operation, closes out the WO.

Core operation#

An SFT move transfers a quantity from one routing operation to the next (or into scrap / rework). The move records:

• WO number, current operation, next operation.
• Quantity moved, quantity scrapped, quantity to rework.
• Operator (WcOperatorHelper) and equipment (WcEquipmentHelper).
• Timestamp; used for cycle-time / throughput analysis.

ShopFloorTrackingHelper is the entry point. Transfer parameters are packaged in TransferParameters and executed inside a transaction so that per-operation counters, WO completed qty, and equipment / operator logs update atomically.

Serial genealogy#

For serialised assemblies, SerialComponentToAssemblyHelper builds the child → parent link when an operation consumes a serialized sub-assembly. This is the record used later to answer “which units of Product X contained Component Y with serial Z?” — critical for recalls and warranty.

Business rules#

• Every SFT move updates ActvQtyHelper (per-op completed) and DeptQtyHelper (per-dept completed).
• The final operation closes the WO — set OPENCLOS = "Closed" and finalise consumption of kit reservations.
• Scrap goes to a scrap bucket per operation; rework quantity re-enters the routing at the specified rework op.
• Test & repair failures come back through DefectEntryController / TestAndRepairController — they can loop parts back to a prior operation.

Where it lives#