Customer device data is stored in a SQL Azure database. Report data resides on the Microsoft Azure Platform.
Customer device data is available for the life of the account.
The Azure platform has received numerous certifications for compliance with various security and data privacy standards. These certifications can be found at https://azure.microsoft.com/en-us/support/trust-center/.
On January 3, 2017, Microsoft announced that Microsoft Azure has received HITRUST CSF certification which incorporates healthcare specific security, privacy and regulatory requirements from existing regulations such as HIPAA/HITECH, PCI, ISO 27001 and MARS-E.1
In addition to the security of the Azure platform, TraceableLIVE® implements additional security in that all communications between TraceableLIVE® devices or users and the cloud is encrypted using the HTTPS protocol. TraceableLIVE® uses OWIN authentication. TraceableLIVE® uses a role based authorization scheme that restricts app users’ access to functions based on their role (Admin/User). TraceableLIVE® data queries are partitioned by account id, to ensure that no user will ever see data from another user account. Each TraceableLIVE® device is uniquely identified and validated by the cloud service in order for it to connect.
In addition to the security measures mentioned above, TraceableLIVE® devices, unlike the IoT devices that have been exploited in many recent security incidents, connect to Wi-Fi networks passively, making the device virtually impossible to compromise. See iOT Security post for more information.
Emails sent from TraceableLIVE® are not encrypted because most email users do not use email encryption technologies like PGP. Similarly, the SMS messages sent by TraceableLIVE® are not encrypted. All communications between users/devices and the cloud service are encrypted via HTTPS.
The cloud services and associated infrastructure for TraceableLIVE® is geo redundant and can be spun up in any Azure data center worldwide in a matter of minutes.
Microsoft also guarantees a 99.63% uptime as part of its Service Level Agreement on the weakest link in the TraceableLIVE® infrastructure The SQL Azure database backups are retained for 35 days. Databases restore points can be from 5 min – 35 days back.
Supports Chrome, Safari, Firefox, Edge, IE 10-11
iOS 8 forward and Android 4.1 forward
Out of the box, WPA2 Enterprise is not supported, however it can be custom implemented for WPA2 networks with username/password authorization methodology. WPA2 networks requiring certificate-based authorization are not supported as there is no method to load a certificate on the device.
@15min interval 2kb/hour
Inconsistent device connectivity, reduced battery life
In general, talk to your network administrator. Utilizing a business wireless router, rather than a consumer wireless router can enhance performance and help to ensure consistent and reliable connectivity.
6 months at default 15-minute communicating interval.
Communication interval, extended loss of connectivity, environmental conditions (i.e. ambient Temp), time in alarm
Initial alarm is at 20% under standard conditions and communication, 2+ weeks remaining. Reminder notifications are sent once per 24-hour period.
Change batteries within time of logging interval. Each device will maintain stored data not yet transmitted even after battery removal and replacement. Recorded data not yet transmitted to cloud will not be erased until transmission is confirmed.
It really is simple and self-explanatory. Four AAA alkaline batteries are required for device operation.
No. A device with a desired static IP address is one that you are looking to actively control from other locations. For security purposes, TraceableLIVE® devices cannot be actively controlled.
You can access the MAC address of each device during setup by placing the device into AP mode and connecting a computer or mobile device to its network and browsing to 192.168.1.1/status.html. This will allow the network administrator to identify the current IP address assigned.
No/None applicable other than replace batteries and recalibrate/replace device when calibration is expired
Not possible for an ISO 17025 accredited calibration. Non-accredited field calibrations can be completed for non-accredited calibration.
Sensors are replaceable, but as with any instrument calibration, the full system must be calibrated together if sensors are replaced.
It is very dependent on equipment and application. In general, for best uniformity of refrigeration, it is recommended to use two probes per refrigerator, one in the back nearest to the compressor/coil locations, and the other at the furthest point from that, nearest to the door. Some VFC guidance directs that a single probe be placed in the center of a refrigerator.
672 readings per channel (7 days@ 15 min interval) and 100 stored alarm events