TomTom WEBFLEET Integration - Revision history

Anw: Categorisation

2025-06-20T10:02:07Z

Categorisation

← Older revision		Revision as of 12:02, 20 June 2025
Line 22:		Line 22:
	You must configure the vehicles with the TomTom WEBFLEET vehicle ID, in the ''CALIDUS'' ePOD Admin Vehicles maintenance screen.		You must configure the vehicles with the TomTom WEBFLEET vehicle ID, in the ''CALIDUS'' ePOD Admin Vehicles maintenance screen.

	<gallery widths=600px heights=200px perrow=1>		<gallery widths="600px" heights="200px" perrow="1">
	File:EPOD-Vehicles3.PNG\|''C-EPOD Vehicle Configuration''		File:EPOD-Vehicles3.PNG\|''C-EPOD Vehicle Configuration''
	</gallery><br />		</gallery><br />
Line 29:		Line 29:
	You must configure the drivers with the TomTom WEBFLEET driver ID, in the ''CALIDUS'' ePOD Admin Users maintenance screen. Note that, currently, the drivers' names must exactly match the names in TomTom WEBFLEET.		You must configure the drivers with the TomTom WEBFLEET driver ID, in the ''CALIDUS'' ePOD Admin Users maintenance screen. Note that, currently, the drivers' names must exactly match the names in TomTom WEBFLEET.

	<gallery widths=600px heights=200px perrow=1>		<gallery widths="600px" heights="200px" perrow="1">
	File:EPOD-Users3.PNG\|''C-EPOD User Configuration''		File:EPOD-Users3.PNG\|''C-EPOD User Configuration''
	</gallery><br />		</gallery><br />
Line 65:		Line 65:
	You can configure this through the settings link in the WEBFLEET application.		You can configure this through the settings link in the WEBFLEET application.

	<gallery widths=800px heights=600px perrow=1>		<gallery widths="800px" heights="600px" perrow="1">
	File:WEBFLEET-OrderWorkflow.png\|''WEBFLEET Order Workflow Configuration''		File:WEBFLEET-OrderWorkflow.png\|''WEBFLEET Order Workflow Configuration''
	</gallery><br />		</gallery><br />
Line 119:		Line 119:

	[[Category:UG 291097 EPOD Advanced Guide\|210]]		[[Category:UG 291097 EPOD Advanced Guide\|210]]
			[[Category:FAQ]]

Anw: Updated for TomTom WEBFLEET automatic logon.

2019-06-14T11:06:09Z

Updated for TomTom WEBFLEET automatic logon.

