Platform · Network Intelligence

One dashboard for every charger, every operator, every city.

Gridwatch is a unified monitoring and audit platform that ingests OCPI feeds from every Charge Point Operator on your network — giving you consolidated, auditable oversight of uptime, sessions, faults, and SLA compliance. Built for organizations that govern, not just operate.

GRIDWATCH · AUDIT CONSOLE
Live · OCPI 2.2.1
Good afternoon, A. Mehta 👋 · State Nodal Agency
Time Analytics
Stations
Operators
Audit Log
ChargersAll expand_more
OperatorsAll 14 expand_more
WindowLast 24h expand_more
Sessions & Utilisation · 24h1,326
Sessions by hourUtilisation 19.3%
SessionsActive vs Complete
94%
Active6%
Complete94%
Avg session duration
103.2min
Median session duration
68.0min
Top 5 stations · sessionsLast 24h
Orbit Mall · Pune490
NH-48 · Lonavala379
Hinjewadi Phase 2303
Pashan Depot154
Multi-operator
Single pane
Region → Charger
5 drill-down levels
OCPI 2.2.1
Native data standard
Government-grade
Monitoring & audit
The problem

Fragmented monitoring hampers governance.

India's EV charging network is operated by dozens of CPOs — each running its own platform, its own data format, its own dashboards. For organizations responsible for overseeing the network, that creates four critical problems.

01

Multiple operators, multiple systems

Each CPO uses its own platform and data format. Getting a unified view of the entire EV charging network on one screen is nearly impossible without a normalisation layer.

02

No single source of truth

There is no centralised platform to monitor charger uptime, charging sessions, fault reports, and SLA compliance across all operators. Decision-makers work off fragmented, inconsistent data.

03

Delayed fault identification

Without real-time consolidated monitoring, detecting offline or malfunctioning chargers takes longer — impacting public access. A charger can sit offline for days before anyone notices.

04

Challenges in data-driven planning

Aggregating accurate, standardised data for infrastructure planning, performance audits, and procurement decisions becomes complex when every operator reports differently.

Introducing Gridwatch

A central monitoring and audit platform. Built on OCPI.

Gridwatch ingests OCPI feeds from Charge Point Operators to give organizations consolidated, auditable oversight of their EV charging networks — across regions, states, cities, and individual chargers.

Purpose

One dashboard for the whole network.

A single, unified dashboard for agencies and organizations to monitor EV charging networks operated by multiple CPOs — without asking any operator to change their backend.

Integration

Native OCPI support.

Gridwatch connects to each CPO's OCPI endpoint and pulls location data, charger status, session records, and tariff information into one standardised view. Different vendors, one schema.

Positioning

Secure. Transparent. Auditable.

Designed for government-level and enterprise-level monitoring of EV charging infrastructure. Role-based access, audit trails, and exportable reports — built for accountability.

Key capabilities

Nine capabilities. One console.

Everything you need to monitor, audit, and govern a multi-operator charging network — with no charger-level control and no interference in CPO operations.

01
monitor_heart

Real-time charger status monitoring

See every charger's live state — Available, Charging, Faulted, Offline — across all operators on one map. No switching between CPO dashboards.

02
query_stats

Session-level analytics

Session duration, energy dispensed, start/end timestamps, connector type, and operator attribution. Drill into any session across any CPO from a single search bar.

03
notifications_active

Automated fault detection & alerting

Gridwatch detects offline, faulted, and underperforming chargers automatically — and routes alerts to the right team via email, SMS, or ticketing system integration.

04
timeline

Uptime, downtime & utilisation tracking

Track uptime, downtime, utilisation, and idle time per charger, per station, per operator, per city. SLA compliance dashboards show who's meeting targets and who isn't.

05
account_tree

Multi-level monitoring hierarchy

Drill down from Region → State → City → Station → Charger. Start with a national overview, zoom into a single connector. Matches how governance actually works.

06
compare_arrows

Operator & station comparison

Compare CPO performance side by side — uptime, session volume, fault frequency, average session duration. Identify top performers and underperformers at a glance.

07
insights

Historical data & trend tracking

Analyse session volumes, utilisation curves, and fault patterns over time. Spot seasonal trends, identify infrastructure gaps, and forecast demand for planning.

08
admin_panel_settings

Role-based access control

Admins, auditors, regional officers, and viewers each see what they need — nothing more. Full IAM with secure login, SSO support, and granular permissions.

