...

Introduction

This introduction gives an overview of the whitepaper from the TIC4.0 will provide the metadata from EDI to create Data Value. It offers an overview of how to translate and incorporate EDI data, from any source (EDI message, TOS, or whatever) to a TIC message, register or data lake (centralized data repository).

This introduction gives an overview of the whitepaper from the point of view of the context, goal, use cases, value proposition, EDI structure, methodology and database.

...

Nowadays, EDIFACT is the established method to exchange information between terminals. For example, operator orders informing about the expected arrival and departure of cargo along with the associated visits & means of transport. These are used in the TOS for operational planning on the terminal e.g. berth planning, stacking or (un)loading.

Challenges

At the moment it is hard The main challenge is to obtain valuable combined information or create useful automated “triggers” as EDI lacks integration with TIC.

Advantage

The main advantage is to support the common set of KPI’s to get a With the integration of EDI data in TIC4.0 a more holistic view of the terminal performance can be achieved. A bonus is that the meaning of EDI data will be positive side effect is to set the EDI data in the context of the TIC4.0 which makes them easier to understand. It offers the capability to fuse data with container and vessel operators, on the one hand, and local terminal operations, maintenance, and yard optimization, on the other.

Goal

The EDIFACT data will be translated to the TIC4.0 will provide the metadata from EDI to create Data Value. It offers an overview of how to translate and incorporate EDI data, from any source (EDI message, TOS, or whatever) to a TIC message, register or data lake (centralized data repository).

How

The EDIFACT data will be translated to the TIC4.0 Data standard/model via the provision of definitions, data formats, data Data standard/model via the provision of definitions, data formats, data models and examples to easily implement the standard.

Happy reading!

Potential use cases

Info

Terminal Operators: TOS AUGMENTATION

VALUE PROPOSITION: Empower what the TOS does by adding different data sources to TOS capabilities using the same language to reduce complexity on integration and adoption. Enable Enrich the data before it has been processed into the TOS or validated to anticipate the actions.

Automated workflow checklist
- COPRAR received (3 / 8)
- MOVINS
- BAPLIE
- Gang assignment

OUTBOUND BAPLIE (or any other EDI):
- Automatically send to other stakeholders in TIC4.0
- Stakeholders will receive the BAPLIE and
Vehicle booking system prediction
- CODECO vs COPINO trends (which was the planned vs executed?)
- COPRAR-D
BAPLIE + MOVINS:
- Trigger alarms to users in order to adapt QC sequences to tackle those vessel bays with higher stowage plans during low tide
- Suggest actions to users in order to nominate the required personnel to perform special operations such as OOG containers that need to be handled with chains / slings
- To know what is going to be discharged / loaded on vessel calls
Make use of advanced capabilities to make predictions from data trends and determine influencing factors.
- For instance, to determine when containers are going to depart from the terminal (vessel, gate…), dwell times according to FDEST, vessel rollouts, gate out date …
Integrate different systems for use on emulation / simulation environments using the same standard

Global Terminal Operators

VALUE PROPOSITION: Reduce the integration efforts across terminals

Combine data from different terminals (and different TOS) using the same standard. In case they are managing terminals around the world and the terminals currently use different standards
- X12 (ANSI)
- EDIFACT
- TOS (Navis, Cyberlogitec, TSB, RBS …)
Process orchestration and workflow management across different terminals in the portfolio to include different data sources using the same format
- Facilitate easier integration with minimized effort to make use of data which is combined from different sources
  - EDI (COARRI, BAPLIE, MOVINS, COPRAR, CODECO, COPINO …)
  - TOS (N4, CATOS, OPUS …)
    - Vessel calls information
    - Yard Inventory
    - Verified load / discharge list
  - M&R
    - Equipment (availability …)
  - Weather API

Added value:
- Trigger alarms prior to processing in TOS for critical discrepancies between EDI files and other sources such as Yard Inventory
  - For instance:
    - IMO 1 container to be received by Gate (info from CODECO) suggest actions to users prior to receiving the container
    - Take actions Allow better operations preparation in case a certain number of empty containers are ordered to be loaded on vessel
- Combine information from different sources
  - For instance: predict yard fluctuations for the next week, combining different data sources, depending on if EDI are received and processed on TOS
  - Historic -> Estimations -> EDI -> Definitive lists

