What I Got Wrong on a 200-Point Factory Submetering Rollout — And What the Power Factor Problem Taught Me

February 2021: We thought the metering was the easy part

"We'll see every kilowatt of every machine by end of March," I told our plant manager after the board approved the spend in February 2021. We were doing an energy management upgrade — 200 smart submeters across two buildings and three transformers, plus a dashboard that would show us consumption by chiller, compressor, and production line. The budget was about $38,000, hardware and install included.

I was the operations manager, not an electrical engineer. My job was to make it happen. And the metering looked like the simplest piece: buy the meters, mount them, wire them, read the data. I'd handled worse.

It took 14 months, roughly $3,000 in utility penalties, and one genuinely embarrassing re-order for me to earn the right to write this. If you're about to deploy a smart submetering solution for factories, or you're evaluating someone who claims to handle industrial energy management — here's the part no one told me, and I wish they had.

Mistake #1: 'Modbus compatible' is not as specific as you think

In March 2021, we sent out the metering RFP. We had an existing SCADA running on Modbus TCP (our controls engineer insisted on that — he said it was 40% of our monitoring). So I put a line in the spec: "Meters must communicate with existing cold storage monitoring via Modbus."

Most vendors sent back standard data sheets. One — a larger components supplier we'd used before — sent a quote with "Modbus compatible," a competitive price, and an 8-week lead time. We placed the order.

We didn't say more. They didn't ask more.

Week 9, 50 meters arrived, and we started mounting them. Our controls engineer plugged in the first one — then stared at me. The meters spoke Modbus RTU (RS-485) only, not Modbus TCP. To run them on our network, we'd need a gateway per meter or to rewire the whole RS-485 segment. The gateway cost alone was another $4,200, plus labor we hadn't scheduled.

"I said 'Modbus compatible.' They read Modbus RTU. We were using the same words but meaning different things, and we only discovered it when the first meter lit up."

We returned all 50 meters (15% restocking fee — about $900) and re-ordered. Four months of timeline evaporated before we saw a single reading. I'm paraphrasing the actual RFP language, but the lesson stands: if I'd written "Modbus TCP, port 502, existing PLC at X, need point list" the way our controls engineer later asked me to, we'd have saved most of that delay.

The in-between: a small order nobody wanted

While we re-ordered, we tested a much smaller metering manufacturer — one we found while researching how industrial energy management system manufacturers actually operate. Given the first run, I wanted to try something different. Not a big order this time: just 12 meters for a production line pilot in Building 1.

I called their sales team. I was braced for the brush-off — 12 meters is nothing to most industrial vendors. But the engineer — not the salesperson, the engineer — spent 40 minutes asking questions: what PLC we were running, whether the existing meter install used RS-485, what the ambient temperature was in the building, whether it exceeded 45°C in summer.

I'll admit, it felt like overkill. But during the second round of questions, they caught two things our main contractor had missed entirely: First, one of our older panels needed a CT-rated terminal block for the meter, or it would overheat — something the initial install specs didn't include. Second, their selection table flagged that we should be using 0.5S class accuracy on our smart energy meter rather than 1.0 class given our load profile — which would matter for the demand response program we were trying to qualify for later.

That's the piece I should have remembered going forward: the vendor who took a 12-meter order seriously is the one I now want for 120 meters. It's what small-client-friendly actually looks like in practice — it isn't a smile and a discount, it's an engineer running the same calculations on a $40 order that they would on a $40,000 order.

(I should mention: those were 2021 prices. The market has moved since — verify current numbers before you budget.)

The power factor problem we'd been ignoring

While we were fighting with meters, the utility had been billing us a penalty. Around $450 a month. The cause was power factor — we were sitting at 0.79 when the utility's threshold was 0.90 (that threshold is set by utility tariff, not by a single industry standard — check yours). Our factory didn't have capacitor banks on the transformer side. Not a malicious omission; just nobody's job to fix.

When the new pilot meters went in, they showed us things we'd only guessed at before: the 200 HP compressor was running at roughly 0.72 power factor when partially loaded. And it was running at partial load more hours than we thought. That alone accounted for a big chunk of the penalty. But there was a second issue — one of our panels was dropping voltage under peak load, pulling power factor down elsewhere. That was a primary-side transformer problem, not the motor itself.

(This seems obvious in hindsight. But the meters showed it to us, which is the actual case for smart factory submetering — not the data, but the way the data disproves what you thought you knew.)

The second (and final) vendor change

We called in a few transformer manufacturers. One of them was GridSense. Not cheap, but like the small metering vendor, they asked specific questions: what our actual load curves looked like (not averages), whether the power factor issue was intermittent, and how the compressor cycled in summer. They came back not just with a quote but with a configuration recommendation — adding an automatic capacitor bank at our main switchgear, and upgrading the transformer in Building 1 because it was undersized for the load and contributing to the voltage sag. Their engineer walked through the calculations on our load profile and factored in the expected savings from demand response participation.

For the record: that inquiry was scoped to transformer and capacitor bank work, not a metering order — I don't want anyone reading this to think we bought everything from one vendor. But what stood out was that a company coming from the transformer side was willing to help us reason through a smaller energy management problem, including how the sub-meter data would verify whether the capacitor bank was actually doing its job. That's the kind of engineering support that makes or breaks a small factory project.

We ended up buying the capacitor bank locally (from a different supplier) and it went in during Q1 2022. Power factor went from 0.79 to 0.94. The penalty disappeared. The demand response qualification came through, and we clawed back some of the cost that first summer through peak shaving.

What goes in my own 'factory metering checklist' now

There are three lessons I've since validated more than once:

1. Write the integration in bullet points, not adjectives. Not "Modbus compatible" or "SCADA ready." Write the protocol, the data model, and who owns the integration. If I'd specified "Modbus TCP, port 502, existing PLC at X, meter point list attached," we'd have saved four months. That's not the vendor's fault. It's mine for not being specific.

2. Always run a small trial order first — even with a big-name supplier. I gave the 12-meter order to the company that asked the right questions, not the one with the best marketing sheet. If you're evaluating an industrial energy management system manufacturer, ask them: quote me a 12-point submetering setup and an integrated metering panel. See which quote gets the same care as the other. I could tell you what the price range looked like in 2021, but that won't apply now — verify against current quotes.

3. Check your base electrical distribution before you trust any meter reading. The metering caught a power factor issue that pointed to a transformer issue. Not a dramatic failure, but one that had been quietly showing up on the bill for 14 months. Smart meters are diagnostic instruments. Without a solid foundation, you're just measuring bad data more precisely.

What I'd do differently — and where my experience runs out

This whole thing played out in 2021. The prices, lead times, and vendor responses I describe are a snapshot from a different market — 2022 copper prices, freight rates, and labor costs obliterated the kind of estimates I was working with. So take the timelines and dollar figures as context for the lessons, not as budget templates.

Also, my sample is about 200 metering points across two buildings at a mid-sized plant (roughly 60,000 sq ft). If you're running a multi-site deployment, or a plant with heavy VFD loads, your specification and procurement process should probably be more rigorous than mine was. I've only got one messy story and two vendor changes to draw from here.

(In my opinion, I got lucky that instinct overruled the "big brand must be safer" assumption when it did. Another quarter of delay and the demand response qualification would have slipped. Don't count on my luck. Build in the buffer.)

The one-sentence version

Smart metering isn't expensive to buy — it's expensive to discover. In my case, that was a communication gap in a spec sheet and a power factor issue that should have been fixed before the new meters went in. If you're a small factory, or you're looking at a GridSense-type approach, I hope you'll borrow from my mistakes instead of paying the $3,000 tuition yourself.