SICAM GridEdge Manual en
SICAM GridEdge Manual en
Table of Contents
E50417-H7640-C641-A3
NOTE
i For your own safety, observe the warnings and safety instructions contained in this document, if available.
Scope
This manual covers only the SICAM GridEdge-related settings and engineering steps.
For general engineering guidelines, refer to the corresponding documents.
Target Audience
System engineers, commissioning engineers, persons entrusted with the setting, selective protection and
control equipment, and operational crew in electrical installations and power plants.
Additional Support
For questions about the system, contact your Siemens sales partner.
Training Courses
Inquiries regarding individual training courses should be addressed to our Training Center:
Siemens AG Phone: +49 (911) 433-7415
Siemens Power Academy TD Fax: +49 (911) 433-7929
Humboldtstrasse 59 E-mail: [email protected]
90459 Nuremberg Internet: www.siemens.com/poweracademy
Germany
Notes on Safety
This manual is not a complete index of all safety measures required for operation of the equipment (module or
device). However, it includes important information that must be followed for personal safety and to avoid
material damage. Information is highlighted and illustrated as follows according to the degree of danger:
! WARNING
WARNING means that death or severe injury may result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! CAUTION
CAUTION means that medium-severe or slight injuries can occur if the specified measures are not taken.
² Comply with all instructions, in order to avoid moderate or minor injuries.
NOTE
i Important information about the product, product handling or a certain section of the documentation
which must be given attention.
The product contains, among other things, Open Source Software developed by third parties. The Open
Source Software used in the product and the license agreements concerning this software can be found in the
Readme_OSS. These Open Source Software files are protected by copyright. Your compliance with those
license conditions will entitle you to use the Open Source Software as foreseen in the relevant license. In the
event of conflicts between Siemens license conditions and the Open Source Software license conditions, the
Open Source Software conditions shall prevail with respect to the Open Source Software portions of the soft-
ware. The Open Source Software is licensed royalty-free. Insofar as the applicable Open Source Software
License Conditions provide for it you can order the source code of the Open Source Software from your
Siemens sales contact – against payment of the shipping and handling charges – for a period of at least
3 years after purchase of the product. We are liable for the product including the Open Source Software
contained in it pursuant to the license conditions applicable to the product. Any liability for the Open Source
Software beyond the program flow intended for the product is explicitly excluded. Furthermore, any liability
for defects resulting from modifications to the Open Source Software by you or third parties is excluded. We
do not provide any technical support for the product if it has been modified.
Preface.......................................................................................................................................................... 3
1 Introduction..................................................................................................................................................9
2 System Configuration................................................................................................................................. 11
2.1 SIEMENS CP-8050............................................................................................................. 12
2.1.1 Updating the SIEMENS CP-8050 Firmware....................................................................12
2.1.2 Preparing SD Card for Installation.................................................................................13
2.1.3 Installing SICAM GridEdge with Prepared SD Card.........................................................16
2.2 SIEMENS IPC 227E.............................................................................................................18
2.2.1 Installing SIMATIC Industrial OS................................................................................... 18
2.2.2 Installing SICAM GridEdge............................................................................................20
2.2.3 Mounting the USB Drive...............................................................................................20
2.2.4 Example Installation.................................................................................................... 21
4 Security.......................................................................................................................................................37
4.1 Security Requirements...................................................................................................... 38
4.2 User Management............................................................................................................ 39
4.3 Backup and Restore...........................................................................................................41
4.4 Diagnosis Log................................................................................................................... 43
4.5 Certificate Management....................................................................................................45
4.6 TCP-UDP Ports................................................................................................................... 47
The Internet of Things (IoT) is poised to be a driver of growth in many business sectors in the coming years,
including the energy industry. In simple terms, IoT is about networking electronic devices over the Internet.
For power-supply systems, connecting to IoT enables all components within a station to make data available in
a cloud-based platform. Applications can then be used to consolidate, link, evaluate, and visualize the infor-
mation for application-specific purposes.
You can utilize the resulting benefits to:
• Enhance the transparency of the plant and equipment status and conditions (such as the availability of
electrical operating values and equipment)
Hardware Requirements
Siemens recommends one of the following systems to run SICAM GridEdge properly:
NOTE
i You need firmware version 04 on your SIEMENS CP-8050 device to run SICAM GridEdge properly.
If you do not have firmware version 04 running on your SIEMENS CP-8050, prepare an SD card and perform
the following steps to update your device.
NOTE
i Since delivery of SIEMENS CP-8050 does not include an SD card, the card has to be ordered separately (see
Hardware Requirements, Page 11).
NOTE
i The SD card has to be empty and formatted using FAT32 file system.
[sc_sd_card_content_FW04, 1, en_US]
[sc_sd_card_content_after_FW04_update, 1, en_US]
In order to install the SICAM GridEdge system, it is necessary to prepare an SD card with the SICAM GridEdge
installation files and mount the SD card to the SIEMENS CP-8050 afterwards.
NOTE
i Since delivery of SIEMENS CP-8050 does not include an SD card, the card has to be ordered separately (see
Hardware Requirements, Page 11).
NOTE
i The SD card has to be empty and formatted using FAT32 file system.
[sc_sd-card_content1, 1, --_--]
[sc_sd-card_content2, 1, --_--]
Underneath the folder lxp there is a folder named config which contains a default configuration.
[sc_sd_card_content, 1, en_US]
• network/interfaces
Configuration of the IP addresses
• ntp.conf
Configuration of the NTP client for time synchronization
• resolv.conf
Configuration of the naming server
In order to configure the IP addresses and the connection to an NTP server, the content of the SD card needs
to be adjusted.
NOTE
[ge_cp-8050_eth, 1, --_--]
Prerequisites
SIEMENS CP-8050 is installed and wired properly.
SIEMENS CP-8050 is connected to station network on port X2 (eth0).
SIEMENS CP-8050 is connected to wide area network on port X3 (eth1).
Procedure
² In order to set specific IP addresses, adjust the file network/interfaces accordingly.
iface lo inet loopback
auto eth0
iface eth0 inet static
address 172.16.0.27
netmask 255.255.0.0
auto eth1
iface eth1 inet static
address 192.168.1.27
netmask 255.255.255.0
gateway 192.168.1.1
# Allow only time queries, at a limited rate, sending KoD when in excess.
# Allow all local queries (IPv4, IPv6)
restrict default nomodify nopeer noquery limited kod
restrict 127.0.0.1
restrict [::1]
If you have your own NTP time servers in the network, use them instead of the global default given.
If you do not have your own private NTP server within your network, consider using public severs in your area
(e.g. from https://www.ntppool.org/)
[ge_cp-8050_card_slot1, 1, --_--]
[ge_cp-8050_card_slot2, 1, --_--]
² Insert the SD card into the slot, apply the plug, and start the SIEMENS CP-8050.
NOTE
Prerequisites
• SIMATIC IPC 227E is installed and wired properly; refer to the SIMATIC IPC227E Quick Install Guide
(https://support.industry.siemens.com/cs/ww/de/view/109477819).
• IPC is connected to station network and wide area network (required for connection to external cloud
platform and for fetching updates of operating system)
• Prepared USB Service Stick for installation of the operating system (for creation instructions refer to
Installation Manual of SIMATIC Industrial OS SIMATIC_Industrial_OS_Vxxxx_Installation_Manual.pdf)
NOTE
i Follow the instructions in chapter 3 "Boot the target with SIMATIC Industrial OS" as written in the section
"Prerequisites". Especially see when and how long to press the <ESC> button to get into the BIOS.
² Open the Setup Utility (SCU) and enable USB Boot in the Boot submenu. Then exit SCU via Exit saving
changes.
² Execute the steps in section Procedure of the installation manual and boot from the attached USB
Service Stick.
² Select Install system.
² Verify that the installed SSD and the image-industrial-os-ipc-......wic.gz file are selected.
NOTE
i If you repeat the installation, the program might find backups. If you want to install completely new, select
Reboot and continue without restoring.
NOTE
NOTE
i A network cable for Wide Area Network must be connected to the X1P1 port.
² Select enp2s0 and define the IP settings for the port X1P1 (DHCP/Static, IP Address, Subnetmask,
Gateway, DNS).
NOTE
NOTE
i If the network configuration between the commissioning and the operation environment differs, you can
reconfigure this using the tool industrial-setup later on.
² For network seperation between Wide Area Network and Station Network, configure the network
settings accordingly for network adapter enp3s0. For Gateway, use 0.0.0.0 here and leave the DNS
empty except there is an internal DNS server in your internal network.
NOTE
NOTE
i If an NTP Server is available in your network, add this as first/primary NTP server.
NOTE
i Since a time synchronization is necessary for a proper connection between GridEdge and the cloud plat-
form, it is strongly recommended to configure NTP properly.
The installation ends with the message You have completed ... and some standard warnings about
possibly failed installations. These are checked in the next step. Confirm with OK and the IPC will reboot.
At the first login, check with the command docker version if the docker framework has been installed. If
no version is replied, check the installation of the Docker CE package.
NOTE
i If you need to configure or reconfigure some settings of the SIMATIC Industrial OS, you can use the
following command: sudo industrial-setup
NOTE
i If you already have a running SICAM GridEdge system and want to upgrade to a newer version, you have to
create a backup of the current configuration and restore the backup after updating the system., see
4.3 Backup and RestoreGridEdge manual, chapter 4.3 Backup and Restore.
² Copy the complete content of the package to the IPC using SSH.
- or -
² Copy the complete content of the package to the IPC using a USB stick.
NOTE
i Keep in mind that the SIMATIC Industrial OS does not automatically mount the USB stick. This has to be
done manually, see 2.2.3 Mounting the USB DriveGridEdge manual, chapter 2.3 Mounting the USB Drive.
² Extract the package and change the directory to the extracted folder.
² Add execution rights to scripts: chmod +x *.sh
² Execute the script sicamgridedge_setup.sh with administrator rights.
² When prompted, enter the IP address of the interface connected to the substation network (X2P1) .
After the installation, the SICAM GridEdge system is up and running.
NOTE
i If you update the network settings of the IPC where SICAM GridEdge is running, it is necessary to re-create
the self-signed certificate used by the SICAM GridEdge Web Interface.
To do so, execute the following script:
sicamgridege_setup.sh -n
² Copy the SICAM GridEdge setup data into the home directory:
edge@NANOBOX-3:~$ cp -r /media/usb-drive/SICAM_GridEdge_1.1 ~
² Unmount the USB drive:
edge@NANOBOX-3:~$ sudo umount /dev/sdb1
This section contains a guideline for configuring a SICAM GridEdge for use in combination with the Siemens
Grid Diagnostic Suite Applications.
3.1 Access to SICAM GridEdge Web Interface 24
3.2 General Settings 25
3.3 Application Configuration 30
3.4 Connection Status 35
3.5 Maintenance 36
The SICAM GridEdge Web interface is available at https://<STATION_LAN_IP>:8900, for example https://
192.168.1.1:8900.
[sc_SICAM_GridEdge_WebInterface, 2, en_US]
When you log on to SICAM GridEdge for the first time you need to set a password.
[sc_SICAM_GridEdge_Cloud_connection, 3, en_US]
NOTE
² From the Cloud list box select the cloud platform you want to send data to (MindSphere, Azure, On-
Premise). Depending on the selection or option you will have to choose different settings.
[ic_mindsphere_spec, 1, en_US]
Azure-Specific Settings
[ic_azure_spec, 1, en_US]
² Enter the IoT Hub Name according to your configuration visible in Azure portal.
² Enable MQTT Over WebSockets to send data via Websockets instad of native MQTT (this option can help
solving issues with firewall limitations in your network).
On-Premise Settings
[ic_on-premise_spec, 1, en_US]
NOTE
i For the Topic Name it is possible to use tags which are replaced later on in the GridEdge system for
publishing data.
• Abbreviation Meaning
– T Time Series key and delta frame
– TM Time Series meta frame
– E Events key and delta frame
– EM Events meta frame
– F Files key and delta frame
– FM Files meta frame
² To upload a (intermediate) Certificate Authority in a PKCS#12 container format, click CA PKCS#12 File.
If your PKCS#12 container is encrypted with a password, enter the password in the import dialog. If your
PKCS#12 file is not encrypted, leave the corresponding field empty.
Click Open to proceed.
For further information on certificate handling refer to 4.5 Certificate Management.
² Upload the Certificate Authority of the MindSphere Broker.
If no filter string is entered, all data will be published. Several filter keys can be entered separated by semico-
lons. The effect of the data filter on the data points can be viewed in the resulting table:
[sc_SICAM_GridEdge_data_filter, 2, en_US]
NOTE
i As a help for selecting the filters properly, adding a semicolon (";") at the end of the filter string will show
all possible data points to be selected in the data table below.
[sc_SICAM_GridEdge_station_settings, 3, en_US]
² Add the IP address range of the devices in the station network or dedicated IP addresses in Target IP
Addresses.
Example:
Target IP Addresses = 192.168.11.*;192.168.10.85
If the corresponding client is active (e.g. IEC 61850 Client, see Configuring the IEC 61850 Client,
Page 30), SICAM GridEdge will automatically scan for devices in the IP Range 192.168.11.1 to
192.168.11.254 and will additionally communicate with the device 192.168.10.85.
[sc_SICAM_GridEdge_IEC61850_Client, 3, en_US]
Protection Devices
• Publisher ID: This is the ID which is used to transfer data to the cloud platform
• Device Connection: Shows if the device is currently connected, and also a timestamp when the status
changed the last time
• Cloud Connection: Shows if the device is currently connected to the cloud platform, and also a timestamp
when the status changed the last time
[sc_SICAM_GridEdge_conection_status, 1, en_US]
3.5 Maintenance
Using the Maintenance menu, you can backup and restore the configuration of SICAM GridEdge and also
change the password of the Web interface.
[sc_SICAM_GridEdge_Maintenance, 2, en_US]
Password
In the Password tile, you can change the password of the current logged in user.
[sc_SICAM_GridEdge_security, 3, en_US]
• Assure system restoration without or only with marginal data loss in case of a system failure
SIMATIC Industrial OS
For security guidelines regarding SIMATIC Industrial OS, refer to the manual of SIMATIC Industrial OS.
NOTE
i Detailed information about securing a Linux system can be found in the manual from debian.org (https://
www.debian.org/doc/manuals/securing-debian-manual/index.en.html)
NOTE
i Only the salt and the password hash are stored in the database. Therefor the algorithm HMACSHA256 is
used.
[sc_SICAM_GridEdge_sec_passwordchange, 2, en_US]
Logging Off
For a proper logoff from SICAM GridEdge, either close all instances of your Web browser or log out using the
corresponding symbol in the upper right corner:
Also, if you leave SICAM GridEdge Web interface unattended the system will automatically log off your current
session after 20 minutes.
[sc_SICAM_GridEdge_logoff, 1, en_US]
NOTE
i The backup will be encrypted with the entered password and AES128-SHA256 encryption.
NOTE
i Each time you update to a newer version of SICAM GridEdge, it is recommended to use the backup and
restore mechanism.
Archiving a Project
[sc_SICAM_GridEdge_sec_backup_pw, 2, en_US]
² On the Maintenance page, in the Configuration Backup & Restore tile, click Save.
² In the Save Configuration dialog, enter the Password to be used to protect your archived project.
² Click Save.
Restoring a Project
In order to restore a project you have to select your previously created backup file and enter the used pass-
word.
[sc_SICAM_GridEdge_sec_restore, 2, en_US]
² On the Maintenance page, in the Configuration Backup & Restore tile, click Restore.
² In the Restore Configuration dialog, enter the Password.
² Click Restore from file (.geconf).
NOTE
i After restoring all modules, SICAM GridEdge will be restarted with the restored configuration.
NOTE
i The password for the SICAM GridEdge user will also be stored along with the backup. After restoring, the
password which was present at the time the backup was created will be active.
NOTE
i Per default, only the last 100 log entries will be shown.
To select the amount of log entries to be show, use the radio buttons in the upper right corner.
NOTE
[sc_SICAM_GridEdge_sec_logging, 3, en_US]
Structure of Events
Element Description
Date/Time (UTC) Date and Time when the event was received or logged
Time format: yyyy-mm-dd hh:mm:ss.tt (time when the event was created)
All events are written in UTC time.
Type Levels of the event: Info > Warning > Error
Element Description
Source The name of the source that generated the log entry
Message The message part of an event
Depending on the event, the message text can contain additional information of
the affected component (for example Publisher ID, Device IP Address).
[sc_SICAM_GridEdge_sec_certman, 3, en_US]
With SICAM GridPass you can easily generate a intermediate certificate authority which includes all needed
information for SICAM GridEdge.
To enable a TLS secured connection to a cloud platform, SICAM GridEdge needs an intermediate certificate
authority (including public and private key; this certificate needs SHA-256 with RSA-4096 encryption)
uploaded to the Web interface as well as the root certificate authority of the cloud platform (refer to Config-
uring the Cloud Connection, Page 25).
In order to enable the mandatory end-to-end encryption (TLS) between the SICAM GridEdge and the MQTT
Broker of MindSphere, it is required to upload the (intermediate) certificate authority to SICAM GridEdge Web
Interface (including public and private key; this certificate needs SHA-256 with RSA-4096 encryption) as well
as the root certificate authority of the cloud platform.
NOTE
i The details how to create/get the required certificates are described in the MindSphere IoT Engineering
Guide.
Whenever SICAM GridEdge finds a new device in the station network (refer to Configuring the Station
Settings, Page 29) a certificate is created for the device which is used for the cloud connection and stored in
the SICAM GridEdge database.
NOTE
i The device certificates are created using SHA-256 with RSA-4096 encryption.
NOTE
i If you need to update the intermediate certificate authority (e.g. because it is expired or revoked), you only
need to upload the updated intermediate certificate authority to the SICAM GridEdge system. SICAM Grid-
Edge will automatically update also the created device certificates based on the new intermediate certifi-
cate authority.
Topic Description
HTTPS For access to the Web interface of SICAM GridEdge as well as for the transfer of files to Mind-
Sphere, the secure HTTPS communication protocol is used. Unencrypted HTTP access is not
supported.
SICAM GridEdge supports the following HTTPS features:
• The open source software OpenSSL is used for the TLS implementation.
• SICAM GridEdge generates a self-signed TLS-certificate and is therefore not signed and
confirmed by a certification authority. When using the SICAM GridEdge Web Interface,
all browsers will show a message regarding an unknown certificate warning about an
untrusted connection. Due to the authentication scheme used by browsers, Siemens
cannot provide certificates (for example, during assembly) to be used for HTTPS with
browsers. This is because either the DNS name or the IP address of the device has to be
part of the signed certificate, both of which are ultimately determined after installation
at the site of the customer. That is why the products generate a self-signed certificate
after the IP address has been set. This self-signed certificate has to be trusted in a secure
way on all clients used to access this device. You can find the recommended way of
trusting self-signed certificates in the document Certificate trusting in Web browsers.
You can find this document at http://www.siemens.com/gridsecurity, Downloads >
Downloads Cyber Security General > Application Notes.
The certificate is generated once during first startup of SICAM GridEdge and uses all
available IP addresses as well as the hostname.
• The transfer of files received from clients/devices to Mindsphere is encrypted. Therefor
the corresponding certificate is used.
MQTT • SICAM GridEdge establishes a TLS secured connection to the external cloud platform. To
do so, SICAM GridEdge automatically creates certificates for the connected clients based
on the configured certificate authority (refer to 4.5 Certificate Management)
NOTE
i Deploy in a secured environment only: Siemens recommends protecting network access to its energy auto-
mation products with appropriate mechanisms (for example, firewalls, segmentation, VPN). It is advised to
configure the environment according to the operational guidelines in order to run the devices in a
protected IT environment.
You can find the recommended security guidelines to Secure Substations at http://www.siemens.com/grid-
security, Cyber Security General Downloads > Manuals.
The following table lists the programs and services that communicate between members of the network. If 2
members are in different subnetworks, the ports and protocols must be opened in the firewalls between the
subnetworks.
NOTE
i If you have configured a proxy for filtering by URL, keep in mind that the URLs for Uploading Files and for
MQTT Connection differ.
Defaults for MindSphere:
• MQTT: mqtt.eu1.mindsphere.io