Kickoff: What's the True North?

• In one sentence, how would you describe this mission’s primary purpose?
• Which of the following best captures the mission’s top business or program driver? Options: Revenue generation / service rollout, Technology demonstration / maturation, Compliance or national security requirement, Constellation scale / cadence, Science or data quality priority, Other
• What orbit or operational environment do you expect the bus and payload to operate in? Options: LEO (incl. SSO), MEO, GEO, HEO / Molniya, Cislunar / Lagrange, Other / hybrid
• Which on‑orbit performance metrics will determine whether this mission is meeting expectations? (Select all that apply) Options: Pointing accuracy, Data throughput (Mbps/Gbps), Sensor resolution / revisit, Availability / uptime, Lifetime (years), Delta‑V / maneuver capability, On‑orbit power margin, Thermal stability
• Do you currently have a fixed launch window or a target range? Options: Fixed, date committed, Target window but flexible ± weeks, Target quarter or year, No launch window yet
• If the launch date is constrained, briefly describe the driver (regulatory milestone, customer contractual date, constellation schedule, investor expectations, etc.).

If Timing Is Destiny, What's Your Dealbreaker?

• What single schedule failure would force you to pause, re-scope, or cancel the program?
• How firm are your internal gate milestones (SRR, PDR, CDR, Test Readiness)? Options: Hard dates (no slip allowed), Mostly firm (minor adjustments OK), Flexible within a range, Not yet defined
• What magnitude of slip is tolerable before cost or customer commitments are materially impacted? Options: Less than 4 weeks, 4–12 weeks, 3–6 months, More than 6 months
• Which downstream partners would be most affected by a schedule slip? (Select all that apply) Options: Launch provider, Ground segment / ops, Payload supplier(s), Insurance underwriters, End customers / service providers, Investors / program sponsors, Government customers / agencies
• Describe the most painful consequence a schedule miss would create for your stakeholders (cost, lost revenue, regulatory penalty, reputational risk, etc.).

What Are You Quietly Worried We Won't Ask?

• What technical or organizational risk do you fear vendors routinely overlook—one that keeps you up at night?
• How mature is your payload at the interface level (concept, EM, QM, FM, interface control document ready)? Options: Concept / early requirements, Engineering model (EM) stage, Qualification model (QM) stage, Flight model (FM) ready, ICD and harnesses finalized
• Which of these supplier or supply-chain vulnerabilities concern you most? Options: Single‑source parts, Long lead cryo/propulsion items, Export controls / ITAR, Obsolete components, Long test shop queues, Geopolitical disruption
• What heritage or test evidence do you insist on seeing before you’ll feel confident in a bus provider? Options: Flight history on similar buses, Full environmental test reports, Failure mode analyses, In‑country operator references, Raw telemetry / anomaly logs, Other
• How long have you been tolerating the current level of that risk, and what have you tried so far to mitigate it?

What's the Hard Limit vs. the Negotiable Trade?

• Which requirements are absolutely non‑negotiable—even if they raise cost or extend schedule?
• From this list, select what you consider hard limits for this program (select all that apply). Options: Launch date, Budget ceiling, On‑orbit lifetime, Specific performance metric (e.g., throughput), Data rights / IP, National security compliance
• How would you rank your tolerance for trading schedule versus capability (1 = prioritize schedule, 5 = prioritize capability)? Options: 1, 2, 3, 4, 5
• Who in your organization must approve any trade between cost, schedule, and performance? Options: Program manager, Chief Engineer / CTO, Procurement Director, Finance / CFO, Executive sponsor / CEO, Government contracting officer
• If pressed to choose one trade the program could accept without breaking mission value, what would it be?

How Will Integration Really Feel Day-to-Day?

• Where do you expect the most friction between your payload engineers and our bus integration team?
• Which of these integration-readiness items are already in-hand from your side? Options: Mechanical ICDs and harness drawings, Thermal models and budgets, Electrical interface definitions, Flight software integration plan, EM/QM hardware available for fit checks
• What level of access to our facilities and teams would your engineers need during integration? Options: Full cleanroom access and onsite days, Remote collaboration with periodic site visits, Dedicated co‑located integration team, No onsite access—data only
• How would you like technical decisions and change requests to be governed during integration? Options: Formal change control board, Integrated product team with weekly signoff, SPOC escalation process, Ad hoc technical swaps
• What deliverables or evidence will you require to accept key milestones (SRR/PDR/CDR/Test Readiness)?

