Ships and marine technology — Electronic port clearance (EPC) — Part 3: Data elements for ship and port operation

This document provides technical specifications to facilitate an efficient exchange of electronic information between ships and shore, for coastal transit and port calls, with a specific focus on the operational data exchange. It specifies requirements to enhance the safety, security and efficiency of information exchanges. This document describes core data elements for use in electronic port clearance (EPC) messages. It does not define any structuring of messages, but rather gives general details on safety-, security- and operation-related maritime information in the context of EPC messages. Details about message formats and applications are found in ISO 28005-1.

Navires et technologie maritime — Opérations portuaires assistées par systèmes électroniques — Partie 3: Éléments de données pour l'exploitation des navires et des ports

General Information

Status
Published
Publication Date
05-Dec-2024
Current Stage
9092 - International Standard to be revised
Start Date
17-Dec-2024
Completion Date
13-Dec-2025
Ref Project
Standard
ISO 28005-3:2024 - Ships and marine technology — Electronic port clearance (EPC) — Part 3: Data elements for ship and port operation Released:12/6/2024
English language
85 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


International
Standard
ISO 28005-3
First edition
Ships and marine technology —
2024-12
Electronic port clearance (EPC) —
Part 3:
Data elements for ship and port
operation
Navires et technologie maritime — Opérations portuaires
assistées par systèmes électroniques —
Partie 3: Éléments de données pour l'exploitation des navires et
des ports
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Reference to data types defined in ISO 28005-2:2021 . 2
4.1 General .2
4.2 Data types modified from ISO 28005-2:2021 .2
5 Relation to the IMO Compendium . 3
6 EPC request body . 4
7 General data types . 7
7.1 General .7
7.2 Epc:ContactInfoType – Contact information .7
7.2.1 Definition .7
7.2.2 Type .7
7.2.3 Representation .7
7.3 epc:CommunicationNumberType – Communication number information .8
7.3.1 Definition .8
7.3.2 Type .8
7.3.3 Representation .8
7.4 epc: ContactTypeContentType - Type of contact for dangerous goods .8
7.4.1 Definition .8
7.4.2 Type .8
7.4.3 Representation .8
7.5 epc:DateTimeType – DateTime with type .8
7.5.1 Definition .8
7.5.2 Type .8
7.5.3 Representation .9
8 Core data types . 9
8.1 General .9
8.2 Ship identity and contacts data types .9
8.2.1 epc:SatelliteServiceProviderCodeContentType .9
8.2.2 epc: SatelliteServiceType – Satellite service number to the ship .9
8.3 Cargo data types .10
8.3.1 epc:CargoDataType – Detailed description of cargo .10
8.3.2 epc:CargoOverviewType – Brief description of onboard cargo .17
8.4 Crew and passenger data .17
8.4.1 Class diagram .17
8.4.2 Non-core data types .17
8.4.3 epc:OtherPersonListType – Information about other persons on board .19
8.4.4 epc:PersonsOnboardNumberType – Number of persons onboard .19
8.4.5 epc: StowawayDetailsType – Details about stowaways found onboard . 20
8.4.6 LanguageContentType . 22
8.5 Class and ship certificates . 22
8.5.1 Class diagram . 22
8.5.2 epc:CertificateType – Certificate description . 22
8.5.3 epc:ISSCertificateStatusType – Security certificate information . 25
8.5.4 epc:ShipClassType – Class notation for ship . 25
8.5.5 Epc: ClassSocietyContentType – Enumeration type for RO/RSO/class . 26
8.6 Ship particulars types. 26
8.6.1 General . 26
8.6.2 Epc:ShipParticularsType – Ship particulars . 26
8.6.3 epc:ShipRegistryType – Ship registry details . 28

