How to link Transport entity to Shipment Event entity?

[RickyTangDeloitte]

Hi Team,

We are looking at DCSA 3.4 Information model and found there is no relationship defined between Transport and Shipment Event entity. In our view, these two should be related. Currently, the shipment event entity is not even linked with shipment entity. Is there a link missing?

Cheers, Ricky

[HenrikHL]

Hi @RickyTangDeloitte,

There is a link between the two (just not in the image). The ShipmentEvent contains two fields: documentID which is UUID pointing to a primary Key and documentTypeCode which identifies what the documentID "points" to

In our SwaggerSpec - this looks like this: (Above image is taken for the GET /events endPoint in EBL)

In case of a Shipment - the documentID would contain the carrier Booking Reference UUID and documentTypeCode would be BKG.

Be aware that a ShipmentEvent can also be used for other notifications such as: ARN (Arrival Notice), SRM (Shipment Release Message), TRD (Transport Document), SHI (Shipping Instruction), etc...

[RickyTangDeloitte]

Hi Henrik,

Thank you so much for your reply. Just wondering is 3.4 the latest one at the moment? I believe the link between Shipment and Shipment Event is also missing in this model?

I do have a question about Transport. I am not quite get it by reading through its definitions and why it links to Equipment event. Can you please give me an example? Is that for Truck/Train to move the good to the port or from the port to its final destination?

@.***

Much appreciated your time.

Cheers, Ricky

