Produce · Factory Command
Turn a bill of material into accountable output.
A works order is incomplete if shortages, scrap and finished stock live in separate files.
This is a capability inside Lightning Pharos, not a separate product.
Release a works order from its bill of material.
01 · What ships
The complete working surface.
Works orders against real bills of material.
- 01
Bills of material with component quantities and material-cost estimates
- 02
Work orders and operations with planned production
- 03
Material issue or backflush from Inventory
- 04
Good and scrap quantity reported against the work order
- 05
Quality gates and conditional finished-output movement
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Release a works order from its bill of material.
- 02 / 03
Governed event
Requirements, issues, output, scrap and rework remain tied to the order.
- 03 / 03
Connected result
Finished quantity enters inventory with the production history behind it.
03 · What it needs
Connected by design.
Pharos requires these modules first because the workflow depends on their records. The dependency is enforced in the product.
04 · Where it stops
The boundary is part of the product.
Cost is material-only, not full actual production cost. Labour, conversion cost, OEE, and operation-level yield are not included. Output posting can be blocked after a report and remains visible for recovery.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system