Who's Holding the Keys—and Where Do They Live?

• If stakeholders disagree mid-program, whose decision is final—and what happens to the schedule and budget when that authority is exercised?
• Which stakeholder groups must be actively involved in milestone approvals for this program? (Select all that apply) Options: Systems engineering, Payload prime, Procurement / legal, Finance, Program sponsor / executive, Mission ops / ground segment, External regulator / agency
• Who will be the primary commercial signatory for delivery, acceptance, and warranty? Options: Procurement Director, Program Manager, Head of Contracts, Legal / Compliance, External contracting officer
• What level of on‑orbit warranty and anomaly support do you expect (select the closest)? Options: Basic handover docs only, Limited warranty (launch + short ops), Standard multi-year warranty with remote support, Comprehensive SLA with on‑call anomaly investigation
• How do you prefer escalation to be handled when a technical or commercial impasse arises? Options: Tiered internal escalation (PM → Exec), Joint governance board, Independent arbitration clause, Rapid war‑room with all parties

If Success Was a Story, How Would You Tell It?

• Describe a headline, internal memo, or customer quote that would prove this mission succeeded—what does it say?
• Which of these metrics would you use to publicly or internally celebrate success? (Select all that apply) Options: On‑orbit telemetry matching requirements, Launch on promised date, Revenue or service availability targets, Ground segment handover without anomalies, Mission lifetime achieved or exceeded, Zero critical failures
• What operational or business benefits do you expect in the first 12 months post‑launch?
• How should we capture lessons learned and continue the partnership after delivery? Options: Formal lessons learned workshop, Shared living document / channel, Quarterly ops reviews, Ad hoc debriefs as needed
• What ongoing support or capability improvements would make you consider us a long‑term partner rather than a one‑off supplier?

Decision & Next Steps: What Would Make This Easy?

• What is the smallest, lowest‑risk next step that would get both teams aligned and moving forward?
• Which of these immediate actions would you find most useful to progress toward a decision? (Select up to three) Options: Site visit to cleanroom and test facilities, Access to flight heritage data room, Joint preliminary bus/payload interface workshop, Draft commercial term sheet / LOI, High‑level schedule & cost model, Independent technical assessment
• What timeline does your organization have for making a commitment or selecting a prime manufacturer? Options: Immediate (weeks), This quarter, In 3–6 months, 6–12 months, Longer / undecided
• Are there any internal approvals, procurement rules, or compliance steps we should anticipate before you can proceed? Options: Internal technical review board, Independent heritage assessment, Budget signoff / CFO, Government procurement rules, Security / export review, None of the above
• Who is the best single point of contact for next steps, and what mode of collaboration do you prefer (workshop, video workshop, written proposal)? Options: Workshop on site, Interactive virtual workshop, Written proposal and CAD/ICD exchange, Hybrid (onsite + remote)

• Current State & Consequence Alignment
• Define Future-State Outcomes & Acceptance Criteria
• Architecture Mapping: Bus & Modular Payload Fit
• Delivery Cadence, Schedule Mapping & Risk Controls
• Integrated Solution Experience Review (Diagnosis → Proof → Validation)

