The Role of Enterprise Architecture in Moving to an AIM Environment

Transcription

1 The Role of Enterprise Architecture in Moving to an AIM Environment Pierre Truter Manager ICT Planning Airservices Australia ICAO: Enabling the Net-Centric Information Environment 2 June

2 AIS to AIM The Airservices Approach AIM defined as: Need to address all current and future needs of ATS and flight operations. (Strategic, Pre-Tactical and Tactical Planning Stages) The basis for Collaborative Decision Making (CDM). Net-Centric Approach. Every system is a node in the network. Airservices Australia AIM History Started planning future AIM in Various systems, different technologies. Only common entity data / information. Many digital systems, but no net-centric approach. Where is AIM s boundary? Airservices approach, 6 core information domains: Air Traffic Management. Air Safety. Board Governance & Compliance. Legislation & Regulatory Obligations. Business Management & Administration. External Stakeholders & Environment. 2

3 Executive Chair Business GM Operations GM CFO Air Traffic Air Board Legislation & Business External Control Safety Governance & Regulat ory Management & Stakeholders & Compliance Obligations Administration Environment Core information Domains People & Change Manager Airservices information will be managed so that it is: Captured once and used many times and there is a single authoritative source for all high-value business critical information Created, organised, used and protected in accordance with its value to the business and stakeholders Fit for purpose and fit for the future, accessible and flexible to support forecasting, planning and decision-making across the business Managed according to its lifecycle and independent of technology systems Compliant with our legislative and regulatory responsibilities transitioning from paper-based to electronic records Leveraged, where appropriate, to create intellectual property as a commercial product for aviation industries and other customers Ex e cu ti ve Chair Busines s GM Operations GM CFO Ai r Tr affic Ai r Cont r ol Safet y Boar d Govern ance & Compl iance Legisl ation & Regulat or y Obligations Co r e info rmation Domains Busi nes Ma na ge ment & Admi nistration Ext ernal St akeholder s & Envi ronm ent People & Change Manager Air Traffic Air Board Legislation & Business External Control Safety Governance & Regulatory Management & Stakeholders & Compliance Obligations Administration Environment Core Information Domains The Process So Far 1. Determine the current systems baseline. 2. Interviews to determine users perception and IM issues. 3. The result was: Information Management Capability Framework. Information Management Architecture Framework. Information Management GAP analysis. Airservices Australia Enterprise Capability Development Air Traffic Control Air Safety Board Governance & Compliance Legislation & Regulatory Obligations Business Management & Administration External Stakeholders & Environment Core Information Domains CURRENT STATE FUTURE STATES Key features of the Airservices Australian Air Traffic Management Target Operational Concept 2025* Significantly enhanced situational awareness for all airspace users the provision of self-separation except in highest density airspace separation services may be provided by third party ATM the management of flights from inception until arrival at the destination parking position the principles of uniformity and seamless service by the promotion of a homogeneous environment a focus on collaborative decision-making demand/capacity management throughout the flight life cycle dynamic conflict management based on risk assessment to replace rigid aircraft separation standards the facilitation of user preferences and the application of air traffic control for intervention by exception. GAP & CRITICAL ANALYSIS STRATEGY DEVELOPMENT CAPABILITY DEVELOPMENT BUSINESS TRANSFORMATION WHO WHAT, WHY, HOW, WHEN, WHERE? Airservices information will be managed so that it is: The end state ATM system will have a capability to dynamically optimise flight trajectories, taking into account traffic complexity, weather and physical environmental constraints. The capability implies the introduction of significantly higher levels of automation, information integration and dynamic system management than are in use today. Captured once and used many times and there is a single authoritative source for all high-value business critical information Created, organised, used and protected in accordance with its value to the business and stakeholders Fit for purpose and fit for the future, accessible and flexible to support forecasting, planning and decision-making across the business Managed according to its lifecycle and independent of technology systems Compliant with our legislative and regulatory responsibilities transitioning from paper-based to electronic records Leveraged, where appropriate, to create intellectual property as a commercial product for aviation industries and other customers 3

