Spectrum Power Training

SP7 Independent Front End (IFS) -

Basic
GSW-SP7-IFSB

Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Course Objectives
Upon completion of the course, the participant will be able to:
▪ Gain basic knowledge to configure Spectrum Power 7 Independent Front End (IFS).
▪ Provide an IFS overview with base functionality and communication Protocols supported.
▪ Provide an overall understanding of the IFS displays and uses.
▪ Provide an overall understanding on how to model IFS data in IMM.
▪ Execute IFS user functions.

Course Length: 1 day

Delivery method: Classroom, Remote, On-Site

Target Audience: Person, who independently maintain RTU communications and are responsible for new RTU data
integration. Communications Administrators, System Hardware Maintainers/Administrators, Operations Support
Personnel

Prerequisites:
▪ Fundamental Data Communication Knowledge
▪ Familiarity with RedHat Enterprise Linux (RHEL)
▪ Familiarity with Spectrum Power 7 database fundamentals

Page 4 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Agenda
01 Independent Front-End System

02 Configuration and redundancy

03 User Interface

04 IFS IMM Model

04 Exercises

Page 6 Restricted | © Siemens 2023 | Grid Software

 Agenda
01 Independent Front-End System

02 Configuration and redundancy

03 User Interface

04 IFS IMM Model

04 Exercises

Page 7 Restricted | © Siemens 2023 | Grid Software

Communications in the SCADA context

Remote Substation
▪ A SCADA system is responsible for the monitoring,
supervision, and control of large geographical areas.
▪ Each substation supervised may contain hundreds
(or thousands) of telemetered data that must be
reported to the control center for situational
awareness.
▪ Telemetered data is usually generated by the
equipment installed at the substation, such as: PLC
units, instrumentation transformers, switches,
protection devices, meters, etc.
▪ Digital, Analog, and Counter data will be typically
processed and stored in a Remote Terminal Unit
(RTU).

Page 8 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Communications in the SCADA context

Communication Links
▪ Communication link is defined as a channel that connects
two devices, or more, with the purpose of data exchange.
▪ Several types of communication medium between the
receiver and transmitter can be used: Radio, Microwave,
Spread-spectrum, Twisted-pair, Fiber-optics, Dial-up,
Leased-Line, etc.
▪ Once data is collected and stored at the RTU, a
communications infrastructure must support data
exchange over long distances.
▪ In general, there is no better or worst communication
medium to be implemented. There are several factors
that may affect such definition, such as: distance, number
of devices, costs, technology, response and transmission
time, etc.

Page 9 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Communications in the SCADA context

SCADA Master Station/Control Center

▪ Once data is reported to SCADA, it will be
processed and reported to the operator for further
evaluation and supporting on decision making
processes.
▪ SCADA may also generate alarms to the operator
based on pre-defined configuration as well as
transmitting such to Power Applications, Historian,
etc.

Page 10 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7
Independent Front-end System (IFS)

▪ The IFS is an interface for connecting RTUs of

different manufacturers to the Spectrum Power
distributed control center system.

▪ The IFS is independent of any special proprietary

hardware.

Page 11 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Base Functions (IFS)
▪ Data Acquisition
▪ Requests and process data from external devices
▪ Data Preprocessing
▪ Implemented by protocol. Example: threshold limitation, characteristics curves, point inversion
▪ Time Processing
▪ For chronologically relevant information.
▪ Error Messages and Quality Flags
▪ Evaluate message and data reliability
▪ Line-Level Redundancy
▪ Allows both servers to communicate with the RTUs. Both have the same priority.
▪ Listening Mode
▪ Supports parallel operation with other Masters
▪ Connection of Data Concentrator
▪ Scalability
▪ Online Engineering Data Activation
▪ Information Model Management (SP7)
▪ Scan Groups
▪ Determines what types of data the Master wants to receive and the periodicity

Page 13 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
What is a communication protocol?

▪ In the utility context, a protocol is simply the language the RTUs, computers,
and other devices use when they communicate with each other.
▪ The world’s first protocol was the Morse code​.
▪ The communication protocols have many features intended to ensure reliable
interchange of data over an imperfect communication channel.​
▪ SCADA communication protocols are designed specifically for the reduced reliability
communications links typically employed with SCADA systems and to provide secure
transmission of data. The protocols employ error detection and message retry
techniques.

Page 14 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Why do we need communication protocols?

▪ The communication protocol will establish the “language” in which two (or more)
devices must follow in order to properly communicate.
▪ As long as the transmitting device follows a predefined set of rules for sending the
data, the device at the receiving end is able to translate the signal into meaningful
data.
▪ The concept of “open standard” based protocols has been receiving increased
attention from the power systems industry, once it provides interoperability between
devices and systems from different vendors.

Page 15 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7
Communication Protocols (Standard)

▪ IEC 60870-5-101 (Master / Slave) balanced and unbalanced

▪ IEC 60870-5-104 (Master / Slave) optional with secure communication
▪ DNP 3.0 (Master / Slave)
▪ DNP 3.0i (Master / Slave) optional with secure communications
▪ TG 8979
▪ Conitel 2020
▪ IEEE C37.118 Synchrophasor Protocol (IP interface)
▪ MODBUS RTU
▪ MODBUS TCP/IP
▪ Others

Page 16 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7
IFS Highlights

Highlights Benefits
• Uses “off the shelf” asynchronous serial multi-port hardware • Saves and protect your investments, no proprietary hardware
components.

• Process interface with distributed system architecture • Flexible and redundant system configuration

• Integral component of Spectrum Power 7 • Configurable „to the last bit“ with Spectrum Power 7

• Line redundancy • High availability

• Online data update • IFS data updates are activated in real-time environment with minimum impact
(reset of affected lines only)

• Data pre-processing and filtering • Higher performance of the total system

• Secure and high performing support of IP based protocols • Flexible and economic process data transfer by using common
(IEC 870-5-104, DNP3i) communication network

• Support of standard and manufacturer specific protocols • Protects your investment, high flexibility

Page 17 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Agenda
01 Independent Front-End System

02 Configuration and redundancy

03 User Interface

04 IFS IMM Model

04 Exercises

Page 18 Restricted | © Siemens 2023 | Grid Software

IFS Topology
Typical Configuration of IFS inside a Spectrum Power 7 System

ADM RTC1 UI01 IF11 Multiport

IEC 104 (Master),

IEC 104 (Slave),
LAN DNP3i (Master),
WAN DNP3i (Slave),
Modbus TCP/IP,
SAP20 TCP/IP,
Genisys

IEC101 (Master), IEC101 (Slave),

DNP3.0 (Master), DNP3.0 (Slave),
Modbus, Conitel, TG8979, TG800,
SINAUT 8-FW, RP570, HNZ, ST1,
SPARE RTC2 UI02 IF12 Multiport ADLP180

Page 19 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS IP and Serial Connections: IEC Connections Overview

Spectrum LAN Spectrum LAN

WAN/LAN

TCP/IP
Connection
Router
IEC 104

Server Server

Multiport Multiport
Serial Connection

Line Splitter

PDM > PCM Converter or IEC101

Synchronous > Asynchronous Converter

Modems

Network

Page 20 Restricted | © Siemens 2021 | Spectrum Power 7 v21Q4

IFS Hardware: IFS Serial Expansion Module

▪ Different type of Serial Expansion Modules can be

used.
▪ It does not cost as much as using remote IFS
servers.
▪ Portserver has the same functionality as the serial
multiport except that it is using a LAN or WAN
connection between the server and serial module.
With the portserver the distance between the server
and serial module could be very long.

Page 21 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS - Sample Port Server Setup

Setup with Ruggedcom Port Server

Ethernet/GSM/ Serial to
IFS Ethernet
Intranet RTU
Server Converter

TCP/IP Serial
Connection Connection
With IEC104 the RTU communicates directly via TCP/IP

Page 22 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS - Hardware

DIGI Connect Ports are often used for IFS

asynchronous (byte) protocols (e.g. IEC101 and
DNP3)

Page 23 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS - Hardware

ASE Terminal Servers are often used for IFS

synchronous (bit) protocols (e.g. Conitel)

Page 24 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS Redundancy: IFS Block Redundancy

▪ The IFS is normally set up in a redundant block.

▪ Both servers are running in PC-PC mode.

▪ The channels can be switched individually between

the two servers.

▪ In a fault situation this will be done automatically.

Page 25 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS Serial Connections: IFS Point to Point Connections

▪ One line from the RTU divided via line splitter to

each IFS.

▪ Both configuration are valid for all serial protocol

types.

▪ Redundant lines from RTU. Both lines have equal