• One-line Re-statements
• Seller to prepare an initial mapping template linking consequences to potential architectural mitigations.
• Identify and confirm stakeholders who must validate metrics and sign decisions in subsequent meetings.
• Recap Current State & Consequences
• A customer-validated one-sentence future state describing the desired operational outcome.
• A prioritized list of outcomes tied to measurable acceptance criteria and evidence.
• Clear validation and sign-off responsibilities for each criterion.
• Seller to produce a Future-State Summary document (one-sentence future state + prioritized outcomes + acceptance criteria).
• Customer to confirm validators and escalation contacts for each acceptance criterion.
• Both parties to review and annotate acceptance criteria against SRR/PDR/CDR milestones.
• Recap Accepted Outcomes & Technical Mapping
• An agreed delivery cadence and milestone plan aligned to customer launch constraints.
• Documented contingency plans for top slip scenarios with owners for mitigations.
• Defined governance and change-control triggers tied to acceptance gates.
• Seller to deliver a draft master schedule with floats, critical path, and contingency actions within 3 business days.
• Customer to confirm hard launch window dates and any immovable program constraints.
• Both parties to nominate governance representatives and circulate the change-control process for sign-off.
• Single-sentence Recap (State, Consequence, Future)
• Customer explicitly validates (or rejects with reasons) that the proposed solution delivers the defined future state.
• All acceptance criteria are either validated or have assigned conditional actions with owners and dates.
• Mutual agreement on whether to advance to the Solution Scope stage and list required artifacts for that handover.
• Seller to compile and deliver the final Evidence Package and Architecture-to-Outcomes matrix for archival and contractual reference.
• If conditional validations exist, assign owners and delivery dates for each condition before Solution Scope kickoff.
• Schedule the Solution Scope kickoff meeting with confirmed attendees and pre-read materials within agreed timeline.
• A validated mapping between bus architecture elements and prioritized customer outcomes.
• A clear list of technical gaps, with mitigation options and estimated schedule/cost impact.
• Customer confirmation on which heritage/proof items are sufficient and which need further evidence.
• Seller to produce an Architecture-to-Outcomes matrix linking each bus feature to acceptance criteria and evidence.
• Customer to supply missing payload interface details and priority variants within 5 business days.
• Jointly schedule focused technical follow-ups for any unresolved gaps (CBE/EM/IFR questions).
• Introductions & Meeting Objective
• A single, customer-validated one-sentence current state is recorded.
• Consequences are quantified with numbers or ranges enabling urgency.
• Agreement on 3–5 success metrics and required evidence for later validation.
• Pre-work artifact list and owners are confirmed to enable follow-on sessions.
• Customer to deliver one-sentence current-state and a concise consequences spreadsheet (cost/schedule/risk) within 3 business days.
• Scenario Walkthrough (Diagnosis → Proof)
• Proposed Delivery Cadence & Rationale
• Customer One-Sentence Current State
• Bus Architecture Walkthrough (Outcome-focused)
• Draft One-Sentence Future State
• Map to Customer Launch Windows & Constraints
• Modular Payload Accommodation Mapping
• Outcome Breakdown & Prioritization
• Consequence Quantification
• Evidence Package Review
• Technical Proof Points & Evidence
• Define Acceptance Criteria & KPIs
• Risk Scenarios & Contingency Plans
• Customer Validation Drill-Down
• Stakeholder Impact Map
• Validation Check & Sign-off Path
• Gap Identification & Mitigation Options
• Decision & Next Steps
• Agreement on Success Metrics & Evidence
• Governance, Change Control & Acceptance Gates
• Validation Exercise
• Validation & Agreement on Next Milestone
• Confirm Pre-work & Next Steps

• Assemble flight spacecraft bus
• Integrate payload to spacecraft bus
• Install and qualify propulsion subsystem
• Install and qualify electrical power subsystem
• Install and qualify attitude determination and control system
• Integrate command-and-data-handling avionics
• Load and validate flight software
• Perform thermal vacuum environmental testing
• Perform vibration and shock qualification testing
• Conduct electromagnetic compatibility and RF testing
• Integrate launch vehicle adapter and separation system
• Ship spacecraft to launch site with cleanroom packing
• Deliver ground support equipment and spares kit
• Execute early orbit commissioning and checkout

Assemble flight spacecraft bus

• Which spacecraft class applies to this program? Options: Smallsat (<500 kg), Smallsat-Medium (500-1,500 kg), Large (>1,500 kg), Custom / Other
• Do you require a baseline (flight-proven) bus configuration or a customer-unique/customized bus? Options: Baseline flight-proven configuration, Customer-customized configuration, Hybrid (baseline + customer mods)
• What is the target delivery milestone/date for the assembled bus to support PDR/CDR/test milestones?
• Which factory acceptance / verification activities must be included prior to payload handover? Options: Mechanical fit-check, Mass & CG report, Power-on functional test, Thermal balance run, Full QA inspection
• Who will own configuration control and CCB decisions for bus hardware changes? Options: Manufacturer owns, Customer owns, Joint agreement (define in contract)
• Are there export control, ITAR/EAR, or special handling constraints that affect assembly or personnel access? Options: Yes, No

