Project

General

Profile

Actions

Task #16592

closed

Task #16586: FFS Sprint2

Booking

Added by Redmine Admin 7 months ago. Updated about 2 hours ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
04/10/2024
Due date:
04/10/2024
% Done:

100%

Estimated time:
32:00 h
GitLab ID:
382
GitLab Milestone:
GitLab Ticket Number:
17
GitLab Time Logged:
0
Lock Timeline Date:
No
gitlab project trace:
FFS Sprint2

Description

Description

Develop and enhance the Booking module to efficiently handle booking requests, manage shipment details, and facilitate communication with stakeholders for both Ocean and Air Import/Export operations.

  Booking Creation and Validation:

  1. Implement logic to create bookings based on accepted quotations or customer requests, or without a quotation if necessary.
  2. Validate booking references to ensure uniqueness and system identification.
  3. Develop validation rules to ensure adherence to predefined validity periods and terms of service.

Shipment Details Management:

  1. Create forms and interfaces to capture relevant shipment details such as origin, destination, cargo type, and quantity.
  2. Develop logic to update bookings with changes in shipment details, schedules, or customer requests.

Notification:

  1. Implement automatic notifications to relevant stakeholders (can be the freight forwarders, accounting persons, CFS, managers) upon booking updates, ensuring alignment and timely communication.
  2. Develop functionality to send vessel schedules for particular bookings to clients for confirmation.

Additional info to be added to the screen:

·        Shipper

·        Consignee

·        Notify

·        Customer Details – can be same as Consignee or other

  • Booking Reference Number: Unique identifier for the booking.
  • Customer Information: Name and contact details of the customer booking the shipment.
  • Shipper Information: Details of the party originating the shipment.
  • Consignee Information: Details of the party receiving the shipment.
  • Notify Party Information (Optional): Details of a party to be notified upon shipment arrival (if applicable).
  • Shipment Details:
    • Origin and Destination (Ports/Airports)
    • Cargo Description
    • Cargo Weight and Volume
    • Incoterms (International Commercial Terms)
  • Booking Date: Date the booking was confirmed with the carrier.
  • Requested Sailing/Flight Date: Preferred date for shipment departure as per customer request.
  • Confirmed Sailing/Flight Date (if applicable): Confirmed departure date allocated by the carrier (may differ from requested date).
  • Container Details (Ocean Specific, Optional): Information about containers used for Ocean shipments (type, quantity, seal numbers).
  • Special Requirements (Optional): Any specific needs or considerations for the shipment (e.g., temperature control, fragile goods).

Bookings can be created based on accepted quotations or customer requests or can be created without a quotation.

Each booking will include relevant shipment details, including origin, destination, cargo type, and quantity.

Bookings will adhere to predefined validity periods and terms of service, ensuring transparency and consistency in pricing and service offerings.

Only authorized personnel will update bookings to reflect changes in shipment details, schedules, or customer requests.

The system should facilitate the streamlined processes for managing and confirming export bookings.

Once the FFW Agent has Approved a booking, The system will send the booking in pdf format to the shipping line (SL) via EDI file integration and IATA corresponding booking message to Airline**. Upon confirmation from Shipping Line, Clients will be notified** – FFWD will update the booking status and a notification will automatically be sent to the particular client with the shipping schedule.

Booking should have a field Status for recording the different statuses of a booking lifecycle

-Example Approved by Shipping Line, on hold, etc…

Quotations, bookings, and the master manifest should be linked within the system to maintain data consistency and traceability throughout the export process.


GitLab Sync Log

[]

Actions #1

Updated by Redmine Admin 7 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin 6 months ago

  • Status changed from In Progress to New
  • Start date changed from 04/06/2024 to 04/10/2024
Actions #3

Updated by Redmine Admin 6 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF