SCADA-SST is designed to be a generic, easy- to-use and easy-to-setup SCADA simulation framework. This is achieved by making the process of setting the SCADA network topology and populating it with nodes as straightforward and intuitive as possible.

Setting Network Topology:
Simulating a SCADA system network starts by creating a network topology. The network topology is implemented in two files, namely, a network topology file (.ned) and a simulation configuration file (.ini). For each simulated network, the network topology file specifies the list of subnetworks (LANs and WANs). For every subnetwork, the configuration specifies the list of nodes and the links (connections) between those nodes. The network topology configuration can be edited directly with text or it can be constructed using the graphical user interface. The simulation configuration file, on the other han, specifies runtime simulation parameters. This includes:
– the network (or subnetwork) to be simulated.
– the simulation duration as well as the scheduler
– TCP protocol settings
– IP protocol settings
– ARP protocol configuration

scada sst (gui)interface

Creating Simulated Nodes:
Adding a simulated node to the network can be done in two different ways. First, adding an entry in the topology configuration file and setting all related links (connections). Second, using the graphical user interface (drag-and-drop). In SCADA-SST, there is an extensive list of node types that can be used to create new nodes. Node types fall into two categories: INET nodes and SCADA related nodes. INET nodes category includes typical network hosts such as routers, wireless hosts, ICMP hosts, etc. SCADA related nodes category includes SCADA specific hosts such as PLC, RTU, historian, database server, etc.

Configuring Interface Nodes:
An interface node is a particular type of nodes that allows external hosts to be connected to SCADA-SST. For each external host, there is a need for (at least) one interface node. Each interface node can support one protocol. That is, if an external host can communicate with simulated nodes using two different protocols, there is a need for two interface nodes. Configuring an interface node consists in setting a set of parameters, such as the routing table, interface table, the external host IP address, etc.