Presentation is loading. Please wait.

Presentation is loading. Please wait.

© NATS Ltd June 2009 NATS Approach to Enterprise Architecture An Introductory Summary EA TRS Dissemination Workshop 8 th June 2009 presented by Dr John.

Similar presentations


Presentation on theme: "© NATS Ltd June 2009 NATS Approach to Enterprise Architecture An Introductory Summary EA TRS Dissemination Workshop 8 th June 2009 presented by Dr John."— Presentation transcript:

1 © NATS Ltd June 2009 NATS Approach to Enterprise Architecture An Introductory Summary EA TRS Dissemination Workshop 8 th June 2009 presented by Dr John R F Guy NATS – Chief Architect European ATM

2 © NATS Ltd June 2009 Presentation Overview » NATS History & the Problem / Challenge » NATS reasons for using Enterprise Architecture (EA) » What is EA and the value of EA » NATS EA approach » Roadmap layers » EA Frameworks » Lessons learned » The Future of EA at NATS » Summary

3 © NATS Ltd June 2009 NATS EA History » NATS started using Architectural methods several years ago (circa 2002) and developed an initial Operational & Technical Strategy (COATS) » In 2006, an urgent need arose to revise how the specification, development & procurement of FDP/Centres systems was being done – led to a more-holistic, ATM System-wide approach to be taken » In 2006, Formal Enterprise Architecture Framework (based on MODAF) was adopted to create The Future Centres Roadmap » The EA approach was institutionalised in 2007 with the formation of the Technology Strategy Group (TSG) » The Roadmap was extended from Future Centres to NERL-wide technology in 2007 » In 2008, the NERL (NATS En-Route Ltd.) Roadmap was implemented » In 2009, the NERL Development & Investment Directorate was created to provide a strategic focus for NERL, including Enterprise Architecture

4 © NATS Ltd June 2009 The Challenge Develop a coherent strategy to address: » Increasing traffic demands » Improving safety & environmental performance » Minimising operating costs » Contractual commitments » Credible evolution strategy » Positioning NERLs systems for SESAR

5 © NATS Ltd June 2009 NATS Reasons for EA Approach » Have been using Enterprise Architecture to improve our technology management & alignment with operational & business goals because …..… » NERL approach to systems development was not coherent, especially with respect to systems at Centres » The value to the business of technical systems was inconsistent » Communication of technical solutions to the stakeholder community lacked clarity » Investment decisions were being made tactically, not strategically » Scenario planning & modelling was very limited

6 © NATS Ltd June 2009 Hurn R&D and Training College Corporate & Technical Centre UK Airports Control of Airport Traffic Integrated digital communications network Manchester Centre Prestwick Centre Control of Oceanic Traffic Control of Area Traffic Control of Domestic Traffic Co-ordination with adjacent Centres European Flight Management Swanwick Centre West Drayton Centre Control of Area Traffic Control of Terminal Traffic Air Defence Control of Military Traffic MET Information Navigation Communications Surveillance NATS in 2006/7

7 © NATS Ltd June 2009 NATS Future Vision Service Oriented Information Bus Infrastructure Datalink with aircraft Prestwick Swanwick Technical Centre Flexible connectivity of voice communications Multiple information derived for surveillance purposes Connections to UK airports Enterprise-wide control and monitoring capability Real-time interoperability with international ATM service providers Information management and data fusion components in high integrity buildings

8 © NATS Ltd June 2009 What is Enterprise Architecture ?

9 © NATS Ltd June 2009 Enterprise Architecture : Some Definitions » Enterprise : an organised entity or group of entities that share a common set of desired outcomes » Architecture : a description of the structure, organisation and relationships among the set of components of a system and the principles for their development and evolution » Value : a measure or set of measures used to assess the success of an entity » Enterprise Architecture : a formal model-based description that aims at optimising the value that information-centric changes bring to an enterprise » Enterprise Architecture Framework : A reusable set of models and views that facilitate the creation of an Enterprise Architecture

10 © NATS Ltd June 2009 What is the Value of Enterprise Architecture? » Quantitative vs. Qualitative » Who are the Stakeholders ? » How to systematically add more value ?

11 © NATS Ltd June 2009 NERL Business Strategy & Goals Solutions delivered through Programmes & Projects The NATS Enterprise Architecture Approach Technical System Architecture & Technology Strategy Operational Strategy

