Shopping Cart

No products in the cart.

BS EN 9722:2023

$198.66

Aerospace series. Architecture for integrated management of a system’s health condition

Published By Publication Date Number of Pages
BSI 2023 70
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This document is mainly aimed at all the trades which are actively involved in managing the health of a system. Although it relies on examples of aeronautical systems, the expert group considers that this document is applicable for systems from other areas. This document specifies the centralization of the health data for a fleet of systems, such as an aircraft fleet for example, to ensure consistency between stakeholders (operators, repair facilities, designers, etc.) and the management of its health card.

PDF Catalog

PDF Pages PDF Title
2 undefined
8 1 Scope
2 Normative references
3 Terms, definitions and acronyms
3.1 Terms and definitions
9 3.2 Acronyms
11 4 Information on which this document is based
4.1 Overview of maintenance
4.1.1 Content of the health card
12 4.1.2 Health card value chain
4.1.2.1 General
4.1.2.2 The uses of the health card
4.1.2.3 Architecture of the maintenance scheduling value (U2)
4.1.3 Use of the health card
4.1.3.1 General
14 4.1.3.2 Design phase
4.1.3.3 Development/manufacturing phase
4.1.3.4 Integration, Verification, Validation and Qualification phase (IVVQ)
4.1.3.5 Maintenance phase
15 4.1.3.6 Operational phase
16 4.2 Overview of maintenance
4.2.1 General
17 4.2.2 Structuring of maintenance in terms of level of impact
4.2.3 Health card and example of coordination between stakeholders
4.2.4 Health card and predictive maintenance
19 4.3 Overview of services engineering
4.3.1 Link between system engineering and services engineering
4.3.2 Enterprise architecture applied to the support architecture
20 4.3.3 Enterprise architecture modelling
21 4.3.4 Presentation of contact/visibility/control lines
4.3.5 Link between product and services
4.3.5.1 General
4.3.5.2 Service engineering in the design of a service/product
24 4.3.5.3 Management of service engineering risks in the design of a service/product
25 4.3.6 Fundamental constraints and requirements
26 5 Recommendations on architectures (ecosystem and product)
5.1 General
27 5.2 Functional architecture centred on the health card
28 5.3 Example of support organization
5.3.1 General
5.3.2 Stakeholders and roles
5.3.3 Breakdown of support into areas and roles
39 5.4 Evolution of the organic value enhancement architecture
40 6 Using the health card
6.1 OODA Loop applied to the health condition of a system
6.1.1 General
6.1.2 Observe
42 6.1.3 Capitalize
6.1.4 Detect
43 6.1.5 Diagnose
6.1.6 Predict
6.1.7 Decide
44 6.1.8 Act/react
6.1.9 Visualize
45 6.2 Capacity projection/reliability of projections
6.2.1 General
6.2.2 Operational configuration of a system
6.2.3 Framework of design studies for operational applications for predictive maintenance (AOMP)
6.2.3.1 General
6.2.3.2 Characterization and qualification of AOMPs
46 6.2.3.3 The components of an AOMP
6.2.3.4 Reliability of projections
47 7 Recommendations regarding data
7.1 General
7.2 Cybersecurity
7.3 Data centralization and digital continuity
53 7.4 Obligations of manufacturers with regard to data
8 Conclusion/outlook
55 Annex A (informative)Enterprise architecture view of an organization example outside the supply chain
56 Annex B (informative)Added value and responsibilities of support stakeholders
57 Annex C (informative)Illustration of the product and services engineering approach
58 Annex D (normative)Overview of the OODA loop: application to a diagnostic and prognostic system
60 Annex E (informative)Decontextualization: an example of degradation and reliability models
E.1 General
E.2 Fundamental hypotheses
E.3 Framework for a solution to assess the level of degradation and reliability
62 E.4 Decontextualization
63 E.5 The uses of these models
64 E.6 Processes in which these models will be used
E.7 Value enhancement architecture
E.7.1 For lessons learned
E.7.2 For design of the maintenance plans
E.7.3 For design of aircraft
E.7.4 For predictive maintenance
65 Annex F (informative)Use case/operational scenarios based on the phases
F.1 For maintenance, preparation of missions
66 F.2 For the pilot, on a mission
F.3 For the manufacturer, the designers
BS EN 9722:2023
$198.66