Project Planning
Industrial IoT Dashboard Requirements Checklist
Specify dashboard data, alarms, user roles, history and acceptance tests before development.
A dashboard brief should describe the decisions operators need to make. Screens and charts are outputs of those requirements. Use this checklist to agree data meaning, response responsibilities and acceptance criteria before visual design begins.
Assets, users and decisions
List sites, asset types, devices and responsible teams. Describe three routine tasks, such as identifying an offline pump, investigating a high-temperature event or preparing a shift report. For each task, name the user, information needed and next action. Decide whether the dashboard is for monitoring only or includes control; commands require a separate permissions and safety review.
A data dictionary for every measurement
Record tag name, source, unit, scaling, valid range, sampling interval and expected delivery delay. Define invalid, missing and stale readings. Show the measurement time separately from the server receipt time when delayed uploads are possible. Example: a temperature last measured an hour ago must not appear as live simply because the web page refreshed. Specify timezone handling for logs and exports.
An alarm response matrix
For each alarm, specify trigger, delay, hysteresis, severity, recipient and escalation. Record who acknowledges it and what acknowledgement means. Include recovery notifications and maintenance suppression with an expiry. Test a signal hovering around a threshold to ensure it does not create an alert storm. A notification service failure should also be visible rather than silently treated as successful delivery.
History, reports and retention
State how long raw and aggregated data must be retained, and which users can export it. Define aggregation rules for averages, totals and peaks; these are not interchangeable. Reports should identify missing periods rather than presenting incomplete data as a full shift. Specify CSV fields, units and timezone. Estimate storage using the number of tags and sample frequency, with allowance for metadata and backups.
Access, operations and ownership
Create a role matrix for viewing sites, editing thresholds, managing devices and issuing commands. Define onboarding, account removal, audit logs and backup restoration. Name the owner for device connectivity, cloud hosting and application support. Agree expected behaviour during maintenance and upgrades. A dashboard specification is incomplete if nobody is responsible for restoring the service when a gateway or server fails.
Make the acceptance checklist executable
Demonstrate normal data, stale data, a threshold crossing, acknowledgement, loss of connection and delayed recovery. Verify access restrictions using accounts with different roles. Export a known dataset and reconcile its values and timestamps with the source. Include an agreed performance test at the expected device count. Sign off the data dictionary, alarm matrix, role matrix and test results together.
Need Help Applying This?
Baztech can assess the hardware, connectivity, software and deployment constraints for your specific project.