From: Henrik Helmø Larsen @.> Sent: Monday, 5 September 2022 7:44 pm To: dcsaorg/DCSA-Information-Model @.> Cc: Tang, Ricky @.>; Mention @.> Subject: [EXT] Re: [dcsaorg/DCSA-Information-Model] How to link Transport entity to Shipment Event entity? (Issue #350)

Hi @RickyTangDeloittehttps://secure-web.cisco.com/1lym_Bs84KDWykI8H0IEcMMV5SGAZy7lyYuuDvCithPTATmnMaHRcExGnXWL_SrzaZwPe3wFrYmr-NbdVBGK1kfu8d-95_r1JjZa1v9exYxrWxq-KWoKrgLE5f-BbocMlBu840iutQDDVI7t6uebDJkJ5UYHUDXD0XWJ9mIzhN_-YWfTseubQCcPaGLJiRNtFnLwjva43r5KpJ84sA1gjkloYuA97JEP2o3j8aQqqA5TbCRAFfiwXby4M7_PDXJ8xMqAPePMI3CKo4DyLpBR0F3fYyAf6X1ZPpi4KfKHMKOI8GV7Bl8PWO4KD6mlYbpCH/https%3A%2F%2Fgithub.com%2FRickyTangDeloitte,

There is a link between the two (just not in the image). The ShipmentEvent contains two fields: documentID which is UUID pointing to a primary Key and documentTypeCode which identifies what the documentID "points" to https://secure-web.cisco.com/1Cu8cqFchu9AzD300Wf9DQR-nImj8khx-EwN1EOHeLOMg1iv0ymbkvM3MBpbLvRU7syDW_iDFzm1gsjzPa1OMxCs7kBIe_6suvBOUb_vkIfTBd-sn3ylnNk4s4NkxSYexorLagZw9xjsmXlSzPdUyG0iHBTrOvjd0gvjWvoxVVLd-atYpjLDFS3hJOoCmybS75q49LG-Jb2MGr9RlUSsV6jS2kGlamRS3Dn47giiRGLbG95bYD_3zRvgKBzBUUqhbsFIQEtJCnG6dKVwDXJyUDACKn3sOjXJeyahzATzqeK1Lvo_iYvf9IKD5OJxlNfGe/https%3A%2F%2Fuser-images.githubusercontent.com%2F3489388%2F188394158-38615162-1f27-4cba-a274-d5533ec14c95.png

In our SwaggerSpec - this looks like this: https://secure-web.cisco.com/1tXXv2izIHNBhuD3grKk7WdAD79yaUs15f1A1oAbJlqf7fYo9EXe0tgxEZY8kvdreQtjp62vIao-SuE55LuWfgpIO2wJI2OgbOjCGu8k-lo6EelpT6rMUZl9KaTh5eQBV0WT8yu-6B-hsfYs7967yXUFdDUwjLM7ybbG3LNVBb-vi4ioGCiDjrzq2cJUioFaaOXgiDT6Qv-YGxnqBq4wST-yNWek4nBrqPqO0NK3KdjPAPr293JpC2ZwDiZUypZhslobx_cFk5Id-CWLvQvkGctJxOIyJrAgXtfhDkGBTuFw8Bzt_wuXIPxlPonh4X8RK/https%3A%2F%2Fuser-images.githubusercontent.com%2F3489388%2F188394725-ca2e9e81-69aa-408e-b5e7-db86347935e4.png (Above image is taken for the GET /events endPoint in EBLhttps://secure-web.cisco.com/1f87DruY458GROMt9r9DFFLDauSrsvB3VNj_HT2bJ1mbiOMMr1JmDkwnZtmn-xMPqmAy1FdWt5ZaEb87ArhuY93ejNFy5IdvacqSWODyl3TPefx3V-mN4QHtm0b7P8HL2mtBIxqF0IE_edggBwW5rGbTknDyka0S05rzr44G13E3sqjR4pMd0C7G4fOpL7twjHy24NJXi9uqgdz3ZxyMI6qrmdOFIDURWKmsrPnHHx88NzhkiNq98cuMP-yoc15hwyUFHqeHwT8MJnW8rgoEIQbD4sotPs7Nx3C4owdfBUs59ABNBMPZzTyukExr6rHM4/https%3A%2F%2Fapp.swaggerhub.com%2Fapis%2Fdcsaorg%2FDCSA_EBL%2F2.0.0-Beta-2%23%2FBill%2520of%2520Lading%2520Events%2Fget_v2_events_)

In case of a Shipment - the documentID would contain the carrier Booking Reference UUID and documentTypeCode would be BKG.

Be aware that a ShipmentEvent can also be used for other notifications such as: ARN (Arrival Notice), SRM (Shipment Release Message), TRD (Transport Document), SHI (Shipping Instruction), etc...

— Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1g6St1Ut413JqXx7QPhFi4EMTMJveiHdwOwNZWITkjEKyLuQvVGgutA9gLefE3tWFDQXuT4g6SJgN7qd0bLvEMeW-v76NQsoPDtWRemyU0SDg7iymJKw_USCSuxPaY6TkHHMnfC4dkSIoByae0tFCV8Srv35LJmX2zpQSY09en2j8uTh4kHfZ74LMSpIDctKfMxP3Q28fYWU_6lZYCky3-76rBa-AuEooIWPOkCyV1zYVUILZHdMO5dOW20qM2PYh_onrX9OzanUJXYCuKIT-VToxOb-VaoZYOcOkVyjdI7OY5EEMIzQeFgNna6VJBh7I/https%3A%2F%2Fgithub.com%2Fdcsaorg%2FDCSA-Information-Model%2Fissues%2F350%23issuecomment-1236650654, or unsubscribehttps://secure-web.cisco.com/1pL-sREE-9EQ6BX_DupOr_33nXshmu3kFjb5jt8I3a_69aKkASoWOoertWl0S4s-VrekcVQFR8Btb34N3U3SeLK6fnsK6LfJvy9sF3pZC-FCHnhY2JSZXKDmnvXj1mcMDrEidmeyIOx81nged01-jhV9jsSuqkH4NC4NsYJAp0KPJGBdZ-A_Wiz_MllMNU2TNEdKl8R9-B8MLCkQwdv3lJyESwEYEWZhKXA0F2Vsjby1_rGxoaodOiqhQnhMiu9Fy4Oyp4nqwOequEzELCiLJMAtb3jQCsFyuZRItN8EcrQwGEB5ejTxuD1Tefd0uBd5R/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA242ZKNNA7EZLZXYFXG4V7LV4WQENANCNFSM6AAAAAAQEQQJLY. You are receiving this because you were mentioned.Message ID: @.**@.>>

Disclaimer: CAUTION: This email message and attachments are confidential to Deloitte and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited. If you are an existing client, this email is provided in accordance with the latest terms of engagement which we have agreed with you. Email is inherently subject to delay or fault in transmission, interception, alteration and computer viruses. While Deloitte does employ anti-virus measures, no assurance or guarantee is implied or should be construed that this email message or its attachments are free from computer viruses. Deloitte assumes no responsibility for any such virus or any effects of such a virus on the recipient's systems or data.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited ("DTTL"), its global network of member firms, and their related entities. DTTL (also referred to as "Deloitte Global") and each of its member firms and their affiliated entities are legally separate and independent entities. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. Deloitte Asia Pacific Limited is a company limited by guarantee and a member firm of DTTL. Members of Deloitte Asia Pacific Limited and their related entities, each of which are separate and independent legal entities, provide services from more than 100 cities across the region, including Auckland, Bangkok, Beijing, Hanoi, Hong Kong, Jakarta, Kuala Lumpur, Manila, Melbourne, Osaka, Shanghai, Singapore, Sydney, Taipei and Tokyo.

[HenrikHL]

Glad to help :-) A link to the newest "official" IM: https://dcsa.my.salesforce.com/sfc/p/#2o000000YvHJ/a/7T000000bnvo/id.kB9TVoeYABFV8NwRBQvgVkWXXK7DAuIelpCDw13M I expect a new version 2022.2 will be published within a month. Regarding the linkage between Transport and EquipmentEvent - I think that is a mistake that was fixed. In the newest IM the linkage looks like this: (EquipmentEvent links to TransportCall)

[RickyTangDeloitte]

