CTD Continuous Planning Standard
CPS-1.
Version 1.0 · October 2026
A plan is not a document you make at 07:00. It is a system that has to stay right all day. CPS-1 sets out the five rules Connect the Dots is built around.
How a plan moves through Connect the Dots
01
Your systems
- TMS
- WMS
- ERP
02
Connect the Dots API
- Idempotent requests
- Asynchronous jobs
- Webhooks
03
Planning engine
- Road matrices on OpenStreetMap
- Optimization
- Plan versions
04
Back to you
- Routes per vehicle
- Arrival times
- Unplanned jobs with a reason
The clauses
-
CPS-1.1
Constraint completeness
Time windows, multiple capacity dimensions, skills such as ADR and vehicle shifts are hard requirements. A job that cannot be planned is reported with a reason, never dropped silently.
-
CPS-1.2
Cost truth
Plans are optimized against what vehicles really cost: a fixed cost per vehicle, a cost per kilometre and a cost per hour.
-
CPS-1.3
Continuous replanning
Every change during the day produces a new version of the plan. Stops that are committed or completed stay exactly where they are.
-
CPS-1.4
Traceability
Every plan records its version, input, settings and key figures, so it can be explained and reproduced. Idempotent requests make retries safe.
-
CPS-1.5
Data sovereignty
Hosted in the European Union, built on open map data, with a full export of every plan and no lock in.
How Connect the Dots implements CPS-1
Connect the Dots is built to CPS-1. Try it free for 30 days with your own data, and check each clause against your hardest planning day.