Integration - Blog

New release with support for driver behaviour, fuel consumption and PRO 7100/9100

Tue, 14 December 2010 14:25 GMT +0200, posted by Ingo Miosga, Business Development Manager

We are about to release an update for WEBFLEET.connect that brings performance improvements to reports, makes available driver behaviour data, introduces a new geoding backend and support for the PRO 7100/9100 series devices as well as various bug fixes.

Please note that we start to phase out support for older SOAP API versions that are currently still available (1.0, 1.1, 1.2 and 1.3). Tests have shown that the newly released version 1.4 is reasonably backwards compatible and we will silently redirect requests for old versions to 1.4. Nevertheless we advise you to test your applications against 1.4 and migrate if possible. The 1.4 release of our SOAP API is not fully backwards compatible to version 0.10, so 0.10 will be around for some time. Users of that version will be approached indivdually to discuss the necessary migration steps.

Update details

Support for TomTom ecoPLUS - Fuel consumption data is now available as part of the message queue data as well as through showTripReportExtern, showTripsSummary, showVehicleReportExtern. showIdleExceptions returns idle exceptions in time and fuel usage.

Improved reporting - Some reports have seen performance improvements (showTripReportExtern, showTripSummaryReportExtern, showIOReportExtern). This has been accomplished by significant changes in our backend, so please get in touch with us should you observe any differences. Please note that the behaviour of showTripReportExtern has changed: trips are now included in the output based on the end date/time of the trip (in the past the trip start was significant for inclusion). Furthermore the output now contains address numbers of addresses matched at the trip start and end locations, making it easier for you to relate trips to activities. showStandStills replaces showStoplistReportExtern and showOrderMessageReportExtern is deprecated and should not be used anymore.

Driver behaviour data - This update makes available driver behaviour data (based on vehicle data) with two new reports: showObjectSpeedingEvents and showObjectAccelerationEvents.

Geocoding and routing - We have started a beta phase for a new geocoding backend that always uses latest maps - geocodeAddress gives access to it while geocodeAddressExtern is still available. Please not that it is still beta and we are constantly working on improvements to the lookup algorithms used to match input parameters with our map data. The new calcRouteSimpleExtern allows you to calculate estimated travel time and distance and as an option takes into account IQRoutes data. We plan to support route calculations with HDTraffic included in the future.

Programming hints

Using return values from SOAP responses - Did you know that when using SOAP, there is very detailed information about an operation's outcome available in the return of the response. The subelement errorInfo (return/errors/errorInfo) contains a precise indication of what parameter is missing or not matching validation criteria or any other information that is relevant to this specific response.

<return>
  <statusCode>9195</statusCode>
  <statusMessage>
    The request parameters for this request are invalid. Please
    make sure you provide parameters that adhere to the required structure
    (see documentation or WSDL) and the minimum amount of request data as
    documented.
  </statusMessage>
  <errors>
    <errorInfo fieldName="timeZone" objectName="GeneralParameters">
      <msg>The value can not be NULL</msg>
    </errorInfo>
  </errors>
  <resultSize>0</resultSize>
  <results xsi:nil="true"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</return>

Developer guides - Have a look at the developers guides that are available in the resource section on the API website. They go into more detail on how to work with specific parts of our API and can help you getting started more easily:

• Developer Guide - Message Queues: This guide helps you working with the WEBFLEET.connect message queues by explaining the core concept and providing usage hints.

• Developer Guide - Job Dispatch: This guide helps you understand how to send jobs to WEBFLEET and how to receive job status updates.

New solutions catalog entries

Check out the latest additions to our solutions catalog:

Beacon Software: Dispatch Anywhere

Dispatch Anywhere, a complete towing, recovery and roadside assistance internet software package that automates and tracks a job's progress through entry, dispatching and billing, uses TomTom to make communication easier. Its features include lot management, driver commissions and two-way text messaging via TomTom and/or cell phone. A call can be directly dispatched to the TomTom device in the truck, which will automatically calculate turn-by-turn directions. A driver can update call information, such as "Arrive Time" and "VIN," by a simple push of a button on the TomTom device. Read on

Tracker Management Systems: Tracker

Tracker Management has be serving towing fleets across the United States for over 24 years. Tracker offers a total management dispatch software system that is seamlessly integrated with TomTom Business Solutions offerings. Read on

Runzheimer International - Logistics Optimizer

