FFA

Title: Create Vessel Schedule

A freight forwarder should be able to manage, create, read, update, delete a vessel schedule. He/she can view the list of vessel schedules and add deadlines.

Vessel schedule will be used:

• in freight purchase screen
• in quotation screen
• in file reference screen

Acceptance Criteria:

(a). Create Vessel Schedule:

·        When accessing the page, the system should allow the user to create a vessel schedule.

·        When creating the vessel schedule, the system should allow the user to add the following information:

• Vessel Name and shipping line (dropdown - information received from manage shipping line and create vessel screen) [Mandatory]
• ATP number
• Arrival Voyage number [Mandatory]
• Departure Voyage Number
• Port of Loading (Dropdown) [Mandatory]
• Port of destination (Dropdown) [Mandatory]
• Loading Terminal
• Destination Terminal
• Report Number
• Estimated Date and time (Arrival [Mandatory] and Departure)
• Actual Date and time (Arrival and Departure)
• Estimated Transit days (calculated: Departure date minus arrival date)

NB:

1. Display all Mandatory fields with [ * ] in red color.
2. The system should display proper error message when mandatory fields are blank when saving (e.g. Kindly fill all the required fields marked by * )

·    After inserting all the information, the system should allow the user to save or cancel the vessel schedule.

·    The system should allow the user to view the created vessel schedule after saving.

(b) Generation of Master File Reference number

·        After creating the vessel schedule, a Master File reference should be generated automatically (e.g. MACCSXXX01)

NB: The Master File Reference number will be used:

• in the Shipment Cost (Freight Purchase) module when vessel schedule is being retrieved.
• in the File Reference module to regroup sub files under the Master File Reference.

(c) Screen display and Filtering:

·        When accessing the page, the system should display the list of vessel schedules already created. Display columns will be as below:

• Master File Reference
• Vessel name
• ATP number
• Date and time of arrival
• Date and time of departure (from origin)
• Arrival Voyage number
• Departure Voyage number
• Estimated transit days
• Port of loading
• Port of destination
• Loading Terminal
• Destination Terminal

NB: User should be able to delete or modify the list of vessel schedules.

·      The system should allow the user to filter the vessel schedule by:

• Master File reference

• vessel name

• voyage numbers,

• created date,

• ATP

  (d) Manage Deadlines:

·        The system should also allow to add, update and delete deadlines for each vessel schedules created with the following information:

• Deadline Text field [Mandatory]
• Date and time of deadline [Mandatory]

The system should display all deadlines in a list.

(e) Reminder Notifications:

• Scheduled Reminder Notifications:
  The system should automatically send reminder notifications 2 days before the deadline date to all users associated with or who have interacted with or referenced the specific Vessel Schedule in the File Reference.
• Continuous Daily Reminders:
  After the initial reminder, the system should continue sending daily reminders (1 day before the deadline and on the deadline date itself) to ensure consistent awareness among users.
• Deadline Day Notification:
  On the actual deadline day, the notification must clearly highlight to users that Vessel schedule deadline reached, clearly emphasizing urgency.
• Notification Delivery:
  Notifications must be clearly delivered through system-supported channels (e.g., email alerts, WhatsApp notifications, or both, based on company configuration).

(f) Test Scenarios as per the attached excel sheet:

Ocean Import - Vessel Schedule Test Scenario.xlsx