Hardware Selection — Choosing the Right Meters & Sensors | EC.DATA

Hardware Selection for Energy Monitoring

Choosing the right meters, sensors, and gateways for your energy monitoring project.

Selection Criteria

• Meter accuracy class — 0.2S for billing, 0.5 for energy management, 1.0 for indicative
• CT ratio — match primary current to expected load with 20% headroom
• Communication protocol — Modbus, BACnet, MQTT, or pulse output
• Environmental rating — IP20 indoor, IP65 outdoor, ATEX for hazardous areas
• Gateway capacity — number of meters, polling frequency, local storage
• Certification requirements — UL, CE, MID, revenue-grade if needed

Hardware Selection in practice

Hardware selection picks the gateway (EC.Node Mini vs Pro), comms backhaul (Ethernet vs cellular vs both), meter brand and CT ratio, and any IoT sensors. EC.Solution Design Studio renders a single BOM the partner can quote.

How EC.DATA operationalises Hardware Selection

EC.Solution Design Studio is the workbench for Hardware Selection: it walks the engineer from the audit findings (captured in EC.Audit) through the platform tier choice, hardware BOM, and proposal narrative. Each step is gated so the design that comes out is internally consistent and reviewable.

Outputs flow downstream automatically — the BOM lands in procurement, the wiring diagrams print on install day, and the commissioning checklists appear in the field tech's mobile companion. Nothing is rekeyed.

Common pitfalls when working with Hardware Selection

Hardware Selection designs go wrong when the audit data is incomplete or the partner over-engineers the solution.

• Designing with stale audit data ships hardware that does not match the panels installed.
• Specifying revenue-grade meters where monitoring meters would do drives the BOM 3-5× without analytical benefit.
• Skipping the IT-architecture conversation produces an install day that gets blocked by the customer's firewall team.
• Choosing the wrong IPMVP option upstream forces a redesign at the M&V phase.

Where Hardware Selection connects across EC.DATA

Hardware Selection touches every layer of the EC.DATA stack: telemetry capture in EC.Node; visualisation and alerting in EC.EMS with EC.Alerts; tariff translation in EC.Bills; savings verification in EC.GAIA; and field-device fleet governance in EC.IoT. Solution work originates in EC.Solution Design Studio; partner and customer training live in EC.Academy.

Frequently asked questions about Hardware Selection

How does EC.DATA expose Hardware Selection to partners?

Hardware Selection is surfaced through EC.Node telemetry capture, normalised into the EC.DATA tag schema, then made available across EC.EMS dashboards, EC.Alerts notifications, EC.Bills tariff models, and EC.GAIA savings reports — one source of truth across every module.

Do I need a separate license to access Hardware Selection?

No. Hardware Selection is part of the core EC.DATA platform; partners get it as part of their standard licence and white-label it under their own brand for their customers.

Where do I learn more about Hardware Selection on EC.DATA?

Start with the EC.Academy track this page belongs to, then explore the related EC.DATA platform modules linked above. The EC.DATA changelog announces new capabilities and the EC.Academy session catalogue tracks every recorded session.

How EC.DATA applies this in production

The concepts in this lesson are not theoretical — they are operationalised every day inside the EC.DATA platform across deployments in 10+ countries on 3 continents. The module most directly tied to this track is Solution Design Studio, working alongside EC.Node and EC.EMS to translate the underlying physics, protocols, and methodology into a working production system.

Every reading in EC.DATA flows through the same lifecycle: telemetry is captured at the meter or sensor, normalised by the EC.Node edge gateway (which speaks Modbus RTU/TCP, BACnet, OPC-UA, MQTT and pulse counting natively), buffered locally for offline resilience, then delivered to the cloud where EC.EMS stores it as 1-minute resolution time-series. From there, EC.Bills reconciles metered kWh against the utility invoice, EC.Billing allocates consumption to tenants or cost centres, EC.Alerts watches for anomalies, EC.PQ scrutinises waveform quality, and EC.GAIA applies machine learning for forecasting and root-cause analysis.

That integration is what differentiates EC.DATA from the patchwork of disconnected tools most facilities run today. Because every module shares the same data warehouse and the same role-based permission layer, a finding in one module is immediately actionable in another — a tariff change in EC.Bills can adjust demand-alert thresholds in EC.Alerts, a setpoint override in EC.BMS is automatically measured for energy impact in EC.EMS, and an IPMVP baseline is established once and reused across reports forever.

The team behind EC.DATA — described in more depth on the Who We Are page — combines former Fortune 500 energy consultants, field commissioning engineers, and software developers, with a deliberate hiring policy that requires every senior product role to have prior experience on the customer side of an energy programme. The platform is what we wish had existed when we ran those programmes ourselves; the academy is the public-domain version of the training material we built internally to bring new hires up to speed.

If you want to see the platform in action, the free assessment, the savings calculator, and the Solution Design Studio are open without an account; the partner programme is the route in for ESCOs, facility-management firms, commissioning agents, and utilities that want to deliver EC.DATA under their own brand.