1. Open EOS SCADA Editor

Creating a SCADA project begins by opening EOS SCADA Editor. Editor is the development environment where the basic configurations required for everything from receiving data from devices to preparing operator screens are performed.

First step: After opening EOS SCADA Editor, use the CREATE NEW PROJECT command on the main menu bar to create a new SCADA project.

2. Create a New Project

To create a new project, click the CREATE NEW PROJECT button on the Main Menu Bar.

The same command can also be accessed under the Program menu. Both methods open the new project creation window.

New Project Creation steps:

  1. Click the CREATE NEW PROJECT button.
  2. Review the Create New Project window that opens.
  3. Enter the desired project name.
  4. If the project is to be protected with a password, enter the project protection password.
  5. Click the CREATE button.

3. Project Name and Protection Password

In the Create New Project window, first enter the name to be assigned to the project. The project name should be selected so that the project can be easily recognized later and distinguished from other projects.

If password protection is required for the project, the project protection password can also be entered in the same window. After completing the required information, click the CREATE button.

Project security: If a project protection password is used, it is important that the password be stored securely by authorized personnel. The project name and security settings are fundamental project information defined during project creation.

4. Your Project Is Created Automatically

When the CREATE button is clicked, EOS SCADA Editor creates the project for you and automatically opens the newly created project. This allows the user to proceed directly to SCADA project development without having to deal separately with project files or initial configuration.

From this point onward, the project must be configured to establish communication with the field and allow the acquired data to be monitored meaningfully by the operator.

5. Basic SCADA Project Development Flow

In a newly created empty SCADA project, performing the basic development operations in a specific order helps establish the project in a more understandable and controlled manner. The general method for a basic project is as follows.

Step 1 — Define the Devices from Which Data Will Be Read

First, the devices with which the SCADA system will communicate are defined. These may include PLCs, RTUs, energy analyzers, protection relays, measurement devices, or other field devices supported by the communication driver in use.

The purpose of this stage is to define which device EOS SCADA will receive data from and by which communication method.

Step 2 — Determine the Data to Be Read from the Devices

After the devices are defined, the data points to be read from these devices are determined. For example, in a power generation facility, values such as active power, reactive power, voltage, current, frequency, breaker status, or unit operating status can be incorporated into the SCADA project.

These data points form the basis of the TAG structure used within SCADA. Therefore, this stage is where physical values from field devices are transformed into meaningful data points within SCADA.

Step 3 — Design the SCADA Screens

After the data has been defined, the screens that the operator will use to monitor the system are prepared. The goal of screen design is to visualize the process clearly, make important information easily accessible, and allow the operator to perform necessary operations safely.

In a simple screen example:

  • General view of the unit or facility,
  • instantaneous measurement values,
  • device and equipment statuses,
  • numerical values and indicators,
  • operator control elements when required

can be brought together on the same screen.

Step 4 — Connect the Data to User Controls

After the screens are prepared, the user controls on the screen are connected to the SCADA TAGs. In this way, actual values read from the field can be displayed in the relevant user controls.

For example, the active/inactive status of a motor can be connected to a status indicator, an active power value to a numerical display, or an analog value to a graph control. Thus, raw data read at the communication layer is transformed into visual information that the operator can understand.

6. Basic Structure of a SCADA Project

The operating logic of a basic EOS SCADA project can be considered through the following chain:

FIELD DEVICE  →  COMMUNICATION  →  SCADA TAG  →  USER CONTROL  →  OPERATOR SCREEN

Alarm and event management, data archiving, trends, reporting, scripts, virtual data, user authorization, and other EOS SCADA functions can later be added on top of this basic structure.

7. Proceed in the Correct Order

When developing a SCADA project, rather than starting directly with screen design, a more robust development approach is to first determine the data source and the values to be read, and then transfer these data to the screens.

Stage Main Purpose
1. Project Creating the SCADA project and defining the basic project information.
2. Device Defining the field devices from which data will be read and the communication structure.
3. Data / TAG Defining the data points to be acquired from devices within SCADA.
4. Screen Designing the SCADA screens used by the operator.
5. Connection Connecting SCADA TAGs to user controls.
6. Development Adding alarms, trends, archives, scripts, reporting, and other functions.

General Method for Your First SCADA Project

When creating your first project with EOS SCADA, the main objective is to reliably transfer actual data from field devices into the SCADA system and transform this data into clear screens that can be used by the operator.

CREATE NEW PROJECT
↓
DEFINE DEVICES
↓
DETERMINE DATA TO BE READ
↓
DESIGN SCREENS
↓
CONNECT TAGs TO USER CONTROLS
↓
DEVELOP THE SCADA PROJECT

This basic structure can be expanded from a small test project to large industrial SCADA systems containing many devices and thousands of data points. As the project scope grows and new functions are added, maintaining the basic data flow and project organization is important for system sustainability.

← Back to Previous Content