CFMU Evolutions by A. FOURNIE

1
Network Operations Plan
Benoit FONCK Central Flow Management Unit
2
RATIONALE
DMEAN CONOPS calls for a consolidated network
flow and capacity overview enabling partners to
anticipate or react to any events and increasing
their mutual knowledge of the situation from the
Strategic phase to the real-time operations.
3
DEFINITION

• Consolidated set of airspace, flow and capacity
  plans, that includes the results of demand and
  capacity balancing in advance of the day of
  operations, and reflects the updated Pan European
  Network Situation from Strategic planning to
  tactical operations.

4
OBJECTIVES

• Reflect the ASM/ATFCM decision status at the time
  they have been taken
• Enable a common understanding of the Network
  situation
• Present potential disturbances that could impact
  the network and that could induce appropriate
  actions for risk mitigation
• Assist Airspace Users to take their operational
  decisions.

5
CURRENT SITUATION
6
CURRENT SHORTCOMINGS

• Most of the information required to be in the NOP
  already exist but are fragmented.
• This fragmentation leads to the following
  shortcomings
• Lack of clear and user-friendly presentation of
  the ATM situation as common reference for the CDM
  processes
• Lack of harmonisation in the information
  dissemination process (RCA, CIA, CHMI, Web-site)
• Lack of integrated view of the ATM decisions
  resulting in difficulty to identify their
  interactions
• Poor use of real-time (short term notice) updates
  leading to a lack of reactivity and flexibility.

7
CONCEPT

• The NOP is a consolidation of information
  provided by systems (e.g. ETFMS) and repositories
  (e.g. Airspace Data repository) and other sources
  (e.g. Network News).
• gt Not a repository
• The NOP is progressively refined from Strategic
  phase up to the real-time operations according to
  the iterative ASM/ATFCM processes (rolling
  NOP).
• Interested parties will have regulated access to
  the NOP based on privileges and will be able to
  create their own operations plan through data
  extraction.
• The NOP presentation will be tailored according
  to the users needs.

8
TYPE OF INFORMATION (1)

• ATM Decisions
• Airspace availability
• Route availability
• Acceptable/agreed scenarios
• Agreed ATFCM solutions
• Agreed sector configuration
• Agreed airport configuration
• Capacity values

9
TYPE OF INFORMATION (2)

• Situation Prognosis
• Information about events (e.g. Salon du Bourget,
  large scale military exercise, etc) that might
  create demand capacity imbalances
• Impact of Meteo forecasts on network operations
  (e.g. risk of fog )
• These information can be defined with a
  probability risk to happen.

10
TYPE OF INFORMATION (3)

• Network situation
• Integration of the ATM decisions and potential
  disturbances within the ATM infrastructure.
• Consideration of additional live data such as
  traffic data presentation (e.g. CPRs).
• Traffic Load information.
• Flight route profiles.
• Critical Areas description.

11
DISSEMINATION

• Broadcast Message delivery to anyone who might
  have an interest in the information (e.g. NOTAM).
• Portal integrated access including graphical
  representation
• Individual Service Delivery to a specific user
  with the up-to-date information at the correct
  time and in the adequate format according to his
  needs (e.g. PIB).

12
PLANNING (STRATEGIC) PHASE
13
ANTICIPATING (PRE-TACTICAL) PHASE
14
REACTING (TACTICAL) PHASE
15
CONCLUSIONS

• NOP is not one deliverable to be implemented in
  one shot in 5 years
• The Summer 2006 ATM Plan must be considered as a
  first step of NOP implementation.
• Further yearly steps in terms of technical
  development will be required.
• These building blocks will be identified in the
  DMEAN Phase 2 together with the associated time
  schedule.