Why Residents Get DG Alerts Late — And How PES Solves It

You've seen it happen. Grid power goes out. The DG kicks in. Fans start spinning again. But the society app? Silent — for another 10 to 30 minutes.

Then the notification arrives: "Power switched to DG."

By that time, every resident has already figured it out themselves — the hard way.

The 15-30-Minute Gap: Why It Exists in Most Systems

Most smart meter systems communicate with meters using a polling model. The server periodically asks the DCU: "Is DG running?" The DCU checks. The meters respond. The server processes. The notification goes out.

This loop — query, wait, process, notify — takes time. Depending on network load and system architecture, that typically means 10 to 15 minutes from the moment DG actually started.

Vendors explain this away with technical reasons: network latency, server processing time, weak 2G signal in the basement. These are real factors — but they are also masking an architectural decision made early in the product's design.

How PES Does It Differently: Sensor + Event-Driven Architecture

PES's advantage works at two levels — hardware and software — and both matter.

At the hardware level: the DG Modem contains a dedicated sensor that monitors both the grid supply and the DG supply simultaneously. The moment the electrical changeover happens — grid cuts, DG powers on — the sensor detects the change at the electrical level, instantly.

At the software level: the system is event-driven. The sensor triggers an event the instant it fires — no polling loop, no scheduled query. The software responds to that event immediately and pushes a notification to the cloud server.

Compare this to how most vendors approach it:

• Most vendors (polling): server asks DCU every few minutes "Is DG running?" — inherent delay baked into the design
• PES (sensor + event-driven): hardware detects the supply changeover instantly → software fires the notification immediately

The result: residents receive a push notification within seconds of the switchover, not 15 minutes later.

Why This Matters for Residents and Society Management

For residents, the impact is immediate:

• Billing accuracy — DG billing starts from the exact moment of switchover, not a rounded or delayed interval
• No guessing — if the app is silent, grid is still on. The app becomes a reliable source of truth
• Dispute prevention — precise timestamps mean no arguments between residents and management about DG runtime
• Trust — the app tells residents what is actually happening, in real time

For facility managers and RWA committees, this eliminates a regular complaint category. Residents stop calling to ask "Is DG on?" because the app already told them.

What This Looks Like in Practice

Grid fails. DG starts at 3:00 PM.

• PES society: notification at 3:00 PM — within seconds
• Other vendors: notification at approximately 3:15 PM

Residents notice. They remember. After a few incidents, the question becomes: "Why is your app always right when the old system was always late?"

The Technology Behind It: PES DG Modem

The DG Modem is the device that makes both layers possible. Installed near the DG panel, it combines sensor hardware with event-driven firmware:

• Built-in sensor monitors both grid and DG supply lines in real time
• Detects the electrical changeover the instant it occurs — no polling schedule
• Event-driven firmware fires the alert immediately on detection — no software delay
• Signals the DCU and cloud server within seconds — notification reaches the resident app instantly
• Timestamps the changeover precisely for accurate DG billing from the first second

The two layers work together. The sensor eliminates detection delay. The event-driven architecture eliminates notification delay. Vendors who rely on polling cannot close this gap with software alone — they would need the same hardware.

The Bottom Line

The 15-minute delay isn't a bug. It was a design choice — one that made sense when smart meter systems were first built for bulk data collection, not real-time alerts.

PES made a different architectural decision: detect at the source, push immediately, and let residents trust their app.

If you've been told the delay is "normal" or "unavoidable" — it isn't. The technology to do better exists. We've already deployed it.

Want instant DG alerts in your society? Talk to our team →