1 / 15

Civil Input to GPS III

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

oona
Download Presentation

Civil Input to GPS III

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Civil InputtoGPS III PNT Advisory Board Meeting 16 Oct 08 HQ AFSPC Mr. Hank Skalski, OST Col Dave Buckman, A5P Peterson AFB, CO

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

  3. Purpose • Describe GPS interagency requirements process • Provide information on candidate GPS requirements/payloads • Geodetic • DASS

  4. Interagency Requirements Process Validated Civil Requirements Validated Interagency Requirements Validated Military Requirements DOT Extended Pos/Nav ExCom Approve Civil Requirements Interagency Requirements Oversight Council (IROC) JROC Approve Military Requirements JCB Coordinate and Adjudicate Military Requirements Interagency Requirements Board (IRB) DOT Extended Pos/Nav WG NC FCB Coordinate and Adjudicate Military Requirements Interagency Forum for Operational Requirements (IFOR) CivilDepartment Requirements Processes Service’s & Defense Agency Requirements Processes Military Panel Civil Panel

  5. Nominal IFOR Approval Cycle Incorporate into GPS Req’ts Documents Send to IFOR For Review Receive Req’t & AoA Prepare Package for Co-Chairs Approve or Send for Rework Resolve Comments Day 105 Day 0 Days 1-60 Days 61-90 Days 91-104 Dependent on Req’t Cycle Enter JCIDS Process • Nominal Cycle Time is 105 days plus time associated with preparing documents • Following document preparation, requirement documents (such as CDDs) will enter JCIDS process

  6. Overall Approval Process

  7. GPS IIIB CDD Schedule

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

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

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

  11. Geodetic Approval Cycle Prepare Package for Co-Chairs Approve or Send for Rework Approved for IIIB CDD Send to IFOR For Review Receive Req’t & AoA Comment Resolution GPSW Analysis & Comment Resolution Enter JCIDS Process • 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

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

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

  14. DASS Approval Cycle Send to IFOR for Review Receive Req’t & AoA Prepare Package for Co-Chairs Approve or Send for Rework Approved for IIIB CDD Comment Resolution Day 105 Day 0 Days 61-90 Days 91-104 Days 1-60 Enter JCIDS Process 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

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

More Related