+ All Categories
Home > Documents > Commercial Range User Requirements Process

Commercial Range User Requirements Process

Date post: 08-Jan-2016
Category:
Upload: earl
View: 33 times
Download: 0 times
Share this document with a friend
Description:
Commercial Range User Requirements Process. Mr. Kelvin Coleman Lt. Col. Tim Brown May 23, 2006. Agenda. Background Process Overview Responsive Space Era Industry Involvement LOSWG Role. Background. - PowerPoint PPT Presentation
15
Commercial Range User Requirements Process Mr. Kelvin Coleman Lt. Col. Tim Brown May 23, 2006
Transcript
Page 1: Commercial Range User Requirements Process

Commercial Range User Requirements

Process

Mr. Kelvin ColemanLt. Col. Tim Brown

May 23, 2006

Page 2: Commercial Range User Requirements Process

2

Agenda

• Background• Process Overview• Responsive Space Era• Industry Involvement• LOSWG Role

Page 3: Commercial Range User Requirements Process

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:

1. Commercial sector range users have a limited voice in determining requirements, plans, investments, etc. associated with maintaining, improving, and modernizing the ranges

2. 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

Page 4: Commercial Range User Requirements Process

4

Commercial Requirements Process

FAA & DoC

2. Pass rqmnts to FAA

1. Industry Identifies Rqmnts

3. FAA passes rqmnts to USAFfor evaluation

Unique commercial rqmnts

Determine Implementation& Cost Projects

USAF

Unfunded/new capabilities meeting AF needs; initiate requirements

process, if required

Projects w/in rqmnts baseline

FY - I&M Initiation

POM Inputs to HAF

Appeals?

4. DoD Provides Status

RVB Process

Page 5: Commercial Range User Requirements Process

5

Preparing for Responsive Space Era - Responsive Launch Traffic Control

(RLTC)

ResponsiveSpace

Payl

oad V

ehicle

Range

3 DoD components:

Responsive Launch Traffic Control (RLTC) is the planned next-generation range to support responsive space requirements

• Force application from space• Counterspace missions• Tactical force enhancement

Page 6: Commercial Range User Requirements Process

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

Page 7: Commercial Range User Requirements Process

7

Notional DoD RLTC Capabilities

Current RangeInitial Responsive

Range (2010)Final Responsive

Range (2018)

Communications Connectivity

Commanding, telemetry, and tracking

Regional End of public

safety risk

ExtendedExisting SATCOM

Globally Transformational

Comm - enables positive weapons control

Flight Plan ApprovalDebris / toxic hazards

risk assessmentsAir space clearanceOn-orbit collision

avoidanceClearance into theater

for weapons release

1-2 Months

Prepare contingency plans to meet timelines

Select set of scenarios

Within hours

Capacity/Sortie rate2 per range

per weekLimited surge

Pre-planned missions

5-16 sorties per day

Wartime scenario

Page 8: Commercial Range User Requirements Process

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

Page 9: Commercial Range User Requirements Process

9

Notional DoD Acquisition Timeline

20162005 20092008 2010 2014

IOC

Technology Development

System Development& Demonstration

Production& Deployment

Operations & Support

FOC

LRIP

A B C

Concept Refinement

MS MS MS

FRP

CDD CPD

RSR

AoA Modifications

ICD Stage II

JROC

AFROCCRSR JROC

AFROCCRSR JROC

AoA Plan

AFROCC

Now

2018 2022

Page 10: Commercial Range User Requirements Process

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

Page 11: Commercial Range User Requirements Process

11

BACKUPS

Page 12: Commercial Range User Requirements Process

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

Page 13: Commercial Range User Requirements Process

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

Page 14: Commercial Range User Requirements Process

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

Page 15: Commercial Range User Requirements Process

RLTC Force Application ScenarioForce Application from Space Scenario for 2018

Current launch ranges will be absorbed into RLTC in support of responsive launch, routine launch, and T&E missions

FAAWestern Region

Global Positioning System (GPS)

Transformational Comm (TC)

Ÿ Ÿ Ÿ ŸŸ Ÿ HDBT

CAOCMCC

CMOC

Eastern Region


Recommended