Technical Architecture - HPL MDM Platform

01 System Architecture

Data Sources

Smart Meters

RF / GPRS / NB-IoT

→

Multiple HES Vendors

~3 per tender

→

Multi-HES Adapter

OBIS Code Mapping

↓

MDM Core

                        VEE Engine
                        Validation
                    

                        Data Store
                        Multi-tenant DB
                    

                        Event Processor
                        Alarms & Alerts
                    

                        Field Ops
                        7-Stage Lifecycle
                    

↓

Applications

Web Dashboard

Multi-tenant UI

Report Builder

Custom Reports

Energy Audit

AT&C at DT/Feeder

REST APIs

Integration Layer

↓

3 Mobile Apps

Consumer App

Bills / Prepaid / Complaints

O&M App

Field Ops / Bluetooth

Utility App

DISCOM Staff

↓

Integrations

DISCOM Billing

Per-DISCOM Adapter

CRM Systems

API Ready

SCADA / DMS

Grid Operations

02 Technology Stack

Backend

Python / Node.js

FastAPI / Express

Frontend

React.js

TypeScript / Material UI

Database

PostgreSQL + TimescaleDB

Multi-tenant Schema

Cache

Redis

In-memory / Queues

Message Queue

Apache Kafka

Event Streaming

Mobile

React Native

iOS + Android (3 Apps)

Container

Docker + Kubernetes

On-premise Ready

Cloud

GCP / AWS / Azure

Mumbai + Delhi Regions

03 API Specifications

RESTful APIs with OpenAPI 3.0 specification. Key endpoints:

Meter Data APIs

POST /api/v1/meters/readings - Ingest meter readings from HES
GET /api/v1/meters/{meter_id}/consumption - Get consumption data
GET /api/v1/meters/{meter_id}/events - Get meter events/alarms

Reporting APIs

GET /api/v1/reports/consumption - Consumption reports
GET /api/v1/reports/losses - AT&C loss calculation
GET /api/v1/reports/export - Export data (CSV/Excel/PDF)

Billing Integration APIs

GET /api/v1/billing/consumption-summary - Billing period summary
GET /api/v1/billing/validated-data - VEE processed data for billing
POST /api/v1/billing/webhook - Push billing data to external system

Field Ops APIs 7-STAGE

GET /api/v1/field-ops/meters - Get meter inventory by lifecycle stage
POST /api/v1/field-ops/work-orders - Create work order (installation/maintenance)
PUT /api/v1/field-ops/work-orders/{id}/status - Update work order status
POST /api/v1/field-ops/site-survey - Submit site survey (GPS, photos)
POST /api/v1/field-ops/commissioning - Commission meter after installation

Mobile App APIs NEW

GET /api/v1/consumer/bills - Get consumer bill history
GET /api/v1/consumer/prepaid/balance - Get prepaid balance and recharge history
POST /api/v1/consumer/complaints - Submit complaint
GET /api/v1/field/work-orders - Get assigned work orders (O&M App)
POST /api/v1/field/meter-read - Submit Bluetooth meter reading (O&M App)

04 Multi-HES Adapter Framework KEY DIFFERENTIATOR

Each DISCOM tender involves ~3 HES vendors supplying meters. Our Multi-HES Adapter Framework provides unified integration with configurable OBIS code mapping per vendor.

MDM is the Brain - HES is Data Source

The MDM platform orchestrates all meter data operations. Multiple HES systems feed data through our adapter framework, which normalizes data formats and OBIS codes to provide a unified view regardless of vendor.

Adapter Architecture	Pluggable adapter per HES vendor - Add new vendors without core code changes
OBIS Code Mapping	Configurable mapping per vendor - Same data field may have different OBIS codes across vendors; adapter normalizes to standard format
Protocol Support	REST API / MQTT / DLMS-COSEM / Proprietary protocols (per vendor requirements)
Data Normalization	Timestamp alignment, unit conversion, data quality flags - unified regardless of source
Data Push	Each HES pushes readings to MDM on configurable intervals (default: 15 minutes)
Data Pull	MDM can query any connected HES for on-demand reads and historical data
Command Routing	MDM routes commands (disconnect, reconnect, on-demand read) to correct HES based on meter mapping
Event Aggregation	Real-time event forwarding from all HES vendors to unified event processor
Security	Per-vendor API keys + IP whitelisting + TLS 1.3 encryption

HPL HES (Native):

Primary adapter for HPL's own meters. Our team will work with HPL's HES team during Discovery phase to develop native connector with full API access.

Third-Party HES:

Generic adapters for other HES vendors in tender. Configurable OBIS mapping and protocol settings per vendor without code changes.