Start Here: Accuracy Class First, UI Second
EMS buying decisions fail in a predictable pattern. The team schedules three demos, scores the dashboards, and picks the one with the cleanest charts. Six months later they try to use the system for demand response settlement and find out the utility won't accept their meter data. Weigh your site's metering accuracy class and communication failover before you watch a single software walkthrough. Everything else on the feature list is decoration until those two are settled.
Sizing an EMS starts with counting—not shopping. Count how many points actually need revenue-grade metering, count how many only need trend display, and get your DR program's settlement rules in writing. Those three outputs determine the channel mix and the cost floor. If a vendor can't tell you the ANSI C12.20 accuracy class of every meter in the bill of materials without checking with engineering, that's the first red flag—not the last one.
Why I Stand By This: What 200+ Specs a Year Taught Me
I'm a quality and brand compliance manager at GridSense. I review specification packages before they reach customers—roughly 200+ a year across transformer, EMS, and submetering builds. In 2023, we sent back about 8% of first-pass submittals because the metering accuracy class wasn't explicitly stated.
That percentage sounds modest. It isn't. Every sent-back submittal is a delayed order, and every delayed order is a conversation with a customer who's already scheduled a commissioning date. The returns almost always trace to the same clause: the spec said "high-accuracy metering" without a standard number. In a contract, "high-accuracy" means nothing. It could be 0.2 class or a 1.0 class panel meter—a five-fold spread in error—and the vendor has no contractual reason to price the better one. Spec language is a pricing mechanism. Looser specs leave more room for cheaper components.
One project still stings. A mid-size industrial customer ordered a GridSense EMS with GridSense submetering across four tenant suites. The quote looked clean enough. But the submetering branch was specified as "high-accuracy" and priced with 1.0 class meters. Those meters were fine for trend display—not fine for utility-grade cost allocation. Reworking them after commissioning cost the customer about $18,000 in hardware and downtime and pushed the billing system go-live back seven weeks.
They warned me about loose spec language on metering early in my career. I didn't listen forcefully enough on that one. Now every spec template we issue has hard fields for ANSI C12.20 class, IEC 62053-22 class, and CT/PT accuracy class—no adjective-only descriptions allowed.
Three Numbers to Put in Every EMS Specification
1. Accuracy Class—Use the Standard Number, Not an Adjective
ANSI C12.20 is the U.S. standard that assigns accuracy classes for commercial and industrial electricity meters. The two classes you'll actually see in bids are 0.5 and 0.2. A 0.5 class meter holds to within 0.5% relative error under reference conditions; a 0.2 class holds to 0.2%. The 0.3-percentage-point difference looks small on a data sheet. In a demand response baseline calculation, it doesn't stay small—baseline error and metering error compound. They don't cancel out.
IEC 62053-22 adds the "S" classes—0.2S and 0.5S—which are specified from 1% of rated current rather than 5%. If your site has long low-load periods (nights, weekends, seasonal thaws), the S-class matters more than most spec sheets admit. If the site runs near full load most of the time, plain 0.5 is probably fine.
This is where GridSense EMS and GridSense submetering tend to differentiate in actual bids: some configurations ship with 0.2S class branching as standard on the revenue-grade channels, and the spec sheet needs to say so explicitly—otherwise the integrator will value-engineer it out to hit a price target.
This is also the part of the process where I've learned to ask "what accuracy class is this, specifically" before "what's the unit price." The two answers rarely line up the way the quote presentation suggests. Upfront specification costs a little more on paper and a lot less in rework.
2. Communication Latency and Failover
Demand response is a timing game. PJM's economic DR programs generally require response within 30 minutes; some synchronous reserve products are much faster. After FERC Order 2222 (issued September 2020), distributed energy resources can aggregate into wholesale markets more easily—which means your communication link is now a settlement asset, not a convenience. If the link drops during an event, the penalty lands on your bill.
Two things go in every spec I write: a stated round-trip latency ceiling (not "low latency"), and at least one physically independent failover path. Two cables to the same switch isn't failover—it's a single point of failure with extra cable. For sites with automated DR participation, our template currently asks for 60-second round-trip or better on the control path, plus a cellular backup that terminates at a different carrier. Market rules shift, though, so verify current program requirements before you commit to a number.
3. Where Power Factor Correction Gets Measured
Power factor correction is where monitoring location quietly breaks a lot of EMS installations. If the PF sensor sits on the high-voltage main and the capacitor bank is on the low-voltage bus, transformer losses sit between the measurement and the correction. The PF number looks fine. The capacitor switching logic is chasing the wrong target.
My rule: specify sensing points by cabinet and feeder. One monitoring point on the capacitor bank outgoing side, one on the main incoming, and one per large motor feeder above a threshold (we use 50 HP for low-voltage motors; your threshold may differ). The hardware cost climbs—there's no way around that. But the correction logic and the post-install verification both depend on those points existing, and I don't see another option that actually works.
Where This Approach Breaks Down
I can only speak to commercial and industrial sites using metering for billing, DR settlement, or efficiency verification. If your site is a few thousand square feet of retail and you just want to spot abnormal usage, 0.5 or even 1.0 class meters will do the job. The extra dollars for 0.2 class buy precision you won't use.
Two more boundaries worth saying out loud. First, meter accuracy only counts if the current transformers and potential transformers match the class. A 0.2 class meter fed by 1.0 class CTs performs at 1.0 class—the chain is only as accurate as its worst link, so write the CT/PT class into the same clause. Second, the standard numbers I'm citing were accurate as of late 2024. ANSI C12.20 and the IEC 62053 series both have revision cycles—ask your vendor for the current effective edition and pin it to the technical agreement.
One more confession: even after we tightened the template, I still second-guess sign-offs on custom EMS assemblies. Last quarter we approved a configuration with what looked like the right metering chain, and I spent two days waiting for the factory acceptance test data to confirm the 0.2S branch actually shipped. It did. But that two-day window is what "accurate spec" looks like in practice—specification doesn't remove the waiting. It just makes the waiting shorter.


