General System Architecture

HYDRO MOBILE and ANS can produce meaningful and reliable information only when the underlying EOS SCADA data collection and alarm infrastructure is correctly established. When the system is considered as a whole, the data flow can be considered as follows:

FIELD DEVICES  →  EOS SCADA  →  SCADA EDITOR CONFIGURATION  →  EOSFastER / DATA FLOW  →  LIVE EVENT  →  HYDRO MOBILE + ANS + LIVE DASH

Each layer produces the information required by the next layer. Therefore, errors made particularly during data and alarm modeling affect not only SCADA screens but also the results produced by HYDRO MOBILE, ANS, and other higher-level modules.

1. EOS SCADA Software Installation

The first layer forming the foundation of the system is EOS SCADA. HYDRO MOBILE, ANS ve diğer üst seviye çözümler için gerekli gerçek zamanlı saha verilerinin oluşturulması ve are provided through this infrastructure.

Core Functions of EOS SCADA

  • Provide communication with field equipment.
  • Provide the data collection, monitoring, and control infrastructure.
  • Model field data as meaningful SCADA TAGs.
  • Provide the data source required by higher-level modules.

The system architecture should also be planned in advance during installation. Tek sunuculu yapı, yedekli yapı ve benzeri mimari seçeneklerin yanı sıra kullanılacak haberleşme protokolleri de should be determined according to plant requirements.

Example communication protocols:

Modbus • IEC 60870-5-104 • OPC / OPC UA ve tesis tarafından kullanılan diğer protokoller

2. Data and Alarm Configuration with SCADA EDITOR

After EOS SCADA is installed, the actual structure of the plant must be defined in the system. This is performed SCADA EDITOR through SCADA EDITOR.

Data Definitions

  • Analog and digital points are defined.
  • Voltage, current, active power, reactive power, level, flow rate, and similar measurements are acquired by the system.
  • Field data is modeled using appropriate TAG structures.
  • Important data to be displayed in HYDRO MOBILE and LIVE DASH is identified.

Alarm Definitions

  • High, High-High, Low, and similar limits are defined.
  • Alarm priorities and severity levels are assigned.
  • Alarm messages and descriptions are created.
  • Critical alarms requiring notification are identified.

Critical point: For ANS to generate correct alarm notifications, the alarm model must be created correctly and meaningfully in SCADA EDITOR. ANS cannot by itself correct an incorrect or incompletely modeled alarm structure.

3. Data Collection and Recording with EOSFastER

After SCADA data and alarm configuration is completed, data collection and recording processes EOSFastER (Fast Event Recorder) can be supported by the module.

Core Functions of EOSFastER

  • High-resolution data recording.
  • Event-based recording.
  • Time-synchronized data archiving.
  • Creating a data infrastructure for performance and event analysis.

Thus, changes occurring within the plant are not only monitored in real time; a data infrastructure that can be used for historical review, event analysis, and performance evaluation is also established.

4. EOS LIVE EVENT Platform

After data flow is established, the EOS LIVE EVENT platform is activated to establish a real-time event and alarm monitoring infrastructure.

  • Real-time event monitoring.
  • Alarm management.
  • Improving operational awareness.
  • Providing data to higher-level notification and mobile access solutions.

LIVE EVENT is not merely a visualization layer; it is also an important integration layer where events and alarms received from EOS SCADA are made meaningful for higher-level use. .

5. HYDRO MOBILE

HYDRO MOBILE can provide mobile access to SCADA data at hydroelectric power plants. This allows plant personnel to access defined data and operational information from mobile devices even when they are physically away from the SCADA center. .

Main Use Cases

  • Access to SCADA data through mobile devices.
  • Real-time plant monitoring.
  • Rapid viewing of important measurement and status information.
  • Supporting operational decision-making processes.

For HYDRO MOBILE to operate correctly: The data to be displayed in the mobile interface must be modeled with the correct TAGs in SCADA EDITOR and correctly transferred to the higher-level access layer.

