Commercial-Spaceport Tenant-Operations Architect

The mandate

The programme has credible infrastructure concepts and prospective launch tenants, but neither defines how a multi-user site will actually allocate access, process payloads, protect airport activity and recover from a delayed or aborted campaign. Providers assume dedicated facilities and flexible windows; airport operators assume predictable closures; authorities require attributable safety and security decisions. The defined problem is to create a tenant operating model before leases, designs and service commitments harden incompatible assumptions.

The named deliverable is a Commercial Spaceport Tenant-Operations Architecture covering tenant qualification, campaign onboarding, site and information access, payload custody, hazardous operations, shared assets, scheduling, range interfaces, airspace and maritime coordination, customs, emergency command, weather decisions, abort recovery, maintenance, service charging and post-campaign closure. It will include authority matrices, tenant archetypes, campaign-state definitions, capacity models, reserved-versus-shared boundaries, evidence requirements and contract schedules requiring legal translation.

Five milestones govern six months. By week four, milestone one maps the current concept and twelve unresolved interface decisions. Week nine produces tenant archetypes and shared-resource demand. Week fourteen delivers alternative authority and commercial-service models. Week twenty concludes tabletop exercises for propellant incident, airspace denial, payload hold, weather delay and overlapping campaigns. At week twenty-four, the final milestone supplies the accepted architecture, service catalogue, facility implications, mobilisation backlog and investment decision paper.

Acceptance rests with the programme chief executive and Joint Authority Steering Committee, with statutory range, aviation, emergency, customs and security bodies retaining their determinations. Work is accepted only when two reference tenants can walk an entire campaign through named authorities and evidence gates; all five exercises close without an ownerless critical decision; airport-service consequences reconcile; and every facility recommendation traces to an agreed operating requirement rather than vendor preference.

The client provides site designs, prospective tenant assumptions, airspace and maritime studies, service concepts, emergency frameworks, security and customs requirements, environmental conditions and authorised specialists. Consultants will not license launches, certify facilities, approve payloads, direct live hazardous work, negotiate tenant contracts or conduct detailed engineering. Vehicle design, range-safety analysis, environmental approval and construction procurement are excluded; specialist conclusions remain attributed to the competent authorities.

Why this is external work

The programme team is organised around infrastructure packages, while prospective tenants describe needs from proprietary vehicle and campaign models. No internal group is neutral across provider, airport and public-authority boundaries, and early commercial enthusiasm makes challenge difficult. External operating architecture converts those perspectives into testable interfaces without assuming any regulator’s or launch operator’s accountability.

What you will own

• Map a reference campaign from tenant qualification through arrival, integration, launch attempt, recovery and site release.
• Segment tenant and campaign archetypes by vehicle, propellant, payload, cadence, exclusivity, hazard and support intensity.
• Define decision rights across tenant, spaceport, airport, range, emergency, security, customs and government authorities.
• Model shared-facility, specialist, access-window and disruption capacity under overlapping and extended campaigns.
• Exercise propellant, airspace, payload, weather and schedule-conflict scenarios with recorded authority and evidence gaps.
• Specify the tenant service catalogue, readiness evidence, change control, charging logic and facility requirements.
• Deliver the accepted architecture, contract inputs, investment choices and sequenced mobilisation backlog.

Candidate qualifications

• Has designed launch-site, spaceport, range, airport or similarly hazardous multi-tenant infrastructure operations.
• Can evidence an infrastructure or lease assumption changed after an end-to-end campaign walkthrough exposed conflict.
• Understands payload custody, hazardous processing, shared facilities, range interfaces, airspace, emergency command and campaign recovery.
• Has worked across commercial operators and sovereign authorities without claiming delegated regulatory or safety power.
• Can model low-frequency, high-consequence resource contention beyond average annual campaign forecasts.
• Produces operating requirements that engineers and commercial counsel can translate without losing decision accountability.

Non-negotiables

• Can work weekly in Abu Dhabi and lead three controlled launch-provider interface workshops.
• Will not certify safety, approve payloads, license activity or direct live hazardous operations through this engagement.
• Brings direct launch, range or comparable hazardous campus architecture; generic airport consulting alone is insufficient.
• Will record unresolved authority questions even where they delay leases or infrastructure commitment.

1. 49 words maximum. Which tenant assumption most often conflicts with a genuinely shared launch-site operating model?
2. 49 words maximum. Describe an exercise that changed a facility design because campaign recovery had been overlooked.
3. 49 words maximum. What unresolved authority would prevent you from recommending a tenant commitment?