8 th June 2009EA TRS Study Consortium1 Enterprise Architecture TRS Dissemination Workshop Overview of Study, Background & Deliverables presented by Dr

8th June 2009 EA TRS Study Consortium 1

Enterprise Architecture TRSDissemination Workshop

Overview of Study, Background & Deliverables

presented by

Dr John R F GuyNATS – Chief Architect European ATM

on behalf of EA TRS Study Consortium



• Some Background from SESAR Project Definition (PD) Phase

• Summary of Output from Service-Oriented Architecture Task Force (SOA-TF)

• Summary of Scope of TRS• Structure of Consortium• Overview of Deliverables D1 to D8• Outline of Approach Taken• Summary of Deliverable D9 - Evaluation Report• Taking Study’s Output into Work of SESAR

Development Programme


SESAR (Single European Sky ATM Research)

– European air traffic control infrastructure modernisation programme

– Aim is to develop new generation ATM System for 2020 and beyond

– Give Europe a high-performance ATM infrastructure to enable :

• Safe, and

• Environmentally sustainable development of air transport

A System that, compared with today (2005), will :

– Enable 3-fold increase in Capacity

– Improve safety performance by factor of 10

– Enable reduction in effects of flights on the environment by 10%

– Provide ATM services to airspace users 50% cheaper

SESAR is taking a Performance-driven Approach

Background from SESAR Project Definition (PD) Phase (1/4)


• System architecture work performed recommended that Enterprise Architecture (EA) & SOA techniques be used to develop, define, design & manage future European Air Traffic Management System (EATMS)

• Proposal based upon following principal shortcomings of current situation :

– Current EATMS has fragmented design which is difficult & expensive to change

– Large diversity of technologies in use throughout Systems in operational service today

– Taking a “bottom-up” approach to making changes to individual systems to create “Single EATMS” for the future will never work

– Need different approach to meet today’s expectations of the stakeholders for taking performance-driven approach in future



• Proposal based upon following principal shortcomings of the current situation (continued) :

– “Piecemeal” approach which has been taken up to now to maintaining legacy systems and/or replacing them “one-by-one”

– Been done in context of a System-design philosophy which is based upon the “point-to-point” exchange of information

– Is fundamentally mismatched with the way in which modern information technology (IT) systems are :

• designed,• how they function• way in which they need to be procured & maintained

– Approach to definition, design & evolution of an EATMS has, to date, neither led to an effective harmonisation of air navigation service providers’ (ANSP) systems, applications, or interfaces, nor to the creation of a true EATMS



• None of above will be capable of enabling the proposals being developed as Future ATM Target Concept to be implemented

• Future relies on – being able to share information between all stakeholders (i.e.,

through the use of System-wide Information Management (SWIM) techniques)

– Provide a high degree of connectivity to maximise the benefits of using Collaborative Decision Making (CDM) techniques



SESAR Concept of Operations• Based on trajectory management – NOT airspace

• Seven major features, the first two :

– System Wide Information Management (SWIM)

– Collaborative Decision Making (CDM)

provide foundation for :

– Trajectory managed environment

– Human-centric decision-making with automation support to reduce work load

– Use of new separation modes to take advantage of :

• advanced aircraft navigation capabilities, to allow (ultimately)

• tasks to be delegated to pilots

– Performance of Aircraft & ATM systems to be matched to achieve “ATM Capability

Levels”

– Airports to be fully integrated into the ATM network


Summary of Output from Service-Oriented Architecture Task Force (SOA-TF) (1/3)

• SOA-TF tasked to investigate EA & SOA to strengthen proposals made during PD phase & provide “bridge” to work of Development Phase

• Fundamentally different approach needs to be taken to the design & development of future EATMS

• To derive benefits of using modern IT solutions (not necessarily bespoke to ATM industry) to implement the Future ATM Target Concept (but starting from today’s diverse legacy systems baseline), making changes to the design of, and/or replacing, systems must be done in a harmonised way and at a common level throughout the EATMS’s architecture.

• Taking a service-oriented approach and using an Enterprise Architecture framework will enable this harmonisation to be achieved

• European ATM has to be seen as a “single enterprise”, manifest in the notion of a European ATM Enterprise Architecture (EAEA)


• The EAEA provides a business-driven framework that allows a meaningful way to partition and manage ATM complexity, reconciling different partners’ business visions for ATM and creating a bridge between their business needs and their requirements for IT solutions

• Using a combination of EAEA and SOA will enable improvements in business agility and efficiency to be realised through a streamlining and alignment of the supporting IT infrastructure to the business

• Adopting EAEA and SOA approach is not a silver bullet that will immediately solve all the issues surrounding the evolution of ATM systems

