Technical reading

Why I Stopped Trusting Energy Management System Suppliers Who Say 'We Do Everything'

An admin buyer's honest take on why 'full-service' EMS pitches failed her factory project — and why she now shortlists vendors based on what they openly admit they don't do well.

Running an energy management project for a factory looks like a procurement problem on paper. It becomes a political problem the moment something goes wrong.

I manage vendor relationships and ordering for a roughly 400-person company across three facilities. In 2024, I got handed the job of sourcing an energy management system (EMS) to pair with our existing plant operations. I'm a buyer, not an engineer. That's exactly why I now look for one thing in every EMS vendor conversation:

I trust the supplier who says "this part isn't our strength" more than the one who promises a one-stop shop.

I know that sounds counterintuitive. Here's how I got there.

Argument 1: "Full-stack" pitches hide the deliverables that actually cause delays

In Q3 2024, we ran an RFP for a factory energy management system across two of our plants. Three vendors responded. Two pitched "end-to-end" packages: meters, software, controls, commissioning, all bundled in one contract. The third, an industrial energy management system manufacturer we'd never worked with, said flat out: "We specialize in plant-side optimization. Sensor hardware and integration are outside our lane — you'll need a partner for that."

I mentally graded that last one as a weakness. I was wrong.

We went with one of the full-stack proposals. Around week three of implementation, their software couldn't ingest data from our existing building meters — a fairly standard integration, honestly. Their project manager's answer was "that's our partner's scope." Two weeks of back-and-forth to identify the partner, then two more weeks for the API documentation to actually arrive. The optimization go-live slipped by 40 days (not 4 — 40).

Total cost of the delay, once I tallied it: roughly $2,800 in extended holding costs, rescheduled audits, and internal overtime. That was the penny-wise, pound-foolish lesson I didn't need twice. A "complete" package looks great in a proposal deck and turns into patchwork in the delivery log.

Argument 2: Generalists dilute accountability; specialists own their piece

Here's the part buyers don't talk about enough. When the "full-stack" supplier delays, the responsibility question has no clean answer. Installation was subcontracted. Integration sat with a partner. Software was in-house but second-tier priority. So "why is this late" becomes "the other party hasn't delivered." That's not necessarily a lie — but it means four meetings, three email chains, and nobody I can actually hold to a schedule.

Compare that to the specialist vendor structure. A capable industrial EMS manufacturer will scope their deliverable to their own team and tell you in writing where their scope ends. Yes, that means I have two contracts to manage instead of one. But I can point at one contract line and say "that date slipped." That's worth the extra administrative hour per month, and I'm speaking as someone who actively tries to minimize vendor count.

I still kick myself for not applying this logic in our first round. If I'd scored the bids on "clarity of scope boundary" instead of "breadth of promise," we'd have saved six weeks and thousands of dollars in churn.

Argument 3: Honest scope boundaries are a form of risk disclosure

The reason isn't sentimental. It's structural. A real commercial energy management system deployment touches metering, data analytics, control logic, commissioning, and — often — third-party audits. No single supplier I've met does all five at a high level. The industry standard most serious deployments reference, ISO 50001 (the energy management systems standard maintained by ISO), explicitly assumes cross-functional input: measurement, analysis, and verification all get audited separately. That's not a design flaw — it's the discipline in the standard.

So when a vendor says "we do everything end-to-end," what they usually mean is "we subcontract the parts we're weakest at and we manage them." Sometimes that works. Often, the weakest part is exactly the part that delays the project (like the metering protocol documentation in our case).

When a supplier says "this isn't our strength, here's who we'd recommend," they're telling me they know their own limits. That's a real signal. In procurement terms, it's the equivalent of a clean title search on a property — boring, unglamorous, and exactly what keeps you out of trouble later.

ISO 50002 (energy audits) and the IPMVP framework for measurement and verification both support this pattern: a credible EMS project has multiple specialized contributors, not a single black box. A supplier who acknowledges that is following the standard. One who doesn't is selling a story.

"But isn't one reliable partner just easier?"

Yes — when that one partner genuinely integrates the work. The problem is, most of them don't. They coordinate. Those are different businesses with different failure modes.

If a full-service energy management system supplier has an in-house metering division, an in-house controls team, and can show you a real org chart, then the single-contract model is genuinely better. Ask for it. If they can't, you're buying coordination, not integration — and you're paying a premium for a handoff.

Where that leaves me

When we re-tendered the project later in 2024, we went with a specialist energy management system manufacturer — one that specialized in plant-side energy optimization and was upfront that metering hardware and software integration were outside their scope. That sentence alone moved them from "third option" to "first shortlist." The project, when we finally ran it with them, finished on schedule within its scope. The integration piece we handled with a separate vendor whose entire job was integration.

My recommendation to any admin buyer inheriting an EMS project is simple: stop asking vendors what they can do. Ask them which projects they've declined and why. Ask them where their scope ends, in writing, on the first call.

The vendors who hesitate — or worse, say "we don't have a boundary" — are telling you something real. The ones who answer clearly are the ones I keep on the shortlist.

Note to self: I really should ask our operations team to add a "scope boundary clarity" line item to our RFP scoring sheet. Adding it next quarter — remind me.