Commercial Range User Requirements Process

1. Commercial Range User Requirements Process Mr. Kelvin Coleman Lt. Col. Tim Brown May 23, 2006

2. Agenda • Background • Process Overview • Responsive Space Era • Industry Involvement • LOSWG Role

3. Background • White House led IWG Report (Feb. 2000) on the Future Use and Management of the U.S. Space Launch Bases and Ranges • Findings: • Commercial sector range users have a limited voice in determining requirements, plans, investments, etc. associated with maintaining, improving, and modernizing the ranges • Federal government has no formal process for gathering, validating , or advocating commercial sector requirements • Recommendation: DOT, DOC, and USAF stand up an on-going process for communicating and considering commercial range user requirements • Action: AF/DOT/DOC MOA (February 2002) establishing process roles and responsibilities

4. Commercial Requirements Process POM Inputs to HAF 1. Industry Identifies Rqmnts FY - I&M Initiation 2. Pass rqmnts to FAA Appeals? FAA & DoC Unique commercial rqmnts 3. FAA passes rqmnts to USAF for evaluation RVB Process Projects w/in rqmnts baseline 4. DoD Provides Status Determine Implementation & Cost Projects Unfunded/new capabilities meeting AF needs; initiate requirements process, if required USAF

5. Responsive Space Payload Vehicle Range Preparing for Responsive Space Era - Responsive Launch Traffic Control (RLTC) 3 DoD components: • Force application from space • Counterspace missions • Tactical force enhancement Responsive Launch Traffic Control (RLTC) is the planned next-generation range to support responsive space requirements

6. Range Mission • Responsibilities • C2 of in-flight launch vehicles (positive control) • Protect the public per public law • Collect vehicle performance data • Functions performed • Flight safety analysis and operations • Telemetry collection and dissemination • Vehicle tracking, commanding, and imagery • Weather observation, modeling, and forecasting • Communications backbone • Hazard corridor surveillance/clearing • Planning and scheduling Applicable now and in the future

7. Notional DoD RLTC Capabilities

8. Invitation to Industry • In concert with the Memorandum of Agreement (MOA) on Spacelift Range Commercial Requirements Process, AFSPC/A5F invites industry to participate in establishing next-generation Responsive Launch Traffic Control (RLTC) performance requirements • Iterative process with increased definition developed at appropriate acquisition milestones • Characteristics and attributes needed prior to Analysis of Alternatives (AoA) • Functional area (comm, weather, tracking, etc.) parameters needed for Concept Development Document (CDD) • Identifying architecture solutions and innovative approaches to satisfying deficiencies comes later MOA provides framework for involvingall stakeholders in vetting “national” set of requirements

9. Notional DoD Acquisition Timeline MS MS MS A B C FOC IOC Production & Deployment System Development & Demonstration Concept Refinement Operations & Support Technology Development LRIP FRP ICD Stage II CDD CPD AoA Plan Modifications AoA AFROCC AFROCC AFROCC RSR RSR RSR JROC JROC JROC 2010 2018 2005 2008 2009 2014 2016 2022 Now

10. LOSWG Role • Conduct regularly scheduled discussions on industry’s needs for range improvements • Identify Collective Industry Requirements • Format Requirements • Prioritize Requirements • Communicate requirements via COMSTAC to the FAA

11. BACKUPS

12. MOA Purpose • MOA states “The process is defined as a formal, repeatable process for collecting commercial sector range support and modernization requirements, communicating these requirements to the AF, and considering these requirements in the existing AF requirements process.” • Prior to the MOA there was no formal way to communicate mid and long term requirements for range support and modernization • The Universal Documentation System is an effective way to communicate near-term requirements/needs

13. Commercial Requirements Process:1st Cycle Results • Demonstrate and certify GPS Metric Tracking capabilities • Status: In-work • Demonstrate and certify space-based telecommunications capabilities, demonstrate and certify autonomous flight safety systems • Status: Responsive Launch Traffic Control (RLTC) era • Additional downrange radar capability (for demonstration flights) • Status: AFSPC prepared to mitigate when need arises • Command destruct receiver freq change/technology upgrade – USAF should fund the development, integration, and qualification of a destruct system • Status: EELV conversion planned • Provide an integrated Air Force range vision and strategy • Status: Evolution toward RLTC Concept - Continue DoD corporate process • Ensure consideration of RLV capabilities and concepts in range safety rules • Status: Interagency Common Standards Rule-making. Risk criteria remains unchanged, but increased reliability expected to enhance flexibility • Provide long term access to space launch property • Status: AF’s ‘02 legislative proposal was killed in H&S conference w/o explanation Lessons Learned: Greater opportunities to incorporate commercial needs as part of next-generation range acquisition

14. Stakeholders • USSTRATCOM – warfighter advocate • AFSPC • National security (DoD, NRO, other) • T&E community • Ballistic missiles (ICBMs, SLBMs, MDA) • Guided weapons • Aeronautical programs • NASA, FAA, and commercial industry (launch providers, spaceports) The ranges are a national asset, of which the Air Force is the steward

15. Transformational Comm (TC) Ÿ Ÿ Ÿ Ÿ Ÿ Ÿ CAOC RLTC Force Application ScenarioForce Application from Space Scenario for 2018 Global Positioning System (GPS) Eastern Region Western Region FAA MCC CMOC HDBT Current launch ranges will be absorbed into RLTC in support of responsive launch, routine launch, and T&E missions