Integrated Tools

1
Integrated Tools System Architecture
Supporting the DMEAN Concept of Operations
Andrew Hill DMEAN
2
Supporting the DMEAN CONOPS
Strategic Capacity Planning
Demand Data Collection
Airspace Design
Pre-Tactical Tactical Demand-Capacity Balancing
DMEAN Integrated Architecture of Systems Tools
Performance Monitoring
CDM and Civil-Military Coordination
Flight Planning
3
Approach for Specifying the DMEAN Tools

• Approach for Tools in DMEAN Phase 2
• Requirements were defined in Phase 1
• Make Survey of Current Tool Set.
• Identify weaknesses of current Tool Set vis-à-vis
  the requirements.
• Identify Interoperability needed between Tools.
• Specify Tool upgrades or New Developments that
  are needed.

4
Airspace Design Tools

• Main Tools in use today
• EUROCONTROL SAAM, CFMU ENV
• Non-EUROCONTROL TAAM, etc.
• Upgrades or New Developments needed to
• support
• validation of the static and dynamic data in the
  ADR (including data in remote parts of the ADR).
• development and validation of the pre-defined
  scenarios.
• Interoperability.

5
Demand Data Collection Tools

• Main Tools in use today
• EUROCONTROL STATFOR
• Non-EUROCONTROL OAG
• Upgrades or New Developments needed to
• support
• Collection of Aircraft Operator demand at
  city-pair level.
• Collection of Military demand for airspace.
• Controlled Access required for all stakeholders.

6
Strategic Pre-Tactical Capacity Planning Tools

• Main Tools in use today
• EUROCONTROL SAAM, RAMS, FAP
• Non-EUROCONTROL PACT, etc.
• Upgrades or New Developments needed to
• support
• Simulations of network capacity at the strategic
  and pre-tactical levels, taking account of
  airport, TMA and en-route declared capacities.
• Dynamic aspects such as sector re-configurations
  and activation/de-activation of TSAs and TRAs.
• Proposal of Scenarios.

7
Pre-Tactical and Tactical Demand-Capacity
Balancing

• Main Tools in use today
• EUROCONTROL SAAM, COSAAC/PREDICT
• Upgrades or New Developments needed to
• support
• simulate network capacity at the tactical level,
  taking account of airport, TMA and en-route
  dynamic capacities.
• identify imbalances between capacity and demand,
  and suitable solution scenarios.
• access for AMCs to be able to run the same or
  similar tools to check selected solutions.

8
CDM and Civil-Military Coordination Tools

• Main Tools in use today
• EUROCONTROL/ANSP CIMACT (for military)
• Non-EUROCONTROL STANLY, etc.
• Upgrades or New Developments needed to
• support
• Greater flexibility in specifying TSA
  requirements dynamically.
• Assessment of alternative scenarios.
• Common Situation Awareness.

9
Flight Planning Tools

• Main Tools in use today
• EUROCONTROL IFPUV, Route Catalogues
• Non-EUROCONTROL Lido, Skytrak, Jeppesen, etc.
• Upgrades or New Developments needed to
• support
• Identification of routing options between
  aerodromes (or points), taking account of dynamic
  airspace changes.
• Identification of flight plans affected by
  airspace changes and proposing changes to
  advantage of improved routings which are
  available.

10
Performance Monitoring Tools

• Main Tools in use today
• EUROCONTROL FIND, PRISME, EFICAT, etc.
• Non-EUROCONTROL STANLY, etc.
• Upgrades or New Developments needed to
• support
• Generation of KPIs.
• Measurement of actual demand, capacity,
  civil-military coordination and flight planning
  issues, including use of CDRs for Flight Planning
  and/or Tactical re-routings.
• Assessment of Flight Efficiency.

11
DMEAN Integrated System Architecture

• A Major deliverable of DMEAN Phase 2 will be a
  proposal for an Integrated System Architecture,
  covering
• Tools.
• Repositories.
• Upgrades to existing CFMU systems,
• Interfaces.
• CBA and Validation.
• Plan for Next Phases.

12
Logical View of DMEAN Integrated System
Architecture
CFMU
ATC Airports Aircraft Operators Military
Pre-Tactical Tactical Tools (PREDICT, IFPUV,
etc.)
Operational Systems (ETFMS, IFPS, etc.)
Operational Systems
Tools
Repositories
NOP
Demand Data Repository
Airspace Data Repository
FPL Repository

• Other Tools
• Airspace Design
• Demand
• Capacity
• Perf. Monitoring
• Civil-Military
• etc.

Archive
Internal i/f
EUROCONTROLNon-CFMU
13
Airspace Data Repository

• An example of a system/tool
• which may have a distributed
• Architecture, including
• European Aeronautical Database (EAD)
• CFMU Central Airspace Capacity Database
  (enhanced Environment Database)
• National/Local systems (Local Aeronautical
  Databases, National AIS, Mil AIS, etc).

14
Conclusion

• By early 2006, requirements and solutions need to
  be presented for agreement.
• This is a unique chance to integrate the ASM,
  ATFCM, Flight Planning and CDM Systems and Tools
  into a common System Architecture.
• ? Commitment of all partners is crucial for
  improvements to materialise