A Quick Pulse: Where Your Program Really Is Today

• What's your role in the program and who else on your team we should be talking to? Options: Ground Segment Program Manager, Director of Satellite Operations, Chief Engineer, IT/Cybersecurity Lead, Procurement/Contracts, Other
• What is your confirmed launch date (or current best estimate) and how locked is that date? Options: Firm/hard-locked, Likely but could slip 1–2 months, Flexible (3+ months of slack), Unsure / TBD
• How do you feel about your ground readiness today—confident, nervous, stretched, or something else? Options: Very confident, Somewhat confident, Uneasy, Actively concerned, Other
• Briefly describe the scope of the mission this ground segment must support (orbit type, number of satellites, primary mission objective).
• Who will be the primary day-to-day users of the ground system after handover? Options: Dedicated ops team at customer, Shared ops with vendor-managed service, Third-party MOC operator, Automated operations/limited human ops, Other

Are You Quietly Betting the Launch on Optimism?

• How confident are you that all cross-team dependencies (spacecraft, payload, IT, facilities) will meet their timelines? Options: Very confident, Some concerns, Major concerns, Unknown
• Which dependencies worry you most right now and why? Options: Spacecraft interfaces, Antenna site readiness, Network latency/links, Cybersecurity accreditation, Procurement/contracts, Other
• If a single schedule slip happens, what part of your plan would be most at risk of cascading delays?
• How long could you absorb a 2–8 week slip before the launch outcome (commissioning) is materially compromised? Options: Less than 2 weeks, 2–4 weeks, 1–2 months, More than 2 months, We can't absorb any slip
• What contingency or risk transfer strategies have you already planned (e.g., alternate sites, vendor-managed test windows, phased acceptance)?

What Keeps You Up the Night Before a Launch?

• What is the single worst ground-failure scenario you fear on Day 0–7 of commissioning? Options: No RF lock with spacecraft, Telemetry corrupt/lost, Command uplink failure, Cybersecurity incident, Site/access failure, Other
• Has your program experienced a comparable failure before? Tell us what happened and how you recovered.
• How often do you run end-to-end rehearsals with your spacecraft simulator today? Options: Weekly, Monthly, Occasionally, Never / planned
• When things go wrong during a pass or test, what is the typical time to identify the root cause and escalate? Options: <15 minutes, 15–60 minutes, 1–4 hours, 4–24 hours, >24 hours
• Emotionally, what are the biggest stresses for your team during early orbit ops—credibility, budgets, staffing, or something else? Options: Credibility with stakeholders, Budget overruns, Staff fatigue/availability, Regulatory/contractual penalties, Other

Who Holds the Keys—and Who Can Stop This?

• Who are the decision-makers that must sign off on ground acceptance and commercial terms?
• Which function has final technical acceptance authority (spacecraft engineering, mission ops, external regulator)? Options: Spacecraft engineering, Mission operations, Program management, External regulator/agency, Other
• Are there stakeholders outside engineering (procurement, legal, cybersecurity) that can impose last-minute constraints? Give examples.
• What governance cadence do you prefer for milestone decisions—weekly technical sync, biweekly program reviews, or milestone gates? Options: Weekly sync, Biweekly review, Monthly gate reviews, Ad-hoc as needed
• If a disagreement arises between spacecraft and ground teams, how is it typically resolved and who arbitrates?

If Ground Went Perfectly, What Would First Contact Feel Like?

• What are the concrete success signals you need to see during initial commissioning to call it a win? Options: Stable telemetry streams, Deterministic command response time, Planned pass coverage achieved, Link margins within spec, Cybersecurity accreditation granted, Other
• Which of those signals are immediate (first pass), and which are validated over weeks/months? Options: Immediate, Validated over time, Both depending on the signal, Unsure
• What quantitative thresholds define 'acceptable'—e.g., minimum Eb/No, BER, latency, telemetry packet loss?
• How will you measure operator proficiency before handover—checklists, observed runs, exam, or live passes? Options: Observed runs, Formal exam/certification, Checklists with sign-off, Live-pass demonstration, Other
• Who outside your team needs documented proof of success (investors, regulators, launch provider)?

