1. Flight and Flow Information for a Collaborative Environment (FF-ICE)
ATMRPP-WG/WHL/13
July 20-24, 2009
A presentation of the DRAFT FF-ICE Concept for ICAO panel secretaries
11/19/2018
ATMRPP-WG/WHL/13

2. Overview Motivation ICE Major Changes Information elements
Document Organization
Need for ICAO panel feedback
11/19/2018
ATMRPP-WG/WHL/13

3. Motivation Global ATM Operational Concept led to:
Requirements in ICAO Doc 9882
Performance-based approach in ICAO Doc 9883
Envision a future with:
More collaborative decision making
Increased management by trajectory
Improved performance management
ICAO flight planning provisions are inadequate
‘Patch’ through PANS-ATM (2012) changes
FF-ICE concept describes the dynamic information-enhanced environment in support of the Concept
Requirement flows from Global Air Traffic Management Operational Concept (ICAO Doc 9854)
Requirements outlined in Manual on Air Traffic Management System Requirements (ICAO Doc 9882).
Focuses on benefits of increased use of trajectory management and CDM, enabled in a SWIM environment.
Current ICAO flight planning system inadequate for the future target environments
‘Patch’ created through changes to PANS-ATM (2012)
FF-ICE Concept describes developments necessary to replace current flight plan processes
Needs
FF-ICE Concept
11/19/2018
ATMRPP-WG/WHL/13

4. Document Organization
Drivers for change
The FF-ICE Concept
Overall collaborative environment
FF-ICE delivers concept components
Flight operation example (more in Appendix C)
Technical Environment
Information elements & hierarchy (more in Appendices)
Information management (SWIM) & formats
Transition
Heterogeneous transition assumed
Long transition with support through versioning
Considerations provided, example transition steps in Appendix B
Appendices provide detailed examples
Focus on Operations
Engineering Focus
Introduction
Drivers of Change
The FF-ICE Concept
Technical Environment
Transition
11/19/2018
ATMRPP-WG/WHL/13

5. Information for a Collaborative Environment (ICE)
AOP
ASP AU AP
ESP
Dynamic Information-rich environment
Interacting information domains require standardization and compatibility on:
Information
Communication mechanisms
Participants
Wider information access
Access controlled
PBA requires flexibility
FF-ICE Concept focuses on:
Flight and Flow Data
Aeronautical Information
Flight & Flow Information
Infrastructure Status
Surveillance Information
Meteorological Information
When we speak of this information for a collaborative environment, we envisage an information-rich environment beginning long before a flight operates
This information-rich environment will require information across multiple domains, and these must interact. This requires compatibility at various levels: from information standards at the syntactic and semantic levels, to compatible communication mechanisms
Yet, the PBA requires flexibility to implement changes in a timely manner to achieve performance targets – some balance has to be reached between the drive to standardization and the flexibility to improve the system.
11/19/2018
ATMRPP-WG/WHL/13

6. Example Flight >3 months pre-departure: Before day of operation
1 year
>3 months pre-departure:
Schedule provided
Obtains permissions
Before day of operation
Obtains shared constraints
Provides initial trajectory for CM, DCB
Pre-departure
Obtains weather, winds, constraints
Provides desired 4DT & SAR info
Provides preferences, performance
Agreed 4DT reached meeting DCB / TS objectives
Incorporate taxi path
In flight
Updates 4DT, information supporting separation
Arrival aerodrome taxi-in 4DT update
Post-flight
Archiving for performance
Depart
Arrive
11/19/2018
ATMRPP-WG/WHL/13

7. Major Changes
11/19/2018
ATMRPP-WG/WHL/13

8. Advanced Notification
<72 hours
FPL
Flight information provided earlier
Up to one year pre-departure
Information supplied progressively
Updated as certainty improves
Continues into flight
QoS on information
Shared among multiple participants
Information flows both directions
More information than today
Supports Capacity Management
Supports Demand / Capacity Balancing
Earlier/more collaboration
CHG
Flight Planning
transforms
Flight Information Sharing
ASP
1 year
AOP
The process of filing a flight plan transforms to one of more continuously sharing of flight information
Information is provided much earlier, the provision of information is updated as the quality of information improves, and continues into the flight.
The idea of “sharing” also indicates a two-way communication of flight-related information – facilitates collaboration
This supports a collaborative approach to capacity management and DCB as information can be known earlier, and with greater certainty on operations - this includes potentially information on performance levels AU
FF-ICE
Depart
ASP
ESP
Arrive
11/19/2018
ATMRPP-WG/WHL/13

9. Single Global Reference
Globally Unique Flight Identifier (GUFI)
Upon first notice of intent, a unique flight identifier is created
Single global reference key for flight information
Enables consistent reference to flight information across ANSP
Supports global interoperability
FF-ICE :
Single , global flight ID
11/19/2018
ATMRPP-WG/WHL/13

10. Data Format XML - balances standardization & flexibility
Global standards
Information items & format defined in XSD published & maintained by ICAO
PBA determines items in use locally & regionally
Regional Extensions
Performance needs may require extensions
New items published in regional XSD
Unambiguous information items
Supports automation
Automated format validation
Flexible - accommodates extensions
Version control w/ backward compatibility
Standard
Flexible
11/19/2018
ATMRPP-WG/WHL/13

