Introduction
Demand Chain Management (DCM) focuses on aligning supply processes with customer demand. Unlike Supply Chain Management (SCM), which mainly deals with the flow of goods from suppliers to customers, DCM emphasizes understanding and responding to customer needs and market trends.
SEKO 360 DCM offers a comprehensive solution for managing your supply chain.
Company/Entity Types
These types also determine the login permissions for users associated with these companies:
Client - Status view, shipment authorizations (if applicable), manage final destination booking
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.
Supplier (Vendor) - Responsible to create and manage bookings using Seko360 vendor portal
Log in Company Type | Role | Details |
|---|---|---|
Origin Agent | Draft Shipments | Shipments at ‘Draft’ state |
| Cancellation Requests | Shipments where the Vendor has asked for them to be cancelled |
| Shipments Required Re-Authorisation | Shipments at ‘Amend’ state |
| Shipments Ready to be Shipped | Shipments at ‘Authorised’ state - getting ready to be COB |
|
|
|
Client | Proposed Shipments Requiring Authorisation | Shipments ready to be approved |
| Deliveries to Book |
|
| Planned Deliveries |
|
| Deliveries to Reschedule |
|
|
|
|
Vendor | Draft Bookings | Bookings at ‘Draft’ state |
| Pending Shipment Instructions (SI) | Bookings that have been submitted (Shipments created) but can still be amended before the final submit |
| Shipments Pending Documents | Shipments created from the Vendors bookings where either the Commercial Invoice or the Packing Lists have not been uploaded yet |
|
|
|
Destination Agent | Deliveries to Book |
|
| Deliveries Require Confirmation |
|
| Planned Deliveries |
|
| Deliveries to Reschedule |
|
| Deliveries Require Amend Confirmation |
|
| Deliveries Require Cancel Confirmation |
|
| Deliveries Require POD and Customs |
|
SEKO360 DCM Process Flow
1. Purchase Order (PO) Creation and Processing
Client: Creates and sends POs to SEKO360.
SEKO360: Processes and stores POs.
2. Vendor Involvement
Vendor (Supplier):
Creates and manages bookings using the SEKO360 vendor portal.
Uploads necessary documents.
Vendor Booking: Vendors create new bookings or upload existing POs via CSV.
Document Upload: Vendors upload necessary documents like packing lists.
Booking Confirmation: Vendors confirm their bookings.
3. Shipment Process
Origin Agent:
Creates and manages shipments from creation until they are "confirmed on-board."
Adds shipment details and sends them to the client for approval or automatic approval.
Updates missing shipment details.
Client:
Reviews and approves or rejects shipments.
Manages final destination booking.
4. Shipment Confirmation and Delivery
Destination Agent:
Manages shipments from "confirmed on-board" to final delivery.
SEKO360: Confirms shipment and processes a confirmation message.
SEKO360: Sends a confirmation message back to the client's system.
In summary, the process involves:
PO creation and processing by the client and SEKO360. (iHub Service: Load Purchase Order)
Vendor Shipment booking and document upload. (iHub Service: Load SI)
Shipment creation and management by the origin agent. (Confirm On Board - COB)
Client approval of shipments.
Shipment management by the destination agent until final delivery.
SEKO360 confirmation and notification to the client. (iHub Service: Push XUS, SDS)
SEKO360 DCM - Cargowise Integration
1. Vendor Booking and Document Upload
Vendor: Creates new bookings or uploads existing POs via CSV.
Vendor: Uploads necessary documents.
2. SEKO360 Processing
SEKO360: Receives booking and document information.
SEKO360: Processes the information and pushes it to Cargowise (Push XUS).
3. Cargowise Integration
Cargowise: Receives information from SEKO360.
Cargowise: Processes the information and updates its system.
4. Shipment Updates
Origin Agent: Updates shipment details in Cargowise.
Cargowise: Receives updates and sends them to SEKO360 (Load XUS).
SEKO360: Updates its system with the latest shipment information.
5. Container Event Updates
Cargowise: Tracks and updates container events.
Cargowise: Sends container event updates to SEKO360 (Load XUE).
SEKO360: Updates its system with the latest container event information.