• Moving to using an EAEA and SOA techniques implies a paradigm shift in the way the business is viewed and managed and in the way the supporting IT infrastructure is specified and developed. This will require a big cultural change, especially to management and system engineering processes



• In an EAEA/SOA and SWIM-based environment, partners give access to their systems and information to other partners within the enterprise.

– Note : This means that security issues, such as authentication & access control, have to be managed at the enterprise level

• Concluded that adoption of an EAEA & taking a service-based approach represents a long-term strategy for change

– Will challenge partners to re-engineer their organisation, processes & IT to optimise their ATM related activities as federations of relatively independent services

• European ATM is not the first to attempt making such a transition– Experience of other industries must be embraced to identify best practice &

learn lessons

• Key recommendation to take an incremental approach, starting with a tightly scoped initial project, to test task force findings


This laid the basis of this Study


Summary of Scope of TRS

• Based upon proposal made by SOA-TF• Scope limited to ATM activities on & around an Airport• Study taking “Demonstration” approach to achieve “proof

of concept/approach” to ATM– interpreted as producing “80/20” completeness of study’s outputs

• “Top-down” approach seen as ideal, but parallel working needed to fit scope & timescale – this was acknowledged as introducing degree of risk

• TRS required formation of Consortium – minimum of :– 1 Airspace User,– 1 Airport Operator,– 1 Air Navigation Service Provider,– 1 Systems Supply Industry


Structure of Consortium• Contributions provided by Consortium Partners were drawn from the

following companies & organisations :– Airline Group (bmi, British Airways, easyJet, Monarch,

Thomsonfly, Thomas Cook, Virgin Atlantic)– BAA– DFS– ENAV– Indra– LFV (supported by Saab / Combitech)– NATS– SICTA

plus contributions from• Eurocontrol• SESAR Joint Undertaking’s (SJU) Industrial Support Function

(EADS)


Airspace Users

AirportOperator

ANSP

ATM Performance Partnership

Business relationships

Process & service

relationships

Operational Processes

[D2]

[D3]

[D6]Systems &

service relationships

Organisational (Unit)

Structure

ApplicationServices

Systems

[D4]

[D7]

ConceptualInformation

Model

Operational (Business) Services

Operational (Business)

Goals

Information Services

Information Model

[D1]

[D5]

[D8]

PRINCIPAL RELATIONSHIPS BETWEEN DELIVERABLES D1 TO D8


Outline of Approach Taken• Training Workshop held immediately before “kick-off” of the Study

• Eurocontrol presented some initial results of their work done prior to the Study on :

– Strategic,– Operations– Systems aspects

• Material presented suggested work was most mature on Operations aspects

• Due to breadth of scope & time limitations, decided to build upon this aspect of their work

• Approach taken was to develop the Operational Processes first & subsequently, draw out the Operational & Information Services

In effect, starting “middle out”


Summary of Deliverable D9 – Evaluation Report

• Introduction• Background from SESAR PD Phase & SOA-TF• Development Approach & Overview of EAEA

Deliverables• Framework Considerations• Lessons Learnt & High-level Conclusions• Recommendations• Proposed Way Ahead


Taking Study’s Output into Work of SESAR Development Programme

• Deliverables include consolidated material from ALL Stakeholders describing :– Business goals,– Operational services,– Operational processes,– Information Services,– Information Model

• Output will feed WP B – Target Concept & Architecture Maintenance

• The results will be high-level enablers for :

– Setting the architectural contexts of the “ATM Performance Partnership”

and

– Identifying operational and system aspects of realising benefits outlined in

ATM Master Plan


OVERVIEW OF SESAR JU – WP-B“TARGET CONCEPT & ARCHITECTURE MAINTENANCE”

• Sub-WP B.0 – GLOBAL CO-ORDINATION & MANAGEMENT

• Sub-WP B.1 – CONSOLIDATION & CO-ORDINATION OF ATM TARGET

CONCEPT

• B4.1 : Development & Maintenance of the ATM Performance

& Business Aspects of the European ATM Enterprise

Architecture• B4.2 : Update and maintenance of the development of the Concept of

Operations (CONOPS) and associated ATM Services

• B4.3 : Development of the high level logical system architecture (SOA)

and the technical system architecture (SoS)

• Sub-WP B.5 – PERFORMANCE ANALYSIS OF ATM TARGET CONCEPT


Enterprise Architecture TRSDissemination Workshop


presented by

Dr John R F GuyNATS – Chief Architect European ATM

on behalf of EA TRS Study ConsortiumTHANK FOR YOUR ATTENTIO

N

Documents

8 th June 2009EA TRS Study Consortium1 Enterprise Architecture TRS Dissemination Workshop Overview of Study, Background & Deliverables presented by Dr