mirror of
https://github.com/Tria-plc/edr-platform.git
synced 2026-08-26 18:42:49 +00:00
1139 lines
53 KiB
Plaintext
1139 lines
53 KiB
Plaintext
sumptions:
|
||
|
||
The customer has finalized the contract signing procedure with Marketing Team;
|
||
The customer requested a customs clearing service (Global Logistics service);
|
||
The customer decided to proceed with the shipment operation
|
||
|
||
Global Logistics workflow Unimodal Export
|
||
US 01: Operation Handover & Contract Verification(if the customer select freight transport with custom clearance)
|
||
|
||
As a Global Logistics Staff,
|
||
I want to evaluate verified contract validity in a secure, read-only interface
|
||
So that I can seamlessly transition a validated business agreement into active execution without exposing agreed financial rates or core contract terms to unapproved structural modifications.
|
||
Acceptance Criteria
|
||
AC 1: Read-Only Contract Viewer
|
||
When an operation is initiated from the customer, signed contracts with the Marketing team will be visible to the Global Logistics team, the system must display the agreed contract details (eg: validity dates, service scopes).
|
||
The system must enforce a strict Read-Only / Deny Edit permission set for all Global Logistics roles on these contractual parameters.
|
||
US02: Initial Station Assignment & Communication Routing
|
||
|
||
As a Global Logistics Customs staff;
|
||
I want the system to automatically parse the origin departure station ( origin station), and route the file directly to the appropriate localized global logistics team,
|
||
So that a dedicated staff can be assigned;
|
||
Acceptance Criteria
|
||
AC 1: Station Dropdown Selection
|
||
The system must present a mandatory station dropdown populated with valid EDR terminals (e.g., Sebeta, Endode, Dire Dawa, Djibouti Marine Port) to define the operational point of contact.
|
||
AC 2: Location-Based Routing Engine
|
||
When the customer triggers an operational action, the system must parse the departure location value and route the task directly to the queue of that specific regional station's department.
|
||
AC 3: Resource Assignment Control
|
||
The system must provide local Station managers with a user assignment dropdown, allowing them to bind a specific staff user ID to the unique MSRN record, updating the status to Staff Assigned.
|
||
US 03- Consignment Documentation Submission
|
||
As a customer,
|
||
I want the system to dynamically request and collect the necessary consignment documentation from the customer for export shipments.
|
||
So that the assigned staff can validate compliance and initiate the clearance process seamlessly.
|
||
AND
|
||
As a Global Logistics Djibouti Staff;
|
||
I want to retrieve the necessary documents for the system
|
||
So that Release Order can be recovered from the carrier
|
||
Acceptance Criteria
|
||
AC 1: Export Document Slots
|
||
If the shipment type is selected as Export, the customer portal must display mandatory upload fields for:
|
||
Booking Confirmation
|
||
Shipping Instructions
|
||
Verified Gross Mass (VGM)
|
||
Railway Bill (Train Waybill)
|
||
Important Export documents for clearance:Commercial Invoice, Packing List, Bank Permit, export License, and Delegation Letter/Power of Attorney
|
||
Export Commodity-Specific Integration Logic
|
||
Coffee: Requires Quality Certificate and Vertical Integration Document (both issued by the Ethiopian Coffee and Tea Authority).
|
||
Teff / Beans: Requires Trade Integration Letter and Permit Letter (Ministry of Agriculture).
|
||
Depending on the Items exported Supporting government regulatory body documents may be required.
|
||
Regional Cross-Border Operations Loop (For export process only)
|
||
The system must provide a dedicated, secure upload slot for the Djibouti Global Logistics Team to attach the collected ocean carrier Release Order.
|
||
Uploading this document must automatically update permissions, making it visible to the Ethiopian Global Logistics team and the customer to proceed with the customs clearance process.
|
||
AC 2: Notification Engine
|
||
Upon successful document upload by the customer, the system must trigger an automated status alert to the designated Global Logistics staff to begin the document review process.
|
||
US04: Document Compliance Management & Border Clearance Validation
|
||
As the assigned Customs documentation compliance staff;
|
||
I want to validate compliance of commercial files and commodity specific regulatory certificates;
|
||
So that I can approve national customs standards are fully met before proceeding with the entry process.
|
||
But this should allow me to revert any query back to the customer on a specific document so that an amendment can be made.
|
||
Acceptance Criteria
|
||
AC 1: Compliance Verification Workflow
|
||
When a customer submits their documents, the shipment status must automatically change to "Pending Document Review", and the assigned staff must receive a system notification.
|
||
The document compliance management staff must have a dedicated workspace to view, download, and check the validity of each uploaded file against customs rules and regulations.
|
||
The system must require the staff to explicitly mark each individual document as either "Approved" or "Queried" before they can move the overall shipment to the next stage of the entry process.
|
||
The system must allow document compliance staff to select a specific document slot (e.g., Commercial Invoice) and launch a query dialog box.
|
||
AC 2: Query & Correction Loop (Reversion Process)
|
||
If any document fails compliance checks, the staff must be able to flag that specific document and input a detailed, mandatory free-text reason explaining the error or required correction.
|
||
Upon submitting a query, the system must change the shipment status to "Action Required: Documentation Amendment" and instantly push a notification to the customer via the Customer Portal.
|
||
The Customer Portal must unlock only the specific queried document slots for re-upload, keeping previously approved files locked to prevent accidental changes.
|
||
When the customer resubmits the corrected documents, the system must log a new version history of the file and alert the compliance staff to reevaluate.
|
||
AC 3: Gatekeeping Logic
|
||
The system must strictly block the staff from proceeding to the customs entry creation until 100% of the mandatory and commodity specific documents are marked as "Approved".
|
||
US 05: Customs Clearance Document Injection- in Ethiopia side
|
||
As a Global logistics staff,
|
||
Once the Customs document verification is finalized and export customs entry process is conducted on the external customs portal,
|
||
I want the system to allow a slot where Customs entry documents are attached and also visible to the customer on the respective portal.
|
||
Acceptance Criteria
|
||
The system must provide dedicated slots for the final processed operational Customs forms: EX3 (Export Document), EX8 (Export Transit Document), Export Release, and T1 (Transport Document)
|
||
When the EX3 and EX8 Documents are uploaded, Declared milestone should automatically triggered on the system
|
||
When the export release and Transport documents (T1) are uploaded, the milestone Export Customs Clearance Process Finalized must automatically transition to completion.
|
||
US 06: Payment settlement and Wagon allocation request- Operational in parallel with US05
|
||
As a Global Logistics Staff;
|
||
I want to Request for Wagon to load the export shipment on behalf of the customer
|
||
So that the customer can settle the payment and proceed with loading the shipment on train
|
||
Acceptance Criteria
|
||
The system must allow the Global Logistics team to request for Wagon to load the shipment to the operations team, the status will be ‘Wagon Requested’
|
||
Operations team will validate the documents and Proceed to generating PNR for payment and status will show Pending payment
|
||
Once Payment is settled in by the customer the status will change to Payment settled
|
||
Once the status shows payment settled, Operations team will proceed with wagon allocation and status will change to Wagon allocated
|
||
US07: Cargo Acceptance and Loading on Train
|
||
As an Operation Staff ,
|
||
I want to cross check and validate the correct shipment has arrived in the warehouse (container number, quantity if shipment is bulk , truck plate number )
|
||
Accepting criteria
|
||
The warehouse and terminal team should trigger time that the cargo arrived and received in the system ‘cargo arrived’
|
||
The operation team should trigger cargo ready for loading and loaded milestones in the system ‘ready for loading’ and once the consignment is ‘loaded’
|
||
The Global Logistics team must upload the transport document T1 as shown in US05.
|
||
Each milestone should also reflect on the Global Logistics window and customer portal for each specific order.
|
||
US08: Train Depart to Djibouti
|
||
As Port and terminal staff;
|
||
I want to confirm the train number and wagon number at departure (Marshalling document)
|
||
So that the status of the shipment can be changed from loaded to departed.
|
||
Accepting criteria
|
||
The system shall use the train number and wagon number from wagon allocation stage and update the milestone ‘Departed’
|
||
The system shall notify the departure time, Estimated arrival time and send a notification to Global Logistics Ethiopia and Djibouti team, Marketing and Business Development team and the customer.
|
||
The system shall generate a load list that contains wagon Number, Train number, customer name and ID, container number. Here the load list should match which container is loaded on which wagon number and should be visible to all departments for downloading and internal use.
|
||
US 09 : Inter-Regional cargo transfer and handover- Djibouti GL
|
||
|
||
As a Djibouti Global Logistics Staff,
|
||
Upon train departure from Ethiopia, the task for cargo handling and offloading to the container yard should automatically be under the custody of GL Djibouti Team.
|
||
|
||
Acceptance Criteria
|
||
AC 1: Operational Phase Handoff Trigger
|
||
When the milestone Departed is triggered from the Ethiopian side, the system must automatically execute a role transfer, setting the primary owner to Global Logistics Djibouti and assigning a read-only copy of the data packet to the Ethiopian origin office.
|
||
AC 2: Asymmetric Milestone Notifications
|
||
Upon train departure execution, the system must distribute tailored data packets automatically:
|
||
Global Logistics Ethiopia: Updates Actual time of Departure (ATD)
|
||
Global Logistics Djibouti: Receives Actual time of Arrival (ATA)
|
||
AC 3: Process Finalization stage
|
||
Global Logistics Djibouti: After retrieving the T1 and the documents from the shipment and in collaboration with the Djibouti customs clearing agent, Gatepass will be processed and the status of the shipment will show Gatpass granted
|
||
Global Logistics Djibouti: Updates the shipment is offloaded at Container yard in Djibouti. ‘Offloaded’. So that the Ethiopian GL and customer can see the arrival time.
|
||
Finance Management Sub-Module
|
||
US10: Post-Transit Miscellaneous Cost Settlement & Finance Cycle Closure
|
||
As a Corporate Finance,
|
||
I want to insert delayed third-party maritime bills into the active payables ledger after cargo delivery
|
||
So that I can lock the file from further adjustments, accurately calculate final profits, and conclude the operational billing lifecycle.
|
||
Acceptance Criteria
|
||
AC 1: Post-Operational AP Ingestion
|
||
The system must allow users to add additional rows to the Accounts Payable (AP) ledger for third-party charges (e.g., Djibouti Port Handling, Subcontracted Service Invoices) even while the invoice lifecycle status sits at Temporarily Closed.
|
||
AC 2: Permanent Accounting Closure Trigger
|
||
Once all outstanding third-party invoices from the Djibouti operations are entered and matched, the user must be able to switch the billing cycle state to Permanently Closed.
|
||
This action locks the financial record against any further adjustments or cost line additions.
|
||
Export Documents
|
||
No
|
||
Customer Uploading documents
|
||
Global Logistics Uploading Documents
|
||
Remark
|
||
1
|
||
Booking Confirmation*
|
||
Release Order
|
||
|
||
|
||
2
|
||
Verified Gross Mass (VGM)*
|
||
Export declaration documents
|
||
|
||
|
||
3
|
||
Shipping Instruction (SI)*
|
||
Export Release
|
||
|
||
|
||
4
|
||
Train waybill*
|
||
T1 (Transport document)
|
||
|
||
|
||
5
|
||
Commercial Invoice*
|
||
Full in Interchange*
|
||
|
||
|
||
6
|
||
Packing List*
|
||
Final Declaration*
|
||
|
||
|
||
7
|
||
Bank Permit*
|
||
|
||
|
||
|
||
|
||
8
|
||
Sales Contract*
|
||
|
||
|
||
|
||
|
||
9
|
||
Power of Attorney (POA)*
|
||
|
||
|
||
|
||
|
||
10
|
||
Export License*
|
||
|
||
|
||
|
||
|
||
|
||
*Mandatory documents
|
||
|
||
|
||
|
||
Milestone updates for Export Shipments
|
||
No
|
||
Important Milestones
|
||
Responsible departments
|
||
Milestones triggered by document upload
|
||
Reamark
|
||
1
|
||
Export Documents Uploaded
|
||
Customer
|
||
No
|
||
|
||
|
||
2
|
||
Pending Document Review
|
||
Global Logistics-ET
|
||
Yes
|
||
Once all documents are uploaded from customer side
|
||
|
||
|
||
3
|
||
Documents Approved
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
4
|
||
Release Order Secured
|
||
Global Logistics-Djibout
|
||
Yes
|
||
Once Uploaded by the Djibouti team
|
||
5
|
||
Under Customs Clearance
|
||
Global Logistics- ET
|
||
No
|
||
|
||
|
||
6
|
||
Declared
|
||
Global Logistics-ET
|
||
Yes
|
||
Once the export clearance documents are uploaded
|
||
7
|
||
Export Released
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
8
|
||
Wagon Requested
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
9
|
||
Pending Payment
|
||
|
||
|
||
|
||
|
||
|
||
|
||
10
|
||
Payment settled
|
||
Customer
|
||
Yes
|
||
When the PNR due amount is settled
|
||
11
|
||
Wagon allocated
|
||
Operations department
|
||
No
|
||
|
||
|
||
12
|
||
Cargo arrived
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
13
|
||
Ready for loading
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
14
|
||
Loaded
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
15
|
||
Departed to Djibouti
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
16
|
||
Arrived at Djibouti
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
17
|
||
Gatepass granted
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
18
|
||
offloaded
|
||
|
||
|
||
Yes
|
||
When Full-in interchange is uploaded
|
||
|
||
|
||
Global Logistics workflow Unimodal Import
|
||
US 01: Operation Handover & Contract Verification (if the customer select freight transport with custom clearance)
|
||
|
||
As a Global Logistics Staff,
|
||
I want to evaluate verified contract validity in a secure, read-only interface
|
||
So that I can seamlessly transition a validated business agreement into active execution without exposing agreed financial rates or core contract terms to unapproved structural modifications.
|
||
Acceptance Criteria
|
||
AC 1: Read-Only Contract Viewer
|
||
When an operation is initiated from the customer, signed contracts with the Marketing team will be visible to the Global Logistics team, the system must display the agreed contract details (eg: validity dates, service scopes).
|
||
The system must enforce a strict Read-Only / Deny Edit permission set for all Global Logistics roles on these contractual parameters.
|
||
US 02- Consignment Documentation Submission- Import
|
||
As a Customer,
|
||
I want the system to dynamically request and collect the necessary consignment documentation from the customer for import shipment processing.
|
||
So that the Global Logistics staff can validate the cross border compliance and initiate the clearance process seamlessly.
|
||
Acceptance Criteria
|
||
AC 1: Import Document Logic (OBL vs. SWB)
|
||
The system must evaluate the Bill of Lading (B/L) type:
|
||
Original Bill of Lading (OBL): The system must display a notification prompting the customer to physically submit two (2) endorsed hard copies to the Djibouti Global Logistics Djibouti office. And upload an endorsed copy of the OBL. (Shipping address will be provided)
|
||
If Sea Waybill (SWB): The system must activate a softcopy attachment slot allowing the customer to upload the endorsed digital B/L, alongside a free-text notes field for communication with the Djibouti team.
|
||
Import Framework: Commercial Invoice, Packing List, Certificate of Origin (COO), Bill of Lading (OBL/SWB), Bank Permit/Franco Valuta, Import License, and Delegation Letter/Power of Attorney.
|
||
Depending on the import shipment type, regulatory documents may be requested so there should be a slot where customers can upload additional documents as required.
|
||
AC 2: Notification Engine
|
||
Upon successful document upload by the customer, the system must trigger an automated status alert to the designated Global Logistics staff to begin the document review process.
|
||
US03: Document Compliance Management & Border Clearance Validation
|
||
As a Customs documentation compliance staff,
|
||
I want to mandate and validate compliance of commercial files and commodity specific regulatory certificates through organized secure upload fields,
|
||
So that I can verify customs standards are fully met prior to proceeding with the entry process.
|
||
But this should allow me to revert any query back to the customer on the specific documents so that an amendment can be made.
|
||
Acceptance Criteria
|
||
AC 1: Compliance Verification Workflow
|
||
When a customer submits their documents, the shipment status must automatically change to "Pending Compliance Review", and the assigned staff must receive a system notification.
|
||
The compliance management staff must have a dedicated workspace to view, download, and check the validity of each uploaded file against customs rules and regulations.
|
||
The system must require the staff to explicitly mark each individual document as either "Approved" or "Queried" before they can move the overall shipment to the next stage of the entry process.
|
||
The system must allow users to select a specific document slot (e.g., Commercial Invoice) and launch a query dialog box.
|
||
|
||
AC 2: Query & Correction Loop (Reversion Process)
|
||
If any document fails compliance checks, the staff must be able to flag that specific document and input a detailed, mandatory free-text reason explaining the error or required correction.
|
||
Upon submitting a query, the system must change the shipment status to "Action Required: Documentation Amendment" and instantly push a notification to the customer via the Customer Portal.
|
||
The Customer Portal must unlock only the specific queried document slots for re-upload and amendment, keeping previously approved files locked to prevent accidental changes.
|
||
When the customer resubmits the corrected documents, the system must log a new version history of the file and alert the compliance staff to reevaluate.
|
||
AC 3: Gatekeeping Logic
|
||
The system must strictly block the staff from proceeding to the customs entry creation or wagon allocation phase until 100% of the mandatory and commodity specific documents are marked as "Approved".
|
||
US 04: Customs Clearance Document Injection- in Ethiopia side
|
||
As a Global logistics staff,
|
||
Once the Customs document verification and entry process is finalized on the external customs portal,
|
||
I want the system to allow a slot where Customs entry documents are attached and also visible to the customer on the portal.
|
||
Acceptance Criteria
|
||
The system must provide dedicated slots for the final processed operational forms: IM4 (Permanent Import Document), IM5 (Temporary Import Document),
|
||
If there are any duties and taxes to be settled, The Global Logistics team will send the amount, Declaration Serial number and automatic notification to the customer will be sent to the customer. Here there should be a spot where the Customer can upload the payment slip from its portal and same will reflect and notify the Global Logistics team ‘Duties and taxes settled’
|
||
There should be a slot where the Transit permit system screenshot can be uploaded in JPG format.
|
||
US 05: Customs Clearance Document Injection- in Djibouti side
|
||
As a Global Logistics Djibouti staff;
|
||
I want to update the Delivery order processing and port invoices are paid
|
||
So that further port handling is processed.
|
||
Acceptance Criteria
|
||
The Djibouti Global Logistics team receive Delivery Order DO once the invoice is paid by the Djibouti clearing Agent, here they will update ‘DO Received’
|
||
US 06: Payment settlement and Wagon allocation request- Operational in parallel with US05
|
||
As a Global Logistics Staff;
|
||
I want to Request for Wagon to load the import shipment on behalf of the customer
|
||
So that the customer can settle the payment and proceed with loading the shipment on train
|
||
Acceptance Criteria
|
||
The system must allow the Global Logistics team to request for Wagon to load the shipment to the operations team, the status will be ‘Wagon Requested’
|
||
Operations team will validate the documents and Proceed to generating PNR for payment and status will show Pending payment
|
||
Once Payment is settled in by the customer the status will change to Payment settled
|
||
Once the status shows payment settled, Operations team will proceed with wagon allocation and status will change to Wagon allocated
|
||
Then update ‘Gate pass permission granted’for import shipment at container(DMP/ DCT) yard.
|
||
US07: Cargo Acceptance and Loading on Train
|
||
As an Djibouti Global Logistics staff ,
|
||
I want to cross check and validate the correct shipment has arrived for loading at port
|
||
AND
|
||
I want to include any exception management if applicable to the cargo.
|
||
Accepting criteria
|
||
AC1: Exception Management
|
||
AC 1.1: Condition Incident Form Factor
|
||
The system must provide an emergency incident logging component within the active milestone interface.
|
||
AC 1.2: Standard Anomaly Taxonomy
|
||
The inspector must select from a predefined incident classification dropdown: Seal is Broken, Container Opened, Container Damaged, or Fluid Leaking/Coming Out.
|
||
A mandatory free-text narrative field for a detailed description must be filled out alongside a mandatory upload slot for photo verification (supported format: .jpg).
|
||
AC 1.3: Real-Time Border-to-Capital Notification Pipeline
|
||
Upon saving an incident record at a border or port station, the system must trigger a high-priority alert to the Global Logistics Team Ethiopia, attaching the text description and photos directly to their operational dashboard. At the same time the customer will receive a notification on its portal ‘damage reported’
|
||
|
||
AC 2: Shipment Loading Management
|
||
The Djibouti Global Logistics team should trigger cargo ready for loading and loaded milestones in the system ‘ready for loading’ and once the consignment is ‘loaded’
|
||
The Global Logistics team must upload the transport documents T1 before train departure.
|
||
Each milestone should also reflect on the Global Logistics window and customer portal for each specific order.
|
||
|
||
|
||
|
||
US08 : Train Depart For Import
|
||
As a Djibouti Global Logistics staff,
|
||
I want to confirm the train number, wagon number and container number at departure
|
||
So that, status of the shipment is changed from loaded status to departed status
|
||
And
|
||
As Ethiopian Global Logistics team and Operations staff,
|
||
I want the system to notify us about the Train Departure from Djibouti
|
||
So that final import clearance preparation can commence
|
||
Accepting criteria
|
||
The system shall use the train number and wagon number from wagon allocation stage and update the milestone ‘Departed from Djibouti’ from Djibouti Global Logistics side
|
||
The system shall notify the departure time, Estimated arrival time and send a notification to Operations and Global Logistics Ethiopia, Marketing and Business Development team and the customer.
|
||
The system shall generate a load list (Marshaling) that contains wagon Number, Train number, customer name and ID, container number. Here the load list should match which container is loaded on which wagon number and should be visible to all departments for downloading and internal use.
|
||
US09 : Inter-Regional cargo transfer and handover
|
||
|
||
As a Djibouti Global Logistics Ethiopia,
|
||
Upon train departure from Djibouti, the task for cargo handling and offloading to the container yard should automatically be under the custody of Operations and GL Ethiopia team.
|
||
Acceptance Criteria
|
||
AC 1: Operational Phase Handoff Trigger
|
||
When the milestone Departed is triggered from the Djibouti side, the system must automatically execute an administrative role transfer, setting the primary owner to Global Logistics Ethiopia
|
||
|
||
AC 2: Asymmetric Milestone Notifications
|
||
Upon train departure execution, the system must distribute tailored data packets automatically:
|
||
Global Logistics Djibouti: Updates Actual time of Departure (ATD)
|
||
Customer Portal: Receives status notification ‘Departed’
|
||
Global Logistics Ethiopia: Receives Actual time of Departure (ATD) and Expected Time of Arrival (ETA)
|
||
US10: Cargo Acceptance and offloading - Import
|
||
As an port and terminal Staff ,
|
||
I want to cross check and validate the correct shipment has arrived through the Marshalling document
|
||
And
|
||
As a Global Logistics Ethiopia Staff,
|
||
I want the system to notify me when the train arrives at Destination
|
||
So that further shipment clearance can proceed.
|
||
Accepting criteria
|
||
The port and terminal team should trigger time that the cargo arrived and received in the system ‘Train arrived’
|
||
The operation team should trigger cargo offloaded milestones ‘Offloaded’ here offloading should state exact Yard number and Zone of the container location. (Warehousing Concept)
|
||
Each milestone should also reflect on the customer portal for each specific order.
|
||
US 11: Global Logistics Customs Clearance and Documentation finalization- IMPORT
|
||
As a Global Logistics Ethiopia staff,
|
||
I want to immediately process the closure of the T1 transport document and secure the Import Release Permit from Customs,
|
||
So that we can finalize the shipment’s status, arrange for cargo dispatch from port, and ensure the customer is notified of the final release milestone.
|
||
Acceptance Criteria:
|
||
Trigger: The system must confirm that the train has arrived at the Ethiopian terminal yard and that the containers have been offloaded.
|
||
T1 Closure: The Global Logistics system must reconcile the offloading confirmation against the T1 document, submitting a closure request to the Customs Authority.
|
||
Risk Assessment: Customs risk criteria (Green, Yellow, Blue, Red) must be assigned, defining the level of physical or documentary examination required. Here the system needs to notify the customer on ‘risk assigned’. GREEN, YELLOW, RED
|
||
Release Submission: Once the T1 is closed and Customs Process is finalized based on the assigned Risk, the system must trigger ‘Import Release Permit granted’
|
||
Customer Notification: Upon permit issuance, an automated notification must be sent to the customer via the Customer Portal, updating their shipment status to "Import Release Granted."
|
||
When the above documents are uploaded, the milestone Import Customs Clearance Process Finalized must automatically transition to ‘Import process Completed’
|
||
US 12: Automated Storage & Demurrage Fee Progressions
|
||
As port and terminal staff,
|
||
I want the system to systematically monitor container dwell times and dynamically apply incremental demurrage tariffs from day three onward,
|
||
So that I can automate auxiliary revenue collection and hold terminal space release until all outstanding storage balances are fully settled.
|
||
Acceptance Criteria
|
||
AC 1: Dwell-Time Calculation Engine
|
||
The system must automatically measure container dwell time:
|
||
Dwell Days = Exit Date —- Cargo Offloading Date
|
||
AC 2: Step-Up Demurrage Tariff Automation
|
||
The system must process billing logic using a stepped progressive calculation model:
|
||
Example:
|
||
Days 1 to 3: Free Storage Period (ETB 0.00).
|
||
Day 4: ETB 2,500per day per container.
|
||
Day 5: ETB 3,200 per day per container.
|
||
Day 6: ETB 4,000 per day per container.
|
||
Day 7: ETB 5,000 per day per container.
|
||
|
||
AC 3: Financial Module Push Block
|
||
The Calculated storage and demurrage amount should automatically be calculated and the Due amount should be Notified to the Customer using a Unique serial Number for settlement ‘Storage and storage invoice raised’ status should be triggered automatically on the customer portal.
|
||
The total accrued cost must be sent as a mandatory charge item line to the Finance Module, and the system must block the release of the electronic exit note until the status of the storage invoice shows as Paid.
|
||
AC 4: Exit Note Trigger
|
||
Upon the completion of storage invoice settlement and status changed to Paid, generation of the final terminal exit note shall proceed.
|
||
Finance Management Module
|
||
US13: Post-Transit Miscellaneous Cost Settlement & Cycle Closure
|
||
As a Corporate Finance team,
|
||
I want to insert delayed third-party maritime bills into the active payables ledger after cargo delivery and explicitly trigger a "Permanently Closed" file validation,
|
||
So that I can lock the file from further adjustments, accurately calculate final profits, and conclude the operational billing lifecycle.
|
||
Acceptance Criteria
|
||
AC 1: Post-Operational AP Ingestion
|
||
The system must allow users to add additional rows to the Accounts Payable (AP) ledger for third-party charges (e.g., Djibouti Port Handling, Subcontracted Service Invoices) even while the invoice lifecycle status sits at Temporarily Closed.
|
||
AC 2: Permanent Accounting Closure Trigger
|
||
Once all outstanding third-party invoices from the Djibouti operations are entered and matched, the user must be able to switch the billing cycle state to Permanently Closed.
|
||
This action locks the financial record against any further adjustments or cost line additions.
|
||
|
||
Import Documents
|
||
No
|
||
Customer Uploading documents
|
||
Global Logistics Uploading Documents
|
||
Remark
|
||
1
|
||
Commercial Invoice*
|
||
Import Declaration Document*
|
||
|
||
|
||
2
|
||
Packing List*
|
||
Transit permitted screenshot*
|
||
|
||
|
||
3
|
||
Certificate of Origin (COO)
|
||
Delivery Order
|
||
|
||
|
||
4
|
||
Bank Permit/Franco Valuta*
|
||
Damage report photos
|
||
Damage report photos are not mandatory only if there is any exceptions took place
|
||
5
|
||
Bill of Lading/SWB*
|
||
T1 Transport documents
|
||
|
||
|
||
6
|
||
Power of Attorney (POA)*
|
||
Import release
|
||
|
||
|
||
7
|
||
Import License*
|
||
Full out Interchange*
|
||
|
||
|
||
8
|
||
Other Regulatory documents as per the imported shipment
|
||
Empty in Interchange*
|
||
|
||
|
||
9
|
||
Duty and tax payment slips*
|
||
Final Declaration*
|
||
|
||
|
||
10
|
||
Storage and Demurrage payment slips*
|
||
|
||
|
||
|
||
|
||
|
||
*Mandatory documents
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Milestone updates for Export Shipments
|
||
No
|
||
Important Milestones
|
||
Responsible departments
|
||
Milestones triggered by document upload
|
||
Reamark
|
||
1
|
||
Import Documents Uploaded
|
||
Customer
|
||
No
|
||
|
||
|
||
2
|
||
Pending Document Review
|
||
Global Logistics-ET
|
||
Yes
|
||
Once all documents are uploaded from customer side
|
||
|
||
|
||
3
|
||
Documents Approved
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
4
|
||
Under Customs Clearance
|
||
Global Logistics- ET
|
||
No
|
||
|
||
|
||
5
|
||
Declared
|
||
Global Logistics-ET
|
||
Yes
|
||
Once the export clearance documents are uploaded
|
||
6
|
||
Duty and Taxes advised
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
7
|
||
Duty and tax paid
|
||
Customer
|
||
Yes
|
||
When the customer uploads the payment slip
|
||
8
|
||
DO Collected
|
||
Global Logistics-Djibouti
|
||
Yes
|
||
When the GL team uploads the DO on the system
|
||
9
|
||
Wagon allocation requested
|
||
Global Logistics-Ethiopia
|
||
No
|
||
|
||
|
||
10
|
||
Payment settled
|
||
Customer
|
||
Yes
|
||
When the PNR due amount is settled
|
||
11
|
||
Wagon allocated
|
||
Operations department
|
||
No
|
||
|
||
|
||
12
|
||
Gatepass granted
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
13
|
||
Ready for loading
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
14
|
||
Loaded
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
15
|
||
Departed from Djibouti
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
16
|
||
Arrived at Port in Ethiopia
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
18
|
||
offloaded
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
19
|
||
T1 Closed
|
||
Global Logistics- Ethiopia
|
||
No
|
||
|
||
|
||
20
|
||
Customs Risk Assigned
|
||
Global Logistics- Ethiopia
|
||
No
|
||
|
||
|
||
21
|
||
Import Release Permitted
|
||
Global Logistics- Ethiopia
|
||
No
|
||
|
||
|
||
22
|
||
Storage and Demurrage charges settled
|
||
Customer
|
||
Yes
|
||
When the customer uploads the payment slip from the customer portal
|
||
23
|
||
Port Exit issued
|
||
Global Logistics- Ethiopia
|
||
No
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Multimodal Transport Global Logistics User Story IMPORT
|
||
US 01: Importer Service Request Placement
|
||
|
||
As a customer I want to submit a digital Freight Proforma Request with complete cargo and supplier details
|
||
I want to seamlessly select my freight direction Import, choose between Modes of transport (Road, Sea, Air) to combine with Rail transport, define precise cargo type (Bulk/ Break bulk or Container..), and upload foundational corporate documentation through a single portal. Additional informations like Port of Loading (POL), Port of Destination (POD), buyer or Seller name, Cargo readiness date (for import shipments)
|
||
So that the MTO team can review the operational requirements and initiate the booking process with an error-free Multimodal Logistics operation tailored to my specific supply chain needs.
|
||
Acceptance Criteria
|
||
AC 1: Direction and Service Selection UI
|
||
Direction Choice: The system must automatically set Import as the Service Type.
|
||
Routing Information: Origin and destination of shipments (Country and port eg: CNNGB, CN designates China and NBG represents Ningbo port)
|
||
The system must render a dynamic selection grid/dropdown allowing the customer to select combinations of Road, Train, Sea, and Air.
|
||
AC 2: Information intake section
|
||
The form must enforce strict character and format validation on the following mandatory input fields:
|
||
|
||
Importer Name & Importer Physical Address (Alphanumeric text strings)/Consignee.
|
||
Supplier/Seller Name & Seller Physical Address (Alphanumeric text strings).
|
||
Container Type (Dropdown: 20ft Standard, 40ft Standard, 40ft High-Cube, 20ft/40ft Reefer etc.).
|
||
Number of containers (Numeric positive integers only).
|
||
Readiness Date (Calendar date picker tool; must be equal to or greater than the current system date).
|
||
Port of Loading or Port of Destination (Dropdown field dynamically mapped to global UN/LOCODE standards).
|
||
|
||
By Clicking the Submit Request button must automatically validate all fields, display real-time inline errors for missing data, change the shipment status to MTO Service Requested`, and timestamp the event in the system log.
|
||
|
||
US 02: Order Intake by Global Logistics MTO (EDR)
|
||
|
||
As Global Logistics Staff, I want to receive the filled information via a notification from the Customer portal
|
||
So that I can validate the requests compliance and decide to accept the service request or not
|
||
Acceptance Criteria
|
||
AC 1: Order amendment, Acceptance or Rejection
|
||
Once the order actually pops up on the Global Logistics interface, the staff can request for amendment on the information to the customer, accept or reject the service request and every acceptance or rejection will be communicated back to the customer.
|
||
Milestone Assumptions
|
||
Service Request amendment requested→ An amendment request will be sent to the customer with a note on it.
|
||
Service request Rejected → Rejection reasoning will be provided to the customer, reasons may arise due to vessel call at POL, Service unavailability at POD.
|
||
Service Request Accepted → Acceptance notification will be sent to the customer to proceed with the operation
|
||
|
||
|
||
US 03: Cargo Agent Space Booking & Allocation (This step will be done via email)
|
||
As a Global Logistics Staff, I want to transfer orders to the designated Freight Forwarding Agent at POL
|
||
So that the system can change the shipment state to Supplier contacted on the customer portal.
|
||
As a designated Freight forwarding agent, I want to check the cargo readiness date, Export formalities are done, Empty equipment availability and stuffing of cargo. Once all these formalities are done; Origin Export formalities finalized milestone will be updated on the customer portal.
|
||
Acceptance Criteria
|
||
AC 1:Notification and update
|
||
The global Logistics staff must have log communication records with the importer, confirming the liner shipping space availability, and input the carrier details and booking reference number.
|
||
US 04: Cargo Receipt & Loaded on Board (This step will be done via email)
|
||
As a designated Freight forwarding agent, I want to confirm the shipment is transferred to the shipping lines for loading. This will trigger, Ready for loading at Origin milestone will be updated on the customer portal.
|
||
Once the Vessel Sails from Origin, the Freight forwarding Agent will update Shipped on Board milestone will be updated on the customer portal and In transit status will automatically follow
|
||
|
||
|
||
|
||
Acceptance Criteria
|
||
AC 1:Notification and update
|
||
The global Logistics staff must have log communication records with the importer, confirming the Ready for Loading Milestone once the cargo is transferred to the shipping lines at Origin and Shipped status once the shipment departs from origin port.
|
||
|
||
|
||
|
||
US 05: Bill of Lading (B/L) Generation (This step will be done via email)
|
||
|
||
As a designated Freight forwarding agent, once the shipping lines receive the physical cargo, the system must expose two secure document upload slots
|
||
Accepting Criteria
|
||
Master Bill of Lading (OBL Slot): After finalizing the communication between the shipping lines and designated freight forwarder/booking agent, Final approved OBL will be uploaded.
|
||
House Bill of Lading (HBL Slot): As per the request from the importer, the designated freight forwarding agent will upload the final approved HBL document on the portal.
|
||
Milestones Updated: Transport Documents Uploaded
|
||
|
||
|
||
|
||
|
||
US 06: Cargo arrive at Djibouti Port
|
||
As a Global Logistics Staff, I want to confirm the shipment arrival at Djibouti
|
||
So that the Customer can be notified and make the necessary documents ready for clearance at the destination port for clearance process
|
||
Accepting Criteria
|
||
There should be a slot where the Global logistics staff notifies the customer as a primary notification for the shipment arrival for the shipment process
|
||
US 07: Inland transportation to Inbound port
|
||
|
||
As a Global Logistics staff,
|
||
I want to electronically submit a rail wagon and train allocation request to the Operations Team, receive an automated schedule assignment, log loading milestones, and track the final dispatch,
|
||
So that we can seamlessly transition cleared multimodal containers from terminal yards to their final destination stations without manual coordination delays.
|
||
Accepting Criteria
|
||
Wagon & Train Allocation Request (Global Logistics Workspace)
|
||
AC1 Submitting an Allocation Request
|
||
Customer/Company Name (Read-only, auto-populated from contract).
|
||
Target Loading Date (Calendar date picker).
|
||
Container Count & Configuration (Auto-extracted from shipping manifest; e.g., 2 × 40ft HC).
|
||
Origin Node & Destination Station (Dropdown menu select options, example: Negad to GMP).
|
||
And clicking Submit Request must instantly transfer the data payload to the Operations Team's active scheduling queue, changing the global status flag to Allocation Pending.
|
||
|
||
|
||
Schedule & Wagon Assignment Matrix (Operations Workspace)
|
||
AC 2: Operations Team Fulfills Request & Assigns Schedule
|
||
Given an incoming request is sitting in the Allocation Pending queue,
|
||
When an Operations user opens the shipment,
|
||
Then the system must provide resource-matching fields to input the following assets:
|
||
Assigned Train Number (Alphanumeric text string field).
|
||
Assigned Wagon Numbers (Multi-select list matching the container count from US-OI-01).
|
||
Scheduled Departure Date & Time (Timestamp inputs).
|
||
Estimated Arrival Date & Time (Timestamp inputs).
|
||
And when the Operations user clicks Confirm Allocation, the system must automatically update the transport file, push the finalized rail schedule to both the Global Logistics dashboard and the Customer Portal, and advance the status to Scheduled / Ready to Load for Inbound transit.
|
||
|
||
Physical Loading Confirmation & Manifest Extraction
|
||
AC 3: Updating Loading Milestone
|
||
Given a shipment holds a status of Scheduled / Ready to Load,
|
||
When the yard loading team or Djibouti Global Logistics team completes container positioning onto the assigned wagons and clicks Confirm Loading Completion
|
||
Then the system must change the shipment status to Loaded
|
||
|
||
AC4: Departure & Dispatch Automation Loop
|
||
Scenario: Train Departure Notification
|
||
Given the shipment milestone is set to Loaded,
|
||
When the terminal yard master updates the system status to Departed (or when integrated terminal tracking sensors flag train departure),
|
||
Then the system must flip the global status to In Transit - Rail Leg.
|
||
And the backend must immediately fire a cross-border notification array (containing the digital transit manifest packet as a PDF attachment) to the receiving Destination Station team so they can prepare inbound logistics, security, and customs processing.
|
||
|
||
|
||
US08: Cargo Acceptance and offloading Station at Destination
|
||
|
||
As Operations/Port and terminal staff,
|
||
I want to cross check and validate the correct shipment has arrived through the Marshalling document
|
||
And
|
||
As a Global Logistics Ethiopia Staff,
|
||
I want the system to notify me when the train arrives at the destination station to process T1 closure with Customs.
|
||
Acceptance Criteria
|
||
The warehouse and terminal team should trigger time that the cargo arrived and received in the system Train arrived
|
||
The operation team should trigger cargo ready for offloading and offloaded milestones should be triggered in the system Offloaded at Container Yard here offloading should state exact Yard number and Zone of the container location.
|
||
Each milestone should also reflect on the customer portal for each specific order.
|
||
US 09: Payment Settlement and Import Process Initiation
|
||
|
||
As Finance Department,
|
||
I want the system to automatically generate an automated payment invoice based on the active customer contract and dynamically flip the shipment milestone status to "Paid" upon payment verification,
|
||
So that we can eliminate credit risk, secure operating cash flow, and programmatically authorize Global Logistics, Operations and Port and terminal team to proceed with the necessary processes.
|
||
|
||
Acceptance Criteria
|
||
Pre-Conditions for System Execution
|
||
After the container is placed at the designated warehouse, The shipment file must be in an initial state of Pending Invoice Generation.
|
||
AC1: Automated Invoice Generation
|
||
Scenario: Compiling Contract Data into a Digital Billing Invoice
|
||
Given a shipment file is in a Pending Invoice Generation state,
|
||
When a Finance user navigates to the "Billing & Invoice Module" and clicks Generate Invoice,
|
||
Then the system's calculation engine must execute a read-only query against the active contract to pull:
|
||
Base freight rates matched to the selected route corridor.
|
||
Container metrics (Total Count multiplied by tariff ).
|
||
Valid ancillary terminal or customs clearance fees (if Value-Added Service is selected).
|
||
And the system must output an immutable digital invoice document containing a unique, bank-integrated alphanumeric tracking serial structured as: [CustomerName]-[DueAmount]-[UniqueUUID].
|
||
And the shipment status must instantly switch to Pending Payment, locking down all downstream operational queues like clearance and shipment exit from terminal.
|
||
|
||
|
||
AC2: Bank-API Integration & Payment Settlement
|
||
Receiving Payment Token and Unlocking System Gates
|
||
Given a shipment holds a status of Pending Payment,
|
||
When the customer settles the due amount and the system receives a secure, cryptographic transaction token from an integrated banking API (e.g., Commercial Bank of Ethiopia, Telebirr) matching the unique invoice serial number,
|
||
Then the system must immediately process a real-time transaction confirmation match.
|
||
And the platform must prevent manual overrides or bypassing of this payment validation gate unless authorized by a Super-User financial security role.
|
||
|
||
US-FIN-03: Dynamic Milestone Triggering ("Paid")
|
||
Scenario: Updating the Global State and Notification Broadcast
|
||
Given the backend banking verification token evaluates to SUCCESS,
|
||
When the system logs the incoming transaction,
|
||
Then the system must automatically flip the shipment milestone status to Paid.
|
||
Below User Story 09 is Applicable only if the Customer Proceeds with Global Logistics Services
|
||
US 10: Customs Clearance Document Injection- Ethiopia side
|
||
As a Global logistics staff,
|
||
Once the Customs document verification and entry process is finalized on the external customs portal,
|
||
I want the system to allow a slot where Customs entry documents are attached and also visible to the customer on the portal.
|
||
Acceptance Criteria
|
||
The system must provide dedicated slots for the final processed operational forms: IM4 (Permanent Import Document), IM5 (Temporary Import Document) for the declared shipment
|
||
If there are any duties and taxes to be settled, The Global Logistics team will send the amount, Declaration Serial number and automatic notification to the customer will be sent to the customer. Here there should be a spot where the Customer can upload the payment slip from its portal and same will reflect and notify the Global Logistics team Duties and taxes settled
|
||
Risk Assessment: Customs risk criteria (Green, Yellow, Blue, Red) must be assigned, defining the level of physical or documentary examination required. Here the system needs to notify the customer on Risk assigned. GREEN, YELLOW, RED
|
||
Release Submission: Once the T1 is closed and Customs Process is finalized based on the assigned Risk, the system must trigger Import Release Permitted
|
||
Customer Notification: Upon permit issuance, an automated notification must be sent to the customer via the Customer Portal, updating their shipment status to "Import Release Granted."
|
||
When the above documents are uploaded, the milestone Import Customs Clearance Process Finalized must automatically transition to Import process Completed
|
||
US 10: Automated Storage & Demurrage Fee Progressions
|
||
As a Finance team,
|
||
I want the system to systematically monitor container dwell times and dynamically apply incremental demurrage tariffs from day six onward,
|
||
So that I can automate auxiliary revenue collection and hold terminal space release until all outstanding storage balances are fully settled.
|
||
Acceptance Criteria
|
||
AC 1: Dwell-Time Calculation Engine
|
||
The system must automatically measure container dwell time:
|
||
Dwell Days=Exit Date - Cargo Offloading Date
|
||
AC 2: Step-Up Demurrage Tariff Automation
|
||
The system must process billing logic using a stepped progressive calculation model:
|
||
Example:
|
||
Days 1 to 5: Free Storage Period (ETB 0.00).
|
||
Day 6: ETB 2,500per day per container.
|
||
Day 7: ETB 3,200 per day per container.
|
||
Day 8: ETB 4,000 per day per container.
|
||
Day 9: ETB 5,000 per day per container.
|
||
AC 3: Financial Module Push Block
|
||
The Calculated storage and demurrage amount should automatically be calculated and the Due amount should be Notified to the Customer using a Unique serial Number for settlement Storage and Demurrage invoice raised status should be triggered automatically on the customer portal.
|
||
The total accrued cost must be sent as a mandatory charge item line to the Finance Module, and the system must block the release of the electronic exit note until the status of the storage invoice shows as Paid.
|
||
US 11: Last Mile Transport processing- EDR processing the Last mile
|
||
As a Global Logistics staff,
|
||
I want to electronically submit a truck assignment request to the Truck & Machinery Department and, upon fulfillment, automatically compile the assigned asset/driver data into a standardized Truck Waybill,
|
||
So that we can efficiently coordinate physical last-mile deliveries, eliminate manual data entry errors.
|
||
Acceptance Criteria
|
||
Pre-Conditions for System Execution
|
||
The cargo must be physically present and the import customs clearance process should be finalized.
|
||
AC1: Inter-Departmental Last-Mile Truck Request
|
||
Scenario: Submitting a Request to the Truck & Machinery Department
|
||
Given a shipment file is ready for last-mile delivery to the customer's doorstep,
|
||
When a Global Logistics user opens the "Last-Mile Module" and clicks Request Fleet Allocation,
|
||
Then the system must auto-populate a routing task packet containing the following read-only fields:
|
||
Client Name & Client ID (Extracted from the master order profile).
|
||
Required Truck Type / Capacity (Based on container configurations or weight specifications).
|
||
Place of Unloading (The final delivery destination address provided by the customer and phone number of contact person).
|
||
Container Type (Eg: 1x40’ HC or 1x20 DV)
|
||
And clicking submit, it must change the local leg status to Pending Truck Request and route the task directly into the Truck & Machinery Department's active workspace queue.
|
||
|
||
|
||
|
||
AC2: Asset Assignment & Data Injection (Truck & Machinery Dept.)
|
||
Fulfilling the Truck Request
|
||
Given a request sits in the Truck Request Pending queue,
|
||
When a user from the Truck & Machinery Department opens the task,
|
||
Then the system allows them to select and assign active, compliant resources from the database by filling out the following mandatory fields:
|
||
Driver Name (Dropdown or text validation matching registered, available operators). Which will auto populate the attached truck details and plate number with the driver
|
||
Truck Type (Dropdown: e.g., Casoni, truck trailer, highbed, low-bed etc.).
|
||
Driver Phone Number (Alphanumeric/Numeric text field linked to the driver profile).
|
||
And clicking Submit Fleet Assignment must update the vehicle monitoring engine state to Truck Assigned and hand control back to the Global Logistics team.
|
||
AC3: Automated Truck Waybill Compilation
|
||
Generating the Final Waybill Documents
|
||
Given the Truck & Machinery Department has completed the truck assignment,
|
||
When the system reassigns the task to the Global Logistics team dashboard,
|
||
Then the system must unlock a Generate Truck Waybill action engine.
|
||
And clicking this button must instantly compile a non-editable, standardized digital transport document incorporating the following multi-departmental data streams:
|
||
From the Client Profile: Client Name and Client ID.
|
||
From the Logistics Order: Place of Unloading.
|
||
From the Truck & Machinery Allocation: Driver Name, Driver Phone Number, and Truck Plate Number.
|
||
And the document must be saved to the database in PDF format, update the leg status to Waybill Generated, and enable a print/download utility for the gate security and driver.
|
||
And Dispatched Milestone will be triggered afterwards.
|
||
|
||
The below User Story is applicable if the Customer does not require last mile service from EDR
|
||
US 12: Last Mile Transport processing- Customer processing the Last mile
|
||
As a Customer/Importer,
|
||
I want to directly input my designated third-party transport vehicle details, container matching fields, and operator data into the Customer Portal, generate a duplicate set of Freight Orders, and track the physical loading and proof of delivery (POD) signing by port operators and Customer.
|
||
So that I can seamlessly manage my own last-mile haulage assets and legally clear my containerized cargo from the terminal yard.
|
||
Acceptance Criteria
|
||
Pre-Conditions for System Execution
|
||
The cargo must be physically present and the import customs clearance process should be finalized.
|
||
AC1: Customer Portal Asset Ingestion Matrix
|
||
Customer Inputs External Truck and Driver Profiles
|
||
Given a shipment file satisfies all pre-conditions and sits in the Ready for loading status,
|
||
When the Customer logs into the portal, opens the shipment file, and fill in the transport details;
|
||
Then the system must provide a user interface requiring the customer to fill out the following mandatory parameters:
|
||
Truck Plate Number (Alphanumeric entry text field).
|
||
Driver Name (Alphanumeric entry text field).
|
||
Truck Type (Dropdown selection matrix: e.g., Flatbed, Container Chassis, Lowboy).
|
||
Container Number to Load (Alphanumeric format validation text box matching ISO container standards).
|
||
And clicking the Verify & Submit Assignment button must check that none of the inputs are empty strings, freeze editing capabilities for the customer, and advance the shipment state to Truck Assigned.
|
||
|
||
|
||
|
||
AC 2: Automated Twin Freight Order Compilation
|
||
Printing Duplicate Freight Orders from the Customer Portal
|
||
Given a shipment holds a status of Truck Assigned,
|
||
When the customer clicks the Generate Freight Order Copies button,
|
||
Then the document generation engine must automatically compile a downloadable, print-ready PDF document containing all details gathered in AC1 alongside the Client Name and unique Client ID.
|
||
And the engine must render the document in a dual-copy format with watermark ("Copy 1: Port Operations Copy" and "Copy 2: Gate Security & Carrier Copy").
|
||
And the gate and security team will check for the physical truck arrival and the port and terminal team will trigger Truck Arrived milestone status.
|
||
|
||
AC 3: Port Yard Loading & Operations Validation Loop
|
||
Port and terminal staff Team Processes
|
||
Given the customer's third-party truck has physically arrived at the port gate holding the printed Freight Order documents,
|
||
When the internal EDR port and terminal staff team opens the matching file via the internal system terminal,
|
||
Then the system must force the operator to verify that the arriving physical vehicle's plate number, driver identity, and container matches the data locked by the customer.
|
||
And upon physical reachstacker positioning of the box, the operator clicks Loaded on truck, loading timestamp will be captured to the system log.
|
||
AC4: Digital POD Signing & Port Dispatch
|
||
Completing Handover and Archiving the File
|
||
Given the container has been physically loaded to the assigned truck,
|
||
When the authorized EDR Port and terminal staff checks the signed paper copy
|
||
Then the system must open a slot where a signed POD is uploaded on the system.
|
||
And saving this file must automatically mark the shipment milestone as Dispatched from Port / Completed.
|
||
|
||
Milestone triggers for Multimodal Operation
|
||
No
|
||
Important Milestones
|
||
Responsible departments
|
||
Milestones triggered by document upload
|
||
Reamark
|
||
1
|
||
MTO Service Requested
|
||
Customer
|
||
No
|
||
|
||
|
||
2
|
||
Service Requested Accepted
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
3
|
||
Supplier/Shipper Contacted
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
4
|
||
Origin Export Formalities finalized
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
5
|
||
Ready for Loading
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
6
|
||
Shipped on Board/Loaded
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
7
|
||
B/L (transport documents) uploaded
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
8
|
||
In transit
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
9
|
||
Ship arrived at Port
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
10
|
||
Scheduled / Ready to Load for Inbound transit
|
||
Global Logistics-Djibouti
|
||
No
|
||
|
||
|
||
11
|
||
Loaded on train
|
||
Global Logistics -Djibouti
|
||
No
|
||
|
||
|
||
12
|
||
In transit to destination port
|
||
Global Logistics -Djibouti
|
||
No
|
||
|
||
|
||
13
|
||
Train Arrived
|
||
Port and terminal Department
|
||
No
|
||
|
||
|
||
14
|
||
Offloaded at Container Yard
|
||
Port and terminal department
|
||
No
|
||
|
||
|
||
15
|
||
Pending payment
|
||
Finance department
|
||
No
|
||
Multimodal transport service payment
|
||
16
|
||
Paid
|
||
System Generated
|
||
Yes
|
||
When the Unique serial number for payment is settled the system will autofill date and time
|
||
17
|
||
Commercial Documents received
|
||
Global Logistics-ET
|
||
NO
|
||
Only if the customer decided to proceed with GL customs clearance services
|
||
18
|
||
Import Customs entry processed
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
19
|
||
Duty and taxes notified
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
20
|
||
Duty and taxes Paid
|
||
Customer /Bank system generated
|
||
Yes
|
||
When the Unique serial number for payment is settled the system will autofill date and time
|
||
21
|
||
Customs Risk Assigned
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
22
|
||
Import Release Permitted
|
||
Global Logistics-ET
|
||
No
|
||
|
||
|
||
23
|
||
Storage and Demurrage Invoice Raised
|
||
Finance
|
||
|
||
|
||
|
||
|
||
24
|
||
Storage and Demurrage Invoice Paid
|
||
Customer /Bank system generated
|
||
Yes
|
||
When the Unique serial number for payment is settled the system will autofill date and time
|
||
25
|
||
Last Mile truck requested
|
||
Global Logistics-ET
|
||
No
|
||
Only if the customer requests for last mile service
|
||
26
|
||
Truck Assigned
|
||
Truck and Machinary
|
||
No
|
||
|
||
|
||
27
|
||
Truck Arrived
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
28
|
||
Truck loaded
|
||
Port and terminal
|
||
No
|
||
|
||
|
||
29
|
||
Truck waybill generated
|
||
Global Logistics-ET
|
||
Yes
|
||
When the truck waybill is printed, it will automatically capture the date and time
|
||
30
|
||
Dispatched
|
||
Port and Terminal
|
||
No
|
||
|
||
|
||
|
||
|
||
|