1. What the device health score is
The device health score combines uptime (online rate), alert frequency, data quality, and runtime into a score from 0 to 100, so the devices that need attention stand out. You can set the calculation by product type, with different weights, because industries do not judge health the same way. The score is tied into alerts, tickets, and reports. Customers in energy, manufacturing, and smart cities already use it to find high-risk devices in a large fleet.
2. What goes into the score
Uptime and time offline
Online rate and time offline both feed the score. A rolling window, such as the last 7 days, keeps an old incident from dragging the score forever.
Alert count
Alert count and KPI out-of-range events count against the score. In industry, you can raise the weight of failure count.
Firmware version and data quality
Whether firmware is current, and whether reports are complete, both count. Dimensions and weights can differ by product type.
3. A typical flow
4. How it connects to other modules
| Module | Integration capability |
|---|---|
| Alerts | A score under the threshold raises an alert, and the alert rule can be tied to that threshold |
| Tickets | A score under the threshold opens a work order and moves inspection or maintenance up the queue |
| Reports | Sort by health score. The health dashboard shows the distribution by product and region |
| API / BI | A health-score API feeds BI and operations displays, including the trend |
| Maintenance schedule | A low score adds the device to the “awaiting inspection” list on the maintenance plan |
5. How operations uses the score
In energy, the score flags batteries that are aging so they can be replaced before they fail. In manufacturing, the ranking shapes spare-parts buying and the maintenance calendar. A device under 60 can join the “awaiting inspection” list and go to the front of field work. The health dashboard shows the distribution by product and by region, which helps place people and parts. SimtoLink can tailor the model, design the rules, wire alerts and tickets, and connect the API. Contact us for support that fits your fleet.
Appendix: a score you can run in production
A health score has to leave the lab. Drill a pre-production or pilot batch that matches production for a connection storm, a full disk, certificate rotation, and a cross-region failure, and file the outcome as an acceptance checklist. Write metrics, alert thresholds, the on-call path, and audit retention into change control, so a weight or threshold change can be traced and undone without depending on one engineer. Each quarter, development, operations, security, and data should check that the score still explains business risk, and attach improvements to tickets and releases. On the SimtoLink Device Management Platform, observability, orchestration, and audit are one operating asset: the console, the open API, and export stay in use after go-live. If the score has to sit beside your ITSM, IAM, data lake, or edge cluster, the SimtoLink solutions team can join the review and return implementation notes and a risk list.