presented to: aixm conference by: office of airspace and aim date: february 2007 federal aviation...
TRANSCRIPT
Presented to: AIXM Conference
By: Office of Airspace and AIM
Date: February 2007
Federal AviationAdministrationAeronautical
Information
Vision and Strategy Executive Briefing
2 2Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Topics
• Introduction concepts• Advances in aeronautical information• Status at FAA• What our customers want• Current activities• Summary
3 3Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Topics/1
• Introduction concepts• Advances in aeronautical information• Status at FAA• What our customers want• Current activities• Summary
4 4Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Introduction concepts
• Products are presentations (Views) of data– Effective at date of publication
• The primary user of [paper] products is humans– Machines have to interpret products to extract underlying data
• The real value is in the data – The product is just the presentation
Publications HypertextWebDisplay
5 5Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Introduction concepts/2
• ICAO Annex 15 describes the product requirements for the Aeronautical Information Service (AIS) (2 Products)
Baseline(Static Situation)
Aeronautical Information Publication
Delta(Dynamic Changes)
RESTRICTEDAIRSPACE ACTIVE
RUNWAY CLOSED
NOTAMS
Notice to Airman
6 6Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Introduction concept/3
• Historically we set up stovepipes to create products– Customers are responsible for integrating products
into view of the airspace system– We cannot ensure the products are consistent
AeronauticalProducts
Customers
NASRNOTAMs
ACESETMSDAFIF
DOFSUA
ALTRVTPPNFD
…
7 7Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Topics/2
• Introduction concepts• Advances in aeronautical information• Status at FAA• What our customers want• Current activities• Summary
8 8Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Advances in Aeronautical Information
1. Maturity in understanding FAA products
2. What is a NOTAM?
3. Move from Messages to Transactions
4. Putting it together
5. What’s changed?
6. Global change: AIS to AIM
9 9Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Maturity in understanding products
• We don’t have to live in the “product-centric” past– We create many systems to do the same thing to the same basic data
elements
– Example of 2 Aeronautical Notices• Notice to Airman (NOTAM)• Special Use Airspace (SUA) status
• Aeronautical information data products have common themes– Identification and Operation [ What ]
• Description (KIAD), Status (Open/Closed)
– Period of Validity [ When ]
– Geometry [ Where ]• Point, Line, Polygon
– Latitude, Longitude, Altitude
1.
10 10Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
What is a NOTAM?
• Notice that the published information has changed
• NOTAM – Notice to Airmen– A0794/06 (09/027) - RUNWAY CLOSED 10/28 12 SEP 04:00 UNTIL UFN
Aeronautical Information Identification & Operation
+
Period of Validity
12 Sep 0400 GMTUntil Further Notice
Geometry
+
Message
2.
11 11Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Another notice Military Airspace Status
• SUA Status – Special Use Airspace status– Buckeye Military Operation Area (MOA)
• Activated 0900 to 1300 on Sep 9 2006
Aeronautical Information Identification & Operation
+
Period of Validity
BuckeyeMOA
Activated
9 Sep 20060900 to 1300 GMT
Geometry
+MOA boundary
Message
2.
12 12Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
What about other FAA products?
• Products (Historically Text based)– NOTAM: Runway is Closed for a certain time – SUA: Buckeye MOA is Active for a certain time– CARF: Temporary Restricted Airspace – GPS/WAAS: GPS Unreliable in Coverage area until further notice
• Common Themes– Identification and Operation [ What ]– Period of Validity [ When ]– Geometry [ Where ]
• The examples above all describe something that is happening to a piece of airspace, but it could be an airport, navaid or any other component of the National Airspace System (NAS)
2.
13 13Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
A Credit Card Transaction A familiar example
Credit Information Identification & Balance
Credit CardTransactionCharge Number
Timestamp
OperationList of changed properties
…
Debit $200
+ =
Credit Information Identification & Balance
(Updated State)
• Credit card [Existing] balance - Charge= [New] balance [Existing] Value + transaction = [New] Value
• Address update…..
Message
3.
14 14Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
A Transaction Aeronautical data works the same way
• Start with published information about an aeronautical feature (runway, airport, airway, fix, airspace…) Add a request to change a property of a feature (owner, status,
availability…) Result is the updated feature
Aeronautical Information Identification & Operation
(Published)
Aeronautical InformationTransaction (AI-T)
Aeronautical Feature
Period of Validity:
Start of ChangeEnd of Change
OperationList of changed properties
Geometry
+ =
Aeronautical Information Identification & Operation
(Updated State)Message
(What, When, Where)
3.
15 15Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Putting it together
• Start flight planning with a snapshot of the current airspace– Request updates to the dataset since the snapshot was taken– Result is a common [near-time] view of the NAS
• Airports• Aircraft FMS• ATC Automation• Traffic Flow Management• Partners – International, Military, …
• User systems would use or show that data in the form that supports their requirements– Query, Filter, Alert, Transform (text or graphic representation)
3.
16 16Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
What’s changed?
• International Recognition that we need to move from text-based products
• There is a global exchange model available – Aeronautical Information Exchange Model (AIXM)
• Describes aeronautical information and relationships– Designed for system to system exchange of data
• We now understand that existing legacy products can be created from base NAS data– Publications– NOTAMs– Charts (after adaptation for best presentation)
• Data Quality starts at the beginning of the process (survey) and must be maintained– Trace-ability of data source and modification– Chain-of-Custody
5.
17 17Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Global change: AIS to AIM
AIP
Classical AIS- publish documents
Document content and format is described by:
- ICAO Annex 15, Appendix 1 – AIP Content
- ICAO Annex 15, Appendix 6 – NOTAM format
- …
SUP, NOTAM,
AIC
AIM System- manage data
Data managed in the system is described by models:
- Aeronautical Information Exchange Model (AIXM)
- AIXM Conceptual Model (AICM)
- Electronic AIP (eAIP) – on-line presentation format
Timesheet<<complexProperty >>
Timetable<<complexProperty >>
0..*
1
0..*
1
ObstacleLightElement<<complexProperty >>
ObstacleLightingTimetable<<complexProperty >>
HorizontalGeometry
+ accuracy+ conf idence lev el+ resolution
<<group>>
VerticalDimensions
+ maximumElev ation+ elev ationDatum+ height+ geoidUndulation+ accuracy+ conf idence lev el+ resolution
<<group>>
ObstacleLighting
+ remarks
<<Feature>>
1
0..*
1
0..*
1
0..1
1
0..1
obstacle lighting availabi...
ObstacleTimetable<<complexProperty >>
Obstacle
+ identif ier+ name+ ty pe+ marking+ f irstColour+ secondColour+ status+ remarks
<<Feature>>
1
1
1
11
1
1
1
1 0..11 0..10..1 10..1 1
obstacle effectivity
Specifications• Content
• Quality
• Metadata
EuroControl Slide
Man
agin
g
Pro
du
ct
Man
agin
g
Dat
a
6.
18 18Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Topics/3
• Introduction concepts• Advances in aeronautical information• Status at FAA• What our customers want• Current activities• Summary
19 19Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Historically at FAA
Separate data sets for each activity
Examples7930.2 NOTAM Manual –
Specifies “human-readable” grammar
8260.19 TERPS – “Mail Sectional Charts” “Rules for interpreting terrain contours”
7400.X Airspace – Manual coordination and publication
of airspace
Criteria is manual and form-based
ExamplesDOF – Obstacle data set for
public
AirNAV – Obstacle data set for procedure development
NASR – NAS data set for public
NACO – NAS data set for charting
Paper-based processing and tracking
Non-integrated Products
ExamplesLetters of Agreement
SUA development and validation
NOTAMs
ExamplesCharts
Letters of Agreement
Publications
Procedure Charts
Airport Layouts
20 20Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Trends in the FAA• Criteria – separating policy, procedures and data
– 8260.19D (TERPS automation)– Proposed NOTAM manual modernization
• Data sets – improved data integrity and information management– Surveys and Airport GIS
• Processing – automation and workflow– iOE/AAA– MIA and MVA evaluations– Milops, Airport GIS, etc.
• Products – automation from a common data set– eNASR
21 21Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Topics/4
• Introduction concepts• Advances in aeronautical information• Status at FAA• What our customers want• Current activities• Summary
22 22Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
What our Customers want
1. 2006 Global AIS Congress
2. Highlights from NOTAM Survey
3. Digital data not text
4. Multiple Views
5. Direct to the cockpit
23 23Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
2006 Global AIS CongressAIS – The key to Interoperability
Capt Ed LyonsCapt Ed LyonsV.P. V.P. Safety & AirworthinessSafety & AirworthinessAir OperationsAir Operations
Quality Aeronautical Information Quality Aeronautical Information The key to InteroperabilityThe key to Interoperability
Pilots (User) Perspective on Pilots (User) Perspective on Aeronautical Information (AI) Aeronautical Information (AI) Presentation given to AIS Congress
By Capt. Ed Lyons
VP Safety & Airworthiness Air Operations for Federal Express
Madrid Attendance
• Over 500 attendees
• Over 80 Countries
High Level Representation
• FAA ATO VP of System Operations
• EUROCONTROL Director General
• ICAO Director of Air Navigation
Message: “US NOTAM system is broken”
Request: NOTAM (AI) data directly to the cockpit
1.
24 24Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Quotes from NOTAM survey• FAA should plan to improve the processing and delivery of the aeronautical
information because:– “The key issue is safety not savings. Savings are nice but safety is paramount. The
current, fragmented system is potentially unsafe and is definitely inefficient.– Contradictory NOTAM – potentially unsafe– Local NOTAM not disseminated – potentially unsafe – Procedures changed by NOTAM – potentially unsafe (when good internal data checks
would have uncovered the bad data in the fist place)– Untimely data – potentially unsafe – No advance warning e.g. long-haul flights inbound the USA – potentially unsafe (D-
NOTAM)– Lack of current surface conditions – potentially unsafe”
• Major Deficiencies to focus on– “Put someone in charge and give them the authority to change how business is done!– The NOTAM Office or some central facility must own, be aware of and have the authority
to deal with all U.S. AIS/AIM data. It should also be able to follow up worldwide issues in coordination with EAD”
• “A SINGLE SOURCE is a MUST”
2.
25 25Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Digital data not text
• Sample NOTAM text– A0794/06 (09/027) - RUNWAY CLOSED 10/28 12 SEP 04:00 UNTIL UFN
• Data– Fully Described (What and When)– Fully geo-referenced (Where)– Timely!!!!!!!!!
• Functionality– Query– Filter– Transform– Alert
3.
26 26Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Multiple views of data
!MCN CCO 14/32 CLSD/PARL TWY 3000X75 AVBL DAY VMC/NO TSNT/NO PLA/NO STUDENT
Traditional US NOTAM format: Plan Language NOTAM format:
NOTAM Number: 5/3232Issue Date: Nov 10, 2005Location: Newnan Coweta County Airport
(CCO)Beginning: Effective immediatelyEnding: Until further notice
Affected Area(s):Runway: 14-32Status: Closed
Taxiway: 14-32 ParallelStatus: OpenLength: 3000 ftWidth: 75 ftOperating Hours: Sunrise to Sunset
Usage Restrictions: 14-32 ParallelFlight Rules: VisualPilots: Certified Only (No Students)Restriction: No practice low approaches
Geo-referenced Display:
5/3232
5/3232
Query Filter Transform Alert
Plain Language NOTAM FormatView A View B
View C
Data enables Functions
4.
27 27Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Direct to the cockpit
x x x x x x x x x x
From Ed Lyons (FedEx) Presentation at 2006 AIS Congress
5.
28 28Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Topics/5
• Introduction concepts• Advances in aeronautical information• Status at FAA• What our customers want• Current activities• Summary
29 29Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Current activities
1. Aeronautical Information Exchange Model
2. Digital NOTAM Prototype• Airport Surface NOTAM Viewer
3. Next-generation Flight Management System (FMS)
4. 2007 NOTAM Improvements
5. Aeronautical Information Management
30 30Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Introduction to AIXM
• Standards-based approach for modeling aeronautical data– ICAO* Standards and Recommended Practices (SARPS)– Industry standards– Data concepts from aeronautical information products
• Originally developed by EUROCONTROL in 1990’s• AIXM 5 Developed by collaboration of EUROCONTROL, FAA,
NGA and others.• Organized into major
conceptual areas– Aerodromes – Airspace– Fixes– Procedures– Routes– Services– Obstacles
*ICAO: International Civil Aviation Organization
31 31Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
AIXM Foundation
Others… ISO 19107Geometry
ISO 19108Temporality
ISO 19115Metadata Schema
Feature Identification
Messages and AI-X
• AIXM 5 Design Document – Model for Aeronautical Information Exchange (AI-X)– www.aixm.aero
AI-X
xNOTAM
SUA Status
Airspace Status
32 32Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Digital-NOTAM prototype
• Partnership with Air Mobility Command (AMC) and National Geo-spatial Intelligence Agency (NGA)
• Proof of concept– Fully digital NOTAM data (what, when, and where)
US NOTAMSystem
NOTAM Data Model(Geo-referenced)NOTAM Data Model(Geo-referenced)
Static and DynamicAeronautical Data
Convert
Distribute
NOTAM Creation
Traditional formats and distribution channels still exist.
33 33Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Airport Surface NOTAM ViewerProof of Concept
Machine readable NOTAM can be accurately filtered
and converted to any format on the fly.
Geo-referenced NOTAMs can be plotted on maps
and associated with Airport surface features.
NOTAM data can be accurately filtered by time.
Visual indicator that there is a NOTAM
Digital NOTAM ExplorerDigital NOTAM Explorer
Filter
Apply
ABQAirport:Plain Language ViewMilitary operations
Civilian, Commercial
Civilian, GA
Select User Type
Operation TypeVFR (Visual)
IFR
Time Range
8/1/200600:00
8/2/200600:00
8/3/200600:00
8/4/200600:00
8/1/200616:00
8/2/200608:00
NOTAM: 5/5454Beginning: 8/1/2006 00:00Ending: 8/3/2006 12:30
Taxiway: A-8Status: Closed
34 34Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Next Generation Flight ManagementARINC Navigation Data Base eXchange (NDBX)
• FMS uses proprietary data formats
– Limiting options and competition
• Equipment Limitations– Equipment and
standard capacity limited
• < 10 year life
• Opportunity to resolve past compromises
An Airlines View on the current constrains and needed changes to pave the way for seamless operation in an increasingly changing ATM environment
The FMC evolution needs a new momentum
http://www.arinc.com/aeec/projects/ndbx/index.html
December 2006
35 35Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
2007 NOTAM Improvements
• FAA needs to address the issue of Local NOTAMS– One central place to pull ALL US NOTAMs
• NOTAM numbering system– Avoid re-using expired NOTAM numbers– Numbers rolled 3 times in 2006
Goal: Maximize short-term benefits
36 36Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Aeronautical Information Management• Operational
– Address AI data quality and tracking directly from the point of origination
• Should airports enter status changes directly into system?
– Single portal for AIS, NOTAM, and all other AI (surveys, obstacles, …)– Integrate Special Use Airspace (SUA) status into the NOTAM system– Digital Delivery along side of legacy NOTAM delivery
• Streamline AIM policy, processes and delivery– Implement workflow management throughout AI processes
• Data Traceability and Metadata (source/author, date info, )• Tracking work throughout the data chain (survey…AIS…aircraft)
• Involve more of the community– Planning a mid-April Community NOTAM briefing
1.
37 37Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Topics/6
• Introduction concepts• Advances in aeronautical information• Status at FAA• What our customers want• Current activities• Summary
38 38Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Summary
1. Paradigm Shift– Move from legacy AIS thinking to Aeronautical Information
Management (legacy product to data)– Actions Planned
2. International Adoption– Global data exchange format
• Aeronautical Information Exchange Format (AIXM)
– Partnership
3. A couple of things to remember….
39 39Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Paradigm Shift Data is the key
• Products are specifications on how data should be presented– Charts (products) have two parts
• The aeronautical data• How the data (label) should be presented (anchored to
graphic) on the document
– Products can be out-of-date the day of publication
• Quality begins at the beginning of the data chain
• Single Entry – Multiple Views
1.
40 40Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Data-driven ChartsComputer-assisted cartography is available now
Location Candidate #1
Candidate #4
Candidate #2
Candidate #5
Candidate #3
XYZ
XYZ
XYZ
XYZ
XYZ
XYZ
XYZ
XYZ
2. Candidate Placements
1. Offset from Attribute General Rules
Label requirements based on rules by scale
Offset based on rules
Label Location based on rules
Overlapping based on rules
1.
41 41Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Single Data EntryComputer automated products are possible now
FDC 0/0000 ZAB NEWMEXICO.. FLIGHT RESTRICTION ROSWELL, NEWMEXICO. PURSUANT TO 14 CFR SECTION 91.137(A)(2) TEMPORARY FLIGHT RESTRICTIONS ARE IN EFFECT DUE TO A HIGH SPEED ...State New Mexico
Affected Location: Roswell, New Mexico near VORTAC (CME)
Beginning Date: 3/2/2004 at 4:46 PM UTCEnding Date: Until further noticeTFR Hours: 24 hours, dailyAffected Operations:AllReason for NOTAM:Temporary flight restrictions
for high speed chaseType: Hazards...
<NotUid><txtNameAcctFac>FDC</txtNameAcctFac><dateIndexYear /><noSeqNo /> <dateIssued>1/1/0001</dateIssued><txtLocalName>BRETT TEST</txtLocalName>…</NotUid><codeTimeZone>UTC</codeTimeZone><txtDescrPurpose>
HIGH SPEED CHASE</txtDescrPurpose>...
Traditional Text
Web Text
xNOTAM (AIXM) XML
TFR Graphics
AIXM
AIXM
Different Transforms
Multiple Products/Views
1.
42 42Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
AIXM DeploymentGlobal Adoption and Implementation
AIXM
EuroControl Slide
2.
2006 2007 2008 2009
Sep 05AIXM 4.5
Release Candidate 2
End 2007 - AIXM 5.0Final Release
Release Candidate 1
43 43Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
International Adoption
1 –AIM iscore ATM enabler
2 – Enlarged scope
4–Ensure quality for all phases
of flight
5 – RegionalExcellence
8 – BusinessFocus
7 - HumanCapital
3 – Move from product to data
approach
9 - Civil/Militarypartnerships
6 - GlobalAIM
Partnerships
From 2006 Global AIS Congress
• Australia
• Canada
• China
• EuroControl
• Japan
• South Africa
• United States
2.
44 44Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
A couple things to remember…
• Quality from the very beginning– Quality check as data enters the system
• Authorization and accuracy
– Focus on end-to-end quality – Complete Chain-of-Custody
• Move to digital delivery of Aeronautical data– Build products from base AI data– Merge like data types (NOTAMs and SUAs)– Single entry – Multiple Views– We will still have to maintain many of our legacy formats
• Aeronautical data is not just traditional AIS and NOTAMs• Its Global…
3.
45 45Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Thank You !
46 46Federal AviationAdministration
Aeronautical Information ManagementJanuary 2007
Definitions
• AEEC Airlines Electronic Engineering Committee (ARINC)• AI Aeronautical Information (also means Artificial Intelligence)• AI-T AI Transaction• AIM Aeronautical Information Management• AIS Aeronautical Information Service• AICM Aeronautical Information Conceptual Model• AIXM Aeronautical Information Exchange Model based on XML• Annex 15 ICAO annex addressing AI Services• CARF• COI Community of Interest• FMC Flight Management Computer• FMS Flight Management System• IV&V Independent Verification &Verification• MOA Military Operating Area• NDBX Navigation Database Exchange• NOTAM Notice to Airman• SUA Special Use Airspace• UML Unified Modeling Language• WG Work Group• XML eXtendable Markup Language