Information Management Task Force

1
Information Management Task Force

• Sarah Amundsen
• DMEAN Framework Programme

2
Objectives for Information Management Task Force

• Identification of information which could be
  shared/used in order to improve planning and
  operations in a more effective manner in 2006/7
• Establishing practical benefits justifying
  specific actions to collect/share/use this data
• Identification of issues which need to be
  considered
• Definition of action timescales,
  responsibilities complementary with information
  management enhancements foreseen through the work
  packages of the Framework Programme Master Plan
  by end 2009

3
Data Groupings

• Airport data
• GAT Demand data
• Military Demand data
• Capacity data
• Airspace Management-related data
• Summer 06 ATM Ops Plan

4
Airport dataStart of Summer/Winter season for
selected airports

• Data
• Slot co-ordination results
• Airport plans effecting network eg.
  runway/taxiway closures
• Special events
• Fix / stack to landing - a more realistic average
  value per airport
• Taxi times per runway/variable taxi times
• Benefits
• Incorporate reliable airport capacity and day of
  operations changes to runway throughput into
  overall network assessment
• Include significant airport capacity
  events/changes in ATM Ops Plan Summer 06
• Provide information on GAT demand
• Provide input to simulations and capacity
  planning activities
• Aid efficient airport operations

5
Airport dataTactical and post-operational phases

• Tactical Data
• Expected runway throughput capacity changes
  from Met forecasts
• Reduced capacity due to environment
  impact/critical events
• Post Operation Data
• Rationalising categories of airport delay -
  airside, groundside, ATC
• Benefits
• Reliable data for tactical flow management
• Aid efficient airport operations and ground
  handling
• Maximise slot utilisation
• Enables effective performance monitoring and
  capacity planning

6
Airport data Issues and Outcomes

• Issues
• Mechanism to exchange data
• Identification of airports from which different
  data sets are significant
• Use made of tactical data by CFMU and ANSPs
• Data storage
• Outcome from IMTF
• Structured exercise involving airports to
  determine airport-related data
• Usage
• Transformations/aggregations
• Value for users at different stages
• Finalise priorities for next IMTF meeting in
  January

7
GAT Demand Data Start of Summer/Winter season

• Data
• OAG Data - origin/destination, a/c type,
  departure time
• Scheduled
• Chartered
• Special events generating abnormal demand
• European slot coordination data
• AOs preferred flight plan 4D profiles
  (routings, levels)
• Changes e.g. due fuel costs
• Significant planned military movements on ATS
  route network
• Benefits
• More accurate demand/capacity balancing
• Longer planning horizons
• Mapping demand picture onto ACCs and eventually
  sector groups
• Better ANSP planning staffing
• Development of targeted flow and capacity
  management scenarios

8
GAT Demand DataD-7 to AOBT

• Data
• D-7 Significant ATS routes crossing by military
  requiring corridors/FL blocks
• D-2 NAT Tracks
• Confirmed Demand - Day of Operations
• Business and GA flight plans
• AOBT
• Flight plan update / missing flight plans
• Benefits
• More accurate demand/capacity balancing
• Mapping demand picture onto ACCs and eventually
  sector groups
• Better ANSP planning staffing, sector
  configuration
• Better modeling of the effects of North Atlantic
  Tracks on ATFCM pre-tactical planning at D-3 to
  D-1

9
GAT Demand DataIssues and Outcomes

• Issues
• Getting pre-season data
• OAG type data
• Commercial and IPR sensitivities
• Low-cost carriers
• Code sharing/double counting
• Preferred routes
• No existing forum
• Whether known restrictions taken into account
• Integrating with RPLs
• Rolling updates for all phases
• System capabilities
• Complexity/workload monitoring
• Expected outcomes
• Examine the accuracy of AO intention data
  (OAG-type data) and the feasibility of
  acquiring the information integrating it with RPL
  info
• Examine sharing of NAT data D-3 to D-1 with
  NATS/EC

10
Military Demand Requirements and Benefits

• Data required
• Initial Plans (strategic/6 months ahead) covering
• Major exercises, including state-specific
  exercises
• Changes to training areas
• Known planned use of airspace which affects
  network capacity
• Unconfirmed planned use, with indication of when
  confirmed
• New requirements
• Weekly update of confirmed demand for areas
  affecting network
