Pilot SOW

10 / 11

Engagement shape

Pilot SOW (draft)

A concrete first slice you can accept, fund, and run — with live portal shells already on the account.

Pilot statement of work (draft)

On-prem MD Hub install for Orbital Composites. MD Hub stands up the stack; Orbital owns day-to-day ops with on-call support. First slice: ML pathing/collision loop scaffold plus one internal app path proven on the portal grid.

In scope

Bootstrap on Orbital infrastructure; identity; three portal shells; path/collision data plane (ingest → train/infer jobs → review UI); documentation and hand-off.

Out of scope (phase 1)

Full FEA productization, production VLM defect models, warehouse WMS depth, and a forced rewrite of Orbital UI.

Owners

Orbital: cell data samples under NDA, IT path, domain process knowledge.
MD Hub: install plan, portal/app plane, job plane, on-call.

  • Deliverable AOn-prem hub online with Orbital operators able to sign in and open internal portals.
  • Deliverable BPath/collision loop: sample data pack → job run → review screen with audit trail (scaffold, not final domain model).
  • Deliverable COne production-bound app path chosen from monitor, Orbital UI host, or BD portal.
  • Success checkOrbital can operate day-to-day without MD Hub on the keyboard; support is on-call; IP stays on-prem.
BackNext