Network Architecture — IoT Infrastructure Design | EC.DATA

IoT Network Architecture Design

Designing network infrastructure for IoT energy monitoring deployments.

Architecture Components

• Edge layer — EC.Node gateways polling meters via RS-485, Ethernet, or LoRaWAN
• Network layer — VLAN-segmented Ethernet or cellular backhaul to cloud
• Cloud layer — MQTT broker, time-series database, API gateway, and analytics engine

Design Considerations

• Redundancy — dual network paths (Ethernet + cellular) for critical monitoring
• Security — TLS encryption, certificate-based authentication, firewall rules
• Scalability — one EC.Node per 50-100 meters, horizontal scaling at cloud tier
• Bandwidth — typical gateway generates 10-50 MB/month at 1-minute polling

Network Architecture in practice

Network architecture for an EC.DATA site means deciding LAN vs cellular, choosing a backup path, sizing the upstream bandwidth (5–50 kbps per gateway is typical), and documenting it on a one-page diagram the customer's IT team can sign off.

How EC.DATA operationalises Network Architecture

Network Architecture sits inside the EC.DATA delivery method as a checklisted gate — work cannot advance to the next gate until the Network Architecture acceptance criteria have been signed off in EC.Solution Design Studio. The studio prints role-specific checklists for the field tech, the project manager, and the customer-side accountable officer so nothing is left to memory.

The handover artefacts (BOM, wiring diagrams, network architecture, commissioning records) are stored against the customer site in EC.IAM. When a follow-on visit happens months later, the next technician opens the same record and continues from a known state instead of re-discovering it.

Common pitfalls when working with Network Architecture

Network Architecture fails most often when steps are skipped under schedule pressure. The EC.Solution Design Studio gates exist precisely to make those skips visible.

• Skipping the panel photographs at site audit forces a return trip when the BOM is wrong.
• Commissioning without the 24-hour shakedown ships CT-polarity errors to production dashboards.
• Handover without an EC.IAM account walk-through generates support tickets the customer's team cannot self-serve.
• Documentation written after the fact is missing the tribal knowledge that mattered most.

Where Network Architecture connects across EC.DATA

Network Architecture 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 Network Architecture

How does EC.DATA expose Network Architecture to partners?

Network Architecture sits inside the EC.Solution Design Studio gate model; checklists are printed for every role at every stage.

Do I need a separate license to access Network Architecture?

No. Network Architecture 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 Network Architecture 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 EC.Node, working alongside EC.EMS and Solution Design Studio 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.