Task #17530
openTask #18451: Ocean Sprint Planning for 16/06/2025 - 30/06/2025
User Story: CFS Storage Handling - Track and Manage CFS storage for cargo
45%
Description
A Freight Forwarder (FFWD) / Co-Loader should be able to track CFS Storage for deconsolidated cargo. He or she can notify consignees of free periods, monitor overdue cargo, and record CFS storage charges efficiently.
Actors:
- Freight Forwarder (FFWD) / Co-Loader
- Consignee
- Container Freight Station (CFS) Operator
- CHCL (Cargo Handling Corporation Ltd) System
Refer to Epic https://gitlab.maccs.mu/rnd/ffa/documentation/-/issues/390 for more information.
Pre-requisites:
- A File Reference must have already been created and HBL approved in the system for the shipment.
- In order to begin the CFS Storage countdown, the Container Status must be updated to "Transferred to CFS", the Unstuffing Date & Time and the CFS Deadline for storage have been recorded.
Acceptance Criteria:
1. Container Discharge & Free Period Starts
-
When a container is discharged at CHCL, the user should be able to record the container status in FFS as “At CHCL Yard".
-
The system should include a "Terminal Storage" section within the container-level section of the Shipment Cost screen.
-
This subsection will store and track key container movement details, including:
- Discharge Date & Time (when the container is offloaded at CHCL).
- CHCL Deadline (the deadline date before storage charges apply).
- CFS Name (the CFS where the container will be unstuffed)
- Gate-In CFS Date & Time (when the container enters the Container Freight Station).
- Gate-Out CFS Date & Time (when the container exits the CFS after clearance).
- Unstuffing Date & Time (when cargo is removed from the container for delivery).
-
Data from the above sub-subsection should be displayed as information in the File Reference screen within the container-level section as "Terminal Storage".
Note that this functionality has already been added in ticket https://gitlab.maccs.mu/rnd/ffa/documentation/-/issues/391 also.
-
The system should include a "CFS Storage" subsection within the HBL-level section of the File Reference screen.
-
This subsection will store and track the following storage details related to the Container Freight Station (CFS), including:
- CFS Deadline (the final date by which the cargo must be cleared before CFS storage charges apply).
2️ FFWD/Co-Loader Moves the LCL Container to CFS
- The system updates container status from "At CHCL Yard" → "Transferred to CFS"
- The Individual House Bill of Lading (HBL) shipments are deconsolidated at CFS.
- The system allows the user to input the Unstuffing Date & Time for each container in the Shipment Cost screen.
- The system allows the user to input the CFS Deadline for each HBL
- The system sends the Consignees notification to clear their goods within the free storage period at the CFS.
3️ Deadline Monitoring & Notifications
- The System should allow tracking of the individual consignees' clearance deadlines.
- The system should allow sending notifications to consignees before charges apply:
- 2 Days Before deadline -> Reminder email/SMS/WhatsApp.
- On deadline Day -> Final reminder before CFS storage fees apply.
- After the deadline -> Notification that storage fees are being applied.
4. CHCL Storage & CFS Storage Fees
- If the container was not moved from CHCL in time, the co-loader (FFWD) is charged Storage per day by CHCL. (for info)
- If the consignee does not clear their shipment from the CFS in time, storage fees start based on:
- CBM or weight of the cargo
- Number of days exceeding free period
- CFS tariff rates
- The system will allow the user to input the CFS Storage Charges in the file reference for the particular consignee HBL file in the Additional cost and Sales charges grid.
- The system will allow the user issuing a Payment Request to CFS.
- The system should allow billing back the consignee as additional invoices.
5. Payment & Clearance Process
- The consignee must settle any outstanding CFS storage fees before collecting their shipment.
- Once paid, the system updates:
- Status: "Cleared by Consignee"
- Date & Time of Clearance
- Storage Fees Paid
- The Freight Forwarding System generates an invoice to bill the consignee for storage fees. This will be catered under the additional sales charges in the File Reference screen.
6. Container Return & System Updates
- Once all HBL shipments are cleared, the FFWD updates the container status to "Returned to Shipping Line".
GitLab Sync Log
[{"id": "25113", "author": "Ra-ees Peeroo", "hours": 3.0, "created": "2025-06-16T11:48:13.029Z", "log_date": "2025-06-16", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-06-16T11:48:13.029Z: 3h-(3.0)h spend at: 2025-06-16", "status": "active", "deleted_by": "", "redmine_entry_id": 9651}, {"id": "25875", "author": "Ra-ees Peeroo", "hours": 8.0, "created": "2025-06-27T05:43:17.740Z", "log_date": "2025-06-24", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-06-27T05:43:17.740Z: 1d-(8.0)h spend at: 2025-06-24", "status": "active", "deleted_by": "", "redmine_entry_id": 9779}]
Updated by Redmine Admin 6 months ago
- Description updated (diff)
- Parent task set to #18123
- gitlab project trace set to Ocean Sprint Planning for 04/06/2025 - 13/06/2025
Updated by Redmine Admin 6 months ago
- Due date changed from 03/21/2025 to 06/27/2025
- % Done changed from 0 to 12
- Estimated time changed from 0:00 h to 24:00 h
- Parent task changed from #18123 to #18351
- GitLab Time Logged changed from 0 to 10800
- gitlab project trace changed from Ocean Sprint Planning for 04/06/2025 - 13/06/2025 to Ocean Sprint Planning for 16/06/2025 - 27/06/2025
Updated by Redmine Admin 6 months ago
- Status changed from New to Development Done
- % Done changed from 12 to 45
- GitLab Time Logged changed from 10800 to 39600
Updated by Redmine Admin 5 months ago
- Parent task changed from #18351 to #18451
- gitlab project trace changed from Ocean Sprint Planning for 16/06/2025 - 27/06/2025 to Ocean Sprint Planning for 16/06/2025 - 30/06/2025
Updated by Redmine Admin 5 months ago
- Status changed from Development Done to QA