Lynxby DOMINION
← Back to components

ALARMS What failed, how long, and why.

An alert tells you something happened. It does not tell you what, how long it lasted, or what it took down with it.

Alarms, included in the Lynx core, brings together the alarm intervals from any asset in the plant and groups them into status periods. The result goes beyond the alert: it identifies what failed, how long it lasted and the impact it had. (The examples come from a photovoltaic site.)

Request a demo →

Configure the platform →

lynxplatform.cloud/monitorizacion/alarmas
Alarms · Status by site
Alarms: one card per site with its availability and, per asset, the number of events and its 0-to-100 bar.

NOT JUST THAT IT FAILED What each stoppage took down with it

Any asset can report alarm intervals. Lynx groups them by variable and builds status periods. So you do not only know when it stopped working. You know why, and with what impact: energy, availability or output, depending on the asset.

  • Groups alarm variablesGathers any asset's alarm signals and consolidates them into coherent status periods.
  • Status periodsTurns isolated events into intervals with start, end and duration to reconstruct the timeline.
  • Cause as well as timingEach status carries its code, criticality and the manufacturer's description to diagnose the cause.

STATUS BY SITE Availability and impact, site by site

One card per site with its availability and all its assets. Each asset shows its number of alarm events and a 0–100 availability bar. Selecting an asset with alarms opens its list on the right with the estimated impact. In the photovoltaic example, that impact is lost energy.

  • Card per siteName, availability percentage and the set of associated assets.
  • Events per assetEach asset shows its number of alarm-type events and a 0–100 availability bar.
  • Detail per assetSelecting an asset with alarms opens its list on the right.
  • Estimated impactIn photovoltaic, lost energy computed from the inverter's nominal power and the radiation during the alarm state.
lynxplatform.cloud/monitorizacion/alarmas
Alarms: one card per site with its availability and, per asset, the number of events and its 0-to-100 bar.

WHAT TO LOOK AT FIRST Six levels, and only two carry real impact

Events are classified following the hardware manufacturers' criteria. By default WARNING, MINOR and MAJOR are shown (all filterable).

  • OK
  • INFO
  • WARNING
  • MINOR
  • MAJOR
  • OTHER
MINOR and MAJOR are the critical levels, with real impact. The rest are informational or review levels. In photovoltaic, that impact translates into lost energy.

ROW BY ROW Every alarm carries what was lost

The selected asset's list details each alarm with its criticality, timeline and estimated impact (lost energy in the photovoltaic example).

COD
Event code and criticality (OK · INFO · WARNING · MINOR · MAJOR · OTHER).
Description
Manufacturer message: voltage loss, overvoltage, etc.
Start
Timestamp when the alarm state begins.
End
Timestamp when the state ends.
Duration
Total time in alarm state (days · hours · min).
Loss
Estimated impact of the interval (lost energy in kWh in the photovoltaic case).

WITHOUT LOGGING IN It reaches you when it trips, and when it clears

Every new status reported by an asset is emailed: location, error code, concentrator, reported value and alarm level, both on trigger and on clearance.

New status · Critical
Email alert sent when a critical alarm triggers, with the affected asset and the time of the status change.
Alert state cleared
Email alert sent when the alarm clears, with the duration of the alert state.
Lynx by Dominion

From the alarm to the diagnosis

We prepare a demo with the alarms from one of your sites and look at the margin that shows up once the cause is known.

Request a demo →

Or write to us directly at support.dt@dominion-global.com

← Back to components