Embed Size (px)
Citation preview
1
Evaluation of Requirements for the Interference
Detection & Mitigation (IDM) of Positioning
Navigation & Timing (PNT) Interference Reports
& Central Data Repository
The Institute of Navigation
International Technical Meeting 2009
John MerrillDHS/MGMT/CIO/OAT
Geospatial Management Office
2
Presentation Overview
• IDM Plan Development & Overview
• DHS IDM Responsibilities
• IDM Plan Implementation
• Central Data Repository Requirements
• Baseline & Go-To Architectures
• Systems under review
– FAA Spectrum Engineering Tracking System (SETS)
– Integrated Common Analytical Viewer (iCAV)
3
DHS IDM Plan Development
• December 2004 - DHS assigned responsibility for domestic
Space-based PNT IDM planning and coordination
• June 2005 – DHS began Space-Based PNT IDM Plan
development starting with existing processes in place for GPS
outage reporting, tracking and resolution
• June 2006 – Space-Based PNT IDM Plan coordinated with the U.
S. PNT Executive Committee
• August 2007 – Space-Based PNT IDM Plan approved/signed by
the U. S. President
4
DHS IDM Responsibilities
• Coordinate domestic capabilities to identify, analyze, locate,
attribute, and mitigate sources of interference to the GPS and its
augmentations
• Develop and maintain capabilities, procedures and techniques, and
routinely exercise civil contingency responses to ensure continuity
of operations in the event that access to GPS signal is disrupted or
denied.
• Collect, analyze, store, and disseminate interference reports from
all sources to enable appropriate investigation, notification and
enforcement action
5
DHS IDM Plan Outline
• Key Policies, Departments and Agencies
– Departments and Agencies that were assigned
responsibilities that impact PNT services
• GPS Interference
– GPS and the Critical Infrastructure
– GPS Vulnerabilities and Analysis Studies
– Categories of Jamming
• Current GPS Interference Reporting Procedures
• Space-Based PNT Interference Detection & Mitigation Plan
6
DHS IDM Plan Implementation
• DHS Geospatial PNT Executive Committee
– PNT Work Group
– Geospatial Work Group
– DHS Departments and U.S. Agencies with Geospatial and
PNT responsibilities are represented
• DHS IDM Implementation Plan
– Development and maintenance is responsibility of DHS
PNT Work Group
– Standardized reporting format of interference reports
– Continuous evaluation of operational procedures
– Development of central data repository requirements
7
Central Data Repository Requirements Elicitation
• Mission Needs Statement
• Concept of Operations
– USCG NAVCEN: All civil non-aviation users of GPS
– FAA NOCC: All aviation users of GPS in the National Airspace
– GPSOC: Status of GPS Service, including accuracy & availability;
predictive coverage/accuracy information… etc…
• Collective Effort of Departments of Transportation, Defense,
and Homeland Security
8
Central Data Repository Requirements
• Central Interference Report (IR) database focal point of all PNT
interference
• Encompass process and functions for detection validation,
investigation, assessment, corroboration of IR
• Automated dissemination of data and reduce IR information
distribution delays for decision support
• Mechanisms for cataloging PNT applications and associated
vulnerabilities to interference
• Employ information assurance components and processes to
protect database
• Assure the integrity of IR and sensors
9
Central Data Repository Requirements
• User Access Threshold – 70 concurrent user access
• User Access Sign-on – 475 read access
• Submission of 150 PNT incident reports (IR) per month (1800
annually)
• Database support 500,000 unique IR entries
• Responses to system queries less than 8 seconds
• New & updated IRs posted immediately visible, available and
accessible
• System availability of 99.9%
• RSS for automatic update to subscribers – Initially:
– Navigation Center, FAA Operations Center, GPS Operations
Center.
10
Central Data Repository• Baseline Requirements - Cost control, use existing
architecture
– FAA Spectrum Engineering Tracking System (SETS)
– Integrated Common Analytical Viewer (iCAV)
• Geospatial enabling/visualization tool
• Standard thin-client Geographic Information System interface
that integrates multiple geospatial data sources from a
centralized geospatial data warehouse
• Based on the Environmental Systems Research Institute’s suite
of products; ability to map, analyze, and view information from a
mission specific application which assembles and compares
data from various sources.
11
Current Architecture
Navigation Center, FAA Operations Center, & GPS
Operations Center only
12
Go-To Architecture Navigation Center, FAA
Operations Center, & GPS Operations Center only
13
Central Data Repository• Federal Aviation Administration’s SETS core 10 data
fields (mandatory entries):
1. SETS ID # {Record URL}
2. DATE START - DD/MM/YYYY
3. DATE STOP - DD/MM/YYYY
4. EVENT TIME START - #### UTC
5. EVENT TIME STOP - #### UTC
6. LATITUDE - +##.####### Degrees
7. LONGITUDE - +###.####### Degrees
8. USER EQUIPMENT TYPE
9. FREQUENCY (L1, L2, L5) - ####.####
10. REMARKS & OTHER RELEVENT INFORMATION
14
Central Data Repository• Federal Aviation Administration’s SETS four
additional data fields (optional entries):11. Event Status
12. Source
13. Joint Spectrum Interference Report (JSIR) DTG
14. Altitude
• Possible future data fields for consideration• US National Grid
• The following slides show the existing FAA’s SETS
web pages which will be changed to a DHS PNTIP
“look and feel”
15
This is the Intranet web form available to authenticated users with access to the http://sets.faa.gov URL.
Address will change to: http://pnt.dhs.gov/login/EVENT_entryPNTIP.asp
16
The PNTIP community can search for an event based on any one or combination of the searchable fields in the form (14 fields).
17
Once a field or set of fields is selected the user can then choose from one of four search criteria – All, Active, Open or Closed Tickets.
18
Name – This is the name of the POC most familiar with the issue. It is determined by the SETS authenticated user creating the ticket who is the best fit for a POC as it relates to the problem.
19
Event Start/End – This is the date and time the actual incident started. May be prior to when the TIX Opened date and time show.
20
Ident – This is a three or four letter identification that is unique to each facility.
21
Equip –FAA Equipment types which may be experiencing the interference. Eventually populate with PNT equipment
22
Event Type – This is the major category of events in SETS. In the GPS SETS module they are TESTING, ANOMALY, RFI, MILITARY and OTHER
23
Code – This is the FAA Maintenance Management System Mainframe event code category. In the GPS SETS module is replaced by JSIR.
24
Freq – This is the frequency of the affected NAS Radio Frequency service. For GPS events there are only three frequencies (L1, L2, L5)
25
Source – This is one of 14 major industry categories where the interference source will fit under. It includes Unknown and Other.
26
iCAV Classic and iCAV NextGen
iCAV “Classic”• First generation DHS Enterprise
Geospatial tool with light analytical capability
• Built on National Geospatial-Intelligence Agency’s (NGA) Palenterra tool
• Provides access to HSIP and Web-mapping services for dynamic, real-time data feeds
iCAV Next Gen• Builds on the success of iCAV Classic
by:– Improving user interface– Making data easier to find and use– Enhancing analytical capabilities
based on needs expressed by users• Scheduled for deployment in early 2009
27
28
29
30
31
32
33
34
Summary• Identification of central data repository requirements complete
• The FAA SETS GUI will reflect PNT preferences
• DHS will continue to evaluate iCAV as the lead geospatial
analysis tool
• Continue prototype evaluation & transition to operational test
early 2009
• Establish central repository 2009 with TRIAD and slowly
migrate other federal agencies for use
• Eventually include international incident reports
35
Points of Contact
DHS Geospatial Management OfficeMr. John [email protected]
FAA Spectrum EngineeringMr. James [email protected]
