Answers are grounded in this paper and cite their sources.
SUMMARY & CONCLUSIONSPrognostics and health management (PHM) gathers and processes health data for a system to determine whether it will continue to meet service requirements. Typically, PHM depends on an end-to-end architecture that describes and defines the enterprise's maintenance process to achieve the operational readiness of complex systems. PHM processes should be organized to provide high-quality, actionable data for fleet insights. Such PHM systems include many health and usage maintenance (HUMS) systems, communication systems, and enterprise data analysis centers.Standards are needed to guide and facilitate technology insertion and define the interactions between PHM systems. Because a PHM architecture spans domains, many components gather, process, and transform data. The PHM data pipeline connecting these components becomes more challenging to integrate without data standards. A critical gap in realizing PHM is an overall strategic approach for selecting standards. Modular Open Systems Architectures (MOSA) depend on standards to define technologies and apply standards across component interfaces. Standards must be tied to an organization's capabilities, strategic priorities, fleet, maintenance technologies, and mission sets.This paper provides a standards development and selection methodology to determine prognostics and predictive maintenance data standards for an enterprise and its fleet and document the standards in enterprise architecture. The latest Condition-Based Maintenance concept is examined to associate standards to each activity. This analysis will result in a common model for the processing and exchange of health data across the maintenance infrastructure.
No takes yet. Share an insight, caveat, or question.
Joseph Kroculick (2023) studied this question.
Synapse has enriched 3 closely related papers on similar clinical questions. Consider them for comparative context: