• Solution Experience Session

• Confirm the current state and its cost
• You confirm that the presented architecture and heritage evidence materially reduces the integration risk you described.
• Deliver the full heritage data package including flight logs, test summaries, anomaly records, and resolution reports within five business days.
• You accept the integration approach and schedule as sufficient to protect the launch window, or you identify specific remaining objections that must be closed.
• Map architecture and heritage to your mission outcomes
• Provide the payload interface control document and any special payload constraints or test requirements.
• Walk the integration approach and schedule protections
• Propose three dates for a cleanroom site visit and provide a draft visit agenda focused on payload integration checkpoints.
• You agree on the exact evidence set and acceptance criteria that will satisfy your technical review board before committing to full technical evaluation.
• Review the evidence set
• Document and finalize acceptance criteria and named sign-off owners for mission performance and integration acceptance.
• Validate acceptance criteria and remaining gaps
• Validate, in your words
• Agree next steps and timeline to close evidence gaps

• Solution Experience Session
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• desired_state
• current_state
• decision_readiness
• stakeholders
• gaps
• success_criteria
• stakeholders
• decision_readiness
• current_state
• desired_state
• success_criteria
• gaps
• stakeholders
• desired_state
• current_state
• decision_readiness
• success_criteria
• gaps
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Manufacture Flight Satellite Bus
• Assemble and Integrate Propulsion System
• Assemble Power System and Solar Array
• Install and Calibrate ADCS (Attitude Control)
• Load and Verify Flight Software
• Payload Mechanical and Electrical Integration
• System-Level Environmental Test Campaign
• EMC/EMI Testing and Mitigation
• Launch Vehicle Interface Kit and Adapter Delivery
• Functional Test and End-to-End Checkout
• Early Orbit Operations and Commissioning
• On-Orbit Anomaly Response and Warranty Support
• Configuration Management and Flight Heritage Documentation
• Capital Procurement and Incentive Qualification Package

Manufacture Flight Satellite Bus

• Specify the target spacecraft class and dry mass range for your flight bus (include structural margins in kg). Options: <50 kg, 50-150 kg, 150-500 kg, 500-2000 kg, >2000 kg
• Provide the required mission lifetime and expected orbital environment (LEO/SSO/GEO and minimum years of operation). Options: LEO, SSO, GEO, Other
• Identify required bus performance guarantees you expect included in contract (power, pointing, data throughput) with numeric targets.
• List mandatory quality and standards evidence you require at delivery (AS9100 certificate copy, FMEA, non-conformance reports). Options: AS9100, FMEA, NCRs, Materials certifications
• Confirm any fixed acceptance thresholds carried forward from qualification (e.g., minimum flight heritage count, delivery date range, acceptance telemetry baselines).

Assemble and Integrate Propulsion System

• Estimate total delta-v and typical maneuvers the propulsion system must support (orbit raise, stationkeeping, collision avoidance) in m/s.
• Indicate preferred propulsion technology and propellant type for the program (electric Hall, ion, bi-propellant, hydrazine) and minimum demonstrated life. Options: Electric (Hall/ion), Bi-propellant chemical, Mono-propellant (e.g., hydrazine), Hybrid / other
• Select required propellant handling support we must provide at factory (fueling at factory, fueling at launch site, safe custody logistics). Options: Fueling at factory, Fueling at launch site, Fueling by buyer, Dry ship
• State any containment or hazardous materials approvals required for transport to the launch site (regulatory class, MSDS constraints).
• Describe required proof pressure, leak rate, and pressurization test evidence for tanks and feedlines.

Assemble Power System and Solar Array

• Upload or list the power profile per mission phase we must design to (nominal, peak, survival) and indicate end-of-life power margins.
• Attach battery and solar array derating requirements and specify depth-of-discharge (DoD) limits or cycle life acceptance. Options: Standard DoD 80%, Conservative DoD 60%, Custom
• Choose preferred battery chemistry and whether a flight-qualified battery data pack is required. Options: Li-ion, Lithium polymer, Other, No preference
• Define the payload power taps and connector pinout constraints we must reserve on the power distribution unit (voltage rails, max continuous amps).
• Name thermal or mass constraints that impact the power subsystem (max stowed volume, allowed radiator area).

Install and Calibrate ADCS (Attitude Control)

• Which pointing accuracy and stability values are required for your payload operations (provide arcseconds for pointing error and arcsec/sec for jitter)?
• Do you require star tracker redundancy or cross-calibration with other sensors during commissioning? Options: Single star tracker, Redundant star trackers, Cross-calibration required
• Are magnetic clean zones or specific material restrictions required near sensors for ADCS performance? Options: Yes, No
• How should we deliver ADCS calibration artifacts (in-flight calibration tables, sensor alignment matrices, test vectors) at handover?
• When do you expect ADCS to be declared functionally ready in the program schedule (before delivery, after environmental test, at test readiness review)? Options: Before delivery, After environmental test, At TRR

Load and Verify Flight Software

