Industrial & Manufacturing Aerospace & Space Commercial Space

Launch Services

Zero-failure programs where certification, partners, and supply chains must execute against gated evidence.

Example organizations in this space: SpaceX United Launch Alliance Arianespace Rocket Lab

This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.

Inside this journey
  1. Pre-Sales

    Qualify and diagnose mission requirements, risks, and schedule before committing to detailed planning.

    1. Qualification

      Confirm budget window, schedule constraints, decision-makers, insurance/governance requirements, and mission critical timelines before full discovery.

      Qualification Questions

      Mission fit and critical timing

      • So we make the best use of your time, what is the mission's target launch window or earliest required on-orbit date? Options: Within 3 months, 3–6 months, 6–12 months, 12–24 months, More than 24 months, Date-driven - I'll specify
      • Are any dates mission-critical and not permitted to slip? If yes, briefly state which.

      Commercial readiness and budget

      • Is there an allocated budget range for launch services today? Options: Under $1M, $1M–$5M, $5M–$20M, $20M–$50M, Above $50M, No allocated budget yet, Prefer not to state
      • Who signs the launch services agreement and who else materially influences the decision?

      Insurance, compliance, and governance

      • Do specific insurance limits, indemnity terms, export controls, or government approvals apply? Options: Standard commercial insurance only, Specific insurance limit required (we will provide details), Indemnity or special contract clauses required, Export controls or national restrictions apply, Government procurement or security clearance requirements, None / not sure
      • If any of the above apply, please briefly state the required insurance limits, approvals, or compliance notes.

      Readiness for discovery and next steps

      • Who from your team should join a focused discovery call (roles and best availability)?
      • From your perspective, is this opportunity ready for a focused discovery conversation now? Options: Yes — ready now, Yes — ready if we share key documents first, Not yet — need internal approvals or budget finalization, Not a fit / prefer to pause
    2. Mission Discovery

      Map mission objectives, payload constraints, required orbit accuracy, manifest flexibility needs, and stakeholder roles for technical due diligence.

      Discovery Questions

      Mapping your mission and timeline

      • Tell me briefly what your mission must achieve on orbit and why the launch date matters to your program
      • When does your first satellite or payload need to be operational on orbit, and how firm is that date Options: Firm date (fixed by contract or operations), Preferred date with ±1 month flexibility, Flexible within a 3–6 month window, Flexible beyond 6 months
      • Which orbital regime and approximate altitude are you targeting for this launch Options: LEO (below 2,000 km), SSO / Sun-synchronous, MEO (2,000–35,786 km), GTO/Transfer orbit, Interplanetary transfer
      • How many satellites or discrete payloads are you planning to fly on this mission Options: Single payload, 2–5 payloads, 6–20 payloads, More than 20 payloads
      • Describe the primary payload form factors, typical mass per unit, and any nonstandard or hazardous components
      • Who will be the named mission director or day-to-day integration owner on your side for decisions and approvals Options: VP/Director level (mission/ops), Program manager, Lead systems engineer, Cross-functional committee, Not yet assigned
      • Share an example of a late requirement change on a past mission and how your team managed schedule or cost impacts

      Where schedule and money really bite

      • If this launch slips by six months, what immediate program costs or operational impacts would you face
      • How often have multi-month schedule slips occurred across your last three launches, and what caused them Options: None, One instance, Two instances, Three or more
      • Who ultimately bears the cost of satellite storage or delayed operations under your current procurement model Options: The buyer (our program), The seller/launch provider, Shared by contract, Depends on the contract terms
      • Which contractual mechanism do you rely on today to recover costs from a delayed or failed launch Options: Liquidated damages clause, Rescheduling without penalty, Insurance claim, No explicit mechanism, Other
      • Explain the orbit insertion error (km or percent of delta-v) that would still allow your mission to meet its operational objectives
      • Estimate how much your insurance premium or underwriting requirements would change after a major schedule slip or anomaly Options: No change, Increase up to 10%, Increase 10–30%, Increase over 30%, Unknown — need underwriter input
      • Name the single contractual or technical failure that would make you walk away from this launch option immediately

      Nailing the technical numbers for mission assurance

      • Imagine your required orbit accuracy shifted by 50 kilometers or an order of magnitude in pointing, how would that change launch viability
      • List the avionics, sensors, and propulsion margins your payloads require for post-separation phasing and on-orbit commissioning
      • How many discrete separation events and deployment windows must the vehicle perform to meet your manifest sequencing needs Options: Single separation event, 2–3 events, 4–8 events, More than 8 events
      • Provide the mechanical, thermal, and vibration limits for your payload interfaces during processing and ascent
      • Identify the telemetry, tracking, and command endpoints you need during the launch campaign and whether access will be continuous Options: Continuous telemetry access, Scheduled windows only, Limited telemetry (post-separation), No telemetry required
      • Name the single unresolved technical question that, if not settled before integration, would force you to delay or cancel the launch

      Practical readiness, facilities, and approvals that gate work

      • Suppose your payload needed a custom separation system, can your schedule and budget absorb an additional 6–10 weeks for design, analysis, and test Options: Yes, schedule and budget absorb it, Only if budget is increased, No, timeline cannot absorb it, Unsure — need program analysis
      • Are your payload shipping windows, receiving inspection slots, and integration bay reservations already secured Options: All secured, Partially secured, Not secured yet, Not applicable
      • Count the number of engineers and technicians you can commit to hands-on integration and campaign support during the launch window Options: 0–2, 3–5, 6–10, More than 10
      • List export controls, licenses, or facility approvals that could gate payload handover or on-site work
      • Identify any ground facility access constraints or range access conflicts that will require external coordination Options: Range window conflicts likely, Range window tentative but manageable, No known conflicts, Unsure — need to verify
      • Name the single missing approval, test result, or resource that would prevent you from meeting your target integration start date

      The other options on your table

      • Assuming keeping your incumbent or solving launch internally is possible, what must be true for you to choose not to move to a new provider
      • Select the alternative approaches you are actively evaluating right now Options: Stay with current launch partner, Switch to a different vehicle class, Book a rideshare slot, Pursue a dedicated competitor vehicle, Develop internal launch capability, Delay satellite deployment
      • List the commercial or internal decision criteria that would keep you with the current approach instead of changing
      • Name internal roles or teams that have proposed an in-house launch or significant program change Options: Systems engineering, Operations, Finance, Procurement, Senior leadership, No internal proposal yet
      • Describe any reference checks, flight histories, or actuarial analyses you require before switching to a new launch provider Options: Independent reliability study, Operator references, Insurance underwriter assessment, Performance flight history, Other
      • Which single condition about a competitor or internal fix would convince you to delay selecting a new launch option

      What will make you sign and what will stop you

      • Outline the top three acceptance criteria your procurement and insurance teams require to move from evaluation to contract
      • Rate how important each of the following decision factors is for your final award: reliability, schedule certainty, cost per kg, manifest flexibility, indemnification terms Options: High, Medium, Low
      • State any absolute non-negotiables in contract language or insurance terms that would veto a deal
      • If a short pilot or demonstration mission proved the performance claims, what would prevent your team from signing within two weeks
      • Predict the internal approval path and typical timeline from mutual technical agreement to signed contract in your organization Options: Weeks (1–4), Months (1–3), Multiple quarters, Unclear
      • Describe the single governance or budget gate that will most likely delay or stop award on your side

      Final practical next steps and immediate blockers

      • Clarify the immediate documents, data, or test reports you can share within the next 7 days to accelerate technical review Options: Mass properties and interface drawings, Flight heritage reports, Thermal/vibration test reports, Insurance certificates, None available in 7 days
      • Choose the preferred cadence and audience for decision meetings over the next month Options: Weekly technical sync with engineers, Biweekly executive check-in, Ad hoc as milestones hit, Formal gating reviews
      • List any internal calendar windows, travel freezes, or blackout dates that would block integration or campaign activities
      • Confirm whether an underwriter or technical advisor will attend a joint technical review and provide their availability Options: Yes, will attend, Maybe, awaiting confirmation, No underwriter involvement, Not applicable
      • Name the one next step we should complete together that would most accelerate a decision on your side
  2. Solution Walkthrough

    Walk through how available vehicle classes, integration flows, and timelines deliver the buyer's mission outcomes using the customer's context.

    Solution Experience

    • Solution Walkthrough Session
    • Confirm the current state and its cost to your program
    • You confirm the recommended vehicle class and integration approach meet your payload mass, orbit accuracy, and manifest flexibility needs.
    • Deliver a mission mapping report that pairs each payload and orbit requirement to recommended vehicle classes, expected insertion accuracy ranges, and cost/schedule tradeoffs.
    • You acknowledge the quantified schedule risk and accept the proposed mitigation path or request specific alternatives.
    • Match vehicle classes to your mission scenarios
    • Provide a timeline with hard dates for payload shipping, integration milestones, and contingency windows, and identify the manifest decision cutoff dates.
    • You identify the remaining evidence required before a commercial decision, such as reference flight data, insertion accuracy statistics, or underwriter inputs.
    • Walk the end-to-end integration flow and risk points
    • Share final payload mass properties and mechanical interface drawings for each payload slot to allow final verification of fit and separation sequencing.
    • Timeline overlay and decision cutoffs
    • Confirm named decision-maker(s) and their approval criteria for schedule commitments and launch acceptance.
    • Validate alignment
    • Solution Walkthrough Session
    • Solution Walkthrough Deck
    • Solution Brief
    • meeting
    • slides
    • document
  3. Mission Scope

    Define the launch configuration, manifest sloting, payload integration tasks, verification requirements, responsibilities, and measurable acceptance criteria.

    Scope Configuration

    • Receive and Inspect Payload Hardware
    • Cleanroom Stowage and Environmental Control
    • Mass Properties and Center-of-Gravity Measurement
    • Mechanical and Electrical Integration to Dispenser/Adapter
    • Install Separation and Deployment Mechanisms
    • Encapsulate Payload within Launch Vehicle Fairing
    • Propellant Loading and Cryogenic/Hypergolic Fueling
    • Vehicle Final Assembly and Payload Mating
    • Execute Vibration, Shock, and Thermal Test Campaign
    • Provide Real-Time Launch Telemetry Feed
    • On-Orbit Deployment Confirmation and Orbit Determination
    • Provide Rideshare Slot Integration and Interface Delivery

    Scope Questions

    Receive and Inspect Payload Hardware

    • Provide your payload shipping manifest and associated tracking numbers (airway bill, container IDs) for the expected incoming consignment.
    • When will your payload arrive at the integration facility (estimated arrival date and time) and what is the inbound carrier?
    • Indicate the sealed-package environmental requirements during transport you expect us to verify on receipt (temperature range, relative humidity, shock thresholds).
    • What measurable acceptance criteria will confirm payload receipt inspection is passed (examples: dimensional tolerance within drawing X, no visible damage, functional power-on test results)?
    • Who on your team will provide the packing list and witness the receipt inspection and sign the packing acceptance certificate? Options: Your payload systems engineer, Your logistics coordinator, No witness required / remote witness via video
    • Specify any hazardous material (HAZMAT) declarations, battery state of charge, or radioactive sources included in the payload manifest that require special handling on receipt. Options: Lithium batteries declared with UN number, Pressurized vessels, Radioactive source declared, No hazardous items

    Cleanroom Stowage and Environmental Control

    • Select the cleanroom class you require for payload stowage and integration tasks. Options: ISO 5 (Class 100), ISO 7 (Class 10,000), ISO 8 (Class 100,000), No controlled cleanroom required
    • Describe any continuous environmental monitoring or data-logger trace you require while the payload is in stowage (temperature, humidity, particulate counts).
    • Identify the ESD (electrostatic discharge) controls and contamination control fixtures your hardware requires (for example wrist straps, ionizers, filtered toolkits).
    • Who will provide the payload contamination control plan or special handling instructions in the payload interface control document (ICD)? Options: Your payload engineer, We will use the ICD provided at handover, No special plan required
    • Specify required access restrictions or PPE (personal protective equipment) for your team during cleanroom operations (gowning level, visitor rules).
    • Estimate the total cumulative cleanroom stowage time your payload needs before integration (days). Options: Less than 3 days, 3-14 days, More than 14 days

    Mass Properties and Center-of-Gravity Measurement

    • Provide your latest mass properties package including mass, center-of-gravity (CG) coordinates, and inertial moments from your structural analysis or prior test reports.
    • Which measurement deliverable do you require from our facility: raw measurement data, calibrated CG report with uncertainty, or both? Options: Calibrated CG report with uncertainty, Raw mass and balance data, Both
    • Indicate the tolerance band for CG and total mass that you accept without requiring redesign or additional integration (e.g., ±1 kg, ±10 mm).
    • Who on your engineering team will approve the final mass properties report and sign the mass-and-balance certificate? Options: Your systems engineer, Your mission assurance lead, No signature required / acceptance by email
    • What measurement fixtures or handling attachments from your hardware drawing (for example, balance interface points or datum references) must be used during the CG test?
    • What acceptance evidence will validate that mass properties measurement is complete and acceptable for launch integration (for example signed mass-and-balance certificate, measurement uncertainty <= X%)?

    Mechanical and Electrical Integration to Dispenser/Adapter

    • Attach or describe the payload interface control document (ICD) for mechanical and electrical mating to the dispenser or adapter, including connector pinouts and mechanical datum drawings.
    • Select the mechanical interface type you require for mounting to the dispenser/adapter. Options: Standard interface plate with bolt pattern, Custom adapter ring per drawing, Direct dispense into pod/dispenser
    • Which electrical interfaces must be routed during integration (power, low-voltage telemetry, separation pyro initiator circuit, separation switch)? Options: Primary power only, Power and bussed telemetry, Power, telemetry, and separation interlock circuits
    • Who will supply flight harnesses, separation switch assemblies, and connector backshells: your team or our integration hardware pool? Options: You will supply all flight harnesses, We will supply standard harnesses per ICD, Hybrid — you supply mission-specific assemblies
    • List any electrical functional checks you require prior to mechanical mating (e.g., continuity checks, basic power-up, bus health telemetry snapshot).
    • When must final connector pin-mapping and harness drawings be locked for harness fabrication (weeks before integration)? Options: >8 weeks, 4-8 weeks, Less than 4 weeks

    Install Separation and Deployment Mechanisms

    • Provide the part number and qualification status of the separation system or deployment mechanism called out in your ICD.
    • Specify required shock and pyrotechnic initiation tests or witness points for the separation hardware (for example shock pulse level, initiation current).
    • Who will certify the separation system acceptance test results and provide the certificate of conformity? Options: Your separation system supplier, Your mission assurance representative, No external certification required
    • Which functional checks must be performed after installation (for example, mechanical stroke verification, latch continuity, redundant switch state)?
    • Identify the separation sequencing constraints for your payload (separation time relative to T+ seconds, desired delta-V vector, any spin or tumble requirements).
    • Estimate whether any specialized tooling or test articles for the separation mechanism must be provided by you for integration or functional verification. Options: You provide specialized tooling, We provide standard tooling, No specialized tooling required

    Encapsulate Payload within Launch Vehicle Fairing

    • Provide your payload mechanical envelope drawing and the fairing interface drawing to confirm fit-check dimensions.
    • Select any environmental constraints during encapsulation you require us to control (for example maximum particulate counts, maximum relative humidity). Options: Particulate control to ISO 5, Humidity limited to <40% RH, No special environmental constraints
    • Which fairing access and purge requirements does your hardware need during encapsulation (nitrogen purge, continuous purge flow rate in L/min)?
    • Who will approve the final fit-check and sign the fairing interface clearance form? Options: Your systems engineer, Your mission assurance representative, Approval not required
    • When must final mass and CG be locked relative to the scheduled encapsulation date (weeks prior)? Options: Locked at least 4 weeks prior, Locked 2-4 weeks prior, Lock within 2 weeks
    • Identify any off-axis protrusions or deployment appendages that require special fairing tooling or altered separation clearances.

    Propellant Loading and Cryogenic/Hypergolic Fueling

    • State whether your payload requires any on-pad fueling or propellant conditioning (for example pressurant recharge, cold-gas topping, hydrazine filling). Options: No fueling required for payload, Propellant topping/pressurant only, Cryogenic or hypergolic fueling required
    • If fueling is required, specify propellant types and maximum filled mass (for example: monomethylhydrazine (MMH) 5 kg, hydrazine 2 kg, liquid oxygen cryogenics).
    • Identify required safety approvals and authorizations for propellant handling that you will provide (Material Safety Data Sheets, certified venting plans).
    • Who on your side is the designated hazardous operations point of contact for fueling rehearsals and fueling execution? Options: Your propulsion lead, Your safety officer, No dedicated point of contact
    • Specify any cryogenic conditioning timelines or thermal soak requirements for your hardware prior to fueling (hours at temperature).
    • Do you require witness access or remote telemetry access during propellant operations (for example live pressure/temperature telemetry)? Options: Onsite witness access, Remote telemetry access, No witness required

    Vehicle Final Assembly and Payload Mating

    • Provide the latest vehicle-to-payload interface drawing and the scheduled date for mechanical mating at the integration facility.
    • Which final electrical and mechanical sign-offs do you require at mating (for example torque witness, connector pincheck, harness strain-relief verification)?
    • Who will provide final flight software version and telemetry configuration to be loaded prior to mating, if applicable? Options: Your flight software lead, We will load standard baseline, No software load required
    • When must your team deliver the approved flight acceptance paperwork required before vehicle mating (for example flight heritage reports, waivers, Certificate of Flight Readiness)? Options: More than 4 weeks before mating, 2-4 weeks before mating, Less than 2 weeks before mating
    • Specify any mechanical or thermal constraints during mating (for example allowable bolt torque, maximum allowable handling acceleration in g).
    • List the named owners from your organization who will sign the final mating acceptance form (name and role).

    Execute Vibration, Shock, and Thermal Test Campaign

    • Provide your environmental test levels and profiles for vibration, shock, and thermal vacuum that we should run (reference the test specification by number or include envelope values).
    • Which test artifacts must you have retained or witnessed (for example flight hardware on the shaker, load path invoices, witness video)? Options: Witness on-site, Remote witness via live stream, No witness required
    • Identify any flight acceptance thresholds or functional test pass/fail criteria that must be demonstrated post-environmental test (for example telemetry bit error rate, checksum integrity).
    • Who will approve the environmental test final report and associated nonconformance dispositions? Options: Your mission assurance lead, Your payload systems engineer, Approval via signed email
    • Estimate the number of hours of test and instrument calibration we should reserve for your campaign (approximate total). Options: Less than 24 hours, 24-72 hours, More than 72 hours
    • Do you require vibration fixture modifications or a full custom test rig built from your mechanical drawing? Options: Standard fixture acceptable, Custom fixture required — you provide drawing, Custom fixture required — we build per drawing

    Provide Real-Time Launch Telemetry Feed

    • Specify the telemetry channels and data rates you require in the real-time feed (for example bus voltage, separation switch status, payload temperature, sample rate in Hz).
    • Which telemetry transport do you prefer for real-time delivery (secure VPN stream, dedicated IP multicast, encrypted API endpoint)? Options: Secure VPN stream, Encrypted API endpoint, Dedicated multicast stream
    • Who on your operations team will receive the real-time feed and act as the telemetry operations lead during launch? Options: Your mission operations lead, Your ground station operator, No dedicated telemetry lead
    • When do you require access to the pre-launch test telemetry (hours before T-0) to perform final checkouts? Options: 48 hours before T-0, 24 hours before T-0, During final 4 hours only
    • List any telemetry security or encryption requirements (for example TLS 1.2+, dedicated keys, IP allowlist).
    • If real-time telemetry is interrupted, what backup evidence will you accept to confirm separation (for example separation event timestamps in on-board log, post-launch TLE confirmation)? Options: On-board event log, Post-launch TLE and orbit determination, Video of separation event
  4. Mutual Commit

    Resolve commercial and contractual terms, insurance and indemnification arrangements, schedule commitments, and launch acceptance criteria.

    Agreement Modules

    • Master Launch Services Agreement (MLSA)
    • Mission Statement of Work (SOW)
    • Launch Order & Order Form
    • Insurance Certificate & Policy Schedule
    • Indemnity and Liability Exhibit
    • Launch Schedule Commitment & Delay Remedies Addendum
    • Launch Acceptance Criteria & Flight Readiness Acceptance
    • Technical Interface Agreement (TIA)
    • Change Order & Contract Variation Agreement
    • Export Control & Regulatory Compliance Addendum
  5. Deployment

    Operationalize the launch campaign with readiness checks, integration, and go/no-go validation.

    1. Pre-Deployment Readiness

      Capture concrete readiness facts — payload shipping dates, facility access, fueling authorizations, range coordination and named owners required before integration.

      Pre-Deployment Questions

      Environment and site access

      • Which integration site(s) or launch facility will receive the payload? (List site name(s) as used in your organization — needed to allocate facility slots.)
      • For each site listed above, what is the first-available date for payload intake? (This date sets the baseline for inbound scheduling and storage.)

      Logistics and shipping

      • What is the confirmed payload shipping window—earliest inbound date and latest acceptable arrival? (So we can book transport and storage hold points.)
      • Who is arranging commercial transport and customs clearance for the payload? (Select the party responsible; if a third party or buyer broker is used, the DeploymentConfig will capture contact details.) Options: Buyer (in-house logistics), Buyer (external broker), Seller will arrange, Third-party logistics provider — buyer to confirm, Not arranged
      • Does the payload contain hazardous items requiring special handling or permits (batteries, pressurized systems, propellant, etc.)? If yes, has the authorization been submitted to the facility/range? Options: No hazardous items, Yes — authorizations submitted, Yes — authorizations pending, Unknown / need assessment

      Technical integration readiness

      • Has the mechanical and electrical integration baseline been locked (fit-checks, separation interface, telemetry endpoints)? (We need a 'Locked' state to freeze integration drawings and dates.) Options: Locked, Locked with minor open items, Draft — key items open, Not started
      • Are required verification tests and witness plans finalized and booked (vibration/thermal/EMC, witness roles)? If booked, provide the target test completion date in DeploymentConfig. Options: Yes — tests complete, Yes — tests scheduled, No — not scheduled, Not applicable

      People and ownership

      • Who is the buyer's named owner for payload inbound coordination (name and role)? (This single point will accept custody at intake and coordinate facility handover.)
      • Who is the named owner responsible for range coordination and launch window approvals (name and role)? (This person must be enabled to approve range interfaces and schedule decisions.)
      • Are there any blackout dates or fixed constraints (facility outages, regulatory windows, insurance embargoes) that must be avoided during integration or campaign execution? (If yes, note that dates/details belong in DeploymentConfig.) Options: No constraints, Yes — scheduled facility maintenance, Yes — regulatory/compliance window, Yes — insurance/contractual embargo, Unsure — need confirmation
    2. Integration Configuration

      Lock technical integration values and operational parameters the team will use — mechanical/thermal limits, telemetry endpoints, separation sequencing, and test sign-offs.

      Configuration Details

      Integration Configuration — Environments & Endpoints

      • Integration instance name (enter the single name used in all configs; format: lowercase alphanumeric and hyphen, Default: mission-integration)
      • Integration environment stage (which environment do these values apply to? Default: Production) Options: Production, Staging, Integration Lab, Test
      • Telemetry ingestion endpoint URL (format: https://... — enter the endpoint the seller will push integration telemetry to)
      • Telemetry authentication method (Default: mTLS — pick how telemetry is authenticated; if choosing token, you will be asked only for the token IDENTIFIER, not the secret) Options: mTLS (mutual TLS), Bearer token header (token identifier only), IP allowlist only, No authentication (open network)

      Mechanical & Thermal Limits

      • Primary mechanical interface standard for the payload adapter (Default: Clamping ring) Options: Clamping ring (standard clampband), Separation bolt interface, CubeSat dispenser standard (e.g., dispenser slot), Custom adapter (provide drawing reference separately)
      • Maximum allowable payload mechanical load during integration (peak g, integer — Default: 3)
      • Minimum allowable payload temperature during integration (°C — Default: 0)
      • Maximum allowable payload temperature during integration (°C — Default: 40)

      Separation, Sequencing & Confirmation

      • Separation sequencing mode (Default: Timed sequencing) Options: Timed sequencing (pre-set delays), Interface-commanded separation (payload/dispenser issues command), Ground-commanded separation (ground triggers), Autonomous onboard sequencer
      • Separation delay after ignition cutoff (seconds — numeric; Default: 120)
      • Primary telemetry endpoint for separation confirmation (enter topic name or URL used to publish confirmation; format example: telemetry://separation/status or https://host/path)

      Verification & Test Sign-offs

      • Required integration test sign-off types (select all that will be required before flight integration) Options: Mechanical fit check, Electrical interface test, Thermal soak verification, Vibration acceptance test, Separation functional test, EMC/EMI check
    3. Launch Campaign Execution

      Plan and execute the launch campaign with a sequenced Gantt, owners for integration tasks, range windows, and real-time launch operations coordination.

    4. Launch Readiness & Go/No-Go

      Formalize final pre-launch checks, stakeholder sign-offs, and the official go/no-go decision with named owners and acceptance criteria.

      Checklist items

      • Receive signed Go/No-Go decision document
      • Obtain written range clearance and NOTAM release
      • Fueling authorization and LOTO verification completed
      • Flight Termination System (FTS) acceptance and arming authorization
      • Final payload acceptance certificate received from payload owner
      • Telemetry and command link end-to-end verification completed
      • Signed flight readiness review (FRR) closure with all open actions closed
      • Required insurance certificates and indemnification docs validated
      • Final integration configuration baseline signed
      • Abort/standdown and contingency plan approval recorded
  6. Success

    Confirm orbital insertion outcomes, share telemetry and orbit determination, capture lessons learned, and maintain a shared channel for issues and enhancements.

    Success Reviews

    • Post-separation Health Check
    • First Measurement Review
    • Formal Acceptance Gate — Orbit Determination Decision
    • Lessons Learned and Anomaly Closure
    • Quarterly On-orbit Review

    Issues & Enhancements

    • Publish the lessons-learned report and the updated runbook to the shared channel.
    • Restate Mission Scope acceptance criteria and numeric targets
    • Produce a documented pass or fail decision against each Mission Scope acceptance criterion and capture the formal acceptance record.
    • If any criterion is unmet, commit to a remediation plan with milestones and an agreed final resolution timeline.
    • Publish the signed acceptance decision and supporting evidence to the shared workspace.
    • If conditional acceptance or failure occurred, publish the remediation plan with milestone dates and verification criteria.
    • Update the mission risk register to reflect acceptance outcomes and any residual risks.
    • Consolidated telemetry and anomaly summary
    • Close or assign resolution dates for all remaining anomalies and confirm the projected closure timeline.
    • Agree a concise set of operational improvements and update the runbook and integration checklist accordingly.
    • Re-confirm success criteria and responsibilities
    • Complete the telemetry archive and verify accessibility for both parties.
    • Close all anomaly tickets that meet closure criteria and update the anomaly tracker with planned residual items.
    • On-orbit health and telemetry uptime review
    • Confirm the asset continues to meet on-orbit health expectations and identify any trending issues requiring attention.
    • Ensure the backlog of enhancements and persistent issues has prioritized next steps and resolution timelines.
    • Publish the quarterly on-orbit health scorecard including telemetry uptime and mean time to anomaly detection.
    • Update and publish the prioritized enhancement and defect backlog with estimated delivery windows.
    • Validate the shared channel escalation contacts and publish any changes to the communications plan.
    • Confirm each payload recorded a completed separation event and initial telemetry was received or document exceptions.
    • Produce an immediate issue list with remediation tasks and target resolution windows.
    • Publish the initial telemetry packet archive and separation timeline to the shared channel for review.
    • Log all immediate anomalies in the shared issue tracker with remediation tasks and target dates.
    • Schedule technical detailed review sessions for any items blocking payload commissioning.
    • Present first orbit determination and telemetry completeness
    • Determine whether orbital insertion error and beacon acquisition time are trending toward Mission Scope targets and identify any remaining risks.
    • Agree a remediation plan with specific tasks and dates that addresses any gaps prior to the acceptance gate.
    • Deliver an updated orbit determination report and telemetry completeness summary to the shared channel.
    • Log and prioritize telemetry frame gaps and provide a re-ingest timeline for missing data.
    • Publish the evidence package checklist required for the Mission Scope acceptance gate.
    • Separation event and timeline verification
    • Root cause and corrective action effectiveness review
    • Present consolidated outcomes against each criterion
    • Compare measurements against Mission Scope targets
    • Incident and anomaly trend review
    • Enhancement and defect backlog review
    • Record pass/fail decision per criterion and capture signatory
    • Operational and process improvements
    • Root cause analysis for any insertion or telemetry gaps
    • Initial telemetry and beacon acquisition check
    • Early functional checks and mode confirmation
    • Shared channel and escalation process validation
    • Archive telemetry and lessons to the shared channel
    • If conditional or failed, agree remediation plan and timeline
    • Agree corrective actions and timeline to acceptance
    • Open issues triage and immediate remediation actions
    • Agree next quarter actions and schedule next review
    • Confirm data and evidence package for the acceptance gate
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.