Mini-Splits & RTUs — Small Commercial HVAC | EC.DATA

Mini-Splits & Rooftop Units

Guide to mini-split ductless systems and rooftop units for small commercial applications.

Mini-Split Systems

• Ductless design — individual indoor units with dedicated refrigerant lines
• Inverter technology — variable speed compressors for energy-efficient part-load operation
• Zoning capability — each indoor unit independently controlled
• Typical SEER ratings: 16-33 for modern inverter models

Rooftop Units (RTUs)

• Self-contained package — compressor, condenser, evaporator, and fan in one unit
• Economizer mode — free cooling when outdoor conditions permit
• Common in QSR, retail, and small commercial — 3 to 25 tons per unit
• Maintenance access from rooftop without entering occupied space

Mini Split RTU in practice

Mini-splits and packaged rooftop units are notoriously under-monitored. EC.IoT bolts a current-clamp and a wireless thermostat onto each unit so EC.EMS can rank them by COP without an expensive chiller-grade BMS retrofit.

How EC.DATA operationalises Mini Split RTU

EC.DATA captures Mini Split RTU on every supported asset class — chillers, AHUs, packaged units, VRV/VRF — through EC.Node's manufacturer adapters. Telemetry lands in EC.EMS with derived efficiency metrics (kW/TR, COP, EER, IPLV) computed in real time so an engineer never has to maintain a spreadsheet of formulas.

The EC.GAIA HVAC capstone (EC.GAIA) compares the measured efficiency band against ASHRAE-aligned benchmarks per asset class so optimisation work targets the units with the most headroom first.

Common pitfalls when working with Mini Split RTU

Mini Split RTU optimisation backfires when the underlying physics is misread.

• Raising chilled-water temperature saves chiller kWh but can raise pump and AHU fan kWh more than the chiller saves; EC.EMS shows total plant kW/TR, not chiller-only.
• Over-tightening setpoints triggers reheat in mild weather and increases consumption.
• Refrigerant top-ups without recovery records create unreported Scope-1 emissions; EC.IoT leak sensors and EC.GAIA's refrigerant ledger close the loop.
• Variable-speed retrofits without sequence-of-operations updates leave equipment running at max speed indefinitely.

Where Mini Split RTU connects across EC.DATA

Mini Split RTU 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 Mini Split RTU

How does EC.DATA expose Mini Split RTU to partners?

Mini Split RTU maps directly onto EC.EMS's HVAC asset model; chiller, AHU, and packaged-unit dashboards all consume it natively.

Do I need a separate license to access Mini Split RTU?

No. Mini Split RTU 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 Mini Split RTU 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.BMS, working alongside EC.Chillers and cold-chain monitoring 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.