• Quantify required flight software determinism and latency constraints for real-time subsystems (control loop period ms, worst-case RT response ms).
• Assign acceptance responsibilities for flight software verification artifacts (unit tests, integration tests, HIL results) between we and you. Options: We provide all artifacts, You provide independent verification, Shared responsibilities
• Prioritize the software features that must be frozen before environmental testing (fault protection, TM/TC handlers, payload drivers). Options: Fault protection, TM/TC handlers, Payload drivers
• Outline your update policy for in-orbit patches (automated patching, manual approval windows, rollback criteria). Options: Automated, Manual approval, No patches allowed
• Measure expected size of flight software image and telemetry footprint (MB, daily downlink GB) for verification of storage and downlink capacity.

Payload Mechanical and Electrical Integration

• Schedule preferred integration milestones for payload mate (preliminary mate, functional mate, final qualification mate) and indicate required witness points.
• Propose mechanical load limits and allowable shock/vibration exposure for the payload during integration and transport.
• Reserve required NRE or special tooling access for payload integration and state whether tooling remains property of you or we. Options: Tooling stays with us, Tooling transferred to you, Tooling returned after use
• Secure required payload acceptance interfaces such as optical boresight, RF passbands, and thermal coupling points with explicit interface drawings.
• Approve acceptance inspection points and gate criteria for mechanical install (torque values, fastener inspections, alignment tolerances).

System-Level Environmental Test Campaign

• Authorize the environmental standards we must follow for system-level testing (thermal vacuum, random vibration, acoustic) and indicate any deviations allowed. Options: Standard GEVS-like profiles, Custom profiles provided, Reduced levels acceptable
• Allocate test article fidelity requirement for each campaign (flight unit, flight-like with mass dummies, or structural dummy) and note mass property representativeness. Options: Flight unit, Flight-like with mass dummies, Structural dummy
• Report any flight-limiting failure modes previously observed in heritage units that test campaigns must focus on (e.g., connector loosening, solar array deploy issues).
• Verify the acceptance criteria that will confirm the flight unit passes system-level environmental testing, including allowed functional failures, leak rate thresholds, and required witness signatures.
• Document witness attendance preferences and the format of test reports you require (raw waveform data, summary pass/fail, calibrated plots). Options: Raw data required, Summary reports only, Both

EMC/EMI Testing and Mitigation

• Specify the RF frequency bands and transmitters that must be evaluated during EMC testing and provide expected transmit duty cycles.
• Provide an EMI mitigation hierarchy you prefer (shielding first, then filtering, then grounding) and any prohibited materials.
• Identify sensitive payload subsystems and their susceptibility thresholds (e.g., receiver front-end IP3, imaging sensor noise floor).
• List required EMC test levels for radiated emissions and susceptibility with numeric dBμV/m or applicable standard references.
• Confirm whether anechoic chamber time must be scheduled through us or arranged by you and any blackout dates. Options: We schedule chamber, You schedule chamber, Mutual arrangement

Launch Vehicle Interface Kit and Adapter Delivery

• Estimate the mass and center of gravity envelope the launch vehicle adapter must accommodate and attach preferred CoG datum.
• Indicate whether separation dynamics studies are required and if you need us to provide simulation outputs (load spectra, center of mass shift). Options: Separation dynamics required, Not required
• Select required electrical umbilical connectors and pinouts for the adapter kit and provide preferred connector families.
• State land transport and handling constraints for the adapter kit (packaging, orientation, lifting points) for safe delivery to the launch site.
• Describe any preservation or flight-cleaning treatments required before adapter handover (passivation, fungus treatment, clean-packaging level).

Functional Test and End-to-End Checkout

• Upload or reference the sequence-of-operations scripts you expect exercised during end-to-end checkout (telemetry streams, commanding sequences, payload modes).
• Attach expected pass/fail metrics for functional test scenarios (command latency ms, telemetry freshness seconds, packet loss %) for verification.
• Choose whether mission control system integration testing will be run on our facility, your facility, or a neutral testbed. Options: Our facility, Your facility, Neutral testbed
• Define required test data products and formats for checkout validation (telemetry packet definitions, CCSDS frames, packet dump formats).
• Name the specific evidence package that will validate end-to-end checkout acceptance (test reports, telemetry captures, signed witness logs) and the required signatories.

Early Orbit Operations and Commissioning

• Which commissioning milestones must be met before payload routine operations (sun acquisition, stable ADCS, payload calibration, RF link baseline)? Options: Sun acquisition, Stable ADCS, Payload calibration, RF baseline
• Do you require our team to provide on-orbit support for the first passes and if so, how many passes or days? Options: First 1-3 passes, First week, First 30 days, No support required
• Are there quantitative commissioning success metrics we should measure (GSD for imagers, bit error rate for comms, pointing offset arcsec)?
• How will acceptance for commissioning be documented and signed off (commissioning report template, calibrated products, formal handover meeting)?
• When will on-orbit commissioning be considered complete and what signed acceptance or quantitative thresholds define 'done' for handover to your ops team?