← Older revision		Revision as of 13:06, 14 June 2019
Line 12:		Line 12:

	== ''CALIDUS'' ePOD Configuration ==		== ''CALIDUS'' ePOD Configuration ==
	In order to enable this functionality, the ~~system must have~~ interfaces ~~created and enabled~~:		In order to enable this functionality, you must create and enable the following interfaces:
	* ''TomTom Orders Export'' - for sending orders to TomTom WEBFLEET.		* ''TomTom Orders Export'' - for sending orders to TomTom WEBFLEET.
	* ''TomTom Order Import'' - for receiving updates back from TomTom WEBFLEET.		* ''TomTom Order Import'' - for receiving updates back from TomTom WEBFLEET.
	* ''TomTom Geocoder'' - for geocoding locations.		* ''TomTom Geocoder'' - for geocoding locations.
			* ''TomTom Device'' - for automatic login.
	See the [[Standard Interface Configuration]] page for more details on how these are configured.		See the [[Standard Interface Configuration]] page for more details on how these are configured.


	~~The~~ vehicles ~~must be configured~~ with the TomTom WEBFLEET vehicle ID, in the ''CALIDUS'' ePOD Admin Vehicles maintenance screen.		You must configure the vehicles with the TomTom WEBFLEET vehicle ID, in the ''CALIDUS'' ePOD Admin Vehicles maintenance screen.

	<gallery widths=600px heights=200px perrow=1>		<gallery widths=600px heights=200px perrow=1>
	File:EPOD-Vehicles3.PNG\|''~~WEBFLEET Process~~ Configuration''		File:EPOD-Vehicles3.PNG\|''C-EPOD Vehicle Configuration''
	</gallery><br />		</gallery><br />


	''CALIDUS'' ePOD can also update standing data from TomTom WEBFLEET, if the TomTom WEBFLEET Orders Interface ~~has been configured~~ for the system.		You must configure the drivers with the TomTom WEBFLEET driver ID, in the ''CALIDUS'' ePOD Admin Users maintenance screen. Note that, currently, the drivers' names must exactly match the names in TomTom WEBFLEET.

			<gallery widths=600px heights=200px perrow=1>
			File:EPOD-Users3.PNG\|''C-EPOD User Configuration''
			</gallery><br />


			''CALIDUS'' ePOD can also update standing data from TomTom WEBFLEET, if you have configured the TomTom WEBFLEET Orders Interface for the system.

	In this case, the Admin Vehicles and Users Maintenance screens can import the vehicles and drivers created in WEBFLEET through an '''Import from WEBFLEET''' button in the button bar. {{Warning}} Existing vehicles and users may be updated and details over-ridden with the details from WEBFLEET, so care should be taken when using these options.		In this case, the Admin Vehicles and Users Maintenance screens can import the vehicles and drivers created in WEBFLEET through an '''Import from WEBFLEET''' button in the button bar. {{Warning}} Existing vehicles and users may be updated and details over-ridden with the details from WEBFLEET, so care should be taken when using these options.
Line 63:		Line 71:

	== Process ==		== Process ==
	Whenever ~~Customers are created~~ (either automatically or manually), the TomTom Geocoder is used to generate Latitude and Longitude co-ordinates for the location.		Whenever the system creates customers (either automatically or manually), the TomTom Geocoder is used to generate Latitude and Longitude co-ordinates for the location.

	Whenever Job Addresses ~~are created~~ (either automatically or manually), the TomTom Geocoder is used to generate Latitude and Longitude co-ordinates for the location.		Whenever the system creates Job Addresses (either automatically or manually), the TomTom Geocoder is used to generate Latitude and Longitude co-ordinates for the location.

	When a user manually allocates loads to a vehicle that is configured for TomTom WEBFLEET, the system checks that all locations on all jobs on the load (customer or job address) have a valid Lat/Long - if not, a warning is issued.		When a user manually allocates loads to a vehicle that is configured for TomTom WEBFLEET, the system checks that all locations on all jobs on the load (customer or job address) have a valid Lat/Long - if not, a warning is issued.


	When a driver logs on to the mobile device application, the application ~~will check~~ the logged-on WEBFLEET user and use this to automatically set the user for log in to the application, if the WEBFLEET user matches the user in C-ePOD. The application will also check which vehicle is assigned to the WEBFLEET user and select that vehicle if available in C-ePOD. If there are any issues during this automatic login, the user will be informed, and will always have the facility to change vehicle.		When a driver logs on to the mobile device application, the application checks the logged-on WEBFLEET user and use this to automatically set the user for log in to the application, if the WEBFLEET user matches the user in C-ePOD. The application will also check which vehicle is assigned to the WEBFLEET user and select that vehicle if available in C-ePOD. If there are any issues during this automatic login, the user will be informed, and will always have the facility to change vehicle.

Anw: Passive voice

2019-04-08T14:10:21Z

Passive voice

Show changes

Anw: Updated with TomTom WEBFLEET driver and vehicle imports

2018-12-12T15:57:47Z

Updated with TomTom WEBFLEET driver and vehicle imports