• Benefits
• Flexibility at Level 1
• Include in network capacity assessment
• Update Summer 06 ATM Ops Plan
• Develop and validate pre-determined scenarios

11
Military DemandIssues and Outcomes

• Issues
• Getting data
• Strategic from States
• Pre-tactical from AMCs
• Confidentiality and security
• Expected outcomes
• Obtaining data on State-specific military
  activities affecting Network
• Obtaining data on known military demand before
  D-1
• Military demand data recorded along with special
  events
• Examine use of tools measuring sector complexity
  on changes of airspace status

12
DMEAN Information Flow
Q
DMEAN Information Flow
AOs ATC
ATC
AOs
AO
DMEAN Information Management System
DMEAN Information Management System
Nicholas Ashley Version 1.0 6th July 2005
13
Q
DMEAN Information Flow
AOs ATC
ATC
AOs
AO
DMEAN Information Management System
DMEAN Information Management System
Nicholas Ashley Version 1.0 6th July 2005
14
Capacity DataElements and Benefits

• Capacity planning inputs for capacity values
• Airspace configuration (with/without CDR
  activation)
• Sector configuration, seasonal (for simulations)
• Demand/historical data
• Existing pre-defined scenarios
• On-the-day capacities of all ANSPs are dependent
  on
• Sector configuration scheme
• Airspace allocation
• More accurate data enables
• More accurate determination of capacity/demand
  imbalances
• Capacity shortfalls can be acted upon earlier
• Pre-determined scenario options validated and
  evaluated

15
Q
DMEAN Information Flow
AOs ATC
ATC
AOs
AO
DMEAN Information Management System
DMEAN Information Management System
Nicholas Ashley Version 1.0 6th July 2005
16
Capacity DataIssues and Outcomes

• Issues
• Format of data to interface with current tools
• Use of consolidated capacity (and demand) data by
  ANSPs early in planning cycle
• Discrepancy between short and medium term traffic
  forecasts
• Expected outcomes
• Single interface for users to obtain capacity
  information
• Providing traffic forecasts by sector and thereby
  capturing more accurate information on sector
  capacity values
• Merge short and medium term traffic forecasts
  into a single forecast to improve accuracy -
  improved accuracy enables more granularity of
  capacity values down to sector level

17
ASMRequirements and Issues

• Required
• More benefit from availability of airspace
  resulting from day of operations AMC decisions
• Higher utilisation of CDRs exploit for flight
  efficiency and/or capacity benefits
• Issues
• How/whether to use UUP to share information of
  airspace status handled on day of operations
• How/whether to have more frequent updates to ENV
• Ensuring no reduction in safety due to any
  changes in notification process
• Tracking effects benefits

18
ASMOutcomes

• Expected outcomes
• Trial in 2006 to support airspace changes decided
  closer to operations than D-1 for specific CDRs
  selected for dedicated action
• Encouraging liaison with AOs regards benefit of
  using under-utilised CDRs
• Specific AMC, FMP CFMU agreement on
• Notification process
• Procedures
• Timings
• Monitoring and assessment
• Work in conjunction with CFMU/AMC/FMP trial in
  2006 and incorporate feedback

19
Q
DMEAN Information Flow
AOs ATC
ATC
AOs
AO
DMEAN Information Management System
DMEAN Information Management System
Nicholas Ashley Version 1.0 6th July 2005
20
Summer 06 ATM Operation Plan Requirements and
Benefits

• Regular Updates to Summer 06 ATM Ops Plan,
  including
• Demand data
• Capacity plans
• Scenarios usage / development
• Special events associated regulations
• Expected Network performance
• ATFCM measures in operation
• Airspace design sector configurations updates
• Specific CDR utilisation changes/procedures
  trialed for 06

21
Summer 06 ATM Operation PlanBenefits, Issues and
Outcomes

• Benefits
• Sharing of information and transparency of
  activities which will impact network performance
  for summer 06
• Actions planned
• Expected performance
• Special events
• Issues
• Collection of all pertinent data
• Format and scope of updates
• Resources
• Expected outcomes
• Regular updates of ATM Ops Plan from April 2006
• Feasibility of web output of ATM Ops Plan
• Can be considered as first phase of the NOP

22
Conclusion

• Next steps
• Determine applicable data, usage and benefits
• Clarify responsibilities of users/providers
• Plan actions and timescales
• Seek agreement at DMEAN Steering Committee
  meeting Feb 8th 2006