Versiones comparadas

Versión anterior 70

changes.mady.by.user TIC-Team Eurogate

Guardado el

comparado con

Nueva versión 71

changes.mady.by.user TIC-Team Eurogate

Guardado el

Clave

  • Se ha añadido esta línea.
  • Se ha eliminado esta línea.
  • El formato se ha cambiado.

Introduction

...

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 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

        • 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 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. 

...

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

 

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 Data base:

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

...

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|@|carriervisit|@|departure|@|mooring|@|firstline|time|planned|timestamp: 2002-11-13T0917:00.000Z
tos|@|carriervisit|@|departure|@|mooring|@|firstline|time|planned|timestamp: 2380 if 2005=133
tos|@|carriervisit|@|arrival|@|mooring|@|firstline|time|planned|timestamp: 2380 if 2005=132
tos|@|carriervisit|@|arrival|@|mooring|@|firstline|time|actual|timestamp: 2380 if 2005=178
tos|@|carriervisit|@|departure|@|mooring|@|firstline|time|actual|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

...

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|@|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
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|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|partyfunctioncode : CF
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|partyfunctionname : Container operator/lease
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#3055|partyfunctioncode : 3035
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#3055|partyfunctionname : 3035 (see list)

C082

PARTY IDENTIFICATION DETAILS

3039

Party Identifier

Company Code

tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|output|actual|value : MAE
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#3055|output|actual|value : 3039

160 Party identification
172 Carriers

1131

Code list identification code

Kind of Party

tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|codelistidentificationcode : 172
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|codelistidentificationname : Carriers
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#3055codelistidentificationcode : 3039
tos|@|cargo|@|responsableparty|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|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|qualifier : 20
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#20|codelistresponisbleagencyname : BIC
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#3055|qualifier : 3055
tos|@|cargo|@|responsableparty|metadata|output|actual|#qualifier#3055#|codelistresponisbleagencyname : 3055 see list

...

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

...

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

...