EECA Reporting Starts With Data, Not a Year-End Scramble

Under Malaysia's Energy Efficiency and Conservation Act 2024 (Act 861), designated consumers must submit Energy Efficiency and Conservation Reports to Suruhanjaya Tenaga (the Energy Commission). The obligation itself is simple. The pain is self-inflicted: most sites try to reconstruct a year of energy use from twelve TNB bills in the week before the deadline. EECA reporting is a data problem first, a paperwork problem second, and the operators who treat it that way submit in an afternoon instead of a fortnight.

This guide covers what the report expects, the data you need behind it, a worked example of how continuous metering changes the work, and the CobiNeural modules that turn the whole exercise into a by-product of running the site well.

What does an EECA report actually require?

An EECA report documents your annual energy consumption, the energy management system you operate, and the energy-saving measures you are taking. That is the short version. The longer version is that every line in it assumes you already hold reliable, organised, equipment-level data. A monthly bill tells you what you spent. It does not tell you which chiller drifted off schedule in March or why the night-shift baseload crept up after a line was added.

The report is prepared and submitted by your Registered Energy Manager (REM), an employee registered with the Energy Commission who runs your energy programme. The REM's job is far easier when the figures already exist. When they don't, the REM spends the reporting window chasing numbers across spreadsheets, sub-contractor exports and half-remembered meter readings.

Suruhanjaya Tenaga sets the consumption threshold that defines a designated consumer under the Energy Efficiency and Conservation Regulations (EECR) 2024. If your site runs continuous process equipment, large chillers, or significant manufacturing load, confirm your annual energy use against the current threshold on the Energy Commission's EECA page.

Why good data is the real prerequisite for EECA reporting

EECA reporting becomes routine when energy data is captured continuously at equipment level rather than reconstructed once a year. The difference is structural, not cosmetic.

Reconstruction from bills gives you one number per month for the whole site. You cannot show a baseline you can defend, you cannot attribute consumption to specific equipment, and you cannot prove a saving measure worked because you never measured the before-and-after at the load that changed. An auditor asking "how do you know this efficiency project saved energy" gets an estimate, not evidence.

Continuous metering inverts this. The baseline, the trends, the energy performance indicators and the anomalies are already in the system the day the reporting window opens. Reporting stops being a project and becomes a query. This is the same measured backbone ISO 50001 expects, which is why building one foundation satisfies both the standard and the Act.

> Reporting should be a by-product of running the site well, not an annual reconstruction of a year you didn't measure.

What data granularity does EECA reporting need?

Meter at site level and at every major load, not just the main incomer. The single utility meter that feeds your TNB bill is enough to pay the bill and nothing more. It cannot tell you where energy goes, so it cannot support either a credible report or the savings measures the report is supposed to describe.

A practical metering hierarchy for a designated consumer looks like this:

- Main incomer for total site consumption and demand, reconciled against the TNB bill.
- Major equipment such as chiller plant, air compressors, large motors and HVAC, where most discretionary energy actually moves.
- Departments or production lines so consumption can be tied to output and energy intensity (kWh per unit produced) can be tracked.

This maps directly to the CobiNeural data hierarchy of Locations, Equipment and Sensors. For the deeper case on why the main meter alone fails operators, see why sub-metering finds the problems a monthly bill hides.

A worked example: the year-end scramble vs. the live foundation

Consider a mid-sized manufacturing site drawing roughly 250,000 kWh a month, about 3 GWh a year.

The scramble version: the REM collects twelve TNB bills, totals the kWh, and writes that the site "is implementing energy-saving measures." There is no equipment breakdown, no defensible baseline, and no quantified result. If the auditor asks for evidence behind a claimed compressor upgrade, the answer is a vendor brochure.

The live-foundation version: the same REM opens a dashboard. Annual consumption is already totalled and reconciled. The chiller plant accounts for, say, 38 percent of load; compressed air 14 percent. A scheduling fix on the chillers, logged earlier in the year, shows a measured drop in off-hours consumption with a clear before-and-after. The report writes itself because every claim has a number behind it, and the same data feeds the measurement and verification the Act and ISO 50001 both reward.

The consumption figures above are illustrative. The point is the workflow: one path produces assertions, the other produces evidence.

The CobiNeural modules that do the work

CobiNeural, Cobler's Smart Operation Platform, is built so that EECA reporting is the output, not the effort. Four parts of the platform carry it:

- Insights to Energy captures consumption, demand, maximum demand, power factor and energy intensity at location and equipment level, in real time. This is the baseline and trend data the report stands on.
- Alerts sends WhatsApp and email notifications when a load drifts, a chiller runs out of schedule, or a meter shows an anomaly, so problems are caught and logged as they happen rather than discovered in a year-end review.
- Plan and Verify runs measurement and verification on saving projects, so the "measures being taken" section of the report carries proof rather than estimates.
- Reporting generates EECA reports directly, including anomalies, energy-saving measures (ESM) and cooling degree day (CDD) outputs, alongside scheduled location and equipment reports.

CobiNeural deploys standalone or as an intelligent overlay on your existing BMS, PLC and SCADA through our automation layer, so you are not replacing working infrastructure to get reporting-ready. Manufacturers including Mosca Malaysia, Kah Hwa Industry and PWO Industries already run on it; see the case studies.

Get the measurement right and EECA reporting, ISO 50001 reviews and your ESG and net-zero disclosures all draw from one trustworthy source. The report stops being a deadline and becomes a query.

If EECA applies to your site and you are not sure your data could survive an audit, book a CobiNeural walkthrough and we will map your monitoring and reporting against the Act's requirements.