6. Alarm Notification System (ANS)

Alarm Notification System (ANS) can be used to deliver SCADA alarms and events to designated users through different communication channels.

Main Functions

  • Automatic notification during alarm conditions.
  • Use of SMS, email, Telegram, and similar notification channels.
  • Notification management by user and communication group.
  • Implementation of alarm escalation scenarios.
  • Rapid notification of relevant personnel during critical events.

The success of ANS largely depends on the quality of the alarm model created in SCADA EDITOR. Therefore, it should be determined in advance whether each alarm requires notification, which group it should be sent to, and its criticality.

7. LIVE DASH – Live Dashboard

LIVE DASH is the dashboard layer that enables visual monitoring and analysis of data obtained from the EOS SCADA system.

  • Real-time data visualization: Data can be monitored through charts, indicators, and tables.
  • Customizable dashboard design: Trend, KPI, status, and performance screens can be created according to requirements.
  • KPI and performance monitoring: Plant production and critical performance indicators can be monitored.
  • Web-based access: Access can be provided from different devices with the appropriate configuration.
  • Decision support: Visualizing data helps operators and managers make rapid assessments.

8. Importance of Integration

For HYDRO MOBILE, ANS, and LIVE DASH to be used effectively, the components in the EOS SCADA infrastructure should not be considered independently, but as parts of a single data and event chain.

Bileşen Primary Role Contribution to Higher-Level Systems
EOS SCADA Field communication and basic SCADA infrastructure Creation of real-time field data
SCADA EDITOR Data, TAG, and alarm modeling Making data and alarms meaningful
EOSFastER Data and event recording infrastructure Historical analysis and performance studies
LIVE EVENT Real-time event and alarm monitoring Event/data access for HYDRO MOBILE and ANS
HYDRO MOBILE Mobile SCADA access Mobile monitoring for field and plant personnel
ANS Alarm notifications Rapid alarm delivery to authorized personnel
LIVE DASH Data visualization KPI, trend, and operational decision support

9. Key Dependencies for a Successful Installation

  1. The EOS SCADA infrastructure must be installed. Communication with field devices and basic data collection must be established.
  2. The data model must be created with SCADA EDITOR. TAGs and related measurement points must be defined correctly.
  3. The alarm model must be created. Limits, priorities, and alarm messages must be defined correctly.
  4. Data and event flow must be verified. The data flow required by the EOSFastER and LIVE EVENT layers must be checked.
  5. HYDRO MOBILE must be configured. The data to be displayed in the mobile environment must be defined and access must be controlled.
  6. ANS must be configured. Notification channels, users, groups, and alarm policies must be defined.
  7. LIVE DASH screens must be created. Dashboards appropriate to the plant's operational and performance requirements must be prepared.

10. Conclusion and Summary

Although HYDRO MOBILE and ANS may appear, when considered separately, to be only mobile access or alarm notification applications, their real value emerges when they operate integrated with the EOS SCADA infrastructure.

EOS SCADA INSTALLATION

SCADA EDITOR: DATA + TAG + ALARM MODEL

EOSFastER: DATA / EVENT RECORDING

LIVE EVENT: REAL-TIME EVENTS AND ALARMS

HYDRO MOBILE + ANS + LIVE DASH

A deficiency or incorrect configuration in any link of this chain can directly affect the reliability and practical value of higher-level systems. Therefore, when planning HYDRO MOBILE and ANS projects, equal importance should be given not only to end-user applications but also to the underlying EOS SCADA data, alarm, and event infrastructure must be given equal importance.

Especially in hydroelectric power plant operations, the objective is not merely to send an alarm to a mobile device or display a value on a screen; correctly modeling, interpreting, recording, and monitoring field data and delivering it to the required personnel in a timely manner to establish an end-to-end operational information chain.

← Back to Previous Content