DID_OAPM-ILS-009_TSE_Database_BI_Tool_Plan.doc

DATA ITEM DESCRIPTION

3. DESCRIPTION/PURPOSE

3. 1 The TSE Maintenance Database and BI Tool Development Plan describes the organizational structure, and the plans and procedures that will be employed to design, develop, and test a TSE Maintenance Database and BI Tool.

3.2 This Data Item Description (DID) provides the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.

OAPM

7. APPLICATION/INTERRELATIONSHIP

7.1 The TSE Maintenance Database and BI Tool Development Plan is closely related to and is harmonious with the TSE Data Analysis Plan (TDAP).

10. PREPARATION INSTRUCTIONS

10.1 GENERAL. The TSE Maintenance Database and BI Tool Development Plan documents the Contractor's plans for the design, development, and testing of a TSE Maintenance Database IT architecture and Business Intelligence (BI) Tool. It identifies and defines requirements, tasks, and the Contractor's processes used to implement and maintain the TSE Database to facilitate efficient and effective TSE Maintenance Data collection, calculation, audit, and storage on the TSA network.

10.2 CONTENT. The TSE Maintenance Database and BI Tool Development Plan consists of the following sections:

a.

Introduction b.

TSE Maintenance Database Design, Development and Testing c.

Import Historical TSE Maintenance Data

10.2.1 Introduction. This section identifies the requirements as specified in the Performance Work Statement. This section contains the information below:

a. Purpose and Scope.

b. TSE Maintenance Database and BI Tool Development Plan. This paragraph includes a summary of the maintenance database architecture development for collection, calculation, audit, and storage of TSE maintenance data.

c. Schedule Overview. This paragraph provides an overview of how the schedule is maintained and monitored.

d. Plan Update Process.

10.2.2 TSE Maintenance Database Design, Development and Testing. Describes the organizational structure that will be used to implement and execute this requirement.

11. DISTRIBUTION STATEMENT

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

DATA ITEM DESCRIPTION

OAPM-ILS-009

10. PREPARATION INSTRUCTIONS (CONTINUED)

a. Design, develop, and test a TSE Maintenance Database on TSAs network. Describe the Contractor’s approach and methodology in design and developing the database on TSAs network. Create data banks and appropriate scripts to generate all the necessary metrics (e.g. Operational Availability, Mean Down Time, Tech Response Time, Mean Time To Repair, etc.).

b. Develop import functionality to import monthly raw data from MSP/OEMs to analyze/validate MSP performance accurately. Describe the Contractor’s approach and methodology for automating the process to import the data from MSP/OEM to streamline the data processing.

c. BI Development Tool Plan. This section contains a description on how the Contractor accomplishes BI tool development and implementation:

· Development. Describe the Contractor’s approach and methodology for developing a BI tool that will enable the TSA to create monthly/ad hoc reports and charts.

· Implementation. Describe the Contractor’s approach and methodology for implementation of BI tool to automatically generate maintenance data reports and ad hoc reports.

· Operating Procedures and Metrics. Describe the Contractor’s approach and methodology for automation of data import and supporting the tool.

d. Develop Uniform template for MSP/OEMs raw maintenance data delivery. This section contains a description on how the Contractor will develop and generate a uniform template for raw maintenance data delivery:

· Development. Describe the Contractor’s approach and methodology for developing a uniform template that enable the MSP/OEMs to provide the delivery of raw maintenance data in the same format to promote data import automation.

· Implementation. Describe the Contractor’s approach and methodology for implementation of a uniform template to provide the delivery of raw maintenance data in the same format.

e. Develop and implement the capability to allow direct connectivity for MSP information reporting system (i.e. Maximo, Koi, etc.) to automate data importing delivery. This section contains a description on how the Contractor will develop and establish direct connectivity from MSP data reporting system to TSA Maintenance Database:

· Development. Describe the Contractor’s approach and methodology for developing and establishing a direct connectivity from MSP data reporting system to the TSE Maintenance Database.

· Implementation. Describe the Contractor’s approach and methodology for implementation of direct connectivity from MSP data reporting system to the TSE Maintenance Database.

10.2.3 Import historical TSE maintenance data (2008 to present) onto the TSE Maintenance Database. Describe the Contractor’s approach and methodology for importing historical data into the database and successfully calculate metrics and generate both monthly and ad hoc reports with historical data.