← Older revision		Revision as of 17:57, 12 December 2018
Line 24:		Line 24:
	File:EPOD-Vehicles3.PNG\|''WEBFLEET Process Configuration''		File:EPOD-Vehicles3.PNG\|''WEBFLEET Process Configuration''
	</gallery><br />		</gallery><br />


			''CALIDUS'' ePOD can also update standing data from TomTom WEBFLEET, if the TomTom WEBFLEET Orders Interface has been configured for the system.

			In this case, the Admin Vehicles and Users Maintenance screens can import the vehicles and Drivers created in WEBFLEET through an '''Import from WEBFLEET''' button in the button bar. {{Warning}} Existing vehicles and users may be updated and details over-ridden with the details from WEBFLEET, so care should be taken when using these options.

Anw: Picture resolution

2017-11-29T09:06:49Z

Picture resolution

← Older revision		Revision as of 11:06, 29 November 2017
Line 52:		Line 52:
	This can be configured through the Settings link in the WEBFLEET application.		This can be configured through the Settings link in the WEBFLEET application.

	<gallery widths=~~600px~~ heights=~~400px~~ perrow=1>		<gallery widths=800px heights=600px perrow=1>
	File:WEBFLEET-OrderWorkflow.png\|''WEBFLEET Order Workflow Configuration''		File:WEBFLEET-OrderWorkflow.png\|''WEBFLEET Order Workflow Configuration''
	</gallery><br />		</gallery><br />

Anw: Added advanced guide

2017-09-04T08:04:11Z

Added advanced guide

← Older revision		Revision as of 10:04, 4 September 2017
Line 104:		Line 104:

	The Planned Vs Actual report can be run from the Reports menu.		The Planned Vs Actual report can be run from the Reports menu.

			[[Category:UG 291097 EPOD Advanced Guide\|210]]

Anw: Added automatic login

2017-05-23T08:45:25Z

Added automatic login

← Older revision		Revision as of 10:45, 23 May 2017
Line 63:		Line 63:

	When loads are manually allocated to a vehicle that is configured for TomTom WEBFLEET, a check is made that all locations on all jobs on the load (customer or job address) have a valid Lat/Long - if not, a warning is issued.		When loads are manually allocated to a vehicle that is configured for TomTom WEBFLEET, a check is made that all locations on all jobs on the load (customer or job address) have a valid Lat/Long - if not, a warning is issued.


			When logging on to the device, the ''CALIDUS'' ePOD application will check the logged on WEBFLEET user and use this to automatically set the user for log in to the application, if the WEBFLEET user matches the user in EPOD. The application will also check which vehicle is assigned to the WEBFLEET user and select that vehicle if available in EPOD. If there are any issues during this automatic login, the user will be informed, and will always have the facility to change vehicle.


	When loads are picked up by the device and accepted (automatically or manually), the load is specified to be In Progress. If the vehicle assigned to the load is configured for WEBFLEET, any orders for the vehicle in WEBFLEET are deleted, and orders for all of the jobs on this load are generated in WEBFLEET.		When loads are picked up by the device and accepted (automatically or manually), the load is specified to be In Progress. If the vehicle assigned to the load is configured for WEBFLEET, any orders for the vehicle in WEBFLEET are deleted, and orders for all of the jobs on this load are generated in WEBFLEET.

Anw: v0.1 - Initial Draft

2017-05-23T08:25:06Z

v0.1 - Initial Draft

New page

''CALIDUS'' ePOD has strong links to TomTom WEBFLEET for:
* Geocoding locations.
* Sending Orders to WEBFLEET for In Progress trips.
* Getting updates back from WEBFLEET for Planned Vs Actual comparison.

On the device, this also allows for:
* Navigation through TomTom's NavApp directly (where there is no WEBFLEET order).
* Activating the TomTom NavApp (where there is a WEBFLEET order).
* Automatic Logon from WEBFLEET User and Vehicle.
* Capture of Vehicle ODO reading.

== ''CALIDUS'' ePOD Configuration ==
In order to enable this functionality, interfaces must be enabled:
* TomTom Orders Export - for sending orders to TomTom WEBFLEET.
* TomTom Order Import - for receiving updates back from TomTom WEBFLEET.
* TomTom Geocoder - for geocoding locations.
See the [[Standard Interface Configuration]] page for more details on how these are configured.

