BS EN 9721:2021:2022 Edition
$215.11
Aerospace series. General recommendation for the BIT Architecture in an integrated system
Published By | Publication Date | Number of Pages |
BSI | 2022 | 94 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
9 | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions |
15 | 3.2 Abbreviations |
17 | 4 BITxe “BIT” stakeholders 4.1 BITxe “BIT” specifier 4.2 BITxe “BIT” designer/developer 4.3 Operational user 4.4 Maintenance engineer |
18 | 4.5 System technical manager 4.6 Expert 4.7 Field data engineer 5 System constraints 5.1 System design |
19 | 5.2 BITxe “BIT” interface functionxe “function” 5.2.1 The alarmxe “alarm” functionxe “function” |
20 | 5.2.2 The diagnosticxe “diagnostic” functionxe “function” 5.2.3 Built-in reconfiguration 5.2.4 The maintenancexe “maintenance” functionxe “function” 5.2.5 The data recording for post analysis functionxe “function” |
21 | 5.3 System technical states 5.4 Functional modes of a systemxe “system” 5.5 System configurationxe “configuration” 5.5.1 Operational configurationxe “configuration” of a systemxe “system” |
22 | 5.5.2 Technical configurationxe “configuration” 5.5.3 BITxe “BIT” parameterisation |
23 | 6 BITxe “BIT” types and metrics 6.1 Generalxe “BIT” 6.2 The various types of BITxe “BIT” 6.2.1 Power-up BITxe “BIT” or Power-on BIT (PBITxe “PBIT”) |
24 | 6.2.2 Initiated BITxe “BIT” (IBIT) or Demanded BIT (DBIT) 6.2.3 Continuous BITxe “BIT” (CBIT) 6.2.4 External BITxe “BIT” (EBIT) 6.2.5 Maintenance BITxe “BIT” (MBIT) |
25 | 6.2.6 Summary of characteristics of the various types of BITxe “BIT” 6.3 The metrics 6.3.1 Role of the mathematical definitions of the metrics |
26 | 6.3.2 Detection rate 6.3.2.1 General 6.3.2.2 Failure detectionxe “detection” capability (FDCxe “FDC”) 6.3.2.3 Failure detectionxe “detection” probability (FDPxe “FDP”) |
27 | 6.3.2.4 Comment |
28 | 6.3.3 Isolation rate 6.3.3.1 Diagnostic and isolationxe “isolation” |
29 | 6.3.3.2 Failure isolationxe “isolation” probability (FIPxe “FIP”) |
30 | 6.3.3.3 Failure resolution probability (FRPxe “FRP”) 6.3.3.4 When is it more relevant to use the FIPxe “FIP” or FRPxe “FRP”? |
31 | 6.3.4 Unreliabilisation rate caused by the BITxe “BIT” 6.3.5 False alarmxe “alarm” rates, false correct operation rates 6.3.5.1 General |
32 | 6.3.5.2 Sensitivity and Specificity |
33 | 6.3.5.3 Diagnostic value |
34 | 6.3.5.4 Calculating the false alarmxe “false alarm” rate |
36 | 7 Use of BITxe “BIT” 7.1 During development 7.2 During production |
38 | 7.3 During service 7.3.1 In operational modexe “mode” 7.3.2 In maintenancexe “maintenance” modexe “mode” 7.4 During validation during repair 8 Architecture of the BITxe “BIT” 8.1 The generic functions of the BITxe “BIT” 8.1.1 Generalxe “function” |
40 | 8.1.2 BITxe “BIT” Detection functionxe “function” 8.1.2.1 General 8.1.2.2 Test 8.1.2.3 Confirmation (optional) 8.1.3 BITxe “BIT” Supervisor functionxe “function” 8.1.3.1 Generalxe “diagnostic” |
41 | 8.1.3.2 Operational diagnosticxe “diagnostic” 8.1.3.3 Context recording (optional): 8.1.3.4 System date (optional): 8.1.3.5 Maintenance diagnosticxe “diagnostic” (optional) |
42 | 8.1.3.6 Data recording (optional) 8.1.3.7 Interface 8.1.3.8 Control of the BITxe “BIT” triggered (optional) |
43 | 8.1.3.9 Inhibition (optional) 8.1.3.10 BITxe “BIT” parameterisation (optional) 8.2 The various architectures of the BITxe “BIT” functionxe “function” 8.2.1 General |
44 | 8.2.2 Distributed BITxe “BIT” Architecture 8.2.3 Centralised BITxe “BIT” Architecture |
45 | 8.2.4 Choice of BITxe “BIT” architecture |
46 | 8.3 Exchanged data typology |
47 | 8.4 Specification process 8.4.1 System design arbitrations: Essential objective and effort |
49 | 8.4.2 The BITxe “BIT” specification process 8.4.2.1 General 8.4.2.2 For the BITxe “BIT” architecture 8.4.2.3 For the tests |
50 | 8.5 Generic modelling and configurationxe “configuration” language 8.5.1 Introduction |
52 | 8.5.2 General information 8.5.2.1 Introduction 8.5.2.2 BITxe “BIT” modelxe “model” applications 8.5.2.3 Utilities |
53 | 8.5.2.4 Constraints 8.5.3 Description of the language tables 8.5.3.1 Generalxe “failure” 8.5.3.2 Table of services in failurexe “failure” |
54 | 8.5.3.3 Table of Cut sets |
55 | 8.5.3.4 Table of Signatures |
57 | 8.5.3.5 Table of Cut sets/Signatures |
58 | 8.5.3.6 Table of Direct dependencies: |
59 | 8.5.3.7 Table of Degradation levels 8.5.4 Functional language 8.5.4.1 The operators 8.5.4.2 Words dedicated to the language 8.5.5 Model instantiation process |
60 | 8.6 Development process and validation/verification of a BITxe “BIT” systemxe “system” 9 Prognosis 9.1 Aim of the prognosis |
61 | 9.2 Organisation of the prognosis 9.3 Data from BITxe “BIT” for use by the Prognosis 10 Conclusions |
63 | Annex A (informative)Examples A.1 Operational efficiency and performancexe “performance” A.1.1 General A.1.2 Example 1: How do you cut down a tree rapidly? A.1.3 Example 2: How do you cut a slab of butter cleanly? |
64 | A.2 Example of calculations for some metrics A.2.1 General |
68 | A.2.2 Calculating detectionxe “detection” rates A.2.2.1 Calculating the FDCxe “FDC” (Failure Detection Capability) |
69 | A.2.2.2 Calculating the FDPxe “FDP” (Failure detectionxe “detection” probability) |
70 | A.2.3 Calculating isolationxe “isolation” rates |
71 | A.2.3.1 Calculating the FIPxe “FIP”n (Failure isolationxe “isolation” probability) |
72 | A.2.3.2 Calculating the FRPxe “FRP”n (Failure resolution probability) |
76 | A.3 Correct operation diagnosticxe “diagnostic” vs failurexe “failure” diagnostic |
77 | A.4 Example of propagation of the diagnosticxe “diagnostic” values on a simple architecture case |
84 | A.5 Ergodicity hypothesis A.6 Example of calculation for assessing the NFFxe “NFF” — No faultxe “fault” found rate |
86 | A.7 Timing chart of events |
88 | Annex B (informative)List of recommendations |