Project

General

Profile

Actions

Task #17528

closed

Task #18451: Ocean Sprint Planning for 16/06/2025 - 30/06/2025

User Story: Track and Manage Demurrage(Detention) for Containers After Pickup

Added by Redmine Admin 7 months ago. Updated about 1 hour ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
03/21/2025
Due date:
03/21/2025
% Done:

100%

Estimated time:
18:00 h
Spent time:
GitLab ID:
2264
GitLab Milestone:
GitLab Ticket Number:
398
GitLab Time Logged:
86400
Lock Timeline Date:
No
gitlab project trace:
Ocean Sprint Planning for 16/06/2025 - 30/06/2025

Description

A Freight Forwarder (FFWD) should be able to track the demurrage (detention) process for containers after they leave the CHCL yard. He/she can monitor the deadline for container return, record demurrage charges, and notify consignees to avoid additional costs.

Actors:

  • Freight Forwarder (FFWD) / Co-Loader
  • Consignee

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 approved in the system for the shipment.
  • In order to begin the demurrage countdown, the Container Status must be updated to "Picked Up", and the deadline for returning the empty container has been recorded.

Acceptance Criteria:

1. Container Pickup & Deadline for Return

  • After leaving the CHCL yard and clearing any Terminal Storage fee, the system updates the container status to "Picked Up" and starts tracking the demurrage deadline.
  • The system should have a subsection named “Return of Container” within the container-level section of the Shipment Cost screen where it will store and track the following fields.
    • Pickup Date
    • Deadline for returning the empty container (the last date before demurrage applies).

2. Deadline Monitoring & Notifications

  • The system should track the allowed return date (LFD).
  • Automated notifications should be sent:
    • 2 days before deadline → Reminder email/SMS/WhatsApp to consignee & FFWD.
    • On deadline day → Final warning before demurrage starts.
    • After the deadline → Notification that demurrage charges are being applied.

3. Demurrage Charges

  • The system should allow the user to record the Demurrage charges as an Additional Cost for the particular container at the MBL level.
  • The system should allow the user to then record the Storage charges as Sales charges to bill back the client (additional invoice) at the MBL level.

4. Payment Request & Invoice Generation

  • The system should allow the FFWD to generate a Payment Request to the accounting department for settling demurrage charges with the Shipping Line.
  • The system should allow the user to generate an invoice to bill the consignee/client fback for this charge.

5. Container Return & Status Update

  • Once the demurrage charges are cleared and the container is returned, the FFWD updates the system with:
    • Return Date
    • Return Location (Shipping Line depot)
  • The shipment status should update to "Container Returned".

6. Demurrage Dashboard & Reports

  • A Demurrage Dashboard should show:
    • Pending Containers (within the deadline).
    • Overdue Containers (demurrage fees being applied).
    • Returned Containers (demurrage cleared).
  • The FFWD should be able to filter by Client, Vessel, Date, or Shipping Line.

 

@Peeroo_Raees Note that demurrage is both at Import & export level (in transhipment cases). Confirmed by Jacques from ED logistics


GitLab Sync Log

[{"id": "24863", "author": "Ra-ees Peeroo", "hours": 8.0, "created": "2025-06-12T11:25:45.072Z", "log_date": "2025-06-12", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-06-12T11:25:45.072Z: 1d-(8.0)h spend at: 2025-06-12", "status": "active", "deleted_by": "", "redmine_entry_id": 9615}, {"id": "24909", "author": "Ra-ees Peeroo", "hours": 2.0, "created": "2025-06-13T10:24:23.009Z", "log_date": "2025-06-13", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-06-13T10:24:23.009Z: 2h-(2.0)h spend at: 2025-06-13", "status": "active", "deleted_by": "", "redmine_entry_id": 9631}, {"id": "25103", "author": "Ra-ees Peeroo", "hours": 4.0, "created": "2025-06-16T11:27:56.750Z", "log_date": "2025-06-16", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-06-16T11:27:56.750Z: 4h-(4.0)h spend at: 2025-06-16", "status": "active", "deleted_by": "", "redmine_entry_id": 9650}, {"id": "25233", "author": "Ra-ees Peeroo", "hours": 4.0, "created": "2025-06-18T09:28:35.807Z", "log_date": "2025-06-16", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-06-18T09:28:35.807Z: 4h-(4.0)h spend at: 2025-06-16", "status": "active", "deleted_by": "", "redmine_entry_id": 9681}, {"id": "26698", "author": "Ra-ees Peeroo", "hours": 4.0, "created": "2025-07-16T06:52:53.176Z", "log_date": "2025-07-16", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-07-16T06:52:53.176Z: 4h-(4.0)h spend at: 2025-07-16", "status": "active", "deleted_by": "", "redmine_entry_id": 9938}, {"id": "32024", "author": "Yashvee Seetul", "hours": 2.0, "created": "2025-10-15T07:55:28.452Z", "log_date": "2025-10-12", "comment": "Imported from GitLab by @Yashvee Seetul on 2025-10-15T07:55:28.452Z: 2h-(2.0)h spend at: 2025-10-12", "status": "active", "deleted_by": "", "redmine_entry_id": 10796}]

Actions #1

Updated by Redmine Admin 7 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin 6 months ago

  • Parent task set to #18123
  • gitlab project trace set to Ocean Sprint Planning for 04/06/2025 - 13/06/2025
Actions #3

Updated by Redmine Admin 6 months ago

  • GitLab Time Logged changed from 0 to 28800
Actions #4

Updated by Redmine Admin 6 months ago

  • GitLab Sync Log updated (diff)
Actions #5

Updated by Redmine Admin 6 months ago

  • GitLab Time Logged changed from 28800 to 36000
Actions #6

Updated by Redmine Admin 6 months ago

  • GitLab Sync Log updated (diff)
Actions #7

Updated by Redmine Admin 6 months ago

  • % Done changed from 0 to 77
  • Estimated time changed from 0:00 h to 18:00 h
  • Parent task changed from #18123 to #18351
  • GitLab Time Logged changed from 36000 to 50400
  • 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
Actions #8

Updated by Redmine Admin 6 months ago

  • GitLab Sync Log updated (diff)
Actions #9

Updated by Redmine Admin 6 months ago

  • % Done changed from 77 to 100
  • GitLab Time Logged changed from 50400 to 64800
Actions #10

Updated by Redmine Admin 6 months ago

  • GitLab Sync Log updated (diff)
Actions #11

Updated by Redmine Admin 6 months ago

  • Status changed from New to Development Done
Actions #12

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
Actions #13

Updated by Redmine Admin 5 months ago

  • Status changed from Development Done to QA
Actions #14

Updated by Redmine Admin 5 months ago

  • Status changed from QA to New
Actions #15

Updated by Redmine Admin 5 months ago

  • Status changed from New to Development Done
  • GitLab Time Logged changed from 64800 to 79200
Actions #16

Updated by Redmine Admin 5 months ago

  • GitLab Sync Log updated (diff)
Actions #17

Updated by Redmine Admin 5 months ago

  • Status changed from Development Done to QA
Actions #18

Updated by Redmine Admin 5 months ago

  • Description updated (diff)
Actions #19

Updated by Redmine Admin about 2 months ago

  • Status changed from QA to Closed
  • GitLab Time Logged changed from 79200 to 86400
Actions #20

Updated by Redmine Admin about 2 months ago

  • GitLab Sync Log updated (diff)
Actions

Also available in: Atom PDF