150 likes | 157 Views
Commercial Range User Requirements Process. Mr. Kelvin Coleman Lt. Col. Tim Brown October 26, 2005. Overview. Background/History Past Results Responsive Space Era Industry Involvement. History.
E N D
Commercial Range User Requirements Process Mr. Kelvin Coleman Lt. Col. Tim Brown October 26, 2005
Overview • Background/History • Past Results • Responsive Space Era • Industry Involvement
History • IWG Report (Feb. 2000) on the Future Use and Management of the U.S. Space Launch Bases and Ranges • Finding: Commercial sector range users have a limited voice in determining requirements, plans, investments, etc. associated with maintaining, improving, and modernizing the ranges • Finding: Federal government has no formal process for gathering, validating , or advocating commercial sector requirements • IWG recommended alternative management structures be stood up to allow and provide greater user voice for range improvements and modernization. • Desired outcome: On-going process for communicating and considering commercial range user requirements • AF/DOT/DOC MOA (February 2002) • We’ve had two calls for requirements/recommendations • 2001 call yielded 7 requirements • 2003 call yielded 0 requirements
Need for Process • 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
Question: Is there a need to continue the process in 2006 and beyond?
Commercial Requirements Timeline CYXX Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec POM Inputs to HAF DoT Solicit Industry FY - I&M Initiation Process Requirements Appeals and ARTWG DoD Provide Project Status DoT Provide input to DoD Projects within requirements baseline/ Commercially funded projects DoD Determine Overlap & Provide Feedback RVB Process DoD Determine Implementation & Cost Projects Unfunded/new capabilities meeting AF needs; initiate requirements process, if required
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 & Test Range (RLTR) 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 RLTR 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
Responsive Space Payload Vehicle Range Preparing for Responsive Space Era - Responsive Launch & Test Range (RLTR) 3 DoD components: • Force application from space • Counterspace missions • Tactical force enhancement Responsive Launch & Test Range (RLTR) is the planned next-generation range to support responsive space requirements
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
Invitation to Industry • In concert with the Memorandum of Agreement (MOA) on Spacelift Range Commercial Requirements Process, AFSPC/DRFG invites industry to participate in establishing next-generation Launch and Test Range (LTR) 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
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
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
Transformational Comm (TC) Ÿ Ÿ Ÿ Ÿ Ÿ Ÿ CAOC RLTR 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 RLTR in support of responsive launch, routine launch, and T&E missions