iii
8.6.4 epc:DeadWeightType – Dead weight . 29
8.6.5 epc:GrossTonnageType – Gross tonnage . 29
8.6.6 epc: SRSRemarksType – Remarks for ship reporting systems . 29
8.7 Vessel operation data types . 30
8.7.1 General . 30
8.7.2 epc: ShipStatusType – Ship status information . 30
8.7.3 epc:WeatherInformationType – Weather information as observed . 30
8.8 Location types .32
8.8.1 General .32
8.8.2 Non-core data types .32
8.8.3 epc:WaypointListType – Waypoint and waypoint list . 34
8.8.4 epc:VoyageEventListType – Time and position for voyage events . 35
8.8.5 epc:PilotBoardingPlaceArrivalType – Pilot boarding place and arrival time . 36
8.8.6 epc:PilotBoardingPlaceDepartureType – Pilot boarding place and departure time . 36
8.9 Ballast water arrival reporting data types .37
8.9.1 General .37
8.9.2 epc:BallastWaterManagementType .37
8.9.3 epc:BallastTankType . 38
8.10 Waste and environmental data types . 40
8.10.1 General . 40
8.10.2 epc:BallastStatusType – Status of ship's ballast water when in port .41
8.10.3 epc:WasteDisposalRequirementsType – Ship's requirements for waste disposal .41
8.10.4 epc: WasteInformationType – Waste information .41
8.11 Health data types .43
8.11.1 Class diagram .43
8.11.2 epc: HealthDataType – Health information for the ship.43
8.12 Maritime service data types .45
8.12.1 epc:MaritimeServiceType – Information related to a maritime service .45
8.13 Inspection data types . 46
8.13.1 General . 46
8.13.2 epc:InspectionType – Information related to inspections . 46
8.13.3 epc:DetentionType – Inspection detention . 48
8.13.4 epc:InspectionCommentType – Information related to an comment given
during an inspection . 48
8.13.5 epc:DeficiencyType – Inspection deficiency . 50
8.13.6 epc:ShipBannedType – Ship banned type .51
8.14 Advanced passenger information .51
8.14.1 General .51
8.14.2 Epc:PersonBookingType .51
8.15 Verified gross mass .52
8.15.1 General .52
8.15.2 Epc:VerifiedGrossMassType .52
8.16 Coastal station name type. 53
8.16.1 Definition . 53
8.16.2 Type . 53
8.16.3 Representation . 53
Annex A (normative) Mapping between this document and the IMO FAL .54
Bibliography .83

iv
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 8, Ships and marine technology, Subcommittee
SC 11, Intermodal and Short Sea Shipping.
A list of all parts in the ISO 28005 series are found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

v
International Standard ISO 28005-3:2024(en)
Ships and marine technology — Electronic port
clearance (EPC) —
Part 3:
Data elements for ship and port operation
1 Scope
This document provides technical specifications to facilitate an efficient exchange of electronic information
between ships and shore, for coastal transit and port calls, with a specific focus on the operational data
exchange. It specifies requirements to enhance the safety, security and efficiency of information exchanges.
This document describes core data elements for use in electronic port clearance (EPC) messages. It does
not define any structuring of messages, but rather gives general details on safety-, security- and operation-
related maritime information in the context of EPC messages.
Details about message formats and applications are found in ISO 28005-1.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 6346, Freight containers — Coding, identification and marking
ISO 6709, Standard representation of geographic point location by coordinates
ISO 9711-1, Freight containers — Information related to containers on board vessels — Part 1: Bay plan system
UNECE R21 (UNECE Recommendation No. 21), Codes for Passengers, Types of Cargo, Packages and Packaging
Materials (with Complementary Codes for Package Names)
UNECE R16 (UNECE Recommendation No. 16), United Nations Code for Trade and Transport Locations (ECE/
TRADE/459)
3 Terms and definitions
No terms and definitions are listed in this document.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/

