NS creates SO + Project · drives MRP demand signal
The new SO is now a manufacturing demand on item SAT-002. The linked Project record begins accruing costs and CPI/SPI tracking. ARM auto-allocates the price across ASC 606 performance obligations.
MRP reads the SAT-002 BOM (synced from Arena PLM) and explodes it against the new demand. For each component: need_date − lead_time − safety = PO release date. Long-lead components are flagged first.
BOM lines exploded
93
8 sub-assemblies + 85 components
Planned POs
~50
long-lead first
Planned Work Orders
4
3 sub-assy + 1 final integ
Critical path
40 wk
PROP thruster + PAY telescope
Action messages
Release: 14
Future: 36 · Expedite: 0
⚙ MRP Algorithm (this is what just ran):
for each component in BOM_explosion(SAT-002, qty=1):
need_date = LRD - assembly_buffer (12 weeks for sub-assy + final integ)
po_release_date = need_date - lead_time - safety_2_weeks
if po_release_date < today + 30: release immediately
elif po_release_date < today + 90: schedule for release
else: future plan
generate planned POs sorted by lead time descending
Buyer reviews + approves planned POs · NS transmits via EDI 850 to each vendor. Each PO is unique · DPAS-rated · ITAR-flagged. Vendors send back EDI 855 acknowledgments.
Each vendor receives the PO · sends EDI 855 acknowledgment. NS auto-matches the ack to the PO · updates status to "Open · Acknowledged". Vendor account YTD spend reflects new committed amount.
Each ASN triggers a receiving event. Receiving + QA (2-person rule for ITAR) record serial numbers · run incoming inspection · route to appropriate bin (cleanroom, ITAR cage, kitting). 3-way match runs automatically.
Financials reflect across AR · AP · GL · Project P&L
Vendor bills post against received POs. AP increases · cash projections update · project costs accumulate. ARM begins recognising revenue (cost-to-cost on long-lead). EVMS dashboard updates with new actuals.
WO released to MES · build progresses through 9 stages
When all materials arrive, NS releases the WO to MES. Operator clocks in · executes traveler ops · captures torques + serials + tests. NCRs flow back to Arena QMS. Each stage close-out triggers ARM recognition (units-of-production for CLIN-004).
A new opportunity created in Salesforce flowed through 10 systems / events to deliver a satellite. The architecture maintained traceability from contract value → BOM → POs → serials → build → revenue. Every dollar billed traces back to a specific contract milestone. Every part installed traces back to a specific PO. Every NCR traces back to ECO/CAPA in Arena.