Upload
oona
View
28
Download
0
Embed Size (px)
DESCRIPTION
Civil Input to GPS III. PNT Advisory Board Meeting 16 Oct 08. HQ AFSPC Mr. Hank Skalski, OST Col Dave Buckman, A5P Peterson AFB, CO. Overview. Purpose Interagency Requirements Process (IRP) Nominal IFOR Approval Cycle Overall Approval Process GPS IIIB CDD Schedule - PowerPoint PPT Presentation
Citation preview
Working together todayto meet the
Positioning, Navigation and Timingneeds of tomorrow
Interagency Forum for Operational Requirements
Civil Inputto
GPS IIIPNT Advisory Board Meeting
16 Oct 08
HQ AFSPCMr. Hank Skalski, OSTCol Dave Buckman, A5PPeterson AFB, CO
Overview
• Purpose• Interagency Requirements Process (IRP)• Nominal IFOR Approval Cycle• Overall Approval Process• GPS IIIB CDD Schedule• Geodetic Requirement (Satellite Laser Reflectors
[SLRs])• Distress Alerting Satellite System (DASS)• Wrap Up
Purpose
• Describe GPS interagency requirements process• Provide information on candidate GPS
requirements/payloads• Geodetic
• DASS
Interagency Requirements Process
ValidatedCivil
Requirements
ValidatedInteragency
Requirements
ValidatedMilitary
Requirements
InteragencyRequirements
Board(IRB)
DOTExtended
Pos/Nav WG
Interagency Forumfor Operational
Requirements (IFOR)
InteragencyRequirements
OversightCouncil(IROC)
JROCApprove Military
Requirements
JCBCoordinate and
Adjudicate MilitaryRequirements
NC FCBCoordinate and
Adjudicate MilitaryRequirements
Civil Panel Military Panel
DOTExtendedPos/NavExCom
Approve CivilRequirements
Civil Department
RequirementsProcesses
Service’s &Defense AgencyRequirements
Processes
Nominal IFOR Approval Cycle
Send to IFOR For Review
ReceiveReq’t & AoA
ResolveComments
Prepare Package for Co-Chairs
Approve or Send for Rework
Incorporate into GPS Req’ts Documents
Day 0 Days 1-60 Days 61-90 Days 91-104 Day 105 Dependent on Req’t
Cycle
• Nominal Cycle Time is 105 days plus time associated with preparing documents
• Following document preparation, requirement documents (such as CDDs) will enter JCIDS process
EnterJCIDSProcess
Overall Approval Process
DEPSECDEF Approve?
EndInclude
Requirement on GPS
Yes
Cost/Funding Assessment
Security Assessment
Technical Assessment
Start
Exclude Requirement
from GPS
No
No
Yes
JCIDS & IRPProcesses Approve
Requirement?
Is this a secondary payload?
No
Yes
ValidatedCivil
Requirements
ValidatedInteragency
Requirements
ValidatedMilitary
Requirements
InteragencyRequirements
Board(IRB)
DOTExtended
Pos/Nav WG
Interagency Forumfor Operational
Requirements (IFOR)
InteragencyRequirements
OversightCouncil(IROC)
JROCApprove Military
Requirements
JCBCoordinate and
Adjudicate MilitaryRequirements
NC FCBCoordinate and
Adjudicate MilitaryRequirements
Civil Panel Military Panel
DOTExtendedPos/NavExCom
Approve CivilRequirements
Civil DepartmentRequirements
Processes
Service’s &Defense Agency
RequirementsProcesses
ValidatedCivil
Requirements
ValidatedInteragency
Requirements
ValidatedMilitary
Requirements
InteragencyRequirements
Board(IRB)
DOTExtended
Pos/Nav WG
Interagency Forumfor Operational
Requirements (IFOR)
InteragencyRequirements
OversightCouncil(IROC)
JROCApprove Military
Requirements
JCBCoordinate and
Adjudicate MilitaryRequirements
NC FCBCoordinate and
Adjudicate MilitaryRequirements
Civil Panel Military Panel
DOTExtendedPos/NavExCom
Approve CivilRequirements
Civil DepartmentRequirements
Processes
Service’s &Defense Agency
RequirementsProcesses
GPS IIIB CDD Schedule
Days Date Days Date1 Submit RSR Request to AF/A5RD 10-Jan-12 10-Jan-122 RSR Briefing to A-A5R 21 31-Jan-12 21 31-Jan-123 HPT Commences 30 1-Mar-12 30 1-Mar-124 HPT Ends 11 12-Mar-12 11 12-Mar-125 Internal Coordination & Cleanup 30 11-Apr-12 60 11-May-126 O-6 Review (MAJCOM, Air Staff, Joint Staff) 21 2-May-12 28 8-Jun-127 Sponsor Completes O-6-Level Comment Resolution 15 17-May-12 30 8-Jul-128 Submit CRM/Doc/Brief for AFROCC 14 31-May-12 14 22-Jul-129 AFROCC 16 16-Jun-12 16 7-Aug-1210 Flag-Level Review (If required*) 21 7-Jul-12 28 4-Sep-1211 Flag-Level Comment Resolution (If required*) 15 22-Jul-12 30 4-Oct-1212 FCB 7 29-Jul-12 14 18-Oct-1213 JCB 7 5-Aug-12 14 1-Nov-1214 JROC 7 12-Aug-12 14 15-Nov-1215 Document Signed 14 26-Aug-12 30 15-Dec-12
TOTAL # of Days: 229 340
EventRegulatory Goal Realistic
Step
New Requirements - Geodetic
• Geodetic Requirements• Achieve a stable geodetic reference frame with an
accuracy at least ten times better than anticipated user requirements
• Maintain a close alignment of the WGS84 reference frame with the International Terrestrial Reference Frame
• Provide a quality assessment capability independent of current radiometric measurement used to determine GPS orbits and clock performance
• Ensure interoperability of GPS with other GNSSs through a common, independent measurement technique
Geodetic Requirements – Status
• Requirements and AoA submitted to IFOR - Apr 07• One GPS-based alternative (Satellite Laser Reflectors) with other
non-GPS alternatives• Sent out for review Apr 07
• No critical/substantive comments received
• Many favorable comments received
• IFOR letter to NASA approving Geodetic Requirements for inclusion in GPS IIIB CDD prior to entering JCIDS process – Aug 07• GPSW analysis had not been accomplished
• IFOR Requested GPSW review for GPS III satellite impacts• White papers provided in Jun 08 opposing implementation on SVs, but
also provided possible solutions
• Geodetic Requirements Working Group chartered by IFOR
Geodetic Requirements Working Group
• Intent is to fully explore all security, cost, and technical issues prior to entering the JCIDS process
• First meeting held 17 July 08• Attended by representatives from NASA, USGS, NRL,
NGA, DOT, USNO, SAF/USA, AF/A5R, GPSW, AFTAC and AFSPC/A5P
• Created roadmap to resolve issues
• Additional Technical Meeting held 26 Aug 08 to further explore technical issues
• Next meeting – Nov 08
Geodetic Approval Cycle
Send to IFOR For Review
ReceiveReq’t & AoA
CommentResolution
Prepare Package for Co-Chairs
Approve or Send for Rework
Approved for IIIB CDD
GPSW Analysis &Comment Resolution
EnterJCIDSProcess
• Requirements submitted Apr 07• IFOR approval Aug 07
• Did not include GPSW analysis• GPSW analysis provided Jun 08• Currently working identified technical issues• Anticipated completion 1 Dec 08
Distress Alerting Satellite System (DASS)
• The United States Government, specifically the U.S. Coast Guard, Department of Defense, and the National Oceanic and Atmospheric Administration, requires an enduring space-based capability to detect, locate, and relay distress alerts from emergency beacons carried by aviators, mariners and land-based users to search and rescue services.
• The federal government requires a capability:• To support the general public• To support civilian SAR efforts of the USCG and DoD
worldwide• To support military SAR operations worldwide• To meet international obligations under the Chicago
Convention
DASS – Status
• Requirements and AoA received 28 Jul 08• Not a GPS or PNT requirement – would be a secondary
payload
• Package sent out for IFOR review 1 Aug 08, comments due 1 Oct 08• Letter supporting requirements received from Joint
Personnel Recovery Agency
• Comments received and being adjudicated
• GPSW performing cost and technical analysis• USAF Red Team conducting national security
analysis
DASS Approval Cycle
Send to IFOR for Review
ReceiveReq’t & AoA
CommentResolution
Prepare Package for Co-Chairs
Approve or Send for Rework
Approved for IIIB CDD
Day 0
Days 1-60
Days 61-90 Days 91-104 Day 105
Task GPSW for Analysis
• Requirements and AoA received Jul 08• Comments received Oct 08• In Comment Resolution• GPSW still conducting cost/technical analysis• Anticipated completion Dec 08
EnterJCIDSProcess
Wrap Up
• Flexibility in the requirements development process is key – one size doesn’t fit all
• Geodetic and DASS requirements are being processed through the IFOR • Each has unique issues that require slightly different
handling