Solarmetrica...
logo
Sign In/Register

Faults Module

The Faults module is used to record, track, and manage technical issues occurring in power plants.

With this module, users can;

  • Create plant or device-based fault records
  • Track the status of faults
  • Assign faults to users
  • Monitor the start and end times of faults
  • Manage fault processes

The Faults module is a critical operational management tool for maintenance teams, operations teams, and system administrators.

Fault List

All faults created in the system are listed on the Faults screen. Each fault record contains the following information:

  • ID
  • Company
  • Site
  • Plant
  • Device
  • Type
  • Source
  • Reason
  • Status
  • Start time
  • End time
  • Elapsed time
  • Stage
  • Priority
  • Assigned user

Fault Types

The system supports two different types of faults:

  • Manual Fault: Faults created manually by the user. Example: Planned maintenance, distribution outage (EDAŞ), transformer maintenance, inverter fault
  • Automatic Fault: Faults automatically detected by the system. Usually triggered by alarm systems or data analysis.

Fault Sources

  • Inverter
  • Transformer center
  • Grid
  • EDAŞ
  • Unplanned outage
  • Maintenance work

Fault Priorities

  • Low: Minor issues that do not directly affect system operation.
  • Medium: Issues that may affect system performance but are not critical.
  • High: Critical faults affecting energy production or system safety.

Fault Status

  • Active: The fault is ongoing and has not yet been resolved.
  • Closed: The fault has been resolved and the process is completed.

Creating a Fault

To create a new fault, the Add Fault button is used. When creating a fault, the following information must be entered:

  • Site
  • Plant
  • Device
  • Source
  • Fault reason
  • Priority
  • Start time
  • Assigned user
  • Description

Fault Duration Tracking

  • Start time
  • End time
  • Total elapsed time

Fault Assignment

Faults can be assigned to specific users. This allows maintenance teams to take action, responsibilities to be defined, and intervention processes to be tracked.

Fault Management Process

  1. Fault is created
  2. Fault is assigned to a user
  3. Fault status is actively monitored
  4. When the problem is resolved, the fault is closed

Alarms Module

The Alarms module enables monitoring of warning and error conditions coming from devices in power plants.

The system automatically detects alarm signals from inverters, transformers, and other energy equipment and records them on the platform.

With this module, users can;

  • View alarms coming from plant devices
  • Review alarm history
  • Track alarm priorities
  • Assign alarms to users
  • Manage alarm processes

Alarm List

All alarms occurring in the system are listed on the Alarm screen. Each alarm record contains the following information:

  • ID
  • Company
  • Site
  • Plant
  • Device
  • Alarm name
  • Start date
  • End date
  • Priority
  • Status

Alarm Source

  • Inverters
  • Data loggers
  • Transformer systems
  • Energy measurement devices
  • SCADA systems

Alarm Priorities

  • Low: Warning-level alarms that do not directly affect system operation. Example: Normal operation warnings, temporary connection issues
  • Medium: Alarms that may affect system performance but are not critical
  • High: Critical alarms affecting energy production or device safety. Example: Inverter fault condition, fan failure, DC insulation fault, PID fault

Alarm Status

  • Open: The alarm is still active and the issue continues.
  • Closed: The alarm has ended or the device has returned to normal operation. Closed alarms are kept in the system as historical records.

Alarm Duration Tracking

  • Alarm start time
  • Alarm end time

Alarm Assignment

Alarms generated on the platform can be assigned to specific users. This allows responsible persons to be defined, technical teams to take action, and intervention processes to be tracked.

Alarm Management Process

  1. Device generates an alarm
  2. Alarm is detected by the system
  3. Alarm is listed on the platform
  4. Alarm is assigned to the responsible user
  5. Technical team intervenes
  6. Alarm is closed

Custom Alarm Module

The Custom Alarm module allows users to define custom alarm rules based on data tags in the system.

  • Create alarms for specific data values
  • Define device or plant-based alarm rules
  • Set alarm priority levels
  • Define the time range in which the alarm will be active

Alarm Rules

Created alarm rules are listed and managed. Each alarm rule contains the following information:

  • ID
  • Alarm name
  • Priority
  • Working range
  • Description
  • Status

Creating a New Alarm Rule

  • Main Company: Determines which company the alarm rule belongs to.
  • Rule Name: The name of the alarm rule displayed in the system. Example: Low DC Voltage, Inverter Temperature Alarm, Zero Production Alarm
  • Description: Text explaining what condition the alarm rule represents.
  • Priority: Low, Medium, High
  • Alarm Condition:
    • Data Tag (example: inverter_power, dc_voltage, temperature, grid_voltage)
    • Operator (example: <, ==, =, <=)
    • Value (example: dc_voltage < 200)
  • Alarm Active Time: Start time – End time (example: 00:00 – 23:59)
  • Alarm Status: Active / Passive

Alarm Working Mechanism

  1. The system continuously monitors data tags
  2. Defined alarm rules are checked
  3. If the condition is met, an alarm is created
  4. The alarm is displayed in the system

Usage Scenarios

  • Alarm when inverter production drops to zero
  • Alarm when DC voltage goes out of limits
  • Alarm when temperature exceeds a certain value
  • Alarm when grid voltage drops