0) Executive Summary

• Mission goal: [1–2 sentences on the payload’s primary objective and success criteria].

• Mission class & context: Secondary payload on a rideshare mission to [orbit], hosted by [bus/deployer] with launch provider constraints.

• Top risks (snapshot): Host ICD change risk; late rideshare manifest changes; export/licensing; EMI/EMC with host; data rate/power shortfalls.

• Key dates: LV environments/ICD freeze; PDR/CDR; payload delivery for I&T; environmental test window; ship to integrator; launch campaign; commissioning; ops end.

1) Scope, Assumptions, and Interfaces

• Scope: End-to-end delivery of a flight-ready payload + EGSE/MGSE, software, procedures, and ops support until decommissioning.

• Assumptions (tailor):

  • Rideshare provides: mechanical envelope, mounting/bolt pattern or deployer spec, LV environments, power/telemetry interfaces (if hosted), mission timeline, export guidance for integration site.

  • Payload class/size: e.g., hosted (bolted to bus) or deployed (e.g., CubeSat/ESPA-class).

  • Data path: S-band/UHF/X-band via host or your ground segment if deployed.

• Primary Interfaces: Launch provider, mission integrator, host satellite provider, regulatory bodies (FCC/NOAA/FAA as applicable), ground segment operator, component vendors.

2) Life-Cycle Phasing & Reviews (Entry/Exit Criteria)

Pre-Phase A — Concept Studies

Objectives

• Establish mission need, stakeholder set, and high-level ConOps; identify rideshare options; rough cost/schedule.
  Artifacts

• Mission Need Statement; Concept of Operations (ConOps); trades (hosted vs deployed, frequency band, ADCS needs); straw-man ICD assumptions; ROM cost/schedule; risk register v0.1.
  Gate/Review: MCR (Mission Concept Review)
  Exit criteria: Selected concept, draft high-level requirements, resourcing for Phase A.

Phase A — Concept & Technology Development

Objectives

• Refine ConOps, define Level 1/2 requirements, close key feasibility risks, pick subsystem architectures, long-lead planning.
  Artifacts

• SEMP (Systems Engineering Management Plan), Stakeholder Expectations, System Requirements (SRD), Initial Verification Strategy (methods: test/analysis/inspect/demo), Preliminary ICD with host/deployer, Risk, Opportunity & Issue (ROIL) Log, Technology maturation plan, Preliminary MEL/PEL, mass/power/thermal/link budgets v1, Safety & Mission Assurance (SMA) plan, Software Plan (standards, IV&V as needed), Cybersecurity tailoring (if hosted data path).
  Review: SRR (System Requirements Review)
  Exit criteria: Baseline requirements; agreed ICD skeleton; V&V approach; Phase B authorization.

Phase B — Preliminary Design & Technology Completion

Objectives

• Mature design to preliminary baseline; confirm interfaces with rideshare; freeze critical parts; place long-lead orders.
  Artifacts

• System/Subsystem Preliminary Design (block diagrams, schematics, models), Preliminary Fault Management / FDIR, Updated ICD (mechanical, electrical, data, EMC), VCRM (Verification Cross-Reference Matrix) v1, Preliminary I&T plan, Configuration Management (CM) Plan, Quality plan & workmanship standards, Safety hazards analysis (PHA/FMEA start), Environmental test plan draft (vibe/acoustic/TVAC/EMI-EMC), Ground segment concept (if deployed), Ops concept & timelines, Long-lead procurement list, Regulatory plan (spectrum, remote sensing).
  Review: PDR (Preliminary Design Review)
  Exit criteria: Preliminary baseline, ICD ≥80% defined, long-lead placed, risks trending down.

Phase C — Final Design & Fabrication

Objectives

• Complete detailed design; release drawings/firmware/software; fabricate EDU/Protoqual/Flight units; finalize procedures & tests.
  Artifacts

• CDR package: detailed CAD/Drawings/BOMs; Schematics & board layouts; Thermal/structural/EMC analyses; Software detailed design (requirements traceability); ICD freeze with host; VCRM v2 (with acceptance criteria); I&T Procedures; Environmental Test Procedures; Safety analyses (FMEA/FTA updates); Ops Products (commissioning timelines, contingency procedures).
  Reviews: CDR → MRA (Manufacturing Readiness Assessment) for boards/mech as needed.
  Exit criteria: Released design; ICD signed; build authorized.

Phase D — System Assembly, Integration, Test, and Launch

Objectives

• Build, integrate, verify & validate; complete environmental tests; deliver to integrator; support LV/host integration; launch & checkout.
  Artifacts