priority and treated as main lines. Only one line
can be operational at the time.

Page 26 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS Serial Connections: IFS Point to Point Connections

▪ Point to point connection with redundant lines from

the RTU divided via MSDs to each IFS. With this
configuration the backup line will be cyclically
tested.

▪ This configuration require that the RTU have two

independent communication interfaces.

▪ This configuration is valid for protocol type

IEC60870-5-101 and DNP3.0.

Page 27 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS Serial Connections: IFS Multi-drop Connections

▪ One line from the RTU divided via Line Splitter to

each IFS.

▪ Both configurations are valid for protocol types

IEC60870-5-101 and DNP3.0

▪ with redundant lines from RTU.

Both lines have equal priority and treated as main
lines. Only one line can be operational at the time

Page 28 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS Serial Connections: IFS RTU Node Connection

▪ The node configuration is of type transparent node.

▪ Each subRTU has its own database on the node

RTU. The Spectrum Power system sees the
subRTU as separate RTUs. The node RTU is the
physical connection point for the IFS.

▪ This configuration is valid for protocol type

IEC60870-5-101.

Page 29 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS Serial Connections: IFS Dial-up Connections

▪ Point-to-point dialup connection will establish the connection

to the RTU and keep it up until it is active disconnected by
the operator.
▪ Different type of dialup media can be used such as
analogue, ISDN, ISDN D-channel and GSM.

▪ Both configurations are valid for protocol IEC60870-5-101

▪ Multidrop dialup connection will only be active as long as

there is data to be sent. When no data is waiting to be
transferred, the connection is inactive.
▪ Applicable for balanced and unbalanced connections.
▪ Different type of dialup media can be used such as
analogue, ISDN, ISDN D-channel and GSM.

Page 30 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS Serial Connections: IFS Radio Connections

▪ Multidrop radio connection.

▪ The connection work the same way as the Multidrop
dialup function. Each RTU has to be called with a
special routine.
▪ The connection will be marked as inactive when no
data is transferred between RTU and IFS server.

Page 31 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS TCP/IP Connection: IEC104

▪ In IEC104 configuration each IFS Server

establishes a TCP/IP connection to each IP
address of the RTU. Only on one connection
telegram StartDT is send to activate data
transmission.

▪ This configuration is valid for protocol type

IEC 60870-5-104.

Page 32 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS IEC 101/104 Slave Function, IEC101RTU and IEC104RTU
Spectrum PowerTM 7

The IEC101RTU and IEC104RTU

work towards other Control Center
as a RTU on the IFS, using the
IEC101 or IEC104 protocol.

Page 33 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
IFS IEC 101/104 Slave Function, IEC101RTU and IEC104RTU

▪ The mapping between Spectrum Power internal address and protocol address for the slave
RTU can be done separately per object in the database, or as a copy of an existing master
RTU.

▪ If a copy of an existing master RTU is going to be used, it is only necessary to define which
RTU is the master RTU. No point definition is necessary for the slave RTU in this case. Note
that the slave RTU data points will have the same protocol addresses as the master RTU.

▪ If the slave RTU is going to send data from several master RTUs, a new set of mapping
between the Spectrum internal address of an object and the protocol addresses must be
done. The mapping is done the same way as for a master RTU.

▪ Commands can also be sent from the remote control center via the IECRTU to a RTU
connected directly to Spectrum Power.

Page 34 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Agenda
01 Independent Front-End System

02 Configuration and redundancy

03 User Interface

04 IFS IMM Model

04 Exercises

Page 35 Restricted | © Siemens 2023 | Grid Software

Spectrum PowerTM 7
IFS data structure

Pair 1 Channel 1 RTU 1 Point 1

Point 2
…
RTU 2
RTU 3
Channel 2 RTU 1 Point 1
Channel 3
…
Channel n

Pair 2 Channel 1 RTU 1 Point 1

Point 2
Channel 2 RTU 1 Point 1

Page 36 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7
IFS Status Display > IFS Lines

The IFS Lines

tab provides
information for
the configured
communication
channels on
the IFS server

Page 37 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7
IFS Status Display > IFS RTUs

The IFS RTUs

tab provides
information for
the RTUs
configured in
IFS

Page 38 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7
IFS Status Display > IFS RTU Data

The IFS RTU

Data tab
provides
information for
the configured
data points for
the selected
RTU.

