Architecture Demo · Turion Space · May 7 Presentation

Sales decides who + when.
Engineering decides what.
NetSuite ties both to a satellite.

A working illustration of the four-system architecture for SAT-001. Click into any of the four product views below to see how each system holds its piece of the truth · then how it lands in NetSuite for planning, manufacturing, and revenue.

$147.5M
Contract value
7
CLINs
93
BOM lines
8
Subsystems
76%
ITAR-controlled
32 wk
Critical path
☁ Salesforce

Customer · Contract

Who decides + when + how much
  • Account · government / defense customer
  • Opportunity · Andromeda Production Award
  • Contract · TUR-FFP-2024-001 · $147.5M FFP
  • 7 CLINs · PDR · CDR · LL Procure · Build · AI&T · Launch · Ops
  • 5 CDRLs · monthly progress · risk · subcontractor · test plans
Open Salesforce Account →
→
SF→NS Connector
⬢ Arena PLM

Engineering BOM

What gets built
  • Item Master · part numbers · revs · AML
  • Multi-level BOM · 8 subsystems · 85 components
  • ECO orchestration · disposition strategies
  • ITAR workspace · technical-data control
  • Documents · drawings · specs · ICD · budgets
  • QMS workspace · NCR · CAPA · audits · AS9100
Open Arena PLM →
→
Arena Connector
◆ NetSuite · CRM Side

Customer · Sales Order

Receives Salesforce demand
  • Customer · synced from SF Account
  • Sales Order · 7 CLINs as line items
  • Project · PROJ-ANDROMEDA-SAT-001
  • ARM · ASC 606 · 7 performance obligations
  • EVMS · CPI 1.04 · SPI 0.97
Open Customer + SO →
→
MRP demand
◆ NetSuite · Manufacturing

MRP Plan · SAT-001

When + how much to procure
  • Item Master · synced from Arena
  • ~50 planned POs · longest lead first
  • 4 planned WOs · sub-assy + final integ
  • Critical-path Gantt · 32-wk thruster + telescope
  • Action messages · Expedite / Release / Future
Open MRP Plan →
↓
WO release
⬛ MES · placeholder · vendor TBD

Shop floor · production stages · operator capture

Who built it · which serial · what they captured · NCR loop
  • 9 production stages · receiving → ship to launch
  • Operator capture · cert · station · time on op
  • Materials traceability · serial back to PO + AML MFR
  • In-process tests · torque · alignment · pass/fail
  • Genealogy tree · SN-001 → components → POs
  • NCR loop → Arena QMS · CAPA + ECO trigger
Open MES shop-floor view →
↑
WO complete + NCR

End-to-end workflow · interactive demo

🎬
Live walkthrough · 10 steps
Create new Sales Order → Final build & acceptance
Watch one opportunity flow through the full architecture: Salesforce form → SF→NS sync → NS SO + Project + ARM → MRP run → 50 POs released to vendors via EDI 850 → vendor accounts updated → 3-way match → financials reflect → MES build (9 stages) → DD-250 acceptance → revenue recognition → invoice issued. Auto-play option shows the full flow in 45 seconds.
▶ Start workflow

NetSuite modules · 7 functional walk-throughs

The two NS panels above are the entry points. Below is every NS module that participates in the SAT-001 lifecycle — each is a complete, clickable mock of what that screen looks like in NetSuite for an aerospace ETO manufacturer running an FFP contract.

01

Customer · Sales Order

SF→NS landing zone
  • Customer master · DPAS · CMMC · ITAR flags
  • SO with 7 CLINs as line items · $147.5M
  • CDRL tracking · 5 deliverables
  • SF reconciliation · daily cron
Open →
02

Items & Inventory

Arena→NS landing zone
  • Item master · synced from Arena PRT-IDs
  • Lot/Serial tracking · 4 BCT serials live
  • Bin locations · ITAR access logged
  • Where-used · 3 BOMs · AML · ECO history
Open →
03

Procurement

Vendors · POs · 3-way match
  • PO drilldown · BCT $729.6K · 3-way ✓
  • Vendor master · 8 ITAR/DPAS qualified
  • RFQ pipeline · 3 active
  • OTD scoring + qual record cross-ref
Open →
04

MRP / Work Orders

Demand explosion · WO release
  • ~50 planned POs · long-lead first
  • 4 planned WOs · sub-assy + final integ
  • Critical-path Gantt · 32-wk PROP/PAY
  • Action messages · Expedite / Release
Open →
04a

Demand Planning

SF pipeline → forecast → MRP
  • 24-mo rolling forecast · $248M weighted
  • SF pipeline · 8 opps · prob-tier mapping
  • Long-lead release rules (lead × confidence)
  • Pooled demand · 62 of 93 items
Open →
05

Project · EVMS

CFO/CIO killer screen
  • EVMS dashboard · BAC $116.2M
  • CPI 1.04 · SPI 0.97 · TCPI 0.99
  • WBS · 4-level cost-loaded
  • S-curve · variance narratives · CDRL A001
Open →
06

Revenue Mgmt (ARM)

ASC 606 recognition engine
  • 7 performance obligations · distinct test PASS
  • 4 methods · point-in-time / CtC / U-of-P / stand-ready
  • 9 recognition events · $31.68M YTD
  • 3-way recon · obligations ↔ billings ↔ GL
Open →
07

Financials

AR · AP · GL · period close
  • Period 2026-04 close · 16-step checklist
  • Trial balance · DR=CR ✓ · $84.2M
  • Project P&L · gross margin 54.2%
  • 5 cross-system reconciliations
Open →

Two integration boundaries · what each connector moves

1 · Salesforce → NetSuite

CRM → Financial / Project
  1. SF Account closed-won → NS Customer record (idempotent on Account ID)
  2. SF Opportunity → NS Sales Order with CLINs as line items
  3. SF Contract → NS customrecord_contract (FFP terms preserved)
  4. SF CLIN schedule → ARM revenue arrangements per performance obligation
  5. SF CDRL → NS Project Tasks with due dates
  6. SF Period of Performance → SO need date drives MRP demand
  7. NS PO release (EDI 850) → Vendor Portal · vendor accept/counter/reject (EDI 855) flows back

2 · Arena → NetSuite

Engineering → Financial / MRP
  1. Arena Item Master → NS Item record (idempotent on part-number)
  2. Arena Multi-level BOM → NS Bill of Materials (effectivity respected)
  3. Arena AML → NS Vendor list with preferred-vendor flag
  4. Arena ECO release → NS customrecord_eco with disposition
  5. Arena Routings → NS Manufacturing Routing + MES traveler
  6. Arena Documents → NS Item URL refs (ITAR access inherits)
  7. Arena QMS NCR → MES NCR record + supplier scorecard
  8. Arena QMS CAPA → linked to Arena ECO + tracked through to next-build verification
⚠ Anti-hallucination caveat (carried through to all four views). Every customer name, contact, contract value, CLIN allocation, part number, manufacturer, and lead time is illustrative · drawn from public smallsat patterns + FAR Part 15 contract conventions. NOT Turion's actual data — Turion swaps in real values at implementation. The architecture (4-system topology · 2 integration boundaries) holds regardless of which specific values populate it.
Prepared by Jithesh Manoharan · jeetnair.in@gmail.com · For Thursday 7 May 2026 architecture review