4 Key Information Management Principles Information Management Strategic Framework Airservices information will be managed so that it is: Captured once and used many times and there is a single authoritative source for all high-value operational and business critical information. Created, organised, used and protected in accordance with its value to the business and stakeholders. Fit for purpose and fit for the future, accessible and flexible to support forecasting, planning and decision-making across the business. Managed according to its lifecycle and independent of technology systems. Compliant with our legislative and regulatory responsibilities transitioning from paper-based to electronic records. Leveraged, where appropriate, to create intellectual property as a commercial product for aviation industries and other customers. 4

5 The Information Management Strategic Framework Air Traffic Management Air Safety Board Governance & Compliance Legislation & Regulatory Obligations Business Management & Administration External Stakeholders & Environment Core Information Domains 5

6 The Concept of Enterprise Architecture Enterprise Architecture: The analysis and documentation of an enterprise in its current and future states from a strategy, business, and technology perspective. EA = S + B + T An Introduction to Enterprise Architecture 2005 IT Systems Video Strategic Initiative 1 Process 1 Data Process 2 Web Services Voice Data Dictionary Applications Strategic Initiative 2 Object Data Reuse Flows Non-integrated processes and systems in different parts of the enterprise Security, Standards, Workforce Technology Business - Strategy Lines of Business Goals & Initiatives Products & Services Data & Information Systems & Applications s & Enterprise Architecture C O M P O N E N T S Strategy Business Information Systems s Strategic Initiative 1 Systems Applications Data Video Strategic Initiative 2 Process 1 Process 2 Process 3 Object Data Reuse Data Flows Dictionary Web Services Voice Integrated processes and systems across the entire enterprise Business & & Technology Alignment EA = S+B+T Enterprise Architecture (EA) = Strategy (S) + Business (B) + Technology (T) 6

7 Enterprise Architecture - Drivers EA documents both current & future views of the enterprise Changes in an architecture come from 3 levels of input: Executive input on strategic direction and priority Business Manager input on process changes Technology Manager input on supporting IT changes Capabilities of the Current Enterprise Strategic Tactical New Direction & Goals (Leadership Team) New Business Priorities (Management Team) Emerging Technologies (IT Support Team) Operating Scenarios Program Plans Capabilities of the Future Enterprise 7

8 Enterprise Architecture Outcomes The Enterprise Architecture outcomes help to: Achieve strategic goals that depend on IT resources. Improve business performance by maximizing IT efficiency. Support the desire of executives and managers to have strategic priorities/business requirements drive IT solutions. Link multiple IT networks, systems, applications, services, and databases across the entire enterprise. Share information between lines of business. Integrate several forms of applications and local/wide area networks that lacked open standards. Reduce duplicative IT resources across the enterprise. Protect data and IT assets that rely on enterprise-wide approaches. Maximize the effective use of limited budgets. Improve human capital management in IT knowledge/skill areas. 8

9 Enterprise Architecture Activities EA activities are two-fold: a management program and a documentation method, which together improve performance through the integration of strategic, business, and technology planning and decision-making. As a management program, EA provides: Resource Alignment: Resource planning and standards determination Standardized Policy: Resource governance and implementation Decision Support: Financial control and configuration management Resource Oversight: Lifecycle approach to development and management As a documentation method, EA provides: EA Approach: A modeling framework &implementation methodology Current Architecture: Views of as-is strategies, processes, resources Future Architecture: Views of to-be strategies, processes, resources EA Management Plan: To move from the current to the future EA 9

10 System Architect / Requirements Integration How? The answer is in the Enterprise Architecture. How do we implement this regulation? How to we meet this compliance requirement? How is this data made available to external systems? How do we ensure system availability? Why? The answer is a Requirement. Why does this firewall exist? Why does this entity exist? What purpose does this dataflow achieve? Why do we perform this business process? Do we still need to support this application? 10