Page 39 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7
IFS Status Display > Show / Hide Columns

Page 40 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Agenda
01 Independent Front-End System

02 Configuration and redundancy

03 User Interface

04 IFS IMM Model

04 Exercises

Page 42 Restricted | © Siemens 2023 | Grid Software

Spectrum PowerTM 7
IFS data structure – Object types in IMM

IfsPair IfsSerialChannel IfsRtu IfsPoint

IfsPoint
…
IfsRtu
IfsRtu
IfsIPChannel IfsRtu IfsPoint
IfsIPChannel
…
IfsSerialChannel

IfsPair IfsIPChannel IfsRtu IfsPoint

IfsPoint
IfsIPChannel IfsRtu IfsPoint

Page 43 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM - Information Model Management

The instance PI is a folder instance that organizes configuration data for different communication types
Relevant to IFS

PI Instance Tree

Page 44 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM - Information Model Management

IFS instance data within PI is important.

The IFS Pairs are defined first,

▪ IFS Channels
(child instances of the IFS Pairs)

▪ IFS RTUs
the IFS RTUs must be added to
appropriate IFS Channels

▪ IFS Points
IFS Points can be linked to a
Characteristic Curve if needed

▪ Characteristic Curves
use for measurement and can be
defined at any time.

Page 45 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM – IFS Channels

▪ IFS Channel instances define the channels that

are associated with an IFS Pair.
▪ There are 2 types of channels:
• Serial channels
• TCP/IP channels.
▪ Each channel must have a Channel Id.
▪ For serial channels, this number is the channel
number.
▪ For TCP/IP channels, the Channel Id should be a
logical number defined higher than the highest
estimated serial channel number.
▪ The number of channels defined in IMM cannot
exceed the maximum number of channels
configured for a Spectrum Front-end block

Page 46 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Spectrum PowerTM 7 – Communication
IFS – IMM – IFS Channels

not for IEC 104

not for IEC 104

not for IEC 104

only DNP3
not for IEC 104
not for IEC 104 only Conitel

not for IEC 104

not for IEC 104
not for IEC 104
not for IEC 104
not for IEC 104
not for IEC 104
not for IEC 104

Page 47 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM – IFS redundant Channels

▪ The channel configured under IFS Pair, defines

how redundant channels of IFS 1 and IFS 2 should applicable for IEC104 and IEC101
behave.

▪ Alternatively, a backup channel can be defined

using a Backup Channel link for channels
configured with point-to-point connection in
independent configuration.

▪ The Channel Id of the backup channel should be

greater than the main Channel Id.

Page 48 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM - IFS RTU

▪ The IFS RTU data defines attributes specific to the

RTU.

▪ After an RTU instance is created, child instances of

type IFS Point can be defined under the RTU.

▪ Each IFS RTU is automatically assigned an RTU Id.

Page 49 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Spectrum PowerTM 7 – Communication
IFS – IMM - IFS RTU

only DNP3
only DNP3

only DNP3, IEC 101

only IEC 101
only DNP3
only DNP3, IEC 101
only DNP3
only DNP3, IEC 101
only DNP3
only DNP3
only DNP3
only for IEC slave protocols only DNP3
only DNP3

only DNP3, PMU

only DNP3, PMU
only Dial connections

only DNP3, IEC 101

Page 50 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM – IFS Point

▪ The IFS Point Data defines the data that is received from
the associated IFS RTU

▪ Each IFS point is automatically assigned a point Id that is

unique within the RTU.

▪ Different Types of IFS Points can be defined

e.g., Singe Pole, Double Pole, Step Position, Analog
Value

▪ Optionally, a characteristic curve can be added to the

IFSpoint. The characteristic curve is used to convert data
received or send from the RTU. (In Curve or Out Curve)

Page 51 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Spectrum PowerTM 7 – Communication
IFS – IMM – IFS Point

only DNP3

only DNP3
only for IEC slave protocols

Page 52 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM – IFS Scan Group

▪ Tied to an IFS RTU

▪ Holds the Scan Group settings

and attributes

▪ Different protocol functions

Page 53 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM – IFS Characteristic Curves

▪ The Characteristic Curves folder is

used to organize curve data
referenced by different
communication types.

▪ A characteristic curve must belong

under an instance of type
characteristic curve Group.

▪ The special curve editor allows you

to define the points of the curve in a
tabular layout.

Page 54 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM – Pseudo Station – IFS Pair

