Home / Solutions

TruCount Pro Features and Alert Rules

TruCount Pro brings sensor data from buildings, industrial facilities and remote assets into one web console. Dashboards and maps help teams find a site or group, check current conditions and investigate trends. Use historical time filters to narrow a review and CSV export to share the relevant readings.

The platform supports footfall, entry and exit counts, occupancy and room presence. It also handles temperature, humidity and CO2, tank level, flow, pressure and leak detection, power and energy, door and switch states, and equipment runtime. Battery and signal readings and missing-reading alerts help teams investigate the sensors themselves.

How it works

Onboard sensors individually or in bulk, or use authenticated JSON ingest with payload mapping. Organise devices by site and group. Multi-site and multi-customer administration uses role-based access, so operators and administrators can work in the scope assigned to them. Verify the incoming measurement and unit before setting a rule for it.

Set up the dashboard around the people who will use it. The operator checking conditions needs to find the relevant site, group and sensor quickly. The person responding to an incident also needs the time and reading that caused the alert. Agree on clear names and use the same names in rules so those two views make sense together.

Example alert rule

Set a high-temperature rule for a cold store. Require the temperature to stay above its limit for ten minutes, then email the duty contact. The team checks the reading history and assigns someone to investigate the refrigeration. Configure a clear condition to follow recovery and use maintenance or suppression windows when planned work affects alert handling.

Review readings and coordinate a response

Decide who should receive an email and who will take ownership when an incident opens. Acknowledge it to show that someone is responding, then assign it if another person needs to investigate. During planned work, use a maintenance or suppression window where appropriate. After the work, check that the expected readings are arriving again.

When reviewing an incident, use a time window that includes readings before the alert and after the condition cleared. Keep the measurement and unit consistent so the comparison is meaningful. A CSV export lets a colleague inspect the same readings, while the incident record keeps the response and assignment visible to the team.

Frequently asked questions

What alert conditions are supported?

Use high or low thresholds, outside-range or sudden-change conditions, low battery, and missing readings. Configure persistence and clear conditions where applicable.

What can teams do after an alert?

Acknowledge the incident, assign someone to respond, email configured contacts and escalate when needed.

How can planned work be handled?

Use maintenance or suppression windows where appropriate to manage alerting during planned activity.

Can multiple locations and customers use the platform?

Yes. The platform supports multi-site and multi-customer administration with role-based access.

Discuss your monitoring project

Tell us what you need to monitor, where the sensors are located and who should respond when conditions change.

Contact TruCount Pro →