{"id":394248,"date":"2024-10-20T04:13:09","date_gmt":"2024-10-20T04:13:09","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-97212021\/"},"modified":"2024-10-26T07:53:01","modified_gmt":"2024-10-26T07:53:01","slug":"bs-en-97212021","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-97212021\/","title":{"rendered":"BS EN 9721:2021"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3.2 Abbreviations <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4 BITxe “BIT” stakeholders 4.1 BITxe “BIT” specifier 4.2 BITxe “BIT” designer\/developer 4.3 Operational user 4.4 Maintenance engineer <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.5 System technical manager 4.6 Expert 4.7 Field data engineer 5 System constraints 5.1 System design <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 5.2 BITxe “BIT” interface functionxe “function” 5.2.1 The alarmxe “alarm” functionxe “function” <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 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” <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 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” <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.5.2 Technical configurationxe “configuration” 5.5.3 BITxe “BIT” parameterisation <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 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”) <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 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) <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 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”) <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 6.3.2.4 Comment <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 6.3.3 Isolation rate 6.3.3.1 Diagnostic and isolationxe “isolation” <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 6.3.3.2 Failure isolationxe “isolation” probability (FIPxe “FIP”) <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 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”? <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 6.3.5.2 Sensitivity and Specificity <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 6.3.5.3 Diagnostic value <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 6.3.5.4 Calculating the false alarmxe “false alarm” rate <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 7 Use of BITxe “BIT” 7.1 During development 7.2 During production <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 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” <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 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” <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 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) <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 8.1.3.6 Data recording (optional) 8.1.3.7 Interface 8.1.3.8 Control of the BITxe “BIT” triggered (optional) <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 8.2.2 Distributed BITxe “BIT” Architecture 8.2.3 Centralised BITxe “BIT” Architecture <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 8.2.4 Choice of BITxe “BIT” architecture <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 8.3 Exchanged data typology <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 8.4 Specification process 8.4.1 System design arbitrations: Essential objective and effort <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 8.5 Generic modelling and configurationxe “configuration” language 8.5.1 Introduction <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 8.5.2 General information 8.5.2.1 Introduction 8.5.2.2 BITxe “BIT” modelxe “model” applications 8.5.2.3 Utilities <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 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” <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 8.5.3.3 Table of Cut sets <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 8.5.3.4 Table of Signatures <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 8.5.3.5 Table of Cut sets\/Signatures <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 8.5.3.6 Table of Direct dependencies: <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 8.6 Development process and validation\/verification of a BITxe “BIT” systemxe “system” 9 Prognosis 9.1 Aim of the prognosis <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 9.2 Organisation of the prognosis 9.3 Data from BITxe “BIT” for use by the Prognosis 10 Conclusions <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 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? <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | A.2 Example of calculations for some metrics A.2.1 General <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | A.2.2 Calculating detectionxe “detection” rates A.2.2.1 Calculating the FDCxe “FDC” (Failure Detection Capability) <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | A.2.2.2 Calculating the FDPxe “FDP” (Failure detectionxe “detection” probability) <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | A.2.3 Calculating isolationxe “isolation” rates <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | A.2.3.1 Calculating the FIPxe “FIP”n (Failure isolationxe “isolation” probability) <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | A.2.3.2 Calculating the FRPxe “FRP”n (Failure resolution probability) <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | A.3 Correct operation diagnosticxe “diagnostic” vs failurexe “failure” diagnostic <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | A.4 Example of propagation of the diagnosticxe “diagnostic” values on a simple architecture case <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | A.5 Ergodicity hypothesis A.6 Example of calculation for assessing the NFFxe “NFF” \u2014 No faultxe “fault” found rate <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | A.7 Timing chart of events <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Annex B (informative)List of recommendations <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Aerospace series. General recommendation for the BIT Architecture in an integrated system<\/b><\/p>\n |