Where Do Your Interfaces Tend to Break?

• Which protocols and standards must the ground system support for your spacecraft (e.g., CCSDS TM/TC, custom binary, REST APIs)? Options: CCSDS TM/TC, S-encapsulated frames, Custom binary protocol, Socket/API integrations, REST/SOAP, Other
• Do you have a working spacecraft simulator we can integrate with, and what level of access will you grant for factory/site testing? Options: Full access for vendor testing, Limited access in controlled windows, Simulator provided on-site only, No simulator yet
• Which interfaces have caused the most integration friction historically—telemetry formatting, time-sync, command sequencing, or link-layer issues? Options: Telemetry formatting, Time synchronization (UTC/PPS), Command sequencing/timing, Modulation/IF mismatch, Network/packet loss
• How do you currently validate end-to-end interoperability—automated regression, manual runs, or hybrid? Share cadence and test coverage if possible.
• What are the top three 'must not break' interfaces for your mission and why?

How Fragile Are Your RF Margins and Coverage Assumptions?

• Which frequency bands will you be operating in for this mission? Options: S-band, X-band, Ka-band, UHF/VHF, Multiple bands
• What nominal link margin do you require at your worst-case elevation angle? Options: >10 dB, 6–10 dB, 3–6 dB, <3 dB, Unsure
• Do you have a coverage map and planned passes that we can use for validation? If yes, how precise/validated is it? Options: Validated by flight dynamics, Preliminary/estimates only, No coverage map yet, We can provide after NDA
• How tolerant is the mission to missed passes or degraded margins—single-pass recovery, mission delay, or critical loss? Options: Single missed pass tolerable, Multiple missed passes tolerable, Delays acceptable with mitigation, Critical loss of mission
• Have you simulated or tested low-elevation multipath and Doppler effects for your intended ground sites? Options: Yes – comprehensive testing, Some testing performed, Planned but not done, No

Who Needs to Sleep Easily About Cyber—and Why They Don’t

• What cybersecurity standards or accreditations does your program require (e.g., NIST, ISO 27001, agency-specific baseline)? Options: NIST 800-53/800-171, ISO 27001, Agency-specific (specify), DoD/IACS, None specified yet
• What are the biggest cybersecurity concerns that would cause a stakeholder to block go/no-go? Options: Data exfiltration, Command spoofing, Insider threat, Supply-chain risk, Network lateral movement
• Do you already have an ATO/Authority-to-Operate path defined and a timeline for accreditation? Options: Yes and on schedule, Yes but delayed, Planned, timeline TBD, No formal path defined
• What level of vendor involvement in cybersecurity will be acceptable—full vendor SOC involvement, controls handed to customer, or hybrid? Options: Vendor manages SOC/controls, Customer manages controls, Hybrid (shared responsibilities)
• Are there particular network segmentation, encryption, or supply-chain requirements we should be aware of up-front?

Can You Operate This Reliably for 10–15 Years?

• What is your intended operational model after handover—fully customer-run, vendor-managed service, or hybrid? Options: Customer-run, Vendor-managed, Hybrid
• What are your lifecycle expectations for spare parts, software updates, and hardware refresh cadence? Options: Spares stocked on-site, Vendor-maintained spares pool, Predictive replacement schedule, Ad-hoc replacements
• How important is backward compatibility of telemetry/command formats over the mission lifetime? Options: Critical, Important, Nice to have, Not required
• What staffing constraints do you anticipate for long-term ops (e.g., limited 2nd/3rd line engineers, high turnover)?
• If budget for sustainment were to tighten by 20%, what parts of ground ops would you deprioritize first? Options: On-site spares, Training frequency, Software updates, Monitoring/alarms, Other

What’s the One Proof That Would Make This Partnership Undeniable?