Agencies

VALUE PROPOSITION: Be connected to different data sources from stakeholders (as terminals, central planners…) using the same standard. For instance: Send EDIs as converted to TIC to terminals and shipping line (COPRARs and Bookings) and receive validated load and discharge list in TIC (For which there are not currently EDI standard)

Modernize interfacing EDI

VALUE PROPOSITION: Intermediate step to modernize and reduce the complexity of the EDI. TIC4.0 global adoption will take time. In the meantime, a translator is needed between EDI and TIC to enable all terminals and systems integration using the same standard. Next step In future it will be possible to communicate directly using TIC and not EDI anymoreexchange all data using the same integrated technology.

EDI structure

The base of the Task Force review and conversion is the Ship Message Design Group (SMDG) Standard which is published by the SMDG group, see EDIFACT MIGs – SMDG e.V. .

...

As a starting point, the smaller EDI message COARRI was chosen to gain experience with the structure and find a good way to review and document the results.

Structure of the EDI File:

The EDI Files follow the same structure and definition of data.

...

UNH Service segment to start and uniquely identify a message

BGM A segment to indicate the beginning of a message and to transmit an identifying number and the further specification of the message type.

Message Body is separated in Segments and Groups dependent on the kind of message

CNT A segment to specify the number of containers in the message, explicitly given by the sender.

UNT A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.

Segments

The way to read and translate the EDIFACT files is explained with the help of some examples.

...

+ is used as a separator between the elements
In the case of composite elements, “:” is used as a separator.
To read a segment we analyze from left to right the content between two “+”.

Example A:

Panel

bgColor	#EAE6FF

DTM+132:202302221600:203'

...

132 - code for arrival time.

202302221600 – concrete confirmed date and time of the arrival

...

As you can find the extract below 2005 is the id of the list. 132, 133, 178 and 186 are the allowed values.

The next example in this line is the 203. This is an entry from the code list 2379.In this case only the value 203 is allowed.

Example B

Panel

bgColor	#DEEBFF

EQD+CN+NYKU4116702+45G1:102:5++3+5'

...

5 - full or empty indicator code – element of list 8169 (allowed values 4, 5, 6)

Extract from the SMDG Standard document related to this example line:

...

Translation Methodology

The review of the EDI messages and translation was done by going through the EDI standard segment-wise. For each segment we considered the possible values transferred and allowed in each TAG. These are either translated in existing TIC4.0 fields or new fields were defined.

...

The table used contains several columns to define the ‘to-be-mapped’ content and the TIC Data Mapping fields.

Explanation of the Columns in the attached EXCEL Database:

Column	Name	Content
A	###	counter / id
B	Possible Code	Allowed Codes according to SMDG
C	EDI SMDG Data Element	Name of the data element
D	EDI SMDG Component Element	Name of the data component element (like list number)
E	EDI SMDG Data name	SMDG Name of the data
F	“Human Name”	Explanation which data are kept in this field
G	TIC Data Mapping	Mapping in the TIC Data structure

In the following, a similar example like example A above is now used to explain how the translation is done and how to read the attached EXCEL Sheet.

Example 1:

Panel

bgColor	#EAE6FF

DTM+133:200211131700:203'

Extract from the EXCEL Sheet with the translation of this example:

B	C	D	E	F	G
	C507		DATA / TIME / PERIOD
132 - Arrival date/time, estimated 133 - Departure date/time, estimated 178 - Arrival date/time, actual 186 - Departure date/time, actual		2005	Date or time or period function code qualifier	Date / Time Information of the Transport	tos

DTM is the TAG for the SMDG data element C507 - Date / Time Period. This explains the following information and doesn’t require fields in the TIC4.0 wordwording.

The following information is relevant after the In the example DTM is followed by a +, which specifies the date information in more detailis the separator between TAG and information transferred in this line.

Panel

bgColor	#DEEBFF

DTM+133:200211131700:203'

...

We have 4 different allowed values which describe “different meanings” for the following date. This means that they have to go to different fields in the TIC 4.0 format.

Allowed values	Translation TIC4.0
132 - Arrival date/time, estimated	tos

The component element 2380 holds the date and time: 200211131700.

