← Back to Proposal

HPL MDM Platform Workflow

End-to-end data flow from smart meters to consumer payments

💡
High-Level Architecture Blueprint

This workflow represents our proven MDM architecture pattern. During the Discovery Phase, we will collaborate closely with HPL's technical team to tailor every component to your specific HES configurations, business rules, and operational requirements.

1 Data Collection Layer

⚡ Smart Meters

RF / GPRS / NB-IoT

↓

HPL HES

Primary

Vendor 2 HES

Per tender

Vendor 3 HES

Per tender

Each DISCOM tender typically has ~3 HES vendors with different data formats

↓

🔗 Multi-HES Adapter

OBIS Code Mapping & Normalization

★ Translates different vendor formats into unified MDM format

2 MDM Core Processing

⚙ VEE Engine

Validation, Estimation, Editing

✓ Validation
  • Range checks
  • Spike detection
  • Missing data flags
  • Consistency rules
📈 Estimation
  • Fill data gaps
  • Interpolation
  • Historical patterns
  • Weather correlation
✏ Editing
  • Manual overrides
  • Approval workflows
  • Audit trail
  • Exception handling
Validated Data

🗃 Data Aggregation

Meter → DT → Feeder → Substation → DISCOM

3 Analytics, Reports & Field Operations

📊

Analytics

  • Energy Audit
  • AT&C Loss
  • DT/Feeder Analysis
📈

Operations

  • Live Dashboard
  • Alert Management
  • Exception Queue
📄

Reports

  • 48+ RDSS Reports
  • Custom Builder
  • Scheduled Export
🛠

Field Ops

7-Stage Meter Lifecycle

1. Site Survey
→
2. Installation
→
3. Commissioning
→
4. Active Ops
→
5. Maintenance
→
6. Replacement
→
7. Decommission

4 Output Channels - Apps & Portal

📱

Consumer App

  • View bills
  • Pay online
  • Usage trends
  • Prepaid recharge
  • Raise complaints
🔧

O&M App

  • Work order queue
  • GPS navigation
  • Photo capture
  • Bluetooth meter comm
  • Status updates
🏢

Utility App

  • Mobile dashboards
  • Alert management
  • Meter lookup
  • Quick reports
  • KPI tracking
💻

Consumer Portal

  • Web-based access
  • Bill download
  • Payment history
  • Usage analytics
  • Multi-language

5 Payment Flow - Who Receives the Money?

👤

Consumer

Views bill, clicks Pay

→
📱

Consumer App/Portal

Built by Trinesis

→
💳

Payment Gateway

DISCOM's Razorpay/PayU

→
🏢

DISCOM Bank

Money lands here

💡 Key Point

DISCOM receives the payment, NOT HPL. HPL provides the technology platform. Each DISCOM configures their own payment gateway. MDM is a passthrough - it never touches the money.

⚙ HPL (Technology Provider)

  • Sells meters + HES + MDM platform
  • Provides Consumer App (white-labeled)
  • MDM sends validated consumption data
  • No involvement in money flow
  • Earns from platform sale

🏢 DISCOM (Utility)

  • Owns the consumers
  • Generates bills (tariff, calculations)
  • Receives all consumer payments
  • Has payment gateway account
  • Responsible for customer service

Per-DISCOM Payment Gateway Configuration

DISCOM A (Bihar)

Razorpay → Bank A

DISCOM B (UP)

PayU → Bank B

DISCOM C (Rajasthan)

BillDesk → Bank C

6 Key Workflow Scenarios

⚡ Daily Meter Reading

Meter → HES → Adapter → VEE → Dashboard + Reports + Billing API

🛠 New Meter Installation

Site Survey (O&M) → Install (GPS+Photo) → Commission (HES Reg) → Active in MDM

💰 Consumer Bill Payment

MDM data → Billing API → Bill Gen → App/Portal → Payment GW → DISCOM Bank

⚠ Exception Handling

VEE flags anomaly → Alert → Operator review → Edit OR Work order to O&M

📊 AT&C Loss Calculation

DT input energy → Sum consumer usage → Calculate loss % → Energy Audit Report

🔧 Meter Maintenance

Alert (no data) → Work order → O&M App → Field visit → Fix/Replace → Update MDM