Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Each Entity/Company is responsible for each chain of events and works with different Interface/Portal.

Company/Entity Types

...

These types also determine the login permissions for users associated with these companies:

  • Client - PO creation, Status view, Shipment authorizations, manage final destination booking

  • Supplier (Vendor) - Responsible to create and manage bookings using Seko360 vendor portal

  • Origin Agent - Responsible to create and manage shipments from creation until they are ‘confirmed on-board’

  • Destination Agent - Responsible to manage shipments from ‘confirmed on-board’ to final delivery. 

Process & Flow Chart

https://seko.atlassian.net/wiki/x/CgAHtw

and Responsibilities

  • The process involves collaboration between the Client, Vendor, and SEKO360 agents (Origin & Destination)

  • The system utilizes i-Hub services for various data exchanges and integrations (CargoWise)

  • The Client's approval is crucial at multiple stages of the process.

  • Notifications are sent in every important events such as Approvals, Cancellations, Amendments & Confirmations.

Entity

Responsibilities

Client

Creates Purchase Order

Authorize Shipments ,

Manage final destination bookings,

Monitor Deliveries

Supplier (Vendor)

Create and manage booking of Goods Shipment

Uploads documents and Shipment instructions,

Communicates with Origin Agent to Arrange transit going to Port of Origin

Origin Agent

Creates Shipment/Book Containers

Provides container shipment details,

Integrates data to CargoWise (Load and Push events)

Confirm-on-Board and notifies the destination.

Destination Agent

Manages Container Arrival in Port of Destination,

Books deliveries and plans the delivery process,

Handles customs clearance,

Provides delivery updates and POD

Process Flow Chart

https://seko.atlassian.net/wiki/x/CgAHtw