LIVEDB

LIVEDB is a live data sharing feature used in EOS SCADA software. It keeps industrial data collected and archived by SCADA Runtime up to date in a database table that can be accessed by other applications at user-defined intervals.

In this method, EOS SCADA Runtime running on the SCADA computer processes and archives data received from field devices. When LIVEDB is enabled, the current values of this data are also maintained in a data structure called ANLIK_DURUM.

This allows another application that needs data collected by the SCADA system to read the LIVEDB data source instead of connecting directly to the SCADA communication layer.

For example, another SCADA system, reporting application, data analysis software, web application, or custom-developed computer program can access current process data through LIVEDB.

When LIVEDB is enabled, a live data structure named ANLIK_DURUM is created under the main EOS SCADA database.

This structure primarily stores the data identifier, current value, and timestamp information. The current values and time information of data archived by SCADA are continuously updated in this table.

The basic approach of LIVEDB is not to store all historical values in this table, but rather to keep the current state of each data point in an easily accessible structure.

The operating principle of LIVEDB is quite simple. Data received from field devices is first collected by EOS SCADA. SCADA Runtime processes this data within its normal operation and archiving mechanisms.

LIVEDB creates a separate live data layer that makes this data available to other applications.

One of the important use cases of LIVEDB is the ability to create data archives outside the SCADA computer.

For example, live data on the computer running SCADA Runtime can be read by another computer on the network, which can then store the data in its own database or archiving system.

This allows data available on a single SCADA computer to be used by different systems and, when necessary, separate archives to be created for different purposes.

One of the fundamental ideas behind the LIVEDB design is to allow a SCADA system to provide the data it collects to other systems without requiring them to send commands.

With this approach, the SCADA system acting as the data source continues to retain control of the process. External applications simply read the live data provided to them and perform monitoring, analysis, or reporting operations.

Therefore, LIVEDB can be considered a simple integration layer, particularly for applications focused on monitoring, data sharing, analysis, and reporting.

One of the original design ideas behind LIVEDB was to create a simple structure that would allow data in a SCADA system to be monitored by different computers and separate data records to be created based on this data.

From this perspective, LIVEDB can be said to have been inspired by the concept of distributed data usage. However, LIVEDB is not a blockchain system in the technical sense.

Mechanisms such as distributed consensus, blockchain structures, cryptographic verification, and immutable records found in blockchain systems are not part of the fundamental operating principle of LIVEDB.

The purpose of LIVEDB is much simpler: to turn live data generated by SCADA into a common data source that other systems can read easily and securely.

To enable the LIVEDB feature in EOS SCADA, the LiveDBActive option in the general settings section related to the Main Database must be set to True.

• Provides data sharing without requiring the development of an additional industrial communication protocol.
• Allows data to be accessed directly through the Firebird database.
• Can be used as a data source for another SCADA system.
• Can be integrated with web applications and custom-developed software.
• Helps create data archives independent of the SCADA computer.
• Its simple structure makes it suitable for development and testing activities.
• Provides an easy-to-understand data sharing model for monitoring applications.

LIVEDB is primarily designed for simple data sharing and monitoring purposes. Therefore, certain limitations should be considered depending on the intended use case.

• LIVEDB is not a standard industrial communication protocol.
• It is not designed for real-time control or command transmission.
• The live table is primarily intended to share current state information.
• Appropriate Firebird, Windows, and network configuration is required for network access.
• For very large data volumes or very high query frequencies, a specialized data architecture should be considered.
• For critical applications, access permissions, redundancy, data security, and database administration should be addressed separately.

Tools that can be used to work with LIVEDB, inspect live data, access Firebird databases, or test LIVEDB data sources will be shared here.

This section will be expanded over time with auxiliary applications, sample programs, testing tools, and other LIVEDB software developed by EOS.

LIVEDB provides a simple approach for transferring data collected by SCADA to other applications without requiring a complex communication protocol.

Sharing live data generated by SCADA Runtime through a Firebird-based table allows software running on different computers to use the same process data.

In this respect, LIVEDB can be used as a simple data sharing layer between SCADA systems, data archiving applications, reporting software, analysis tools, and custom-developed industrial applications.

The basic approach of LIVEDB is simple: SCADA collects the data and updates the live table; other applications read this table and use the data they need.

You can contact us about EOS software, LIVEDB, or technical content.

• benanbasoglu@gmail.com
• ANKARA