230 likes | 536 Vues
Network Management functions Evolutions in SESAR WP7 and WP13. Moving Towards an Integrated ASM/ATFCM/ATS Approach Etienne de Muelenaere 20 September 2012. Evolutions of the Network Management functions (1) . The main objectives.
E N D
Network Management functionsEvolutions in SESAR WP7 and WP13 Moving Towards an Integrated ASM/ATFCM/ATS Approach Etienne de Muelenaere 20 September 2012
Evolutions of the Network Management functions (1) The main objectives • Performance driven – high Airspace Users’ involvement in decision making • From airspace-based to trajectory-based operations • Strong Network View on Capacity Management • Dynamic airspace management with enhanced civil/military cooperation • Network Management up to the execution phase • Collaborative process continuously reflected into the Network Operations Plan (NOP) Evolutions in SESAR WP7 and WP13
Towards Time-Based Operations • The objective: • Extending the Network Management to the Execution phase. • The milestones: • Research & Development (SESAR Step 1): 2010 – 2013+ • Deployment in operations: 2013 – 2017+ Towards Trajectory-Based Operations • The objective: • Using the accurate and shared view of the trajectory as common reference to perform Network Management. • The milestones: • Research & Development (SESAR Step 2): 2012 – 2017+ • Deployment in operations: 2018 – 2022+ Evolutions of the Network Management functions (2) Evolutions in SESAR WP7 and WP13
Evolutions of the Network Management functions (3) • Business and Mission Trajectory • User Preferred Routing • Advanced Flexible Use of Airspace • Dynamic Airspace Configuration • Enhanced ATFCM Processes (DCB) • Network Operations Plan Operational Focus Areas: Evolutions in SESAR WP7 and WP13
Military Mission Trajectory enables complex military operations • Military Mission Trajectory • enables complex military operations • includes ARES requests/allocations 4D Trajectories data linked and negotiated between aircraft-ATC 4D Business Trajectories Achieving Airspace Users’ business objectives Predicted Position, Altitude, time, speed Trajectory negotiation Trajectory negotiation 4DT 4DT 4DT 4DT 4DT 4DT 4DT 4DT 4DT 4DT 4DT 4DT TTA Business and Mission Trajectory (1) Improved sharing of the Demand Evolutions in SESAR WP7 and WP13
SESAR Step 1 Derived 4D Profiles Shared Profile ICAO FPL Shared view of Traffic Demand All Restrictions Network Mgnt Airspace Users 4D profiles + Additional Data Business and Mission Trajectory (2) Improved sharing of the Demand (pre-departure) • Current shortcomings: • Different views of profiles • Rejections of valid FPL • Demand impredictability • Additional workload • Reduced Network performance Evolutions in SESAR WP7 and WP13
TTO TTO Crew AOC TTO TTA RBT/MT TTOT TMA + y min NM Fn ATC Tolerances -x min Business and Mission Trajectory (3) Reference Trajectories (RBT/MT) => support the CDM processes in the planning and execution phases RBT/MT Revision Process The Reference Trajectory = 4D profile and tolerances agreed so far The Predicted Trajectory = 4D profile provided by aircraft systems When PT out of tolerances => CDM revision process is triggered Evolutions in SESAR WP7 and WP13
User Preferred Routing (1) • Routing based on users’ business needs – No fixed route network except for high complexity areas (flight efficiency/capacity trade off). • Dynamic transition from structured area (high complexity traffic) to user preferred routing area (low/medium complexity traffic). • Step 1: Free routing inside Functional Airspace Blocks (FABs) above Flight Level xxx. • Step 2: Pre-defined ATS Routes only when and where required (part of the Airspace Configuration Process) • From 2020: Free routing from TMA exit to TMA entry. Evolutions in SESAR WP7 and WP13
SESAR Step 1 Airspace Manager Improved ASM/ATFCM Integration Network Impact Network Mgnt Airspace Management up to real time Advanced Flexible Use of Airspace (1) • Shortcomings: • Lack of Airspace management flexibility • Missing capacity opportunities • Unnecessary protections • Demand impredictability • Reduced capacity Evolutions in SESAR WP7 and WP13
More an more Flexible Airspace Structures, in order to define the best location limiting constraints for other Airspace Users: Fixed areas (TSA – CBA – TRA ) Variable Profile Areas Dynamic Mobile Areas (DMA – 1) Dynamic Mobile Areas (DMA – 2) Advanced Flexible Use of Airspace (2) Evolutions in SESAR WP7 and WP13 Military airfield
SESAR Step 1 TSA X Fixed areas (TSA – CBA – TRA ) Advanced Flexible Use of Airspace (3) TSA Xi TSA Xi TSA Xi TSA Xi TSA Xi TSA Xi Variable Profile Area (VPA) Evolutions in SESAR WP7 and WP13
Dynamic Mobile Area (DMA 1) Needs are expressed in term of Airspace Design (Volume description) Area with defined lateral/vertical dimensions + time allocation Decided through CDM in order to implement the optimal DCB scenario Reference Mission Trajectory included the allocated areas Advanced Flexible Use of Airspace (4) TSA X Military airfield ~10 min transit time Evolutions in SESAR WP7 and WP13
Dynamic Mobile Area (DMA 2) Area with defined lateral/vertical dimensions + time allocation. At variable geographical location along the trajectory, activated & de-activated during specific timeframes to protect an activity Advanced Flexible Use of Airspace (5) Evolutions in SESAR WP7 and WP13
Airspace Manager Improved ASM/ATFCM/ATC Integration Network Impact ARES Request (SMT) Airspace User Network Mgnt Airspace Configuration up to real time AllocatedARES (RMT) Advanced Flexible Use of Airspace (4) • Flexible Airspace shapes • Dynamic Airspace Configuration • CDM approach Evolutions in SESAR WP7 and WP13
computed by probalistic analyses and AU intentions • ATC Workload • Assessment : • Occupancy • Complexity • Environment • Human Factors Lg/Med-Term computed from Trajectories (BT/MT) Short-Term or Exec Dynamic Airspace Configuration (1) • Hotspot detection: • modular based AS solutions • high granularity workload assessment • made visible to all via the NOP • Sector managment: • modular based sector configuration • re-configure sectors to meet User Prefered Routing • made visible to all via the NOP • DCB/dDCB: • optimum Airspace Configuration • Workload reduction measures (if needed) Evolutions in SESAR WP7 and WP13
Flow 1 (RBTs) Flow 1 (SBTs) DMA 1 DMA 1 Sector 2 DMA 2 Sector 1 Sector 2 DMA 2 Sector 3 Flow 2 (SBTs) Flow 2 (SBTs) Dynamic Airspace Configuration (2) Building Blocks (“PIXEL”) AUs NOTIFIED + NEGOTIATION WITH MIL HOT SPOT(workload/complexity) Higher granularity => finer solutions Evolutions in SESAR WP7 and WP13
Planning Phase Execution Phase All Phases Enhanced ATFCM Processes (1) Airspace Users All Service Providers Airspace Configuration Trajectory Edition SMT • Airspace Users: • more involved in DCB • access to Network View (Airspace Config, hotspot…) SBT • Airspace configurations: • primary solution • fully integrated in DCB (Demand Capacity Balancing) Hotspot detection 4D Targets • Hotspot detection: • modular based airspace solutions • high granularity workload assessment • Made visible to all Trajectory Management Trajectory Implementation RBT RMT • Network Manager: • provide the Network view • assess Network impact of local/FAB DCB • promote Network efficient solutions PT Evolutions in SESAR WP7 and WP13
SESAR Step 1 TTA CTOT Involve Flight crew and ATC Network Mgnt Target Time of Arrival Enhanced ATFCM Processes (2) Improved implementation of the plans DNM Profile Congested location ICAO FPL • Current shortcomings: • CTOT derived from NM Profile • No ATC/Pilotawareness of congested locations and regulation entry times • Changes in execution (weather, …) • Impredictability of entry times • Reduced Nw performance Evolutions in SESAR WP7 and WP13
SESAR Step 1 CDM Updates of the Plans (STAM) FMP • Occupancy counts • Hot Spot Detection • Network View • Support to CDM Network Mgnt Airspace Users Enhanced ATFCM Processes (3) Short-Term ATFCM Measures (STAM) Congestion ? (hourly counts) Let’s say Yes In fact no congestion Too Late ! STAM • Shortcomings: • Lack of flexibility in Flow Management • Lack of accuracy with Hourly counts • No measure at and after departure • Overprotections • Reduced Nw performance • Initial solution = local STAM, but: • No coordination with neighbours • No Network View Evolutions in SESAR WP7 and WP13
NOP: • Output of Network Management • All Nw Ops actions throuh CDM • Network Situation: • Data supporting NOP generation • Network Demand and Capacities • ATFCM scenarios • Airport data • Met data • NOP System: • Distributed open system architecture providing a set of functions/tools allowing access and modification of the NOP and the Network Situation Network Operations Plan Aeronautical Information Management Network Operations Aircraft ATMActors Air-Ground Datalink Management primary gateway for all users and providers to visualise and understand the ATM environment En-Route & approach ATC Airspace Design Evolutions in SESAR WP7 and WP13 AOC/WOC ATM Airport Airside Ops
Questions ? Evolutions in SESAR WP7 and WP13