Integrate payload to spacecraft bus

• What type of payload(s) will be integrated (select all that apply)? Options: Imaging (EO), Communications / RF, Science / Sensors, Hosted experiments, Other (describe)
• What mechanical interface standard and preservation features are required (e.g., separation ring, adapter, bolt pattern, mounting face)? Options: Standard interface (provide spec), Custom interface (drawings will be provided), Using payload-provided adapter
• Describe the electrical and data interface requirements (power voltages, harnessing, protocols such as SpaceWire, RS-422, Ethernet, custom) and any hard constraints.
• When will flight-ready payload deliverables (mechanical drawings, harness pinouts, flight units) be available for integration planning? Options: Already available, T-6 months, T-3 months, To be defined
• Are there cleanliness, contamination, or handling requirements from the payload owner (e.g., ISO class, witness samples, humidity limits)? Options: Yes - specify, No
• Who is responsible for mass properties, acoustic/PC acceptability, and payload-level environmental testing prior to handover? Options: Customer, Manufacturer, Joint

Install and qualify propulsion subsystem

• Which propulsion technology is required for this mission? Options: Chemical (mono/bi-propellant), Electric propulsion (ion/Hall), Cold gas / reaction control, Hybrid / Other
• What propulsion performance requirements drive scope (delta-V budget, thrust levels, Isp, maneuver frequency)?
• Are there propellant loading, ground fueling, or hazardous materials (hazmat) controls that must be managed at assembly or launch site? Options: Manufacturer manages fueling, Customer manages fueling, Launch provider handles fueling, Yes - special controls required
• What qualification level is required for the propulsion system prior to flight (flight heritage, qualification test campaign, protoflight)? Options: Flight-proven heritage only, Qualification + acceptance testing, Protoflight approach
• Is propulsion subsystem acceptance tied to specific verification milestones (e.g., SRR/PDR/C DR/Test Readiness)? Options: Yes - specify milestones, No - standard flow
• Who will retain responsibility for anomaly investigation, long-term storage or propellant handling post-delivery? Options: Manufacturer, Customer, Launch provider, Joint

Install and qualify electrical power subsystem

• What is the expected average and peak power demand profile for nominal operations and worst-case scenarios (W)?
• Which power-generation and storage technologies are required or preferred (solar arrays type, deployable vs fixed, battery chemistry)? Options: Rigid solar arrays, Deployable solar arrays, Lithium-ion batteries, Ni-based batteries, Other
• What end-of-life power margin and redundancy level are required (e.g., N+1, dual string)? Options: Single string, N+1 redundant, Fully redundant dual-string, Custom
• Which qualification and acceptance tests must EPS pass (e.g., charge/discharge cycling, TVAC under load, thermal-vacuum power performance)? Options: Charge/discharge cycles, TVAC power soak, Battery safety/abuse tests, Solar array deployment tests
• Who provides the power budget and margin allocations: manufacturer or customer payload team? Options: Manufacturer provides budget, Customer provides budget, Joint reconciliation required
• Are there specific battery transport, storage, or shipping constraints (e.g., UN shipping class, state-of-charge limits)? Options: Yes - provide details, No

Install and qualify attitude determination and control system

• What pointing accuracy, stability, and knowledge requirements are driving ADCS selection (e.g., arcsec, mrad)?
• Which sensors and actuators are required or preferred (star trackers, sun sensors, IMUs, reaction wheels, magnetorquers, thrusters)? Options: Star trackers, Gyros/IMU, Reaction wheels, Magnetorquers, Cold gas thrusters, Other
• Are there specific control modes or maneuvers to support payload operations (e.g., fine-pointing, scan patterns, rapid repoint)? Options: Yes - describe, No
• What verification activities are required for ADCS (hardware-in-the-loop sim, on-sky calibration, gyro alignment, vibration tests)? Options: HIL simulation, On-sky calibration, Alignment & balancing, Vibration & shock
• Who will provide attitude determination algorithms or models (manufacturer, customer, third party)? Options: Manufacturer, Customer, Third party
• Are there operational constraints (sun/earth exclusion zones, safe modes) that should be captured in acceptance criteria? Options: Yes - specify, No

Integrate command-and-data-handling avionics