4 Reference to data types defined in ISO 28005-2:2021
4.1 General
Several XSD [extensible markup language (XML) schema definition] data types defined in ISO 28005-2:2021
have been reproduced in this document. Some of the definitions reproduced from in ISO 28005-2:2021 have
been changed in this document. A summary of the changes is listed in Table 1.
4.2 Data types modified from ISO 28005-2:2021
Table 1 lists data types, data elements, and code lists from ISO 28005-2:2021 that have been modified in this
document.
Table 1 — Changes to data types from ISO 28005-2:2021
Definitions from ISO 28005-2:2021 Definitions in this document
Epc:InmarsatCallNumberType epc:SatelliteServiceType
Epc:ShipNameType epc:ShipIdType
BeamType epc:ShipParticularsType
DeadWeightType epc:ShipParticularsType
DoubleBottomContentType epc:ShipParticularsType
GrossTonnageType epc:ShipParticularsType
IceClassType epc:ShipParticularsType
LengthOverallType epc:ShipParticularsType
NetTonnageType epc:ShipParticularsType
SummerDraughtType epc:ShipParticularsType
ShipTypeContentType epc:ShipParticularsType
ISSCStatus in data type ISSCertificateSta- epc:CertificationType.ValidCertificateIndicator and epc:ISSCertifi-
tusType cateStatusType.ISSCStatus
Data elements EmbarkationDate and Debarka- Embarkation.DateTime [TimeType = Actual, Planned etc] and De-
tionDate in PersonOnboardType barkation.DateTime [TimeType = Actual, Planned etc]
Data element IsssuerLocation in Certificate- CertificateIssueLocationCode and CertificateIssueCountryCode in
Type CertificateType
epc:ContactInfoType updated version of epc:ContactInfoType
epc:CommunicationNumberType updated version of epc:CommunicationNumberType
epc:DateTimeType updated version of epc:DateTimeType
Ship identity and contacts data types updated versions are used
Cargo data types updated versions are used
Crew and passenger data updated versions are used
Class and ship certificates updated versions are used
Ship particulars types updated versions are used
Vessel operation data types updated versions are used
Location Types updated versions are used
Waste and environmental data types updated versions are used
Health data types updated versions are used
epc:ShipClassType updated versions of epc:ShipClassType and epc: ClassSocietyCon-
tentType
Waste and environmental data types updated versions are used
Ship Particulars Types updated versions are used
Annex A Table 2
TTabablele 1 1 ((ccoonnttiinnueuedd))
Definitions from ISO 28005-2:2021 Definitions in this document
Annex B Annex A
[30]
Annex D code values as defined in the IMO Compendium
Annex E code values as defined in the IMO Compendium, Annex A Sec-
[30]
tion 9
[30]
Annex F use code values as defined in the IMO Compendium instead.
[30]
Annex G code values as defined in the IMO Compendium
[30]
Annex L code values as defined in the IMO Compendium
[30]
Annex P code values as defined in the IMO Compendium
[30]
Annex R code values as defined in the IMO Compendium
Annex A Table 2
Annex B Annex A
[30]
Annex D code values as defined in the IMO Compendium
Annex E code values as defined in the IMO Compendium Annex A Sec-
[30]
tion 9
5 Relation to the IMO Compendium
The data types defined in this document are a starting point for the implementation of the data elements
[30]
and the reference model defined in the IMO Compendium on Facilitation and Electronic Business. The
mapping between the data elements in this document and the data elements in the IMO Compendium shall
[30]
be carried out as specified in Annex A. The IMO Compendium is approved by the facilitation committee in
IMO (IMO FAL).
This document includes data types for all data elements in the IMO compendium as decided by IMO FAL
[31]
47, including data sets for:
[38]
— Maritime Declaration of Health
— Just in time concept
— Stowaways
— Ship and company certificates
— Acknowledgment receipt
— Maritime service
— Ship registry and company details
— Inspections
— Port state control (PSC) inspection history data
— Ship reporting systems
— Ballast water arrival reporting
— Waste delivery report
— Advanced passenger information
— Verified gross mass
6 EPC request body
Table 2 lists the data elements in the EPC request body.
Table 2 — EPC request body
Core element Type Cardi- Description
nality
Agent epc:Agent Type 0.1 The ship's agent
AirDraught epc:AirDraughtType 0.1 Air draught
AnchorageArrival epc:AnchorageArrivalType 0.* Specification of arrival to an anchorage.
The arrival time can be actual, estimated,
planned or requested.
AnchorageDeparture epc:AnchorageDepartureType 0.* Specification of departure from an anchor-
age. The departure time can be actual,
estimated, planned or requested.
ArrivalDeparture epc:ArrivalDepartureType 0.1 Arrival or departure flag
ArrivalDraught epc:ArrivalDraughtType 0.1 Arrival draught
ATP epc:ATPType 0.1 Actual time of passage
Authenticator epc:AuthenticatorType 0.1 Information about the authenticator of the
information
BallastStatus epc:BallastStatusType 0.1 Status of ship's ballast water when in port
BallastWaterArrivalRe- Epc:BallastWaterManagementType 0.1 Ballast water arrival reporting
porting
BerthArrival epc:BerthArrivalType 0.* Specification of arrival to a berth. The
arrival time can be actual, estimated,
planned or requested.
BerthDeparture epc:BerthDepartureType 0.* Specification of departure from a berth.
The departure time can be actual, estimat-
ed, planned or requested.
BerthPositionArrival epc:BerthPositionArrivalType 0.* Specification of arrival to a berth position.
The arrival time can be actual, estimated,
planned or requested.
BerthPositionDeparture epc:BerthPositionDepartureType 0.* Specification of departure from a berth
position. The departure time can be actual,
estimated, planned or requested.
BulkLoadUnloadData epc:BulkLoadUnloadDataType 0.1 Data required for safe loading and unload-
ing
CallPurpose epc:CallPurposeType 0.* Purpose of call
CargoData epc:CargoDataType 0.1 Detailed description of cargo
CargoOverview epc:CargoOverviewType 0.1 Brief description of onboard cargo
CertificateList epc:CertificateListType 0.1 List of ship's certificates
Company epc:CompanyType 0.1 The ship's operating company
CSO epc:CompanySecurityOfficerType 0.1 Information about the company security
officer shown in the ship security plan.
CrewList epc:CrewListType 0.1 Information about all crew on board, in-
cluding information about the Master.
Key
* = the maximum number of instances of this data type is unbounded
0.* = there is/are 0, 1 or many instance(s) of this data type
0.1 = there is/are 0 or 1 instance(s) of this data type