Hi Henrik,

I am not able to access your link. Could you please check if you can give me access to the shareforce file? Do you know why there are two lines link between transport and transport call?

@.***

Also I have asked another question:

I am not quite get it by reading through its definitions and why it links to Equipment event. Can you please give me an example? Is that for Truck/Train to move the good to the port or from the port to its final destination?

Thank you for your help in advance.

Cheers, Ricky

From: Henrik Helmø Larsen @.> Sent: Tuesday, 6 September 2022 6:54 pm To: dcsaorg/DCSA-Information-Model @.> Cc: Tang, Ricky @.>; Mention @.> Subject: [EXT] Re: [dcsaorg/DCSA-Information-Model] How to link Transport entity to Shipment Event entity? (Issue #350)

Glad to help :-) A link to the newest "official" IM: https://dcsa.my.salesforce.com/sfc/p/#2o000000YvHJ/a/7T000000bnvo/id.kB9TVoeYABFV8NwRBQvgVkWXXK7DAuIelpCDw13M I expect a new version 2022.2 will be published within a month. Regarding the linkage between Transport and EquipmentEvent - I think that is a mistake that was fixed. In the newest IM the linkage looks like this:

(EquipmentEvent links to TransportCall)

— Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1MGzze6mm_9JNReeLZ0sLDAv0qmC-zg5bY3eZ1spBJtySHpoXDUQs-fO86H3r9ZMW1zeWzJoizP8kJ7uayt4G_hk4KneD0jrK6zX1EC1z6oEFu73q7w_LXvmCtpugg1A17nnJNkUAJYsJKBe-0sIbnuDWWRBYZNBIEckuGCGwCTHtfJQJWPWj5sFLa-z4AIpHBn09MAgfMLPMqCPtyuVe6ZK618YQ-FEtd9fkn55vXN6bkGdN2TZl-ayFzsNBZzD053V09XN2YouDykEn6EboSBq0N8cif-dXOOQmI1SprwrykikjQGF6zYIaq8-xlUR9/https%3A%2F%2Fgithub.com%2Fdcsaorg%2FDCSA-Information-Model%2Fissues%2F350%23issuecomment-1237731856, or unsubscribehttps://secure-web.cisco.com/1lZOciNsVtx1Jv4RGM4YN-wIJMNMx-BvOy-Oev9Nmu7dXLAFpkXMQ-LTSh6H3eOfew1i8f8VQwSX1Ks1mkQmc3piAAKr6cXTQKdCaKFFp-MkJ_wZuSRWWfPb_s3UptbOmU7BA8EDkCWtje0JrtE01aq3Cq-M5Y-kss1QlGl2catgd-tRUfDPgMPRmzzPE2rHvt5imBXBJZUmtcqy2rcSmOR4XkL2Su2PmlOIhMmjGddyddV4p0CRb-QLx0_JGOEr41oSfMOLeFAZYwvkcEYgLOqat0nNTXmF90r_jwlWWhvT0K15JZZ1lf3vw9BFtm6VF/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA242ZKLMHTMZVIT54GJGTFDV43TCHANCNFSM6AAAAAAQEQQJLY. You are receiving this because you were mentioned.Message ID: @.**@.>>

Disclaimer: CAUTION: This email message and attachments are confidential to Deloitte and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited. If you are an existing client, this email is provided in accordance with the latest terms of engagement which we have agreed with you. Email is inherently subject to delay or fault in transmission, interception, alteration and computer viruses. While Deloitte does employ anti-virus measures, no assurance or guarantee is implied or should be construed that this email message or its attachments are free from computer viruses. Deloitte assumes no responsibility for any such virus or any effects of such a virus on the recipient's systems or data.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited ("DTTL"), its global network of member firms, and their related entities. DTTL (also referred to as "Deloitte Global") and each of its member firms and their affiliated entities are legally separate and independent entities. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. Deloitte Asia Pacific Limited is a company limited by guarantee and a member firm of DTTL. Members of Deloitte Asia Pacific Limited and their related entities, each of which are separate and independent legal entities, provide services from more than 100 cities across the region, including Auckland, Bangkok, Beijing, Hanoi, Hong Kong, Jakarta, Kuala Lumpur, Manila, Melbourne, Osaka, Shanghai, Singapore, Sydney, Taipei and Tokyo.

[RickyTangDeloitte]

Hi Henrik,

Somehow the link works for me now…

Cheers, Ricky