• AIV plan execution; Test Reports (functional, vibe, acoustic, TVAC, EMC), Software qualification reports; As-Built Configuration; Non-conformance & waivers; Logistics & shipping plan; Launch Site procedures; Ground segment readiness.
  Reviews: TRR (Test Readiness), QR/PRR (Qualification/Pre-ship), FRR (Flight Readiness), ORR (Operations Readiness).
  Exit criteria: Flight article delivered & accepted; launch campaign complete; on-orbit checkout successful.

Phase E — Operations & Sustainment

Objectives

• Nominal ops, data delivery, performance monitoring, anomaly resolution, updates/patches (if allowed), reporting.
  Artifacts

• Ops handbook, Anomaly response tree & fault rules, KPIs & performance budgets, Data management plan, Calibration/validation plan (if science payload), Monthly/quarterly status & lessons learned.
  Reviews: MOR (Mission Operations Review), periodic ops reviews.

Phase F — Closeout & Disposal

Objectives

• Execute end-of-life (EOL) passivation/disposing plan per host and regulations; archive data & configuration; finalize lessons learned.
  Artifacts

• EOL report, Data archive (formats, DOIs as relevant), Final performance assessment, Lessons Learned.

3) Systems Engineering Management (SEMP) Content (Tailored)

3.1 Technical Baseline & Requirements

• Hierarchy: L1 mission goals → L2 payload system requirements → L3 subsystem specs.

• Quality of requirements: unique, verifiable, bounded (with margins).

• Budgets: mass, power (peak/avg), thermal, data rate/volume, pointing/jitter, environments, EMC, reliability.

• Margins: define by phase (e.g., mass +20% Phase A → +10% Phase C; power +30% → +20%; thermal headroom; link margin ≥3 dB unless justified).

• ICD: mechanical envelope, keep-out zones, CG/CM, fasteners; electrical (power profile, inrush limits, grounding/bonding, discrete/serial/ethernet links); data (protocols, packet definitions, timing); EMC/EMI limits; thermal interfaces; optical/RF interfaces; handling/cleanliness.

3.2 Architecture & Design

• Trade studies: COTS vs custom; ADC/DAC precision; SDR vs fixed RF; onboard processing vs ground; harness vs backplane; materials/thermal straps.

• Reliability & FM: FDIR states, safe-mode entry/exit, watchdogs, brownout/over-current responses, single-event mitigation (TMR, EDAC), redundancy philosophy (cold vs warm).

• Software & FPGA: standards (coding, reviews, unit/integration tests), requirements traceability, CI builds, static analysis, hardware-in-the-loop (HIL).

3.3 Verification & Validation (V&V)

• Methods: Test (T), Analysis (A), Inspection (I), Demonstration (D).

• VCRM: Each requirement mapped to V-method, environment, level (unit/board/subsystem/system), success criteria, witness/sign-off.

• Qualification approach: Proto-qual (if one-off) vs qual + flight lot.

• Environments (tailor to LV/host): random vibe, sine burst, acoustic, shock/pyro, TVAC, EMI/EMC (conducted/radiated, susceptibility), deployable tests, burn-in, leak tests, cleanliness.

• Functional: end-to-end under worst-case power/thermal; latency; data throughput; fault injection; software timing.

3.4 Integration & Test (I&T / AIV)

• Flow: unit → subsystem → system HIL → environmental → re-test → acceptance.

• Facilities & EGSE: power supplies with inrush limiting, comms front-ends, data recorders, RF chambers, TVAC chamber, vibe table, clean area.

• Configuration control: as-designed vs as-built; serialized parts; waiver/deviation board.

• Readiness gates: TRR entry criteria (procedures released, calibration valid, NCR process active), FRR criteria (all tests closed or dispositioned).

3.5 Safety, Mission Assurance, & Cyber

• Hazards analyses: PHA → FMEA → FTA; mitigations verified.

• Workmanship & quality: soldering standards, torque logs, ESD/cleanliness, lot acceptance for EEE parts.

• Cybersecurity (hosted payloads especially): interface threat model, authentication/command protection, supply-chain controls.

• Export/ITAR/EAR & site rules baked into integration schedule.

3.6 Project Management

• WBS & Org: SE, Payload HW, Payload SW/FPGA, AIV, SMA, Ops, Ground, Regulatory, Supply Chain.

• RACI: see sample below.

• Schedule logic: pin rideshare ICD freeze and delivery for integration as immovable anchors; set long-lead procurement backward from CDR; hold risk buy-downs before PDR.

• Cost & reserves: phase-dependent; carry hardware, schedule, and technical reserves; keep management reserve for rideshare slips.

• Comms & reviews cadence: weekly IPTs; monthly technical/management reviews; risk board biweekly.

