Im32p01b10 01en
Im32p01b10 01en
Im32p01b10 01en
Manual
ProSafe-RS User’s Guide
IM 32P01B10-01EN
IM 32P01B10-01EN
6th Edition
i
Introduction
This manual provides the overview of ProSafe-RS. Please read first to understand the prod-
uct. Links are also listed to guide you to the descriptions of ProSafe-RS usage for each situa-
tion.
This manual consists of the following parts:
• Part A Overview of ProSafe-RS
Provides an overview of the typical functions of ProSafe-RS. ProSafe-RS can be used ei-
ther on a physical computer or on a virtual computer that is built on a virtualization plat-
form.
• Part B ProSafe-RS Security
Describes the security function that should first be understood when handling ProSafe-
RS products.
• Appendix 1 Glossary
A glossary of terms used in the user manual
• Appendix 2 List of links
A list that guides you to the description of ProSafe-RS usage in typical situations.
n Notes on Software
• YOKOGAWA makes no warranties, either expressed or implied, with respect to the Soft-
ware Product's merchantability or suitability for any particular purpose, except as speci-
fied in the warranty terms.
• Purchase the appropriate number of licenses of the Software Product according to the
number of computers to be used.
• No copy of the Software Product may be made for any purpose other than backup; other-
wise, it is deemed as an infringement of YOKOGAWA's Intellectual Property rights.
• Keep the software medium of the Software Product in a safe place.
• No reverse engineering, reverse compiling, reverse assembling, or converting the Soft-
ware Product to human-readable format may be performed for the Software Product.
• No part of the Software Product may be transferred, converted, or sublet for use by any
third-party, without prior written consent from YOKOGAWA.
Documentation Conventions
n Symbols
The following symbols are used in the User's Manuals.
Indicates precautions to avoid a danger that may lead to death or
WARNING severe injury.
n Typographical Conventions
The following typographical conventions are used throughout the User's Manuals.
n Drawing Conventions
Drawings used in the User's Manuals may be partially emphasized, simplified, or omitted for
the convenience of description.
Drawings of windows may be slightly different from the actual screenshots with different set-
tings or fonts. The difference does not hamper the understanding of basic functionalities and
operation and monitoring tasks.
n Trademark Acknowledgments
• CENTUM, ProSafe, Vnet/IP, PRM, Exaopc, FieldMate Validator, and STARDOM are reg-
istered trademarks or trademarks of Yokogawa Electric Corporation.
• The names of corporations, organizations, products and logos herein are either regis-
tered trademarks or trademarks of Yokogawa Electric Corporation and their respective
holders.
CONTENTS
PART-A Overview of ProSafe-RS................................. A-1
A1. Requirements..................................................................................... A1-1
A1.1 Hardware requirements............................................................................. A1-2
A1.2 Software requirements.............................................................................. A1-5
A2. Overview of SCS................................................................................ A2-1
A2.1 SCS hardware configuration.....................................................................A2-4
A2.2 SCSP2 hardware configuration................................................................ A2-9
A2.3 RAS (Reliability, Availability, Serviceability) functions of SCS............A2-10
A2.3.1 SCS operating mode..................................................................A2-12
A2.3.2 Security level of SCS................................................................. A2-15
A2.3.3 Diagnosis for hardware.............................................................. A2-17
A2.4 Dual-redundancy in the SCS...................................................................A2-18
A2.4.1 Redundant configuration in SCS................................................A2-19
A2.4.2 CPU redundant status................................................................A2-22
A3. Outline of the safety system generation function.......................... A3-1
A3.1 Window components common to builders............................................A3-12
A3.2 Types of downloading............................................................................. A3-16
A4. Configuration of maintenance function...........................................A4-1
A5. Overview of the SCS Maintenance Support Tool............................ A5-1
A5.1 Relationships among functions of SCS Maintenance Support Tool.............
..................................................................................................................... A5-2
A5.2 Application examples at maintenance..................................................... A5-4
A5.3 Customization of the SCS Maintenance Support Tool window............. A5-7
A6. Virtualization platform....................................................................... A6-1
A6.1 Outline of virtualization platform..............................................................A6-2
A6.2 System configuration of virtualization platform..................................... A6-3
A6.2.1 Virtualization host computer.........................................................A6-4
A6.2.2 Thin client.....................................................................................A6-6
A6.3 Software environment............................................................................... A6-7
A6.3.1 Virtualization host computer.........................................................A6-8
A6.3.2 Thin client.....................................................................................A6-9
A6.3.3 License.......................................................................................A6-10
CONTENTS
PART-B ProSafe-RS security........................................ B-1
B1. Overview of ProSafe-RS security..................................................... B1-1
B2. Security for project database........................................................... B2-1
B3. Security of SCS.................................................................................. B3-1
B4. NIU status and security..................................................................... B4-1
B4.1 Status of the NIU maintenance port......................................................... B4-2
B4.2 Operation mode of the NIU........................................................................B4-3
B4.3 Shifting the Status of the NIU................................................................... B4-5
B4.4 Checking the status of the maintenance port of the NIU....................... B4-6
B5. Security of SCS Maintenance Support tool.....................................B5-1
B6. Access control and history management........................................B6-1
CONTENTS
Appendix
Appendix 1. Glossary...........................................................................App.1-1
Appendix 2. List of links...................................................................... App.2-1
A. Overview of ProSafe-RS
ProSafe-RS is the Safety Instrumented System (SIS) comprising Safety Control Station (SCS)
and Safety Engineering PC (SENG).
This section describes the following topics to give an overview of ProSafe-RS:
• Operating Environment
• Overview of the SCS
• Configuration of System Generation Function
• Configuration of Maintenance Function
• Configuration of the SCS Maintenance Support Tool
• Virtualization platform
A1. Requirements
This section explains the hardware and software requirements. It also explains the software
that can collaborate with ProSafe-RS and software that can co-exist on the same computer.
SEE
ALSO For more information about hardware on which the virtualization platform runs, and Yokogawa system prod-
ucts running on virtualization platform virtual machines, refer to:
IA system products virtualization platform (GS 30A05B10-01EN)
Table A1.1-2 Hardware requirements for SENG (Windows Server 2016, Windows 2008 R2)
Component Requirements
CPU Xeon 4 core (2.2 GHz) equivalent or above
Main memory 8 GB or more
Hard disk space Available space of at least 100 MB x the number of SCS units
Table A1.1-4 Hardware requirements for SENG (Windows Server 2016, Windows 2008 R2)
Component Requirements
CPU Xeon 4 core (2.2 GHz) equivalent or above
Main memory 8 GB or more
Hard disk space Available space of at least 60 GB
• When using the SOE Viewer Package, SOE OPC Interface Package and Forced I/O
Viewer Package:
Table A1.1-6 Hardware requirements for SENG (Windows Server 2016, Windows 2008 R2)
Component Requirements
CPU Xeon Dual Core (2.93 GHz) or higher (mandatory)
Main memory 4 GB or more
Hard disk space • Available space of at least 20 GB (required)
• Available space of at least 40 GB (recommended)
The components for which requirements are same irrespective of OS and license conditions
are summarized in the following table.
Table A1.1-7 SENG hardware requirements (components for which requirements are the same for all
the conditions)
Component Requirements
Display • When using a square monitor, a resolution of at least SXGA (1280x1024), True
Color (required)
• When using a wide-screen monitor, a resolution of at least WXGA+ (1440×900),
True color
Graphics DirectX 9 graphic processing unit or equivalent, and supports the following (mandato-
ry):
• Windows Driver Display Model (WDDM)
• Pixel Shader 2.0
• 32 bits per pixel
• 128 MB graphic memory
Peripheral unit • DVD-ROM drive (mandatory)
• 1 PCI Express slot is necessary for the Vnet/IP interface card (mandatory) (*1)
• Mouse (mandatory)
*1: When connecting the computer to the Vnet/IP.
Table A1.1-8 Hardware requirements for a file server (Windows Server 2016, Windows Server 2012 R2,
Windows Server 2008 R2, Windows Server 2008)
Component Requirements
CPU 2 GHz or higher
Main memory 2 GB or more
Continues on the next page
l Supported OS
Windows OS versions to be supported by ProSafe-RS are as follows:
• Windows 10 Enterprise 2016 LTSB (64-bit) (*1)
• Windows 10 IoT Enterprise 2016 LTSB (64-bit) (*1)
• Windows 7 Professional SP1 (64-bit)
• Windows Server 2016 Standard (64-bit)
• Windows Server 2008 R2 SP1 Standard (64-bit)
*1: For the LTSB model, whose functions are not updated, only security patches and hotfixes are provided. Exercise caution be-
cause Windows 10 Enterprise LTSB is functionally different from other Windows 10 models. LTSBs are sold only with volume
licenses.
TIP Windows Server 2008 SP2 Standard Edition and Windows Server 2012 R2 can be used as a domain control-
ler or file server not running ProSafe-RS software.
Before installing ProSafe-RS, make sure that a Windows OS version and service pack appro-
priate for the ProSafe-RS software release number are installed on the computer.
IMPORTANT
• On a Windows pre-installed computer, various Windows utilities and other software may
have been installed in addition to the Windows OS. These additional functions are not on-
ly unnecessary for SENG but also can disturb its operations. To avoid disturbance to op-
erations, reinstall the Windows OS.
• It is assumed that security patches are applied according to the customer's security poli-
cy. YOKOGAWA recommends to apply security patches to ProSafe-RS systems. It is rec-
ommended to apply all required security patches before the system goes into operation
and also apply security patches that are released after the system went into operation as
promptly as possible. YOKOGAWA offers security patch application services. Contact
YOKOGAWA Service for more information.
• When using a Windows 10 Enterprise LTSB computer, some customization is required
when you install Windows 10.
SEE
ALSO For more information about the procedure for the customization at installation of Windows 10 Enterprise
LTSB, refer to:
Appendix 5., “Customization at Installation of Windows 10” in Installation Guide (IM 32P01C50-01EN)
l .NET Framework
When the ProSafe-RS software is installed, .NET Framework is automatically installed. How-
ever, .NET Framework included in the ProSafe-RS software medium will not be installed auto-
IMPORTANT
Use only the volume license version of Microsoft Word and Microsoft Excel.
l IT security setting
• You can fortify computer security. To fortify the security, select "Standard model" with the
IT Security Tool at installation of both ProSafe-RS and CENTUM VP.
• If you integrate ProSafe-RS with CENTUM VP earlier than R5.01, manually relax some
security items according to the IT security setting of CENTUM VP.
SEE
ALSO For more information about IT Security Tool, refer to:
6.1, “IT Security Tool” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
SEE
ALSO For more information about iDefine version that can coexist with ProSafe-RS and CENTUM VP, refer to:
“n Use of iDefine” on page A1-9
For more information about installing the control bus driver, refer to:
B3.3.1, “Installing the Control Bus Driver” in Installation Guide (IM 32P01C50-01EN)
For more information about setup of Windows with CENTUM VP, refer to:
B4.2, "Setting Up Windows" in CENTUM VP Installation (IM 33J01C10-01EN)
l Version
When using ProSafe-RS R4.05.00, the recommended version of FAST/TOOLS is R10.03 or
later. However, FAST/TOOLS R10.03 does not support the following devices and functions:
• N-IO nodes
• Mapping blocks S_HSDTR, S_GASDTR
• Fire and gas communication
• S2CP471
n Use of iDefine
l Coexistence of ProSafe-RS and iDefine on the same computer
When using ProSafe-RS R4.03 or later, iDefine and ProSafe-RS software can coexist.
When using ProSafe-RS R4.05 or later, iDefine software can coexist on the computer where
ProSafe-RS and CENTUM VP R6.07 or later software coexist. iDefine and CENTUM VP
alone cannot coexist.
IMPORTANT
You cannot install iDefine software on the computer where ProSafe-RS and PRM client soft-
ware coexist.
l Version
The following table shows the version numbers of ProSafe-RS and iDefine that can be used
in combination.
n Use of PRM
l Coexistence of ProSafe-RS and PRM on the same computer
Whether or not the PRM and ProSafe-RS software can run on the same computer is as fol-
lows:
• A PRM server and ProSafe-RS software cannot run on the same computer.
IMPORTANT
You cannot install iDefine software on the computer where ProSafe-RS and PRM client soft-
ware coexist.
You can ignore this error message when the DTM name is not YFGW410.
l Version
When using ProSafe-RS R4.05.00, the recommended version of PRM is R3.30 or later. PRM
versions earlier than PRM R3.30 do not support SCSP3 station. Also, PRM versions earlier
than R3.12 cannot be connected to the narrowband mode of Vnet/IP-Upstream.
n Use of Exaopc
l Coexistence of ProSafe-RS and Exaopc on the same computer
Exaopc and ProSafe-RS software cannot run on the same computer.
l Version
When using ProSafe-RS R4.05.00, the recommended version of Exaopc is R3.78 or later.
When using Exaopc of the version that is not recommended, the following restriction applies:
n Use of Exaquantum
l Coexistence of ProSafe-RS and Exaquantum on the same computer
Exaquantum and ProSafe-RS software cannot run on the same computer.
l Version
When using ProSafe-RS R4.05.00, the recommended version of Exaquantum is R3.01 or lat-
er. ProSafe-RS can be connected to Exaquantum R2.20 or later. However, because the ver-
sions of Exaquantum earlier than R2.60 do not support the IT security function, you must se-
lect the Legacy model to use the IT security function of ProSafe-RS.
Control bus
SCS
DCS of other companies
Control bus communication function (Higher-level System)
Modbus
Application logic Communication
execution function External
communication function Subsystem
Application logic
execution Modbus
Communication
AIO/DIO data
input/output function ProSafe-SLS
l Application logic
An SCS executes application logic written in the IEC 61131-3 program language. The applica-
tion logic is defined by the user using Multi Language Editor and downloaded to the SCS.
SEE
ALSO For more information about Structured Text (ST), refer to:
2., “Structured text” in POU Reference Manual (IM 32P03B20-01EN)
For more information about Function Block Diagram (FBD), Ladder Diagram (LD), refer to:
1., “Overview of POU” in POU Reference Manual (IM 32P03B20-01EN)
PSM: Power supply module for SCU and SNU (SPW48x) ESB bus
CPU: Processor module (SCP461 S2, S2CP471)
SEC40x: ESB bus coupler module SCU
S S
SSB401: ESB bus Interface module 2 2 S S S S C C P P SCSP3
SNT4x1: Optical ESB bus repeater master module E E N N E E
N N T T C C P P S S
SNT5x1: Optical ESB bus repeater slave module 4 4 4 4 4 4 U U M M
S2EN40x: N-ESB bus coupler module 0 0 x x 0 0
x x 1 1 x x
FIO: FIO I/O module
PSU: Power supply unit for N-IO node (S2PW50x)
S2EN501: N-ESB bus module
N-IO: N-IO I/O module
N-ESB bus Optical ESB bus
S S S S
2 2 2 2
E E P P E E P P
N N N N
N N S S - - N N S S - -
5 5 U U 5 5 U U
0 0 I I 0 0 I I
1 1 O O 1 1 O O
N-ESB bus Optical ESB bus
N N N N N N N N
- - - - - - - -
I I I I I I I I
O O O O O O O O
S S S S
2 2 2 2
E E P P E E P P
N N N N
N N S S - - N N S S - -
5 5 U U 5 5 U U
0 0 I I 0 0 I I
1 1 O O 1 1 O O
N N N N N N N N
- - - - - - - -
I I I I I I I I
O O O O O O O O
PSM: Power supply module for SCU and SNU (SPW48x) ESB bus
CPU: Processor module (SCP461 S2, S2CP471)
SEC40x: ESB bus coupler module
SCU
SSB401: ESB bus Interface module S S S S C C P P SCSP2/SCSP3
SNT4x1: Optical ESB bus repeater master module F F F F N N E E
T T C C P P S S
SNT5x1: Optical ESB bus repeater slave module I I I I 4 4 4 4 U U M M
S2EN40x: N-ESB bus coupler module O O O O x x 0 0
1 1 x x
FIO: FIO I/O module
PSU: Power supply unit for N-IO node (S2PW50x)
S2EN501: N-ESB bus module
N-IO: N-IO I/O module
Optical ESB bus ESB bus
SNU SNU
S S S S S S P P S S P P
F F F F N N N N S S F F F F F F F F S S
T T T T B B S S B B S S
I I I I 5 5 4 4 4 4 M M I I I I I I I I 4 4 M M
O O O O x x x x 0 0 O O O O O O O O 0 0
1 1 1 1 1 1 1 1
ESB bus
ESB bus
Optical ESB bus
SNU SNU
S S S S P P S S P P
F F F F F F N N S S F F F F F F F F S S
T T B B S S B B S S
I I I I I I 5 5 4 4 M M I I I I I I I I 4 4 M M
O O O O O O x x 0 0 O O O O O O O O 0 0
1 1 1 1 1 1
ESB bus
N-IO node
S S
2 2
E E P P
N N
N N S S - -
5 5 U U
0 0 I I
1 1 O O
N N N N
- - - -
I I I I
O O O O
SNU
S S S S P P
F F F F F F N N S S
T T B B S S
I I I I I I 5 5 4 4 M M
O O O O O O x x 0 0
1 1 1 1
ESB bus
Figure A2.1-3 Configuration example of an N-IO node and safety node unit connection
• Separating N-IO nodes and safety node units, and connecting them together
When N-IO nodes and safety node units are separated from each other, and they are
connected with the safety control unit, the N-IO nodes-only connection and the safety
node units-only connection are combined.
The following figure shows a configuration example when N-IO node and safety node unit
are separated and connected together.
S S S S P P
2 2 F F F F F F F F S S
P P B B S S
E E N N I I I I I I I I 4 4 M M
N N S S - - 0 0
5 5 O O O O O O O O
0 0
U U I I 1 1
1 1 O O
N N N N
- - - -
I I I I
O O O O
Figure A2.1-4 Configuration example when N-IO node and safety node unit are separated and connec-
ted together
PSM
PSM
IOM
IOM
IOM
IOM
IOM
IOM
SEC402
SEC402
SCP461
SCP461
-SEC402 (always redundant)
-IOM (up to 6 or 8 modules can be mounted)
PSM
PSM
IOM
IOM
IOM
IOM
IOM
IOM
IOM
IOM
SSB401
SSB401
IOM
IOM
IOM
IOM
IOM
IOM
IOM
IOM
SSB401
SSB401
respectively, in one SCS.
However, the maximum number of nodes is 13
in total on both connectors.
Input Input -PSM (always redundant)
-SSB401 (always redundant)
Output Output -IOM (up to 8 modules can be mounted)
ESB Bus
PSM
PSM
PSM
PSM
IOM
IOM
IOM
IOM
IOM
IOM
IOM
IOM
SSB401
SSB401
IOM
IOM
IOM
IOM
IOM
IOM
IOM
IOM
SSB401
SSB401 ESB bus cables are used to connect between
SEC402 and SSB401. The allowable cable
length is 10 m for the upper and lower
connectors respectively, and 20 m in total
on both connectors.
SENG HIS
V net
Diagnosis
System Alarms
Information
Download,
Changing
SCS FCS
Actions
RAS
function
Input/output
modules
Loading
Mode
Can be transferred
from all other modes
SCS stopped
SEE
ALSO For more information about Data value in unlocked / locked status and output disable / enable status, refer to:
A6.2, “I/O variable” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about Output enable operation, refer to:
C8., “Output enable operation” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about SCS State Management Window, refer to:
H1.2, “SCS State Management window” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
*1: It is allowed to reset the security level from Level 1 to Level 2 via the RST input in the SYS_SECURE block,
regardless of the security level change enable/disable status of SYS_SEC_CTL.
l Online level
The Online Level is a security level to be used when normal operation is performed in SCS.
The SCS itself provides security of the Online Level by controlling access to the memory from
the outside.
The Online Level is separated into two levels according to limits of functions which can be
used.
l Offline level
The Offline Level is a security level to be used when a regular operation is not performed in
SCS. This is displayed as "Level 0" on the LED of SCS or the SCS State Management win-
dow of SENG. In the Offline Level, SCS does not limit access to SCS from the outside. How-
ever, information which was used at test may be stored in SCS databases depending on op-
erations performed by those tools.
IMPORTANT
To restore an SCS to Online Level from Offline Level, restart the SCS or do offline download.
This ensures that the system returns to the security level for normal operation.
l Temperature monitoring
The SCS monitors the surrounding temperature of the N-ESB module, as well as the upper
limit and lower limit value in the hardware. It monitors whether the temperature exceeds the
prescribed value or not.
n CPU module
• The CPU module on the standby side performs the same control processing as the con-
trol side even while it is in the standby status. For this reason, it is possible to take over
outputting data immediately after the control right is switched. Moreover, the operating
mode of the SCS does not change.
• Only the CPU on the control side accesses the hardware composing the SCS and the
CPU on the standby side always sets the equivalent value as the processing result.
Therefore, the CPU modules on both sides always perform processing using the same
data.
• In redundant configuration, if the CPU module on the standby side is not in the STBY sta-
tus and the control right cannot be switched, the same operation as single configuration
CPU module is performed.
• SOE data related to discrete inputs might be lost when the control right is switched be-
tween the CPU modules.
• With the CPU module of SCSP2, the data loaded with the previous scan may be used
instead of updating the data with the value from the input module when performing a scan
immediately after a control right switchover of the CPU. Also note that data loaded from 1
or 2 scans earlier may be used with subsystem communication modules.
• With the CPU module of SCSP3, the data loaded with the previous scan may be used
instead of updating the data with the value from the input module or fire and gas commu-
nication module when performing a scan immediately after a control right switchover of
the CPU. Also note that data loaded from 1 or 2 scans earlier may be used with subsys-
tem communication modules.
n F-SB bus
The F-SB bus has redundant configuration.
• The F-SB bus is normally used at the same time on both sides.
• If an error occurs in either F-SB bus, the SCS continues communication using only the
normal ESB bus on the other side.
• An erroneous F-SB bus is monitored for normal recovery at regular intervals.
n Vnet/IP communication
Vnet/IP is redundant. Independent subnets using bus 1 and bus 2 comprise redundant buses.
Normally, bus 1 is used for control communication. If a communication error occurs on bus 1,
bus 2 is used to perform control communication.
n CPU status
In order to show the status of a redundant configuration, it is necessary to indicate the status
of each CPU separately. The operating status of the CPU is called the CPU status.
• The CPU status indicates the operating status of the CPU.
• The processing of the SCS references the CPU status as necessary. The user can check
the CPU status via the CPU's LED, the SCS State Management window of the SENG,
and the Status Display view of HIS.
• If an error occurs in the standby CPU, the FAIL status is notified to the application logic
via a system block.
The figure below illustrates the CPU status shift. Note that in order to explain the CPU status,
the operating modes it can shift to the Initial mode are called "CTRL" and "STBY." These indi-
cate whether the CPU has the control right and are specific to the redundant status, i.e., not
related to the operating mode.
CPU Fail
CTRL
STBY
CPU Fail
(a)
(e)
FAIL CTRL control side
CTRL
FAIL CPU status
FAIL
stand-by side
STBY
CPU status
Single Operation
l APC status
The APC status refers to the status where the data in the CPU memory is being copied from
the control side to the standby side.
The APC status can be checked by the LED on the CPU, the SCS Status Display window of
the SENG or the Status Display view on the HIS. The start and end of the APC status are
notified via a diagnostic information message.
l Editor and tools that are used for I/O list engineering
The following table shows the editors and tools used when performing I/O list engineering.
You can start the SCS Manager from the System Structure Navigator in AD Organizer.
(*2)
AD Suite
AD Organizer
Safety
Safety I/O Editor Communication IOM Definition Editor
I/O Editor
RS Generation Manager
(*1)
SENG
SCS Manager
Link Hardware
Binding List View Dictionary View I/O Wiring View
Architecture View Architecture View
SCS Link
Multi-Language SCS Project I/O Parameter Communication SCS Constants
Transmission
Editor Properties Builder Builder I/O Builder Builder
SCS
Output Passwords
Safety subsystem
SCS project Link transmission communication
Binding SCS parameters
attribute definition definition I/O definition
SCS
*1 : In the case of I/O list engineering, you can reflect the safety I/O list, safety communication I/O list, and IOM definition to the SCS
Manager builder by running the reflection process through RS Generation Manager. If you run the reflection process on the
engineering data that was created by using iDefine through RS Generation Manager, the application data can be reflected to the
Multi-Language Editor and SCS.
*2 : AD Organizer exports the data that was created from the safety I/O list, safety communication I/O list, and IOM definition to iDefine.
*3 : AD Organizer imports the engineering data that was created by using iDefine.
Legends
: Builder or editor
: Definition, file, parameter, or variable
: Group of definitions or files
: Download of builder definitions
: Communication
l AD Organizer
AD Organizer is installed in the SENG computer. You can perform the ProSafe-RS engineer-
ing by using AD Organizer. AD Organizer comes with some built-in engineering tools, and
SCS Manager is one of them.
l ADMDB
This is the server database that stores all the engineering data that is included in the AD
Server. The revision history of the engineering data and the hardware configuration informa-
tion are also stored in this database.
The AD Server manages the engineering data.
l Generation Manager
For SCS projects that are created with I/O list engineering, Generation Manager reflects the
information of the safety I/O lists, safety communication I/O lists, and I/O module configuration
and builds SCS projects.
l Dictionary View
If you select the RS original engineering method, the Dictionary View is used to set the pa-
rameters of FUs and FBs and define project variables. If you select the I/O list engineering
method, the variables that were defined by using AD Organizer and iDefine are read-only in
Dictionary View.
l Multi-Language Editor
Edit the POUs for the LBD, LD, and ST.
POUs that were defined by using iDefine are read-only in Multi-Language Editor.
SENG
Definition
Tag Name Builder AD Suite
Reflection
Import Definition
Alarm Processing Alarm Priority
Table Builder Builder
SCS
Communication
ENG HIS
Download
SCS Tag list Builder SCS Tag list
SENG
Modbus Address
Builder
Definition
SCS
Modbus
Safety Slave
Application Communication
Application Other System
(Modbus Master)
Map
Modbus devices Communication
Variables Application
defined virtually
SCADA
DNP3 Ethernet
Defined by DNP3 client
Communication Builder Defined by
IOM Definition Editor,
Key: DNP3 data type and index or I/O wiring view and
I/O Parameter Builder
FB DNP3 data
Instances
n Engineering tools
The following describes the tools that are used after you have created a ProSafe-RS applica-
tion:
l Integrity Analyzer
The Integrity Analyzer is used to analyze the safety of existing created application logics. It
detects unauthorized FB /FU as the safety function, and outputs results of analyzing on
screen or on the analysis report.
l Self-Documentation function
This is for printing user applications. The entire definitions of an SCS project or any parts can
be selected as a printed item.
l Import/Export function
Import or export functions can be used to import or export SCS project data. Therefore, these
data can be used for test functions or for reusing applications.
l SCS Information
This function is used to display and print SCS project usage conditions such as POUs used
within the SCS and the number of variables. This function can also be used to check the data-
base revisions in the SCS project, number of project I/O licenses and their usage. You need
to build an SCS project before using this function.
Message
Ready
n Title bar
The title bar displays project name, file name, etc.
n Menu bar
The menu bar contains the [Edit], [Tools] and other menus. The menu structure of the menu
bar differs depending on the builder; the menu bar used on most builders is as follows.
l File menu
TIP If there is no document window, only [Open], [Latest File] and [Exit SCS Constants Builder] are displayed.
l Edit menu
l View menu
l Tools menu
l Window menu
n Toolbar
The toolbar contains icons representing frequently used functions in the menu bar.
Standard
Display/Hide Data Menu Same as [Data Menu Area] of the [View] menu
l IOM download
This function downloads the execution data that was active in an input/output module to a
new input/output module after replacing it. The data of the input/output module (part of the
SCS database) saved in the master database on the SENG is downloaded.
This download can only be performed when replacing hardware of input/output modules.
SENG
SCS project
SCS database
TIP • Master Database Restoring Function is provided in order to copy the master database to the work data-
base in case a recovery is needed. Do not operate the master database folder/files directly by using
Windows explorer, or edit the master database.
• SCS projects are also registered in the ADMDB and managed by the AD Server.
l Offline download
The work database generated by building is downloaded to an SCS. The master database is
overwritten by the work database.
l IOM download
Only data in the master database related to input/output modules is downloaded to an SCS.
l Restart SCS
This is for restarting SCS.
SENG
Password
SCS Manager check(*1)
SCS status display Setup Tool
Application
definition Diagnostic
Online monitoring information operation
function
Windows
[Start] menu Password Message Cache Tool
check(*2)
SOE Viewer
SCS
*1: When the "Access Control and Operation History Management Package" is used, password checking
is not performed because user authentication check is done when SCS Manager is started.
*2: When the "Access Control and Operation History Management Package" is used, password checking
is not performed because user authentication check is done when the SCS Maintenance Support Tool is started.
Figure A5.1-1 Relationships among functions included in SCS Maintenance Support Tool
n Online monitoring
The online monitoring function displays the operating status of the application logic in SCS.
Using this function, the user can keep track of the values of variables as well as the condition
statuses on FBD and LD.
n SOE Viewer
SOE Viewer is a tool to display event information held by SCS. It also displays the diagnostic
information messages. The SOE Viewer is capable of displaying events and messages in
chronological order, which helps you analyze messages output from the SCS.
1. SENG power ON
window
8. SCS State Management Check the SCS status after removing the causes.
window
Engineer
Completed
n Step 7: Maintenance
The maintenance personnel removes the causes according to the operation procedure made
by the engineer.
Font
Height 16
Color
Text Color
Back
OK Cancel Apply
n General tab
Make settings related to the overall appearance of the window including font and text color in
the "General" tab.
l Font
The setting items related to font are as follows.
• Font name
This item is used to select a font name. The font specified here is used in all windows
related to SCS Maintenance Support Tool. The default font installed in SENG becomes
the initial font.
• Height
This item is used to select a font size. The font size specified here is used in all windows
related to SCS Maintenance Support Tool.
l Color
The setting items related to color are as follows.
• Text color
This item is used to select a text color. The text color specified here is used in all windows
related to SCS Maintenance Support Tool.
• Back
This item is used to select a text background color. The background color specified here
is used in all windows related to SCS Maintenance Support Tool.
Acknowledgement method
Individual Group
Deletion method
Individual Group
File: C:\RS-Projects\Guide\UserHelpTop.htm
Setup
OK Cancel Apply
Figure A5.3-2 Diagnostic Information Tab of SCS Maintenance Setup Dialog Box
l Method of acknowledgment
The setting items related to the method of acknowledgment are as follows.
• Individual
Select this option to acknowledge the diagnostic information messages individually. It is
recommended to use [Individual] during a normal operation.
• Group
l Method of deletion
The setting items related to the method of deletion are as follows.
• Individual
Select this option to delete the diagnostic information messages individually. It is recom-
mended to use [Individual] during a normal operation.
• Group
Select this option to delete all diagnostic information messages in a batch.
IMPORTANT
If you select [Group] as the acknowledgement/deletion method, all diagnostic information
messages displayed in the screen become the target of the acknowledging/deleting opera-
tion. So, you should not use this function during normal plant operation; use it only temporarily
when testing, etc.
n Terminology
This section describes virtualization and related terms.
Virtualization is a technology to make a single unit of physical hardware look like multiple logi-
cal units of hardware, or to make multiple units of physical hardware look like a single unit of
logical hardware. In this document, we mainly deal with the technique that makes it look like
there are multiple computers in the server.
• Virtualization software
Refers to the software that realizes virtualization.
• Virtualization host computer
Refers to a server on which virtualization software is installed and that is able to make it
look like there are multiple computers in it.
• Virtual machine
Virtualization can make it look like there are multiple computers on the virtualization host
computer, and these pseudo computers are referred to as virtual machines.
• Host OS
Refers to the OS operating as the foundation on the virtualization host computer.
• Guest OS
Refers to the OS running the virtual machines.
• Thin client
Refers to a client computer that contains minimum functions and performance and that is
used for user interface.
Operation of the virtual machines on the virtualization host computer is performed on the thin
client remotely connected via the network.
SEE
ALSO For more information about detailed functions of virtualization platform, refer to:
A., “Overview” in Virtualization Platform Setup (IM 30A05B20-01EN)
For more information about how to operate the virtualization host computer, refer to:
B., “Operating virtualization host computers” in Virtualization Platform Setup (IM 30A05B20-01EN)
For more information about how to set up a thin client, refer to:
C., “Setting up thin clients” in Virtualization Platform Setup (IM 30A05B20-01EN)
For more information about procedure to set up ProSafe-RS running on virtualization platform, refer to:
A2.2.2, “Setup Procedure for ProSafe-RS Running on a Virtual Machine on the Virtualization Platform” in
Installation Guide (IM 32P01C50-01EN)
For more information about virtualization platform IT security setting, refer to:
1., “Overview” in Virtualization Platform Security Guide (IM 30A05B30-01EN)
For more information about IT security setting for ProSafe-RS running on virtualization platform, refer to:
1., “Overview” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
FCS SCS
ProSafe-RS R4.04.00 and later software can run on the virtual machines of the virtualization
platform.
SEE
ALSO For more information about hardware on which the virtualization platform runs, and Yokogawa system prod-
ucts running on virtualization platform virtual machines, refer to:
IA system products virtualization platform (GS 30A05B10-01EN)
n Live migration
Live migration is a feature that enables you to move active virtual machines to another virtual-
ization host computer without stopping them. With this feature, you can apply security patches
to the host OS or replace the hardware of the virtualization host computer without shutting
down the virtual machines.
However, automatic live migration may not be suppressed sometimes. For example, if you
shutdown a host OS while a virtual machine is active in a virtualization host computer that
forms a part of an HA cluster, live migration occurs automatically.
n Failover
Failover is a function to restart the virtual machines of a virtualization host computer that
stops due to an error, on another virtualization host computer in an HA cluster. This function is
used to reduce the down time of a system when a virtualization host computer stops due to
an error.
Restoration by restarting the virtual machine by using failover runs in the same way as [OS
startup after unexpected shutdown].
Apart from the HA cluster failover that is explained in this section, there is another function
called replication failover.
l Failover conditions
Failover occurs in the following scenarios:
• When an active virtualization host computer stops due to an error.
• When communication is interrupted in both the management network and the HA-cluster
network on an HA cluster that consists of three or more virtualization host computers.
n Host OS
This section describes the software environment of the host OS.
l Operating system
The following host operating systems are supported:
• Windows Server 2016 Datacenter Edition Desktop Experience
l IT Security Tool
The IT Security Tool, which is used to configure IT security settings of the host OS, is provi-
ded in the software medium for the virtualization platform.
n Virtual machine
This section describes the software environment of the virtual machine.
l Operating system
The following operating system is supported for virtual machines:
• Windows Server 2016 Standard Edition
n Operating system
The thin clients that are supported in the virtualization platform environment uses the follow-
ing operating systems:
• Windows 10 IoT Enterprise 2015 LTSB or later (hereinafter referred to as Windows 10
IoT)
• Wyse ThinOS 8.4 or later (hereinafter referred to as Wyse ThinOS)
n IT Security Tool
The IT Security Tool, which is used to configure IT security settings in Windows 10 IoT, is pro-
vided in the software medium for the virtualization platform.
A6.3.3 License
You need a license to use the Vnet/IP interface package. After installing YOKOGAWA system
products, assign the license to the virtual machine.
The virtual Vnet/IP stations without licenses are the same as the Vnet/IP stations that are not
connected to the Vnet/IP network cable.
SEE
ALSO For more information about required OS license for virtualization host computer and thin client, refer to:
IA system products virtualization platform (GS 30A05B10-01EN)
n License
You need a license to use the Vnet/IP interface package. After installing YOKOGAWA system
products, assign the license to the virtual machine.
The virtual Vnet/IP stations without licenses are the same as the Vnet/IP stations that are not
connected to the Vnet/IP network cable.
n Security
You must control the administrative privileges of the virtual Vnet/IP station to ensure the se-
curity of the Vnet/IP communication.
l FAST/TOOLS integration
The virtualization platform does not support FAST/TOOLS integration. Also, wide area com-
munication and narrow band communication supported by FAST/TOOLS integration cannot
be used.
Table A6.4.2-2 Computers on which Dongle Gateway can be installed and where to insert the USB
dongle
Computers on which Dongle Where to insert the USB dongle Remarks
Gateway can be installed
Thin client Thin client Windows version
Physical SENG Physical SENG -
Virtualized SENG USB Device Server (*1) -
*1: Please contact YOKOGAWA for recommended products for USB Device Server.
SEE
ALSO For more information about Dongle Gateway IT security setting, refer to:
“■ The users for using iDefine in a virtualization environment” in 2.2.3, “User/Group Management” in
ProSafe-RS Security Guide (IM 32P01C70-01EN)
For more information about how to install Dongle Gateway, refer to:
Dongle Gateway Installation and User Guide (PR03076-MAN-983_01)
l License authentication
To use iDefine in a virtualization platform environment, authenticate the license via Dongle
Gateway.
IMPORTANT
• If the iDefine for the number of Dongle Gateway licenses granted to the USB dongle is
already connected to the Dongle Gateway at the same time, trying to connect another
iDefine will cause license authentication to fail.
• If communications between iDefine and Dongle Gateway are disconnected, such as if
there is a communication error or if the USB dongle is pulled out, update of the license
information will fail and the iDefine license will be invalidated. If communication between
iDefine and Dongle Gateway is restored within 5 minutes and license information can be
acquired, the iDefine license is re-activated and iDefine can be used. If the license infor-
mation cannot be acquired, Dongle Gateway releases the license and becomes available
from other iDefine.
SEE
ALSO For more information about how to authenticate iDefine license via Dongle Gateway, refer to:
Dongle Gateway Installation and User Guide (PR03076-MAN-983_01)
B. ProSafe-RS security
ProSafe-RS has the following security functions to prevent access to the system by unauthor-
ized users and devices, and unintended changes caused by operation mistakes made by
users.
• Security for the project database
You can configure the SENG function so that the user is required to enter a password
when changing the project data with SCS Manager. (Recommended)
• Security for access to SCS
You can limit access to SCS from the outside based on the SCS security level. The user
is required to enter a password when changing the SCS security level. (Mandatory)
• Security for the SCS Maintenance Support Tool
On SENG, you can limit writing to SCS with the SCS Maintenance Support Tool by setting
a password. (Recommended)
• Access control and operation history management
Access control and operation history management can be performed on projects that are
saved in the AD Server. You can also use the Access control and operation history man-
agement package.
• Countermeasures against threats to IT security
ProSafe-RS security threats include attacks via the network, direct attacks by executing
actions on an SENG, and analysis of important data carried out by stealing an SENG.
The security features are designed to take measures against these types of security
breaches.
This section provides an overview of the ProSafe-RS security function, and the main proce-
dures for setting passwords and implementing security relating to unauthorized access and
protection against unintended operations.
SENG SCS
Security Function
Security for
Verify password SCS project Project Database
Setting
information
AD Server SENG
User management
Access control Logon control
System Structure
Navigator Access control and operation history management
Operation history
Access control management
Safety I/O Editor
History
management
ModPack-based
change management SCS Access
Control
SCS
n IT security
This section describes the requirements for IT security.
For SENG, Windows OS is used as a platform. Therefore, it is necessary to prevent, detect,
and recover from computer viruses and attacks from the external through the network. For ex-
ample, there are countermeasure such as network access control using firewall and system
backup.
In the CENTUM Integration Structure, it is necessary to consider comprehensive IT security
including ProSafe-RS system and CENTUM system.
You can harden the security of the PC designated as a SENG terminal to enhance the
ProSafe-RS IT security (PC hardening). This section describes the details regarding PC hard-
ening and the setting guidelines.
l Modification management
This function manages the changes made to SCS projects. It has the following functions:
• Backup
SCS projects are registered and managed in AD Server.
• Version management
This function manages the history of changes made to SCS projects.
• Master database management
SENG always maintains the backup SCS project that keeps the same SCS database with
the one running on the SCS.
• Saving modification files
When you use the Access Control and Operation History Management Package, the
changes made to the project database downloaded to the SCS are saved.
l SOE Viewer
No password is set up for SOE Viewer because no writing operations to an SCS are per-
formed on SOE Viewer.
l RS generation
You can set the rights to run RS generation.
l History management
You can set the rights to set and delete labels.
Security
Password
Old: ***
New: ***
Read Only
OK Cancel Apply
Password
Old:
New:
Confirm New:
OK Cancel Apply
IMPORTANT
No password has been set after executing offline download and master database offline
download. Make sure to set passwords again.
TIP The access to SCS is controlled by SCS itself according to its security level. Operations on the SENG is not
be prohibited according to the SCS security level, however.
SEE
ALSO For more information about security level of SCS, refer to:
A2.3.2, “Security level of SCS” on page A2-15
IMPORTANT
No password has been set after executing offline download and master database offline
download. Make sure to set a password at this stage.
Current Level: 2
New Level: 1
Password: ****************
Level: 1
OK Cancel
4. Select the security level for which you set a password in [Level:].
It is necessary to set one password for changing to Level 1 and one for Level 0, respec-
tively.
5. Enter the current password in the [Old Password:] field.
6. Enter a new password in the [New Password:] field, and once again in the [Confirm New
Password:] field.
The passwords you have entered appear as a series of asterisks (*).
A password is a maximum 16 of single-byte alphanumeric characters and following sym-
bols including a space character. The password is case-sensitive.
! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ¥ ] ^ _ ` { | } ˜
You do not need to enter [Old Password:] if you have not set any password before, or if
you have just executed an offline download or a master database offline download.
7. Click the [OK] button.
The confirmation dialog box appears.
SCS Manager
OK Cancel
To change the security level, you need to enter the password. However, you don’t need to en-
ter a password when changing the security level from Level 1 to Level 2.
You cannot raise the security level from Level 0 to Level 2 from the Set SCS Security Level
dialog box. In SCS Simulator of SCS Test Functions, however, you can raise from Level 0 to
Level 2 on the Set SCS Security Level dialog box. This operation does not require a pass-
word.
CAUTION
To set the SCS security level back to Level 2 after changing to Level 0, you must restart the
SCS, execute offline download, or execute master database offline download. In particular, be
sure to execute offline download if you used break points in debugging of the application log-
ic.
These operations require stopping of the system. When you change the security level to Level
0, do so very carefully considering the consequences of the system stop.
Current Level: 2
New Level: 1
Password: ****************
4. Select the security level you want in [New Level:] and enter the password for the level
you want in [Password:] text box.
All characters you enter are displayed as asterisks (*).
5. Click the [OK] button.
The confirmation dialog box appears.
Is it OK to set to Level 1 ?
Domain : 01
Station : 24
OK Cancel
SCS Manager
Is it OK to set to Level 0 ?
WARNING: [Restart SCS] or [Offline Download] is mandatory
to switch back to Level 2 (normal operation) later.
This will turn all output channels OFF.
Domain : 01
Station : 24
OK Cancel
If the security level of SCS is changed, the message showing the result of change is dis-
played.
The error message is displayed if the security level could not be changed.
IMPORTANT
This dialog box is for confirmation only. Open the corresponding SCS project again and
change the security level using the Set SCS Security Level dialog box.
OK
Figure B3-8 Example of Confirmation dialog box (when closing by exiting SCS Manager)
Clicking the [OK] button to exit SCS Manager leaves the security level unchanged.
• When closing an SCS project by opening another SCS project
SCS Manager
OK Cancel
Figure B3-9 Example of Confirmation dialog box (when closing by opening another SCS project)
Click the [OK] button to close the currently opened SCS project without changing its se-
curity level, and then open another SCS project.
Click the [Cancel] button to keep the currently opened SCS project opened, and another
SCS project will not open.
IMPORTANT
The Node number setting tool and FieldMate Validator are included in the N-IO maintenance
tool.
n Disabled status
The disabled status of the maintenance port prohibits access from the maintenance port.
N-ESB bus /
Optical ESB bus
Maintenance NIU
port
Disabled status
n Enabled status
The enabled status of the maintenance port allows access from the maintenance port.
N-ESB bus /
Optical ESB bus
Maintenance NIU
port
Enabled status
(Changing to maintenance mode
enables access to N-IO I/O modules.)
F-SB bus : Route of access
SEE
ALSO For more information about how to enable/disable the maintenance port, refer to:
I4.5, “NIU maintenance port setting tool” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
n Online mode
In online mode, you can access the N-IO I/O modules from the N-ESB bus or the optical ESB
bus.
You cannot access the N-IO I/O modules from the maintenance port.
N-ESB bus /
Optical ESB bus
Maintenance NIU
port
Online mode
n Maintenance mode
In maintenance mode, you can access the N-IO I/O modules from the maintenance port.
You cannot access the N-IO I/O modules from the N-ESB bus or the optical ESB bus.
N-ESB bus /
Optical ESB bus
Maintenance NIU
port
Maintenance mode
IMPORTANT
When the node number setting tool is used as a N-IO maintenance tool, the unit will switch to
the maintenance mode when a node address is configured. After the node address is config-
ured, the unit will switch to the online mode.
TIP • Switching the maintenance mode of the dual-redundant N-ESB bus modules
Because the N-ESB bus modules are dual-redundant, when you change the operation mode on one
side, the operation mode of the other side will switch accordingly.
SEE
ALSO For more information about Node number Setting tool, refer to:
F2.1.1, “Using the Node Number Setting Tool” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about FieldMate Validator, refer to:
manual of FieldMate Validator
Online /
Enabled
(Setting at the time of the
shipment of NIU)
By performing one of the following procedures.
• Issue the switching command from the
Switching to the maintenance mode N-IO maintenance tool connecting to the
by issuing the switching command maintenance port. The access to NIU
from the N-IO maintenance tool • Remove the USB cable connecting to can be accepted
the maintenance port.
• Set the power supply of NIU to ON from OFF.
The access to
The access to N-IO via Maintenance /
N-IO via NIU
NIU cannot be accepted Enabled can be accepted
The following table shows the factory settings of the N-ESB bus modules (S2EN501) that are
installed in the NIU.
n Status display
The status of the NIU maintenance ports can be checked by using the following tools:
• SCS Status Overview window of SENG
• SCS Status Display view of HIS
• SCS Node Status Display dialog box of HIS
n Message
The SCS generates the following messages for the status and status change of the NIU main-
tenance port, and the status change of the NIU operation mode:
• A diagnostic information message that notices the status of the NIU maintenance port
• A safety control station status change message that notices the status change of the NIU
maintenance port
• A safety control station status change message that notices the status change of the NIU
operation mode
n IOM report
The status of the NIU and NIU maintenance port is displayed in the IOM report.
SENG
SCS engineering functions
SCS Maintenance Support Tool
Security functions
SCS Manager
Verification
TIP No security is set in order to use SOE Viewer as it only displays information.
1. Open the window related to SCS Maintenance Support Tool from SCS Manager or [Start]
menu of Windows.
When the window requiring a password is opened, the Input Maintenance Support Pass-
word dialog box appears.
Input Maintenance Support Password
Password: ********
OK Cancel
3. Enter the current password in the [Old Password:] field. Enter a new password in the
[New Password:] field, and once again in the [Confirm New Password:] field.
The passwords you have entered appear as a series of asterisks (*).
4. Click [OK].
The password is set.
IMPORTANT
If you fail to enter the correct password, SCS Maintenance Support Tool is started in the read-
only status.
1. Open the window related to SCS Maintenance Support Tool from SCS Manager or [Start]
menu of Windows.
When the window requiring a password is opened, the Input Maintenance Support Pass-
word dialog box appears.
If the current window is called from another window of SCS Maintenance Support Tool,
the Input Maintenance Support Password dialog box does not appear, because the se-
curity is inherited.
Password: ********
n User management
The package has a function that enables management of the users who work with SCS Man-
ager and the SCS Maintenance Support Tool. In AD Suite, you can set access rights to the
targets of operation for each user role. The user management function is used to register and
delete engineers and manage the passwords of engineers. It also keeps records of the opera-
tions that were performed by each user.
n Access control
The access control function enables you to check engineers who operate the SENG, restrict
login or operations on the SENG, and control authorization of engineering operations.
In AD Suite, you can define access rights to files and folders on the AD Server and various
functions for all users who perform engineering and maintenance of ProSafe-RS.
Appendix 1. Glossary
The following terminologies are used in the User’s Manual of this product.
Revision information
Title : ProSafe-RS User’s Guide
Manual No. : IM 32P01B10-01EN
Dec. 2019/6th Edition/R4.05 or later
Introduction Updated description of registered trademarks and trademarks
A1.1, A5, A5.1, Added description of Forced I/O Viewer function
A6.4.2, B1
A1.2 Updated software version descriptions in "● Software that can coexist with
ProSafe-RS," "■ CENTUM integration system," "■ FAST/TOOLS integration sys-
tem," “■ Use of iDefine,” “■ Use of PRM," "■ Use of Exaopc,” and "■ Use of
Exaquantum.”
Appendix 1 Added Forced I/O Viewer function, and stand-alone ProSafe-RS system in the
glossary.
Aug. 2018/5th Edition/R4.04
Introduction Updated description of registered trademarks of YOKOGAWA.
A1.1, A1.2 Added descriptions of Windows Server 2016.
A1.2 Updated descriptions of .NET Framework.
A1.2 Updated software version descriptions in "● Software that can coexist with
ProSafe-RS," "■ CENTUM integration system," "■ FAST/TOOLS integration sys-
tem," “■ Use of iDefine,” “■ Use of PRM," "■ Use of Exaopc,” and "■ Use of
Exaquantum.”
A6 Added new section on virtualization platform.
Oct. 2017/4th Edition/R4.03.10
A1.2 Changed version number and added version description in CENTUM integration
system, FAST/TOOLS integration system, use of iDefine, use of PRM, use of
Exaopc and use of Exaquantum.
A2, A2.3.1 Added Safety Subsystem communication related descriptions.
A2.3.1, A2.4.1 Added description about Fire and Gas communication module.
A3, A4, B1 Added Safety subsystem communication engineering related descriptions.
Appendix 1 Added Field network, Field wireless backbone network, Field wireless network,
Field wireless system, Fire and gas communication, %WB, %WW, %XB, %XW
and safety subsystem communication in the glossary.
May 2017/3rd Edition/R4.03
Introduction Deleted Windows Vista from "■ Trademark Acknowledgments."
A1.1, A1.2 Added descriptions of Windows 10 and deleted descriptions of Windows Vista and
Windows Server 2008.
A1.2 Changed software versions, descriptions of ProSafe-RS functions and CENTUM
release number, descriptions of coexistence of ProSafe-RS and CENTUM on the
same computer, descriptions of whether or not ProSafe and iDefine can coexist on
the same computer, and descriptions of versions.
Oct. 2016/2nd Edition/R4.02
Entire manual Changed the symbols that indicate warning and caution.
Introduction Updated descriptions in "■ Safety, Protection, and Modification of the Product," "■
Symbols," and "■ Trademark Acknowledgments." Added a new term in "■ Full
Names and Simplified Terms."
n For Questions and More Information Online Query: A query form is available on the fol-
lowing URL for online query. http://www.yokogawa.com/iss
n Written by Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN