šŸ”„šŸ”„ Donā€™t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

šŸ”
BS EN IEC 63173-1:2021

BS EN IEC 63173-1:2021

$215.11

Maritime navigation and radiocommunication equipment and systems. Data interface – S-421 route plan based on S-100

Published By Publication Date Number of Pages
BSI 2021 254
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

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 part of IEC 63173 specifies an S-100 compliant product specification for route plan intended for exchange of information. It specifies the content, structure, and metadata needed for creating fully S-100 compliant route plan information and its portrayal within an S-100-based application. The IHO manages all numbers for S-100 compliant product specifications and has assigned S-421 for this route plan IEC standard. This document specifies only a data format for the route plan exchange. This document does not specify a data format of vessel monitoring and logging information. This information can be provided by other mechanisms or be specified in other standards. The format of the route plan exchange includes some limited vessel static information. When more static information is required, it can be obtained by other methods such as AIS.

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Annex ZA (normative)Normative references to international publicationswith their corresponding European publications
7 CONTENTS
15 FOREWORD
17 INTRODUCTION
18 1 Scope
2 Normative references
3 Terms and definitions
19 4 Abbreviated terms
20 5 General description
5.1 General data product description
5.2 Data product specification metadata
Tables
Table 1 ā€“ Informal description of the data product
Table 2 ā€“ Data product specification metadata
21 5.3 Product specification maintenance
5.4 Specification scopes
5.5 Dataset identification
6 Data content and structure
6.1 General
Table 3 ā€“ Route plan product specification scope
Table 4 ā€“ Dataset identification
22 6.2 Application schema
23 Figures
Figure 1 ā€“ Route plan application schema
24 6.4 Geometry
6.5 Coordinate reference systems
7 Feature catalogue
7.1 General
Table 5 ā€“ Route plan coordinate reference systems
25 7.2 Feature types
7.2.1 Geographic
7.2.2 Meta
7.2.3 Route
7.2.4 RouteActionPoints
26 7.2.5 RouteActionPoint
27 Table 6 ā€“ Route object attributes
Table 7 ā€“ RouteActionPoints object attributes
28 Table 8 ā€“ RouteActionPoint object attributes
29 Table 9 ā€“ Definition of RouteActionPointRequiredAction
Table 10 ā€“ RouteWaypoints object attributes
30 7.2.6 RouteWaypoints
7.2.7 RouteWaypoint
31 Figure 2 ā€“ RouteWaypointID usage examples: Delete
Figure 3 ā€“ RouteWaypointID usage examples: Insert
32 Table 11 ā€“ RouteWaypoint object attributes
33 7.2.8 RouteWaypointLeg
Figure 4 ā€“ RouteWaypointLegDistance between WP2 and WP3
Figure 5 ā€“ RouteWaypointLeg parameters belonging to WP3
34 Figure 6 ā€“ Under-keel clearance example
35 Figure 7 ā€“ RouteWaypointLeg limits example
36 Table 12 ā€“ RouteWaypointLeg object attributes
38 7.3 Information types
7.3.1 General
7.3.2 RouteSchedules
7.3.3 RouteSchedule
39 Table 13 ā€“ RouteSchedules object attributes
Table 14 ā€“ RouteScheduleManual object attributes
Table 15 ā€“ RouteScheduleCalculated object attributes
Table 16 ā€“ RouteScheduleRecommended object attributes
40 Table 17 ā€“ RouteSchedule object attributes
41 7.3.4 RouteScheduleManual/RouteScheduleCalculated/RouteScheduleRecommended
7.3.5 RouteScheduleElement
7.3.6 RouteInfo
43 Figure 8 ā€“ State diagram for route status from ship perspective
Figure 9 ā€“ State diagram of route status from shore perspective
44 Table 18 ā€“ RouteScheduleElement object attributes
45 Table 19 ā€“ RouteInfo object attributes
47 Table 20 ā€“ Definition of RouteInfoStatus
48 Table 21 ā€“ Type of ship
50 7.4 Association roles of feature catalogue
Table 22 ā€“ Roles of the route plan
51 7.5 Associations of feature catalogue
7.5.1 General
7.5.2 Feature association
7.5.3 Information association
Table 23 ā€“ Feature association for route plan
52 7.6 Attributes
7.6.1 General
7.6.2 Simple attribute types
Table 24 ā€“ Information association for route plan
53 7.6.3 Complex attributes
Table 25 ā€“ Simple attribute types
54 7.6.4 Spatial attribute types
7.7 Binding
7.7.1 General
7.7.2 Feature binding
Table 26 ā€“ RouteExtensions attributes
Table 27 ā€“ Spatial attributes
55 7.7.3 Information binding
Table 28 ā€“ Feature binding for the route plan
56 8 Data type and structure of transmission format
9 Maintenance
9.1 Feature and portrayal catalogue management
9.1.1 Feature catalogue management
9.1.2 Portrayal catalogue management
Table 29 ā€“ Information binding for the route plan
57 9.2 Data source
9.3 Production process
10 Portrayal
10.1 General
10.2 Portrayal catalogue
Table 30 ā€“ Information binding for the route plan portrayal catalogue
58 11 Data product delivery
11.1 General
11.2 Single XML file
59 11.3 Compressed data container
11.4 S-100-compliant exchange set
11.4.1 General
11.4.2 Exchange set
Figure 10 ā€“ S-100 exchange set structure
60 11.4.3 Dataset
11.4.4 Exchange catalogue
11.4.5 Digital signature
11.4.6 Encryption
61 11.4.7 Metadata
Figure 11 ā€“ Realization of the exchange set classes
62 Figure 12 ā€“ Route exchange set catalogue
Figure 13 ā€“ Route exchange set
63 Figure 14 ā€“ Route exchange set ā€“ Example of class details
64 12 Test methods and expected results
12.1 General
Table 31 ā€“ Dataset metadata
65 12.2 Test data
12.2.1 Test material
12.2.2 Minimum generic test data
66 12.2.3 Basic generic test data
67 12.2.4 Full generic test data
68 12.3 Route plan test
12.3.1 General
12.3.2 Minimum generic route plan test
69 12.3.3 Basic generic route plan test
73 12.3.4 Full generic route plan test
80 Annex A (normative)Examples of use cases for route
A.1 General
A.2 Route cross check
A.2.1 Description
81 A.2.2 Information exchange diagram
Figure A.1 ā€“ Route cross check example
82 A.2.3 State transition diagram
Figure A.2 ā€“ Interaction diagram
83 A.2.4 Required objects and attributes and their usage
Figure A.3 ā€“ State transition diagram for the route plan onboard
Figure A.4 ā€“ State transition diagram for the route plan onshore
84 Table A.1 ā€“ Objects and attributes used by route cross check
89 A.2.5 Test methods and expected results
Table A.2 ā€“ Test procedures for route cross check
91 A.3 Flow management
A.3.1 Description
92 A.3.2 Information exchange diagram
Figure A.5 ā€“ Flow management example
93 A.3.3 State transition diagram
Figure A.6 ā€“ Data interaction diagram
94 Figure A.7 ā€“ State transition diagram for the route plan onboard
Figure A.8 ā€“ State transition diagram for the route plan onshore
95 A.3.4 Required objects and attributes and their usage
96 Table A.3 ā€“ Objects and attributes used by flow management
99 A.3.5 Test methods and expected results
Table A.4 ā€“ Test procedures for flow management
100 A.4 Enhanced monitoring
A.4.1 Description
101 A.4.2 Information exchange diagram
Figure A.9 ā€“ Enhanced monitoring example
102 A.4.3 State transition diagram
Figure A.10 ā€“ Information exchange diagram
Figure A.11 ā€“ State transition diagram for the route plan onboard
103 A.4.4 Required objects and attributes and their usage
Figure A.12 ā€“ State transition diagram for the route plan onshore
104 Table A.5 ā€“ Objects and attributes used by enhanced monitoring
107 A.4.5 Test methods and expected results
Table A.6 ā€“ Test procedures for enhanced monitoring
108 A.5 Ice navigation
A.5.1 Description
109 A.5.2 Information exchange diagram
Figure A.13 ā€“ Ice navigation example
110 A.5.3 State transition diagram ship side
Figure A.14 ā€“ Interaction diagram on request
Figure A.15 ā€“ State transition diagram for a ship
111 A.5.4 Shore side
A.5.5 Required objects and attributes and their usage
Figure A.16 ā€“ State transition diagram for a shore
112 Table A.7 ā€“ Objects and attributes used by ice navigation
114 A.5.6 Test methods and expected results
Table A.8 ā€“ Test procedures for ice navigation
115 A.6 Under keel clearance management
A.6.1 Description
116 Figure A.17 ā€“ Example of UKCM area
Figure A.18 ā€“ Example of portrayal of S-421 part of UKCM
117 A.6.2 Information exchange diagram
Figure A.19 ā€“ Example of portrayal of S-129 overlay part of UKCM
118 A.6.3 State transition diagram
Figure A.20 ā€“ Information exchange diagram
119 Figure A.21 ā€“ State transition diagram of UKCM for a ship
120 Figure A.22 ā€“ State transition diagram of UKCM for a shore
121 A.6.4 Required objects and attributes and their usage
122 Table A.9 ā€“ Objects and attributes used by UKCM
125 A.6.5 Test methods and expected results
Table A.10 ā€“ Test procedures for UKCM
128 A.7 Fleet route planning
A.7.1 Description
A.7.2 Information exchange diagram
129 A.7.3 State transition diagram
Figure A.23 ā€“ Information sequence diagram
130 Figure A.24 ā€“ State transition diagram for a ship
Figure A.25 ā€“ State transition diagram for a shore
131 A.7.4 Required objects and attributes and their usage
132 Table A.11 ā€“ Objects and attributes used by fleet route planning
135 A.7.5 Test methods and expected results
Table A.12 ā€“ Test procedures for fleet route planning
136 A.8 Chart management
A.8.1 Description
137 A.8.2 Information exchange diagram
A.8.3 State transition diagram
Figure A.26 ā€“ Interaction diagram
138 A.8.4 Functional requirement
A.8.5 Required objects and attributes and their usage
139 Table A.13 ā€“ Objects and attributes used by chart management
140 A.8.6 Test methods and expected results
Table A.14 ā€“ Test procedures for chart management
141 A.9 Route optimization
A.9.1 Description
Figure A.27 ā€“ Route optimization example
142 A.9.2 Information exchange diagram
Figure A.28 ā€“ Interaction diagram on request
143 A.9.3 State transition diagram
Figure A.29 ā€“ State transition diagram for a ship
144 A.9.4 Required objects and attributes and their usage
Figure A.30 ā€“ State transition diagram for a shore
145 Table A.15 ā€“ Objects and attributes used by route optimization
149 A.9.5 Test methods and expected results
Table A.16 ā€“ Test procedures for route optimization
150 A.10 Port call synchronization
A.10.1 Description
151 A.10.2 Information exchange diagram
152 Figure A.31 ā€“ Interaction diagram
153 A.10.3 State transition diagram
154 Figure A.32 ā€“ State transition diagram for a ship
155 A.10.4 Required objects and attributes and their usage
Figure A.33 ā€“ State transition diagram for shore
156 Table A.17 ā€“ Objects and attributes used by port call synchronization
158 A.10.5 Test methods and expected results
Table A.18 ā€“ Test procedures for port call synchronization
159 A.11 Reference route
A.11.1 Description
160 A.11.2 Information exchange diagram
Figure A.34 ā€“ Example of reference routes
161 A.11.3 State transition diagram
Figure A.35 ā€“ Data interaction diagram
162 Figure A.36 ā€“ State transition diagram for a ship requesting a reference route
163 A.11.4 Required objects and attributes and their usage
Figure A.37 ā€“ State transition diagram for a shore center providing a reference route
164 Table A.19 ā€“ Objects and attributes used by reference route
168 A.11.5 Test methods and expected results
Table A.20 ā€“ Test procedures for reference route
169 A.12 Search and rescue
A.12.1 Description
170 A.12.2 Information exchange diagram
Figure A.38 ā€“ A search and rescue example
Figure A.39 ā€“ Interaction diagram
171 A.12.3 State transition diagram
Figure A.40 ā€“ State transition diagram for a ship
172 A.12.4 Required objects and attributes and their usage
Figure A.41 ā€“ State transition diagram for shore
173 Table A.21 ā€“ Objects and attributes used by Search and Rescue
174 A.12.5 Test methods and expected results
Table A.22 ā€“ Test procedures for Search and Rescue
175 A.13 Summary of objects and attributes used by service scenarios
Table A.23 ā€“ Objects and attributes used by service scenarios as seen from the ship
183 Annex B (normative)Data classification and encoding guide
B.1 General
B.1.1 Overview
B.1.2 Descriptive characteristics
184 B.1.3 Spatial characteristics
B.2 Attributes
B.2.1 General
Table B.1 ā€“ Feature types
185 B.2.2 Simple attribute types with acronym
Table B.2 ā€“ Simple attribute types
186 B.2.3 Mandatory attributes by schema
187 B.2.4 Missing attribute values
Table B.3 ā€“ Mandatory attribute types
188 B.2.5 Multiplicity
B.2.6 Spatial attribute types
B.2.7 Textual information
B.2.8 Attributes referencing external files
Table B.4 ā€“ Multiplicity
189 B.2.9 Dates
Table B.5 ā€“ Predefined derived types
Table B.6 ā€“ File format
190 B.3 Associations
B.3.1 General
Figure B.1 ā€“ Association routeInfoComposition
Table B.7 ā€“ Truncated dates
191 B.3.2 Association names
B.3.3 Association roles
B.3.4 Use of various associations
B.4 Datasets
B.5 Metadata
B.5.1 General
Table B.8 ā€“ Dataset types
192 B.5.2 Dataset metadata
Figure B.2 ā€“ Metadata packages
193 Table B.9 ā€“ Metadata for route plan
194 B.5.3 Support file metadata
195 B.5.4 Exchange set metadata
B.5.5 Catalogue file metadata
Table B.10 ā€“ Support files for route plan
196 B.6 Description of table format for feature and information formats
Table B.11 ā€“ File metadata for route plan
197 Table B.12 ā€“ Example of table format for feature
198 B.7 Feature types
B.7.1 Feature type in general
B.7.2 Route
Table B.13 ā€“ General feature types
199 Table B.14 ā€“ Table format for Route
200 B.7.3 RouteActionPoints
B.7.4 RouteActionPoint
Table B.15 ā€“ Table format for RouteActionPoints
201 Table B.16 ā€“ Table format for RouteActionPoint
202 B.7.5 RouteWaypoints
Table B.17 ā€“ Table format for RouteWayPoints
203 B.7.6 RouteWaypoint
B.7.7 RouteWaypointLeg
Table B.18 ā€“ Table format for RouteWaypoint
204 Table B.19 ā€“ Table format for RouteWaypointLeg
205 B.8 Information types
B.8.1 InformationType in general
Table B.20 ā€“ General information types
206 B.8.2 RouteInfo
Table B.21 ā€“ Table format for RouteInfo
207 B.8.3 RouteSchedules
Table B.22 ā€“ Table format for RouteSchedules
208 B.8.4 RouteSchedule
Table B.23 ā€“ Table format for RouteSchedule
209 B.8.5 RouteScheduleManual
Table B.24 ā€“ Table format for RouteScheduleManual
210 B.8.6 RouteScheduleCalculated
B.8.7 RouteScheduleRecommend
Table B.25 ā€“ Table format for RouteScheduleCalculated
211 B.8.8 RouteScheduleElement
Table B.26 ā€“ Table format for RouteScheduleRecommend
212 Table B.27 ā€“ Table format for RouteScheduleElement
213 Annex C (informative)Examples of how to fulfil the requirementsof IMO voyage planning
C.1 General
C.2 Reference points
Figure C.1 ā€“ Example of reference point
214 C.3 Astronomical events
Figure C.2 ā€“ Example of presentation of added textual information
215 C.4 Under keel clearance
Figure C.3 ā€“ Example of astronomical event
216 C.5 Overhead clearance
Figure C.4 ā€“ Example of presentation of added textual information
218 C.6 Regulated areas
219 Figure C.5 ā€“ Example of presentation of added textual information
220 Figure C.6 ā€“ Example of graphical presentation of regulated area
221 Annex D (normative)Route plan feature catalogue and example
D.1 Application schema
245 D.2 Example
250 Annex E (informative)Guidelines for GML ID allocation
Table E.1 ā€“ Example of GML ID
252 Bibliography

Related products

BS EN IEC 63173-1:2021
$215.11