Guidelines for the Development of Architectures for Integrated Vehicle Health Management Systems
This SAE Aerospace Recommended Practice (ARP) provides best practices and guidance for creating an architecture for integrated vehicle health management systems. Where possible, this document will also provide references to tools to conduct architectural trades. Finally, this document will provide use cases to expose considerations and stakeholders to be included in these trades and utilization of an IVHM system (which may lead to new functional or non-functional requirements).
Rationale: This ARP provides guidelines for development of the architecture for the design of an integrated vehicle health management system. The purpose of this document is to insure that the architecture design covers the utilization of information disseminated by each function contained in the design requirements and to define and document an optimum architecture for an IVHM solution that is in line with the organization’s business goals and objectives.
Architecture is “the structure of components, their relationships, and the principles and guidelines governing their design and evolution over time.” (IEEE STD 610.12 as stated in the DoD Architecture Framework (DoDAF)). It is useful for designing unprecedented, complex systems. In general a system architectural design needs to consider physical components, functions, performance, technologies, cost, risk, constraints, boundaries, and internal and external interfaces.
Some efforts have tried to standardize the process of architecture development. ISO 13374 “Condition monitoring and diagnostics of machines - Data processing, communication and presentation” defined functional layers in building a CBM system. In addition, frameworks like DoDAF outline an architecture development process. This document will incorporate these suggested standard practices into specific guidelines for IVHM architecture development.
For the purposes of clarity and in keeping with the needs of the IVHM architecture, the guidelines will be divided into sections that address each possible tier of the end to end architecture.
This architecture may include:
• The On-Vehicle Tier: which addresses the capture, processing and packaging of on-board data
• The Data Transfer Tier: which provides guidelines in the movement of data
• The At-Vehicle Tier: which includes maintenance support through data analysis and presentation equipment (such as a ground station or portable maintenance aid)
• The Fleet Data Services and Application Tier - Which includes a central, ground-based Data Center and provides guidelines on the transformation, analysis and exchange of that data to the user community. Since each application of this tier is specific to a particular organization’s needs, the various uses of the data by the user community will not be addressed in this document.