Section 1. KHA Enterprise Architecture Program Management

1.1    Governance and Principles

Governance and principles document the way that policy and decision making will occur within the Enterprise Architecture (EA) program.  This is also where the underlying principles of the EA program are articulated.

• The Chief Architect is the principle Program Manager for the KHA EA program and will direct the program under the strategic guidance of the KHA executive managers.

• The KHA EA program will be implemented using the Enterprise Architecture EA³ Cube Framework.

• Emphasis will be placed on the alignment of the KHA enterprise with strategic goals.  Specifically the concept of:

- Enterprise Architecture = Strategy + Business + Technology  

• The repository for KHA EA information will be web based designed using the Living Enterprise ^TM   structure.

• The KHA EA will reflect the following principles, and a high emphasis that KHA’s places on:

- Information sharing

- Stake holder participation

- The use commercial products that are based on open standards

- The recognition that Information Technology (IT) is a means and not an end

• The recognition that EA adds value to planning, decision making and communication.

1.2    Support for Strategy and Business

One of the main purposes for the EA program is to support and improve the KHA enterprise’s strategic and business planning processes, as well as to identify performance gaps that EA components can help close.  This is done by:

• Depicting how the EA components are currently being used

• Identifying new processes and technologies that can be implemented in future views to improve the strategic position of the enterprise

It is important to show the linkage of the EA program to the accomplishments of the enterprise’s strategic goals, and to clearly show how EA components support the lines of business activities.

1.3    EA Roles and Responsibilities

A listing of KHA’s EA development effort stakeholders, their roles, and responsibilities is located on the EA Program Tab.  Please click the following link to view this information.

Link to EA Program Tab

1.4    EA Program Performance Measures

The performance measures document how the effectiveness and efficiency of the EA program will be measured.  Outcome measures identify progress being made toward some new end-state.  Output measures provide data on activities and things.  The performance of the KHA EA program will be measured using the Balanced Scorecard method in which:

• Outcome Measure    =   Qualitative; reaching an end state

• Output Measure         =  Quantitative

Please click the following link to view KHA’s Performance Measures:

Link to Strategic Initiatives Detailed Level View

Section 2. KHA Current Architecture Summary

2.1    Strategic Goals and Initiatives

Strategic goals and initiatives identify how the EA program and specific EA components support the attainment of the enterprise’s strategic level goals.  The Kitty Hawk Aeronautics 2007-2010 Strategic Plan contains a listing of KHA’s strategic goals and initiatives.  However, a clearer view of how the EA components and strategic initiatives are involved in each strategic goal can be found at the following link:     Link to Strategic Initiatives Medium Level View

2.2    Business Processes and Information Flows

The business process and information flows emphasize the role that EA plays in supporting business process analysis and improvement, as well as identifying and optimizing information flows with and between these processes.  KHA’s main Line of Business (LOB) services and associated information flows in each LOB is also depicted.  Detailed diagrams of information flows and data structure are provided.

• The KHA LOB descriptions, which can be view at Link to Business Process High Level View includes (but is not limited to) information on:

- KHA Business Overview

- KHA Executive Team Profile

- Relationship of Business Activities to Strategic Goals

- KHA Organizational Chart

- KHA Market Outlook and Competitive Strategy

- KHA Business Cycle

The KHA Knowledge Warehouse contains a detailed description and views of the KHA Knowledge Management Plan.  It provides both an “as-is” (current state) depiction and a “to-be” future view of KHA knowledge management activities.

          Link to Information Flows High Level View

The KHA Warehouse Inventory System Entity Relationship Diagram (ERD) can be viewed at:

          Link to Information Flows Medium Level View

• The three basic elements in ERD models are:

-          Entities are the "things" about which we seek information.

-          Attributes are the data we collect about the entities.

-          Relationships provide the structure needed to draw information from multiple entities.