12 © NATS Ltd June 2009 The NERL Roadmap » The Need for a Roadmap » The Roadmap Development Process » NERL Roadmap Layers

13 © NATS Ltd June 2009 The Need for a Roadmap Operational & Business Drivers » Captures the drivers & lays out the basis for the strategic evolutionary development of NATS systems » Aligns the operational needs with the technology solutions (Coherence) Communication of the Strategy » Facilitates communication to all Stakeholders » Positive tracking of Benefit delivery Assurance provided » Explores What-if scenarios and options » Deliverability of the strategy is assessed

14 © NATS Ltd June 2009 The Relationship between the Roadmap and the Long Term Investment Plan Operational Strategy Technical System Architecture & Technology Strategy Information Architecture NATS Investment Roadmap Long Term Investment Plan Discretionary Strategic Projects Core Sustainment Projects Sustain Deployed ATM System Assets Asset Base Buildings and Facilities Add & Change Guides & Shapes Guide & Shape Asset Health Reviews Asset Management © NATS Ltd June 2009

15 Project Context Investment Roadmap Investment Planning (NIG) Investment Proposal Investment Intelligence Project Design Envelope Strategic Context Strategic Project Requirements SPRs generated from SFRs Technology Evolution Planning (Strategic Functional Requirements) The Roadmap as a Management Tool

16 © NATS Ltd June 2009 The Roadmap Development Process Iterations Cost & Benefit Modelling Spreadsheet based model contains estimates for System developments Testing & Deploying Training (ATC & Engineering) Strategic Requirements Technology Evolution Plans Strategic Evolution Requirements Strategic Project Requirements Roadmap Modelling Identifies systems impacted by evolution Groups changes into Tranches & Projects Portfolio Deliverability Assessment Operational and Technology Strategies Functional & Architectural Drivers High Level System Evolution

17 © NATS Ltd June Business Objectives Why Operational & Technical Drivers What Benefits & Impacts Who Other Changes Functionality Changes How System Changes Where Acquisition Tranche / Delivery When How Much NERL Roadmap Layers

18 © NATS Ltd June 2009 Enterprise Architecture Frameworks …. there are a lot to choose from.… » The Zachman Framework » DODAF (US Department of Defense Architecture Framework) » MODAF (UK Ministry of Defence Architecture Framework) » TOGAF (The Open Group Architecture Framework) » NAF (NATO Architecture Framework) » TEAF (US Treasury Enterprise Architecture Framework) …. how to select one ?

19 © NATS Ltd June 2009 Why use MODAF for our Roadmap ? This must have been done before ? » Do not re-invent » Look to industry best-practice … An Architecture Framework ? » Examples include Zachman, TOGAF, DODAF, MODAF, etc. » ATM no different to any other large complex system of systems, e.g. military » MODAF contains many of the views we needed MODAF

20 © NATS Ltd June 2009 MODAF » What is MODAF ? » The UK Ministry of Defences Architecture Framework » A standardised meta-model, set of views & ontology

21 © NATS Ltd June 2009 How should we use MODAF ? » MODAF CAN be : » Daunting » Too many views » Too much to understand » We NEED to: » Focus on the Roadmap goals » Only choose views of most value

22 © NATS Ltd June 2009 Roadmap Views - a summary of views and why chosen » MODAF uses views to express Architectural aspects » MODAF v1.2 has 46 views » NATS uses 5 » These define our Architectural Evolution in enough detail to make key decisions & launch projects

23 © NATS Ltd June 2009 NATS Application of MODAF (to date) MODAF Views » OV-1/OV-5 » SV-5/SV-3 » StV-3 Non-MODAF views » Product list/cost estimates » Development/Deployment matrices » High-level Architecture MODAF

24 © NATS Ltd June 2009 OV-5 : Operational Activity Model

25 © NATS Ltd June 2009 SV-5 : Ops Activity to System Function Matrix