From: Tang, Ricky Sent: Wednesday, 7 September 2022 1:17 pm To: 'dcsaorg/DCSA-Information-Model' @.>; 'dcsaorg/DCSA-Information-Model' @.> Cc: 'Mention' @.***> Subject: RE: [EXT] Re: [dcsaorg/DCSA-Information-Model] How to link Transport entity to Shipment Event entity? (Issue #350)

Hi Henrik,

I am not able to access your link. Could you please check if you can give me access to the shareforce file? Do you know why there are two lines link between transport and transport call?

@.***

Also I have asked another question:

I am not quite get it by reading through its definitions and why it links to Equipment event. Can you please give me an example? Is that for Truck/Train to move the good to the port or from the port to its final destination?

Thank you for your help in advance.

Cheers, Ricky

From: Henrik Helmø Larsen @.**@.>> Sent: Tuesday, 6 September 2022 6:54 pm To: dcsaorg/DCSA-Information-Model @.**@.>> Cc: Tang, Ricky @.**@.>>; Mention @.**@.>> Subject: [EXT] Re: [dcsaorg/DCSA-Information-Model] How to link Transport entity to Shipment Event entity? (Issue #350)

Glad to help :-) A link to the newest "official" IM: https://dcsa.my.salesforce.com/sfc/p/#2o000000YvHJ/a/7T000000bnvo/id.kB9TVoeYABFV8NwRBQvgVkWXXK7DAuIelpCDw13M I expect a new version 2022.2 will be published within a month. Regarding the linkage between Transport and EquipmentEvent - I think that is a mistake that was fixed. In the newest IM the linkage looks like this:

(EquipmentEvent links to TransportCall)

— Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1MGzze6mm_9JNReeLZ0sLDAv0qmC-zg5bY3eZ1spBJtySHpoXDUQs-fO86H3r9ZMW1zeWzJoizP8kJ7uayt4G_hk4KneD0jrK6zX1EC1z6oEFu73q7w_LXvmCtpugg1A17nnJNkUAJYsJKBe-0sIbnuDWWRBYZNBIEckuGCGwCTHtfJQJWPWj5sFLa-z4AIpHBn09MAgfMLPMqCPtyuVe6ZK618YQ-FEtd9fkn55vXN6bkGdN2TZl-ayFzsNBZzD053V09XN2YouDykEn6EboSBq0N8cif-dXOOQmI1SprwrykikjQGF6zYIaq8-xlUR9/https%3A%2F%2Fgithub.com%2Fdcsaorg%2FDCSA-Information-Model%2Fissues%2F350%23issuecomment-1237731856, or unsubscribehttps://secure-web.cisco.com/1lZOciNsVtx1Jv4RGM4YN-wIJMNMx-BvOy-Oev9Nmu7dXLAFpkXMQ-LTSh6H3eOfew1i8f8VQwSX1Ks1mkQmc3piAAKr6cXTQKdCaKFFp-MkJ_wZuSRWWfPb_s3UptbOmU7BA8EDkCWtje0JrtE01aq3Cq-M5Y-kss1QlGl2catgd-tRUfDPgMPRmzzPE2rHvt5imBXBJZUmtcqy2rcSmOR4XkL2Su2PmlOIhMmjGddyddV4p0CRb-QLx0_JGOEr41oSfMOLeFAZYwvkcEYgLOqat0nNTXmF90r_jwlWWhvT0K15JZZ1lf3vw9BFtm6VF/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA242ZKLMHTMZVIT54GJGTFDV43TCHANCNFSM6AAAAAAQEQQJLY. You are receiving this because you were mentioned.Message ID: @.**@.>>

Disclaimer: CAUTION: This email message and attachments are confidential to Deloitte and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited. If you are an existing client, this email is provided in accordance with the latest terms of engagement which we have agreed with you. Email is inherently subject to delay or fault in transmission, interception, alteration and computer viruses. While Deloitte does employ anti-virus measures, no assurance or guarantee is implied or should be construed that this email message or its attachments are free from computer viruses. Deloitte assumes no responsibility for any such virus or any effects of such a virus on the recipient's systems or data.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited ("DTTL"), its global network of member firms, and their related entities. DTTL (also referred to as "Deloitte Global") and each of its member firms and their affiliated entities are legally separate and independent entities. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. Deloitte Asia Pacific Limited is a company limited by guarantee and a member firm of DTTL. Members of Deloitte Asia Pacific Limited and their related entities, each of which are separate and independent legal entities, provide services from more than 100 cities across the region, including Auckland, Bangkok, Beijing, Hanoi, Hong Kong, Jakarta, Kuala Lumpur, Manila, Melbourne, Osaka, Shanghai, Singapore, Sydney, Taipei and Tokyo.

[HenrikHL]

Somehow the link works for me now…

For future you could also go directly to the dcsa.org website. Here you:

• choose the "Standards" tab
• At the moment Booking and Electronic Bill of Lading are the "newest" - choose any of the two
• Go to the bottom of the page and select the newest "Standards"
• Scroll to the bottom and find the Information Model

Do you know why there are two lines link between transport and transport call?

There are 2 links between Transports and Transport Call because in the Transports there is Load Transport Call and a Discharge Transport Call

I am not quite get it by reading through its definitions and why it links to Equipment event. Can you please give me an example? Is that for Truck/Train to move the good to the port or from the port to its final destination?

The linkage between the Transport Call and Equipment Event is to specify where and in what context something is happening with the container (e.g. Mode of Transport, Voyage ID, Vessel ID, etc) - the model (as it is now) - does not cater for identifying a Truck, Barge og Rail (only the Mode of Transport). I foresee that sometime in the future - Vessel ID will be substituted with Transportation Reference (which in case of a Vessel would be IMO Number, for a Truck it would most likely be license plate, for Rail some kind of rail-identification) The reason why Equipment Event also has an Event Location is because of customs inspection, stuffing and stripping - these events do not happen in a Transport Call context.

[RickyTangDeloitte]

Thank you so much for your detailed explanation! Helps a lot!

Wish you have a lovely day.

Cheers, Ricky

Sent from my iPhone

On 7/09/2022, at 7:06 PM, Henrik Helmø Larsen @.***> wrote:



Somehow the link works for me now…

For future you could also go directly to the dcsa.orghttps://secure-web.cisco.com/1g_-7rAr1K-jgyi9WZ_04Gtvmn35iFpN7fQ3tmB8XtKpxTNnSI_Jj-MMTP-06uzSeWlocAzLFcke49N_n5WdHe26ngMWI8fYtLBI3rrNIKNVOrEtWaYhF1eQD2Pikt2sHAlTr51nftDysXC2zRWwUaKhLllZ7ubk8j7o1ScGitEnMTf6DwTKbHTi297e6vIjczshVpveJNZu5pXV6nZjUPF10CenTHJJU0c3PQ13NjO4RurgZemo1DyEGsmOyS02c7eTL6fGVz9e7GQ35SgJhY-d8mdXw0aaX9syCCZttwgA6y5iB67ffEGffrYa1B9mG/https%3A%2F%2Fdcsa.org%2F website. Here you:

• choose the "Standards" tab
• At the moment Booking and Electronic Bill of Lading are the "newest" - choose any of the two
• Go to the bottom of the page and select the newest "Standards"
• Scroll to the bottom and find the Information Model

Do you know why there are two lines link between transport and transport call?

There are 2 links between Transports and Transport Call because in the Transports there is Load Transport Call and a Discharge Transport Call

I am not quite get it by reading through its definitions and why it links to Equipment event. Can you please give me an example? Is that for Truck/Train to move the good to the port or from the port to its final destination?

The linkage between the Transport Call and Equipment Event is to specify where and in what context something is happening with the container (e.g. Mode of Transport, Voyage ID, Vessel ID, etc) - the model (as it is now) - does not cater for identifying a Truck, Barge og Rail (only the Mode of Transport). I foresee that sometime in the future - Vessel ID will be substituted with Transportation Reference (which in case of a Vessel would be IMO Number, for a Truck it would most likely be license plate, for Rail some kind of rail-identification) The reason why Equipment Event also has an Event Location is because of customs inspection, stuffing and stripping - these events do not happen in a Transport Call context.

— Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1ENILnmchAKWJHSPwlr3zFtEBPqxkRYyIiA5O1Q_YrC-DPJL3DUTOj5hLtcxP6n021f36KaySjyjAm4h9Za3Jz7eyQMH9Ly9ovjjz-8x8hBh-U4YHf3L-FRdpdRQTsde5aXJ81w772OhS34HPFHTImwTfR13itHzmVRmuWJ0pJd816ObfXWMx8nQv8UO8WJsjIxViE2ADpxGJjZQbQPy59ZcTRqtQpw9RNd7PoepjVY28dQcWyWlnlTBDNAyjnMZ_e87oUX1mGnUFL17Wn1uVwWS73I5jXr05-pxcUnwVLIcIxF-kS1QIJmhBBPQ03mmS/https%3A%2F%2Fgithub.com%2Fdcsaorg%2FDCSA-Information-Model%2Fissues%2F350%23issuecomment-1238992687, or unsubscribehttps://secure-web.cisco.com/1twiTUyv-b6dfA_mZ9ZpOwM4L6i3KHP8iurB2Ou5sBmA5wSjQxX2fxXwT6XWL_3fFdp1T1Hwwk_hQTxpOxn32WeCtuRV8ih8Fqdq9ZKzHwiafG9T_I9rhNZhc0WvjLmP8eZKcBKpXaCtxQezIZZWlt5xq04qcwcGbzfYRupdXAFsgc2HrtC9oGApM2lMSgEuBuAOyTT6qQlagCA5Y-FXszv05XIq-K6F7J6qhADrkjPgiHmDHEis_bOCcl7DtIZivYyScb7mZ_CzIHrOXRD6KJwr10ls-1IsXGUTW0S9KTcyDcz7NPuIoZtTCmK-TOhoC/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA242ZKIOAW75WNSTA36RDQTV5A5F5ANCNFSM6AAAAAAQEQQJLY. You are receiving this because you were mentioned.Message ID: @.***>

Disclaimer: CAUTION: This email message and attachments are confidential to Deloitte and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited. If you are an existing client, this email is provided in accordance with the latest terms of engagement which we have agreed with you. Email is inherently subject to delay or fault in transmission, interception, alteration and computer viruses. While Deloitte does employ anti-virus measures, no assurance or guarantee is implied or should be construed that this email message or its attachments are free from computer viruses. Deloitte assumes no responsibility for any such virus or any effects of such a virus on the recipient's systems or data.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited ("DTTL"), its global network of member firms, and their related entities. DTTL (also referred to as "Deloitte Global") and each of its member firms and their affiliated entities are legally separate and independent entities. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. Deloitte Asia Pacific Limited is a company limited by guarantee and a member firm of DTTL. Members of Deloitte Asia Pacific Limited and their related entities, each of which are separate and independent legal entities, provide services from more than 100 cities across the region, including Auckland, Bangkok, Beijing, Hanoi, Hong Kong, Jakarta, Kuala Lumpur, Manila, Melbourne, Osaka, Shanghai, Singapore, Sydney, Taipei and Tokyo.

[RickyTangDeloitte]

Hi Henrik,

We have more questions come up when reviewing the latest 2202.1 information model.

1. Why there are two relationships between Location and Facility? What is the purpose of the link between UN location and Facility? @.***

2. Why there is a link between location and operation event, not facility and operation event? In another word, why equipment event links to facility, not location? Looks like it is not consistent. @.***

3. What is the difference between requested equipment equipment and Utilized Transport equipment? Looks like it's duplicated. They both linked to shipment and equipment.

@.***

Really appreciate your time and answer in advance.

Cheers, Ricky

From: Henrik Helmø Larsen @.> Sent: Wednesday, 7 September 2022 7:06 pm To: dcsaorg/DCSA-Information-Model @.> Cc: Tang, Ricky @.>; Mention @.> Subject: [EXT] Re: [dcsaorg/DCSA-Information-Model] How to link Transport entity to Shipment Event entity? (Issue #350)

Somehow the link works for me now…

For future you could also go directly to the dcsa.orghttps://secure-web.cisco.com/1g_-7rAr1K-jgyi9WZ_04Gtvmn35iFpN7fQ3tmB8XtKpxTNnSI_Jj-MMTP-06uzSeWlocAzLFcke49N_n5WdHe26ngMWI8fYtLBI3rrNIKNVOrEtWaYhF1eQD2Pikt2sHAlTr51nftDysXC2zRWwUaKhLllZ7ubk8j7o1ScGitEnMTf6DwTKbHTi297e6vIjczshVpveJNZu5pXV6nZjUPF10CenTHJJU0c3PQ13NjO4RurgZemo1DyEGsmOyS02c7eTL6fGVz9e7GQ35SgJhY-d8mdXw0aaX9syCCZttwgA6y5iB67ffEGffrYa1B9mG/https%3A%2F%2Fdcsa.org%2F website. Here you:

• choose the "Standards" tab
• At the moment Booking and Electronic Bill of Lading are the "newest" - choose any of the two
• Go to the bottom of the page and select the newest "Standards"
• Scroll to the bottom and find the Information Model

Do you know why there are two lines link between transport and transport call?

There are 2 links between Transports and Transport Call because in the Transports there is Load Transport Call and a Discharge Transport Call

I am not quite get it by reading through its definitions and why it links to Equipment event. Can you please give me an example? Is that for Truck/Train to move the good to the port or from the port to its final destination?

The linkage between the Transport Call and Equipment Event is to specify where and in what context something is happening with the container (e.g. Mode of Transport, Voyage ID, Vessel ID, etc) - the model (as it is now) - does not cater for identifying a Truck, Barge og Rail (only the Mode of Transport). I foresee that sometime in the future - Vessel ID will be substituted with Transportation Reference (which in case of a Vessel would be IMO Number, for a Truck it would most likely be license plate, for Rail some kind of rail-identification) The reason why Equipment Event also has an Event Location is because of customs inspection, stuffing and stripping - these events do not happen in a Transport Call context.

— Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1ENILnmchAKWJHSPwlr3zFtEBPqxkRYyIiA5O1Q_YrC-DPJL3DUTOj5hLtcxP6n021f36KaySjyjAm4h9Za3Jz7eyQMH9Ly9ovjjz-8x8hBh-U4YHf3L-FRdpdRQTsde5aXJ81w772OhS34HPFHTImwTfR13itHzmVRmuWJ0pJd816ObfXWMx8nQv8UO8WJsjIxViE2ADpxGJjZQbQPy59ZcTRqtQpw9RNd7PoepjVY28dQcWyWlnlTBDNAyjnMZ_e87oUX1mGnUFL17Wn1uVwWS73I5jXr05-pxcUnwVLIcIxF-kS1QIJmhBBPQ03mmS/https%3A%2F%2Fgithub.com%2Fdcsaorg%2FDCSA-Information-Model%2Fissues%2F350%23issuecomment-1238992687, or unsubscribehttps://secure-web.cisco.com/1twiTUyv-b6dfA_mZ9ZpOwM4L6i3KHP8iurB2Ou5sBmA5wSjQxX2fxXwT6XWL_3fFdp1T1Hwwk_hQTxpOxn32WeCtuRV8ih8Fqdq9ZKzHwiafG9T_I9rhNZhc0WvjLmP8eZKcBKpXaCtxQezIZZWlt5xq04qcwcGbzfYRupdXAFsgc2HrtC9oGApM2lMSgEuBuAOyTT6qQlagCA5Y-FXszv05XIq-K6F7J6qhADrkjPgiHmDHEis_bOCcl7DtIZivYyScb7mZ_CzIHrOXRD6KJwr10ls-1IsXGUTW0S9KTcyDcz7NPuIoZtTCmK-TOhoC/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA242ZKIOAW75WNSTA36RDQTV5A5F5ANCNFSM6AAAAAAQEQQJLY. You are receiving this because you were mentioned.Message ID: @.**@.>>

Disclaimer: CAUTION: This email message and attachments are confidential to Deloitte and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited. If you are an existing client, this email is provided in accordance with the latest terms of engagement which we have agreed with you. Email is inherently subject to delay or fault in transmission, interception, alteration and computer viruses. While Deloitte does employ anti-virus measures, no assurance or guarantee is implied or should be construed that this email message or its attachments are free from computer viruses. Deloitte assumes no responsibility for any such virus or any effects of such a virus on the recipient's systems or data.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited ("DTTL"), its global network of member firms, and their related entities. DTTL (also referred to as "Deloitte Global") and each of its member firms and their affiliated entities are legally separate and independent entities. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. Deloitte Asia Pacific Limited is a company limited by guarantee and a member firm of DTTL. Members of Deloitte Asia Pacific Limited and their related entities, each of which are separate and independent legal entities, provide services from more than 100 cities across the region, including Auckland, Bangkok, Beijing, Hanoi, Hong Kong, Jakarta, Kuala Lumpur, Manila, Melbourne, Osaka, Shanghai, Singapore, Sydney, Taipei and Tokyo.

[HenrikHL]

Hi again @RickyTangDeloitte,

Sorry for this late reply - some urgent things came up...

1. Why there are two relationships between Location and Facility? What is the purpose of the link between UN location and Facility?

When you write two relations you mean one in each direction? There is a link from Location -> Facility because it is possible to express a location as the location of where a Facility i located. There is a link from Facility -> Location because not all Facilities have BIC or SMDG codes and by linking a Facility to a Location it is possible to express where the Facility is located (could be via e.g. an address) The reason for linking Facility to UNLocationCode is because we split the UNLocationCode from the SMDG code in the facility. The Facility Code = UNLocationCode + SMDGCode

2. Why there is a link between location and operation event, not facility and operation event? In another word, why equipment event links to facility, not location? Looks like it is not consistent.

The link between Location and OperationsEvent is to express e.g. Anchorage (where to anchor a vessel) or Vessel-position. There is an indirect link from OperationsEvent -> Facility via the Location entity (a location can be expressed using a Facility) Regarding the link between facility and EquipmentEvent - I think you have found a bug. In the entities there is no linkage between the two - the line does exist in the overall image and in the T&T image overview. I will make sure this is updated in next version - thank you!

3. What is the difference between requested equipment equipment and Utilized Transport equipment? Looks like it's duplicated. They both linked to shipment and equipment.

Requested equipment is done during the Booking phase and is the "shipper" requesting the carrier to provide some containers. At this point in time the equipmentReference (container number) might not be known (in rare cases they are known and therefore we have a link to Equipment). During the ShippingInstruction phase - the Shipper then Stuffs the containers - this is the UtilizedTransportEquipment. Here the Shipper provides information about which goods go into which container - at this stage the equipmentReference is mandatory plus it has much more information about container content

[HenrikHL]

@RickyTangDeloitte - FYI here is a new updated "overall" image:

I will send a link to newest IM document as soon as I have it...

[RickyTangDeloitte]

Hi Henrik,

Thank you so much for this updated image. Really helps a lot!

Wish you have a good weekend!

Cheers, Ricky

Sent from my iPhone

On 16/09/2022, at 10:45 PM, Henrik Helmø Larsen @.***> wrote:



@RickyTangDeloittehttps://secure-web.cisco.com/1Hk18El_2--ZiXfBdo9iSp_FpZnRpZsu7-i9YgvEgw19ny31F0z1rl80Aw4hgJdzWvCSAFDKVSNlkLEVviUcU2Xcb7dLHsUwHPUlnu-x6TI6rAYHoGGNVGsEYKTHSf3-aGsHpXQbl-4zKLHOfmgZaThk78JJiiskUvqIirutWU5HmHP5GMFOZWIERKpOXxJtII2HE_MQpcv3p68bu-x08D61ORaCEZQu1VUrzFNL0uvOZ0RTQivpy5XLL6JTyl9y21ysDLQel3d-Agv4upL0LG2jtxIa4w5vuHEj7Z-whs-67dUhGG8vrQat2PPl07LZe/https%3A%2F%2Fgithub.com%2FRickyTangDeloitte - FYI here is a new updated "overall" image: [overall]https://secure-web.cisco.com/12S0kyw0BZOEK1J_6A9AR5hFYsNSVLznHsuQ2n9mMiRpetXy7-MGQ5sjeoSzc5WvC1oo5ZVfXtSS1YXIOZc3Y4Mb5apv5mSvxzUzWlOic4ULeoIy8ceblr65rNzZTMsPyvEjtmKUw6KJ-_0CWCmSpmEIkZvvoF__rR-W5eZC4CV0A4Jb5x4Ru6br7OlHeFMfQI8Fd2ji7OwUJID4mOjDO6PRyu2x6LZ_KyFshNCHZu2qmN-Ql8N9xYtrrsMfVOlAswPAesp2IBwukzlVGJcwuXw82f6vzyGfawyjhwxsUcyqkxrZPgapXIf8BZM7VsgVL/https%3A%2F%2Fuser-images.githubusercontent.com%2F3489388%2F190621684-f383980f-48cc-4ec9-b717-e087e03e484d.png

I will send a link to newest IM document as soon as I have it...

— Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1VJWCdtWwDRzpNHeMlBMVO-r2HMcf4sbK29UjYptVDjLbNVS161sOkd6IcBu7_LCeff8jlCcKF9TSuOk75OX6ue3XtOh4sWRy6ztoQohiYFpZIUT05e7OV1ByuXjlQW2bx6lzbciwUR-qkJsYiMzx07w9UpOCHsnVfa-e42H_-OAEgEyX9Hbxg9YvaHGD4ZWRZKCWtSiq9ZcUS5mbXPVGhqK-FOebi5zgBZwJ0L6nAoGelYch4n2Jrocx7qonsI3D8yHRpLg00z8eYwtgmuSJhIsKqT75drimyfxOgHsSry9Q0ARmFh9_6EdVgBI6NPgl/https%3A%2F%2Fgithub.com%2Fdcsaorg%2FDCSA-Information-Model%2Fissues%2F350%23issuecomment-1249213693, or unsubscribehttps://secure-web.cisco.com/13JIIZiLlZdMUB61jj0Yw3jP1P0VJlDZwc6g6yAumLgDJtqzBDGb8HDv67KxB07pqzhPejWiM9-gepb-DejbjcVPQPW3uNxgXvE4el6SjciiBgiOBH10CTG23q8j6pciFlky3dsqHaB2bXIo6_A_6FqMsoXW8ggCl0M54VLRu9fwzcwq0YjMkZ4XH7yX0B-3dAV5aF2UeulMgXAPUNX2FOCwFZ7FobiO_3KZRTbjhLX4088-UKtHRxLnPc9D_cHNGLLnlvJh0XTW7xrNh7yjp82PwheH_mka3MDiEuA-hKNxI-g0gnG7LhvR3Dov1gaX0/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA242ZKPZB3DBTHA77HU5CR3V6RFRPANCNFSM6AAAAAAQEQQJLY. You are receiving this because you were mentioned.Message ID: @.***>

Disclaimer: CAUTION: This email message and attachments are confidential to Deloitte and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited. If you are an existing client, this email is provided in accordance with the latest terms of engagement which we have agreed with you. Email is inherently subject to delay or fault in transmission, interception, alteration and computer viruses. While Deloitte does employ anti-virus measures, no assurance or guarantee is implied or should be construed that this email message or its attachments are free from computer viruses. Deloitte assumes no responsibility for any such virus or any effects of such a virus on the recipient's systems or data.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited ("DTTL"), its global network of member firms, and their related entities. DTTL (also referred to as "Deloitte Global") and each of its member firms and their affiliated entities are legally separate and independent entities. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. Deloitte Asia Pacific Limited is a company limited by guarantee and a member firm of DTTL. Members of Deloitte Asia Pacific Limited and their related entities, each of which are separate and independent legal entities, provide services from more than 100 cities across the region, including Auckland, Bangkok, Beijing, Hanoi, Hong Kong, Jakarta, Kuala Lumpur, Manila, Melbourne, Osaka, Shanghai, Singapore, Sydney, Taipei and Tokyo.

[HenrikHL]

Link to newest IM PDF: https://dcsa.my.salesforce.com/sfc/p/#2o000000YvHJ/a/7T0000005DYt/jyzttKZQS1vxdd6dAFkWYi4F5RMiz38EsGwCBGhp1ic (the pdf fitting the IM image above ;-) )