1.0 Background

In our budget-constrained operation environment, in is imperative that we operate as efficiently as possible. In the aircraft sustainment community, we it is frequently encounter sub-systems that fail more often that expected resulting in high demands on limited supply assets. Develop interfaces with existing Reduction of Total Ownership Cost (R-TOC) and other required maintenance data systems. This process should be fully automated so that minimal operator control is needed.

2.0 Problem Statement

This project is to research and seek an automated process that will mine existing weapon system maintenance, supply and sustainment data systems, and then analyze that data to determine which sub-system should have the highest priority for limited R&M dollars. The engine community may be a good candidate for the initial effort as there are multiple blocks of engines and is a system that would prove beneficial and would most likely benefit most other weapon systems. This process should be automated to optimize the data collection process.

3.0 Anticipated Methodology/Tasks

Task Area 1

Data collection for indentured parts

• Evaluate of Total Ownership Cost program

• Evaluate CEMS interfaces

• Evaluate Shop Floor Portal methodology

• Research methodology for needed data fields

• Develop schema for a relational database table

Task Area 2

Failure capture is the response to the discovery of what actually caused the sub-system to fail.

• Currently no electronic maintenance data is captured or stored on lower level component failure

4.0 Anticipated Schedule

For the 2003 CASI program, the following schedules/periods of performance are allowed (you may wish to include this list and check all of the periods of performance that you would accept, i.e.):

[ ] Execution and Completion of Project between June 1, 2003 and August 31, 2003.

[X ] Execution and Completion of Project between June 1, 2003 and May 31, 2004

[ ] Executed as a single project, or

[ ] Executed in two or more phases with an intermediate set of deliverables and successful completion of the intermediate deliverables required before funding successive phase(s). NOTE: CASI research phases will normally have completion dates that correspond to the academic researcher’s semester schedule, i.e., August 15 or December 31.

[ ] Execution and Completion of Project between August 15, 2003 and May 31, 2004

[ ] Executed as a single project, or

[ ] Execution as the first phase of a multi-year project. NOTE: Due to funding mechanisms, only the effort between June 1, 2003 and May 31, 2004 can be funded by the 2003 CASI program. The project must produce a set of intermediate deliverables at the end of the 2003 funding cycle and funding of successive phases/years is contingent upon funding availability, project priority, and performance.

5.0 Anticipated Deliverables

A final report shall be submitted which includes the results as well as a description of any work associated with the project. A cost benefit analysis is required and a final briefing will be held at the end of the project period. In addition, brief monthly status updates shall be submitted to the project manager for the purpose of project tracking.

6.0 Anticipated Benefits

Cost/Benefit Analysis

• Identify R&D funding needs

• Reduction in Total Cost of Ownership

• Increase Missions Capable Rate

• Increase Mean-Time-Between Failure

Increase Mean-Time-Between Maintenance