• Would a short pilot (e.g., a factory integration run with your simulator) materially reduce your risk—why or why not? Options: Yes, definitely, Maybe with constraints, Unlikely to help, Not applicable
• What acceptance or commercial terms are non-negotiable for you before starting physical deployment? Options: Fixed acceptance criteria, Performance-based payments, Warranty length, Spares commitments, Cyber SLA
• What timeline and decision checkpoints would you need to see before committing to a vendor-led integration plan?
• How would you like us to demonstrate credibility—reference missions, site visits, simulation logs, or an on-site proof-of-concept? Options: Reference missions, Site visits, Simulation logs / test reports, On-site PoC, Other
• If we proposed a targeted next step (e.g., a 2-week simulator integration), what obstacles would stop you from saying yes immediately?

Quick Launch Snapshot — Who, What, When

• Can you give a one-line summary of this program and the single outcome that must be achieved by launch?
• What is your hard-locked launch date? Options: Within 3 months, 3–6 months, 6–12 months, 12–24 months, 24+ months, TBD
• Who are the core decision-makers for ground acceptance and their roles (name, title, responsibility)?
• Which teams must be aligned to accept the ground segment at-go/no-go (select all that apply)? Options: Spacecraft engineering, Ground operations, IT / Cybersecurity, Procurement / Contracts, Launch / Range, Mission assurance, Other
• How would you describe your current program phase? Options: Requirements definition, Preliminary design, Detailed design, Assembly, Integration & Test (AIT), Flight ready / launch campaign, Operations

So... What’s Actually On The Ground?

• If your ground system had to carry the entire commissioning load tomorrow, where would it break first?
• List the physical ground assets you control or plan to reuse (antennas with size/band, RF heads, modems, racks).
• Which frequency bands and polarizations do your sites currently support? Options: S-band, X-band, Ka-band, UHF, Other
• Do you operate telemetry/command processing stacks today? If yes, please name vendor/software and version. Options: Yes — vendor & version provided, Yes — custom stack, No — plan to procure, Unknown
• Describe your ground network topology between stations and mission control (type and redundancy). Options: Private WAN with redundancy, Single private link, VPN over public internet, Direct fiber, Mixed / other, Unknown
• How much spare antenna/RF capacity exists to absorb additional passes or provide failover? Options: Full spare capacity, Partial spare capacity, Minimal spare capacity, No spare capacity, Unknown

Are Your Interfaces a Love Story or a Minefield?

• How confident are you that your spacecraft's command and telemetry interfaces will 'just work' with a third‑party ground stack on day one? Options: Completely confident, Somewhat confident, Unsure, Not confident at all
• Which telemetry/command protocols and framing schemes are in use or planned for this mission? Options: CCSDS TM/TC packets, CCSDS AOS, SLE, Custom proprietary framing, RTP/UDP, Other
• Do you have a spacecraft simulator available for integration testing (describe fidelity)? Options: Yes — full fidelity with RF emulation, Yes — software-only simulator, No simulator yet, Simulator under procurement
• If a vendor needs to run end-to-end tests, what level of access to your simulator would be possible? Options: Full access for vendor testing, Restricted access under NDA, Access during scheduled windows, Not accessible
• Are Interface Control Documents (ICDs), test vectors, and wire-level examples available and how complete are they? Options: Complete and validated, Partial and evolving, High-level only, Not documented
• What custom modulation, framing, timing, or encryption behaviors should integrators be aware of?

How Many Windows Do We Actually Get?

• If a pass is the currency of commissioning success, would you say you are short on passes, balanced, or oversupplied for the work ahead? Options: Severely short, Somewhat short, Balanced, Oversupplied, Unknown
• Which orbit type describes this mission and which orbital parameters are critical for coverage planning? Options: LEO (<2000 km), MEO, GEO, HEO, SSO / Polar / Sun-synchronous, Other
• What minimum elevation angle do you consider productive for commissioning passes? Options: >20°, 15°–20°, 10°–15°, <10°
• How many successful passes per day or per week do you require during the commissioning phase? Options: >20/day, 10–20/day, 5–10/day, 1–5/day, <1/day
• Which geographic regions are mission‑critical for latency or handover (select all that apply)? Options: North America, South America, Europe, Africa, Asia‑Pacific, Polar, Other
• Do you have coverage maps, link budget files, or simulations we can review? How are those currently generated? Options: Yes — produced with STK/Proprietary tools, Yes — produced with public tools, No, Available on request