The KHA Data Dictionary, which is a collection of descriptions of the data objects or items in a data model for the benefit of programmers and others who need to refer to them, is located at

         Link to Information Flows Detailed View

Specific fields contained in the data dictionary are:

2.3          Systems and Applications

Identified here is how current KHA EA components and artifacts at the Systems and Applications level of the EA³ Framework support the information flows that are required for LOBs throughout the KHA enterprise.  The system and application views depict how well the IT systems and front/back office services provide the functionality needed by the enterprise.  These views can be found at the following links:

            Link to Systems and Services High Level View

            Link to Systems and Services Medium Level View

            Link to Systems and Services Detailed View

2.4          Technology Infrastructure

The technology infrastructure consists of the voice, data, and video EA components and artifacts that make up the Technology and Infrastructure level of the EA³ Framework. The KHA IT department offers service across the organization in accordance to relevant Service Level Agreements.  KHA services provide and seamless communications infrastructure and enhance the enterprise level information sharing environment. The specific information on the services KHA provides is located at

     Link to Common Operating Environment High Level View 

Descriptions of the services include detail in the following categories:

• Service Name

• Description

• Service Level Agreement

• Service Options

• Service Charges

2.5          IT Security

The sections describes the KHA approach to IT security.  At KHA IT security is an integral part of all of our strategic goals and initiatives.  The overall success of the KHA is directly linked to our ability to provide accurate and properly authenticated information throughout the enterprise. A depiction of the high level artifacts for KHA’s security infrastructure can be found at

          Link to Security Solutions High Level View

The goal is to secure the front and back office applications, infrastructure services, access profiles for software service providers, and business partners.

Additional information is also available on other general elements of the KHA Security Plans to include:

• Information Security

• Personnel Security

• Operational Security

• Physical Security

• Network Security

Link to Security Solutions Medium Level View

2.6    EA Standards

EA standards document the Technical Standards Reference Model (TRSM) which provides EA standards for voice, data, video, and IT security.   EA standards are the key element of configuration management process.  KHA EA standards that are governed by:

• Institute of Electrical & Electronics Engineers, Inc. (IEEE)

• International Organization for Standardization (ISO)

• International Telecommunication Union (ITU)

• Military Standard (MIL-STD)

• Synchronized Multimedia Integration Language   (SMIL)

• American National Standards Institute (ANSI)

• Federal Information Processing Standard (FIPS)

These EA standards are the key element of configuration management process, and can be found at

          Link to EA Standards Tab

Section 3. Future Architecture Summary

3.1          Future Operating Scenario

Future operating scenarios describe a vision of situations that the enterprise will experience while conducting business in the newly architected environment.  Planning assumptions are contained in the scenarios.  These planning assumptions identify new capabilities and resources that will be needed if the enterprise is to be successful in the future scenarios. 

          Link to Future EA Views (Scenarios) Tab

3.2          Sequencing Plan

The Sequencing Plan documents the timeframe for implementing the new EA components and artifacts.  KHA is integrating our front office and back office systems into a more streamline architecture. The major components of this new architecture include the implementation of an Enterprise Service Bus, a Knowledge Warehouse, and the KHA Living Enterprise ^TM EA Repository.  By using the EA repository authorized employees in all line of business will have access to enterprise level information.

Front office systems will connect to the ESB in the following order Commercial Division Systems, Defense Division Systems, Space Division Systems, and finally Research and Development Division Systems.  Functionality and data from the legacy USAF Geo Talk System will migrate to the USAF Ultra-Low-Latency Satellite Communications System, which will connect to the ESB.   (See: Figure 1 Sequencing Plan – Front Office Systems)

Back office systems will also connect to the ESB, the order of this transition is depicted in Figure 3, Sequencing Plan – Back Office Systems.  A KHA Enterprise Accounting System is established by migrating the separate legacy finance, payroll, and general ledger accounting systems.  The new KHA Knowledge Warehouse will be assessable through the EA repository.

© 2008 CMU/Boeing Class - all rights reserved