© 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
11-D10_NATS_Approach_to_ EA_
May 11, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
© NATS Ltd June 2009
NATS Approach to Enterprise ArchitectureAn Introductory Summary
EA TRS Dissemination Workshop
8th June 2009
presented byDr John R F Guy
NATS – Chief Architect European ATM
© 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
© 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
© 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 NERL’s systems for SESAR
© 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
© NATS Ltd June 2009
Hurn R&Dand 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
© 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
© NATS Ltd June 2009
What is “Enterprise Architecture” ?
© 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
© NATS Ltd June 2009
What is the Value of Enterprise Architecture?
»Quantitative vs. Qualitative
»Who are the Stakeholders ?
»How to systematically add more value ?
© 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
© NATS Ltd June 2009
The NERL Roadmap
» The Need for a Roadmap
» The Roadmap Development Process
» NERL Roadmap Layers
© 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
© NATS Ltd June 2009
The Relationship between the Roadmap and the Long Term Investment Plan
OperationalStrategy
Technical System Architecture &
TechnologyStrategy
InformationArchitecture
NATS Investment Roadmap
Long Term Investment Plan
Discretionary StrategicProjects
Core SustainmentProjects
Sustain
Deployed ATM System
AssetsAsset Base
Buildingsand
Facilities
Add&
Change
Guides&
Shapes
Guide&
Shape
Asset HealthReviews
Asset Management
© NATS Ltd June 2009
© NATS Ltd June 2009
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
© NATS Ltd June 2009
The Roadmap Development Process
Iterations
Cost & Benefit ModellingSpreadsheet based model containsestimates 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
© NATS Ltd June 2009
1717
Business Objectives
Why
Operational & Technical Drivers
What
Benefits & Impacts
Who
Other Changes
Functionality Changes
How
System ChangesWhere
Acquisition
Tranche / Delivery
When
How Much
NERL Roadmap Layers
© 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 ?
© 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
© NATS Ltd June 2009
MODAF
»What is MODAF ?» The UK Ministry of Defence’s Architecture Framework
» A standardised meta-model, set of views & ontology
© 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
© 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
© 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
© NATS Ltd June 2009
OV-5 : Operational Activity Model
Human Performance
Va
lue
Capacity
Human Performance
Capacity
Human Performance
Human Performance
Capacity
Human Performance
Capacity
Human Performance
CapacityCapacity
Human Performance
Human Performance
Human Performance
London Area
Control
Prestwick Centre
Phase 1
TC Tools, iFACTS, nPC on legacyInitial P-RNAV routes
Phase 2
Heathrow Mixed ModeLL stacks moved
Closely spaced P-RNAV routesCapacity benefits from sectorisations only fully realised with conformance monitoring tools
Introduction of first stages of InteroperabilityController tools not dependent on iTEC functionality
Phase 3
Controller Tools which require iTECContinued roll out of new technology – ADS-B, multilateration.
NOTE: CORA and Full CDM are outside the scope of the roadmap.
AMAN Sequencing/Metering & PST – LL /
KK / GW / SS
Multi Sector Planer
(En-Route)
Vertical Conformance
Monitoring
Longitudinal Conformance
Monitoring
Advanced Planner Tools
Safety Net Advanced Restricted Airspace
Penetration Warning
DMAN
Departure Sequencing -
LL
Safety Net
Minimum Safe Altitude
Warning
Safety Net
Glide slopeMonitor
Human Performance
Safety Net
Minimum Safe Altitude
Warning
London Terminal Control
Key:1 2 3 32
Va
lue
Capacity
Human Performance
Functional Driver
Has a beneficial impact on Human Performance
Has a beneficial impact on Costs
Has a beneficial impact on Capacity
Green if has a beneficial impact on Environmental Performance
2
9
9
11
1415 21
22 23
24
28 29
Text and box border colour indicates priority:
Level 1 – Red – highest Level 2 – PurpleLevel 3 – Blue – lowest
Configuration RecordWhat If – Batch 1 based on Version: 1.11Date: 5 Jan 07Last Edited by: Dave Colquitt
Change since last issue if present
Functional Dependencies
TC South WestQ1 08
Capacity
NUS
Q4 12
Capacity
2829
Unspecified
Airspace
Capacity
2829
Unspecified
Airspace
Capacity
222829
Unspecified
Airspace
Capacity
222829
Unspecified
Airspace
Va
lue
Capacity
Human Performance
Enhanced Airspace
Management Cell
40
Human Performance
Safety Net E2STCA with Conflicting
SFL Highlight1
CapacityCapacity
6
6TC North
EastQ2 09
CapitalQ4 09
Contains P-RNAV Routes
Capacity
Surveillance 3nm
Separation MRT
3
Human Performance
Va
lue
Capacity
Military
Base of Cover
Proximity Warning 34
Capacity
Human Performance
WX DataNear Real
Time Radar Display
5
Human Performance
Workload management
RTF Frequency Occupation –
Phase 1 – Offline Reporting 33
Va
lue
36
Human Performance
Interop
Airfield Interface
Human Performance
Safety Net E2STCA with Conflicting
SFL Highlight1
Human Performance
Va
lueIntegration of
LMARS East with LAC
7
Capacity
CentralQ4 09
Capacity
DTY
Q4 10
Human Performance
Safety Net E2STCA with Conflicting
SFL Highlight1
Human Performance
Safety Net
CAITPhase 1& 2
4
Human Performance
Safety Net
CAITPhase 1& 2
4
Va
lue
Capacity
10
Human Performance
Electronic Tactical HMI
and Co-ordination Data Entry
Va
lue
Capacity
Human Performance
Electronic Tactical HMI
and Co-ordination Data Entry10
Human Performance
Va
lue
Capacity
MilitaryBase of Cover
Proximity Warning 34
Capacity
Surveillance
Wind Farm Plot Filtering
35
Capacity
Surveillance
Mode-S Flight ID
2
Capacity
Surveillance 3nm
separation MRT
3
Human Performance
6Capacity
AMAN Stack
Departure Time –
PH / PF / CC
Capacity
GWY Split
Q4 07
Capacity
Oceanic Hi Level Sector
TransferQ4 08
Capacity
Surveillance
Mode S Flight ID
Human Performance
Workload management
RTF Frequency Occupation –
Phase 1 – Offline Reporting 33
Capacity
6
Human Performance
AMAN Stack
Departure Time – LL /
KK / GW / SS / LC
Capacity
Surveillance
Mode S Flight ID
2
Va
lue
Human Performance
Interop
Airfield Interface
36
Human Performance
Safety Net Restricted Airspace
Penetration Warning 12
Human Performance
Ob
lig
ati
on
Capacity
Basic Datalink
13
Capacity
Human Performance
Lateral Conformance
Monitor (TMA)
16
Capacity
Human Performance
Dynamic Video Maps
19
Human Performance
Workload management
RTF Frequency Occupation –
Phase 2 – Online Reporting 33
Capacity
181115
Mixed Mode @ Heathrow
Q1 11
Contains P-RNAV Routes
Capacity
1617
Cowly/Welin
Q1 11
Capacity
15
BNN / LAM
Q4 11
Capacity
15
BIG / OCK
Q4 12
Capacity
Human Performance
Approach Path Monitor
18
Human Performance
Ob
lig
ati
on
Capacity
Interop
OLDI 3 / SYSCO
Capacity
Human Performance
Tactical Separation
Monitor (TMA)
17
Human Performance
Pilot Intent Monitoring CFL/SFL
8
Va
lue
Human Performance
Interop
Airfield Interface
36
Capacity
Surveillance
Wind Farm Plot Filtering
35Capacity
Flight Trajectories from AOC
20
Human Performance
Capacity
Basic Datalink
13
Human Performance
Pilot Intent Monitoring CFL/SFL
8
Human Performance
Safety Net Restricted Airspace
Penetration Warning 12
Human Performance
Va
lue
Capacity
Military
Base of Cover
Proximity Warning 34
Human Performance
Capacity
Interop
OLDI 3 / SYSCO
14
Capacity
Human Performance
Dynamic Video Maps
19
Capacity
Human Performance
WX DataNear Real
Time Radar Display
5
Capacity
Surveillance 3nm
Separation MRT
3
Va
lue
Capacity
InteropOnward
Routed Data to/from Military 32
Human Performance
Workload management
RTF Frequency Occupation –
Phase 2 – Online Reporting 33
Human Performance
Workload management
RTF Frequency Occupation –
Phase 1 – Offline Reporting 33
Capacity
Dublin area TMA
InterfaceQ4 10
Contains P-RNAV Routes
Capacity
15
ScTMA Stage 2Q1 11
Capacity
15
MTMA Stage
2Q4 11
Human Performance
Capacity
Basic Datalink
13
Human Performance
Capacity
Lateral Conformance
Monitor
16
Human Performance
Safety Net Restricted Airspace
Penetration Warning 12
Capacity
Human Performance
Dynamic Video Maps
19
Va
lue
Capacity
InteropOnward
Routed Data to/from Military 32
Human Performance
Pilot Intent Monitoring CFL/SFL
8
Capacity
Human Performance
Tactical Separation
Monitor (En-Route)
17
Capacity
Human Performance
Tactical Separation
Monitor (TMA)
17
Human Performance
Capacity
Interop
OLDI 3 / SYSCO
14
Capacity
Human Performance
WX DataNear Real
Time Radar Display
5
Capacity
Human Performance
AMAN Sequencing / Metering & PST PF / PH / CC
15
Human Performance
Workload management
RTF Frequency Occupation –
Phase 2 – Online Reporting 33
Contains P-RNAV Routes
Capacity
222829
Unspecified
Airspace
Capacity
222829
Unspecified
Airspace
Va
lue
Capacity
Human Performance
Multi Sector Planner (TMA)
22
Capacity
Human Performance
Advanced Datalink
25
Capacity
Interop
IOP
26
Human PerformanceSafety Net Advanced Restricted Airspace
Penetration Warning 24
Human Performance
Safety Net
Mode S DAPs with E2STCA 31
Human Performance
Capacity
27
Integrated AMAN /
DMAN - LL
Capacity
Mode SDAPs with
TP
30
Va
lue
Human Performance
Graphical Route Editing
38
Va
lue
Capacity
Dynamic Sectorisation
37
Capacity
P-RNAV Route
Allocation
39
Capacity
Interop
IOP
26
Capacity
Mode SDAPs with
TP
30
Human Performance
Safety Net
Mode S DAPs with E2STCA 31
Capacity
Human Performance
Advanced Datalink
25
Capacity
Human Performance
Vertical Conformance
Monitor
28
Capacity
Human Performance
Longitudinal Conformance
Monitor
29
Va
lue
Human Performance
Graphical Route Editing
38
Va
lue
Capacity
Dynamic Sectorisation
37
Va
lue
Capacity
Human Performance
Multi Sector Planner
(En-Route)
22
Va
lue
Capacity
Human Performance
Multi Sector Planner (TMA)
22
Capacity
Human Performance
Advanced Datalink
25Capacity
Mode SDAPs with
TP
30
Capacity
Interop
IOP
26
Capacity
Human Performance
Vertical Conformance
Monitor
28
Capacity
Human Performance
Longitudinal Conformance
Monitor
29
Human PerformanceSafety NetAdvanced Restricted Airspace
Penetration Warning 24
Human Performance
Safety Net
Mode S DAPS with E2STCA 31
Va
lue
Human Performance
Graphical Route Editing
38
Va
lue
Capacity
Dynamic Sectorisation
37
Capacity
Human Performance
Advanced Planner Tools
23
Capacity
P-RNAV Route
Allocation
39
Key:1 2 3 32
Val
ue
Capacity
Human Performance
Functional Driver
Has a beneficial impact on Human Performance
Has a beneficial impact on Costs
Has a beneficial impact on Capacity
Green if has a beneficial impact on Environmental Performance
Text and box border colour indicates priority:
Level 1 – Red – highest Level 2 – PurpleLevel 3 – Blue – lowest
Change since last issue if present
Functional Dependencies
© NATS Ltd June 2009
SV-5 : Ops Activity to System Function Matrix
System Component FDP SDP SNET Tact HMINumber of Products (inc dupls) = 44
Facility OpF# Operational FunctionTC 1 Operational Function 1 NODE NODETC 3 Operational Function 2 NODE NODETC 6 Operational Function 3 NODE
TC 2 Operational Function 4NAS
CCDS?NODE NODE NODE
TC 4 Operational Function 5 NODE NODETC 5 Operational Function 6TC 10 Operational Function 7 NAS COTSTC 34 Operational Function 7 NODE NODE NODETC 33 Operational Function 8TC 36 Operational Function 9 EFD
AC 1 Operational Function 1 NODE NERC NERC
AC 2 Operational Function 2NASSFS
CCDS?NODE NERC NERC
AC 7 Operational Function 3NAS
EDDUS
PC 3 Operational Function 1 NODE NODEPC 1 Operational Function 2 NODE NODE
PC 2 Operational Function 6NAS
CCDS?NODE NODE NODE
PC 4 Operational Function 7 NODE NODEPC 6 Operational Function 8 NODEPC 10 Operational Function 9 NAS COTSPC 34 Operational Function 10 NODE NODE NODEPC 33 Operational Function 11PC 35 Operational Function 12 NODEPC 6 Operational Function 13 NODEPC 36 Operational Function 15 EFD
© NATS Ltd June 2009
Swanwick AC
Swanwick TC
Prestwick
iFACTS
iFACTS
2Mode S/ ESTCA
/SFL
Mode S / ARTAS
nSISARTAS
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 2Implementing new infrastructure upon which to deploy enhanced capability
Phase 1
Adding capability to existing infrastructure
Phase 3Longer-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 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
© NATS Ltd June 2009
How it all fits together
Functional DriverDocument
(OV-1)
OV-5 Operational Activity Model
High LevelArchitectural
EvolutionDiagram
Deployment Model(StV-3)
SV-5 Ops Activityto System
Function Matrix+ SV-3
ArchitecturalEvolution 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
© 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» Don’t avoid it !
» Communication is difficult and has to be worked hard» Without good stakeholder communication, you will fail !
© 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 can’t
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)
© 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
© 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 ...
© NATS Ltd June 2009
NATS Approach to Enterprise ArchitectureAn Introductory Summary
EA TRS Dissemination Workshop
8th June 2009
presented byDr John R F Guy
NATS – Chief Architect European ATM
THANK YOU FOR YOUR ATTENTIO
N
Related Documents
