eco2lot feature · Know when something is off

Alarms

eco2lot keeps an eye on your data for you. When limit values are exceeded, devices stop sending data or consumption develops unusually, eco2lot automatically informs the people in charge. This way you detect faults and deviations early — while your plants run on their own.

  • Monitor limits, states and consumption automatically
  • Notification to users or teams — by email or push
  • Central alarm overview with history and acknowledgement
my.eco2lot.de · Alarms Alarm overview
What are alarms in eco2lot?

Alarms are the automatic monitoring in eco2lot. For every reading, meter or device you define what is normal — for example a maximum temperature or a daily consumption. If a value deviates from it, a device stops sending data or a fault state occurs, eco2lot triggers an alarm and informs the people or teams in charge by email or push notification. All alarms come together in one central overview with history and acknowledgement.

What it looks like

From the limit value to the message

Real views from eco2lot: you define what is normal. eco2lot reports when a value deviates from it — and records who reacted.

my.eco2lot.de · Alarms Active alarms
Acknowledge with one click

The list of active alarms shows status, trigger time and message. Whoever reacts ticks the box and acknowledges — with timestamp, optionally with a comment. The "History" tab keeps everything past.

Meter alarm
Limit consumption per day

For a meter you define period and limit — here 4,800 kWh per day. Below that you choose which user or team receives an email, optionally also when the alarm ends.

Data point alarm
React to a state

A data point reports "fault" as true or false. The "signal bit" strategy triggers as soon as the state occurs — entirely free of a limit value.

In detail

What is inside Alarms

What eco2lot monitors for you

For every data point or meter you define your own alarm rules. eco2lot detects, for example:

  • Limit exceeded: temperature too high, power too large, pressure outside the desired range
  • Limit undershot: fill level, temperature or pressure too low
  • State occurs: machine reports fault, standstill or another defined status
  • Device or meter stops sending data — a hint at a communication problem or sensor failure
  • Consumption per day, week or month higher than expected
  • Consumption unusually low — a hint at standstill, defective meter or failed plant

Your benefitOne rule replaces the daily check — for every measured variable.

The right information at the right time

For every alarm you decide yourself who is informed:

  • Notification to individual users, whole teams or both
  • By email or push notification — straight to the phone
  • Optionally an all-clear as soon as the value is back in the normal range
  • Escalation chains in case nobody reacts — more under "For experts"

Your benefitThe person in charge finds out first — instead of everyone or nobody.

Everything in one place: the alarm overview

All triggered alarms come together centrally. There you see at a glance:

  • what happened and when the alarm was triggered
  • which device, data point or meter is affected
  • whether the alarm is still active and whether someone has already acknowledged it
  • the history of past alarms with timestamps and comments

Your benefitNotifications become a traceable history — for audits as well.

For experts: fine-tune rules

Whoever wants to go deeper has further options:

  • Hysteresis: the alarm ends only when the value falls clearly below the limit again — this prevents constant switching on and off at the limit edge
  • Time conditions: a value must violate the limit for a minimum duration before the alarm triggers
  • Escalation chains per team, plant and time of day
  • Further channels: Microsoft Teams and webhooks to ticket systems (webhook = automatic message to another system)
  • Alarm statistics with clusters per plant and cause, plus cause documentation right at the alarm
  • Bridge to automation: an alarm triggers an action

Your benefitFewer false alarms, clear responsibilities, clean evidence.

One level deeper

Examples from practice

How operations use automatic monitoring — anonymized, with typical numbers.

Cooling water gets too warm

An operation monitors the cooling water flow of its refrigeration plant. If the temperature rises above 32 °C, maintenance receives a message immediately. The dirty recooler is cleaned before the plant shuts down.

Power consumption at the weekend

The daily consumption of a production hall is normally below 4,800 kWh. On a Saturday with no production, eco2lot reports an exceedance. The reason: the compressed air system kept running. Since then the alarm saves energy every weekend.

Compressor reports a fault

A machine builder monitors the fault signal of its compressors as a state. When the status changes to "fault", the message goes to the maintenance team. Once the compressor runs again, eco2lot sends the all-clear.

Meter delivers no values

A water meter in the annex has sent no data for two hours. eco2lot reports the outage automatically. The cause is a flat battery in the radio module — detected before a gap appears in the monthly billing.

Your outcome

Afterwards you can …

  • You learn about faults and deviations before they become expensive.

  • You monitor plants and consumption while the daily dashboard check becomes optional.

  • The person in charge is informed — by email or push, individually or as a team.

  • In the alarm overview you see at any time what is open and what has been done.

  • You have a traceable history of all events.

Frequently asked questions

What you should know about Alarms

Which values can I monitor?

Every data point and every meter in eco2lot: temperatures, pressures, power values, meter readings, states such as "fault" or "operation" as well as consumption per day, week or month. The absence of data can be monitored as an alarm too.

How am I informed?

By email or push notification to individual users or whole teams. For deeper integrations, Microsoft Teams and webhooks are available — this way alarms also reach ticket systems and your own applications.

What happens when the value is back to normal?

The alarm ends automatically. Optionally eco2lot sends an all-clear to the same recipients. In the alarm overview the alarm stays visible with start, end and acknowledgement.

How does eco2lot avoid false alarms?

Through hysteresis and time conditions: a value must violate the limit clearly and long enough before the alarm triggers. This stops the typical flutter at the limit edge when a value fluctuates narrowly around the limit.

Are alarms documented in an audit-proof way?

Yes. Every alarm carries trigger time, end, acknowledgement with the responsible person and the documented cause. The history is kept as evidence — for ISO 50001 or internal audits, for example.

Are Alarms the right fit for your task?

Describe your starting point and your goal — we get back to you with a concrete recommendation of matching features and solutions, plus a price indication.

Configure your solution
Esc or click outside to close