11. Data Distribution
Anticipate shift from point-to-point to system-wide information distribution
Caveat: Interoperable but heterogeneous environment
Not all regions implement SWIM
Technical implementations may vary
Facilitates collaboration
Improves information consistency
Supports system evolution
Accommodates multiple points of entry
Information must be shared on a system-wide basis
Pertinent information will be available when and where it is required
11/19/2018
ATMRPP-WG/WHL/13

12. Security Mechanisms provided for information security
Aviation security
Commercial sensitivities
Support for application-to- application information security
 Enables information exchange for increased collaboration
Identification
Authentication
Authorization
Integrity
Confidentiality
Availability
Accountability
11/19/2018
ATMRPP-WG/WHL/13

13. Flight Deck Interaction
Envisage exchange of flight information with flight deck
Examples:
In-flight trajectory negotiation
Additional information for improved separation provision
Flight deck information exchange must remain limited and controlled
11/19/2018
ATMRPP-WG/WHL/13

14. Information Elements
11/19/2018
ATMRPP-WG/WHL/13

15. Information Elements Every FPL item is accounted for
FF-ICE
Every FPL item is accounted for
Additional information elements support:
Collaborative Decision Making
Performance-based operations
Management by trajectory
Information presented hierarchically
FPL
11/19/2018
ATMRPP-WG/WHL/13

16. Trajectory 4D-Trajectory gate-to-gate Multiple trajectory types:
Consists of: departure, airborne and arrival segments
Trajectory-based items:
Agreed
Ranked
Negotiating
Desired
Executed
Performance
Alternates
Constraints
Flight rules
Aircraft intent
Tolerances
11/19/2018
ATMRPP-WG/WHL/13

17. Agreed 4D Trajectory
Information exchange between participants to reach agreed trajectory
Tolerances bound agreement
Agreement may be re-negotiated
Information supports improved separation management
Executed trajectory
For performance reporting
11/19/2018
ATMRPP-WG/WHL/13

18. Expressing Preferences
Desired trajectory
User may request a specific trajectory
Dynamic – can update as situation warrants
ICE provides constraint information to users
Ranked trajectories
Some ANSP may implement
Allows selection from ranked alternatives
Conditions on switching (e.g. up to a 10 minute delay for 1st choice)
Additional preferences:
Flight priority – Between flights
Operating practices – What practices are acceptable to the flight?
Movement preferences - What are user-preferred controls for traffic management? (e.g. up to 4000’ vertical, 20 NMI lateral to the South)
 System delivers trajectory best meeting user intentions
What does airspace user wish to do?
11/19/2018
ATMRPP-WG/WHL/13

19. Performance Items Broader set: Trajectory-based
Operations affect:
Broader set:
Trajectory-based
Performance varies along trajectory
Infrastructure dependence
Service delivery depends on actual performance, not average for class
Communications
Safety-net
Navigation
Noise
Surveillance
Emissions
Wake-turbulence
Runway Requirement
Wake Vortex
Service delivery can include access limitations based on performance
Low noise/emissions
11/19/2018
ATMRPP-WG/WHL/13

20. Formation Flights More flexible description of formation flights:
Formation bounds
Join / split points
Leadership change
4D trajectory information
More flexible formation flights supported
11/19/2018
ATMRPP-WG/WHL/13

21. ? Feedback Request Are panels aware of current work:
Affected by the FF-ICE concept?
Relevant to the concept, but not mentioned?
Is the FF-ICE concept consistent with the work?
Can it be made consistent?
Comments on clarity or consistency of FF-ICE concept document
Concepts or capabilities supported?
Can transition occur?
Flight-deck interaction
Trajectory-based performance
Exchange mechanisms consistent with ground-ground communication evolution?
11/19/2018
ATMRPP-WG/WHL/13

22. Backup
11/19/2018
ATMRPP-WG/WHL/13

23. Support for PBA Long-term performance mgmt
Data
Long-term performance mgmt
Historical data
Flexibility
Pre-tactical performance mgmt
Extended flight information timeline
Support for collaborative activities
Tactical performance optimization
Constraints, preferences, trajectories support
Performance monitoring
Supports end-to-end performance monitoring
Real-time to post-event performance evaluation
Longer timeline
Flexibility
Historical data is provided for target setting, validation, model improvement trend analysis
Flexibility is offered through information constructs that allow new operational improvements driven by performance needs
Pre-tactical performance management is supported through the provision of information with a longer timeline (allows capacity
management to occur with best available information such as planned operations, capabilities and levels of performance) Includes feedback and collaboration on demand/capacity
Information provided to support individual stakeholder performance optimization at a tactical level. Through the sharing of constraints, preferences and trajectories, operators can collaboratively influence outcomes and have the information to optimize their own operations
Performance monitoring is more easily accomplished end-to-end as information is harmonized
The expanded timeline of information provision allows performance monitoring to occur real-time, through post –event. With the provision of preferences, performance can be measured against delivering preferences.
11/19/2018
ATMRPP-WG/WHL/13