Runzheimer International's Route Planning & Logistics, a professional route optimization and dispatch software solution suite, helps organizations with delivery route planning, installation, service or mobile healthcare fleets. Read on

The updated documentation (1.7.3) is available in the download section.

Updated support for the digital tachograph, documentation changes and some hints

Thu, 2 September 2010 15:10 GMT +0200, posted by Ingo Miosga, Business Development Manager

Recently we have released an intermediate update for WEBFLEET.connect that improves our support for the digital tachograph by making available precise timing information for messages that originate from the digital tachograph (DT). In request results, we have added event_time (eventTime in SOAP) that conveys the time a message-triggering event occured. In case of the DT, this is the LINK's local time taken from the internal clock. For users who want to be as precise as possible, we even make available the time difference between the LINK's local time and the DT time. Check out the documentation on messages for more details.

Besides that, we have fixed some minor things (localised date/time formatting, reduced the required permissions to clear text messages from devices). The revision history in the documentation has all the details.

Programming hints

Using WinINet - If you are using the WinINet functions to access WEBFLEET.connect, make sure that you force the function InternetOpenURL to always reload the page by supplying INTERNET_FLAG_RELOAD to its flags. Otherwise you might end up with outdated results from the local on-disk cache.

Using WEBFLEET.connect addresses with SOAP and Visual Basic - Due to a naming conflict (VB handles names case insensitive) there is some manual work necessary to use the addressService with VB:

• Download the WSDL file for the addressService and store it locally.

• Find this line: '<wsdl:portType name="address">' and replace 'address' by 'address_if'.

• Find this line: '<wsdl:binding name="addressServiceSoapBinding" type="tns:address">' and again replace 'address' by 'address_if'.

• Now you can create a new service reference using this WSDL file without naming conflicts.

New solutions catalog entries

Check out the latest additions to our solutions catalog:

Ideo SAP - TomTom WORK connector

Ideo facilitates organizations in achieving tangible results by mobilizing its expertise and experience in the area of service and maintenance processes in SAP. Tightly integrating jod dispatch, location updates and estimated arrival times allows their customers to gain a competitive edge. Read on

Hinze Consulting: infoBoard

Hinze Consulting has expanded it's electronic planning board software that supports users with interactive and graphical task management by adding WEBFLEET's job dispatch solution set, providing their customers with a higly efficient way to communicate with their workers out in the field. Read on

The updated documentation (1.7.2) is available in the download section.

Integration partners use video to demo products online

Wed, 22 Oct 2009 11:38 GMT +0200, posted by Ingo Miosga, Business Development Manager

Sometimes written words are just not the right tools to communicate the value of an application. It is the difference between a lengthy explanation and a hands-on experience that makes videos an interesting alternative. Searching the web for videos that relate to TomTom WEBFLEET.connect yields results that I'd like to share:

• Kommunikation mittels Tom Tom Work - Dorner Electronic BRM

• Destiny, TomTom WORK and DMS have combined forces to create JobFlow PLUS

• Create WEBFLEET addresses directly from your Outlook Contacts

• Send your Outlook Appointments to your TomTom Work Go unit

• Adressen importeren in TomTom WEBFLEET (NL) and Adressimporter für TomTom WORK (DE)

Updated Visual Basic example now uses SOAP, too

Wed, 5 Aug 2009 16:48 GMT +0200, posted by Ingo Miosga, Business Development Manager

As the previous VB example will turn 30 (months) soon, it was time to give it an update. And the availability of SOAP as a new interface transport was just about the right reason to do that.

Unfortunately, VB doesn't support MTOM encoding out of the box, so the file 'app.config' needs some tweaking after adding the service reference(s): find each occurence of the element textMessageEncoding and rename it to mtomMessageEncoding. Don't forget to reload the project after this change, otherwise VB won't recognise the changes.

The example is available in the download section.

New: driver management, event handling and address colors

Tue, 17 Feb 2009 15:25 GMT +0200, posted by Ingo Miosga, Business Development Manager

We have added new functional areas to WEBFLEET.connect:

• Drivers - a complete set of methods to manage drivers (insert, update, delete) and identify the vehicle the driver is currently signed on to.

• Events - added methods to acknowledge and reset events and extended the filter parameters

Other additions include support for address colors and editorial changes to the documentation (including message types for popQueueMessagesExtern and additions to the list of result codes).

