HardTrack Alerts are configured within the Concrete Type. Typically, the same concrete type is assigned to all sensors within a HardTrack Project, except for the Ambient temperature sensor and any other sensor that you do not want to be included in the Alerts that you configure for that concrete type.
Here is an example of setting up Alerts for a Concrete Type where the Maximum concrete temperature in the Thermal Control Plan (TCP) is 160°F and the maximum temperature difference between the center/core of the concrete pour and the surface cannot exceed 35°F:
In the next example, in addition to having a Maximum concrete temperature of 180°F and having the maximum temperature difference between the center/core of the concrete pour and the surface cannot exceed 35°F, there is a specification when the forms may be removed:
Remove Forms when the temperature difference between the Core/Center Temperature and Ambient Temperature drops below 50°F and the Elapsed time of the pour reaches or exceeds 72 hours. Filling out these fields will allow the HardTrack Dashboard to snap lines in the charts that it renders to assist you with knowing when your TCP monitoring is complete. This will also add this information to the Temperature Report that you can export to Excel from HardTrack.
The frequency of repeating Alerts is controlled by setting this value on a special HardTrack Contact set up with the contact name of hardtrack_connect. This special contact is used by HardTrack to communicate with the HardTrack Cloud Server and with the devices when sending commands to them over the internet.
On the user tab for the hardtrack_connect contact, the reoccurring alert frequency is set so that the HardTrack Cloud Server, which processes the temperature readings from all of the devices being used on concrete pours, will know how often to resend the same alert for a project to your distribution list.
Here we have opened up the HardTrack Contacts, selected the hardtrack_connect contact from the drop-down. Important, Please do not alter any of the information on the Contact tab for hardtrack_connect, doing so may cause communications from your devices and/or the HardTrack Desktop software to stop working.
On the user tab of the contact, the alert frequency for reoccurring alerts can be updated. The value is expressed in minutes. The importance of this setting should not be overlooked. If the value is not set, you may receive an overwhelming number of repeating alerts every time temperature readings are uploaded from the devices to the HardTrack Cloud Server.
Advanced Alerts may also be set up within HardTrack for specifications within your TCP. It is recommended that you send a copy of your TCP to Wake and ask Wake to initially configure the Advanced Alerts for you.
HardTrack can handle a wide variety of Advanced Alerts. These can be Warnings, Advisories or Achieve Goals.
The following is just one example. Anything that you TCP calls for can be handled by HardTrack's Advanced Alerts. If your TCP calls for something very new, this is not a problem. The Advanced Alerts work as a configurator, which allows HardTrack to be set up to meet your needs.
In this example, the TCP calls for a stair step of temperature differences between the center/core and the surface, depending up the time that has elapsed in the pour: