The Problem Your Members Hit Every Procurement Cycle
Mini-grid and village-energy operators in Africa are trapped in a loop: every AMI vendor ships a closed bundle, every tender copies MDMS boilerplate written for national utilities, and swapping a meter OEM means rewriting your billing integration.
The result is that operators either over-buy — paying for utility-grade head-end software they will never fully use — or under-buy — running manual reads with all the revenue-loss and theft risk that entails.
The Closed-Bundle Lock-In Cycle
What OpenAMI Actually Is
OpenAMI is a geo-asset data model and a small, northbound API contract — not a product, not a head-end system, not a billing platform.
| Layer | What it specifies | What it does NOT specify |
|---|---|---|
| Asset model | Feeder → pole → meter → customer hierarchy (GeoJSON-native) | Which database, which cloud |
| Northbound contract | Lightweight MQTT topic schema; per-customer read envelope | Head-end software, billing system |
| VMRS tiers | Vendor Meter Rating Scheme — 3 tiers of field-validated capability | Which OEM to buy |
| Gateway norm | Translate vendor-specific frames at the edge; publish normalised reads | Which gateway hardware |
Architecture at a Glance
OpenAMI and Street Pole EMS are hardware threads inside ISV's shared metering practice — not certified standards, but validated field artifacts operators and vendors can point to.
Why IEEE
IEEE sits outside every product line in the mini-grid metering ecosystem. It has no meters to sell, no head-end to license, no integration margin to protect.
That neutrality is exactly what the market cannot provide itself. EnAccess, Energy IoT, and individual OEMs all have legitimate roles — none can write the contract the others must accept.
What ISV's Tech Committee Publishes
Northbound MQTT Schema
Per-customer read envelope operators and billing platforms can agree on
VMRS Tier Matrix
Vendor Meter Rating Scheme — field-validated OEM capability tiers
POC Gap Matrices
Proof-of-concept gap analysis validated on real deployments — not lab simulations
Vendor Benchmarks
OEM scorecards against the common northbound contract
OpenAMI Asset Model
GeoJSON geo-asset hierarchy — feeder to customer, migration-safe
Street Pole EMS Kit
Pole-gateway reference hardware thread inside the same metering focus
What This Means for AMDA Members Specifically
AMDA's membership spans the full mini-grid value chain. OpenAMI maps directly to the operational pain each segment faces:
🏗️ Mini-Grid Developer / IPP
Scope procurement from VMRS tier sheet instead of copying utility tender boilerplate. Avoid MDMS lock-in from day one.
⚙️ Operator / O&M Firm
Per-customer reads and prepaid billing without buying a full utility stack. Theft flag built into gateway normalisation — visible without manual reads.
🔌 Technology Integrator
Bid against a published northbound contract. Build once, deploy across operators on different OEM fleets without integration rewrites.
🏛️ Policy / DFI Stakeholder
Reference artifacts to anchor technology-neutral procurement language in concession agreements and grant conditions.
The Ecosystem Outcome ISV Is Building Toward
More Integrators Bidding
When the northbound contract is published and stable, any integrator can build to it — competitive market on implementation rather than proprietary APIs.
Operators Mix OEM Fleets
Add Hexing meters to a feeder running Calin without a parallel billing stream. The gateway normalises; the asset model tracks both.
Migration Paths When Vendors Exit
Vendor exit is a real risk in SSA. If the northbound contract is stable and the asset model is open, operators migrate to a new OEM without data loss.
Open Gateways Compete on Quality
Gateway vendors differentiate on firmware maturity, uptime, and feature velocity — not on protocol lock-in.
Reusing EPRI Open-Source Code Blocks
EPRI has published two open-source repositories under epri-dev that OpenAMI can draw from directly. Both are licensed BSD-2-Clause — compatible with ISV's open-artifact publishing model.
See the companion report EPRI Smart Grid Open-Source Stacks: Maturity Audit & Hardening Specification (EMG-TECH-015) for a full code and protocol-level review.
epri-dev/DLMS-COSEM — Gateway Normalisation Layer
A C-language DLMS/COSEM stack implementing the IEC 62056 protocol spoken by the majority of electricity meters deployed in Africa (Calin, Hexing, CHINT, Landis+Gyr, Itron). This is OpenAMI's most immediately applicable EPRI block.
Use 1 — Gateway Normalisation (Street Pole EMS): The DLMS-COSEM stack provides OBIS code resolution, COSEM object parsing, and HDLC framing — exactly the translation logic OpenAMI places at the gateway edge. This eliminates the need for each integrator to independently write a meter-frame parser.
Use 2 — VMRS Benchmark Testing: The EPRI stack can serve as a neutral reference codec in VMRS lab tests, providing an open baseline against which OEM implementations are scored for conformance.
Caveat African deployments frequently use non-standard OBIS mappings not covered by the EPRI stack's default profiles (US/European). Any reuse requires an OBIS profile registry layer on top — field validation of African profiles is ISV's added-value contribution that no commercial player has done systematically.
epri-dev/IEEE-2030.5-Client — Northbound Transport Layer
An open-source C++ client framework for IEEE 2030.5 (SEP 2.0), covering DER resource messaging, TLS/certificate handling, and scheduler logic. More narrowly applicable than the DLMS-COSEM stack, but relevant for specific integration points.
Use 1 — DER Messaging Primitives: The IEEE 2030.5 MirrorUsagePoint structures map onto OpenAMI's northbound read envelope. Gateway implementations reporting to utility SCADA or donor monitoring platforms can link against the EPRI codec rather than writing their own XML/EXI parser.
Use 2 — TLS Mutual-Authentication Scaffold: Village-energy gateways reporting to donor aggregators (e.g., USAID-funded platforms) can reuse EPRI's certificate management utilities for the northbound TLS channel.
Caveat The EPRI client targets US DER utility use cases; its scheduler and event-handling logic assumes a full head-end server on the other side. OpenAMI should adopt only the codec and transport layers — not the application stack. The SEP 2.0 profile itself may need adaptation for PAYG mini-grid semantics not present in US DER standards.
Reuse Summary Matrix
| EPRI Repo | OpenAMI Use Case | Adoption Scope | Key Gap |
|---|---|---|---|
| DLMS-COSEM | Street Pole EMS gateway frame parsing; VMRS benchmark codec | OBIS resolver + HDLC framing layer only | African OBIS profile variants need registry overlay |
| IEEE-2030.5-Client | Northbound TLS transport to utility/donor aggregators; MirrorUsagePoint codec | Codec + TLS layer only; not application scheduler | SEP 2.0 profile needs PAYG semantic adaptation |
Concrete Next Steps for AMDA
- Map your members' meter OEM fleet against the OpenAMI VMRS tier matrix — identify which vendors already publish parseable DLMS frames and which require custom gateway normalisation adapters.
- Pilot a Street Pole EMS gateway kit on one active feeder with DLMS/COSEM-capable meters, using the EPRI DLMS-COSEM stack as the parsing layer. Target a feeder where theft visibility is an active operational problem.
- Contribute field-derived African OBIS profiles back to the ISV knowledge base — this is the interoperability data the ecosystem is missing and that ISV's neutral position makes possible to aggregate.
- Embed the northbound MQTT contract in AMDA's model procurement annex so future tenders create a competitive, multi-vendor market by default — not a closed bundle competition.
Resources
IEEE Smart Village · ISV Technology Committee
OpenAMI and Street Pole EMS are reference artifacts, not certified IEEE standards.
Document reference: EMG-PITCH-019 · June 2026
🔗 Related Reports in This Suite
- EMG-PITCH-007 OpenAMI Pan-African Pitch Blueprint
The full funding pitch that this AMDA-focused document summarises. - EMG-REG-008 OpenAMI Nigeria Expansion Blueprint
Nigeria-specific strategic report for the OpenAMI regulatory engagement described here. - EMG-TRD-005 OpenAMI Smart Metering Reference Design
Technical foundation: IHM-4000 meter platform underpinning the AMDA partnership proposition.