Every answer an operator needs.
No digging required.
Fault context, revenue impact, and actionable guidance in one view — plus an open API so your stack stays connected.
- Real-Time Monitoring
- AI Diagnostics
- Revenue Impact
- Open API Integration
Plain language.
Not raw error codes.
When a fault fires, GridLyt's AI layer translates the raw BMS code into a plain-language diagnosis — root cause, affected components, and a recommended action window — before the operator has finished reading the alert.
- Root cause in plain English, not hex codes
- Affected module and cell group identified automatically
- Urgency classification — act now vs. schedule within 72h
- Historical pattern matching across your fleet
Fault detected — Asset BESS-04, Module B-07
ERR_CELL_IMBALANCE_0x4A2F · 14:32:07 UTC
Raw fault code
ERR_CELL_IMBALANCE_0x4A2F
AI diagnosis
Cell group 3 showing 18mV imbalance above threshold. Likely passive balancing circuit degradation in module B-07.
Revenue impact
−€2,340 / day if unresolved (capacity derating at current dispatch schedule)
Recommended action
Schedule module inspection within 72h. No immediate curtailment required.
Cell imbalance — Module B-07
−€2,340
per day
Thermal runaway risk — Rack 3
−€8,900
per day
BMS comms dropout — intermittent
−€410
per day
SOC drift — calibration needed
−€620
per day
Every anomaly has
a euro figure.
GridLyt calculates the daily revenue at risk for every active anomaly based on your dispatch schedule, current market prices, and the fault's expected capacity impact. Operators see the business consequence immediately — not after a separate analysis.
- Revenue at risk calculated per anomaly, per day
- Accounts for dispatch schedule and market price
- Fleet-level roll-up for executive reporting
- Resolved anomalies tracked for ROI attribution
Your data.
Your stack.
GridLyt exposes every asset, anomaly, and revenue metric via a versioned REST API. Subscribe to real-time events via webhooks — anomaly detected, resolved, or status changed — and pipe data into your SCADA, CMMS, or trading platform.
REST API v1
Versioned, JSON, OpenAPI spec included
Webhooks
Signed payloads, retry with backoff
Bearer auth
Per-integration token scoping
Real-time
Sub-second event delivery on anomalies
GET /v1/assets
Authorization: Bearer <token>
// Response
{
"assets": [
{
"id": "bess-04",
"name": "BESS-04",
"soh": 94.2,
"soc": 78.1,
"status": "anomaly",
"revenue_at_risk_daily": 2340
},
...
],
"total": 12,
"updated_at": "2026-06-06T14:33:00Z"
}See it live on your fleet data.
Request a demo and we'll walk through AI fault explanation, revenue impact, and API integration with your actual asset configuration.
Request a demo