4) Rideshare-Specific Planning

• ICD Lockpoints:

  • T-L ~ CDR-1 month: Mechanical envelope, mounts, CG/CM, mass allocations.

  • T-L ~ CDR: Electrical & data pinouts, power profiles (inrush/peak/average), EMI/EMC limits, grounding.

  • T-L ~ FRR: Final procedures, handling, cleanliness, labeling, shipping & site access.

• Regulatory/Licensing (as applicable): frequency/spectrum (FCC/NTIA), remote sensing (NOAA), debris assessment & disposal, export licenses for integration country.

• Host/Deployer Constraints: keep-alive currents, inhibit requirements, battery shipping rules, commanded operations windows, contamination control (optics/RF).

• Contingency: manifest change, late ICD changes, reduced power/data allocation, integration day anomalies → pre-approved waivers and fallbacks.

5) Budgets & Margins (living documents)

(Tailor margins to your center/host standards.)

6) Verification Cross-Reference Matrix (VCRM) — Skeleton

7) I&T Flow (high level)

1. Unit functional → 2. Subsystem functional + HIL → 3. System functional

2. EMI/EMC pre-screen (optional but recommended)

3. Environmental qual (vibe/acoustic/shock → TVAC → EMC)

4. Final functional & workmanship inspection

5. Pre-ship review (PSR) → Ship to integrator

6. Host fit-check → Interface tests → FRR → Launch site ops

8) Ground Segment & Operations (Phase E)

• LEOP/Commissioning plan: timelines, stepwise power-on, RF checks, thermal stabilization, initial data take.

• Nominal ops: pass plans, autonomy rules, duty cycles vs host allocations, data downlink & processing.

• Contingencies: comm loss, latch-ups, power brownouts, safe-mode; return-to-service procedures.

• Performance monitoring: trending of power/thermal/data, alert thresholds.

• Configuration control in ops: versioned procedures, command loads, patch policy (if applicable).

9) Regulatory, Export, and Safety

• Spectrum: licensing, frequency coordination, call signs, emissions masks, ITU filings (if applicable via provider).

• Remote sensing (if imaging): NOAA licensing & data policy.

• Debris & disposal: match host plan; for deployables, deorbit lifetime & passivation.

• Export/ITAR/EAR: part lists, integration site licenses, shipping paperwork timeline.

• Site safety: ESD/cleanliness, batteries/pressurant rules, payload hazards closure.

10) Risk, Opportunity & Issue Management

Likelihood (L) × Consequence (C), 5×5 matrix; risk burn-down reviews biweekly.

11) Configuration & Data Management

• CM: single source of truth (PLM or repo); drawing/BOM release at CDR; as-built EIDPs.

• Change control: CCB with SE/SMA/PM; deviations/waivers tracked.

• Data management: test data schemas, calibration files, ops data retention & public release (if applicable).

12) Team, WBS, and RACI (sample)

Core roles: PM, SE, EE, ME, Thermal, RF/Comms, SW/FPGA, AIV Lead, SMA/QA, Regulatory, Ops, Supply Chain.

(R=Responsible, A=Accountable, C=Consulted, –=None)

13) Schedule Backbone

14) Deliverables Checklist by Review

SRR: ConOps, SRD, ICD v0.5, SEMP, Budgets v1, V&V strategy, Risk Log v1, SMA plan, Software plan, Regulatory plan.
PDR: Preliminary design package, ICD v0.8, VCRM v1, I&T plan draft, Environmental plan draft, FMEA/PHA, Long-lead list, Updated budgets, Config & QA plans.
CDR: Released drawings/BOMs, Software detailed design, ICD v1.0 (signed), Test procedures, VCRM v2 with acceptance criteria, Safety updates, Manufacturing plans.
TRR: Test procedures approved, calibrated EGSE, configs frozen, hazards closed to test.
FRR/PSR: All test reports with closures, NCRs dispositioned, as-built EIDP, shipping plan, site procedures, operations handbook draft.
ORR: Commissioning procedures, anomaly rules, ground readiness, data pipeline validated.

15) Immediate Next Actions (you can start these today)

1. Draft one-page ConOps (user goals, timelines, operating modes).

2. Start ICD assumption sheet from host/deployer datasheets (envelope, power, data, EMC).

3. Stand up risk log and budget workbook (mass/power/thermal/data).

4. Create SEMP v0.1: org/RACI, review calendar, V&V philosophy, CM & QA, regulatory path.

5. Identify long-leads (radiation-tolerant parts, precision optics, custom PCBs, HV supplies).

6. Put hard anchors on the schedule: ICD freeze date, DDI (delivery), FRR window.