PI Tree – IFS Pseudo Station

▪ The IFS Pseudo station is required by the IFS software.
This section is for information only.
▪ The IFS Pseudo station can be found in IMM by
navigating to /.DoNotModify/Pseudo Stations/IFS.

IFS Pair
▪ When you define an IFS Pair, a B2Block for each front-
end computer is inserted automatically into the IFS
Pseudo station. The naming convention IF<Pair Id>1
and IF<Pair Id>2 is used.

Page 55 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM - IFS Pseudo Station - IFS Channel

▪ When you define an IFS Channel under an

IFS Pair a B2Block and B3Blocks is
inserted automatically into the IFS Pseudo
station.

Page 56 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM - IFS Pseudo Station – IFS RTU

▪ When you define an IFS Rtu, a B3Block with the

same name as the Rtu instance is automatically
inserted into the IFS Pseudo station under the
B2Block named RTU_P1 for Pair_1.

Page 57 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Spectrum PowerTM 7 – Communication
IFS – IMM - IFS Pseudo Station

▪ Element Type and IFS data is defined and created

automatically by the IMM for B2Blocks, and
B3Blocks.
ElementName = IFS-RTU (641)
▪ The status and control TAs are defined with the ElementType = IFSState (480)
special IFSState element type

▪ The IFS Pseudo station handles the Channel

Status and Control TAs for the IFS software to
ElementName = IFS-CHAN (640)
alarm the states of the channels on both Front-
ElementType = IFSState (480)
ends.

Page 58 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Spectrum PowerTM 7 – Communication right click on Job name
IFS – IMM – Online Data Activation
The IMM single instance editor only changes data in the IMM database.

Steps to move data changes into the online operational database:

1. Select the IMM job in which the data was modified.
2. Execute the IMM prepare and activate steps to move the data into the online operational database.
1. Prepare Step: This step performs validation of the data, prepare the change log, and transfer the
data changes into the DBA copy on the Spectrum Power Administrator (ADM) Server.
2. Activate Step: This step distributes the DBA copy (copy 1) of the job to all servers, apply changes to
the Real-Time copy (copy 0), and notify all processes which subscribed for these changes, that is,
IFS and characteristic curve data.
3. Upon job activation, IFS is informed of the database changes, and applies the changes to its internal
image, and immediately uses the applied changes in its processing.

Page 59 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
 Agenda
01 Independent Front-End System

02 Configuration and redundancy

03 User Interface

04 IFS IMM Model

04 Exercises

Page 60 Restricted | © Siemens 2023 | Grid Software

Lab: IFS IMM – Create a Channel

Objective: Set up an IFS Channel in IMM and verify the channel appearance on the IFS Lines Display

Steps:
1. Select or create a new Job in IMM.
2. Navigate to an IFS Pair (/PI/IFS)
3. Open the Context Menu and Press “New”. Select “IfsIPChannel” or “IfsSerialChannel”
4. Define a name for the channel (maximum 16 characters). Press button OK.
5. Introduce the channel settings as desired:
1. Device Type
2. Baud Rate (serial channel)
3. Channel ID
4. IP address (IP channel) 10.240.50.130
5. Character Size (serial channel)
6. Configuration Type
7. Parity (serial channel)
8. Protocol ID
9. Port Number 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413
6. Prepare/Transfer/Activate Job
7. Validate that the new channel appears on the IFS Lines Display

Page 61 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Lab: IFS IMM – Create an IFS RTU

Objective: Set up an IFS RTU in IMM and verify the RTU appearance on the IFS RTU Display

Steps:
1. Select or create a new Job in IMM.
2. Navigate to an IFS Channel (/PI/IFS)
3. Open the Context Menu and Press “New”. Select “IfsRtu”
4. Define a name for the RTU (maximum 16 characters). Press button OK.
5. Introduce the RTU settings as desired:
1. ASDU Address choose one number 3, 4, 5, 6, 7, 8, 9, 10
2. GI Time-out Value
3. Link Address (serial channel)
4. ASDU Address Size 2 bytes
5. Link Size 0 bytes
6. Info Object Address Size 3 bytes
6. Prepare/Transfer/Activate Job
7. Validate that the new RTU appears on the IFS RTUs Display

Page 62 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Lab: IFS IMM – Create a RTU Data Point

Objective: Set up an IFS RTU Data Point in IMM and verify the RTU appearance on the IFS RTUs Data Display

