Planning under pressure
Disruptions, availability and priorities change faster than the operating plan.
Back to CANDOR TMSCentralise customer orders.
CANDOR TMS · Carrier edition
Centralise customer orders.
Prepare every mission.
Bring the customer, stops, freight, time slots and requirements into a mission ready for planning.
BEFORE CANDOR
Scattered availability and history
Re-entry, limited visibility, late trade-offs and scattered data slow operations.WITH CANDOR
Connected fleet and maintenance
Connect vehicles, documents, availability, due dates and maintenance work to operational planning.“
Every mission connects the customer commitment, allocated resources, field execution, delivery evidence and economic outcome.
CANDOR Carrier journey
From customer order through the mission’s actual outcome.
The Carrier edition connects operations, fleet, drivers, field events, evidence and billing in one shared timeline.
Qualified missionStage 01 · Prepare
Qualify order and constraints
Customer, stages, goods, time window and requirements form the mission file to be planned.
- Orders & operations. Customer files, planning, missions, stages and allocations.
- Plan. Allocate vehicles, drivers and subcontractors according to known constraints.
- Ecosystem. The role of ERP is validated during scoping.
01 / 04
Decision scenarios
The situations that reveal the journey’s value.
These scenarios make the experience concrete without turning a scoping option into a contractual commitment.
A vehicle becomes unavailable
Planning shows the impact on missions and the resources that may need to be reassigned. Define availability, escalation and replanning rights.
The driver’s connection is intermittent
Data capture and synchronisation follow the selected mobility policy. Scope offline behaviour, conflicts, timestamps and security.
Actual cost exceeds plan
The mission reconciles available fuel, subcontracting, expenses and operational events. Validate sources, calculation rules and level of detail.
Fuel consumption becomes unusual
The value is compared with the vehicle, driver, mission and available sources before analysis. Define threshold, control, justification and authorised action.
A maintenance deadline approaches
Planning reconciles availability, planned work and committed missions. Set tolerance, workshop priority and reassignment rule.
A mission is subcontracted
Order, terms, statuses, documents and service remain connected to the customer file. Define rights, evidence, cost and closure responsibility.
What holds operations back
When information fragments, operations slow down.
The starting point is not software. It is difficult decisions, repeated data entry and the areas where teams lose time or confidence.
Opaque execution
Progress still depends on calls and incomplete field information.
Late margin insight
Costs and discrepancies appear only after invoicing or mission closure.
Data Flows DecisionsExpected transformation
See, orchestrate, improve.
The target system should simplify daily work, clarify responsibilities and make exceptions actionable.
Plan
Allocate vehicles, drivers and subcontractors according to known constraints.
Execute
Share missions, milestones, incidents, documents and field evidence.
Analyse
Reconcile revenue, charges, utilisation and outcome by the relevant management axis.
What the solution puts into motion
Capabilities designed as a journey.
Each capability belongs to a business sequence. The final scope, modules, integrations and validation rules are defined during scoping.
Orders & operations
Customer files, planning, missions, stages and allocations.
View the journeyFleet & drivers
Availability, documents, constraints and useful history.
View the journeyRAFIK mobility
Missions, milestones, incidents, reservations and field POD.
View the journeySubcontracting
Allocations, exchanges, supporting documents and provider follow-up.
View the journeyBilling & analysis
Billable items, charges and an economic reading of each mission.
View the journeyFleet register & maintenance
Characteristics, mileage, preventive due dates, corrective work, interventions and immobilisation.
View the journeyDriver management
Allocations, skills, documents, time and operational events.
View the journeyFuel & costs
Consumption, expenses, anomalies and costs reconciled with available vehicles, drivers and missions.
View the journeyBilling & disputes
Time, distances, services, rates, POD and history brought together for customer control.
View the journeyAn experience that remains clear
From field execution to the cockpit.
Screens are built around tasks, exceptions and decisions. Illustrative data explains the experience and is not a contractual commitment.
- Guided, contextual workflows
- Mobility adapted to field use
- Connected alerts, actions and history
- Actionable analysis without decorative dashboards
Reference points from the supplied CANDOR Carrier copy
Expected outcomes and automation remain visible with their measurement conditions.
The following benefits and capabilities are preserved from the source. Publishing them as achieved outcomes depends on the available data, rules, interfaces and evidence.
“Take back total control” and real-time monitoring
The source promises a continuous view of activity, vehicles, drivers, missions and events. Actual coverage depends on telematics, RAFIK, partners, access rights and synchronisation frequencies.
Automatically generated invoices
The source states that invoices are generated from completed services, evidence remains accessible and customers pay faster. Workflow, controls, tax rules, approvals and the effect on payment times must be documented.
Reduce fuel spend
The source links route optimisation, consumption monitoring and driving-behaviour analysis to lower fuel use. A baseline, period, comparison method and external factors are required to measure the effect.
A better-maintained, lower-cost fleet
Preventive alerts, history, immobilisation and availability remain relevant levers. Meter triggers, parts, costs, responsibilities and the Workshop scope must be confirmed.
Carrier testimonials
The mock-up provides space for testimonials and concrete outcomes. Anonymous verbatims are allowed, but the wording, contexts, results and publication rights must come from supplied evidence.
Integrations & interoperability
Fits your ecosystem—according to your architecture.
Standard connectors are available. Coverage is confirmed by vendor, version and flow; complementary exchanges are defined during scoping.
B‑AGILEBusiness layer
ERP
Telematics
Finance
Mobility
Customers
Subcontractors
Trust principle. APIs, events, files, EDI or databases: the choice depends on criticality, volume, security and the systems concerned. Deployment can be SaaS or on-premise.Explore our principles
A controlled path
Deploy for value, not complexity.
Understand
Activities, systems, friction and goals.
Scope
Scope, data, rules and evidence.
Design
Journeys, architecture and integrations.
Pilot
A representative site or flow.
Deploy
Adoption, migration and rollout.
Improve
Measurement, support and continuous evolution.
Frequently asked questions
Useful answers before moving forward.
An answer often depends on context. When the scope is not confirmed, we say so and propose the next useful step.
Is driver mobility included?
CANDOR RAFIK covers the mobile journey; its exact scope depends on the processes, devices and exchanges selected during scoping.
Can existing telematics be integrated?
Yes, when a standard connector or available APIs cover the project’s data, rights and responsibilities.
SaaS or on-premise?
Both deployment models are available. The choice depends on the validated architecture and constraints.
Is CANDOR TMS Carrier suitable for a small fleet?
Relevance depends less on a fixed vehicle threshold than on mission, resource, billing and management complexity. An initial scope can be defined and extended progressively.
How do drivers use CANDOR RAFIK?
They can receive missions, review instructions, record milestones, report incidents and attach the expected evidence. Synchronisation and offline behaviour depend on the mobility configuration.
Can it exchange data with accounting?
Standard connectors are available. Billing data, analytical dimensions, statuses and controls are defined with the selected financial system and version.
How can fuel consumption be analysed?
Consumption can be reconciled with missions, vehicles or drivers when the source data is available. Thresholds, anomalies and authorised actions remain defined by the company.
Build the right path
Your reality deserves more than a generic demonstration.
Share your context. We will prepare a discussion focused on your flows, systems and priorities.