April: Temperature
The AddSecure UK development team publish feature updates and bug fixes on a monthly basis. In April, we will be launching our new Reefer solution.
Last updated
Was this helpful?
The AddSecure UK development team publish feature updates and bug fixes on a monthly basis. In April, we will be launching our new Reefer solution.
Last updated
Was this helpful?
As part of our continued investment in market leading temperature solutions, there are several significant enhancements to our temperature platform, including bug-fixes for Transcan customers and the launch of a brand new Reefer solution that works directly with ThermoKing refrigerated units.
Over the past 4 months we've been working on phase 1 of our Reefer Solution. Using our hardware attached directly to ThermoKing Ibox/Bluebox Reefer units, you can now view important temperature, unit and operational data within the platform.
We include everything from return, supply and evaporator temperatures, through to error codes, set points, fuel and runtime stats and mode.
In May, we'll be releasing new reports and alert/alarms to support reefers, and in Q3, we expect to release 2-way communication and support for Carrier devices.
The Reefer solution is an add-on and licensed. Please speak to your sales representative for more information.
Following customer feedback we've made some improvements to the Fleet Utilisation report. Previously, the report displayed utilisation based on 'time away from the home depot'. However, not all customers have named home-depots for each trailer/unit.
In the new version, we offer fleet utilisation based on actual journey time. I.e. the amount of time that each trailer is travelling.
Following feedback from some of our larger customers, we've made several improvements to the way that Transcan data is processed and displayed.
Timestamps: Transcan devices have no awareness of time-zone, and lack a method of auto-correction. This makes it difficult to store Transcan time in Verilocation. To address this, all new Transcan data being received will be processed against the account time-zone set in the customer preferences. If no time-zone is set, we will default to UTC. This change means manual recovery of historic data will now be correct.
Time Drift: Some of our customers have reported time-drift. Whilst these drifts are within the industry standard tolerances, we understand the importance of accurate timing. We have introduced new functionality that will allow our platform to automatically adjust the clock on Transcans back to the correct time. This new functionality is based on 'learning' algorithms that run daily, and autonomously. The changes will not be immediate, but over a period of 4-12 weeks, the platform will iteratively correct the clock on devices, and keep them correct going forwards.
Batch updates: Occasionally (e.g. hardware failure, cable issues), Transcan temperature readings are bunched up and sent as a batch to our servers, and on these occasions, all the records show as having the same timestamp. As a result of the timestamp and time drift fixes, we can now implement a fix for these batch updates, allowing us to accurately receive, process and report on historic temperatures. The fix is only applicable from 28th April onwards. For previous events, our technical support team can manually correct any issues.
Reporting: As a result of the changes above, it will now be possible to run scheduled and one-time reports on historical temperature events, with the reports accurately reflecting Transcan time stamps.
We have included a number of bug fixes in this release. Our support teams will be in touch with customers to notify them of relevant bug fixes.