TTabablele 2 2 ((ccoonnttiinnueuedd))
Core element Type Cardi- Description
nality
CrewReference epc:CrewMemberDataType 0.1 Reference to the crew onboard that has
authorized a message from the ship.
CurrentPortSecurityLevel epc:CurrentPortSecurityLevelType 0.1 Current security level in port.
CurrentShipSecurityLevel epc:CurrentShipSecurityLevelType 0.1 Current security level on ship.
DangerousGoodsCargoIn- epc:DangerousGoodsCargoIndica- 0.1 A yes/no indicator whether the ship is car-
dicator torType rying any dangerous goods.
DepartureDraught epc:DepartureDraughtType 0.1 Departure draught
DutiableCrewEffects epc:DutiableCrewEffectType 0.1 List of crew effects that are dutiable
ETP epc:ETPType 0.1 Estimated time of passage
FacilityArrival epc: FacilityArrivalType 0.* Specification of arrival to a facility. The
arrival time can be actual, estimated,
planned or requested.
FacilityDeparture epc: FacilityDepartureType 0.* Specification of departure from a facility.
The departure time can be actual, estimat-
ed, planned or requested.
GeneralDescriptionOfDG epc:GeneralDescriptionOfDGType 0.1 General description of dangerous cargo
GeneralRemark epc:RemarksType 0.1 Statement of any other information rele-
vant to ship arrival, stay or departure
HasSecurityPlan epc:HasSecurityPlanType 0.1 Approved security plan
HealthData epc:HealthDataType 0.1 Health information for the ship
INFClassContent epc:INFClassContentType 0.1 Irradiated nuclear fuel class
ISSCertificateStatus epc:ISSCertificateStatusType 0.1 International Ship Security (ISS) Certifi-
cate status
LastPortOfCall epc:LastPortOfCallType 0.1 Last port of call
MaritimeService Epc:MaritimeServiceType 0.1 Reference to a maritime service related to
ServiceName and ServiceCode as given in
the EPCMessageHeaderType.
NavigationalStatus epc:NavigationalStatusContent- 0.1 Navigational status
sType
NextPortOfCall epc:NextPortOfCallType 0.1 Next port of call
NextReportTime epc:NextReportTimeType 0.1 Time of next report
OBOLoadUnloadData epc:OBOLoadUnloadDataType 0.1 Data required for safe loading and unload-
ing of oil-bulk-ore (OBO)
OtherPersonList epc:OtherPersonListType 0.1 List of persons onboard that are neither
crew nor passengers
PassengerList epc:PassengerListType 0.1 Information about passengers
PeriodOfStay epc:PeriodOfStayType 0.1 Period of stay
PersonsOnboard epc:PersonsOnboardNumberType 0.1 Number of persons onboard
PilotBoardingPlaceAr- epc:PilotBoardingPlaceArrival- 0.1 Time and location for an arrival to a pilot
rival Type boarding place
PilotBoardingPlaceDepar- epc:PilotBoardingPlaceDeparture- 0.1 Time and location for a departure from a
ture Type pilot boarding place
PortCallList PortCallListType 0.1 Last ten port calls
Key
* = the maximum number of instances of this data type is unbounded
0.* = there is/are 0, 1 or many instance(s) of this data type
0.1 = there is/are 0 or 1 instance(s) of this data type