What Keeps You Awake at 02:00?

• Which single failure mode during commissioning scares you most — and what would the impact be?
• Have past missions experienced commissioning-impacting outages? Tell us briefly what happened and the root cause if known.
• Where do you see single points of failure in the ground-to-spacepath today (select all that apply)? Options: Antenna hardware, RF front-end / LNA, Transport network, Mission control software, Identity/authentication & cyber, Personnel / ops procedures, Other
• What is your typical MTTR (mean time to repair) for critical ground assets? Options: <4 hours, 4–24 hours, 1–3 days, >3 days, Unknown
• Do you have hot/failover sites, spare-part inventory, or mutual support agreements to limit commissioning risk? Options: Comprehensive hot failover & spares, Limited spares/failover, No formal failover, In negotiation / planning

How Real Are Your Rehearsals?

• If your 'dress rehearsal' were a live pass tomorrow, how many issues would you expect to surface? Options: None — flawless, A few minor issues, Several significant issues, We haven't rehearsed
• Which end-to-end tests have you completed between your simulator and a ground stack? Options: Full E2E with RF, E2E software-only, Partial interface tests, None
• Do you run failure-scenario tests (antenna loss, degraded SNR, network outage) and do you have documented mitigation playbooks? Options: Yes — regularly, Occasionally, Planned but not executed, No
• How are timing and latency-sensitive commands validated (describe method and fidelity)? Options: Hardware-in-loop with time sync, Simulated latency tests, NTP/PTP only, Not validated
• How do you assess operator readiness and procedural proficiency before launch? Options: Formal certification & checklists, Tabletops and runbooks, On-the-job training, Not assessed

Security — Accreditation or Afterthought?

• If an accreditation audit occurred tomorrow, would your ground setup pass without major remediation? Options: Yes — passes now, Probably with minor fixes, No — major gaps, Unknown
• Which security standards or accreditations are required or desired for this program? Options: NIST 800‑53, DoD RMF, FedRAMP, ISO 27001, National / Agency-specific, None
• Must mission data traverse only isolated/private links, or is public-network transit acceptable with encryption? Options: Always private / isolated, Mostly private with VPN, Public network with strong encryption, Undecided
• What is the timeline for completing cybersecurity accreditation relative to launch? Options: Accredited now, Within 3 months, 3–6 months, 6–12 months, Not planned
• Have you budgeted for security remediation and for schedule contingency if accreditation slips? Options: Yes — budgeted & contingency, Partially budgeted, No budget, Unsure

Spare Parts, OEMs, and the Supply‑Chain Trap

• If a critical RF component became obsolete next year, how would your operations cope?
• Who are the primary OEMs for your antenna and RF hardware and what are typical lead times?
• Do you hold long-term maintenance contracts or SLAs for critical components? Options: Yes — 24/7 SLA, Yes — limited hours SLA, No formal contracts, Managed by third-party integrator
• Which spares are on site versus on order, and which items represent single‑point spares?
• How would operator turnover or loss of tribal knowledge affect maintaining custom integrations? Options: Minimal — well documented, Moderate — some tribal knowledge, Severe — dependent on few individuals, Unknown

If Launch Day Were Perfect…

• Describe the one acceptance criterion that would make you sign off on ground readiness without hesitation.
• Which telemetry and command performance metrics must be met at handover (examples: BER, link margin, command latency)?
• What operator proficiency level and training completion do you expect at handover? Options: Fully certified operators, Operators with supervised runs, Basic operator training only, Other
• What contingency capabilities must be guaranteed for the first week post-launch (select all that apply)? Options: Backup stations and spare links, Priority engineering support, Rapid on-site repair teams, Escalation playbook and war room, None formalized
• How do you prefer to structure risk-sharing during the launch campaign (acceptance gates, milestone payments, joint risk register, etc.)? Options: Acceptance gates with milestones, Performance-based payments, Joint risk register and shared governance, Other

