Knowledge Management Plan - AS-IS (Current) Situation

The following knowledge management plan attempts to provide an overview of the current state for knowledge management within Kitty Hawk Aeronautics.

A. The approach to managing data, information, and knowledge across the enterprise

The current approach within Kitty Hawk Aeronautics for knowledge management is that each LOB unit is responsible for managing their own individual operational data. This includes financial, payroll, and sales data.

B. How data and information sharing support the Business Plan

No understanding of how data and information sharing support the Kitty Hawk Aeronautics Business Plan exists at this time.

C. Data and information-sharing strategies and diagrams for each Line of Business

Currently, each Line of Business unit is responsible for managing their own operational data.

D. What types of data in the enterprise require extra protection?

There is no current data sensitivity guideline or policy defining what types of data require extra protection and what security mechanisms need to be in place at each sensitivity level.

E. The lifecycle for data and information that is key to the success of the enterprise

There is no current lifecycle for data and information for Kitty Hawk Aeronautics.

Overall Conclusion

Not much is known from an enterprise perspective by Kitty Hawk Aeronautics about the current state of their data. They have no linkage to their Business Plan, no data or information sharing strategies in place beyond each LOB, and no defined policies for how to manage sensitive data or how to address data lifecycle management.

Knowledge Management Plan - TO-BE (FUTURE) Situation

The following knowledge management plan attempts to provide an overview of the desired state for knowledge management within Kitty Hawk Aeronautics. Specifically, it will outline a vision statement, detail how information sharing is linked to its Business Plan, and provide guidelines on data sensitivity and data lifecycle mgmt.

A. The desired approach to managing data, information, and knowledge across the enterprise.

The future vision is to establish the following:

1. A Knowledge Warehouse that is run by the KHA Office of the CIO -  Based on an architecture that the KHA EA team will design with participation by line of business managers and other key stakeholders. Access to the KHA Knowledge Warehouse will be through the EA Repository.  Implementation of the KHA Knowledge Warehouse will be accomplished in conjunction with the implementation of an Enterprise Service Bus to enable and enhance the sharing of information and data within and between all KHA lines of business.

2. An Enterprise Wide Cost Accounting System – This will be to replace each LOB’s current finance, payroll, and ledger accounting systems that make it difficult to track and control costs for the enterprise.

3. Integration of Financial Information and Sales & Warehouse Data – An access controlled datamart will be created that will integrate financial, sales, and warehouse data. It will be used to automatically deliver daily reports to senior management on the current sales & cost status of Kitty Hawk Aeronautics.

From a planning perspective the achievement of the above objectives will require that the following tasks be completed:

1. Identify all operational databases currently used to support each LOB.

2. Complete an Activity-Data Entity matrix analysis to determine if any redundancies or gaps exist.

3. For redundant operational databases determine proper transition strategy (e.g. which operational database should be used?)

4. For non-existent operational databases determine the appropriate building/acquisition strategy

5. Conduct an acquisition task to identify, rank, and purchase a COTS based Enterprise cost accounting software package for implementation across Kitty Hawk.

6. Define target structures of KH Knowledge Warehouse and KH Financial/Sales & Warehouse Datamart

7. Define ETL processes used to populate the Knowledge Warehouse and Data Mart with operational data. Define their ETL frequency (daily, weekly, monthly).

Please refer to the Strategic Initiative Medium Level View for goals and initiatives that have been identified within the Kitty Hawk Strategic Plan.

B. How data and information sharing will support the Business Plan?

We will accomplish support of the Kitty Hawk Aeronautics Business Plan by making all enterprise information available within the Kitty Hawk Data Warehouse necessary to meet the following data/information categories:

1. Financial Results – To provide management with timely financial information which will enable them to make decisions that will support solid financial growth.

2. Internal Business Information - To provide management with the facts and data they require to manage the business at peak performance to enable increasing market share and competitiveness.

3. Customer Satisfaction – To provide information to management that will enable us to achieve high customer satisfaction by understanding what the customer wants and delivering it flawlessly.

4. Learning Information - To provide information which will enable us to continually improve the way we design, build, and support our products.

Please refer to the Strategic Initiative Detailed View for specific outcomes that have been identified within the Kitty Hawk Business Plan.

C. What Data and information-sharing strategies and diagrams for each Line of Business will be used?

The following data context diagram (below) showing how current and future operational databases, knowledge warehouse, and an Enterprise Service Bus (ESB) can be used for sharing, publishing data, information between operational databases and knowledge warehouse.

Overall Description

All operational databases displayed above are used to support the day to day operations for each LOB. On a predetermined schedule (daily, weekly, monthly), relevant data from each operational LOB DB shall be extracted, transformed and loaded within the KH Data Warehouse using the Enterprise Service Bus to drive automation of this ETL process. Access to the KH Data Warehouse and KH Financial-Sales-Warehouse Datamart will be through the EA repository using a standard web browser. Daily reports from the KH Financial-Sales-Warehouse Datamart will be delivered to senior mgmt.

   Link to the high-level entity-relationship graphical view of the Kitty Hawk Data Warehouse

   Link to the data dictionary view of the Kitty Hawk Data Warehouse

Other Considerations

1. Access to the KH Data Warehouse shall be provided to all KH employees as determined by their security clearance.

2. Certain data (e.g. top secret) will not be inserted within the KH DataWarehouse.

D. What types of data in the enterprise require extra protection?

Data shall be evaluated to determine its sensitivity level based upon the following attributes:

1. Confidentiality – What is the consequence of an unauthorized or accidental release of data?

2. Availability – How long is the unavailability of the data acceptable to the enterprise?

3. Integrity – How important is it to ensure that the data is accurate, complete, and that an audit trail of changes is maintained?

Once the sensitivity level for the data has been determined the following table of recommended safeguards shall be used to select and determine the appropriate level of security that will need to be applied to safeguard the data.

Table 1 - Data Sensitivity Table

These guidelines must be reviewed every three years and, if necessary, updated to provide an acceptable level of data sensitivity for the enterprise.

For a more detailed understanding of the Kitty Hawk information security policies please follow the provided link here to the Security Solutions, Detailed View.

E. The lifecycle for data and information that is key to the success of the enterprise

Data shall have its lifecycle classification determined using the following table below. The classification assigned to the data shall be used to determine the lifecycle policy assigned to the data (e.g. how long it needs to be maintained).

Table 2 – Data Lifecycle Table