A Standard IMO data elements |
2.1 Table 1 shows the Organization's definitions for the data elements of the IMO Data Set. The Organization documents these definitions in the Compendium to promote harmonization among different data models and to help ensure accurate transmission, receipt and response of electronic data exchange. Each data element receives a unique identifier for reference purposes. In addition, table 1 shows the correlation between each data element and the legacy paper forms used to record the information in paragraph 1.1.4 with a notation of the relevant form cell number.
2.2 Mapping legacy paper forms to an electronic data exchange environment necessitates a number of decisions to represent and utilize the data most efficiently. For example, in the legacy paper forms, designed for completion by hand, several data elements often populate a single cell, such as the numerous characteristics or markings of a particular cargo. In the electronic environment, each data element is discriminated. In addition, paper forms do not accommodate the efficiency of using attributes to distinguish different types of similar data. For instance, a person's possible attributes include agent, crewmember, security officer or passenger. Furthermore, repeated information, such as the IMO number, ship name, ship type, and arrival time and date, can be stored and repeated in electronic data exchange, whereas it must be re-entered in each case on a paper form.
2.3 The IMO Data Set includes some data elements not found on the legacy paper forms but which are required for electronic data exchange, such as the message header date-time stamp, unique identifiers and other requirements for message tracking and machine-to-machine communications.
|
B Using the IMO data set |
2.4 The Change Indicator column shows the status of the data element in that row to help maintain the history of changes to the data set. The change indicator meanings are:
|
|
.1 a plus sign (+) for an addition to the data set since the last edition;
.2 a minus sign (-) for a deletion from the data set since the last edition; and
.3 a hash sign (*) for changes to a data element since the last edition.
|
|
|
2.5 The Data Number column shows the unique number assigned to each data element for reference. The "IMO" prefix identifies the source of the data element and distinguishes it from other data model elements.
2.6 The Data Element column shows the standard name of each data element.
2.7 The Definition column shows the standard definition of each data element. Note, these definitions seek to satisfy technical details. Therefore, instead of the traditional definition, some definitions refer to the information location so that the system or software designer can determine the specific format detail requirements.
2.8 The Correlation to IMO Standard Reporting columns show the location of each data element in the traditional paper versions of the FAL declarations by cell number or other reference. An "X" in this column indicates a data element not described in the annex to the Convention or other sources but commonly used in electronic data exchange. Dark grey cell shading identifies a data element needed to transmit electronic messages but not used in the traditional paper versions of the FAL declarations. Light grey cell shading identifies a data element not included in the data structure shown in section 3 because it derives from a combination of other data elements.
2.9 The Format column shows the required format of each data element for electronic data exchange purposes.
2.10 The format indicator meanings are:
a alphabetic characters
n numeric characters
an alphanumeric characters
a3 3 alphabetic characters, fixed length
n3 3 numeric characters, fixed length
an3 3 alphanumeric characters, fixed length a..3 up to 3 alphabetic characters
n..3 up to 3 numeric characters
an..3 up to 3 alphanumeric characters
n..11,3 up to 11 numeric characters of which 3 positions for a decimal
Examples for a n..11,3 type:
12345678.123 (Valid)
123456789.123 (Invalid – too many digits before decimal point and too many digits in total)
12345678.1234 (Invalid – too many digits after decimal point and too many digits in total)
Numerical fields should be either a cardinal value (integer value) or a decimal value. The decimal separator is the decimal point"." and no other symbols are permitted as a decimal separator. The decimal notation (with the decimal point) should only be used to indicate required precision. Triad separators, such as a comma, should not be used.
|
|
2.11 The Code Lists column identifies the source of specific standardized codes for the data element in that row. For example, ISO standard 3166-1, Codes for the representation of names of countries and their subdivisions, contains the internationally agreed list of two-character country codes. In some cases, cells in this column contain the phrase "To be defined" to identify a standardized code list that is envisioned in future use. The Code Lists under the maintenance responsibility of IMO are set out in annex 4.
2.12 The Business Rule column identifies recommended procedures for satisfying specific data element formats and requirements by referencing a relevant business rule listed in section 4.
2.13 The link https://www.unece.org/cefact/recommendations/rec_index.html leads to the list of a list of UNECE trade facilitation recommendations. |
|
|
|