Scheduled trips
What is Scheduled Trips?
- Scheduled trips is an advanced and highly customizable solution to receive feedback on trips that are executed by your drivers.
- It allows integrators to create trips that use SCALAR assets, drivers, places, activity definitions and workflows.
- Non-finished parts of the trip can still be updated by the integrator to support last-minute changes during execution. The integrator can follow up on the trip by collecting all entered feedback on the trip and corresponding workflows.
- The drivers see the legs of the trips that are assigned to them and/or to their linked asset in the Cargo app. They can start and finish their work and give feedback on each action by filling in the workflow linked to the action.
- A dispatcher has an overview of all SCALAR trips by looking at the dense trips table which shows you the trips for a selected day. When more details of the trip are needed, the dispatcher can inspect the trip in the trip details side sheet.
How does Scheduled Trips work?
Scheduled trips are created by using the SCALAR datahub API’s. The following steps describe how this can be done.
- Collect all necessary data from SCALAR which needs to be provided when creating a scheduled trip. A scheduled trip needs:
- a driver ID and/or asset id for every leg in the trip.
- a place ID for every mission (optionally a non-SCALAR place can be provided as well)
- an activity definition ID and workflow ID for every action.
- Create a scheduled trip by doing a ‘create trip’ call to the scheduled trips module and sending the relevant SCALAR IDs. A successful call returns the corresponding trip ID, and the trip becomes visible on the SCALAR ‘Trips’ page.
- Each leg of the created trip is immediately shown to the relevant driver in the Cargo App as soon as:
- The driver mentioned in the leg (driverId) logs in into the Cargo App
- The asset mentioned in the leg (assetId) is linked to the logged in driver (manually or via tacho)
- The driver can start and stop the leg and execute all relevant actions.
Subscribe to trip feedback - Push
- scheduledTrips.trip.created
- scheduledTrips.trip.updated
- scheduledTrips.trip.deleted
- scheduledTrips.trip.started
- scheduledTrips.leg.started
- scheduledTrips.mission.started
- scheduledTrips.mission.eta
- scheduledTrips.action.started
- scheduledTrips.action.finished
- scheduledTrips.mission.finished
- scheduledTrips.leg.finished
- scheduledTrips.trip.finished
Updated 2 days ago