Incomplete mission
A missing step, contact, constraint or document forces the driver to reconstruct the instruction.
Back to CANDOR TMS
Give the driver the mission that matters.
CANDOR TMS · Driver mobility
Give the driver the mission that matters.
Make every event actionable.
CANDOR RAFIK supports the driver from mission receipt to delivery evidence, then attaches statuses, incidents and documents to the relevant transport file.
RAFIK is the CANDOR TMS driver mobility layer. The TMS retains the plan and mission; RAFIK presents useful instructions and captures field reality within the configured scope.
Office-to-field continuity
Two contexts. One transport file.
Operations prepare and arbitrate in CANDOR TMS. The driver receives, executes and documents in RAFIK. Each data point retains its source, author and role.
01 · Office · operations
CANDOR TMS composes the mission
Order, steps, instructions, constraints, allocation, expected documents and escalation rules are prepared before transmission.
Explore this context
02 · Field · driver
RAFIK documents execution
The driver reviews the mission, records milestones and qualifies authorised incidents, reservations, photos, signatures or documents.
Explore this contextOperational pressure
When the field calls instead of documenting, operations control with a delay.
Status by phone
Scattered calls and messages provide a partial view that is difficult to reconcile with the right file.
Context-free incident
A delay or exception without a reason, location, comment or attachment slows arbitration.
Fragile evidence
A photo, signature, document or reservation sent outside the flow weakens service, disputes and billing.
End-to-end driver journey
From mission receipt to closure, every milestone retains its context.
The journey adapts to the selected role, service and equipment. It assumes neither embedded navigation, offline operation nor automatic synchronisation without technical validation.
Decision lab
Test the moments when the field changes the plan.
Each scenario reconciles the latest known instruction, the field signal, decision rights and evidence to retain. RAFIK informs; arbitration remains governed.
Version, author, time, acknowledgement and affected steps01 / 04
A step or instruction changes after departure.
Context
The driver must distinguish the received version, the still-valid version and the change requiring acknowledgement.
Signals to examine
- Mission version
- Completed steps
- Change criticality
Expected decision
Notify, request a new acknowledgement or retain the previous instruction under validated rules.
Retained evidence
Version, author, time, acknowledgement and affected steps
Module capabilities
Equip the driver with the right level of information and capture.
Each capability is confirmed according to the CANDOR edition, equipment, network, rights, interfaces and expected evidence. The page describes a composable scope, not a universal promise.
Selected capability
Mission inbox
Present allocated missions to the driver with their version, priority, due time and acknowledgement state.
Mission identified before executionSystem responsibilities
Useful mobility because every system retains its responsibility.
RAFIK replaces neither the TMS, mapping, telematics nor document management. It presents and captures authorised elements, then attaches them to the CANDOR mission.
CANDOR TMS
- Owns
- Order, route, steps, allocation, version, rules and consolidated transport status.
- Exchanges
- Mission, instruction, decision, event, evidence and closure.
CANDOR RAFIK
- Owns
- Authorised display, driver capture and transmission state within the configured scope.
- Exchanges
- Acknowledgement, milestone, incident, comment, photo, signature and document.
Mapping / telematics
- Owns
- Mapping data, optional guidance, position or vehicle signal according to the selected provider.
- Exchanges
- Route, available position, mileage, timestamp and alert according to the interface.
Identity / DMS / third-party systems
- Owns
- User, device, master document, customer order, accounting or third-party reference data.
- Exchanges
- Rights, document, reference, notification and authorised status update.
Connected architecture
Useful mobility because every system retains its responsibility.
RAFIK replaces neither the TMS, mapping, telematics nor document management. It presents and captures authorised elements, then attaches them to the CANDOR mission.
Source, frequency, version and recovery are defined flow by flow.CANDORRAFIK
CANDOR TMS
Mapping
Telematics
Identity / MDM
DMS
Notifications
Customer portal
Controlled deployment
Start with one driver role, one mission and one evidence loop.
Observe
Day, tasks, calls, documents and friction
Scope
Roles, missions, steps, rights and evidence
Equip
Devices, network, security and fleet management
Connect
TMS, maps, telematics, DMS and identity
Pilot
One complete mission and its real exceptions
Extend
Roles, depots, services and continuous improvement
Resources and methods
Prepare mobility that withstands real conditions.
CANDOR TMS and RAFIK: from plan to field evidence
Position RAFIK within CANDOR editions and identify capabilities to confirm during scoping.
Download the brochure
Scope a mobile mission before choosing screens
Roles, steps, evidence, network and recovery procedures to map.
Explore guides
Handle an incident without losing the mission context
From the driver signal to the operations decision and field response.
Explore cases
Design actionable field evidence
Connect event, author, context, distribution right and decision.
Explore webinarsFrequently asked questions
Clarify the mobile scope before promising the experience.
01Is CANDOR RAFIK a standalone solution?+
RAFIK is the CANDOR TMS driver mobility layer. Its scope depends on the CANDOR edition, missions, steps, rights and selected interfaces.
02Which information can the driver receive?+
Missions, steps, addresses, windows, contacts, instructions and documents can be presented when required, available and authorised within the configured scope.
03Which elements can the driver capture?+
Depending on scope: acknowledgement, status, milestone, incident, comment, photo, signature, document and reservation. The exact list is validated role by role.
04Does RAFIK work offline?+
No generic promise is made. Offline behaviour, queues, recovery and conflicts depend on the device, version and configuration validated during the project.
05Are mapping or telematics included?+
They belong to distinct services or providers. RAFIK can exchange with them when interfaces, data, rights and responsibilities are confirmed.
06Is a photo or signature sufficient evidence?+
The value of evidence depends on the process, sold service, contractual rules and applicable legal framework. RAFIK attaches captured elements to the file; it does not determine their value alone.
07How should deployment start?+
With one driver role, one mission type, a complete journey, identified devices, real exceptions and a tested contingency procedure before extension.
Your next step
Let’s map a real mission, from first order to final evidence.
Start with one driver, one working day, network conditions and exceptions to build useful, governed and deployable mobility.