Steps:
1. Select or create a new Job in IMM.
2. Navigate to an IFS RTU (/PI/IFS)
3. Open the Context Menu and Press “New”. Select “IfsPoint”
4. Define a name for the Point. Press button create instance.
5. Introduce the Point settings as desired:
1. Monitor Type: e.g. Single Pole Indication
2. Monitoring Address MvMoment 10000, 10001, … Digital 1000, 1001, 1002, …
3. Add a mandatory SCADA link for association, “Links to other objects”, IfsPoint_LinksTo IFS- Linked To (Info).
4. Optional, link to an instance of type CharacteristicCurveGroup for “Links to other objects”, IfsPoint_HasIn In
Curve.
6. Prepare/Transfer/Activate Job
7. Validate that the new Point appears on the IFS RTUs Data Display

Page 63 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Lab: IFS IMM – Incoming data processing
only possible if RTU
simulation is available

Objective: Have an RTU simulator to communicate with IFS and verify telemetered data showing up in the IFS
displays.

Steps:
1. Have and analog and digital point defined in the RTU simulator connected to IFS
2. Make sure the point address is defined in the IMM Model (IfsPoint) and connected to a SCADA point
3. Establish communication between the IFS and the RTU simulator
4. One the IFS Display, select IFS RTU Data tab and in the drop-down menu select the RTU in which the simulated
points belong to.
5. Verify if the point “Value” changes once the telemetered points is toggled or modified in the RTU simulator

Page 64 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Lab: Manual Switching Redundant IFS Servers
only possible if redundant
IFS servers are available
Objective: Manual switchover of channel between IFS servers

Steps:
1. Check in the Lines display which active channel is operating
2. Manually reconnect the Channel to IFS2 by editing the Lines display and assigning the IFS2
server and save
3. Disconnect the communication path from the Channel to IFS1.
Manually reconnect the RTU to IFS1 by using the RTU status and control display.

Page 65 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Lab: Automatic Switching Redundant IFS Servers
only possible if redundant
IFS servers are available
Objective: Automatic switchover of channel between IFS servers

Steps:
1. Observe in the Lines display that there are active connection on both IFS servers
2. Run down the IFS1 with STOPSOS
1. BaSiDi > System > Status
2. Clicking the Restart button in the IFS 1 server.
3. Restart the IFS1 with INITSOS
1. Both IFS are running in dual process mode.
2. On the System Status (BaSiDi > System > Status) display
3. Both IFS are active

Page 66 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Lab: Manual Blocking of RTU
only possible if RTU
simulation is available

Objective: RTU goes down, failure is detected, points marked as not renewed

Steps:
1. The communication is UP and Running (Oper State=UP)
2. Block the RTU by right clicking the RTU row and selecting OFF for the RTU on the IFS RTU display
(BaSiDi > Communication > IFS RTUs)
▪ The failure of the connected RTU is detected and displayed on the Resource Summary (BaSiDi >
General > Resource Summary)
▪ The communication is DOWN (Oper State=DOWN) in the Lines and RTU display
▪ All the points configured for the RTU are marked not renewed in the RTU Data display

3. Unblock the RTU by right clicking the RTU row and selecting ON for the RTU on the IFS RTU display
▪ The availability of the RTU is detected and a GI request is sent to the RTU (reported on the Resource
Summary)
▪ The communication is UP again (Oper State=UP) in the Lines and RTU display
▪ The not renewed marks are removed from the objects

Page 67 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software
Lab: IFS Configuration using IMM Import

Objective: Configure IFS using an IMM Import.

Steps:
1. Select the IfsPair to export and right-click on it in the IMM Instances pane.
2. Select Export hierarchy from the context menu and enter the pathname of a file in the Export Dialog pane.
3. Select XDF for Output format and select Include subtree.
4. If Include GUID is selected, uncheck the box.
5. Edit the exported XML file for the new data to be imported.
6. Create an IMM job for the Import.
7. In the job, select File -> Import -> XML to server from the IMM menu bar and enter the import file name in
the Import Dialog pane.
8. If Include object identifier (GUIDs) is selected, uncheck the box.
9. Click OK.
10. Execute the IMM validate, prepare activation, transfer, and activate steps to move the data into the online
operational database.

Page 68 Restricted for participants of Grid Software Trainings | © Siemens 2023 | Grid Software