National PNT Architecture Workshop at Volpe
Transcript of National PNT Architecture Workshop at Volpe
1
National PNT Architecture Workshop at Volpe
26 April 2007
Report Documentation Page Form ApprovedOMB No. 0704-0188
Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.
1. REPORT DATE 17 APR 2007 2. REPORT TYPE
3. DATES COVERED 00-00-2007 to 00-00-2007
4. TITLE AND SUBTITLE National PNT Architecture Workshop at VOLPE
5a. CONTRACT NUMBER
5b. GRANT NUMBER
5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S) 5d. PROJECT NUMBER
5e. TASK NUMBER
5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Department of Defense,National Security Space Office ,Washington,DC,20301
8. PERFORMING ORGANIZATIONREPORT NUMBER
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)
11. SPONSOR/MONITOR’S REPORT NUMBER(S)
12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited
13. SUPPLEMENTARY NOTES National PNT Architecture Workshop at Volpe National Transportation Systems Center in Cambridge,MA, on 26 Apr 2007
14. ABSTRACT
15. SUBJECT TERMS
16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as
Report (SAR)
18. NUMBEROF PAGES
46
19a. NAME OFRESPONSIBLE PERSON
a. REPORT unclassified
b. ABSTRACT unclassified
c. THIS PAGE unclassified
Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18
2
Agenda
• Welcome and Introductions• Background of National PNT Architecture Effort• National PNT Architecture Development Process
– Data Gathering– Concept Development– Analysis and Assessment
• Overview of Current Status and Future Direction• Interactive Session
– Architecture-Level Questions– Identified PNT Gaps for 2025– Technologies and Concepts
3
Agenda
• Welcome and Introductions• Background of National PNT Architecture Effort• National PNT Architecture Development Process
– Data Gathering– Concept Development– Analysis and Assessment
• Overview of Current Status and Future Direction• Interactive Session
– Architecture-Level Questions– Identified PNT Gaps for 2025– Technologies and Concepts
27-Apr-07 4
PNT Architecture Background
• Study requested by– Assistant Secretary of Defense for Networks and
Information Integration– Undersecretary of the Department of Transportation for
Policy– National Space-based PNT Executive Committee
• Justification– PNT Strategic Landscape is Changing
• Products– 20 year strategic outlook to guide near and mid-term
decisions on PNT capabilities
5
National PNT Architecture PerspectiveNational PNT Architecture Perspective
Enterprise Level Assessment to Ensure National PNT PreeminenceCross Community Forum to Achieve Common Understanding
2025 Strategic Environment
Political
Economic
Technology
PNT EnterpriseUsers / Missions
CONOPS
Policy
Communities
Capabilities
AcquisitionAssets & Infrastructure
Industry
2025 Strategic Objectives
Security
Economy
Pol-Mil Strength
Interactions
6
National PNT Architecture Scope
Military
HomelandSecurity
Civil
Commercial
Individual
Far Space
Near Space
Atmosphere
Surface
Urban
Enclosed
Under Surface
Space NavTerrestrial NavISR / Targeting
Traffic Management
LogisticsManufacturing
AgricultureCooperative
LocationGeo Science
TimingSecurity
Orientation
GNSS
GNSS Augmentation
TerrestrialNAVAIDS
Onboard / User Equip
Networks
Military
Civil
Commercial
International
USERS DOMAIN MISSIONS PROVIDERSSOURCES
Broad Scope Requires Innovative Approaches and Focused Analysis Efforts
7
PNT Architecture StakeholdersPNT Architecture Stakeholders
• National Security Space Office• Dept of Defense / Networks and
Information Integration• Dept of Transportation / RITA• Dept of Commerce• Dept of Homeland Security• Dept of State• NASA• National Space-Based PNT
Coordination Office• Dept of Transportation / FAA• Dept of Transportation / FHWA• Dept of Transportation / FRA• Department of Interior / USGS • National Security Agency• National Geospatial Intelligence
Agency
• US Army• US Navy• US Air Force• US Marine Corp• US Coast Guard• US Strategic Command• Joint Staff• Air Force Space Command• GPS Wing • Dept of Defense / S&T• US Naval Observatory • National Institute for Standards and
Technology • Joint Planning Development Office• Policy Board on Federal Aviation
8
Related Efforts & Upcoming DecisionsRelated Efforts & Upcoming Decisions
• Recent & Upcoming Decisions – Future of eLORAN– Future of NDGPS and High Accuracy NDGPS– Backup SATNAV Tasking – Backup PNT Needs (ADS-B, NGATS, Timing Infrastructure)– GPS III and OCX Acquisition Strategies
National PNT ArchitectureDOT and FAA
• Aviation Navigation Evolution RoadmapDOT and FAA
• Aviation Navigation Evolution Roadmap
National Space-Based PNT Coordination Office
• 5-Year Plan & Assessment• Alternate Financing Study
National Space-Based PNT Coordination Office
• 5-Year Plan & Assessment• Alternate Financing Study
DOD• DOD PNT S&T
Roadmap update
DOD• DOD PNT S&T
Roadmap update
NRO• Orientation Functional
Solutions Analysis
NRO• Orientation Functional
Solutions AnalysisUSSTRATCOM
• PNT Joint Capabilities Document• PNT Functional Solutions Analysis
USSTRATCOM• PNT Joint Capabilities Document
• PNT Functional Solutions Analysis
NSSO• NSS Program Assessment
• NSS Plan
NSSO• NSS Program Assessment
• NSS Plan
RAND• Ensuring Effective PNT
RAND• Ensuring Effective PNT
Joint Planning & Development Office• Next Generation Air Transportation System
Joint Planning & Development Office• Next Generation Air Transportation System
MAINTAIN SHARED SITUATIONAL AWARENESS
9
Agenda
• Welcome and Introductions• Background of National PNT Architecture Effort• National PNT Architecture Development Process
– Data Gathering– Concept Development– Analysis and Assessment
• Overview of Current Status and Future Direction• Interactive Session
– Architecture-Level Questions– Identified PNT Gaps for 2025– Technologies and Concepts
10
Purpose of NSSO ArchitecturesPurpose of NSSO Architectures
• Enterprise Level Guidance– High Level Capabilities– Fundamental Processes– Organizations– Infrastructure
• Similar to City Planning– Considerations for how people, buildings,
transportation, utilities work together– Effect of External Factors (e.g., weather,
state jurisdiction, etc.)– Objective is not to design all the buildings– May conduct detailed design of some
elements, primarily to gain understanding of higher level issues
11
Architecting Process Overview
Rob
ust
Fibe
rN
etw
ork
Airb
orne
Com
ms
Nod
e
Spac
eC
ross
links
MB
/MM
Te
rmin
al
Packet Network Over All Domains
Develop High Capacity Terrestrial Gateways
Traffic Model / Modeling and Simulation Supporting R & DCross-Banding
Treat Comm as an Enterprise
Recommendations
Commercial
Government
Space
Terrestrial
Centralecentralized
BA
C
D
Current Evolved Architecture
As-Is
Trade Space Definition
How could we do it?
Key Capability Identification
What have we learned?
Stakeholder ParticipationIndustry Input
User/Operator Input
Stakeholder ParticipationIndustry Input
User/Operator Input
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
0 1 2 3 4 5
Maturity Model Level
Val
ue
How well do they work, what do
they cost, etc.?
Design Evaluation
Current Current ReqmtsReqmtsFuture NeedsFuture Needs
Potential Future Needs
What do we need to do?
What can we do it with?
Technology
Operational Concepts
How do we want to do it?
Transition Plan
What needs to be done, when?
GPS
GPS Augmentations
External PNT Sources
Users Navwar
Autonomous PNT SourcesSupporting Infrastructure
GPS
GPS AugmentationsGPS Augmentations
External PNT Sources
External PNT Sources
UsersUsers NavwarNavwar
Autonomous PNT SourcesAutonomous PNT SourcesSupporting InfrastructureSupporting Infrastructure
Concepts & Designs
What mightthey look like?
12
Architecting Process Overview
Rob
ust
Fibe
rN
etw
ork
Airb
orne
Com
ms
Nod
e
Spac
eC
ross
links
MB
/MM
Te
rmin
al
Packet Network Over All Domains
Develop High Capacity Terrestrial Gateways
Traffic Model / Modeling and Simulation Supporting R & DCross-Banding
Treat Comm as an Enterprise
Recommendations
Commercial
Government
Space
Terrestrial
Centralecentralized
BA
C
D
Current Evolved Architecture
As-Is
Trade Space Definition
How could we do it?
Key Capability Identification
What have we learned?
Stakeholder ParticipationIndustry Input
User/Operator Input
Stakeholder ParticipationIndustry Input
User/Operator Input
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
0 1 2 3 4 5
Maturity Model Level
Val
ue
How well do they work, what do
they cost, etc.?
Design Evaluation
Current Current ReqmtsReqmtsFuture NeedsFuture Needs
Potential Future Needs
What do we need to do?
What can we do it with?
Technology
Operational Concepts
How do we want to do it?
Transition Plan
What needs to be done, when?
Data Gathering Phase
GPS
GPS Augmentations
External PNT Sources
Users Navwar
Autonomous PNT SourcesSupporting Infrastructure
GPS
GPS AugmentationsGPS Augmentations
External PNT Sources
External PNT Sources
UsersUsers NavwarNavwar
Autonomous PNT SourcesAutonomous PNT SourcesSupporting InfrastructureSupporting Infrastructure
Concepts & Designs
What mightthey look like?
Concept Development PhaseAnalysis Phase
Assessment Phase
13
? ?
APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN3rd Quarter FY07
CY 2007CY 20062nd Quarter FY071st Quarter FY073rd Quarter FY06 4th Quarter FY06
Second Cycle(4 Aug – 30 Mar)
JUL AUG SEP4th Quarter FY07
?
First Cycle(23 May – 3 Aug)
Third Cycle(1 Apr – 31 Jul)
?
PNT Needs & Shortfalls
Future Environment Description
PNT Baseline
PNT Evolved Baseline
List of PNTTechnologies
Operational Concepts
Tradespace Description
Alternative Architectures
Initial List of Capabilities
Initial Analysis Results
Interim Findings
Future Environment Description
PNT Evolved Baseline
List of PNTTechnologies
Operational Concepts
Tradespace Description
Alternative Architectures
Initial Recommended
Capabilities
Revised Analysis Results
Recommended Capabilities
Final Findings & Recommendations
Investment Roadmap
Lifecycle Cost Assessment
ADT – ArchitectureDevelopment TeamWG – Working GroupR&V – Reviewand Validation
DCG – DecisionCoordination Group
FCB/JROC/MRB
Industry Day
? ?
Legend
PNT TOR
PNT Needs & Shortfalls
Future Environment
Outline
PNT Baseline
PNT Evolved Baseline
List of PNTTechnologies
Operational Concepts
Tradespace Outline
Alternative Architectures
Outline
Initial Outline of Capabilities
Identify Analysis Needs
and ToolsPreliminary
Findings
PNT Architecture Schedule
14
Draft Draft ““AsAs--IsIs”” PNT Architecture (2007)PNT Architecture (2007)
EMI EMI
C2
Infrastructure & Enablers
GALILEO (GIOVE-A)
GPSGLONASS
GPSCompass
WAAS
EGNOS
TASS
LORAN-C
VOR/DME, TACAN
ILS, NDB
Tracking
N
SEW
Compass
Clock
INS
Celestial Navigation
Star Trackers
Commercial Augmentations
Time Transfer
Time TransferTercom
Doppler
Pedometers
Commercial Augmentations
GDGPS IGS
CORS
WAGEZAOD
Time Transfer
EnvironmentWeather
Geo-politicalFiscal
SpectrumNavwarInterference
ENABLERS & INFRASTRUCTURE
NAVCENNAVCEN
USNO NISTStar Catalogs
Cryptography
Modeling
Standards Science & Technology
PoliciesMapping/Charting/GeodesyElectro Optical Info.
Reference Frames NGA NGSNSA
TestingIndustrial Base
Laser Ranging Network
GPSOCGPSOC NOCCNOCCUser Interface OrgsUser Interface Orgs
Version16 Apr 2007
NDGPSMDGPS
Time Transfer
Repeater
MTSAT
Launch
Cell Network
PNT
GBAS Cat-IASIAAI
15
Evolved Baseline (EBL): 2007 Evolved Baseline (EBL): 2007 -- 20252025C
apab
ility
AsAs--IsIsArchitectureArchitecture Architecture Emphasis
Now 5 years 10 years 15 years 20+ yearsSystem Emphasis
EBL
Near and Mid Term Decisions
Guided by Architecture
Based on Long Term
Vision
“Should-Be”Architecture
Without Enterprise
Architecture Strategy
16
EBL (2025): How the future might look
EMI EMI
C2
Infrastructure & Enablers
SCA GALILEO GPS
GLONASS
GPS Compass
IRNSS
QZSS
WAAS
EGNOS
GAGAN
TASS
eLORAN
VOR/DME, TACAN
ILS, NDB
Tracking
N
SEW
Compass
Clock
INS
Celestial Navigation
Star Trackers
Commercial Augmentations
Time Transfer
Time TransferTercom
Doppler
Pedometers
NigComsat -1 SBAS
Commercial AugmentationsASI
JPALS
GDGPS IGS
CORS
WAGEZAOD
Time Transfer
EnvironmentWeather
Geo-politicalFiscal
SpectrumNavwarInterference Technological
Demographics
ENABLERS & INFRASTRUCTURE
NAVCENNAVCEN
USNO NISTStar Catalogs
Cryptography
Modeling
Standards Science & Technology
PoliciesMapping/Charting/GeodesyElectro Optical Info.
Reference Frames NGA NGSNSA
TestingIndustrial Base
Laser Ranging Network
GPSOCGPSOC NOCCNOCCUser Interface OrgsUser Interface Orgs
Version 16 Apr 2007
NDGPSMDGPS
Time Transfer
Repeater
MTSAT
Launch
Cell Network
PNT
GBAS Cat-I
17
PNT User Perspectives (2025)
Many (100K+)Some (1000+)Few/None
User Group Size
Large (1M+)
* Color accounts for indirect users, to some extent
Agricu
lture
Loca
tion B
ased
Servic
es
Machin
e Con
trol
Tran
spor
tation
Trac
king
Surve
y
Comm &
Timing
Wea
pons
Orient
ation
Recre
ation
Scient
ific
Cell Phones & PCs
Autos
Aviation
PDAs
PGMs
PGMs RadiosHandhelds
Satellit
esBoats and Rail
***
ISR
Compasses
JBFSA
**
*
*
*
***
** *
*ISR
*
***
*
Wx Balloons
Satcom
Huge (10M+)
Scuba
** **
Position Navigation Orientation Time
Space
Air
Surface
Sub-surface
Version 9 Feb 2007
Underwater Vehicles
Torpedoes
18
Primary PNT Gaps
• Gaps primarily drawn from military’s PNT Joint Capabilities Document, with additions and modifications from parallel civil community documents and discussions– Physically Impeded Environments – Electromagnetically Impeded Environments – Higher accuracy with integrity– Hazardously Misleading Info (Integrity) – High Altitude/Space Position and Orientation– Geospatial information - access to improved GIS data
(regarding intended path of travel)– Insufficient modeling capability
19
Concept Development Overview
Futures
Technologies
Needs
EBL
Identify Shortfalls And Opportunities
Concepts
• Purpose– Explore various concepts – Identify PNT capabilities
• Concepts are first building blocks of the architecture– Includes Policies, Institutions, Processes, Material
DATA GATHERING
20
PNT Architecture Trade Space
• Source Location (of the service provider)– Terrestrial: concept provides service from,
near, or beneath the surface of the earth– Space: concept provides service from space
• Service Volume (of the service provided)– Local: concept provides a meaningful
service only at a fixed point– Interplanetary: concept provides a
meaningful service throughout the solar system
• Autonomy (of the user)– Dependent: concept requires frequent
refresh of information from external sources to provide a meaningful service
– Autonomous: concept, once initialized, is self-contained and requires no refresh of information from external sources to provide a meaningful service
LocalInterplanetary
Dependent
Autonomous
Terrestrial
Space
21
PNT Functional Reference Model
Disseminate PTO
(to User)
Disseminate Disseminate PTO PTO
(to User)(to User)
Receive PTO
Information
Receive Receive PTO PTO
InformationInformation
Generate PTO
Information
Generate Generate PTO PTO
InformationInformation
Determine PTO State
Determine Determine PTO PTO StateState
Receive PTO
Information
Receive Receive PTO PTO
InformationInformation
Disseminate PTO
Information
Disseminate Disseminate PTO PTO
InformationInformationDetermine
PTODetermine Determine
PTOPTO
AugmenterAugmenter
ProviderProvider
UserUserDisseminate PTO
Information
Disseminate Disseminate PTO PTO
InformationInformation
Receive PTO
Information
Receive Receive PTO PTO
InformationInformation
Determine PTO State
Determine Determine PTO PTO StateState
Generate PTO
Information
Generate Generate PTO PTO
InformationInformation
Reference Frames
Reference Reference FramesFrames
Geospatial InformationGeospatial Geospatial InformationInformation
ModelsModelsModelsStandardsStandardsStandardsCommand, Control &
Status
Command, Command, Control & Control &
StatusStatus
PTO: Position, Time, and/or OrientationPTO: Position, Time, and/or Orientation
22
Representative Architectures (RA)
RA0 = EBL (Point of Departure)RA0 = EBL (Point of Departure)
Service VolumeService Volume Source LocationSource LocationAutonomyAutonomy
0: Evolved Baseline1: Dependent Terrestrial2A: Combined GNSS
Constellations4: Network Aiding of GNSS5: Aided Autonomous
Sensors and Aiding Sources6: Highly Autonomous
14
65
2A
LocalInterplanetary
Dependent
Autonomous
Terrestrial
Space
RAs ARE NOT FINAL SOLUTIONS – THEY ARE USED TO GAIN INSIGHTS TOWARDS FINAL RECOMMENDATIONS
23
Example RA: Dependent Terrestrial
RTN
Backup NAVAID &
Surveillance
Backup Time Transfer
GBAS
EMI EMICell NetworkAiding
C2
Infrastructure & Enablers
Beacon
Beacon
High Altitude Platforms
Optical FiberOptical Fiber
Beacon
Low Freq RF
Beacon
Low Altitude Platforms
NOTE: DEPICTED ARCHITECTURE IS NOT A RECOMMENDATION
24
Preliminary Analysis
Risks• Performance• Programmatic• Acceptance
Needs• Accuracy• Availability• Coverage• Continuity• Integrity• Timeliness• Security
Gaps• Physically Impeded Environments• Electromagnetically Impeded Environments• Higher accuracy with integrity• Hazardously Misleading Info (Integrity) • High Altitude/Space Position/Orientation• Geospatial information
Evaluators• Adaptability • Interoperability• Robustness• Sustainability
RTN
Backup NAVAID & Surveillance
Backup Time Transfer
GBAS
EMI EMICell NetworkAiding
C2
Infrastructure & Enablers
Beacon
Beacon
Bathymetry
Pseudolites
Pseudolites
Optical FiberOptical FiberRTN
Backup NAVAID & Surveillance
Backup Time Transfer
GBAS
EMI EMICell NetworkAiding
C2
Infrastructure & Enablers
Beacon
Beacon
Bathymetry
Pseudolites
Pseudolites
Optical FiberOptical Fiber
Representative Architectures
Stakeholder Scores and Comments (6000+) Reviewed and Consolidated to identify Insights and Key Features
25
From Representative Architectures … to Recommendations
Representative Architectures
Hybrid Architectures
Should Be Architecture- Recommendations- Guidance- Decision Criteria
Preliminary Analysis(Feb - Mar 07)
Cost and Performance Analysis
(Apr - Jul 07)
26
Agenda
• Welcome and Introductions• Background of National PNT Architecture Effort• National PNT Architecture Development Process
– Data Gathering– Concept Development– Analysis and Assessment
• Overview of Current Status and Future Direction• Interactive Session
– Architecture-Level Questions– Identified PNT Gaps for 2025– Technologies and Concepts
27
Recap of Recent Activities
• Data Gathering (Aug – Nov 06)– Industry Days on east and west coasts– Review of civil needs (Volpe Center)– Presentation at Institute of Navigation Conference– Architecture Development Team (ADT) meetings in Aug and Nov– Products: As-Is and Evolved Baseline Architectures, PNT Gaps
• Concept Development (Nov 06 – Jan 07)– ADTs in Nov, Dec and Jan– Products: Concepts, Trade Space, Representative Architectures
• Analysis & Assessment (Feb – Mar 07)– ADTs in Feb and Mar– Products: Features, Insights, and Initial Findings
• Decision Coordination Group (Mar 07)– Approved way-ahead towards completion of effort
28
Preliminary Insights & Findings (1 of 3)
• US PNT Preeminence will face increased challenges at all levels
• Commercial PNT investments and services will increase significantly over the next 20 years
• PNT services will become more tightly integrated with other military missions as well as civil and commercial applications
• Demand for assured PNT in RF impeded environments (interference and obscuration) will increase
• Current GPS-centric architecture could be significantly altered by emergence of networked or autonomous PNT systems
29
Preliminary Insights & Findings (2 of 3)
• Signal diversity and use of multiple phenomenologies (autonomous, RF, networks, etc) are key to addressing identified gaps and providing robustness
• Higher power is one way to address impeded environment, but must consider implications of raising the noise floor
• Combined GNSS has the potential to provide improved accuracy and integrity; but the U.S. must maintain sufficient stand-alone global capability to support military operations
• Improvements to civil GPS performance and the advent of foreign PNT systems complicates Navigation Warfare, but can foster a cooperative international commercial environment
30
Preliminary Insights & Findings (3 of 3)
• Solution available for space/high altitude orientation gap—need improved star trackers and updated star catalogs
• Standards are an essential starting point for interoperability
• Low frequency RF-based systems are not sufficiently accurate to meet most-stressing positioning needs
• Political will may be needed if contemplating radical departures from the evolved baseline
31
Cycle 3 Products
• On track to deliver a Should Be Architecture for DCG approval in Jul 07– Recommended Capabilities– Supporting Findings
• Challenges – Sustain participation from stakeholder organizations– Using existing analysis tools to support long-term enterprise architecture
decisions– Development and coordination of Implementation Plan
• Targeted towards FY10 Budget Build Processes– Transition from “As Is” to “Should Be” Architecture
• Requires Structured Approach for Implementation• Identify Responsible Agency Participants• Tie Programs and Plans to Architecture Recommendations
– Sustaining the PNT Architecture as a configuration-managed baseline
Broad Scope Requires Innovative Approaches and Focused Analysis Efforts
32
Agenda
• Welcome and Introductions• Background of National PNT Architecture Effort• National PNT Architecture Development Process
– Data Gathering– Concept Development– Analysis and Assessment
• Overview of Current Status and Future Direction• Interactive Session
– Architecture-Level Questions– Identified PNT Gaps for 2025– Technologies and Concepts
33
Architecture-level Questions
• How do we determine the line between government and user (or commercial) provided capabilities?– Economic impact– Safety of life– Critical infrastructure
• What PNT capabilities should be permitted/regulated by USG?• What is the “right” mix of terrestrial, space-based, and autonomous
sources … as well as government-provided global vs. regional augmentation systems? Commercial systems?
• What role should autonomous PNT capabilities play (ex: INS, clocks)?• What is the future role of pseudolites and military augmentations?• What requirements should be apportioned to basic GPS, which to
augmentations, and which to user equipment?• How can terrestrial/augmentation systems best make up GNSS
shortfalls?
34
Architecture-level Questions
• How important is our leadership role in providing global PNT?• What PNT services are most appropriate to support critical
infrastructure? • Can existing infrastructure (commercial fiber, established stations, etc)
be reused or leveraged to support PNT?• Is DoD too dependent/reliant on GPS as a primary PNT source?• Should the US continue to pursue exclusive military services or instead
assume availability of PNT to all on the battlefield? • What role should foreign navigation services play in providing PNT
capabilities?– Does DoD continue to use only US PNT services?– Should WAAS and NDGPS monitor and broadcast Galileo corrections?
• What international principles, policies, agreements, and cooperation are most important in protecting US national security and the US economy?
35
Architecture-level Questions
• Funding priorities: Which PNT capabilities should we field next? Who pays: service provider vs. user?
• Where should we look first if we have to make cuts? • Within Federal Government, which agency funds a program with
overlapping requirements?• How can we meet long-term PNT and orientation needs for high altitude
and space users?– Can these PNT capabilities be leveraged to provide capability beyond
geosynchronous orbit?• How should we synchronize space, control, and user segments?• What capabilities and coordination should be planned in order to control
and operate the systems in the PNT Architecture?• What architectures or components help avoid or mitigate electromagnetic
interference?
36
Architecture-level Questions
• What PNT backup systems are required? (Especially for critical infrastructure)
• How can we better embrace commercial industry and academia, since they are often a driving force for innovation and change?
• How do we protect the spectrum, nationally and internationally?
• How will the FAA study on future of WAAS and GBAS impact the architecture?
• What are the implications of Net-Centric PNT?• How will software defined radios impact the future of PNT?
37
Strawman Analytical Framework
CostCost
Science & Science & TechnologyTechnology
Research & Research & DevelopmentDevelopment
Operations & Operations & MaintenanceMaintenance
PerformancePerformance
NeedsNeeds GapsGaps EvaluatorsEvaluators
National National StrategyStrategy
DiplomaticDiplomatic InformationInformation MilitaryMilitary EconomicEconomic
RiskRisk
CostCost PerformancePerformance AcceptanceAcceptance
INCLUDES QUALITATIVE AND QUANTITATIVE MEASURES
38
Overview of Civil PNT Challenges
• Diverse Set of Applications with Different Performance Requirements
• No Overarching Strategy Documents to Define Civil GPS/PNT Requirements – Identified in Civil PNT Analysis of Alternatives Study
• Promulgation of GPS Augmentation Systems• What is the “Right” Mix of Terrestrial, Space, Based of
Autonomous NavAids to Meet Performance Requirements?• What is the “Right” Mix of Government-Provided GPS
Augmentation Systems? Commercial Systems?• Within Federal Government, Which Agency Funds a
Program with Overlapping Requirements?
39
Primary PNT Gaps
• Gaps primarily drawn from military’s PNT Joint Capabilities Document, with additions and modifications from parallel civil community documents and discussions– Physically Impeded Environments – Electromagnetically Impeded Environments – Higher accuracy with integrity– Hazardously Misleading Info (Integrity) – High Altitude/Space Position and Orientation– Geospatial information - access to improved GIS data
(regarding intended path of travel)– Insufficient modeling capability
40
Who: Cell phones, radios, PDAs for LBS, and asset tracking, surface transport
Why: Growth of urban areas; growing indoor applications; current GPS radio frequency signals not always available
Gap: Physically Impeded Environments
What: Assured and real time PNT in physically impeded environments
Where: Areas including indoors, urban canyons, underground, underwater, and under dense foliage; users moving at surface speeds; communications available
Issues: Cost a key constraint; multipath; user equipment size/weight
Reference: PNT JCD
Surface transport
LBS; JBFSA; asset tracking
Cell phones; radios
41
Who: Future automobiles; railroads
Why: Growing population requires increased road and rail capacity; allows more cars/trains to safely fit on the same highways/tracks; increased efficiency/profits; improve safety
Gap: Higher Accuracy with Integrity
What: Advanced driver assistance (road departure and lane change collision avoidance) systems need 10cm accuracy; railroads need 1m accuracy for positive train control and 10cm accuracy for rail survey and test; advisory systems affecting safety of life drive integrity requirements
Where: On roads/rail at surface speeds; includes urban canyons, under canopy, in tunnels & valleys
Reference: 2006 FRP and PNT JCD
Road
Rail
42
Who: Air and surface transportation; weapons
Why: Many military users not provided with timely notification of degraded or misleading info; civil community seeks lower cost integrity for safety of life applications; PNT dependence makes spoofing more attractive
Gap: Notification of Degraded or Misleading Information (Integrity)
What: Timely notification (as short as 1 sec in some situations) when PNT information is degraded or misleading, especially for safety of life applications or to avoid collateral damage
Where: Transportation routes including roads, harbors, & airport approaches; military ops especially with high jamming/spoofing threat
Issues: Integrity requirements for JBFSA and intelligent highway use; sufficient availability of integrity
Reference: PNT JCD
Air/land/sea Transportation
Weapons
43
Who: Support to “space situational awareness, intelligence collection, and other missions”; NASA missions
Why: Current star catalog degrading; growing scientific uses—formation flying; navigation in environments with sparse radiometric signals
Gap: High Altitude/Space Position and Orientation
What: Real time high accuracy position and orientation (<10 milliarcseconds) information. Example: 3cm (relative) formation flying
Where: Space (Keplerian orbits) and at high altitude (medium dynamics)
Issues: No funding to update star catalog; GPS signal availability at GEO and beyond; need for additional radiometric sources beyond Earth orbit (cislunar space, and beyond)
Reference: PNT JCD; NASA Space Communication (and Navigation) Architecture
Space users
High Altitude users
Formation Flying
Precise Pointing
Degrading star catalog
44
Who: Air, surface and subsurface navigation users
Why: Robust geospatial information facilitates use of navigation information and provides the user with the knowledge of the environment along the intended path of travel.
Gap: Geospatial InformationWhat: Users require access to timely geospatial information for successful navigation
Where: On, near, or under the surface of the earth
Issues: What information is needed? How should it be produced? How should it be disseminated? How should it be processed, fused, and displayed?
Reference: PNT JCD
Aircraft
Cars, Ships, Handhelds Handhelds,
Subs
Which way?
Objective
45
Gap: Insufficient Modeling Capability
Need: Capability to model PNT capabilities in impeded conditions to determine impacts; need more timely capabilities; capability to predict impacts in urban environments
Characteristics: • Primarily a DoD need
Key Users: Joint mission planners
Now used: GIANT; SBMCS; Nav Tool Kit; reach back to GPS Ops Center, JSOC, JNWC
Growing jamming threat; interference more common
46
Points of Contact
• Karen Van Dyke– DOT/RITA/Volpe Center– [email protected]– 617-494-2432
• Major Shawn Brennan– NSSO– [email protected]– [email protected]– 571-432-1486
• http://www.acq.osd.mil/nsso/pnt/pnt.htm