Small First Step — What Would Reduce Risk Now?

• What’s the smallest, highest‑impact test or deliverable we could complete in the next 30–90 days to materially reduce your launch risk?
• Would you be open to a 48–72 hour simulator integration and RF smoke test to prove connectivity and basic telemetry/command flows? Options: Yes — schedule it, Yes — pending approvals, Maybe — cost dependent, No
• What specific access, credentials, or environments would a vendor need to run that pilot (IPs, certificates, simulator endpoints)?
• Who must be present or sign off for a vendor‑led integration run (names/roles)?
• What commercial or contracting barriers would block an immediate pilot (select all that apply)? Options: Procurement lead times, Security clearances, Budget approval, Contract negotiation, None / ready to proceed

Tell Us About Your Mission — Start Broad

• In one sentence, what is your mission trying to achieve?
• Which mission type best describes this program? Options: LEO communications, MEO/GEO communications, Earth observation / imaging, Science / exploration, Navigation / positioning, Technology demonstration, Government / defense, Other
• How locked is your launch schedule right now? Options: Firm launch date (hard-locked), Launch window with some flexibility, Target year but flexible, Not yet set / exploratory
• Who are the primary stakeholder groups that must sign off on ground readiness (pick all that apply)? Options: Mission engineering, Ground operations / flight ops, IT / Cybersecurity, Procurement / contracting, Program office / PMO, Launch services, Regulatory / spectrum, Other
• What are the top three measurable signals you will use to declare the ground segment ready for commissioning?

If We Missed First Contact, What Would It Cost?

• If first contact were delayed by a week, what are the concrete program consequences (schedule, cost, insurance, reputational)?
• Which specific commissioning or launch-week milestones are absolute cannot‑miss events for you? Options: First contact / first RF pass, Orbit determination & ephemeris, Payload checkout, Telemetry & command verification, Critical payload activation, Safe-mode recovery capability
• How many missed or degraded passes can your program tolerate before schedule or mission objectives are compromised? Options: None — zero tolerance, 1–2 critical passes, A short window (days) of degraded coverage, Flexible / depends on which passes
• Who—organizationally or contractually—bears the cost or schedule risk if ground readiness causes delays? Options: Customer / mission, Ground provider / contractor, Shared allocation, Insurance covers, Undetermined
• How long has the team been operating under launch-week pressure for this program? Options: New program (<6 months), Planning phase (6–18 months), Long-running (>18 months)

Where Your Ground System Might Be Hiding Fragile Assumptions

• Which assumption about your ground-to-space integration, if it turned out to be false, would most likely derail the schedule?
• Which of the following assumptions have already been validated through tests or emulator runs? Options: Spacecraft simulator fidelity, Time synchronization (NTP/PTP) across systems, Protocol compatibility (CCSDS / custom frames), RF performance at low-elevation, Network latency and routing
• Do you have a spacecraft simulator available for vendor use, and at what fidelity? Options: Full flight model including RF emulation, Functional simulator (telemetry/commands) only, Limited RF-only simulator, No simulator available for external teams
• Tell us about a past integration surprise (what happened, how long it took to resolve, and the residual risk today).
• On a scale of 1–10, how would you rate your current integration risk and what drives that score? Options: 1–2, 3–4, 5–6, 7–8, 9–10

Show Me Your Current World — Let’s Map Reality

• Which parts of your existing ground network do you trust under launch-week pressure, and which parts give you pause?
• List the ground assets currently in place or committed (antennas, TT&C centers, NOCs, simulators), with location and status if possible.
• For vendor integration and testing, what level of access is available for each asset? Options: Full remote access with credentials/VPN, Limited remote access (sandboxed), On-site access required under escort, No external access permitted
• How complete and version-controlled is your Interface Control Document (ICD) and systems documentation? Options: Complete and maintained, Mostly complete with a few gaps, Partially documented, several gaps, No formal ICD / undocumented
• Do you have formal configuration management and version control for ground software and RF equipment? Options: Yes — formal CM system & change control, Informal processes in place, Ad-hoc / manual tracking, No CM in place
• Are there site-specific constraints we should know (power limits, local RF noise, restricted access windows, customs/import issues)? Please list.