11 Management Portal / Requirements Integration Management Portal will help provide answers to the following questions: Are key projects aligned with ASA strategy? Do ASA have the right balance of risk/reward? Are projects delivering the expected value? Are ASA doing the right projects? Are ASA spending in the right areas? Do ASA have the right resources? 11

12 AIM Building Blocks Preflight Route Optimisation (Based on forecast winds) A. Flextracks (common route) B. UPRs (individual routes) C. UPTs (individual routes and times -4DT) Preflight Demand / Capacity Balancing ATM Long-range Optimal Flow Tool (ALOFT) DST that allocates required times at Outer Fix early in cruise, allowing fuel efficient flight time adjustments AMAN (MAESTRO) DST that allocates required times at Feeder Fixes for optimum sequence at runway threshold (DST based on forecast airport acceptance rates) Central Traffic Management System CTMS Ground holding etc in collaboration with airlines DMAN DST linked to AMAN allocates departure times between AMAN landings CDTI / EFB Surface moving map with ADS-B traffic (SafeRoute) A-SMGCS Surface surveillance - safety runway incursion prevention & optimum taxi (fuel/emissions) RNP Departures Increased payload ADS-B ITP Access most fuel efficient levels Tailored Arrivals Engine idle descents to hit allocated FF time RNP-AR Arrivals Shorter, lower noise, fuel & emissions GBAS Precision landing system leading to curved approaches & CatII, CatIII ops A-SMGCS Surface surveillance - safety (runway incursion prevention) & optimum taxi (fuel) CDTI / EFB Surface moving map with ADS-B traffic (SafeRoute) En Route Oceanic En Route Airport TFM Airlines IN D E X ATC TFM Airlines Takeoff Departure TFM Airlines Arrival Landing ATC TFM Airlines IN D E X Airport TFM Airlines Pushback Take Off Up to 4-5 hrs from ETA INDEX Data exchange between Airlines, Airports, Traffic Flow Management and ATC Outer Fix (eg 120nm) Top of Descent Feeder Fix Runway Threshold + 60 sec + 30 sec + 10 sec INDEX Data exchange between Airlines, Airports, Traffic Flow Management and ATC 12

13 Airservices Australia Enterprise Architecture Online Repository 13