• What onboard data throughput and storage requirements must the C&DH support (average kbps, peak kbps, recorder size GB)?
• Which communication and wiring standards are required for avionics interfaces (SpaceWire, CAN, MIL-STD-1553, Ethernet, custom)? Options: SpaceWire, CAN, MIL-STD-1553, Ethernet, Custom
• What redundancy and fault-tolerance levels are required for critical C&DH functions? Options: Single string, Redundant processors, Watchdog-only, Fully redundant with cross-strapping
• Are there real-time processing or deterministic latency constraints for payload control or data processing? Options: Yes - specify latency, No
• Who owns the interface control documents (ICDs) and communication protocol definitions for payload-to-C&DH integration? Options: Manufacturer, Customer, Jointly owned
• Will avionics integration require onsite access to customer-supplied payload testbenches or simulators? Options: Yes, No, Maybe - to be scheduled

Load and validate flight software

• Who is responsible for flight software development and baseline ownership (manufacturer, customer, third-party)? Options: Manufacturer, Customer, Third-party contractor, Joint development
• What software validation and verification activities are required prior to flight (unit tests, integration tests, SIL/HIL, regression suites)? Options: Unit tests, Integration tests, SIL/HIL, Regression suites, Security penetration tests
• Are there cybersecurity or encryption requirements for command/telemetry channels (e.g., authenticated uplinks, encrypted downlinks)? Options: Yes - specify, No
• What is the process for delivering software updates during assembly, pre-launch, and post-launch (versioning, signed builds, update window)?
• Will customer flight software components be delivered as source, binaries, or containerized packages? Options: Source code, Binaries, Containerized images, Other
• What acceptance criteria or test evidence is required to sign off software load and validation for Test Readiness Review?

Perform thermal vacuum environmental testing

• Will TVAC be performed at full spacecraft level, payload-level only, or both? Options: Full spacecraft, Payload-only, Both
• Specify temperature ranges, soak durations, and thermally critical modes that must be included in the TVAC profile.
• Are thermal balance tests and thermal model correlation required as part of the TVAC campaign? Options: Yes, No
• Are witness samples, contamination monitoring, or cleanliness monitoring required during thermal testing? Options: Yes, No
• Who provides instrumentation and data acquisition for TVAC (manufacturer test lab, customer instrumentation, third party)? Options: Manufacturer lab, Customer-supplied instrumentation, Third-party lab
• What deliverables are required after TVAC (test reports, CDRL items, thermal model updates)? Options: Detailed test report, Data files, Thermal model correlation, All of the above

Perform vibration and shock qualification testing

• Is the test campaign qualification-level, acceptance-level, or both for the spacecraft and payload? Options: Qualification + acceptance, Acceptance only, Qualification only
• Which test types are required (sine, random, acoustic, separation shock, pyro shock)? Options: Sine, Random, Acoustic, Separation shock, Pyro shock
• Are there payload-specific constraints on vibration (sensitive optics, fragile assemblies) that require special fixtures or test limits? Options: Yes - specify, No
• Will full-system modal survey and mass/dynamics inputs be supplied prior to environmental testing? Options: Yes - provided, No - manufacturer to perform
• Who will provide telemetry and witness data collection during vibration (customer, manufacturer, third-party)? Options: Manufacturer, Customer, Third-party
• What acceptance criteria or post-test inspections are required to clear the spacecraft for subsequent processing?

Conduct electromagnetic compatibility and RF testing

• Which EMC/RF tests are required (conducted emissions, radiated emissions, susceptibility, antenna pattern, link budget verification)? Options: Conducted emissions, Radiated emissions, Susceptibility/immunity, Antenna pattern, Link budget verification
• Which frequency bands and RF power levels will the spacecraft and payload operate in?
• Are specific RF interface control documents (ICDs) or coordination with other satellites/ground stations required? Options: Yes, No
• Will RF testing be performed in-house or at an external chamber/anechoic facility? Options: In-house, External facility, Hybrid
• Are there mitigation measures required for EMI/EMC (shielding, filtering, grounding) that must be implemented prior to testing? Options: Yes - specify, No
• What pass/fail criteria or margin requirements apply to RF link and EMC performance?

