ISV Tech Comm primary endeavor · 2026
Mini-grid operators need to bill each home, shut off non-payers, and catch stolen power — without city-scale AMI cost. Digest: problem→solution map, tender pitfalls, what ISV publishes.
Overview (here) → Roadmap → TC2.0 review → Village scope → vendor study · register checklist.
Rural metering stalls when every vendor ships a closed bundle, tenders copy utility software requirements, and operators cannot swap gear without rewriting billing. IEEE Smart Village sits outside those product lines: neutral place to compare field evidence and publish draft specs without picking a winner. Goal: mixed meter brands on one feeder, and migration paths when a vendor exits.
Same village problems, four stacks: SteamaCo, SparkMeter / EarthSpark, EnAccess OSS, and an OpenAMI could. Empty cells = not documented this pass. Source: problem-solution-map.json.
Open map full page ↗ · SteamaCo · SparkMeter · EnAccess · OpenAMI · TC2.0 proto
Full billing-suite and 15-minute load-profile requirements in a 200-meter tender. City tools; village wallet.
Prepaid tokens, meter reads, inverter monitoring, and cloud format are different layers. One RFP line that says “all protocols” creates impossible bids.
Mesh + cloud + billing from one vendor ships fast but blocks second-source hardware and migration.
When pole uplink fails, customers still need tokens and keypads must still work. May 2026 notes.
Roadmap — installed-base interop → microgrid core → grid connectivity.
Register checklist — ~10 values every village billing case needs.
Pole gateway → JSON over MQTT so billing is written once.
Vendor study — cited tables, contacts, dead ends.
Anchor pilots compare real meters against the register checklist and JSON profile on live feeders — gap matrices operators can cite. SteamaCo (closed AMI, migration path) · Darway (pole EMS + JSON envelope).