Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
NATS Approach to Enterprise Architecture An Introductory Summary EA TRS Dissemination Workshop 8 th  June 2009 presented b...
Presentation Overview <ul><li>NATS History & the Problem / Challenge </li></ul><ul><li>NATS’ reasons for using Enterprise ...
NATS EA History <ul><li>NATS started using Architectural methods several years ago (circa 2002) and developed an initial  ...
The Challenge   <ul><li>Develop a coherent strategy to address: </li></ul><ul><li>Increasing traffic demands </li></ul><ul...
NATS Reasons for EA Approach <ul><li>Have been using Enterprise Architecture to improve our technology management & alignm...
NATS in 2006/7 Hurn R&D and Training College Corporate & Technical Centre UK Airports Control of  Airport Traffic Integrat...
NATS Future Vision Service Oriented Information Bus Infrastructure Datalink with aircraft Prestwick Swanwick Technical Cen...
What is “Enterprise Architecture” ?
Enterprise Architecture :  Some Definitions <ul><li>Enterprise  :  an organised entity or group of entities that share a c...
What is the Value of Enterprise Architecture? <ul><li>Quantitative  vs.  Qualitative </li></ul><ul><li>Who are the Stakeho...
The NATS Enterprise Architecture Approach NERL Business Strategy & Goals Solutions delivered through Programmes & Projects...
The NERL Roadmap <ul><li>The Need for a Roadmap </li></ul><ul><li>The Roadmap Development Process </li></ul><ul><li>NERL R...
The Need for a Roadmap <ul><li>Operational & Business Drivers </li></ul><ul><ul><li>Captures the drivers & lays out the ba...
The Relationship between the Roadmap and the Long Term Investment Plan © NATS Ltd  June 2009 Operational Strategy Technica...
The Roadmap as a Management Tool Project Context Investment Roadmap Investment Planning (NIG) Investment Proposal Investme...
The Roadmap Development Process Iterations <ul><li>Cost & Benefit Modelling </li></ul><ul><ul><li>Spreadsheet based model ...
How Much NERL Roadmap Layers Business Objectives Why Operational & Technical Drivers What Benefits & Impacts Who Other Cha...
Enterprise Architecture Frameworks <ul><li>… . there are a lot to choose from .… </li></ul><ul><li>The Zachman Framework <...
Why use MODAF for our Roadmap ? <ul><li>This must have been done before ? </li></ul><ul><ul><li>Do not re-invent </li></ul...
MODAF <ul><li>What is MODAF ? </li></ul><ul><ul><li>The UK Ministry of Defence’s Architecture Framework </li></ul></ul><ul...
How should we use MODAF ? <ul><li>MODAF CAN be : </li></ul><ul><ul><li>Daunting </li></ul></ul><ul><ul><li>Too many views ...
Roadmap Views - a summary of views and why chosen <ul><li>MODAF uses “views” to express Architectural aspects </li></ul><u...
NATS Application of MODAF (to date) <ul><li>MODAF Views </li></ul><ul><ul><li>OV-1/OV-5 </li></ul></ul><ul><ul><li>SV-5/SV...
OV-5 : Operational Activity Model
SV-5 : Ops Activity to System Function Matrix
StV-3 : Capability Phasing   Swanwick AC Swanwick TC Prestwick iFACTS iFACTS 2 Mode S/  ESTCA  /SFL Mode S /  ARTAS nSIS A...
How it all fits together Functional Driver Document (OV-1) OV-5 Operational  Activity Model High Level Architectural  Evol...
Lessons Learnt (1/2) <ul><li>Learn through actions </li></ul><ul><ul><li>Start “small” </li></ul></ul><ul><ul><li>Identify...
<ul><li>Use of an Architecture Framework (AF) is essential </li></ul><ul><ul><li>It gives a structure to architecture anal...
Future of Enterprise Architecture at NATS <ul><li>We are still on a journey… </li></ul><ul><li>Roadmap alignment with othe...
Summary <ul><li>Baseline NERL Roadmap in place </li></ul><ul><li>Roadmap now being used to support business decision-makin...
NATS Approach to Enterprise Architecture An Introductory Summary EA TRS Dissemination Workshop 8 th  June 2009 presented b...
Upcoming SlideShare
Loading in …5
×