The RF Moment: Where Link Margins Meet Reality

• Describe the RF scenario most likely to push your margins to failure — low elevation, interference, pointing errors, or other — and why it remains unresolved.
• Which RF bands will you rely on for telemetry/command and for payload downlink? Options: S-band, X-band, Ka-band, UHF/VHF, Other (please specify)
• What minimum link margin (dB) do you require for critical passes (telemetry/command)? Options: >6 dB, 4–6 dB, 2–4 dB, <2 dB / marginal
• Have RF interference and site noise surveys been completed for the planned stations? Options: Completed recently (within 12 months), Completed previously (older than 12 months), Planned but not executed, Not planned
• Do you require advanced RF features from the ground provider (Doppler compensation, adaptive coding & modulation, real-time link adaptation)? Options: Yes — full set required, Some features required (specify), No — basic TT&C only
• Are there spectrum coordination or licensing constraints that could affect pass availability? Options: Yes — pending coordination, Yes — licensed and cleared, No major constraints, Unsure / need support

Security & Compliance — What Keeps Your CISOs Awake?

• If cybersecurity accreditation slips by even a month, what program consequences would you face (operational, contractual, launch hold)?
• Which compliance or accreditation standard is required for this program? Options: NIST/FedRAMP, DoD IL / Agency-specific IL, ISO 27001, CNSS / National security standard, Agency-specific security framework, Other
• What is your current accreditation stage for the ground segment (e.g., ATO, in process, not started)? Options: Accredited / ATO in place, In process with POA&M, Not started, Unknown / depends on vendor
• Who owns cybersecurity sign-off and what are the primary outstanding objections or requirements from that authority?
• Will the ground system require air-gapped networks, or will tightly controlled VPN tunnels be acceptable? Options: Air-gapped required, Dedicated VPN with strict controls, Standard VPN with monitoring, Undecided
• Have you completed threat modeling and penetration testing for ground components, and when was the last test? Options: Yes, within last 12 months, Yes, older than 12 months, Planned but not executed, No testing performed

People, Training, and Long-Term Care — Who Owns the Ship After Handover?

• Who will be awake and empowered at 02:00 to fix a ground system outage on day one of commissioning?
• What operational model do you plan after handover? Options: Customer-run operations, Provider-managed operations, Hybrid / shared ops, Third-party managed
• How many full-time operators (or FTE-equivalents) do you anticipate needing for nominal operations? Options: 1–2, 3–5, 6–10, 10+
• What level of operator training and certification do you require before handover? Options: Full certification with exam & sign-off, Hands-on lab & simulator training, Classroom / runbook walkthroughs, No formal training required
• What is your spares strategy for critical RF and antenna components? Options: On-site spares with SLA, Regional spares pooling, Vendor-managed spares, No spares plan yet
• How would you like software updates, patches, and feature requests to be handled over the lifecycle? Options: Scheduled releases with change control, On-demand patches with approval, Customer-managed updates, Hybrid / negotiated per change

Decision Signals — What Would Move This Deal Forward?

• What procurement, governance, or cultural habit has most delayed past ground-system awards—and what single change would accelerate you now?
• Where are you in the procurement lifecycle today? Options: Requirements definition, RFP / RFQ drafting, RFP issued / evaluating proposals, Negotiation / contracting, Awarded / post-award
• Who are the decision-makers and approvers (titles or roles) that must sign the contract?
• What are the top three evaluation criteria likely to decide the award? Options: Schedule certainty / delivery timeline, Price / total cost of ownership, Technical heritage & proven performance, Support & lifecycle commitments, Cybersecurity & compliance posture, Performance guarantees / SLAs
• Are you open to a paid pilot, experiment, or limited acceptance milestone ahead of full contract award? Options: Yes — paid pilot, Yes — limited scope trial, Maybe / depends on terms, No
• What contractual terms or risk allocations are non-negotiable for your organization (e.g., liquidated damages, indemnities, acceptance criteria)?