TTabablele 2 2 ((ccoonnttiinnueuedd))
Core element Type Cardi- Description
nality
PortOfArrival epc:PortOfArrivalType 0.1 Arrival port and time
PortOfDeparture epc:PortOfDepartureType 0.1 Departure port and time. This includes
port name and possibly ETD and ATD:
PortOfDeparture/Time[Estimated] and
PortOfDeparture/Time[Actual]
PSCInspectionHistory epc:InspectionType 0.* List of port inspection information
Radiocommunications epc:RadiocommunicationsType 0.1 Radiocommunication active
RemarkSRS epc:SRSRemarksType 0.* Additional information regarding a ship
reporting system
ReportingEvent epc:VoyageEventType 0.1 This is the location from which a report is
given and the time given in coordinated
universal time (UTC) when the report is
given. The type is changed from Location-
CallType to VoyageEventType.
RequestStatus epc:RequestStatusType 0.1 Status of a request (used by server)
ROBBunkers epc:ROBBunkersType 0.* Bunkers remaining onboard
SecurityOtherMatter- SecurityOtherMattersToReport- 0.1 Other security matters to report
sToReport Type
ShipBanned epc:ShipBannedType 0.1 Information related to the banning of
a ship as a result of a port state control
inspection.
ShipCertificateList epc:CertificateListType 0.1 List of ship certificates. Name changed
from CertificateListType to ShipCertificat-
eListType to distinguish from ship compa-
ny certificates.
ShipClass epc:ShipClassType 0.1 Class notation for ship
ShipCompanyInspection epc:InspectionType 0.1 Report on inspection of the ship's company
ShipCompanyCertificat- Epc:CertificateListType 0.1 List of certificates for the ship's company
eList
ShipDefects epc:ShipDefectsType 0.* Any defects of important ship equipment
ShipID Epc:ShipIDType 0.1 The set of different identifiers of the ship
ShipInspection epc:InspectionType 0.* Reports on inspection of the ship
ShipParticulars Epc:ShipParticularsType 0.1 Ship particulars
ShipStatus epc:ShipStatusType 0.1 Vessel status information
ShipStore epc:ShipStoreType 0.1 Description of ship's dutiable stores
ShipToShipActivityList epc:ShipToShipActivityListType 0.1 Ship-to-ship activities
ShipType epc:ShipTypeContentType 0.1 Ship type code
TerminalArrival epc: TerminalArrivalType 0.* Specification of arrival to a terminal. The
arrival time can be actual, estimated,
planned or requested.
TerminalDeparture epc: TerminalDepartureType 0.* Specification of departure from a terminal.
The departure time can be actual, estimat-
ed, planned or requested.
VoyageDescription epc:VoyageDescriptionType 0.1 Brief description of voyage.
Key
* = the maximum number of instances of this data type is unbounded
0.* = there is/are 0, 1 or many instance(s) of this data type
0.1 = there is/are 0 or 1 instance(s) of this data type