The updated documentation is available in the download section.

Improvements to message access and object details

Tue, 28 Oct 2008 11:25 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

We always try to make it easier for developers to retrieve information to help them accomplishing their objectives. One of the things we observed is that fast and easy access to incoming messages is an important element of our API. Although this has always been the case, we are pleased to announce some major improvements to the way incoming messages can be retrieved by introducing WEBFLEET.connect Message Queues:

• Higher level of detail and data that are easier to process. More location details that enable you to create custom location descriptions, separate status information as typed in on the TomTom (id and text). Depending on device support, current navigation destination, eta and distance to (order) destination are now available.

• Improved performance. Using message queues that store messages only until retrieval (up to 14 days) enables us to offer you a shorter response time to your requests and allows you to query data at a higher rate.

In addition, we have extended the data set returned from showObjectReportExtern to include details about the current navigation destination and the order that is currently worked on.

The message queue operations supersede the showMessageReportExtern operation that is no longer part of the API. It is therefore no longer listed in the documentation, but support for it is continued until end of this year (2008-12-31).

Please note that we have updated our network: the host name connect.webfleet.tomtomwork.com now resolves to the IP address 83.133.69.51 only. As long as you are using the host name to access WEBFLEET.connect, this change is transparent for you.

The updated documentation is available in the download section.

Documentation updated

Tue, 29 July 2008 18:35 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

We have updated the documentation with some smaller clarifications regarding parameter size limits (objectno and orderno) or meaning and possible values (visible for insertAddressExtern and updateAddressExtern, userstate for showOrderMessageReportExtern). With this documentation update we introduce support for ISO8601 formatted date and time values and reworked the section that explains how to create a dedicated user account for WEBFLEET.connect.

The updated documentation is available in the download section.

RSS feed example, documentation updated

Thu, 8 May 2008 17:14 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

RSS feed example

The Perl example package just got a new member: objects2rss.pl. Use the script to create a RSS feed with current positions of all objects.

In order to get you started without having to install Perl on your system, you can use the form below to download a RSS file. You could even add the URL shown after pressing 'submit' to Google Maps. Perl source code for the CGI module we use (and that can be run standalong, too) is available as part of the Perl example package in the download section.

Documentation updated

The documentation has been updated to version 1.3.7, adding tripid-based replication to showTripReportExtern. Check out our download section.

New request limits

Thu, 24 Jan 2008 16:10 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

In order to make life easier for users who are currently limited by the static rate limit configuration, for example on the number of orders that can be send during peak load times or on the number address-related requests, the rate limiting system has been modified.

The new rate limits differentiate between functional groups and are set to reasonable defaults for most use cases. So, from now on there is a much higher rate limit for order-related methods compared to the limit for access to raw messages. If you want to learn more about the new rate limits, check out the updated documentation.

The deployment of this rate limits has already started for new users; existing users are currently not affected and only migrated on request.

Solutions Catalog

Fri, 11 Jan 2008 14:42 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

We have added a Solutions Catalog to the WEBFLEET.connect web site.

If you are looking for applications that have built-in support for WEBFLEET.connect readily available, this is the place to browse.

For existing WEBFLEET.connect integrations, we offer the opportunity to be listed in our solutions catalog - a great way to promote your product to TomTom WORK customers, dealers and everybody else looking for applications that work with WEBFLEET.

If you would like to have your solution listed here, please use the contact form to drop us a note.

Order management updated

Fri, 12 Oct 2007 16:35 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

The set of order management functions in WEBFLEET.connect has got two new members:

• showOrderMessageReportExtern - download or replicate order-related messages. This function makes available the history for an order including status changes, additional input given by the driver when sending custom order status messages and addresses matching the position of the order status message.

• reassignOrderExtern - assign a new object to an existing order and send a 'cancel order' message to the previous object.

The new functions are available to all WEBFLEET.connect-enabled accounts; the updated documentation is available in the download section.

DNS name for WEBFLEET.connect changed

Fri, 10 Aug 2007 16:35 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

We have added new computing ressources to WEBFLEET.connect that will give you even better performance than before. But in order to make use of this, you need to make some changes to your configuration: the dedicated cluster is available on a new DNS name: connect.webfleet.tomtomwork.com