Starting Together: What Brought You Here?

• Briefly describe your mission and the single most important ground-side outcome you need at separation (T0).
• What is your launch date and which timeline constraints are firm vs. flexible? Options: Firm launch date / no flexibility, Small buffer (days–weeks), Moderate buffer (1–3 months), Flexible / TBD
• Which mission profile best matches your program? Options: LEO single satellite, LEO constellation, MEO/HEO, GEO, Government science mission, Other
• Where are you in procurement and systems design right now? Options: Requirements defined, seeking vendors, RFP issued / evaluating proposals, Contracting underway, Design and integration phase, Installation scheduled, Post-installation
• What has been the most frustrating part of past ground integrations (if any)? Tell a brief story—what happened and how did it impact the program?

What Would Keep You Up at Night Before Launch?

• If contact were lost on first passes, how severe would that be for your mission—and why might that happen? Options: Mission-critical failure, Severe delay to commissioning, Manageable with contingency, Low impact
• Which specific failure modes worry you most (e.g., RF margin at low elevation, timing/latency, simulator incompatibility, cybersecurity hold-ups)? Options: RF margin at low elevation, Antenna pointing / mechanical failures, Network latency or jitter, Telemetry/command protocol mismatch, Cybersecurity accreditation delays, Spare parts logistics, Other
• How often have these failure modes showed up in previous programs, and how long did resolving them typically take? Options: Never, Rarely (1–2 times), Occasionally (a few times), Frequently
• What emotional or political consequences do you face internally if the ground is late (e.g., program cost overrun, leadership scrutiny, lost launch windows)? Options: Major political/career risk, Significant budgetary pressure, Schedule reshuffle, Minor criticism, Other
• Which contingency measures do you already plan to rely on, and where do you feel those measures are weakest?

Where Are Your Interfaces Most Likely to Break?

• What assumptions are you making about telemetry/command interfaces that, if wrong, would derail commissioning?
• Which interface standards and protocols must we validate against your spacecraft (select all that apply)? Options: CCSDS TM/TC, SLE, TCP/UDP custom payload, Proprietary framing, Encrypted link with custom key management, Other
• Do you have a spacecraft simulator we can use for factory and on-site integration, and what access constraints exist? Options: Full simulator access (local), Remote simulator access with test vectors, Limited simulator access (time-limited), No simulator available yet
• How mature are your interface documents (ID, ICD) and how often do they change? Options: Stable / baseline frozen, Draft with occasional updates, Changing frequently, No formal ICD yet
• What specific bit-level, timing, or encryption checks would you expect as part of acceptance—please list the top three.

If We Could Guarantee Coverage, What Would You Ask For?

• Imagine we promised a firm coverage and margin profile for every critical pass—what would that change for your team?
• What minimum pass duration and contact frequency are required during commissioning and routine ops? Options: Multiple long passes per day, Daily medium passes, Several short passes per day, Occasional passes as-needed
• What link margin (dB above threshold) do you need at worst-case elevation to feel confident? Options: >10 dB, 6–10 dB, 3–6 dB, <3 dB but mitigated
• Which geographic sites or regions are must-haves versus nice-to-haves for your orbit and latency needs?
• How quickly do you expect a backup station online if a primary site fails (response SLA)? Options: Hours, 24 hours, 72 hours, Weeks

Money, Risk, and the Tradeoffs You Can't Ignore

