Introduction
...
The main challenge is to obtain valuable 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 archieved. 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.
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).
HowGoal
The EDIFACT data will be translated to the TIC4.0 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 AUGMENTATIONVALUE 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 the data before it has been processed into the TOS or validated to anticipate the actions.
Global Terminal OperatorsVALUE PROPOSITION: Reduce the integration efforts across terminals
AgenciesVALUE 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 EDIVALUE 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 will be to communicate directly using TIC and not EDI anymore. |
...
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.
...
B | C | D | E | F | G |
C507 | DATA / TIME / PERIOD | ||||
132 - Arrival date/time, estimated | 2005 | Date or time or period function code qualifier | Date / Time Information of the Transport | tos|@|carriervisit|@|departure|@|mooring|@|firstline|time|planned|timestamp: 2002-11-13T0917:00.000Z | |
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 |
...
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.
132 - Arrival date/time, estimated | tos|@|carriervisit|@|arrival|@mooring|@|firstline|time|planned|timestamp: 2380 if 2005=132 |
133 - Departure date/time, estimated | tos|@|carriervisit|@|departure|@|mooring|@|firstline|time|planned|timestamp: 2380 if 2005=133 |
178 - Arrival date/time, actual | tos|@|carriervisit|@|arrival|@|mooring|@|firstline|time|actual|timestamp: 2380 if 2005=178 |
186 - Departure date/time, actual | tos|@|carriervisit|@|departure|@|mooring|@|firstline|time|actual|timestamp: 2380 if 2005=186 |
The component element 2380 holds the date and time: 200211131700.
The component element 2379 holds the format description of the component element 2308: CCYYMMDDHHMM.
...
Panel | ||
---|---|---|
| ||
NAD+CF+MAE:172:20' |
B | C | D | E | F | G |
CA Carrier | 3035 | PARTY FUNCTION CODE QUALIFIER | tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|partyfunctioncode : CF | ||
C082 | PARTY IDENTIFICATION DETAILS | ||||
3039 | Party Identifier | Company Code | tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|output|actual|value : MAE | ||
160 Party identification | 1131 | Code list identification code | Kind of Party | tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|codelistidentificationcode : 172 | |
20 BIC (Bureau International des Containeurs) | 3055 | Code list responsible agency code | tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|qualifier : 20 |
NAD is the SMDG TAG for name and address.
...
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
...
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#3055|partyfunctioncode : 3035
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#3055|partyfunctionname : 3035 (see list)
example: tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#20|partyfunctioncode : CF
MAE:172:20
This is the smdg data element C082 which holds the party identification details.
...
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#20|output|actual|value : MAE
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#3055|output|actual|value : 3039
172 is an entry of list 1131 and describes the kind of the party.
...
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#20|codelistidentificationcode : 172
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#20|codelistidentificationname : Carriers
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#3055codelistidentificationcode : 3039
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#3055codelistidentificationname : 172= Carriers/160 Party identification
20 is an entry of the list 3055 and describes the code list standards from which the data values were taken.
...
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#20|qualifier : 20
tos|@|cargo|@|responsibleparty|metadata|output.actual|#qualifier#20|codelistresponisbleagencyname : BIC
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#3055|qualifier : 3055
tos|@|cargo|@|responsibleparty|metadata|output|actual|#qualifier#3055#|codelistresponisbleagencyname : 3055 see list
DATA BASE
The backend of this code is public available at
...