On-Orbit Anomaly Response and Warranty Support

• Quantify expected warranty cover items (coverage of hardware failures, software defects, operator errors) and specify duration per failure class.
• Assign primary contacts from your side for warranty claims and list required documentation for each claim (telemetry, ground logs, reconstructed timeline).
• Prioritize which anomaly severities require immediate 24/7 response vs standard business-hour handling. Options: Severity 1 24/7, All severities business hours, Custom
• Outline the process for classification of anomalies and the evidence thresholds that escalate an issue to warranty support.
• Measure expected telemetry retention and access you require for investigations (raw TM retention days, access frequency).

• Purchase Agreement
• Statement of Work (SOW)
• Master Terms and Conditions (MSA)
• Milestone & Payment Schedule
• Acceptance Test Protocol
• Warranty & On-Orbit Support Agreement
• Program Governance & Escalation Plan
• Change Order Agreement
• Data Rights & Intellectual Property Schedule
• Export Control & Licensing Addendum
• Insurance & Risk Allocation Schedule
• Government/Defense Procurement & Security Rider (conditional)

• Early Commissioning Health Check
• Initial Performance Measurement
• Formal On-Orbit Acceptance Gate (Day 90)
• Monthly Hypercare Operations Review
• Quarterly Operational Review
• Annual Warranty and Performance Review

• Measured performance against payload downlink throughput (Mbps) and telemetry health is reviewed and understood.
• Execute the operations transfer checklist and confirm the buyer's access to the shared anomaly and telemetry channels.
• Anomaly log review
• Anomaly rate and time-to-resolution trends are within or trending to Program Scope thresholds.
• Outstanding remediation tasks are updated with new dates or verification evidence.
• Anomaly channel and escalation path are confirmed operational and accessible.
• Update the anomaly log with final statuses and attach verification telemetry or test reports for closed items.
• Schedule any required in-orbit firmware or configuration updates with a test plan and blackout windows.
• Run an escalation path test and publish results confirming response times met Program Scope SLAs.
• Quarterly performance summary
• Operational performance is validated against Program Scope targets and trends are documented.
• Priority open issues are agreed and scheduled for remediation during the next quarter.
• Any agreed process improvements to the support workflow are captured with delivery dates.
• Deliver a quarterly performance report with telemetry extracts, throughput logs, and trend charts versus Program Scope targets.
• Publish the prioritized list of open operational issues with target remediation quarters.
• Implement agreed alert threshold adjustments and document the rationale and expected impact.
• Annual performance against guarantees
• Annual metrics MTBA and propellant usage are reviewed and their impact on mission lifetime is agreed.
• Warranty claims and remaining entitlements are documented and understood by both parties.
• Support model and escalation contacts are refreshed for the coming year.
• Publish the annual performance dossier including MTBA calculations, propellant consumption summary, and implications for mission lifetime.
• Document warranty claim history and remaining entitlements with reference to Program Scope warranty terms.
• Update the shared support contact and escalation matrix for the next 12 months.
• All parties confirm the commissioning sequence status and that no critical commissioning steps remain open.
• Immediate blockers are documented with remediation tasks and target dates.
• Shared anomaly channel and escalation path are validated and available for use.
• Publish a one-page commissioning completion summary that lists remaining steps, open anomalies, and named owners.
• Create remediation tasks for each open commissioning anomaly with target dates and expected verification criteria.
• Confirm and distribute the anomaly reporting channel endpoint and escalation contacts to the operations team.
• Present initial performance data
• Re-confirm acceptance criteria and owners
• Corrective actions are agreed with clear tasks and timelines toward the acceptance gate.
• Data sources and methods for the acceptance decision are validated and recorded.
• Deliver a detailed performance packet with raw telemetry extracts and analysis supporting the presented throughput and telemetry health figures.
• Open remediation tasks for each root cause with a test plan and target completion date ahead of the acceptance gate.
• Publish the acceptance gate checklist referencing the specific Program Scope criteria that will be measured.
• Restate acceptance criteria and signatory authority
• A formal acceptance decision is recorded against the Program Scope criteria with a named signatory and effective transfer date.
• All failed or conditional criteria have remediation plans with target resolution dates.
• Transfer checklist completed and warranty start conditions are confirmed.
• Publish the formal acceptance record that lists pass/fail results, signatory name, effective transfer date, and attachments of supporting evidence.
• Create remediation tasks for any failed or conditional criteria with verification steps and deadlines.
• Commissioning sequence validation
• Present outcome data against each criterion
• Root-cause analysis for gaps
• Risk and maintenance planning
• Warranty and entitlement review
• Time-to-resolution trends
• Remediation plan and timelines
• Document pass/fail decisions
• Open issue burn-down
• Remediation progress and verification
• Long-term anomaly trends and mitigation
• Early telemetry and link health
• Formal acceptance decision and signatory
• Shared channel and escalation health check
• Operational support model and contact refresh
• Acceptance gate readiness check
• Open issues and blocker triage
• Shared support process improvements