• If you had to trade budget for reduced schedule risk or vice versa, which would you prioritize and why? Options: Prioritize schedule, Prioritize budget, Balance both equally, Depends on phase
• Which commercial terms feel non-negotiable (e.g., fixed-price milestone, SLA for passes, liability cap, acceptance criteria)? Options: Fixed-price milestones, Defined SLAs, Acceptance criteria tied to tests, Limited liability cap, Long-term maintenance commitments, Other
• How do you prefer risk be allocated between supplier and customer on items like site readiness, simulator availability, and cybersecurity accreditation? Options: Majority on supplier, Shared 50/50, Majority on customer, Case-by-case
• What budget contingency do you have for unexpected integration or spares costs (percentage or absolute)? Options: None, 5–10%, 10–20%, >20%
• Have contracting timelines or approval gates in your organization historically delayed ground contracts? If so, how long and where?

Who Really Decides, and How Fast?

• Who are the critical decision-makers for ground procurement and acceptance, and what outcomes do each of them care about most?
• Which decisions need in-person sign-off vs. programmatic email approval, and who holds those authorities? Options: In-person sign-off required, Email/programmatic approval ok, Board/steering committee required, Other
• What typical review cadence and lead times do we need to design for (e.g., design review, CDR, acceptance test signoff)? Options: Weekly, Bi-weekly, Monthly, Ad-hoc
• If approval gets stalled, what escalation path has worked best for you (roles, timeframe)?
• Who else outside engineering must be comfortable with the handover (procurement, security, legal, operations)? Options: Procurement, IT/Cybersecurity, Legal/Contracts, Operations/Ops Center, Senior leadership, Other

Readiness: What Would Make You Sleep Better the Week Before Launch?

• Which single validation (test, certificate, or demonstration) would remove your anxiety entirely?
• What acceptance criteria must be met for you to accept handover—list measurable items (e.g., end-to-end latency, successful automated passes, bit error rate).
• How do you want operator proficiency demonstrated (shadow ops, simulation exam, live pass supervision)? Options: Shadow ops, Simulation exam, Live supervised passes, Formal certification
• What spare parts, on-site spares, or logistic agreements are required to meet your risk tolerance? Options: On-site spares, Regional spares pool, Guaranteed delivery SLA, No specific spares required
• What cybersecurity accreditation milestones or paperwork must be complete before on-site integration or handover? Options: Full accreditation/cert, Interim authorization, Plan with timeline, Customer-managed

The Human Factor: Who Must Be Proud to Operate This?

• If your operations team doesn't feel ownership of the system at handover, what negative outcomes follow?
• What baseline skills and certifications do your operators already have, and where will we need to upskill? Options: Telemetry processing, Antenna ops, RF troubleshooting, Network ops, Cybersecurity operations, Other
• How much hands-on training time do you expect per operator to reach proficiency? Options: 1–2 days, 3–5 days, 1–2 weeks, Multiple weeks
• Which training formats work best for your team (classroom, simulator-led, on-site shadowing, recorded modules)? Options: Classroom, Simulator-led, On-site shadowing, Recorded modules, Blended approach
• How should operational runbooks, failure playbooks, and escalation procedures be delivered and maintained to best serve your team? Options: Static documents, Living wiki, Integrated runbook tool, Training + doc bundle

Governance & Long-Term Support: What Keeps Your Future Healthy?

• Over a 5–15 year mission life, what support commitments matter most (spares availability, software updates, feature upgrades, SLA response times)? Options: Spares availability, Regular software updates, Feature roadmap guarantees, Fast SLA response, Dedicated account team
• How do you prefer long-term commercial models: CAPEX turnkey, OPEX managed service, or hybrid? Options: CAPEX turnkey, OPEX managed service, Hybrid model, Unsure / depends
• What metrics would you track jointly in a governance cadence to ensure ongoing mission health (e.g., pass success rate, mean time to repair, P1 incident count)? Options: Pass success rate, Mean time to repair (MTTR), P1/P2 incident counts, Software patch latency, Security incident rate
• What cadence and forum do you want for program governance after handover (weekly ops, monthly review, quarterly steering)? Options: Weekly, Bi-weekly, Monthly, Quarterly, Ad-hoc
• Are there any regulatory, export control, or partner obligations that will shape long-term support or data sharing? Options: ITAR/EAR/export control, Classified handling, Partner data-sharing agreements, None known