# Nexora | IoT Data Planning: Devices, Dashboards & Alerts

> Plan your IoT data journey with this Nexora guide: device messages, missing readings, user roles and alert ownership before designing the dashboard.

Canonical page: https://www.nexoraesrd.com/blog/plan-a-connected-product/
Language: English

Connected systems

# IoT Data Planning: Devices, Dashboards & Alerts

A dashboard is the visible part of a connected product. Its usefulness depends on what happens before a reading reaches the screen.

Electronic test probes positioned on a printed circuit board.

[Photo credits](https://www.nexoraesrd.com/photo-credits/)

## Define the decisions your IoT data will support

Write down the decisions a user needs to make: investigate a reading, check a device, assign a follow-up or review a trend. Work backwards to the data and context each decision requires. A temperature number without a timestamp, unit or device identity can be hard to interpret.

## Define device messages, timestamps and units

Agree device identifiers, units, timestamps and error states. Decide how the receiving system distinguishes a new message from a duplicate and how it represents readings that arrive late. Keep a sample payload with the interface documentation so firmware and application teams can review the same example.

## Handle missing readings and connectivity gaps

A device that has not reported is different from one reporting a normal value. Define expected reporting intervals, stale-data behavior and how users see a connectivity gap. Include recovery scenarios when connections return rather than only testing the happy path.

## Assign alert ownership and follow-up actions

Describe who receives each alert, how it is acknowledged and what closes the follow-up. Separate a notification from a completed action. Walk through a real operational scenario with the people who will use the system before finalizing the screens.

[Explore the related service ↗](https://www.nexoraesrd.com/services/iot-connected-systems/)