Data for decision-making: dock utilization in Power BI from the TSC OData API
Time Slot Control already contains your reservation data. See how a few OData steps can load it into Power BI and turn it into a weekly view of utilization for each dock.
Latest from the world of logistics and Time Slot Control
Time Slot Control already contains your reservation data. See how a few OData steps can load it into Power BI and turn it into a weekly view of utilization for each dock.
A group can manage multiple warehouses in one Time Slot Control system without forcing every site to follow the same operating procedure. Shared settings maintain the company standard, while branch-specific action layouts adapt day-to-day processing to local conditions.
Operational communication does not end when you press Send. In Time Slot Control, we made auction email history easier to follow, removed technical HTML markup from reservation-change history in notifications, and fixed country-code selection when sending SMS.
Tenant-specific routing, richer GPS telemetry and safer position handling help dispatchers and receiving teams work with a more relevant estimated arrival time.
Four API calls are enough: obtain a Bearer token, find the reservation by ReservationNumber, and record the carrier’s arrival at and departure from the site. This practical example shows how easily Time Slot Control can connect to an ERP, WMS or gatehouse application.
On holiday, a language barrier is an inconvenience. In logistics, it can mean delays across the entire operation.
Booking alone will not solve the queue at the gate. However, when the same data continues through vehicle identification, entry, navigation around the area and Slot Monitor to the ramp, there is less manual transcription, phone calls and unnecessary waiting. In addition, a separate record of visits helps to manage the entry of people according to the rules of a specific operation.
Events from Time Slot Control go to connected systems without unnecessary polling. A delivery log, automatic retry and manual resend show what really happened to each message.