Knowledge Warehouse

As-Is Situation

Each of the Lines of Business (LoBs) have their own databases, essentially a “stovepipe”.
The LoBs
- Commercial Aviation Systems
- Defense Systems
- Space Systems
- Research and Development
- Shipping and Receiving
- Finance and Administration
- Technology Support
- Contracts and Legal
Each LOB, even though a stovepipe, needs data from other areas, such as Finance to perform reporting and analysis. Access to this data is via file sharing, dataloads, FTP, etc.
Each manufacturing LOB keeps their own resource planning data.
Each Manufacturing LOB maintains supplier data and that some suppliers support multiple LOBs.
Each Manufacturing LOB maintains quality data.

To Be

The system which need their data to be integrated with Knowledge Warehouse are identified below:

Commercial Aviation Systems Division:
- CAD/CADCAM v7.1
- Production Plant Monitoring System v4.2
Defense Systems Division:
- USN F-18C UHF/VHF EMI-EMC Test System
Space Systems Division:
- NASA Standards & Design System II
- USAF GeoTalk System
- NASA Mars Lander Communications System (Node to JPL and Houston Center)
Research and Development Division:
- KHA Avionics Design & Testing System
- NASA Next-Generation Space Shuttle Avionics Program
Finance and Administration Division:
- PRISM Accounts Receivable/Payable, SAP General Ledger, SAP HR Module
Technology Support Division:
- Linux Print and File Servers (dual clustered/mirrored units are at all operating sites)
- Standard Desktop Image: XP, Office 2007, Exchange 2007, Adobe Acrobat
- Collaboration: SharePoint 2007; NetMeeting, GoToMeeting
Contracts and Legal Division:
- LEXUS/NEXUS Law Reference v4.8
- PRISM (Computer Associates) Contracting System v6.1
Shipping and Receiving Division:
- Pitney Bowes Shipping Center v3.5 (Node)
- FEDEX Tracking System (Node)
- KHA Warehouse Inventory System
- Intermec Bar Code Readers/Database v2.42

Benefits of Knowledge Warehouse:

Since data is often shared, across Lines of Business, having a single, integrated set of databases allows for easier access to that data in the form of database views, or by setting up DataMarts accessing the Knowledge Warehouse.
Knowledge Warehouse eliminates interfaces between systems which can become points of failure. Eliminating system interfaces improve synchronization of data and eliminates redundant dataloads.
Knowledge Warehouse eliminates redundant table structures.
Knowledge Warehouse supports the use of common systems such as an enterprise resource planning system, finance system, accounting system, etc.

	As-Is	To-Be
Approach to managing information across the enterprise	The current approach is that each LOB is having isolated systems maintaining their own databases.	- Knowledge Warehouse (KWH) to be run by CIO Office - KWH would contain all data across the enterprise - Access to KWH would be through an Enterprise Repository
Support of Business Plan	In the present model, there is no understanding of how the information sharing supports the business plan.	Sharing of information through KWH would support following strategic initiatives in business plan: - Commercial Aviation Systems : Roll out of new plant, expand product line and cost control - Defense Systems: Delivery of products - R&D: KWH provides baseline data for R&D Finance and Administration: - Establish an enterprise-wide cost accounting system and migrate from separate legacy finance, payroll, and general ledger accounting systems. - Integrate financial information with sales and warehouse data, and establish access controlled data marts that push pre-formatted reports daily. Contacts and Legal: - Implement a performance-based contracting approach that uses standard on-line templates and a document tracking/correspondence control system - Integrate contracting information with finance and accounting information. - Upgrade legacy Lexus/Nexus on-line legal library system, make available in San Diego. Technology Support: - Establish and maintain an enterprise architecture program and on-line repository of actionable EA information. - Establish an IT capital planning program to improve the value of investments in IT. - Develop and implement a follow-on IT Security solution for the IT-COE. - Establish a Knowledge Warehouse for the KHA enterprise. Shipping and Receiving: - Expand the Warehouse and Shipping Department at the San Diego facility. - Reduce average warehouse handling time by 10% per year for 2008-2010.
Information Sharing Strategies for LoBs	There is no information sharing strategy. The information sharing is ad-hoc and happens through file-sharing, ftp, or manually, and creates redundant information.	- KWH implementation would be realized through Enterprise Service Bus to enhance information sharing across LoBs. - Data would be captured at one place and shared across multiple LoBs as Information - The specific LoBs and organizational entities would be given ownership and control of specific parts of KWH to ensure consistency, integrity and quality of data.
Information Security and Protection	There are no information security or protection guidelines or policies ate present.	Information security and protection would be achieved through policies, their implementation and monitoring
Information Lifecycle	There is no information or data lifecycle process, guidelines or mechanism in place.	- Different types of data would have different lifespan, the three lifespans would be recommended: - Upto 5 Years, Upto 20 Years, Permanent - The data would be archived after its lifespan is over and moved out of KWH into archive Warehouse. - The archived data would not be deleted. However, this policy would be reviewed every 3 years.