How to Deploy an Energy Management System

Why Many Energy Management Systems Fail

Many sites already have meters, dashboards or BMS data, but energy savings are still not achieved. The common reason is that the system only displays data. It does not clearly identify waste, assign actions, track savings or create accountability.

The IoTWatt 4.0 Energy Management Workflow

IoTWatt 4.0 is designed around this workflow. It collects data from the site, applies analytics, identifies savings opportunities, creates action tickets and tracks potential, achieved and missed savings through WattSave.

Step 1: Decide What and Where to Measure

The first step is to identify Significant Energy Uses. This means finding the systems, areas or processes that consume the most energy or have the highest savings potential. Measurement should not be done randomly. It should be linked to business operations, energy cost and operational responsibility.

• Main incomers and transformer feeders
• Major distribution boards and production lines
• Chillers, cooling towers, AHUs and HVAC systems
• Compressed air systems and air compressors
• Pumps, motors, fans, blowers and process equipment
• Water, gas, BTU, steam and other utility systems
• Tenant, department, process or area-level energy usage

Step 2: Select the Right Metering and Sensors

The type of measurement device depends on what is being monitored. Electrical systems require power meters or multi-circuit meters. Chilled water systems may require BTU meters. Compressed air systems may need flow meters and pressure sensors. Water and gas systems may need pulse, analog or Modbus-enabled meters.

Step 3: Build Reliable Data Communication

Once measurement points are identified, the data must be brought into the platform reliably. This is normally done using RS485, Modbus RTU, Modbus TCP, Ethernet, WiFi, MQTT, 4G or existing EMS/BMS/SCADA connections.

• Use existing communication infrastructure where possible
• Keep RS485 networks properly segmented and documented
• Use IoT gateways where meters are far apart or not connected to BMS
• Validate data quality before using it for reporting or savings calculation
• Define suitable logging interval based on the application

Step 4: Configure IoTWatt 4.0 Data Acquisition

IoTWatt 4.0 organises data based on the actual site structure. A site can be configured by plant, building, area, process, department, equipment, utility or cost centre.

Step 5: Define EnPI and Baseline

Energy Performance Indicators convert energy data into management information. Instead of only looking at kWh, the site should define indicators that show performance against production, operating hours, cooling load, floor area, process output or other relevant drivers.

• kWh per production unit
• kWh per operating hour
• kW demand per production shift
• Chiller kW/TR or COP
• Compressed air kW per flow rate
• Energy cost per process, area or department
• Carbon emissions linked to electricity usage

Step 6: Use Analytics to Identify Savings

The real value of an EnMS is not the dashboard. The value is the ability to identify waste and act on it. IoTWatt 4.0 includes analytics for demand profile, Time-of-Use optimisation, equipment runtime, abnormal consumption, energy comparison and equipment-level performance.

Step 7: Convert Findings into Action Tickets

Many energy audits fail after the report is issued because actions are not tracked. IoTWatt 4.0 addresses this through DEES action tickets. Each finding can be assigned to a department, area, equipment owner or person-in-charge.

• Assign corrective actions to responsible users
• Track open, in-progress, completed and verified actions
• Link each ticket to estimated or verified savings
• Create management visibility on action progress
• Reduce repeated wastage caused by poor follow-up

Step 8: Track Potential, Achieved and Missed Savings

IoTWatt 4.0 uses WattSave as a savings ledger. This separates identified opportunities from actual implemented savings and highlights missed savings when actions are delayed, ignored or not sustained.

Step 9: Reporting for Management, Audit and EECA

A good EnMS must support regular management review. IoTWatt 4.0 can support daily, weekly, monthly and energy audit reporting, including EECA-related energy reporting through structured site energy data, EnPI, action tracking and savings records.

• Monthly energy performance reports
• Energy audit and digital energy audit reports
• EECA reporting support
• Management dashboards and site summaries
• Equipment-level analytics reports
• Savings ledger and action ticket summary

Conclusion

An effective Energy Management System must do more than collect data. It must create visibility, identify opportunities, assign responsibility, verify savings and support continuous improvement.

IoTWatt 4.0 provides this practical structure by combining energy monitoring hardware, IoT connectivity, digital energy audit analytics, action ticketing, savings tracking and reporting in one platform.