26 © NATS Ltd June 2009 SwanwickAC SwanwickTC Prestwick iFACTS 2 Mode S/ ESTCA /SFL Mode S / ARTAS nSIS ARTAS 5 Initial TC Tools Phase 1 1 Mil East into AC NERC System & LMARS 3A NAS / Node TC & Prestwick Systems Electronic Flight Data 3 Deploy NSNETS Deploy NSNETS Deploy NSNETS ARTAS and iNCW Initial Common Workstation Phase 3 Advanced Common Workstation 9 Phase 3 build 2 Phase 3 build 2 Phase 3 Build 2 Advanced Tools 10 Phase 3 build 3 Phase 3 build 3 Phase 3 Build 3 Advanced Operations 11 Phase 2 Implementing new infrastructure upon which to deploy enhanced capability Phase 1 Adding capability to existing infrastructure Phase 3 Longer-term development of common advanced operations StV-3 : Capability Phasing AMAN Tools Electronic Flight Data 4 TC & Prestwick Systems AMAN Tools Electronic Flight Data 4 TC & Prestwick Systems Swap to iTEC FDP Swap to iTEC FDP Swap to iTEC FDP Swap to iTEC FDP Swap to iTEC FDP Swap to iTEC FDP iTEC Integratio n 6 Deploy NSNETS Deploy NSNETS Deploy NSNETS Safety Nets 7 ARTAS and iNCW Initial Common Workstation Deploy Tools 8 ARTAS and iNCW Mil East into AC NERC System & LMARS 3A NAS / Node TC & Prestwick Systems Electronic Flight Data 3

27 © NATS Ltd June 2009 How it all fits together Functional Driver Document (OV-1) OV-5 Operational Activity Model High Level Architectural Evolution Diagram Deployment Model (StV-3) SV-5 Ops Activity to System Function Matrix + SV-3 Architectural Evolution Diagrams Cost Model SV-5 Product to Ops Function Matrix Strategic Requirements Related to Operational and Business Drivers Quantify changes in terms of SLOC (S/W) and Capital (H/W) Identifies the system changes required to achieve the functional drivers Identifies the systems impacted by each of the Functional Drivers Describes the required deployment of functions for each Centre Operation Groups the functional change into deliverable groups impacting common areas Description of the Evolution of the Operations towards a target architecture Describes System Evolutions related to Functional Drivers

28 © NATS Ltd June 2009 Lessons Learnt (1/2) » Learn through actions » Start small » Identify Key Issues » There is no ideal organisational solution » Collaboration is essential ! » Different Stakeholders have different roles at different points of the lifecycle » Clear responsibilities and accountabilities needed » Strong Leadership needed » Gain Executive Sponsorship ! » Mine the conflict between stakeholders » Dont avoid it ! » Communication is difficult and has to be worked hard » Without good stakeholder communication, you will fail !

29 © NATS Ltd June 2009 » Use of an Architecture Framework (AF) is essential » It gives a structure to architecture analysis » It provides a standard form for communication » The Real Value of an Architecture Framework is in its Meta-model, not the Views » The meta-model allows capture of entities & their relationships » The meta-model ensures consistency between views » Choose an AF that has good tools support » Zachman may be an interesting thought-map, but you cant really use it to develop architecture » Architecture is only a means » Focus on the value the architecture modelling provides » Adapt/Tailor a standard framework to meet your needs » There is no one size fits all Lessons Learnt (2/2)

30 © NATS Ltd June 2009 Future of Enterprise Architecture at NATS » We are still on a journey… » Roadmap alignment with other ANSPs and SESAR is important » Increasing emphasis on Strategic Business issues » Service Orientation » Architecture Governance & Maturity » Develop EA Maturity Approach » Improve EA governance » Raise profile of EA at Executive and Board levels » Embed EA across the organisation

31 © NATS Ltd June 2009 Summary » Baseline NERL Roadmap in place » Roadmap now being used to support business decision-making » Significant further opportunities to use EA to manage change in NERL and SESAR » Recognised Industry EA Leader » Watch this space...

32 © NATS Ltd June 2009 NATS Approach to Enterprise Architecture An Introductory Summary EA TRS Dissemination Workshop 8 th June 2009 presented by Dr John R F Guy NATS – Chief Architect European ATM THANK YOU FOR YOUR ATTENTION


Download ppt "© NATS Ltd June 2009 NATS Approach to Enterprise Architecture An Introductory Summary EA TRS Dissemination Workshop 8 th June 2009 presented by Dr John."

Similar presentations


Ads by Google