Custom Simacan Control Tower API integration
A control tower shows you where your trips are and whether they will arrive on time, even when they are run by different carriers. It gives you visibility that you cannot build yourself. But it only pays off if the planned trip you feed into it is correct, and if someone acts on a deviation.
What a control tower does and does not solve
The problem a control tower addresses is fragmentation. Your goods travel with several carriers, each with its own system and its own way of reporting status. The receiving location, whether a shop, a distribution centre or a customer, wants one answer to one question: when will it arrive? None of your carriers can give that answer on their own.
A control tower brings together the planned trips and the actual positions and calculates an expected arrival time from them. That is valuable, and it is also exactly where expectations go wrong: the quality of that estimate depends on what you put into it. A plan in which the stops are in the wrong order, or in which loading and unloading times are an assumption, produces an ETA that looks precise but is structurally off.
The second point is what happens when something deviates from the plan. An alert that a trip is running twenty minutes late is just information; it only becomes valuable when someone calls a shop, moves a time slot or changes the order of stops because of it. In most integrations we come across, the technology is not the bottleneck; the question is who reads the alerts and what they are allowed to decide. For what applies to personal data in transport data, see the Dutch Data Protection Authority.
How we build this
The starting point is the trip as it arises in your organisation, and the question of who will respond to a deviation later on. Without that second answer, you are building a dashboard.
Where does the planning come from, how complete is it, and what is assumption: stop sequence, loading and unloading times, time slots at the receiving end. That determines the quality of everything that follows.
Who sees an alert, what are they allowed to decide, and who informs the receiving location. That is an organisational question, and we answer it before we build, not afterwards.
Every sprint ends with something you can verify yourself, and we start with delivering planned trips and retrieving status. Passing the information on to your own systems comes afterwards.
We compare the predicted arrival times with the actual ones over a real week. Where they deviate structurally, the cause almost always lies in the planning rather than the prediction.
What the integration actually does
The exchange of trips and statuses is the foundation. What you then do with a deviation determines whether the rest has any value.
Delivering planned trips
Trips with stops, sequence and time slots from your own planning or TMS, in the format the control tower expects. We establish exactly what can be exchanged during the discovery phase; we do not promise an integration before we have seen the interface.
Progress and expected arrival fed back
Status per stop and an expected arrival time fed back into your own systems, so your customer service and your locations don't have to look at a second screen.
Deviations with an owner
A delay or a missed stop becomes an alert with a responsible person and an expected response, not a line in an overview. Without that step, it remains a dashboard that nobody opens after three weeks.
Passing information on to the receiving location
A shop or customer doesn't want trip information but a time. That translation, including what you do and don't communicate in the event of a delay, is a choice you make and we document.
Feedback to the planning
Making structural deviations visible per stop or per location, so that loading and unloading times are adjusted to what actually happens. That is where accuracy comes from in the long run.
History kept per trip
What was planned, what happened and when who was informed. In a dispute with a carrier or a customer, it is the only usable source.
Who we build for
Your position determines whether you control the planning or have it handed to you. Four situations.
Retail with its own distribution
Fixed shop routes with tight delivery time slots and staff waiting for the delivery. Here a reliable arrival time directly saves labour hours. If you also drive the last miles yourself, see last-mile delivery software.
Shippers with multiple carriers
Your goods travel with different parties using different systems. Bringing it all together is the entire value, and it is exactly what you don't want to build yourself. The planning itself often runs via a WMS or your ERP.
Manufacturers with inbound flows
Not only outbound but also inbound: when will the raw material be at the gate. If a weighbridge or site access is part of it, that belongs in the same flow; see access control and weighbridge.
Carriers reporting to shippers
You supply the data and are held to account for it. It is in your interest that what you pass on matches what your own systems say, because otherwise you end up arguing about figures instead of performance.
Technology and integrations
Position data arrives continuously, so this is a stream rather than a daily batch. The data also concerns vehicles driven by people, which makes the privacy side weigh more heavily than with a standard integration.
If you want to identify distribution centres, docks and delivery locations unambiguously in your routes using their GLN, read more about our GS1 GLN integration.
Why Appfront
The forecast is only as good as your planning
An accurate-looking arrival time on top of the wrong stop sequence is misleading. We start with the quality of what you supply.
An alert without an owner is just a dashboard
Visibility only pays off when someone is allowed to step in. We answer that question before we build.
The recipient wants a time, not a trip
What you see internally is not what a store or customer needs. The translation is a design decision in its own right, not a by-product.
Honest about what we don't know
There is no partner relationship with the supplier. We establish what is possible via the interface during discovery, and we promise nothing we haven't seen.
Security and privacy
Trip data looks purely business-related, but it isn't entirely. A vehicle is driven by a driver, and continuous position data therefore also says something about where that person is, how long they stay somewhere and how they drive. That makes it personal data, even if that is not your aim. We therefore separate the operational view from everything that can be traced back to individual behaviour, and keep the retention period for raw positions short.
If you work with a works council or with employed drivers, introduction is something to discuss beforehand, because tracking systems touch on employee monitoring. With subcontracted carriers there is also confidentiality between parties: a carrier must not be able to see how a competitor performs on the same route. Separation per party is therefore a design requirement. We also record per trip what was planned, what happened and when who was informed, because in a dispute over a missed delivery that is the only usable source. How we handle security ourselves is described in our information security policy; external reports go through our CVD policy.
Frequently asked questions about a control tower integration
Your TMS knows your own planning; a control tower brings together trips from multiple carriers and calculates a single expected arrival from them. If everything runs with one carrier in one system, the added value is limited. If your goods travel with four partners who each report differently, bringing it all together is exactly what you don't want to build yourself.
Usually not because of the forecast but because of the input. A stop sequence that differs in reality, or loading and unloading times that are an assumption rather than a measurement, produce an accurate-looking time that is structurally off. That is why we build the feedback loop: actual times per location feed back into the planning.
That depends on the interface available for your situation and your contract. We are not a partner of the supplier and do not promise an integration before we have established what is possible. That assessment is the first step; contact about it goes through you, because you hold the contract.
That is the most important question, and it is organisational, not technical. A deviation nobody reads changes nothing. That is why we build alerts with an owner and an expected response, and agree in advance who informs the receiving location. Without that, it becomes a dashboard nobody opens after three weeks.
Yes, but not in the same form. A store wants a time, not trip information. How this is passed on is a design decision in its own right: what do you communicate in the event of a delay, from what deviation onwards, and what do you keep internal? Those choices determine whether it builds trust or simply generates more phone calls.
Continuous position data is personal data, even if your focus is the shipment. We separate the operational view from anything that can be traced back to an individual's driving behaviour, and we keep the retention period for raw positions short. For employed drivers, this is also a matter for your works council.
Then that flow drops out of your view and you only have a partial overview, which is sometimes worse than none. This is a procurement conversation, not a technical problem: supplying trip data belongs in your transport agreements. We do make visible which part of your volume is and isn't covered, so you know where you are blind.
That depends on the number of carriers, the quality of your planning, and whether the translation to stores or customers is in scope. The exchange of trips and statuses is usually the smallest part; feeding back into the planning and the customer communication cost more. We give a well-founded estimate after the discovery phase. The connection to your TMS runs via integrations.
Ready to build a control tower integration?
Tell us how many carriers transport your goods and who currently makes the call when a delivery is late. The second answer usually contains the real project. We build this as part of a broader custom software project or via smart API integrations.