User story | Description |
---|---|
“As a shipper I want to update the number of packages in the current Shipping Instructions.“ | The shipper submits an update of the Shipping Instructions with Bill of Lading use case “UC3: Submit updated Shipping Instructions”. |
“As a shipper I want to modify a Reefer attribute in the Draft Transport Document.“ | Reefer attributes can only be modified as part of the Booking process. Therefore, the shipper can request an update to the Draft Transport Document by initiating a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. After approving the amendment with Booking use case “UC8: Process amendment to confirmed booking”, the carrier publishes an updated Draft Transport Document with Bill of Lading use case “UC6: Publish Draft Transport Document”. |
“As a shipper I want to modify a Dangerous Goods attribute in the Draft Transport Document.“ | Dangerous Goods attributes can only be modified as part of the Booking process. Therefore, the shipper can request an update to the Draft Transport Document by initiating a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. After approving the amendment with Booking use case “UC8: Process amendment to confirmed booking”, the carrier publishes an updated Draft Transport Document with Bill of Lading use case “UC6: Publish Draft Transport Document”. |
“As a shipper I want to modify a seal number in the Draft Transport Document.“ | The shipper cannot directly modify the Draft Transport Document. Instead, the shipper requests a Shipping Instructions update with Bill of Lading use case “UC3: Submit updated Shipping Instructions”. After approving the update with Bill of Lading use case “UC4: Process updated Shipping Instructions”, the carrier publishes an amended Draft Transport Document reflecting the new information with Bill of Lading use case “UC6: Publish Draft Transport Document”. |
“As a shipper I want to modify a Reefer attribute in the Transport Document (after issuance).“ | Reefer attributes can only be modified as part of the Booking process. Therefore, the shipper can request an amendment to the Transport Document by initiating a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. Depending on the type of Transport Document, different paths are followed: Before or after the carrier has approved the amendment request with Booking use case “UC8: Process amendment to confirmed booking”, the shipper must submit a request to surrender the eBL for amendment back to the carrier (via the eBL platform from which it was issued) with Bill of Lading use case “UC9: Request surrender Transport Document (amendment)”. After both the amendment request (via the Booking use case UC8) and the eBL surrender request are approved with Bill of Lading use case “UC10: Process Transport Document surrender request (amendment)”, the carrier voids the existing eBL and issues an amended eBL reflecting the new information with Bill of Lading use case “UC11: Void original Transport Document and issue amended Transport Document”. The amendment of a physical Bill of Lading happens out of band from the DCSA standard API (e.g. email, phone, mail). |
“As a shipper I want to modify a Dangerous Goods attribute in the Transport Document (after issuance).“ | Dangerous Goods attributes can only be modified as part of the Booking process. Therefore, the shipper can request an amendment to the Transport Document by initiating a booking amendment with Booking use case “UC7: Request amendment to confirmed booking”. Depending on the type of Transport Document, different paths are followed: After both the amendment request (via the Booking use case UC8) and the eBL surrender request are approved with Bill of Lading use case “UC10: Process Transport Document surrender request (amendment)”, the carrier voids the existing eBL and issues an amended eBL reflecting the new information with Bill of Lading use case “UC11: Void original Transport Document and issue amended Transport Document”. |
“As a shipper I want to modify the HS code in the Transport Document (after issuance).“ | The shipper cannot directly modify the Transport Document. Instead, the shipper requests a Shipping Instructions update with Bill of Lading use case “UC3: Submit updated Shipping Instructions”. Depending on the type of Transport Document, different paths are followed: After both the amendment request (via Bill of Lading use case UC4) and the eBL surrender request are approved with Bill of Lading use case “UC10: Process Transport Document surrender request (amendment)”, the carrier voids the existing eBL and issues an amended eBL reflecting the new information with Bill of Lading use case “UC11: Void original Transport Document and issue amended Transport Document”. |