Introduction
This page describes examples of typical booking scenarios, and the shape of the workflow that needs to be created automatically from each
Processing Order
Bookings are received from the Client into the system (e.g. via the Booking API endpoint)
Bookings need to be data-enriched as needed, to complete any vital missing information (based on who the Client is) e.g. consignor, consignee, responsible SEKO agent - this completes the Booking Model
SEKO operators see new Bookings on their dashboards, arranged in a priority order e.g. in collection / creation date ascending order
A SEKO operator selects a Booking and creates a Workflow from it
The system generates the Workflow using configured Templates that may be client-specific
Workflows from Booking Scenarios
At a Standard Task level, the system will create Workflows based on the scenario in the Booking, as per the following table, with the tasks in sequence as per the stated top-down order
Booking Scenario | Workflow Tasks |
|---|---|
Inbound Booking, SEKO not responsible for transport | RECEIVE FROM AGENT RECEIVE & PUTAWAY |
Normal Inbound Booking | TRANSPORT RECEIVE & PUTAWAY |
Outbound Booking, release to Carrier only | PICK, PACK & RELEASE HANDOVER TO AGENT |
Outbound Booking to White Glove | END CUSTOMER SCHEDULE PICK, PACK & RELEASE TRANSPORT WG PARTNER INSTRUCTION (install) |
Manufacturer straight to White Glove, no warehouse involved | END CUSTOMER SCHEDULE TRANSPORT WG PARTNER INSTRUCTION (install) |
Manufacturer straight to Site, SEKO not responsible for the White Glove install | END CUSTOMER SCHEDULE TRANSPORT HANDOVER TO AGENT |
White Glove only, SEKO not responsible for transport | END CUSTOMER SCHEDULE RECEIVE FROM AGENT WG PARTNER INSTRUCTION (install) |
Goods Transfer, between warehouses | PICK, PACK & RELEASE TRANSPORT RECEIVE & PUTAWAY |
Request to “Do a Site Survey” | WG PARTNER INSTRUCTION (site survey) |
Request to “Do a maintenance visit” | WG PARTNER INSTRUCTION (maintenance) |
Knauf Road Transport Booking | TRANSPORT |