• Master Supply Agreement (MSA)
• Statement of Work (SOW)
• Commercial Term Sheet
• Delivery & Milestone Schedule
• Payment & Invoicing Schedule
• On‑Orbit Warranty & Anomaly Support
• Acceptance Criteria & Test Evidence
• Change Control & Engineering Variants
• Program Governance & Steering Committee
• Performance Guarantees & Remedies
• Insurance & Liability Allocation
• Export Control & Compliance (ITAR/EAR)
• Intellectual Property & Data Rights
• Third‑Party Supplier Commitments & Flowdowns
• Escrow & Software Source Access
• Termination, Suspension & Dispute Resolution
• Transition & Long‑Term Support Agreement

• On-Orbit Performance Review — Validation Against Success Signals
• Lessons Learned & Continuous Improvement Workshop
• Customer Operational Handover & Long-Term Support Setup
• Anomaly Review & Corrective Action Planning
• Enhancement Roadmap & Future-State Confirmation

• One-sentence Current State
• Create an improvement backlog with timelines and a cadence for progress reviews.
• Produce a formal lessons-learned report with RCA notes and link to evidence artifacts.
• Create the prioritized improvement backlog in the shared workspace and assign owners/due dates.
• Define success metrics for each improvement and schedule the first progress review.
• Finalize escalation paths and contact lists for each severity level.
• Agree governance cadence and handover artifacts (SLA doc, runbooks, access lists).
• Current State & SLA Consequences
• Establish concrete support channels, access rights, and SLA targets agreed by both parties.
• Provision agreed support channels and invite primary contacts with defined permissions.
• Publish and sign off the SLA and escalation matrix in the shared workspace.
• Deliver access to telemetry portals and provide read-only and admin credentials as agreed.
• Anomaly Summary & Impact Statement
• Select a corrective approach with documented risk trade-offs and validation criteria.
• Assign cross-functional owners, resources, and a timeline for implementation and validation.
• Agree rollback criteria and communication plan for stakeholder notification during execution.
• Document the chosen corrective plan, validation steps, and rollback criteria in the change request.
• Allocate required engineering and operations resources and confirm scheduling availability.
• Execute the validation activities and report results to the governance channel within the agreed timeframe.
• One-sentence Future State Confirmation
• Produce a prioritized enhancement roadmap directly tied to the future-state outcomes with owners and timelines.
• Agree funding approach and change-control entry criteria for each enhancement.
• Define the review cadence and metrics that will demonstrate progress toward the future state.
• Draft the prioritized roadmap with owners, costs, and milestones and circulate for stakeholder sign-off.
• Open change requests or modification orders for top-priority enhancements and schedule integration windows.
• Establish the roadmap review calendar and link metric dashboards to each roadmap item for progress tracking.
• Formally verify which success signals are met and which require action, with evidence noted.
• Agree on immediate remediation or acceptance decisions and owners with clear timelines.
• Capture required evidence packages and schedule any follow-up validation checkpoints.
• Compile and store the full evidence package (telemetry extracts, plots, logs) linked to each success signal.
• Assign ownership and due dates for each discrepancy remediation or additional verification activity.
• Schedule follow-up validation meeting and update the shared performance dashboard.
• One-sentence Current State & Consequence
• Document a prioritized set of lessons and improvements tied to quantified consequences.
• Assign owners and success metrics for the top 3–5 corrective/improvement actions.
• Success Signal Mapping
• Support Channel Designation
• Operational Timeline Review
• Current vs Future Gap Analysis
• Telemetry Evidence & Reproduction Status
• Proposed Enhancements & Evidence of Impact
• Consequence Assessment
• RCA Findings & Confidence
• Root Cause Analysis Breakouts
• Escalation Paths & SLA Targets
• Data Access, Telemetry & Evidence Sharing
• Business Case & Funding Options
• Evidence Review & Anomaly Flags
• Corrective Options, Risks & Trade-offs
• Consequence Quantification
• Warranty, Anomaly Support & Funding Boundaries
• Change Control, Integration & Deployment Plan
• Prioritization & Impact/Effort
• Acceptance Decision & Validation Steps
• Validation Plan & Rollback Criteria
• Next Steps, Owners & Timeline
• Governance, Cadence & Reporting
• Action Planning & Success Metrics
• Commitments, Roadmap Owners & Review Cadence
• Resource Approval & Scheduling