Choose an energy management system (EMS) by the building’s requirements and the system’s tested behavior, not by a “smart” label or a list of protocols. Before comparing products, define the electrical limit, the load data and signals the system may use, the resident service it must preserve, and what it does when those inputs or its network are unavailable.

“EMS” can mean charger-to-charger load sharing, an EV energy management system (EVEMS), a building-wide controller, or a system that coordinates several energy resources. Suppliers use the term differently. Ask which equipment and loads are actually inside the control boundary. A charger network that schedules sessions is not automatically measuring the building’s main supply.

Write the requirements before requesting prices

Create a short brief that answers these questions:

1. What should the system accomplish?

Choose the primary job: keep charging under a site-defined limit, allocate capacity across chargers, reduce overlap with a tariff-defined peak, use more on-site generation, participate in a named utility program, or support planned expansion. Add secondary goals only where the building can measure them. A project should not treat lower bills, added charger capacity, resident readiness and outage service as interchangeable outcomes.

2. Which data and meters does it need?

Ask the supplier to map each input to its physical source and purpose:

  • building or feeder measurements and their interval, accuracy and ownership;
  • charger and vehicle availability, charging requests and departure information;
  • the applicable utility tariff, time window or grid signal;
  • solar, battery or other building-system data, if part of the proposed control;
  • the source of each signal, how often it is updated and how stale data is detected.

Confirm that the building is allowed to provide the data and that the proposed meter sits at the boundary relevant to the control objective. Ordinary control telemetry and a meter used to calculate a resident charge are different questions; confirm local measurement rules before relying on a number for billing.

3. What can it control, and who has authority?

Request a diagram showing the system’s inputs, outputs, control boundaries and responsible parties. Confirm which charger models, firmware versions and communication features are supported. If a proposal names OCPP, OpenADR or another protocol, ask which version and functions were tested with the exact equipment. A protocol name does not prove that two vendors’ products will interoperate in the way the building needs.

Identify who can issue a charging command, who can override it, who can change settings, and who responds to a failure. Separate the building’s energy control from resident access, pricing and billing rules. For decisions involving utility programs or export to the grid, identify the utility, aggregator and approvals involved.

Conceptual control map showing building measurements, utility signals and charger requests entering an energy management system, which coordinates charger commands and support responsibilities.

Evidence progresses from an advertised feature to an exact integration test, enabled site control, measured response, and resident-service evaluation.

4. What happens when something fails?

Ask for a written failure table before signing:

Condition to test What the supplier should explain
Building meter or sensor reading is missing or stale How the system detects the problem, what approved fallback it uses and who receives an alert.
Internet, cloud service or site network is lost Which functions continue locally, which stop, and how the building restores service.
Charger stops communicating Whether it can keep charging within the approved design, and how staff identify the affected space.
Utility price or control signal is unavailable Whether the system holds, resumes or changes its schedule, and which party decides.
Power returns after an outage How equipment is restored and how the restart is tested against the approved controls.

Do not accept “fails safe” without asking what safe means for this building, which limits remain active and how residents are notified. The fallback must be designed and commissioned by qualified professionals. Do not bypass electrical protections or depend on a cloud service as the only explanation of how the installation behaves.

A failure path identifies the unavailable input or device, applies the site-designed fallback, alerts the named owner and residents, then restores and retests the system.

Protect resident service and data

Agree on what residents can expect when the system slows or shifts charging. State how the building handles departure needs, overrides, enrollment, notices, support and complaints. Include residents who do not use a smartphone or cannot respond during a control event. Ask whether charging changes are visible to residents and whether the building can explain a shortfall.

Request a clear data and security schedule: data collected, purpose, retention, sharing, access roles, encryption and security updates; who controls accounts and network credentials; how incidents are reported; and what happens to data and equipment if the supplier changes. Cybersecurity, privacy and service continuity belong in the operating contract as well as the technical proposal.

Confirm asset ownership and the exit path

For a utility-owned, leased, rebated or otherwise supported installation, map the arrangement before comparing the monthly price. Ask who owns each charger, meter, controller and fixed electrical component; who operates and maintains it; who pays for electricity, software, communications, repairs and replacements; and who receives any charging revenue or program payment. Identify the customer of record and the party responsible for resident billing and support.

Read the term and exit clauses for each asset. Record what happens at renewal, buyout, provider change, property sale or program end: whether ownership transfers, equipment must be returned or removed, what removal or restoration costs may remain, who keeps the credentials and operating data, and how service continues during the handoff. A utility or grant paying for selected equipment does not establish that all site infrastructure, ongoing costs or resident service are included. Confirm current eligibility and responsibilities in the governing tariff, participation agreement and installed-equipment schedule; an advertised offer is not proof of installed performance.

Require evidence, a demonstration and commissioning

Ask the vendor to separate a feature that exists on a product sheet from a capability tested with the proposed equipment and an outcome measured at a comparable site. Request the test conditions, time period, building and charger configuration, baseline, missing data, failures and limitations. A federal-fleet guide, demonstration project or utility pilot can help form questions, but is not an apartment performance guarantee or universal scorecard.

A commissioning evidence card records the required behavior, exact equipment, test condition, observed result, and witness or support owner.

Before acceptance, have the project’s qualified electrical and controls professionals define commissioning tests. Depending on the design, they may verify meter mapping, power-limit response, charger communication, loss and recovery of inputs, alerts, resident instructions and expansion behavior. Record who witnessed each test, the result, outstanding defects and the person responsible for remediation. Exact limits and test methods must come from the site design, applicable code and equipment instructions.

If the property is in Great Britain, check which chargepoint and load-control rules apply to the equipment, provider and use. GOV.UK’s smart-charge-point guidance covers a defined class of private domestic or workplace chargepoints in Great Britain; it does not by itself classify every shared apartment facility or establish a building-wide EMS requirement. Ofgem’s 2026 consumer-protection guidance addresses licensees providing load-control services, including suitability, control transparency, complaints and support, exit, and fees. First verify whether the provider and arrangement fall within that guidance’s scope; it is not a blanket classification of apartment EMS products. Northern Ireland and publicly accessible installations have different scope questions. Confirm current requirements with the relevant authority and qualified installer.

Local verification: General procurement guidance checked 9 November 2026. Product functions, security support, regulations, tariffs, program terms and asset ownership can change. Verify the exact equipment, agreement, service responsibilities and local rules before approval.

A useful EMS decision leaves the building with a control diagram, tested failure behavior, a resident service description, a data agreement and a named support owner. Use managed charging to set the service goal, then review building capacity and network and data requirements.