U.S. Army ADS-79D-HDBK — ADS-79D-HDBK.pdf

Downloaded from https://www.everyspec.com ADS-79D-HDBK 5. DETAILED GUIDANCE Detail guidance for the CBM system is grouped by the functionality shown in Figure 1to link the guidance to the overarching International Standards Organization (ISO) and Data Acquisition (DA) architecture for CBM. Sections below briefly describe the elements of the CBM system architecture and link those elements to specific technical considerations for Army Aviation. To enable these technical considerations to be easily refined as CBM implementation matures, the technical considerations are grouped into twelve separate Appendices.

These appendices set forth acceptable means, but not the only means, of compliance with CBM detailed technical elements. They are offered in the concept of a Federal Aviation Administration (FAA) Advisory Circular. They include: a. Appendix A: Fatigue Life Management b. Appendix B: Regime Recognition/Flight State Classification with Validation of Regime Recognition Algorithms c. Appendix C: Structural Health and Loads Monitoring d. Appendix D: Minimum Guidance for Determining CIs/His e. Appendix E: Vibration Based Diagnostics f. Appendix F: Rotor Track and Balance g. Appendix G: Turboshaft Engine and Auxiliary Power Unit Condition Based Maintenance (CBM) h. Appendix H:

Embedded Diagnostics/Prognostics and Health Management of Electronic Components i. Appendix I: Sample Sizes for Maintenance Credits Using Vibratory CBM on Propulsion Systems j. Appendix J: Seeded Fault Testing k. Appendix K: Verification and Validation of CBM Processes l. Appendix L: Data Integrity m. Appendix M: Oil Condition and Debris Monitoring 5.1 External systems. External system data guidance is defined by various Standard Army Management Information Systems (STAMIS). Any system designed to enable CBM on an Army platform should follow the guidance set for these systems. 5.2 Technical displays and technical information presentation.

Technical displays and information presentation to support CBM should be developed for compatibility with software operating systems and DoD style guides. These operating systems are identified by the Logistics Information 20