The Vehicles must be configured with the TomTom WEBFLEET vehicle ID, in the ''CALIDUS'' ePOD Admin Vehicles maintenance screen.

<gallery widths=600px heights=200px perrow=1>
File:EPOD-Vehicles3.PNG|''WEBFLEET Process Configuration''
</gallery><br />

It is currently recommended that Arrival Times are not enabled in ''CALIDUS'' ePOD when using WEBFLEET orders, to reduce the number of steps required to complete orders.



== TomTom WEBFLEET Configuration ==
The driver will use the WEBFLEET Order Workflow to take the order to completion. This can consist of a number of steps in WEBFLEET:
* Accept Order
* Start
* Navigate Start
* Show Route Summary
* Arrive
* Deliver Start
* Deliver End
* Complete
* Deleted
* Depart from destination
* Continue with next order

It is recommended that the Order Workflow in WEBFLEET consists of the following:
* Start
* Navigate
* Arrive
* Complete

This can be configured through the Settings link in the WEBFLEET application.

<gallery widths=600px heights=400px perrow=1>
File:WEBFLEET-OrderWorkflow.png|''WEBFLEET Order Workflow Configuration''
</gallery><br />

== Process ==
Whenever Customers are created (either automatically or manually), the TomTom Geocoder is used to generate Latitude and Longitude co-ordinates for the location.

Whenever Job Addresses are created (either automatically or manually), the TomTom Geocoder is used to generate Latitude and Longitude co-ordinates for the location.

When loads are manually allocated to a vehicle that is configured for TomTom WEBFLEET, a check is made that all locations on all jobs on the load (customer or job address) have a valid Lat/Long - if not, a warning is issued.

When loads are picked up by the device and accepted (automatically or manually), the load is specified to be In Progress. If the vehicle assigned to the load is configured for WEBFLEET, any orders for the vehicle in WEBFLEET are deleted, and orders for all of the jobs on this load are generated in WEBFLEET.

Within the ''CALIDUS'' ePOD Mobile application, when a job is started, the device will display a WEBFLEET icon instead of the normal Navigation Map Icon.

Clicking this WEBFLEET icon will activate the WEBFLEET app directly, where the order can be selected from the list of orders.

The driver will follow the WEBFLEET process steps to take the order to completion. It is expected that the process steps in WEBFLEET consist of the following:
* Start
* Navigate
* Arrive
* Complete

Arrival can be automatic based on the arrival to the Lat/Long location provided.

If the order does not exist in the list of orders, navigation instructions can still be sent to the TomTom NavApp. The user can return to the ''CALIDUS'' ePOD application and long-press on the WEBFLEET button. This allows the user to select sending the address directly to the TomTom NavApp, for either just this job or for all jobs on the load.

The address is sent directly to the TomTom NavApp, which will immediately start navigation to this address.

Once navigation is complete, the user will switch back to the ''CALIDUS'' ePOD application, using the shortcut on the status bar. The ePOD application can then be used to complete the order.

When complete, the user can switch back to the WEBFLEET app immediately to complete the order workflow, or can select the next job in the ePOD Job List and use the WEBFLEET button there.

If the ''CALIDUS'' ePOD application is not configured for WEBFLEET orders, the TomTom NavApp can still be used for direct navigation. The user can press on the Navigation icon, and the address is sent directly to the TomTom NavApp, which will immediately start navigation to this address. If a Lat/Long has not been provided for the address, this will be geocoded at this time, if possible.

As process steps are completed in TomTom WEBFLEET (e.g. Start, Arrival, Complete, Break), this information can be picked up by ''CALIDUS'' ePOD and stored for later Planned Vs Actual Comparison. Details stored:
* Auditing of all events
* Breaks created
* Distance (ODO)
* Time

The Planned Vs Actual report can be run from the Reports menu.