Downloaded from https://www.everyspec.com ADS-79D-HDBK b. Ordering parts, based on exceeded CI/HI thresholds that indicate the presence of a fault, requires an interface of the data from the ground based equipment through STandard Army Management Information System (STAMIS), Standard Army Retail Supply System (SARSS), and Unit Level Logistics System-Aviation (ULLS-A). This interface should be accomplished to eliminate the need for duplicative data entry.
The ground based equipment should enable monitoring of CI/HIs and use the predetermined ―thresholds‖ or CI/HI values to allow for anticipatory supply actions, optimized maintenance planning, and enhanced safety by avoiding a precautionary landing/recovery/launch. c. Extending/overflying the CRT based on individual component fatigue damage assessment for a specific serialized component will require automated changes to be recorded in STAMIS record system. d. Configuration Management of the Monitoring System should enable the following items to be displayed on any data output: i. The date, drawing number revision, and software version of the monitoring hardware/software. ii.
Any controlled changes to hardware/software configuration items of the monitoring system. iii. Compliance with any applicable safety of flight messages and aviation safety action messages. iv. A list of software versions, part numbers, and respective serial numbers being monitored. For Army aircraft systems, tracking of individual serialized items begins at the time of manufacture through its life cycle and is accomplished by manual records and an electronic log book, or either manual records or electronic log book which is an integral part of the STAMIS architecture.
CBM credits extending/overflying a fatigue-related retirement or inspection interval can be given to groups of aircraft or parts, as long as they can be tracked. CBM credits extending/overflying a fatigue-related retirement or inspection interval cannot be applied to individual items based on individual component fatigue damage assessment estimates without accurate tracking of an individual part‘s installation and maintenance history as reflected in the electronic log book and other records.
While one of the objectives of CBM is to provide complete visibility of the operational history of a serialized component, the Army‘s current maintenance information systems do not have the capability to meet this objective. Shortfalls include: a. Lack of quality control tools in the current system allow for duplicate entries, typographical errors, and erroneous entries. b. Data requirements (scope, data size, and analysis requirements) for this effort have yet to be defined, which creates uncertainty and risk in defining the Data Storage, Analysis, and Transmission capabilities required. c.
Software inoperability to calculate and manage varying usage rates (flight hours) based on operational history. d. Lack of complete serialization of monitored components 19