09
receipt_long

Centralised audit logs

Every action on the platform — logins, data exports, report generation, configuration changes — is logged with timestamps and user attribution. Built for transparency.

How Gridwatch works

OCPI in. Unified dashboard out.

Four steps. No charger-level configuration. No disruption to CPO operations.

01

Connect CPOsOCPI 2.2.1

Each Charge Point Operator exposes an OCPI 2.2.1 endpoint. Gridwatch connects and begins pulling location, charger, session, and tariff data in real time.

02

Normalise & storeSingle schema

Data from every CPO — regardless of internal platform or hardware vendor — is normalised into a single schema. Different naming, status codes, and formats harmonised automatically.

03

Monitor & auditOne dashboard

Stakeholders log in to a single dashboard. National overview on home. Drill into any region, city, station, or charger. Set SLA targets, track compliance, generate audit reports.

04

Alert & actConfigurable

When a charger goes offline, a fault is detected, or utilisation drops below threshold — Gridwatch triggers alerts. Tickets can be routed to CPOs automatically via webhook or email.

Who Gridwatch is for

Built for the organizations that govern India's charging network.

account_balance

State Nodal Agencies & Transport Departments

Monitor all CPOs operating under state EV policy mandates. Track subsidy utilisation, charger deployment targets, and SLA compliance across concession agreements.

location_city

Government Bodies & Smart City SPVs

Unified visibility across multiple EV charging concessions within a city or district. Audit-ready reports for CAG, ministry reviews, and parliamentary questions.

domain

Large Enterprises & Campuses

Corporates, airports, and institutional campuses that contract multiple CPOs across locations. One dashboard to track performance, costs, and service quality.

hub

eMSPs & Roaming Hubs

eMobility Service Providers that aggregate chargers from multiple CPOs via OCPI roaming. Gridwatch adds the monitoring and audit layer on top of the roaming layer.

What makes Gridwatch different

Not another CMS. A governance layer.

Feature
Typical CMS
Gridwatch
Controls chargers
✓ (your own)
✗ — reads from all CPOs, controls none
Multi-CPO view
✗
✓ Ingests OCPI from any operator
Audit trails
Limited
✓ Every action logged, exportable
SLA tracking
Per-operator
✓ Cross-operator, with benchmarking
Target user
CPO ops team
✓ Agency, government, enterprise oversight
Data standard
OCPP · charger-level
✓ OCPI · network-level
Gridwatch doesn't replace your CPOs' CMS platforms. It sits above them — reading their OCPI feeds and giving you a consolidated, auditable view that no single operator's dashboard can provide.
FAQ

Questions agencies ask us.

Pulled from procurement, security, and policy conversations.

Does Gridwatch require CPOs to change their backend?add
No. Gridwatch connects via OCPI 2.2.1, which is an open standard most CPOs already support. If a CPO doesn't have an OCPI endpoint live, we help them enable it — typically a 2–4 week integration.
Can Gridwatch control or configure chargers?add
No. Gridwatch is a read-only monitoring and audit layer. It does not send commands to chargers (that's the CPO's CMS via OCPP). This is by design — governance platforms should observe, not interfere.
What data does Gridwatch ingest?add
Via OCPI: charger locations, connector status (real-time), session records (CDRs), tariff structures, and operator metadata. Gridwatch normalises all of this into a single queryable schema.
Is the platform secure enough for government use?add
Yes. Role-based access control, SSO, encrypted data at rest and in transit, full audit logging, and deployment options include on-premise / government cloud (NIC, MeitY empanelled infra). Designed for government procurement and security requirements.
Can I export reports for audits?add
Yes. Exportable reports in PDF and Excel — filterable by operator, region, time period, and metric. Designed for CAG audits, ministry reviews, state EV policy compliance reporting, and concession agreement SLA tracking.
How long does deployment take?add
For organisations where CPOs already have OCPI endpoints: 4–6 weeks from contract to live dashboard. For CPOs that need OCPI enablement first: add 2–4 weeks per operator.
What does pricing look like?add
Annual SaaS licence, tiered by number of CPOs and chargers monitored. Government and enterprise pricing available on request. Contact us for a scoping call.

See every charger. Audit every operator. One platform.

Government-grade network monitoring built on OCPI. No charger control, no CPO interference — just consolidated, auditable oversight of the infrastructure you govern.