So, please search your configuration for the old DNS name new.webfleet.de and replace this with the new one. You should notice the immediate improvement. The new domain name comes in conjunction with a new SSL certificate, so check your security settings too. The old system will be taken out of service by end of August. Make sure that you have applied the change by then.

We have also updated the documentation in some places, in particular, the description of showMessageReportExtern has been extended.

Replay your track with Google Earth

Thu, 24 May 2007 18:35 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

The Perl example package just got a new member: messages2kml.pl. Use the application to export a day's trip to a KML file. Open this in Google Earth, select the Path with your object id and click Play Tour.

In order to get you started without having to install Perl on your system, you can use the form below to download a day's trip as a KML file. You could even add the URL shown after pressing 'submit' as a Network Link to Google Maps My Places. Perl source code for the CGI module we use is available as part of the Perl example package in the download section.

Update: KML file example

If you do not have access to an WEBFLEET account with WEBFLEET.connect enabled, you can download a sample KML file here.

Update: Demo video

Replicating messages into a local database using Perl

Wed, 16 May 2007 15:20 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

We have released a new Perl example application that demonstrates how to export messages from WEBFLEET and store them in a local database. It is part of the WEBFLEET::connect sample package, the file name is download_messages.pl.

This makes it easy to store historic information on your disk and make it available to your back office applications. That way, your applications can benefit from Connected Navigation without the need to bind them directly to WEBFLEET.

Prerequisites

• You must have a valid WEBFLEET account with WEBFLEET.connect enabled.

• You need access to a database engine (PostgreSQL, MySQL, Oracle, ...) with privileges to create a new table.

• You must have a DBI driver module for your database within the Perl library path.

Using the example

• Create a new table messages in your database, that has the same columns as the response from showMessageReportExtern.

• Use your operating system's scheduling facility to execute the example periodically (say, every 2 or 5 minutes).

After messages start to show up in the messages table, access these with your own back office application as you like.

Learn more details about this application from the documentation included in the example file as Perl POD.

Geocoding added to WEBFLEET.connect

Mon, 7 May 2007 10:30 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

Based on popular demand (Geocoding has been asked for quite a lot, for instance), we have just updated WEBFLEET.connect with new and extended functions:

• new geocodeAddressExtern - adds geocoding to WEBFLEET.connect as a separate function

• updated showObjectReportExtern - now returns the most recent position for every object in addition to the object data.

Geocoding

Instead of integrating geocoding in multiple functions we provide a new function that returns all possible matches (if any) for the given location details. This is necessary as there might be multiple matches caused by typographic errors in the address data or an incomplete parameter set. You are responsible to make the decision on whether you just use the first row returned or let you users make the decision on which result to use.

In order to save some processing steps, geographic coordinates are returned formatted for user display as well as in a representation suitable for use with other WEBFLEET.connect functions that require geographic coordinates.

The updated documentation is available in the download section.

Using the WinHttpRequest COM object to access WEBFLEET.connect

Tue, 6 Mar 2007 10:05 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

If you are working in a high-level programming environment that does not support making HTTP connections out of the box but allows you to access COM objects, you can use the WinHttpRequest COM object to send HTTP requests and read the response. This makes it easy to integrate WEBFLEET.connect into your own applications as you can see from the Visual Basic example below:

Function WFCobjects(Account As String, UserName As String, Password As String) _
    As String
    Dim Action As String
    Dim ReqUrl As String
    Dim Req As WinHttpRequest
    
    Action = "showObjectReportExtern"
    ReqUrl = "https://connect.webfleet.tomtomwork.com/extern?lang=en"
    
    ReqUrl = ReqUrl & "&" & "account=" & Account
    ReqUrl = ReqUrl & "&" & "username=" & UserName
    ReqUrl = ReqUrl & "&" & "password=" & Password
    ReqUrl = ReqUrl & "&" & "action=" & Action
    
    Set Req = New WinHttpRequest
    Req.Open "GET", ReqUrl
    Req.Send
    WFCobjects = Req.ResponseText
End Function
      

The complete example is available in the download section.

Welcome

Tue, 13 Feb 2007 13:35 GMT +0200, posted by Ingo Miosga, Project Manager WEBFLEET.connect

Besides making the API documentation and examples available online, we plan on posting things here that focus on issues that help developers using the API:

• A list of changes that were or a will be included in API updates

• Official announcements or updates

• Techniques for using the API, including discussion of examples

• Interesting solutions that integrate with WEBFLEET.connect