Solution

Zero Data Loss Guarantee

No measurement is lost, even if the internet drops or the server restarts. The local queue holds the data safely and transfers it automatically once the link returns - nothing is deleted without server acknowledgement.

Common Problems
The most critical energy management challenges faced in the field

Data Loss During an Internet Outage

In cloud-only systems the live readings are lost as soon as the link drops, leaving a gap that matters for billing and alarms.

The Server Restart Window

No data can be received during a backend update or maintenance, and that window falls out of the energy analysis.

Weeks-Long Offline Periods

Seasonal facilities and remote sites can go without a connection for weeks at a time.

Duplication and Collision

If the same measurement is written twice on retransmission, the figures break and alarms fire incorrectly.

How Argus EMS Solves Them
Real-time monitoring, automatic alarms and comprehensive reporting
💾

Safe Local Queue

The field agent writes every measurement to the local queue first. It is not removed from the queue until it has been written to the server.

Acknowledged (ACK) Transfer

The server acknowledges that it received the measurement. No record leaves the queue before that acknowledgement arrives.

📅

Offline Buffer

The local queue capacity keeps every reading safe even through a long offline period.

🔄

Automatic Retransmission

Once the connection is restored, the accumulated data is sent automatically in chronological order - no manual intervention.

🚫

Duplication Protection

If the same measurement is written a second time, the system silently ignores the duplicate record.

🚨

Queue-Full Alarm

An early-warning alarm as capacity is approached - the site's connection problem is detected before it bites.

Frequently Asked Questions
Why is a 30-day buffer enough?

Most sites in Turkiye stay offline for at most a weekend plus a public holiday. Thirty days is a generous buffer for both seasonal shutdowns and unexpected communication faults. The buffer duration and size are configurable.

What happens if the server acknowledgement never arrives?

The measurement stays on the field side until it is acknowledged by the server. When the link is re-established, every pending record is sent again. Even if the same measurement is sent more than once, the system prevents duplication.

How is data transfer guaranteed?

Transfer is acknowledgement-based; a measurement is held on the field side until the server confirms it - zero data loss.

What happens if the queue fills up?

The queue never deletes data; when capacity is reached it raises an alarm. That design is deliberate: detecting the problem early is preferred over discarding measurements.

What This Solution Measures
Quantities measured in the field and the outputs produced from them
Data during an outage
The field unit writes the measurement to the local queue first
No record is deleted before the server acknowledgement arrives
During an internet outage, measurements accumulate locally for up to 30 days
When the link returns
Accumulated measurements are back-filled automatically
Writing the same record a second time is blocked at database level
Hourly and daily summaries are recalculated for late-arriving data
Technical Requirements
Offline Buffer30 days of local retention
TransferTLS-encrypted, acknowledged (ACK) communication
Data Loss0 - raises an alarm when the queue is full, never deletes
Duplication ProtectionThe same measurement is never written twice
Queue-Full AlarmEarly warning as capacity is approached

Secure your data continuity today

No measurement is lost, whatever happens to the internet link or during server maintenance.

Request a Demo → info@nevacontrol.com