The component element 2379 holds the format description of the component element 2308: CCYYMMDDHHMM.

Example 2

This example explains the use of the lists from smdg in the TIC4.0 database related to the EDI translation

Panel

bgColor	#DEEBFF

NAD+CF+MAE:172:20'

Extract from the EXCEL Sheet with the translation of this example:

B	C	D	E	F	G
CA Carrier CF Container operator/lessee HR Shipping line service MR Message recipient MSDocument/message issuer/sender	3035		PARTY FUNCTION CODE QUALIFIER		tos

...

Panel

bgColor	#DEEBFF

NAD+CF+MAE:172:20'

NAD is the SMDG TAG for name and address.

The following information is relevant after the +, which specifies the date information in more detailis used as separator.

CF is an entry of the smdg data element 3035 which has a fix list of allowed values:

CA Carrier
CF Container operator/lessee
HR Shipping line service
MR Message recipient
MSDocument/message issuer/sender

The definition in the TIC data model is done as follows. There are metadata defined for it. The metadata partyfunctioncode holds the number of the list. :he metadata partyfunctionname holds the list with the possible values.

MAE:172:20

This is the smdg data element C082 which holds the party identification details.

MAE is the data value. After the “:'s ” it is described what exactly this data value describesrepresents. As each filed in smdg this one has a number: 3039

This is translated as follows:

172 is an entry of list 1131 and describes the kind of the party.

...

This is translated similar to the example before:

20 is an entry of the list 3055 and describes the code list standards from which the data values were taken.

...

This is translated as follows:

...

DATABASE

The backend of this code is public publicly available at

View file

name	EDI template TiC_COARRI V10 20240411.xlsxV12 20240523.xlsx

The database will be updated and populated for all EDI messages (work in progress). This database will allow the user to translate any EDI content to TIC 4.0 straightforwardly.

Versiones comparadas

Versión anterior 66

Nueva versión Actual

Clave

Introduction

Potential use cases

Terminal Operators: TOS AUGMENTATION

Global Terminal Operators

Agencies

Modernize interfacing EDI

EDI structure

Structure of the EDI File:

Segments

Example A:

Example B

Translation Methodology

Example 1:

Example 2

DATABASE

\|timestamp: 2380 if 2005=186
	2380	Date or time or period value	Arrival/departure date/time
203 - CCYYMMDDHHMM	2379	Date or time or period format code		COARRI is CCYYMMDDHHMM format ant TIC4.0 is always in ISO8601 format

\|@mooring\|@\|firstline\|time\|planned\|timestamp: 2380 if 2005=132
133 - Departure date/time, estimated	tos

\|timestamp: 2380 if 2005=133
178 - Arrival date/time, actual	tos

\|timestamp: 2380 if 2005=178
186 - Departure date/time, actual	tos

\|@\|responsibleparty\|metadata\|output\|actual\|#qualifier#3055\|partyfunctionname : 3035 (see list)
	C082		PARTY IDENTIFICATION DETAILS
		3039	Party Identifier	Company Code	tos

\|@\|responsibleparty\|metadata\|output\|actual\|#qualifier#3055\|output\|actual\|value : 3039
160 Party identification 172 Carriers		1131	Code list identification code	Kind of Party	tos

\|@\|responsibleparty\|metadata\|output\|actual\|#qualifier#3055codelistidentificationname : 172= Carriers/160 Party identification
20 BIC (Bureau International des Containeurs) 87 Assigned by carrier 166 US, National Motor Freight Classification Association 184 AU, ACOS (Australian Chamber of Shipping) SMD SMDG (Shipplanning Message Development Group) ZZZ Mutually defined		3055	Code list responsible agency code		tos

Comparación de páginas

Versiones comparadas

Versión anterior 66

Nueva versión Actual

Clave

<span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-0">[data-colorid=</span>

<span class="diff-html-added" data-a11y-before="Start of added content" data-a11y-after="End of added content" id="added-diff-8">y7iy4laf5d</span><span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-9">]{color:</span>

Potential use cases

Terminal Operators: TOS AUGMENTATION

Global Terminal Operators

Agencies

Modernize interfacing EDI

EDI structure

Structure of the EDI File:

Segments

Example A:

Example B

Translation Methodology

Example 1:

Example 2

DATABASE