14 Enterprise Architecture Implementation DODAF ENTERPRISE ARCHITECTURE - A FRAMEWORK TM MOTIVATION PEOPLE DATA FUNCTION NETWORK What How Where Who When Why TIME SCOPE List of Things Important to the Business (CONTEXTUAL) List of Processes the Business Performs List of Locations in which the Business Operates List of Organizations Important to the Business List of Events Significant to the Business List of Business Goals/Strat SCOPE (CONTEXTUAL) Planner ENTITY = Class of Business Thing Function = Class of Business Process Node = Major Business Location Ends/Means=Major Bus. Goal/ People = Major Organizations Time = Major Business Event Critical Success Factor Planner e.g. Semantic Model ENTERPRISE MODEL (CONCEPTUAL) e.g. Business Process Model e.g. Business Logistics System e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE MODEL (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Reln = Business Relationship I/O = Business Resources Node = Business Location Link = Business Linkage People = Organization Unit Work = Work Product Time = Business Event Cycle = Business Cycle End = Business Objective Means = Business Strategy Owner MODEL (LOGICAL) e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System Architecture e.g. Human Interface Architecture e.g. Processing Structure e.g., Business Rule Model MODEL (LOGICAL) Designer Ent = Data Entity Reln = Data Relationship Node = I/S Function Proc.= Application Function (Processor, Storage, etc) I/O = User Views Link = Line Characteristics People = Role Work = Deliverable Time = System Event Cycle = Processing Cycle End = Structural Assertion Means =Action Assertion Designer e.g. Physical Data Model TECHNOLOGY MODEL (PHYSICAL) e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY MODEL (PHYSICAL) Builder Ent = Segment/Table/etc. Reln = Pointer/Key/etc. Proc.= Computer Function I/O = Data Elements/Sets Node = Hardware/System Software Link = Line Specifications People = User Work = Screen Format Time = Execute Cycle = Component Cycle End = Condition Means = Action Builder DETAILED REPRESEN- TATIONS (OUT-OF- CONTEXT) e.g. Data Definition e.g. Program e.g. Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- TATIONS (OUT-OF CONTEXT) Ent = Field Reln = Address Proc.= Language Stmt I/O = Control Block Node = Addresses Link = Protocols People = Identity Work = Job Time = Interrupt Cycle = Machine Cycle End = Sub-condition Means = Step Sub- Contractor Sub- Contractor FUNCTIONING ENTERPRISE e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY FUNCTIONING ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture software is available Commercially of the shelf (COTS). 14

15 EA Products Link to Each Other OPERATIONAL CONCEPT ROLES & MISSIONS SET SCOPE FOR ACTIVITY MODEL HIGH-LEVEL OPERATIONAL CONCEPT DESCRIPTION (OV-1) VALUE ADDED: BUSINESS/MISSION PROCESS & RELATIONSHIPS AMONG ACTIVITIES AND OPERATIONAL INFORMATION EXCHANGED ST ATE VECTOR ACTIVITY MODEL (OV-5) A1 A2 A3 VALUE ADDED: SUMMARY LEVEL REPRESENTATION OF ORGANIZATIONS/ROLES, MISSION, AND CONTEXT FOR THE ARCHITECTURE ACTIVITIES MAP TO OPERATIONAL NODES I/OS MAP TO NEEDLINES PERFORMERS OF ACTIVITIES, IF SHOWN ON 0V-5, MAP TO OPERATIONAL NODES OPERATIONAL CONCEPT CONNECTIVITY & INFORMATION EXCHANGES, IF SHOWN ON 0V-1, MAP TO OPERATIONAL NODE CONNECTIVITY DESCRIPTION NEEDLINES & INFORMATION EXCHANGES TECHNICAL STANDARDS PROFILE (TV-1) STANDARDS APPLY AT TO INTERFACES S INTERFACE DESCRIPTION (SV-1) NODE A 1 VALUE ADDED: COMPLETE LIST OF RELEVANT STANDARDS WITH OPTIONS & PARAMETERS COMMS Interface COMMS Interface 1 3 NODE B 2 SATCOM Interface INPUT/OUTPUT LABELS MAP TO OPERATIONAL INFORMATION EXCHANGES (NOT ALWAYS ONE-TO- ONE) OPERATIONAL INFORMATION EXCHANGE MATRIX (OV-3) Nature Identifier/ IER Information of Name of Information Source Transaction Operational Element Purpose/ Collaborative Sender Sender Needline (Identifier/ Triggering Sender Description Size OPFAC Supported Name of Language Scenario Units Event or Owning Performing Media LISI (or functional (Content) Activity (fromov-2) Information (For Multior One- Organization/ Level node, as Exchange) Mission National Way? Unit (e.g., Operations) Req d appropriate) UJTLID) e.g., 1-a 1. 1-n e.g., 2-a n n Recipient OPFAC (or functional node, as appropriate).. Information Destination Recipient Recipient Owning Performing Organization/ Activity Unit (e.g., UJTLID).... INFORMATION EXCHANGES ASSOCIATED WITH EACH NEEDLINE ARE DETAILED IN OV-3 VALUE ADDED: INDIVIDUAL INFORMATION EXCHANGES ASSOCIATED WITH EACH NEEDLINE, PERFORMANCE REQUIREMENTS FOR OPERATIONAL INFORMA- TION EXCHANGES OPERATIONAL NODE CONNECTIVITY DESCRIPTION (OV-2) High-Level Description of Needline Collective summary of information exchanged, including: Needline identifier/name Critical attributes for the given architecture s purpose, such as timeliness, bandwidth, media, etc., Statement of Minimum, Mean, and Maximum requirements for critical attributes From External Source, including Allies, Coalition Partners Nodes Node A Performs: Activity 1 Activity 2 Node Performs: B Activity 2 Activity 3 Node C Performs: Activity 3 To External Destination, including Allies, Coalition Partners Nodes VALUE ADDED: STATEMENT OF OPERATIONAL NODES, ACTIVITIES, AND CRITICAL INFORMATION NEEDS (NEEDLINES & SUMMARY INFORMATION EXCHANGED) 15 OPERATIONAL NODES ARE ASSOCIATEAD WITH S AND S NODES EACH OPERATIONAL NEEDLINE MAPS TO ONE OR MORE S LINKS INFORMATION EXCHANGES RELATED TO DATA ELEMENTS 2 EXTERNAL CONNECTION One-way SATCOM Interface NODE C COMMS Interface 1 4 VALUE ADDED: STATEMENT OF S NODES, S, LINKS & COMPONENT INTERFACES; SUMMARIZED INFORMATION EXCHANGES S DATA EXCHANGE MATRIX (SV-6) SERVICE AREA SERVICE STANDARD Support Applications Web Applications Internet Explorer Version 4.X or better Netscape Version 3.X or better Data Management Business Data Data Universal Numbering System (DUNS) Standards ZIP Code Directory Congressional District Identifier ISO 3166: ISO (1Ocober 1997) and ISO (15 December 1998) (Codes for the Representation of Names of Countries and Their Subdivisions) U.S. State Codes and Territory Codes Catalogue for Federal Domestic Assistance Program Electronic Grants Data Elements Data Interchange Document XML 1.0, W3C Recommendation, 10 February 1998, Rec-xml (Extensible Interchange Markup Language) HTML 4.0 Specification, W3C Recommendation revised 24-apr-1998, Rec-html (Hypertext Markup Language) ANSI ASC X12 (Electronic Data Interchange) Communications World Wide Web IETF RFC-2616 Hypertext Transfer Protocol HTTP/1.1, June 1999 Services Electronic Mail IETF Standard 10/RFC-821/RFC-1869/RFC-1870 Simple Mail Transfer Protocol (SMTP) Service Extensions, November 1995 IETF Standard 11/RFC-822/RFC-1049 Standard for the Format of ARPA Internet Text Messages, 13 August 1982 IETF RFCs Multipurpose Internet Mail Extensions (MIME), November 1996 Nature Identifier/ IER Information Information of Name of Information Source Destination Transaction Operational Element Purpose/ Collaborative Sender Sender OPFAC Recipient Recipient Recipient Needline (Identifier/ Triggering Sender Description Size OPFAC Performing Performing Supported Name of Language Scenario Units Event Media or Owning (or functional Owning LISI (or functional (Content) Activity Activity (fromov-2) Information (For Multior One- Organization/ node, as Organization/ Level node, as Way? (e.g., (e.g., Exchange) Mission National Unit appropriate) Unit Operations) Req d appropriate) UJTLID) UJTLID) e.g., 1-a 1. 1-n e.g., 2-a n n VALUE ADDED: INDIVIDUAL INFORMATION EXCHANGES ASSOCIATED WITH SPECIFIC DATA ELEMENTS 15

16 Summary Using Enterprise Architecture as the underpinning of our modernisation strategy. Airservices Australia, FAA and the US Air Force will shortly start to develop an initial Common Information Model based on the content of Annex 15. The current AS-IS. We hope to mature this concept sufficiently so we can discuss it at the next AIM Global Consortium meeting planned for October 2008 in Sydney. Airservices will also capture it s complete Communication, Navigation and Surveillance networks in our Enterprise Architecture System. 16