BS EN 62940:2017
$198.66
Maritime navigation and radiocommunication equipment and systems. Integrated communication system (ICS). Operational and performance requirements, methods of testing and required test results
| Published By | Publication Date | Number of Pages |
| BSI | 2017 | 60 |
IEC 62940:2016(E) specifies the minimum operational and performance requirements, technical characteristics and methods of testing, and required test results, for shipborne integrated communication systems (ICS) designed to perform ship external communication and distress and safety communications (GMDSS) and the functions of onboard routeing of this communication. It takes account of IMO Resolution A.694(17) and is associated with IEC 60945. When a requirement in this document is different from IEC 60945, the requirement in this document takes precedence.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 7 | CONTENTS |
| 10 | FOREWORD |
| 12 | INTRODUCTION |
| 13 | 1 Scope 2 Normative references |
| 14 | 3 Terms, definitions and abbreviations 3.1 Terms and definitions 3.2 Abbreviations |
| 15 | 4 General and operational requirements 4.1 General requirements 4.1.1 Requirements |
| 16 | 4.1.2 Methods of testing and required test results 4.2 Test site 4.3 Functional requirements 4.3.1 GMDSS equipment |
| 17 | 4.3.2 Non-GMDSS equipment/function 4.4 Operational requirements of ICS 4.4.1 Requirements 4.4.2 Methods of testing and required test results |
| 18 | 4.5 Operational requirements of the COM-HMI 4.5.1 General |
| 19 | 4.5.2 Interconnection with automatic identification systems (AIS) 4.5.3 GMDSS COM-HMI |
| 21 | Figures Figure 1 – Example of ICS supporting distress communications |
| 22 | 4.5.4 Maritime Safety Information 4.5.5 Remote COM-HMI |
| 23 | Figure 2 – Remote COM-HMI |
| 24 | 4.6 Optional common storage media for electronic printing 4.6.1 Requirements |
| 25 | 4.6.2 Methods of testing and required test results 4.7 Software and firmware maintenance 4.7.1 Requirements 4.7.2 Methods of testing and required test results |
| 26 | 5 Technical requirements 5.1 Network integrating the ICS 5.1.1 Requirements Figure 3 – ICS interfaces |
| 27 | 5.1.2 Methods of testing and required test results 5.2 Malfunctions and restoration 5.2.1 Requirements |
| 28 | 5.2.2 Methods of testing and required test results |
| 29 | 5.3 Accuracy and performance 5.3.1 Requirements 5.3.2 Methods of testing and required test results |
| 30 | 5.4 Integrity monitoring 5.4.1 Requirements 5.4.2 Methods of testing and required test results Tables Table 1 – Minimum integrity/status information to be presented by COM-HMI |
| 31 | 6 ICS alert management 6.1 Classification of alerts 6.1.1 Requirements 6.1.2 Methods of testing and required test results Table 2 – Classification of GMDSS equipment alerts for alert management purposes |
| 32 | 6.2 Alert management 6.2.1 General Figure 4 – Example of alert management in an ICS |
| 33 | 6.2.2 Unacknowledged warnings 6.2.3 Remote acknowledgement and silencing of alerts 7 Interfacing 7.1 IEC 61162 interfaces 7.1.1 Requirements |
| 34 | Figure 5 – Interfaces of an ICS |
| 35 | Table 3 – Mandatory IEC 61162-1 sentences received by the ICS equipment Table 4 – Mandatory IEC 61162-1 sentences transmitted by the ICS equipment Table 5 – IEC 61162-1 sentences received by the ICS equipment from remote COM-HMI and from external devices using MSI |
| 36 | Table 6 – IEC 61162-1 sentences transmitted by ICS equipment to remote COM-HMI and to external devices using MSI Table 7 – IEC 61162-1 sentences received by ICS equipment from an external navigation equipment Table 8 – IEC 61162-1 sentences transmitted by the ICS equipment to an external navigation equipment |
| 37 | 7.1.2 Methods of testing and required test results 7.2 BNWAS interface 7.2.1 Requirements Table 9 – Optional IEC 61162-1 sentences received by the ICS equipment from external equipment Table 10 – Optional IEC 61162-1 sentences transmitted by ICS equipment to external equipment |
| 38 | 7.2.2 Methods of testing and required test results 7.3 INS/EPFS interface 7.3.1 Requirements 7.3.2 Methods of testing and required test results 7.4 Optional communication access interface 7.4.1 Requirements |
| 39 | 7.4.2 Methods of testing and required test results Figure 6 – Role of communication access interface |
| 40 | Annexes Annex A (normative)Distress alerting Figure A.1 – Distress alert procedure |
| 41 | Figure A.2 – Follow up voice procedure |
| 42 | Annex B (informative) Extracts from IMO performance standards for alarms and indications B.1 Alarms B.1.1 VHF radio installations B.1.2 MF/HF radio installations B.1.3 Inmarsat-C ship earth stations B.1.4 Inmarsat ship earth stations B.1.5 NAVTEX |
| 43 | B.1.6 EGC equipment B.1.7 Automatic battery chargers B.2 Indications B.2.1 VHF radio installations B.2.2 MF/HF radio installations B.2.3 NAVTEX |
| 44 | B.2.4 EGC equipment |
| 45 | Annex C (normative) Communication access interface implementation details C.1 HTTP communication |
| 46 | C.2 Paths, directories and URIs Table C.1 – Information elements HTTP communication |
| 47 | C.3 Meta information for the file transport Table C.2 – Communication access interface directories |
| 48 | C.4 Vessel-id and shore entity identifier C.5 Access to files by multiple on-board systems Table C.3 – Information elements file transport |
| 49 | C.6 Authentication and authorization C.7 Implementation examples for data transfer scenarios C.7.1 Ship system sends data to shore-system “TrackingSys” at “Acme” C.7.2 On-shore system “controlpanel-update” at GadgetCorp sends data to ship system “controlpanel” C.7.3 Ship client (ECDIS) requests the latest chart from shore Table C.4 – Communications access interface operations |
| 50 | Figure C.1 – Example of a shore to ship transfer |
| 51 | Annex D (informative) Ship/shore and shore/ship communication implementation in support of e-navigation D.1 General D.2 One alternative for data transfer D.2.1 General Figure D.1 – Example of communication for e-navigation |
| 52 | D.2.2 Vessel to shore data transfer D.2.3 Shore to vessel data transfer Figure D.2 – Shore to vessel data transfer |
| 53 | D.2.4 Vessel to vessel data transfer D.3 Another alternative for data transfer |
| 54 | Annex E (informative) Digital interface sentence to parameter group number equivalence Table E.1 – Digital sentence to PGN equivalence |
| 56 | Bibliography |