11-D10_NATS_Approach_to_ EA_

838 views

Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

11-D10_NATS_Approach_to_ EA_

  1. 1. 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. 2. Presentation Overview <ul><li>NATS History & the Problem / Challenge </li></ul><ul><li>NATS’ reasons for using Enterprise Architecture (EA) </li></ul><ul><li>What is EA and the value of EA </li></ul><ul><li>NATS EA approach </li></ul><ul><li>Roadmap layers </li></ul><ul><li>EA Frameworks </li></ul><ul><li>Lessons learned </li></ul><ul><li>The Future of EA at NATS </li></ul><ul><li>Summary </li></ul>
  3. 3. NATS EA History <ul><li>NATS started using Architectural methods several years ago (circa 2002) and developed an initial Operational & Technical Strategy (“COATS”) </li></ul><ul><li>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 </li></ul><ul><li>In 2006, Formal Enterprise Architecture Framework (based on MODAF) was adopted to create ”The Future Centres Roadmap” </li></ul><ul><li>The EA approach was “institutionalised” in 2007 with the formation of the Technology Strategy Group (TSG) </li></ul><ul><li>The Roadmap was extended from Future Centres to NERL-wide technology in 2007 </li></ul><ul><li>In 2008, the NERL (NATS En-Route Ltd.) Roadmap was implemented </li></ul><ul><li>In 2009, the NERL Development & Investment Directorate was created to provide a strategic focus for NERL, including Enterprise Architecture </li></ul>
  4. 4. The Challenge <ul><li>Develop a coherent strategy to address: </li></ul><ul><li>Increasing traffic demands </li></ul><ul><li>Improving safety & environmental performance </li></ul><ul><li>Minimising operating costs </li></ul><ul><li>Contractual commitments </li></ul><ul><li>Credible evolution strategy </li></ul><ul><li>Positioning NERL’s systems for SESAR </li></ul>
  5. 5. NATS Reasons for EA Approach <ul><li>Have been using Enterprise Architecture to improve our technology management & alignment with operational & business goals ........ because …..… </li></ul><ul><ul><li>NERL approach to systems development was not coherent, especially with respect to systems at Centres </li></ul></ul><ul><ul><li>The value to the business of technical systems was inconsistent </li></ul></ul><ul><ul><li>Communication of technical solutions to the stakeholder community lacked clarity </li></ul></ul><ul><ul><li>Investment decisions were being made tactically, not strategically </li></ul></ul><ul><ul><li>Scenario planning & modelling was very limited </li></ul></ul>
  6. 6. NATS in 2006/7 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
  7. 7. 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. 8. What is “Enterprise Architecture” ?
  9. 9. Enterprise Architecture : Some Definitions <ul><li>Enterprise : an organised entity or group of entities that share a common set of desired outcomes </li></ul><ul><li>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 </li></ul><ul><li>Value : a measure or set of measures used to assess the success of an entity </li></ul><ul><li>Enterprise Architecture : a formal model-based description that aims at optimising the value that information-centric changes bring to an enterprise </li></ul><ul><li>Enterprise Architecture Framework : A reusable set of models and views that facilitate the creation of an Enterprise Architecture </li></ul>
  10. 10. What is the Value of Enterprise Architecture? <ul><li>Quantitative vs. Qualitative </li></ul><ul><li>Who are the Stakeholders ? </li></ul><ul><li>How to systematically add more value ? </li></ul>
  11. 11. The NATS Enterprise Architecture Approach NERL Business Strategy & Goals Solutions delivered through Programmes & Projects Technical System Architecture & Technology Strategy Operational Strategy
  12. 12. The NERL Roadmap <ul><li>The Need for a Roadmap </li></ul><ul><li>The Roadmap Development Process </li></ul><ul><li>NERL Roadmap Layers </li></ul>
  13. 13. The Need for a Roadmap <ul><li>Operational & Business Drivers </li></ul><ul><ul><li>Captures the drivers & lays out the basis for the strategic evolutionary development of NATS systems </li></ul></ul><ul><ul><li>Aligns the operational needs with the technology solutions (Coherence) </li></ul></ul><ul><li>Communication of the Strategy </li></ul><ul><ul><li>Facilitates communication to all Stakeholders </li></ul></ul><ul><ul><li>Positive tracking of Benefit delivery </li></ul></ul><ul><li>Assurance provided </li></ul><ul><ul><li>Explores ‘What-if’ scenarios and options </li></ul></ul><ul><ul><li>Deliverability of the strategy is assessed </li></ul></ul>
  14. 14. The Relationship between the Roadmap and the Long Term Investment Plan © NATS Ltd June 2009 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
  15. 15. The Roadmap as a Management Tool 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)
  16. 16. The Roadmap Development Process Iterations <ul><li>Cost & Benefit Modelling </li></ul><ul><ul><li>Spreadsheet based model contains </li></ul></ul><ul><ul><li>estimates for </li></ul></ul><ul><ul><ul><li>System developments </li></ul></ul></ul><ul><ul><ul><li>Testing & Deploying </li></ul></ul></ul><ul><ul><ul><li>Training (ATC & Engineering) </li></ul></ul></ul><ul><li>Strategic Requirements </li></ul><ul><ul><li>Technology Evolution Plans </li></ul></ul><ul><ul><li>Strategic Evolution Requirements </li></ul></ul><ul><ul><li>Strategic Project Requirements </li></ul></ul><ul><li>Roadmap Modelling </li></ul><ul><ul><li>Identifies systems impacted by evolution </li></ul></ul><ul><ul><li>Groups changes into “Tranches” & Projects </li></ul></ul><ul><ul><li>Portfolio Deliverability Assessment </li></ul></ul><ul><li>Operational and Technology Strategies </li></ul><ul><ul><li>Functional & Architectural Drivers </li></ul></ul><ul><ul><li>High Level System Evolution </li></ul></ul>
  17. 17. How Much NERL Roadmap Layers Business Objectives Why Operational & Technical Drivers What Benefits & Impacts Who Other Changes Functionality Changes How System Changes Where Acquisition Tranche / Delivery When
  18. 18. Enterprise Architecture Frameworks <ul><li>… . there are a lot to choose from .… </li></ul><ul><li>The Zachman Framework </li></ul><ul><li>DODAF (US Department of Defense Architecture Framework) </li></ul><ul><li>MODAF (UK Ministry of Defence Architecture Framework) </li></ul><ul><li>TOGAF (The Open Group Architecture Framework) </li></ul><ul><li>NAF (NATO Architecture Framework) </li></ul><ul><li>TEAF (US Treasury Enterprise Architecture Framework) </li></ul><ul><li>… . how to select one ? </li></ul>
  19. 19. Why use MODAF for our Roadmap ? <ul><li>This must have been done before ? </li></ul><ul><ul><li>Do not re-invent </li></ul></ul><ul><ul><li>Look to industry best-practice … </li></ul></ul><ul><li>An Architecture Framework ? </li></ul><ul><ul><li>Examples include Zachman, TOGAF, DODAF, MODAF, etc. </li></ul></ul><ul><ul><li>ATM no different to any other large complex “system of systems”, e.g. military </li></ul></ul><ul><ul><li>MODAF contains many of the views we needed </li></ul></ul>MODAF
  20. 20. MODAF <ul><li>What is MODAF ? </li></ul><ul><ul><li>The UK Ministry of Defence’s Architecture Framework </li></ul></ul><ul><ul><li>A standardised meta-model, set of views & ontology </li></ul></ul>
  21. 21. How should we use MODAF ? <ul><li>MODAF CAN be : </li></ul><ul><ul><li>Daunting </li></ul></ul><ul><ul><li>Too many views </li></ul></ul><ul><ul><li>Too much to understand </li></ul></ul><ul><li>We NEED to: </li></ul><ul><ul><li>Focus on the Roadmap goals </li></ul></ul><ul><ul><li>Only choose views of most value </li></ul></ul>
  22. 22. Roadmap Views - a summary of views and why chosen <ul><li>MODAF uses “views” to express Architectural aspects </li></ul><ul><li>MODAF v1.2 has 46 views </li></ul><ul><li>NATS uses 5 </li></ul><ul><ul><li>These define our Architectural Evolution in enough detail to make key decisions & launch projects </li></ul></ul>
  23. 23. NATS Application of MODAF (to date) <ul><li>MODAF Views </li></ul><ul><ul><li>OV-1/OV-5 </li></ul></ul><ul><ul><li>SV-5/SV-3 </li></ul></ul><ul><ul><li>StV-3 </li></ul></ul><ul><li>Non-MODAF views </li></ul><ul><ul><li>Product list/cost estimates </li></ul></ul><ul><ul><li>Development/Deployment matrices </li></ul></ul><ul><ul><li>High-level Architecture </li></ul></ul>MODAF
  24. 24. OV-5 : Operational Activity Model
  25. 25. SV-5 : Ops Activity to System Function Matrix
  26. 26. StV-3 : Capability Phasing Swanwick AC Swanwick TC Prestwick iFACTS iFACTS 2 Mode S/ ESTCA /SFL Mode S / ARTAS nSIS ARTAS 5 Initial TC Tools 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 Phase 3 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 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 Integration 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. 27. 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. 28. Lessons Learnt (1/2) <ul><li>Learn through actions </li></ul><ul><ul><li>Start “small” </li></ul></ul><ul><ul><li>Identify Key Issues </li></ul></ul><ul><li>There is no ideal organisational solution </li></ul><ul><ul><li>Collaboration is essential ! </li></ul></ul><ul><li>Different Stakeholders have different roles at different points of the lifecycle </li></ul><ul><li>Clear responsibilities and accountabilities needed </li></ul><ul><li>Strong Leadership needed </li></ul><ul><ul><li>Gain Executive Sponsorship ! </li></ul></ul><ul><li>Mine the conflict between stakeholders </li></ul><ul><ul><li>Don’t avoid it ! </li></ul></ul><ul><li>Communication is difficult and has to be worked hard </li></ul><ul><ul><li>Without good stakeholder communication, you will fail ! </li></ul></ul>
  29. 29. <ul><li>Use of an Architecture Framework (AF) is essential </li></ul><ul><ul><li>It gives a structure to architecture analysis </li></ul></ul><ul><ul><li>It provides a standard form for communication </li></ul></ul><ul><li>The Real Value of an Architecture Framework is in its Meta-model, not the Views </li></ul><ul><ul><li>The meta-model allows capture of entities & their relationships </li></ul></ul><ul><ul><li>The meta-model ensures consistency between views </li></ul></ul><ul><li>Choose an AF that has good tools support </li></ul><ul><ul><li>Zachman may be an interesting thought-map, but you can’t really use it to develop architecture </li></ul></ul><ul><li>Architecture is only a means </li></ul><ul><ul><li>Focus on the value the architecture modelling provides </li></ul></ul><ul><li>Adapt/Tailor a standard framework to meet your needs </li></ul><ul><ul><li>There is no “one size fits all” </li></ul></ul>Lessons Learnt (2/2)
  30. 30. Future of Enterprise Architecture at NATS <ul><li>We are still on a journey… </li></ul><ul><li>Roadmap alignment with other ANSPs and SESAR is important </li></ul><ul><li>Increasing emphasis on Strategic Business issues </li></ul><ul><li>Service Orientation </li></ul><ul><li>Architecture Governance & Maturity </li></ul><ul><ul><li>Develop EA Maturity Approach </li></ul></ul><ul><ul><li>Improve EA governance </li></ul></ul><ul><ul><li>Raise profile of EA at Executive and Board levels </li></ul></ul><ul><ul><li>Embed EA across the organisation </li></ul></ul>
  31. 31. Summary <ul><li>Baseline NERL Roadmap in place </li></ul><ul><li>Roadmap now being used to support business decision-making </li></ul><ul><li>Significant further opportunities to use EA to manage change in NERL and SESAR </li></ul><ul><li>Recognised Industry EA Leader </li></ul><ul><li>Watch this space ... </li></ul>
  32. 32. 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

×