Overview
As part of the U.S. Department of Energy's Better Buildings Initiative, Legrand North America published a widely-shared retrospective titled 10 Lessons Learned Through Submetering. The document distills experience from submetering deployments across the company's manufacturing plants, distribution centers, and office buildings — a portfolio diverse enough that the lessons translate well to most commercial and industrial owners.
The ten lessons
Legrand's lessons, paraphrased, address the entire deployment lifecycle:
- Start with the questions, not the meters. Define what decisions the data will support before specifying any hardware.
- Match meter depth to the use case. A revenue-grade tenant meter, a circuit-level submeter, and a Hall-effect current sensor each have appropriate — and inappropriate — applications.
- Plan the data path before installation. Communications, storage, time synchronization, and integration with the building automation system should be designed alongside the meters, not after.
- Validate data on day one. Bad data discovered six months later is bad data that drove six months of decisions.
- Establish baselines carefully. Pre-project baselines determine the savings story for the life of the program.
- Assign owners. A meter without a human accountable for its data is a meter that drifts, fails, or gets ignored.
- Visualize for the audience. Operators, executives, and sustainability teams need different views of the same data.
- Tie data to action. Anomalies should generate work orders, not just dashboard alerts.
- Iterate the program. Early deployments inform what to instrument next; mature programs add meters where the data has driven the largest savings.
- Share the wins. Internal case studies — kWh saved, dollars avoided, equipment lifetime extended — sustain executive support and budget.
Common pitfalls
Legrand is explicit about what went wrong before it went right. The recurring pitfalls included over-instrumenting buildings where nobody was prepared to act on the data, under-specifying meter accuracy for what turned out to be billing applications, treating the metering project as an IT deliverable rather than a facilities program, and stopping at installation instead of investing in the analytics and workflows that produce savings.
Why it matters
The lessons are practical rather than theoretical, and they reinforce a consistent message from DOE, GSA, ASHRAE, and academic research: submetering produces savings only when paired with clear use cases, validated data, and human accountability.
Takeaway
For any facility team planning or scaling a submetering program, Legrand's ten lessons are a useful pre-mortem. Walking through them before specifying hardware can prevent the most common — and most expensive — mistakes.
