Looking to provide reporting for travel time survey / TMR compliance monitoring, or have a bespoke compliance need to address with simple and effective reporting?

Mooven is approved for use in Travel Time Surveys and is data agnostic. This means we can provide a wide dataset, including a 'no hardware' option or crowdsourced data / specific data need + hardware options. We find the best fit for your compliance needs.

Find out more about these below:

The contractual requirements stipulated by Queensland Transport and Main Roads (TMR) provide a good example of clauses we typically see; a copy is shared in the appendix of our Compliance Brochure.

Our most frequently used datasets for TMR are floating vehicle data from Google and TomTom as they provide increased reliability and aren't prone to hardware faults.

A review conducted for Queensland Transport and Main Roads (TMR) found that floating vehicle data provided by Mooven didn't suffer from data gaps seen in Bluetooth data, that it more accurately represented travel times as they were less prone to noise introduced by erroneous data points or low-volume periods.

Mooven was approved as an alternative to the Bluetooth systems specified in clause 3.7 of MRTS02.1 in March 2020, and is widely used for compliance monitoring across NSW, VIC, QLD, WA, SA, ACT, New Zealand and the United States.

Google analyses the GPS, cellular and wifi-determined locations transmitted to it by mobile devices across Android and iOS platforms, in addition to connected vehicle data (where Google is used within car navigation) and third-party sources to provide accurate current live travel times. Google processes the incoming raw data about mobile phone device locations, then excludes anomalies and removes all personally identifiable information.

The travel times provided by Google are generally very accurate when compared to other forms of journey time monitoring. When insufficient data is being collected to provide live travel times, Google returns their static ‘free flow travel time’ making it easy to identify these situations. TomTom’s live travel service operates in a similar manner.

Read more about our metrics such as journey time and travel time delay here, these are found in the plan functionality of the Mooven platform.

Gaining information on sample size can be useful, however most providers do not include this information within their live traffic feeds.

Google does not provide information on market share, however, there are a range of industry reports available for different markets that consistently show Google (Google and Waze) is the most dominant mapping provider. See the example here. Similar information can be found for TomTom, Here and Inrix.

Connected vehicle data is generally not an appropriate source of volume information. Where volume is required, Mooven’s customers most frequently use telematics sites, signals data or dedicated hardware.

Sometimes, there are compliance and performance reporting obligations that require specific data sources. We incorporate a wide range of datasets, with pre-built reporting in addition to customised reporting as required.

Our pre-built reporting is effective and clear, with our goal to make compliance reporting easy and hassle free, however, we understand your need for the raw data behind the scenes and you can also download an excel file of raw data.

Mooven is data agnostic and experienced at utilising a wide range of data sources. Our team can help you assess which data sets will be most suitable for your use case and explain the trade-off associated with each option.

Common situations include the need to capture wait times of individual vehicles, individual vehicle speeds, queue monitoring, vehicle classification and lane level reporting. This is where Mooven can bring in more specific data from pre-existing sources near the site, partner data, customer data or Mooven’s existing partner network.

Some examples of these requirements may be:

In areas with high-profile works, TMR often wants to understand worst journey times in addition to the usual journey experience. Our crowdsourced data can provide percentile speeds and sample size with samples that match Bluetooth sensors, but without the expense.

Depending on the use case, there are circumstances where volume data from floating vehicle data sources can be used successfully to infer traffic counts or inform decision-making.

In these circumstances, Mooven compares volume data from the floating vehicle data providers with known telematics slides in the area to ascertain appropriate scaling factors and estimate the potential margin of error.

With this secondary verification, it is then possible to infer the count and decision that may be impacted by vehicle count within the area.

Depending on the use case, there are circumstances where volume data from floating vehicle data sources can be used successfully to infer traffic counts or inform decision-making.

In these circumstances, Mooven compares volume data from the floating vehicle data providers with known telematics slides in the area to ascertain appropriate scaling factors and estimate the potential margin of error. With this secondary verification, it is possible to infer the count and decision that may be impacted by vehicle count within the area.