| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 4 Purpose 4.1 Bridge alert management \u2013 Implementation 4.2 Structure of document <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 5 Implementing BAM in an equipment standard 5.1 Implementing a concept 5.2 Implementation process Figure 1 \u2013 BAM is a concept applied to equipment rather than a piece of equipment <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 5.3 Subjects for consideration when developing\/modifying an individual equipment standard 5.3.1 General 5.3.2 Description of subjects <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 5.4 Role of a Central Alert Management system (CAM system) <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 6 Alert properties 6.1 Harmonization of alert sound vs legacy alarm sounds 6.1.1 General Figure 2 \u2013 Role of a CAM system in Bridge Alert Management <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 6.1.2 Emergency alarms <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 6.1.3 Sounds in standards where MSC.302(87) does not take precedence 6.2 Priority <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Figure 3 \u2013 Typical decision tree for the classification of alert priority <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 6.3 Category Figure 4 \u2013 Typical decision tree for the classification of alert priority after escalation of a warning <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 6.4 Functional vs technical alerts <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 6.5 Alert management using context information 6.5.1 General 6.5.2 Different operational modes \u2013 Different alert requirements <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6.5.3 Other operational sectors <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 7 Pre-BAM power failures and alarm-outputs 7.1 General 7.2 Pre-BAM alerts 7.2.1 Applying ALR sentences 7.2.2 Pre-BAM alert \u2018alarm condition\u2019 <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7.2.3 Applying dry contacts to inform about abnormal conditions (e.g. system failure) 7.2.4 Pre-BAM alert \u2018power failure\u2019 7.3 Alerting on power problems 7.3.1 General <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.3.2 Description 7.3.3 Discussion <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 7.3.4 Resolution Figure 5 \u2013 EUT scope with one or two power inputs with one or two power sources <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 8 Alert Identifiers 8.1 General <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 8.2 Application Table 1 \u2013 Blocks of alert identifier end numbers in each 10 consecutive alert identifiers above 300 <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 9 Clarification regarding presentation of alerts in the list of active alerts 10 WG16 assistance <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Maritime navigation and radiocommunication equipment and systems. Bridge alert management – Guideline on implementation<\/b><\/p>\n |