| 1. Match the measurement to the job | Confirm whether you need whole-building electricity, individual circuit, equipment, gas, water, or thermal-energy data. | List the quantities and locations to measure, then verify that the device supports the required sensor or meter inputs. | Different monitoring goals require different measurement points; a device cannot provide detail that its sensors do not capture. |
| 2. Check measurement specifications | Review stated accuracy, measurement range, supported voltage and current, and any installation or calibration requirements. | Compare the specifications with the site’s electrical system and ask how accuracy is tested and maintained. | Suitable specifications help ensure readings are useful for energy analysis and comparisons over time. |
| 3. Choose an appropriate sampling interval | Find out how often readings are measured, recorded, transmitted, and made available for export. | Check whether the interval can reveal the operational changes you need to see, and whether transmission can be configured separately from measurement. | Shorter intervals can show brief changes in load, while longer intervals may be adequate for broader consumption trends. |
| 4. Evaluate the data platform | Review dashboards, historical views, data retention, user access, export formats, and access to raw readings. | Request a sample export and confirm that timestamps, units, device identifiers, and missing-data periods are clearly represented. | Accessible, well-organized data makes it easier to investigate trends and use readings in other analysis tools. |
| 5. Verify time and data quality handling | Check timestamp format, time-zone handling, clock synchronization, duplicate readings, and how outages or gaps are shown. | Ask how the platform handles daylight-saving changes, offline devices, delayed uploads, and corrected readings. | Consistent timestamps and transparent gap handling are essential for comparing readings and aligning energy data with operations. |
| 6. Review alert options | Look for configurable thresholds, rate-of-change rules, schedules, notification channels, and alert history. | Test a sample alert and confirm who receives it, how it can be acknowledged, and whether repeated notifications can be controlled. | Useful alerts can help teams identify unusual consumption or device problems without creating excessive notifications. |
| 7. Confirm integration methods | Check supported interfaces and protocols, such as MQTT, HTTP APIs, Modbus, or BACnet, as relevant to the site. | Verify the exact protocol version, data format, authentication method, and whether a gateway or licensed connector is required. | Compatibility with existing building systems and software can reduce manual data handling and integration effort. |
| 8. Assess connectivity and offline behavior | Evaluate available wired or wireless connections, network coverage needs, buffering, and recovery after an interruption. | Ask whether readings are stored locally during a network outage and how queued data is uploaded when service returns. | Reliable data collection depends on both suitable site connectivity and a clear strategy for temporary outages. |
| 9. Review security and access controls | Examine encryption in transit, authentication, role-based permissions, update practices, and device decommissioning procedures. | Confirm how credentials are managed, how access is revoked, and how software or firmware updates are delivered. | Energy-monitoring devices and platforms should be managed as part of the organization’s broader network-security practices. |
| 10. Plan installation and future expansion | Consider enclosure and environmental requirements, installation access, commissioning steps, channel capacity, and device-management tools. | Check installation requirements with a qualified professional where needed, then pilot the setup at a representative site before scaling. | A practical pilot can expose site-specific issues and help estimate the effort needed to maintain and expand the system. |