Streaming ingestion
Interval reads, register reads, and signals flow in over governed Kafka topics into versioned day facts — idempotent, durable, with DLQ replay governance and full support triage tooling.
Core platform · MDMS
A complete Meter Data Management System: streaming ingestion, a three-phase VEE engine with weather-aware and machine-learned estimation, an exception workbench, master data from your systems of record, and certified, immutable data served to billing, outage operations, gas, device commands, market settlement, analytics, and regulators.
Kafka-native
Streaming Ingestion Pipeline
3-phase VEE
Validate · Estimate · Act
Electric + Gas
One pipeline, Commodity-aware
Billing-grade
Certified · Immutable · Auditable
The core of the family
Everything a utility decides — what to bill, how to treat reads through an outage, which device to disconnect, what to settle with the market — is only as good as its meter data. GDMP exists to make that data trustworthy: ingested without loss, validated by explicit rules, estimated transparently, worked through a real exception workbench, and served consistently to every consumer — then certified into bills that never change without a revision trail.
Interval reads, register reads, and signals flow in over governed Kafka topics into versioned day facts — idempotent, durable, with DLQ replay governance and full support triage tooling.
Validation rule families for register, interval, cross-channel, and extreme-value checks; action rules that estimate, flag, open exceptions, notify, or raise service orders — all behind an eligibility gate that explains every decision.
Estimation by reference day, load-profile regression, temperature correlation, and interval-register conversion — with a Spark ML estimation service and MLflow pipelines for temperature-segmented models.
A workbench for the exceptions VEE raises: assignment pools and rules, escalation policies, manual override and suppression, bulk resolution, trends, a command-day graph, and a map.
Continuous synchronization of customers, contracts, premises, devices, and channels from the systems of record — staged, validated, conformed with SCD history, and traceable payload by payload.
Raw facts, signals, and read decisions become current serving rows with replay and convergence checks — VEE, Billing, Outage, Gas, dashboards, and APIs all see one consistent answer.
Determinants for energy, demand, TOU, reactive, ratchet, CPP/RTP, and special contracts; certification and cycle close; CIS export with profiles and acknowledgements; daily extract; rebill, dispute, and hold; NEM credits; immutable ledgers; shadow reconciliation for cutover.
A first-class outage record with lifecycle, scope, evidence, and policy; outage-aware VEE treatment; holds and automatic restoration replay; outage-linked exception resolution; PSPS handling; and a command center with map.
Pressure districts, governed conversion factors (JSON, CSV, EDI 867), HDD and diurnal-profile derivation, gas VEE kernels, safety events, unaccounted-for gas, gas billing certification, dashboards, and ten standard reports.
Device commands — disconnect, reconnect, on-demand reads, pings — with CCO assignments, device criticality, request statistics, and a clean billing pull-request boundary.
Formula-driven virtual meters, submeter and check-meter context, and unmetered supply — the network the utility actually has.
Elasticsearch-backed global, master-data, and exception search; analyst inquiry over customers, premises, devices, and attributes with comments, tags, and personalization — with Whisper-Wind embedded for plain-English questions.
A standalone, read-only monitoring application: pipeline health, queue lag, worker metrics, runtime-stage logs, Grafana dashboards, and an alert catalog with drill-down queries.
A companion settlement service: zonal load and forecasts, capacity tag sets and peak events, LMP, UFE and loss factors, supplier tranches, approvals and market submissions — from the same certified usage the bills came from.
What a customer’s actual interval usage would cost under alternative rate schedules — analyzed from the platform’s own serving data.
Feature catalog, role bindings, navigation, bill cycles, day types, gate policies, retention, and system configuration through Keycloak with schema-scoped isolation; a client configuration workbook, bootstrap package, readiness gates, and rollback runbook for every new deployment.
Manual reads, meter tests, service actions, and regulated data sharing with privacy aggregation.
A feature catalog with role bindings, feature groups, and per-role navigation — governed through Keycloak.
How it works
Step 1
Head-end systems publish reads and signals onto governed Kafka topics; workers land every payload idempotently, with traceability and DLQ replay.
Step 2
Day facts are versioned and correlated with the master-data picture — customer, premise, device, channel.
Step 3
The VEE engine runs its three phases under an eligibility gate; findings become estimates, flags, exceptions, notifications, or service orders, with outage policy applied to affected days.
Step 4
Decision and serving rows refresh with replay and convergence checks — every downstream consumer reads one consistent, current answer.
Step 5
Billing determinants are certified and exported to CIS, daily extracts stream, settlement and analytics draw from the same serving data — every step observable in the Operations Monitor.
Use cases
Collect, validate, and store data from millions of smart meters as the authoritative meter data repository.
Deliver certified determinants to CIS with every estimate, edit, rebill, and hold auditable — and prove parity against the legacy system before cutover.
Treat meter data correctly through outages and PSPS events, replay on restoration, and close the exceptions an outage caused in bulk.
Run electricity and gas on one platform, with commodity-specific derivation, VEE, safety, and billing where it matters.
Coordinate disconnects, reconnects, and on-demand reads through the same governed data spine.
Settle supplier load against market data from the same certified usage the bills came from.
Green Button sharing, privacy aggregation, and full audit trails for regulator-ready reporting.
Spot missing reads, stuck meters, and estimation drift before they become revenue leakage.
Under the hood
Better together
Every family application shares one identity platform, one design system, one registration pattern, and one deployment path.
A working demonstration takes thirty minutes — on our environment or yours, with realistic simulated data.
Connect With Us