System Wide Information Management (SWIM) PENS Symposium Brussels, 17 October 2012

Transcription

1

2 System Wide Information Management (SWIM) PENS Symposium Brussels, 17 October 2012

3 THIS PRESENTATION IS ABOUT Introduction Principles & Definition Governance Logical models Technical infrastructure Open issues

4 INTRODUCTION

5 The need for sharing ATM information ATM Planning Phases 6 MONTHS YEARS DAYS MINUTES HOURS Business Development Forecasts Airline Plans Schedule Dev Military Exercises Major Events Business Development Trajectory Lifecycle of Business Trajectory Planning Sharing Information Negotiation on: Plan refinement: Schedules Arrival capacity Airspace Departure Routes planning Resources Weather a Key enabler for BDT Airspace Design SBT SBT SBT SBT SBT RBT Shared Business Trajectory Execution Local capacity mgt. Traffic balancing Real time synchronisation Tactical De-Confliction planning executing - analysis Reference Business Trajectory Tactical Actions Flight Object

6 Systems implementation The way to share ATM information Systems interoperability Common data definition common interfaces Integrating aircraft, regional systems, local systems, military systems Data Exchanged Air/Ground Datalink Surveillance data Flight data Airport Airside Operations SWIM Systems AOC ATM A/G Datalink Ground Management Aerodrome ATC En-route // Approach ATC Aeronautical data Meteo data ATFCM scenario data Demand & Capacity data Ground/Ground SWIM Military Meteo Advanced Airspace Management Aeronautical Information Management Network Information Management

7 PRINCIPLES & DEFINITION

8 Principles Information sharing Multiple stakeholders Service orientation separate concerns, flexibility Federation Ownership of information Open standards Semantic & Technical interoperability Information and service life cycle governance Controlled evolution, trust System Wide Information Management (SWIM) Page 8

9 SWIM Concept SWIM consists of standards, infrastructure and governance enabling the management of ATM information and its exchange between qualified parties via interoperable services. SWIM Governance Qualified parties Qualified parties ATM information Service consumer(s) Qualified party ATM information Service(s) Standards Standards Standards SWIM Infrastructure Standards Network infrastructure AIM/SWIM team #3 SESAR SWIM presentation Page 9

10 SWIM Concept SWIM consists of standards, infrastructure and governance enabling the management of ATM information and its exchange between qualified parties via interoperable services.

11 GOVERNANCE

12 Governance - overview Trust Controlled Evolution Information Framework regulatory functions Service Framework design-time runtime general oversight I M Compliance Framework Institutional Arrangements registration operational functions certification security supervision oversight F U N C T I O N S System Wide Information Management (SWIM) Page 12

13 Governance Information Management functions are being identified from the SWIM Concept of Operations that was produced end of Proposals are being formulated for how governance may be organised in real life in the future. Note: Implementing governance is part of the deployment activities and hence outside the scope of the current work. Governance aspects are set-up and evaluated inside the programme. CCBs for AIRM and ISRM. Preparation of a registry capability to support design time governance. SWIM compliance framework being defined and foreseen to be applied as well.

14 Qualified parties Need to identify what it takes to become a qualified party in SWIM. Link to SWIM governance and compliance framework Infrastructure Services Information lifecycle... AIM/SWIM team #3 SESAR SWIM presentation Page 14

15 LOGICAL MODELS AIRM & ISRM Reference models

16 ATM Information Reference Model (AIRM) Semantic interoperability within ATM The same name means the same thing in all parts of the system. Seamlessly combine and process information from more than one provider. Consistent information and data modeling Minimize redundancies by spotting overlaps within data models Reuse existing model constructs Reduces effort to creating and maintaining information and data models ATM information standards on European and global level System Wide Information Management (SWIM) Page 16

17 ATM Information Reference Model (AIRM) Logical model (consolidated) Semantic interoperability System Wide Information Management (SWIM) Page 17

18 ATM Information Reference Model (AIRM) Logical model (consolidated) Semantic interoperability Physical models (domain specific) Technical interoperability AIXM - Aeronautical Information Exchange Model WXXM Weather Information Exchange Model FIXM - Flight Information Exchange Model System Wide Information Management (SWIM) Page 18

19 Information Service Reference Model (ISRM) Operational context Processes, Scenario s, Actors, Information Flows Information Exchange Requirements Issuer, Addressee, Information Element, QoS Service allocation and development Allocation to SWIM infrastructure Allocation to legacy system Page 19

20 Working Method on Services Page 20

21 Interoperable services Information Service Reference Model (ISRM) is under development Logical service definitions Physical service implementation possible on SWIM infrastructure that supports the service s functional and nonfunctional requirements. Iteration/evolution in 6 month intervals. Iteration 0.5 planned for end of September From 6 services in iteration 0.4 to ~12 in iteration 0.5 Actual (model compliant) prototype implementation is (to be) done by SESAR technical projects. AIM/SWIM team #3 SESAR SWIM presentation Page 21

22 TECHNICAL INFRASTRUCTURE

23 A net centric approach

24 Connecting multiple stakeholders FO (ATC) FO (ATC) FO (ATC) SWIM Step1 infrastructure Airport NOP (CFMU) Web Service client (Airlines/GA) EAD SWIM as a means to share information between multiple stakeholders

25 Interoperability between legacy systems SWIM as a means to create interoperability between legacy systems (APP) (enabling the gradual transition towards services)

26 Different needs require different solutions Security A E I RR PS B All Grouping of needs leads to SWIM profiles ROFILE ROFILE DEFINITION DEFINITION UNDER UNDER CONSTRUCTION CONSTRUCTION Exch Pattern Performance High Availabilit BE Middleware FN LR DC DV Not Profile 3 Profile 1 Profile 2

27 Service 1 Service 2 Service 3 SWIM Profiles Service 4 Service 5 Characteristics Technology Standards Service 6 ROFILE ROFILE DEFINITION DEFINITION UNDER UNDER CONSTRUCTION CONSTRUCTION Offered Infrastructure Required Infrastructure

28 Capability ATC to ATC B2B CFMU NOP B2B EAD CONSTRUCTION Messaging X X X Security X X X Logging & Tracing Supervision X X X Recording X X X Validation activities on PENS SESAR VPN High Availability X X Interface Management X Data Validation X X X Shared Object Message Exchange Pattern Request/Reply Publish/Subscribe Technology Standards X Request/Reply ROFILE ROFILE DEFINITION DEFINITION UNDER UNDER CONSTRUCTION X Request/Reply Publish/Subscribe Network WS, DDS WS WS, WS-N PENS & National Internet Internet

29 Ongoing PENS SJU coordination Led by Bolek Gasztych (ECTL) since 24 May 2012 Objective I: Short term validation requirements Objective II: Align SWIM design and network requirements Identify network configuration options (e.g. multicast) Identify applicable SWIM profile requirements Define the optimal network configuration in support of SESAR requirements for future deployment of SWIM. Note Deployment of solutions is out of the SJU scope. Decisions on a deployment management body are pending.

30 Air/Ground SWIM

31 OPEN ISSUES

32 Still cracking the tough nuts Supervision Charging Security Liability Common language Registration Discovery Roles Responsabilities Copy rights Interoperable, Affordable,.

33 Summary We agree on the basic SWIM concept Step 1 infrastructure profiles evolving to Step2 profiles We have some initial infrastructure prototypes Evolution required. Baseline AIRM available Evolution required. Need to assure full use. Services being defined, subject to operational requirements. Governance aspects need elaboration. Registry service being set-up for the programme. Air ground SWIM in early development AIM/SWIM team #3 SESAR SWIM presentation Page 33

34