TTabablele 2 2 ((ccoonnttiinnueuedd))
Core element Type Cardi- Description
nality
VoyageEventList epc:VoyageEventListType 0.1 Time and position when entering /exiting
from ship reporting or getting to a Pilot-
Boarding point.
VoyageNumber epc:VoyageNumberType 0.1 Voyage identification code
WasteDisposalRequire- epc:WasteDisposalRequirement- 0.1 Ship's requirements for waste disposal
ments sType
WasteInformation epc:WasteInformationType 0.1 Waste information
WayPointList epc:WayPointListType 0.1 Way-point list
WeatherInformation epc:WeatherInformationType 0.1 Weather information as observed
Key
* = the maximum number of instances of this data type is unbounded
0.* = there is/are 0, 1 or many instance(s) of this data type
0.1 = there is/are 0 or 1 instance(s) of this data type
7 General data types
7.1 General
This clause contains information on general data types.
7.2 Epc:ContactInfoType – Contact information
7.2.1 Definition
This data type contains contact information for either a person or a company.
7.2.2 Type










7.2.3 Representation
Common information for both persons and companies are addresses and contact numbers. Companies and
persons differ, in that companies have one name in a string, while persons can have a given name, family
name, and middle name. CompanyId is the recognized identification number of the company. ContactType
is a code specifying the type of contact for dangerous goods. The code values are according to UN/EDIFACT
[48]
codes 3139 Contact function code.

7.3 epc:CommunicationNumberType – Communication number information
7.3.1 Definition
This data type specifies a contact point via telephone or other means.
7.3.2 Type










7.3.3 Representation
This element contains a list of contact points for a person or organization. Telephone numbers shall be
specified with an international prefix code. The email tag shall be a valid URI with the “mailto:” prefix.
7.4 epc: ContactTypeContentType - Type of contact for dangerous goods
7.4.1 Definition
This data type is used to specify the type of company that is the contact for dangerous goods.
7.4.2 Type



7.4.3 Representation
This data type contains the enumated values from UN/EDIFACT codes 3139 Contact function code.
7.5 epc:DateTimeType – DateTime with type
7.5.1 Definition
This data type defines a date and time with additional time zone information. It also contains the type of
this time, whether it is an actual time, estimated time, planned time, or requested time.
7.5.2 Type















7.5.3 Representation
The time is represented by the core type epc:dateTime. The time type is represented by the enumeration
TimeTypeContentType containing either actual, estimated, planned or requested. In addition, an event type
can be added, specifying whether the time of event is related to arrival, departure, service start, service
end, or if the event is happening at a certain location (at). This type is a generalization of the types ETPType,
ATPType, ATAType, ETAType, ATDType and ETDType from ISO 28005-2.
8 Core data types
8.1 General
This clause contains data types that are instantiated as core data elements in EPC-related messages. It is
divided into a number of subclauses which contain data types from a specific domain. This subdivision is for
convenience only and does not imply any special organization of core data elements in a specific message.
Where relevant, subclauses are introduced with a simplified class diagram showing the main relationships
between data types defined in the clause. The notation is based on Unified Modelling Language (see
ISO/IEC 19501). An open arrow means that a new type includes an existing type as one new attribute and a
closed arrow means that the new type extends the old by adding all old attributes as its own or that it has
the type of the same. Extension does not require additional attributes to be added. Cardinality is used to
show that an included old type is optional (0.), that it is included exactly once (1:1) or that it is included a
number of times (.*).
8.2 Ship identity and contacts data types
8.2.1 epc:SatelliteServiceProviderCodeContentType
8.2.1.1 Definition
This enumeration data type contains a list of mobile satellite service providers used by ships.
8.2.1.2 Type



8.2.1.3 Representation
[30]
The code list is maintained by IMO and published in the IMO Compendium.
8.2.2 epc: SatelliteServiceType – Satellite service number to the ship
8.2.2.1 Definition
This data type contains satellite service call numbers to a ship.
8.2.2.2 Type







8.2.2.3 Representation
The elements shall be used as follows.
— Number: Satellite service call number. If it is necessary to have the extension code related to the area
in which the ship operates, this extension code shall not be included in this number. If no number is
available, the string should be empty.
— SatelliteServiceProviderCode: The ships recognized mobile satellite service provider.
— Alternative contact information, e.g. via mobile phone, satellite, very high frequency radio (VHF), high
frequency radio (HF) or medium frequency radio (MF).
8.3 Cargo data types
8.3.1 epc:CargoDataType – Detailed description of cargo
8.3.1.1 Definition
The CargoDataType contains the list of consignments of ca
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...