Im32p01c50 01en

User's ProSafe-RS
Manual ProSafe-RS Lite
Installation Guide
IM 32P01C50-01EN
IM 32P01C50-01EN
7th Edition
i
Introduction
This manual describes the procedure for setting up ProSafe-RS.
When you integrate ProSafe-RS with FAST/TOOLS, replace "Vnet/IP" in the descriptions in
this manual with "Vnet/IP-Upstream."
This manual consists of the following parts:
• Part A Overview
This part provides an overview of ProSafe-RS setup.
• Part B: New Setup
This part describes the procedure for a new setup of ProSafe-RS.
• Part C Maintenance
This part describes the tasks to be done while a ProSafe-RS system is used.
• Part D Connection with Other Products
This part describes how to connect ProSafe-RS to other YOKOGAWA products and pro-
vides cautionary notes.
• Appendix
This section describes hardware settings and cautionary notes.
7th Edition : Feb. 2021 (YK) IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

All Rights Reserved. Copyright © 2015, Yokogawa Electric Corporation
ii
Safety Precautions for Use

n Safety, Protection, and Modification of the Product
• To protect the system controlled by the Product and the Product itself and to ensure safe
operation, please observe the safety precautions described in this Manual. Yokogawa
Electric Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observe
the safety precautions and instructions when operating the Product.
• If the Product is used in a manner not specified in the User's Manuals, the protection pro-
vided by the Product may be impaired.
• If any protection or safety circuit is required for the system controlled by the Product or for
the Product itself, please install it externally.
• Be sure to confirm the specifications and required settings of the devices that are used in
combination with the Product by referring to the instruction manual or other documents of
the devices.
• Use only spare parts that are approved by YOKOGAWA when replacing parts or consum-
ables of the Product.
• Do not use the Product and its accessories such as power cords on devices that are not
approved by YOKOGAWA. Do not use the Product and its accessories for any purpose
other than those intended by YOKOGAWA.
• Modification of the Product is strictly prohibited.
• The following symbols are used in the Product and User's Manuals to indicate the accom-
panying safety precautions:
Indicates that caution is required. This symbol for the Product indicates the possi-
bility of dangers such as electric shock on personnel and equipment, and also indi-
cates that the user must refer to the User’s Manuals for necessary actions. In the
User’s Manuals, this symbol is used together with a word “CAUTION” or “WARN-
ING” at the locations where precautions for avoiding dangers are described.
<French> Signale qu’il faut faire preuve de prudence. Ce symbole pour le produit
signale la possibilité d’un danger pour le personnel et l’équipement comme un
choc électrique, et signale également que l’utilisateur doit se référer au Manuel de
l’utilisateur afin de prendre les mesures nécessaires. Dans le Manuel de l’utilisa-
teur, ce symbole est utilisé conjointement avec la mention «CAUTION» ou
«WARNING» aux endroits où sont décrites les précautions pour éviter les
dangers.
Indicates that caution is required for hot surface. Note that the devices with this
symbol become hot. The risk of burn injury or some damages exists if the devices
are touched or contacted.
<French> Signale qu'il faut faire preuve de prudence avec la surface brûlante. Les
appareils sur lesquels est apposé ce symbole risquent de devenir brûlants. Tout
contact physique ou matériel avec ces appareils risque de provoquer des brûlures
ou des dommages.
Identifies a protective conductor terminal. Before using the Product, you must
ground the protective conductor terminal to avoid electric shock.
Identifies a functional grounding terminal. A terminal marked "FG" also has the
same function. This terminal is used for grounding other than protective grounding.
Before using the Product, you must ground this terminal.
Indicates an AC supply.
Indicates a DC supply.
IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

iii
Indicates that a component such as a power supply switch is turned ON.
Indicates that a component such as a power supply switch is turned OFF.
n Notes on Handling User's Manuals

• Hand over the User's Manuals to your end users so that they can keep the User's Man-
uals on hand for convenient reference.
• Thoroughly read and understand the information in the User's Manuals before using the
Product.
• For the avoidance of doubt, the purpose of the User's Manuals is not to warrant that the
Product is suitable for any particular purpose but to describe the functional details of the
Product.
• Contents of the User's Manuals are subject to change without notice.
• Every effort has been made to ensure the accuracy of contents in the User's Manuals.
However, should you have any questions or find any errors, contact us or your local dis-
tributor. The User's Manuals with unordered or missing pages will be replaced.
n Warning and Disclaimer

• Except as specified in the warranty terms, YOKOGAWA shall not provide any warranty for
the Product.
• YOKOGAWA shall not be liable for any indirect or consequential loss incurred by either
using or not being able to use the Product.
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.

iv
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.
Indicates precautions to avoid a danger that may lead to minor or

CAUTION moderate injury or property damage.
IMPORTANT Indicates important information required to understand operations or

functions.
Indicates additional information.
Indicates referenced content.

In online manuals, you can view the referenced content by clicking
the links that are in green text. However, this action does not apply
to the links that are in black text.
n Typographical Conventions
The following typographical conventions are used throughout the User's Manuals.
l Commonly Used Conventions throughout the User's Manuals

• Δ Mark
Indicates that a space must be entered between character strings.
Example:
.ALΔPIC010Δ-SC
• Character string enclosed by braces { }
Indicates character strings that may be omitted.
Example:
.PRΔTAG{Δ.sheet name}
l Conventions Used to Show Key or Button Operations

• Characters enclosed by brackets [ ]
When characters are enclosed by brackets in the description of a key or button operation,
it indicates a key on the keyboard, a button name in a window, or an item in a list box
displayed in a window.
Example:
To alter the function, press the [ESC] key.
l Conventions of a User-defined Folder

• User-defined folder name enclosed by parenthesis ( )
User definable path is written in a pair of parentheses.
Example:
(RS Project Folder)\SCS0101

v
If the RS Project Folder is C:\MYRSPJT, the above path becomes
C:\MYRSPJTSCS0101.
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 Explanation of Hardware and Software Behaviors in the User's

Manuals
In the User's Manuals, system behaviors are explained assuming that the latest versions of
YOKOGAWA software and hardware at the time of publication of the User's Manuals are in-
stalled.
If additional precise information about the safety of legacy versions of software or hardware is
required, a link to the corresponding explanation is provided. Please refer to the information
according to your system.
n Definitions of Node and Module Terms

In the User's Manuals, nodes and modules are referred to by using collective terms, another
terms, or abbreviations based on the following definitions:
• Definitions of nodes
• Node: A node is a collective term for an FIO node and an N-IO node.
• FIO node: This is a collective term for a safety control unit, a safety node unit, and a
unit for optical ESB bus repeater module.
• CPU node: This is another term for a safety control unit. The abbreviation of safety
control unit is SCU.
• I/O node: This is another term for a safety node unit. The abbreviation of safety node
unit is SNU.
• N-IO node: This is a collective term for a node interface unit and an N-IO I/O unit.
The abbreviation of node interface unit is NIU.
• Definitions of modules
• I/O module: This is a collective term for an FIO I/O module and an N-IO I/O module.
• FIO I/O module: This is a collective term for an analog I/O module and a digital I/O
module for FIO, and a communication module.
• N-IO I/O module: This is a collective term for the modules that can be mounted on an
N-IO I/O unit.
• AIO/DIO module: This is a collective term for an analog I/O module, a digital I/O mod-
ule, and a universal type I/O module.
• Analog I/O module: This is a collective term for an analog input module and an ana-
log output module.
• Digital I/O module: This is a collective term for a digital input module and a digital out-
put module.
• Universal type I/O module: This is a collective term for the I/O modules for which the
channel signal category can be changed by software.

vi
• Input module: This is a collective term for an analog input module, digital input mod-
ule, and a universal type I/O module with defined input channels.
• Output module: This is a collective term for an analog output module, digital output
module, and a universal type I/O module with defined output channels.
• Communication module: This is a collective term for a serial communication module,
an Ethernet communication module, and a fire and gas communication module.
n Full Names and Simplified Terms

In the User’s Manuals, simplified terms listed in the following table are used.
Table Info-1 Full Names and Simplified Terms

Full Name Simplified Term
Automation Design Suite AD Suite
Automation Design Organizer AD Organizer
Automation Design Server AD Server
Automation Design project AD project
Automation Design Master Database ADMDB
Automation Design Suite Administration Tool ADS Administration
Tool
iDefine for ProSafe-RS iDefine
Modification Package ModPack
SCSV1-S SCSV1
(SCS supporting the SSC10S/SSC10D safety control units)
SCSP1-S SCSP1
SCSP2-S SCSP2
SCSP3-S SCSP3
(SCS supporting the S2SC70S/S2SC70D safety control units)
SCSL2-S SCSL2
(SCS supporting the L1SC70S/L1SC70D safety control units)
SCSU1-S SCSU1

vii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the software medium of the
Software Product shall remain with YOKOGAWA.
You are allowed to print the required pages of the online manuals for the purposes of using or
operating the Product; however, reprinting or reproducing the entire document is strictly pro-
hibited by the Copyright Law.
Except as stated above, no part of the online manuals may be reproduced, transferred, sold,
or distributed to a third party in any manner (either in electronic or written form including, with-
out limitation, in the forms of paper documents, electronic media, and transmission via the
network). Nor it may be registered or recorded in the media such as films without permission.
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.

TocA-1
Installation Guide
IM 32P01C50-01EN 7th Edition
CONTENTS
PART-A Overview...........................................................A-1
A1. How to Read This Document............................................................ A1-1
A2. Overview of Setup Tasks...................................................................A2-1
A2.1 Before You Set Up......................................................................................A2-2
A2.2 Procedures for New Setup........................................................................ A2-3
A2.2.1 Setup Procedure for a ProSafe-RS System.................................A2-4
A2.2.2 Setup Procedure for ProSafe-RS Running on a Virtual Machine on
the Virtualization Platform............................................................ A2-7
A2.2.3 Setup Procedure for SENG........................................................A2-10
A2.2.4 Setup Procedure for a Computer Installed with Only AD Server.........
................................................................................................... A2-13
A2.2.5 Setup Procedure for a File Server............................................. A2-14
A2.2.6 Setup Procedure for a Computer Dedicated to License Management
................................................................................................... A2-15
A2.3 Explanation for Maintenance.................................................................. A2-16

TocB-1
Installation Guide
CONTENTS
PART-B New Setup........................................................ B-1
B1. Preparing for the Setup..................................................................... B1-1
B1.1 Items to be Determined Before the Setup................................................B1-2
B1.2 Precautions for Setup................................................................................B1-4
B1.3 Precautions for Setting Up ProSafe-RS on a Virtual Machine on the
Virtualization Platform............................................................................... B1-6
B2. Setting Up the Windows Domain Environment...............................B2-1
B2.1 Overview of Setting Up the Domain Environment.................................. B2-2
B2.2 Configuring the domain controller........................................................... B2-5
B2.3 Configuring Security Settings for the Domain Controller......................B2-6
B2.4 Creating Domain Users........................................................................... B2-13
B2.5 Adding Computers to the Domain..........................................................B2-17
B2.6 Setting Up Redundant Domain Controllers........................................... B2-19
B2.7 Setting Up Time Synchronization in Windows Domain Environment...........
................................................................................................................... B2-20
B2.7.1 Implementing Time Synchronization in a System Consisting of Only
ProSafe-RS................................................................................B2-21
B2.7.2 Implementing Time Synchronization When Integrated with CENTUM
................................................................................................... B2-24
B3. Setup of an SENG or a Computer Installed with Only AD Server.........
............................................................................................................. B3-1
B3.1 Setting Up the Hardware........................................................................... B3-2
B3.2 Setting Up Windows.................................................................................. B3-7
B3.2.1 Setting of Common Windows OS Items.......................................B3-8
B3.2.2 Setting of Items Specific to Windows 10....................................B3-10
B3.2.3 Setting of Items Specific to Windows Server 2016.................... B3-14
B3.3 Configuring Network Settings................................................................ B3-18
B3.3.1 Installing the Control Bus Driver................................................ B3-19
B3.3.2 Installing the Vnet/IP Open Communication Driver....................B3-21
B3.3.3 Installing the Vnet/IP Interface Package on a Virtual Machine............
................................................................................................... B3-23
B3.3.4 Configuring Windows Network Settings.....................................B3-27
B3.4 Notes on Using a Virtual Machine.......................................................... B3-38
B3.5 Installing the ProSafe-RS Software........................................................ B3-40

TocB-2
B3.6 Configuring IT Security Settings............................................................ B3-44
B3.6.1 Running the IT Security Tool......................................................B3-45
B3.6.2 Precautions for Coexistence with Other Product....................... B3-50
B3.6.3 Running Domain Link Management Tool................................... B3-51
B3.7 Distributing and Accepting Licenses.....................................................B3-54
B3.8 Creating User Accounts.......................................................................... B3-55
B3.8.1 When the Standard Model with Standalone Management Security
Settings are Applied...................................................................B3-56
B3.8.2 When the Legacy Model of Security Settings are Applied......... B3-57
B3.9 Configuring Windows Environment Settings for Each User............... B3-58
B3.9.1 Setting of items common to Windows 10 and Windows Server 2016.
................................................................................................... B3-59
B3.9.2 Setting of Items Specific to Windows 10....................................B3-63
B3.10 Configuring the Uninterruptible Power Supply (UPS) Service............ B3-65
B4. Configuring the Functions Specific to SENG..................................B4-1
B4.1 Setting the Manual Browsing Environment.............................................B4-2
B4.2 Settings of Project Database Folder........................................................ B4-3
B4.3 Settings for Message Cache Tool.............................................................B4-4
B4.4 Settings Required to Use the Forced I/O Viewer Function.................... B4-5
B4.5 Settings Required for OPC Communication............................................B4-6
B4.6 Setup when Using the Access Control and Operation History
Management Package................................................................................B4-8
B4.6.1 Setup Procedure when Using Access Control and Operation History
Management Functions............................................................. B4-10
B4.6.2 Security Settings for the Operation History Database................B4-11
B5. Setting Up a File Server.....................................................................B5-1
B5.1 Setting Up a Computer that Serves Only as a File Server..................... B5-2
B5.2 Setting Up the File Server Function on an SENG or a Computer Installed
with Only AD Server.................................................................................B5-12
B5.3 Setting Up the Computer that Serves as Both File Server and License
Management Station................................................................................ B5-14
B6. Setting Up the Computer Dedicated to License Management..............
............................................................................................................. B6-1
B7. Configuring the Hardware of SCS and Devices for Connection
between Domains.............................................................................. B7-1
B8. Installing the Functions that Operate with CENTUM VP Licenses.......
............................................................................................................. B8-1

TocC-1
Installation Guide
CONTENTS
PART-C Maintenance.....................................................C-1
C1. Adding Licenses and Changing License Assignments................. C1-1
C1.1 Adding a License....................................................................................... C1-2
C1.2 Changing License Assignments...............................................................C1-3
C2. Setting Up the Windows Domain Environment Later.....................C2-1
C3. Backing Up the System..................................................................... C3-1
C3.1 Backing Up the Entire Windows............................................................... C3-2
C3.2 Backing Up the ProSafe-RS Engineering Data........................................C3-3
C4. Upgrading the ProSafe-RS Software................................................C4-1
C4.1 Installation for Upgrading......................................................................... C4-2
C4.1.1 Upgrading the Version of ProSafe-RS Software..........................C4-4
C4.1.2 Upgrading the Revision of ProSafe-RS Software........................ C4-8
C4.2 Settings after Upgrading ProSafe-RS Software.................................... C4-12
C4.2.1 Updating the engineering data after an upgrade....................... C4-13
C4.2.2 Upgrading an SCS project......................................................... C4-16
C4.2.3 Cautionary notes for upgrading to R4.06...................................C4-17
C4.2.4 Procedures for using new functions...........................................C4-20
C4.3 Upgrading the Computer Dedicated to License Management.............C4-24
C5. Uninstalling the ProSafe-RS Software............................................. C5-1
C5.1 Uninstallation on SENG.............................................................................C5-2
C5.1.1 Uninstalling the ProSafe-RS Software.........................................C5-3
C5.1.2 Uninstalling the Network Drivers..................................................C5-5
C5.2 Uninstallation on the computer Dedicated to License Management............
................................................................................................................... C5-10
C6. Reinstalling the ProSafe-RS Software............................................. C6-1
C6.1 When the Computer Used is the Same.................................................... C6-2
C6.2 When the Computer Used is Not the Same............................................. C6-6
C7. Troubleshooting.................................................................................C7-1
C7.1 Windows Related Troubleshooting.......................................................... C7-2
C7.2 Troubleshooting Related to Network....................................................... C7-3
C7.2.1 Precaution on Network Cable Connection...................................C7-4
C7.2.2 Problems Related to Installation and Deletion of Drivers............ C7-5

TocD-1
Installation Guide
CONTENTS
PART-D Connection with Other Products................... D-1
D1. Connecting YOKOGAWA products.................................................. D1-1
D1.1 CENTUM VP and ProSafe-RS....................................................................D1-3
D1.1.1 CENTUM VP Standard Operation and Monitoring Function and
ProSafe-RS Safety System Engineering and Maintenance Function..
.....................................................................................................D1-4
ProSafe-RS SOE Viewer Package.............................................. D1-6
D1.1.3 CENTUM VP SOE Viewer Package and ProSafe-RS Safety System
Engineering and Maintenance Function...................................... D1-7
ProSafe-RS SOE OPC Interface Package.................................. D1-8
ProSafe-RS Forced I/O Viewer Package...................................D1-12
D1.1.6 CENTUM VP System Builder Function and ProSafe-RS CENTUM
VP Integration Package............................................................. D1-13
D1.1.7 CENTUM VP System Builder Function and ProSafe-RS Safety
System Engineering and Maintenance Function....................... D1-14
D1.1.8 CENTUM VP Engineering Server Function and ProSafe-RS Safety
System Engineering and Maintenance Function....................... D1-15
D1.1.9 CENTUM VP System Builder Function and ProSafe-RS Engineering
Server Function......................................................................... D1-16
D1.2 ProSafe-RS and iDefine........................................................................... D1-17
D1.2.1 ProSafe-RS Safety System Engineering and Maintenance Function
and iDefine for ProSafe-RS....................................................... D1-18
D1.2.2 ProSafe-RS functions other than Safety System Engineering and
Maintenance Function and iDefine for ProSafe-RS...................D1-20
D1.3 ProSafe-RS and PRM............................................................................... D1-22
D1.3.1 ProSafe-RS SOE OPC Interface Package and PRM Server..............
...................................................................................................D1-23
D1.3.2 PRM Client and Forced I/O Viewer Package.............................D1-25
D1.4 ProSafe-RS and Exaquantum................................................................. D1-26
D1.4.1 ProSafe-RS SOE OPC Interface Package and Exaquantum PIMS
Server........................................................................................ D1-27

TocApp.-1
Installation Guide
CONTENTS
Appendix
Appendix 1. Setting Switches............................................................. App.1-1
Appendix 2. Procedure for Erasing VI702 Internal Settings.............App.2-1
Appendix 3. Vnet/IP Interface Management Tool.............................. App.3-1
Appendix 4. Antistatic Precautions When Handling Hardware.....................
.......................................................................................... App.4-1
Appendix 5. Customization at Installation of Windows 10............... App.5-1
Appendix 6. Compatibility between Revisions and Cautionary Notes for
Upgrading........................................................................ App.6-1
Appendix 6.1 Cautionary Notes for Upgrading to R4.01.................................App.6-2
Appendix 6.2 Cautionary Notes for Upgrading to R4.02.................................App.6-4
Appendix 6.3 Cautionary Notes for Upgrading to R4.03...............................App.6-10
Appendix 6.4 Cautionary Notes for a Revision Upgrade to R4.03.10.......... App.6-13
Appendix 6.5 Cautionary Notes for Revision Upgrade to R4.04.................. App.6-15
Appendix 6.6 Cautionary Notes for Revision Upgrade to R4.05.................. App.6-17

<A. Overview> A-1
A. Overview
This section explains how to read this document, types of ProSafe-RS setup tasks and their
workflows.

<A1. How to Read This Document> A1-1
A1. How to Read This Document

This document explains the setup procedures for the ProSafe-RS software. This document
does not touch upon installation procedures of Windows OS, related service packs, and Mi-
crosoft security patches. Also, this document does not touch upon the procedure for installing
iDefine and how to configure the security settings on the computer on which iDefine is to be
installed.
To use the software packages installed on an SENG, licenses must be distributed to and acti-
vated on the SENG by using a program called License Manager. Procedures for the tasks
performed using License Manager are described in the License Management IM. You are gui-
ded to refer to the License Management IM as necessary in the explanation of setup proce-
dures.
You are also guided to refer to the Security Guide IM for information about functions that rein-
force security of the system.
SEE
ALSO For more information about the procedure for installing the Windows operating systems, related service packs
and the Microsoft security patches, refer to:
the information provided by Microsoft
For more information about Microsoft security patches, refer to:
Microsoft Security Update Policy (TI 33Y01B30-02E)
For more information about the procedure for distributing and activating the licenses on the stations, refer to:
1., “Overview of license management” in License Management Guide (IM 32P01C60-01EN)
For more information about system security, refer to:
1., “Overview” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
For more information about the procedure for installing iDefine, refer to:
iDefine Installation Guide (PR03076-MAN-991_01)
For more information about how to configure the security settings on the computer on which iDefine is to be
installed, refer to:
iDefine Security Manual (PR03076-MAN-981_01)
n Structure of This Document

This document consists of the following parts:
• Part A Overview
This part describes how to read this document, various types of ProSafe-RS setup tasks
along with their workflows are explained.
• Part B New Setup
This part explains the procedures for setting up each station.
• Part C Maintenance
This part describes maintenance tasks that are required after the stations have been set
up and went into operation.
• Part D Connection with Other Products
This part describes the required settings when connecting ProSafe-RS with other
YOKOGAWA products, such as CENTUM VP, PRM, and Exaquantum.

<A2. Overview of Setup Tasks> A2-1
A2. Overview of Setup Tasks

This section describes the workflows of setup tasks and provides the information you should
understand before you set up individual stations.
SEE
ALSO For more information about the operating environment of ProSafe-RS, refer to:
A1., “Requirements” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

<A2.1 Before You Set Up> A2-2
A2.1 Before You Set Up

This section describes the relationship between installation and licensing of ProSafe-RS soft-
ware.
n Installation and Licensing of Software Packages

In order to use ProSafe-RS software packages, it is necessary to install the ProSafe-RS soft-
ware on a computer and then grant licenses to the computer to enable the use of the software
packages.
The tasks of installing the software packages on each computer are performed using a pro-
gram called an installer. The tasks of giving licenses are executed using software called Li-
cense Manager. License Manager is automatically installed when the ProSafe-RS software is
installed on a computer.
Among computers installed with License Manager, the computer that is given the role of man-
aging licenses of each computer in the system is called the license management station. The
license management station distributes licenses to each computer on which the software
packages are installed. On a computer to which licenses have been distributed, the software
packages can be made available for use by accepting the distributed licenses.
TIP • It is possible to install only License Manager on a computer and use it as the computer dedicated to li-
cense management.
• License management for iDefine is based on a hardware key. It is not controlled by License Manager.
ProSafe-RS
License Medium
Software Medium
Install
Distribute licenses
License Management Station SENG
Figure A2.1-1 License Distribution
SEE
ALSO For more information about the details of licenses, refer to:
For more information about license management for iDefine, refer to:
License User Guide (PR03076-MAN-971_02)

<A2.2 Procedures for New Setup> A2-3
A2.2 Procedures for New Setup

This section describes the overall procedures for setting up a ProSafe-RS system and for set-
ting up each type of station or computer using flowcharts. As ProSafe-RS system setup pro-
cedures, it also describes the procedure for setting up a ProSafe-RS system that runs on a
virtual machine on the virtualization platform.
The procedures for the following types of stations and computers are described.
• Safety engineering PC (SENG)
• Computer installed with only Automation Design Server (AD Server)
• File server
• Computer dedicated to license management
A computer installed with only AD Server, file server, and computer dedicated to license man-
agement should be provided in the system as necessary.
SEE
ALSO For more information about the virtualization platform, refer to:
A., “Overview” in Virtualization Platform Setup (IM 30A05B20-01EN)

A2.2.1 Setup Procedure for a ProSafe-RS System

The following figure shows the overall procedure for setting up a ProSafe-RS system.
Start
Prepare for setup
Build the system in a domain Yes

environment? (*1)
Set up Windows domain environment (*2)
No
Set up SENG
Set up a computer installed

with only AD Server
Set up stations (*3)
Set up a file server
Set up the computer dedicated

to license management
Preparation before starting

the engineering
Set up hardware
(SCS and devices for connection
between domains)
The system is built in Yes

a domain environment?
Synchronize the time of stations
No
End
*1: You may set up the domain environment at a later stage.

*2: If linked domain management is selected for the user management type of IT security settings,
do not add the client computer to the domain before you set up the station.
*3: Start by setting up the station that is to be used as the license management station.
Figure A2.2.1-1 Setup Procedure for a ProSafe-RS System
You can jump to the explanation of each task that appears in the flowchart from the reference
link that is provided in the following subsections.
n Prepare for Setup

Determine the required items such as station number for setting up a ProSafe-RS system.
SEE
ALSO For more information about the items that must be determined before setting up a ProSafe-RS system, refer
to:
B1., “Preparing for the Setup” on page B1-1

n Set Up the Windows Domain Environment

When using ProSafe-RS in a Windows domain environment, set up the Windows domain en-
vironment. You may also set up the Windows domain environment at a later stage.
SEE
ALSO For more information about setting up a Windows domain environment, refer to:
B2., “Setting Up the Windows Domain Environment” on page B2-1
n Set Up Each Station

Set up SENG, file server, and other stations to be used in the ProSafe-RS system.
In a ProSafe-RS system, you must first set up the license management station, which is used
to grant licenses for software packages. The license management station can be set up on an
SENG or a computer dedicated to license management.
Software packages installed on other stations become available for use once the stations ac-
cept the licenses distributed from the license management station.
SEE
ALSO For more information about the procedure for setting up an SENG, refer to:
A2.2.3, “Setup Procedure for SENG” on page A2-10
For more information about the procedure for setting up a computer installed with only AD Server, refer to:
A2.2.4, “Setup Procedure for a Computer Installed with Only AD Server” on page A2-13
For more information about the procedure for setting up a file server, refer to:
A2.2.5, “Setup Procedure for a File Server” on page A2-14
For more information about the procedure for setting up a computer dedicated to license management, refer
to:
A2.2.6, “Setup Procedure for a Computer Dedicated to License Management” on page A2-15
n Preparation for starting engineering

The following tasks are required as the preparation for starting engineering.
• Creating an Automation Design project (AD project)
• Creating an RS project
• Registering the RS project in the AD project
SEE
ALSO For more information about preparation for starting engineering, refer to:
C1., “AD Server administration functions” in Engineer's Reference Manual (IM 32P04B10-01EN)
n Set Up the Hardware of SCS and Devices Used for Connection

between Domains
Set up the hardware of SCS and devices used for connection between domains.
SEE
ALSO For more information about setting up the hardware of SCS and devices for connection between domains,
refer to:
B7., “Configuring the Hardware of SCS and Devices for Connection between Domains” on page B7-1

n Set Up Time Synchronization in Windows Domain Environment

When using ProSafe-RS in a Windows domain environment, synchronize the time on the do-
main controller with the time on computers used in the ProSafe-RS system.
SEE
ALSO For more information about setting up time synchronization in a Windows domain environment, refer to:
B2.7, “Setting Up Time Synchronization in Windows Domain Environment” on page B2-20

A2.2.2 Setup Procedure for ProSafe-RS Running on a

Virtual Machine on the Virtualization Platform
The following figure shows the overall procedure for setting up a ProSafe-RS system running
on a virtual machine on the virtualization platform.
Start
Set up
the virtualization platform (*1)
Prepare for setting up stations

on the virtual machines
Build the system in a domain Yes

environment? (*2)
Set up Windows domain environment (*3)
No
Set up SENG (*5)
Set up a computer installed

with only AD Server
Set up stations (*4)
Set up a file server
Set up the computer dedicated

to license management
Preparation before starting
the engineering
Set up hardware
(SCS and devices for connection
between domains)
The system is built in Yes

a domain environment?
No
End : Tasks not described in this manual
*1: Prepare a computer for virtualization host, and install the virtualization platform.
*2: You may set up the domain environment at a later stage.
*3: If linked domain management is selected for the user management type of IT security settings,
do not add the client computer to the domain before you set up the station.
*4: Start by setting up the station that is to be used as the license management station.
*5: You do not need to set up a Vnet/IP interface card. Install the Vnet/IP Interface Package.
Figure A2.2.2-1 Setup Procedure for a ProSafe-RS System Running on the Virtualization Platform

n Setup for a Virtualization Platform

Before setting up ProSafe-RS, prepare the virtualization host computer and set up the virtuali-
zation platform.
SEE
ALSO For more information about the setup procedure for a virtualization platform, refer to:
B., “Working with virtualization host computer” in Virtualization Platform Setup (IM 30A05B20-01EN)
n Preparing to Set Up Stations that Run on Virtual Machines

Decide on the required information, such as station numbers, for setting up a ProSafe-RS
system.
When installing software on a virtual machine, you must create an ISO format file of the con-
tents of the software medium to be installed and mount it.
SEE
ALSO For more information about the items that must be determined before setting up a ProSafe-RS system, refer
to:
B1., “Preparing for the Setup” on page B1-1
For more information about the procedure and precautions when setting up ProSafe-RS that runs on the vir-
tualization platform, refer to:
B1.3, “Precautions for Setting Up ProSafe-RS on a Virtual Machine on the Virtualization Platform” on
page B1-6
n Set Up the Windows Domain Environment

You can use a computer in the existing physical environment as the domain controller, or you
can build the domain controller on the virtual machine.
You may also set up the Windows domain environment at a later stage.
SEE
ALSO For more information about the procedure for setting up a domain controller on a physical computer, refer to:
B2., “Setting Up the Windows Domain Environment” on page B2-1
For more information about the domain controller on the virtualization platform, refer to:
• “■ Domain controller” in A1.3, “Other devices” in Virtualization Platform Setup (IM 30A05B20-01EN)
• “■ Domain controller” in A3.3, “Other devices” in Virtualization Platform Setup (IM 30A05B20-01EN)
n Set Up Each Station

Set up SENG, file server, and other stations to be used in the ProSafe-RS system.
In a ProSafe-RS system, you must first set up the license management station, which is used
to grant licenses for software packages. The license management station can be set up on an
SENG or a computer dedicated to license management.
Software packages installed on other stations become available for use once the stations ac-
cept the licenses distributed from the license management station.
You can use a computer in the existing physical environment as the license management sta-
tion, or you can build the license management station on the virtual machine.

SEE
ALSO For more information about the procedure for setting up an SENG, refer to:
A2.2.3, “Setup Procedure for SENG” on page A2-10
For more information about the procedure for setting up a computer installed with only AD Server, refer to:
A2.2.4, “Setup Procedure for a Computer Installed with Only AD Server” on page A2-13
For more information about the procedure for setting up a file server, refer to:
A2.2.5, “Setup Procedure for a File Server” on page A2-14
For more information about the procedure for setting up a computer dedicated to license management, refer
to:
A2.2.6, “Setup Procedure for a Computer Dedicated to License Management” on page A2-15
n Preparation for Starting Engineering

The following tasks are required as the preparation for starting engineering.
• Creating an Automation Design project (AD project)
• Creating an RS project
• Registering the RS project in the AD project
SEE
ALSO For more information about preparation for starting engineering, refer to:
C1., “AD Server administration functions” in Engineer's Reference Manual (IM 32P04B10-01EN)
n Set Up the Hardware of SCS and Devices Used for Connection

between Domains
Set up the hardware of SCS and devices used for connection between domains.
SEE
ALSO For more information about setting up the hardware of SCS and devices for connection between domains,
refer to:
B7., “Configuring the Hardware of SCS and Devices for Connection between Domains” on page B7-1
n Set Up Time Synchronization in a Windows Domain Environment

When using ProSafe-RS in a Windows domain environment, synchronize the time on the do-
main controller with the time on computers used in the ProSafe-RS system.
On the virtualization platform, you must synchronize the time of the entire virtualization plat-
form using the SNTP server.
Do not use the host OS or virtual machine of the virtualization host computer as the top level
SNTP server for time synchronization. Also, do not use the domain controller as the SNTP
server.
SEE
ALSO For more information about setting up time synchronization in a Windows domain environment, refer to:
For more information about the virtualization platform time synchronization, refer to:
“■ SNTP server” in A1.3, “Other devices” in Virtualization Platform Setup (IM 30A05B20-01EN)

A2.2.3 Setup Procedure for SENG

The following figure shows the setup procedure for SENG.
Start
Set up the hardware
Set up Windows
Set up the network
Install ProSafe-RS software
Install other YOKOGAWA Yes

products?
Install software of other
No YOKOGAWA products (*1)
Configure IT security settings
Distribute and accept licenses
Create user accounts
Set up Windows environment

for each user
Set up the UPS
Configure function-specific
settings
Set up for connection with

other systems
End
*1: You may install other products later. If you install later, you need to configure IT security settings again.
Figure A2.2.3-1 Setup Procedure for SENG
n Set Up the Hardware

Set up the Vnet/IP interface card to be installed in the SENG.
In the case of SENG that runs on a virtual machine, there is no interface card setting because
it does not use the Vnet/IP interface card.

SEE
ALSO For more information about setting up the hardware of SENG, refer to:
B3.1, “Setting Up the Hardware” on page B3-2
n Set Up Windows
Configure Windows settings on the computer.
SEE
ALSO For more information about setting up Windows, refer to:
B3.2, “Setting Up Windows” on page B3-7
n Set Up the Network

Configure the network settings.
In the case of SENG that runs on a virtual machine, after installing the Vnet/IP Interface Pack-
age, you need to configure the network settings.
SEE
ALSO For more information about configuring network settings, refer to:
B3.3, “Configuring Network Settings” on page B3-18
n Install the ProSafe-RS Software

Install the ProSafe-RS software.
SEE
ALSO For more information about installing the ProSafe-RS software, refer to:
B3.5, “Installing the ProSafe-RS Software” on page B3-40
n Configure IT Security Settings

Configure IT security settings.
SEE
ALSO For more information about configuring IT security settings, refer to:
B3.6, “Configuring IT Security Settings” on page B3-44
n Distribute and Accept Licenses

Distribute licenses to the SENG from the license management station, and accept the licen-
ses on the SENG.
SEE
ALSO For more information about distributing and accepting licenses, refer to:
B3.7, “Distributing and Accepting Licenses” on page B3-54
n Create User Accounts

Create user accounts.
SEE
ALSO For more information about creating user accounts, refer to:
B3.8, “Creating User Accounts” on page B3-55

n Configure Windows Environment Settings for Each User

Configure Windows environment settings for each user.
SEE
ALSO For more information about configuring Windows environment settings for each user, refer to:
B3.9, “Configuring Windows Environment Settings for Each User” on page B3-58
n Set Up the Uninterruptible Power Source (UPS) Service

If necessary, set up the uninterruptible power source (UPS) service.
SEE
ALSO For more information about configuring the UPS service, refer to:
B3.10, “Configuring the Uninterruptible Power Supply (UPS) Service” on page B3-65
n Configure Function-Specific Settings

Configure the settings specific to certain functions of the SENG.
SEE
ALSO For more information about configuring the settings specific to each function of SENG, refer to:
B4., “Configuring the Functions Specific to SENG” on page B4-1
n Set Up for Connection with Other Systems

As necessary, set up for connection with other YOKOGAWA products.
SEE
ALSO For more information about the settings required to connect with other YOKOGAWA products, refer to:
D1., “Connecting YOKOGAWA products” on page D1-1

A2.2.4 Setup Procedure for a Computer Installed with Only

AD Server
The following figure shows the setup procedure for a computer installed with only AD server.
Start
Set up Windows
Install ProSafe-RS software

products?
Install software of other
No YOKOGAWA products (*1)

for each user
Set up the UPS
End
Figure A2.2.4-1 Setup Procedure for a Computer Installed with Only AD Server
SEE
For more information about installing the ProSafe-RS software, refer to:
For more information about configuring IT security settings, refer to:
For more information about distributing and accepting licenses, refer to:
For more information about creating user accounts, refer to:
For more information about configuring Windows environment settings for each user, refer to:
For more information about configuring the UPS service, refer to:

A2.2.5 Setup Procedure for a File Server

You can provide a file server in the system if centralized management is required for project
databases. The following figure shows the setup procedure for a file server.
TIP This flowchart illustrates the procedure for setting up a computer that serves only as a file server.
Start
Prepare to configure IT security

settings on the file server
Create and set up shared folders
Save the IT security settings

on the file server
Configure the IT security settings

on the file server
Create accounts on the file server

for users who access project data
Create the project folder

on the file server
End
Figure A2.2.5-1 Setup Procedure for a File Server
SEE
ALSO For more information about setting up a computer that serves only as a file server, refer to:
B5.1, “Setting Up a Computer that Serves Only as a File Server” on page B5-2
For more information about the procedure to set up a computer as both a file server and a license manage-
ment station, refer to:
B5.3, “Setting Up the Computer that Serves as Both File Server and License Management Station” on
page B5-14
For more information about setting up the file server function on SENG, refer to:
B5.2, “Setting Up the File Server Function on an SENG or a Computer Installed with Only AD Server” on
page B5-12

A2.2.6 Setup Procedure for a Computer Dedicated to

License Management
You can provide a computer dedicated to license management according to the scale and op-
eration policy of the system. The following figure shows the setup procedure for a computer
dedicated to license management.
Start
Set up Windows
Install the license management

software

products?
Install the license management
No software of other
YOKOGAWA products (*1)

for each user
End
Figure A2.2.6-1 Setup Procedure for a Computer Dedicated to License Management
SEE
ALSO For more information about setting up a computer dedicated to license management, refer to:
B6., “Setting Up the Computer Dedicated to License Management” on page B6-1

<A2.3 Explanation for Maintenance> A2-16
A2.3 Explanation for Maintenance

When you perform the following maintenance tasks, refer to Part C.
• Add licenses and change license assignments
• Set up the domain environment later
• Back up the system
• Upgrade the ProSafe-RS software
• Find out cautionary notes for upgrading and compatibility with the previous revision
• Uninstall the ProSafe-RS software
• Reinstall the ProSafe-RS software
• Troubleshooting

<B. New Setup> B-1
B. New Setup
This section describes the procedure for setting up the devices such as the SENG, file server,
computer dedicated to license management.

<B1. Preparing for the Setup> B1-1
B1. Preparing for the Setup

This section explains the items that must be determined before you start setting up a station
and precautions for the setup.

<B1.1 Items to be Determined Before the Setup> B1-2
B1.1 Items to be Determined Before the Setup

This section lists the items that need to be determined before you start the setup tasks.
n Domain Number/Station Number

A domain number is a number assigned to a group of stations connected on a control bus
network. Set a domain number from 1 to 31 (1 to 16 when integrating with CENTUM).
A station number is a number assigned to each station. In each domain, station numbers
should be set within a range from 1 to 64.
n Computer Name/Station Name

A computer name is a name used to identify each computer on the Windows network. You
can set the computer name from Windows Control Panel.
A station name is a unique name that is assigned based on the control bus address in the
ProSafe-RS system.
Examples: HISddss (HIS/SENG)
STNddss (SENG)
(ddss: “dd” is the domain number and “ss” is the station number.)
It is recommended to match the computer name and the station name of a station.
n IP Address
Determine the IP addresses of stations for control bus and Ethernet.
When using Vnet/IP without installing Ethernet, also determine the IP addresses for Vnet/IP
open communication.
n Subnet Mask
Determine the subnet masks of stations for control bus and Ethernet.
When using Vnet/IP without installing Ethernet, also determine the subnet masks for Vnet/IP
open communication.
SEE
ALSO For more information about IP addresses and subnet mask for control bus, refer to:
“l Setting IP Address for Vnet” on page B3-33
For more information about IP addresses and subnet mask for VnetIPOpen, refer to:
“l IP Address for VnetIPOpen” on page B3-34
For more information about IP addresses and subnet mask for Ethernet, refer to:
“l Setting IP Address for Ethernet” on page B3-34
n Administrative User's Account and Password

Determine the name and password for the administrative user account of the computer.
If the system is used in a domain environment, determine the name and password for the ad-
ministrative user of the domain.
n Security Model and User Management Type

Determine the security model and user management type.

<B1.1 Items to be Determined Before the Setup> B1-3
IMPORTANT
• Be sure to determine the policies for security settings of the entire system before you
start the setup tasks because some of the setup procedures vary depending on the se-
curity model and user management type.
• If you select the Legacy model, restrictions related to Windows are in effect in some envi-
ronments. For that reason, we recommend you select the Standard model.
SEE
ALSO For more information about IT security, refer to:
n License Assignment
Determine the license assignments for the computers you are going to set up.
IMPORTANT
In a ProSafe-RS system, you need to decide on one computer to be used as the license man-
agement station. The license management station can be set up on a computer where SENG
runs.
When setting up each station, you must set up the license management station first. Then, set
up the computers that will be used as license-assigned stations. The software packages in-
stalled on each license-assigned station become available for use after you distribute the li-
censes from the license management station and accept them.
If an independent license management station is desired, you can also set it up as the com-
puter dedicated to license management.
SEE
ALSO For more information about licenses, refer to:

<B1.2 Precautions for Setup> B1-4
B1.2 Precautions for Setup

Take note of the following precautions before you start the setup.
n Changes in Windows Settings

Installing the ProSafe-RS software changes the following Windows settings.
Table B1.2-1 Changes in Windows Settings

Items Setting Purpose
Account name display in logon screen Disable To protect logon account names from unauthorized use.
Fast user switching Disable Simultaneous logon of multiple users is not supported.
n When the System Contains Different Revisions

• The SENGs in the same RS project should have the software of the same release num-
ber.
• The SCS system program release number of SCSs in a system should basically be the
same, but mixture of different release numbers is allowed. However, release numbers of
SCSs communicating with each other by Inter-SCS safety communication must be in ac-
cordance with the explanation in this manual.
SEE
ALSO For more information about compatibility in inter-SCS safety communication between different revisions, refer
to:
• Appendix 6.1, “Cautionary Notes for Upgrading to R4.01” on page App.6-2
• C5., "Upgrading to R3.02.20" and Appendix 4., "Compatibility between Revisions and Cautionary
Notes for Upgrading" in Installation for ProSafe-RS R3 (IM 32Q01C50-31E)
n When a User Account Control Dialog Box Appears

During installation, a user account control dialog box may be displayed on certain circumstan-
ces.
If displayed, click [Yes] or [Continue] (for uninstallation, [Yes] or [Allow]) to continue.
n Downloading the Windows Update Programs (Windows 10

Enterprise 2019 LTSC)
Download and apply the following Windows update programs. If you do not apply these up-
dates, permissions to access to some ProSafe-RS installation folders may not be specified
properly.
• Servicing stack updates for Windows 10, version 1809 in September 8, 2020
• Cumulative update for Windows 10, version 1809 in September 8, 2020
TIP This information is current as of September 2020. The latest information is provided as Endpoint Security
Service. For information about the Endpoint Security Service, contact YOKOGAWA.
n Downloading the Windows Update Programs (Windows Server 2012

R2)
Download and apply the following Windows update programs. If you do not apply these up-
dates, an error occurs when you access the share folders and files on Windows Server 2012
R2, and you cannot access them.

<B1.2 Precautions for Setup> B1-5
• Servicing stack update for Windows Server 2012 R2 in July 14, 2020
• Windows Server 2012 R2 Update in April 2014
• Security Update for Windows Server 2012 R2 in November 2014
n When Connecting with Other Products

When connecting ProSafe-RS to other YOKOGAWA products, configuration of IT security set-
tings or other tasks may be required.
SEE
ALSO For more information about the tasks when connecting CENTUM VP with other products, refer to:
D., “Connection with Other Products” on page D-1
n Notes on Initial Data of IT Security Settings

On a file server or domain controller, it is necessary to save the state before applying IT se-
curity settings as initial data.
When changing the user management type or IT security setting items, use the saved initial
data to restore the state before applying the IT security settings, and then apply the IT securi-
ty settings again.
About a file server, when changing the security settings, the following saved data of IT securi-
ty settings is required depending on the user management type.
• When the user management type is standalone management or linked domain manage-
ment in Standard model:
Data saved before the first application of IT security settings in the standalone state
• When the user management type is Domain management or Combination management
in Standard model:
Data saved before applying IT security settings after adding to the domain
SEE
ALSO For more information about saving of IT security settings of the computer that serves only as a file server,
refer to:
“n Procedure 4: Save the Initial Data of the IT Security Settings” on page B5-5
For more information about the procedure for reapplying IT security, refer to:
6.5.2, “Procedure for a File Server or Domain Controller” in ProSafe-RS Security Guide (IM
32P01C70-01EN)

<B1.3 Precautions for Setting Up ProSafe-RS on a Virtual Machine on the Virtualization Platform >
B1-6
B1.3 Precautions for Setting Up ProSafe-RS on

a Virtual Machine on the Virtualization
Platform
The following are precautions on setting up ProSafe-RS on a virtual machine on the virtualiza-
tion platform.
n Creating and Mounting ISO Format Files

A virtual machine on the virtualization platform cannot access the optical drive on the virtuali-
zation host computer. When using DVD-ROM or other media, for setting up a virtual machine,
you must convert the media to ISO format and save it in an accessible folder on the host OS.
l Create an ISO Format File

On the host OS, save the contents of the software media to an ISO format file by using free
software or other means.
l Mounting an ISO Format File on a Virtual Machine

Follow these steps to mount an ISO format file on a virtual machine:
1. Sign in to the host OS of virtualization host computer as an administrative user.
2. Copy an ISO format file of the software to mount and paste it into a folder on the host OS.
3. Select [Start] > [Server Manager].
Server Manager starts.
4. Select [Tools] > [Hyper-V Manager].
Hyper-V Manager starts.
5. On the left pane, select the virtualization host computer.
Virtual machines on the virtualization host computer are displayed on the middle pane.
6. Right-click on the virtual machine that the ISO format file is mounted and select [Con-
nect].
The virtual machine connection window appears.
TIP The virtual machine connection window may appear full-screen. If it appears full-screen, click [Undo] to exit
full-screen.
7. Select [Media] > [DVD Drive] > [Insert Disk].

A file opening dialog box appears.
8. Select the ISO format file of the software to mount and click [Open].
The selected ISO format file is mounted on the virtual machine.
n Replacement in Descriptions when Installing on a Virtual Machine

on the Virtualization Platform
When you install software on a virtual machine on the virtualization platform, replace “Insert
the xxx software medium into the drive.” with “Specify the ISO format file of the xxx software.”
as you read the descriptions of procedures.

<B2. Setting Up the Windows Domain Environment> B2-1
B2. Setting Up the Windows Domain

Environment
This section describes the required settings when ProSafe-RS is used in a Windows domain
environment. You may also set up the Windows domain environment at a later stage.
SEE
ALSO For more information about how to set up the Windows domain environment later, refer to:
C2., “Setting Up the Windows Domain Environment Later” on page C2-1
n Consolidated Management of IT Security Settings Using the Domain

Controller
ProSafe-RS allows for consolidated management of IT security settings using the domain
controller.
To perform consolidated management of IT security settings, set IT securities on all clients
first, and then use the domain controller to set consolidated management of IT security set-
tings.
SEE
ALSO For more information about the procedure for setting IT security on a client, refer to:
For more information about setting up consolidated management of IT security settings, refer to:
6.10, “Active Directory-Based Consolidated Management of IT Security Settings” in ProSafe-RS Security
Guide (IM 32P01C70-01EN)

<B2.1 Overview of Setting Up the Domain Environment> B2-2
B2.1 Overview of Setting Up the Domain

Environment
This section explains the overview of setting up the Windows domain environment.
It is recommended to provide dual-redundant domain controllers because the entire system
will have troubles if the only domain controller fails.
n Workflow
The following figure shows the procedure for setting up the Windows domain environment.
Start
Set up the domain controller

for the domain controller
Create domain users
Add client computers

to the domain
End
Figure B2.1-1 Flow of setting up the Windows domain environment
The timing for adding the client computer to the domain differs depending on whether the user
management type of the IT security settings of the client computer is linked domain manage-
ment or domain/combination management.
SEE
ALSO For more information about the timing for adding client computers to the domain, refer to:
B2.5, “Adding Computers to the Domain” on page B2-17
n Items to be Determined in Advance

• Domain name
• IP Address of the domain controller
n Items to be Prepared
• Computer for the domain controller
• ProSafe-RS software medium
This is required for configuration of IT security settings.
n Items to be Set to the Domain Controller in Advance

• IP address
• Password for the Administrator account

n Forest and Domain Function Level Settings

To configure the domain controller, the forest function level and domain function level must be
set. The function level to be set varies depending on whether a new forest and domain will be
configured or the domain controller will be added to an existing forest and domain.
l Function Level to Be Set When Configuring a New Forest and Domain

Set the lowest function level that can be commonly set on all domain controller server OSs
supported by ProSafe-RS.
If the following domain controller server OSs are supported by ProSafe-RS, for example, the
lowest function level is Windows Server 2008:
• Windows Server 2012 R2
• Windows Server 2016
TIP Set the lowest function level, considering the possibility that a server OS of low function level may be added
as a domain controller.
l Functional Level to Be Set When Adding a Domain Controller to an

Existing Forest and Domain
In this case, the functional level of the existing forest and domain is set. Accordingly, which
server OS can be used for the domain controller is limited by the functional level of the exist-
ing forest and domain.
The following table shows a list server OSs that can be selected for different functional levels
of the existing forest and domain.
Table B2.1-1 Functional Levels of Existing Forest and Server OSs Selectable for ProSafe-RS
Functional level of existing forest Server OSs Selectable for ProSafe-RS
Windows Server 2003 Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
Windows Server 2008 R2 Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
Windows Server 2016 Windows Server 2016
Table B2.1-2 Functional Levels of Existing Domain and Server OSs Selectable for ProSafe-RS
Functional level of existing domain Server OSs Selectable for ProSafe-RS
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016 Windows Server 2016

For example, when the function level of the existing forest is Windows Server 2003 and the
function level of the domain is Windows Server 2008 R2, the server OS that is selectable for
ProSafe-RS is Windows Server 2012 R2 or Windows Server 2016.

<B2.2 Configuring the domain controller> B2-5
B2.2 Configuring the domain controller

Configure the domain controller using Windows Server 2012 R2 or Windows Server 2016.
SEE
ALSO For more information about how to configure the domain controller using Windows Server 2012 R2, or Win-
dows Server 2016., refer to:
Windows-related manual or the web site of Microsoft Corporation

<B2.3 Configuring Security Settings for the Domain Controller> B2-6
B2.3 Configuring Security Settings for the

Domain Controller
In a system that uses the Standard model of security settings, you need to run the IT Security
Tool on the domain controller as well to apply the Standard model of security settings.
TIP If you do not run the IT Security Tool on the domain controller because of the security policy of the user envi-
ronment, manually create a domain user group.
SEE
ALSO For more information about domain user groups required by ProSafe-RS, refer to:
• “● Type 3: Standard Model/Strengthened Model - Domain Management” in “■ Combination of User
Management and Security Model for Windows” in 2.2.3, “User/Group Management” in ProSafe-RS
Security Guide (IM 32P01C70-01EN)
• “● Type 4: Standard Model/Strengthened Model - Combination Management” in “■ Combination of
User Management and Security Model for Windows” in 2.2.3, “User/Group Management” in
ProSafe-RS Security Guide (IM 32P01C70-01EN)
• “● Type 5: Standard Model/Strengthened Model - Linked Domain Management” in “■ Combination
of User Management and Security Model for Windows” in 2.2.3, “User/Group Management” in
ProSafe-RS Security Guide (IM 32P01C70-01EN)
n Installing Windows Update Programs (Windows Server 2012 R2)

Download and apply the Windows update programs.
SEE
ALSO For more information about downloading the Windows Server 2012 R2 update programs, refer to:
“n Downloading the Windows Update Programs (Windows Server 2012 R2)” on page B1-4
n Disabling the Automatic Cleanup Task (Windows Server 2016 or

Windows Server 2012 R2)
When using Windows Server 2016 or Windows Server 2012 R2 as a domain controller, disa-
ble Automatic cleanup task.
SEE
ALSO For more information about the procedure for disabling the Automatic cleanup task, refer to:
“n Disabling the Automatic Cleanup Task” on page B3-15
n Installation of Microsoft Visual C++ 2017 Redistributable Package

Before you can run the IT Security Tool, you must install the Microsoft Visual C++ 2017 redis-
tributable package.
Follow these steps to install the Microsoft Visual C++ 2017 redistributable package:
1. Log on to the domain controller as an administrative user.
2. Insert the ProSafe-RS software medium into the drive.
3. Using Explorer, double-click <DVD drive>:\ProSafe-RS\vcredist_x86_2017\VC_redist.x
86.exe.
4. Agree to the license terms and perform the installation.

n Preparing for Running the IT Security Tool

1. Log on to the domain controller as an administrative user.
2. Open the Control Panel.
3. Select [System and Security] > [Administrative Tools] > [Active Directory Users and Com-
puters].
The Active Directory Users and Computers window appears.
4. In the left pane, right-click the [Users] folder and then select [New] > [Group].
The New Object - Group dialog box appears.
Figure B2.3-1 Active Directory Users and Computers
5. Enter PSF_MAINTENANCE in the Group name box, select the Group scope and Group
type options, and then click [OK].

Figure B2.3-2 New Object - Group
6. Check the right pane to confirm that the PSF_MAINTENANCE group has been created in
Users.
Figure B2.3-3 Activate Directory Users and Computers (after creating a new group)
7. Add the logged on user to the PSF_MAINTENANCE and Domain Admins groups.
TIP If the domain controller is shared with CENTUM VP, the user must also belong to the CTM_MAINTENANCE
group.
SEE
ALSO For more information about how to add uses to user groups, refer to:
“n Adding Domain Users to Domain Groups” on page B2-14

n Saving the Initial IT Security Settings
IMPORTANT
• When changing the IT security setting items, you need to use the initial data that was
saved beforehand to restore the state before applying the IT security settings, and then
apply the IT security settings again. Therefore, before you run the IT Security Tool to con-
figure IT security settings for the first time after the Windows domain has been set up, be
sure to save the security settings on the computer.
• When configuring the security settings for the second time onward, basically the security
settings need not be saved. To configure the security settings by using the IT Security
Tool of R3.01 to R4.02 and change the IT security version to 2.0 by using the IT Security
Tool of R4.03 or later, save the initial security setting data again.
• To save the initial security setting data again, restore the security settings that were
saved before by using the IT Security Tool. Then, perform this procedure to save the se-
curity settings. From then on, the data you have saved again will be used when the se-
curity settings are initialized; accordingly, keep the saved data in a safe place.
Follow these steps to save the security settings before your run the IT Security Tool:
1. Log on to the computer as the user who belongs to the Domain Admins and PSF_MAIN-
TENANCE groups.
• If the AutoPlay dialog box appears, click [Run Launcher.exe].
• If the AutoPlay dialog box does not appear, use Explorer and double-click Launch-
er.exe in the top folder of the software medium.
The installation menu appears.
3. Click [Setting IT Security (File server/domain controller use)].
The IT Security Tool starts.

Figure B2.3-4 IT Security Tool menu
4. Click [Save].
The Specify destination page appears.
5. Specify the destination folder and enter following setting items.
• Distinguished Name
• Support Product
• Support OS
• File Version
TIP The [Distinguished Name] and [File Version] are omissible.
6. Click [Next].
The Type default account password page appears.
7. Enter the password for use as the initial account password and click [Next].
The Type password (Encryption Key) page appears.
TIP This initial password will be set when the account saved with this tool is recovered. If the saved accounts are
not found on the computer when you recover the accounts, new accounts are created. This password will be
set as the initial password for the newly created account.
Even when multiple accounts have been created, the same initial password is assigned to all.
If the set password does not meet the password policy in the environment where the account is to be recov-
ered, an error will occur when recovering an account.
This password is set as the initial password for the account. Accordingly, you will be prompted to change the
password when you log on for the first time using this account.
8. Enter the password for encrypting the saved data, and click [Next].
Saving of the security settings starts.

IMPORTANT
• If this password (encryption key) is lost, the saved security settings cannot be restored.
The password (encryption key) must be carefully kept by the customer.
• The password (encryption key) must be at least one character.
• The password can consist of upper-case and lower-case alphanumeric characters and
the following symbols: ` ~ ! @ # $ % ^ & * ( ) _ + - = { } | \ : " ; ' < > ? , . /
Double-byte characters cannot be used.
9. When the saving is completed, click [Finish].

If the saving failed, the details of the failure are displayed.
10. On the IT Security Tool menu, click [Close].
TIP If any save failures are displayed, contact YOKOGAWA Service.
n Configuring IT Security Settings

1. From the IT Security Tool menu, click [Setup].
A confirmation dialog box appears.
2. If you have saved the aforementioned security setting data for initialization, click [OK].
The Select Security Model page appears.
TIP If you have not saved the initial security setting data, click [Cancel] to go back to the main menu and save the
current security settings.
Figure B2.3-5 Select Security Model
3. From the Select IT security version drop-down list, select the IT security version.
4. From the Setting Model drop-down list, select [Domain Controller Standard Model Do-
main/Combination Management].

5. Click [Next].
The Confirm Setting Information page appears.
TIP If you click [Details], the Select Setting Items page appears.
6. For the rest of steps, perform the same operations as when the IT Security Tool is run
immediately after installing the ProSafe-RS software.
TIP If the domain controller is shared with CENTUM VP, start the IT Security Tool for file server and domain con-
troller from the installation menu of CENTUM VP R6.04 or later software medium and set IT security for
CENTUM VP as well.
SEE
ALSO For more information about the IT security setting operations that are performed following the ProSafe-RS
software installation, refer to:
B3.6.1, “Running the IT Security Tool” on page B3-45
For more information about the procedure for importing the IT security settings, refer to:
6.8, “Exporting/Importing the IT Security Setting File” in ProSafe-RS Security Guide (IM
32P01C70-01EN)

<B2.4 Creating Domain Users> B2-13
B2.4 Creating Domain Users

This section explains how to create domain users and add them to the domain groups.
IMPORTANT
When you change the rights of domain users, the changes may not be applied immediately. If
this happens, log on and log off twice on each computer after you have changed users' rights.
Do the same thing when you have deleted rights from domain users.
n Creating a Domain User

puters].
The Activate Directory Users and Computers window appears.
3. In the left pane, right-click the [Users] folder and then select [New] > [User].
Figure B2.4-1 Activate Directory Users and Computers
4. The New Object-User dialog box is displayed. Input the necessary information.
TIP Full name and User logon name have to be input in this dialog box. Additionally, if the User logon name is
input, another logon name which is located under the above-mentioned User logon name is automatically in-
put. However, the name is changeable.

Figure B2.4-2 New Object-User
5. Click [Next].
A dialog box appears, prompting you to enter the password.
6. Enter the password, select the check boxes of the required items, and click [Next].
7. Click [Finish].
8. Open the Users folder and check the right pane to confirm that the new domain user has
been added.
Figure B2.4-3 Activate Directory Users and Computers (confirmation of newly created user)
n Adding Domain Users to Domain Groups

When applying the Standard model of security settings, you must add the domain users to ap-
propriate domain groups.

After you run the IT Security Tool on the domain controller, the following ProSafe-RS domain
groups have been created.
• PSF_OPERATOR
• PSF_ENGINEER
• PSF_OPC
• PSF_MAINTENANCE
• ADS_MANAGER
l Adding a Domain User to a Domain Group

This section describes an example of adding a domain user (the user “yokogawa”) to the
PSF_MAINTENANCE group.
TIP For domain users who belong to a domain group which requires administrative rights, you also need to per-
form the procedure in the next section "●Setting Administrative Rights."
1. In the Active Directory Users and Computers window, double click the user that you want
to grant the group's rights.
The properties dialog box for the selected user appears.
2. Select the [Member Of] tab and click [Add].
The Select Groups dialog box appears.
3. Click [Advanced].
The advanced settings are displayed in the Select Groups dialog box.
4. Click [Find] to display the list of available groups. Select the PSF_MAINTENANCE group
and click [OK].
Figure B2.4-4 Select Groups dialog box - Search results
5. In the Select Groups dialog box, ensure that PSF_MAINTENANCE appears and click
[OK].
6. In the Properties dialog box, confirm that PSF_MAINTENANCE is displayed in the Mem-
ber of list.

l Setting Administrative Rights

Follow these steps to assign administrative rights to a domain user who belongs to a domain
group which requires administrative rights:
1. Add the domain user to the Domain Admins group.
2. Open the properties dialog box for the user. Click the [Member Of] tab, select [Domain
Admins], and click [Set Primary Group].
The primary group of the user changes to Domain Admins.
3. Select [Domain Users] and click [Remove].
4. Confirm that Domain User has been removed from the Member of list and click [OK].

<B2.5 Adding Computers to the Domain> B2-17
B2.5 Adding Computers to the Domain

To add computers to a domain, computer accounts of the computers need to exist on the do-
main controller. Computer accounts can be created in two ways: creating on the domain con-
troller or on computers.
When creating a computer account on the domain controller, the computer can be added to
the domain by configuring on the computer after the computer account is created. When cre-
ating a computer account on the computer, the computer is added to the domain at the same
time the computer account is created.
This section explains the procedure for the case where computer accounts are created on the
domain controller and computer can be added to the domain by configuring on the computer.
In the procedure, you are required to enter the user name and password of the administrative
user of the domain when you configure on a computer.
n Precautions When Setting Up Computers

This section describes precautions on operating the client computer with linked domain man-
agement for its user management type of the IT security settings.
• After you run IT Security Tool on the client computer, add the computer to the domain be-
fore you run Domain Link Management Tool.
The following are precautions on operating the client computer with domain or combination
management for its user management type of the IT security settings.
• Before you install the ProSafe-RS software, add the client computer to the domain.
• If you are unable to add the computer to the domain in advance, set the Legacy model or
the Standard model applying Standalone management temporarily in the IT security set-
ting configuration that is performed following the ProSafe-RS software installation. Then,
add the computer to the domain and change to the Standard model applying Domain
management or Combination management.
• If a user who belongs to a domain group is used to install the ProSafe-RS software on a
computer added to the domain, an administrative user for installing the ProSafe-RS soft-
ware on the domain controller must be created in advance. Add the administrative user to
the Domain Admins and PSF_MAINTENANCE user groups in advance.
• After installing the ProSafe-RS software, add the administrative user of the computer to
the PSF_MAINTENANCE_LCL group.
SEE
ALSO For more information about changing the security model, refer to:
6.4, “Changing the IT Security Settings” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
n Configuration on the Domain Controller

puters].
The Active Directory Users and Computers window is displayed.
3. Right-click the Computers folder, and select [New] > [Computers].
The New Object - Computer dialog box appears.
4. Enter the [Computer Name], and click [OK].
5. Confirm that the new computer has been added in the Computers folder.
Configuration on the domain controller is finished. Go on to the procedure for configura-
tion on the computer.

<B2.5 Adding Computers to the Domain> B2-18
n Configuration on a Computer
Follow these steps to add a computer to the domain:
2. Select [System and Security] > [System].
The System window appears.
3. Click [Change Settings].
The System Properties dialog box appears.
4. Select the [Computer Name] tab and click [Change].
The Computer Name/Domain Changes dialog box appears.
5. Select [Domain], enter the domain name, and click [OK].
The Windows Security dialog box appears.
6. Enter the user name and password of the administrative user of the domain and click
[OK].
TIP An error message dialog box may appear, indicating that the domain name cannot be changed. However, you
can click [OK] to proceed because the computer has been added to the domain successfully.
7. On the Computer Name/Domain Changes dialog box, click [OK].

8. On the dialog box for confirmation of restarting, click [Restart Now] to restart the comput-
er.

<B2.6 Setting Up Redundant Domain Controllers> B2-19
B2.6 Setting Up Redundant Domain Controllers

It is recommended to provide another domain controller for redundancy because the entire
system will have troubles if the only domain controller fails.
n Setup Procedure
1. Add the second domain controller computer to the existing domain.
2. Configure IT security settings.
SEE
ALSO For more information about IT security settings, refer to:
B2.3, “Configuring Security Settings for the Domain Controller” on page B2-6

<B2.7 Setting Up Time Synchronization in Windows Domain Environment> B2-20
B2.7 Setting Up Time Synchronization in

Windows Domain Environment
When using ProSafe-RS in a Windows domain environment, the time on computers used in
the ProSafe-RS system and the time on the domain controller must be synchronized.
Because the time synchronization service of a ProSafe-RS system uses the time on the con-
trol bus as the time master, the time of the domain controller should be synchronized to the
time of client computers if the system is used in a domain environment.
This section describes how to set up time synchronization in a system that consists of only
ProSafe-RS.
n Cautionary Note on Time Synchronization

A computer installed with the ProSafe-RS software is automatically configured so as not to
use the domain controller as the time master for time synchronization, even if the computer is
added to the Windows domain.

B2.7.1 Implementing Time Synchronization in a System

Consisting of Only ProSafe-RS
This section describes how to implement time synchronization in a system consisting of only
ProSafe-RS for the following cases:
• V net — Not synchronize to the Coordinated Universal Time (UTC)
• Vnet/IP — Synchronize to the Coordinated Universal Time (UTC)
• Vnet/IP — Not synchronize to the Coordinated Universal Time (UTC)
n For V net — Not Synchronize to the Coordinated Universal Time

(UTC)
Configure a station connected to the V net domain as the SNTP server. Times on the comput-
ers within the V net domain are synchronized using the V net time synchronization function.
Time synchronization of the entire system is achieved by synchronizing the time on the do-
main controller to the SNTP server.
TIP When a station is used as the SNTP server, the system time is not synchronized to UTC but to the time on
the hardware of the SNTP server.
• On the computers connected on V net, do not use the Windows W32Time service to per-
form time synchronization. If used, times on the computers are synchronized to the time
on the domain controller and synchronization with the SNTP server is prevented.
• On the domain controller, use the Windows W32Time service to synchronize its time with
the SNTP server.
Domain
Controller
Ethernet
Synchronize
V net
SNTP Time Master
Computer
Server (SENG etc.)
V net time synchronization

V net
SCS
Figure B2.7.1-1 Implementing Time Synchronization (V net — Not Synchronize to UTC)
SEE
ALSO For more information about how to configure a station as the SNTP server, refer to:
“l Setting a Station as the SNTP Server” on page B2-23
n For Vnet/IP — Synchronize to the Coordinated Universal Time (UTC)

• Introduce an SNTP server and make it synchronize with UTC. Configure the domain con-
troller and the Vnet/IP system so that they will reference the time of the same SNTP serv-
er.

• On the computers connected on Vnet/IP, do not use the Windows W32Time service to
perform time synchronization. If used, times on the computers are synchronized to the
time on the domain controller and synchronization with the SNTP server is prevented.
Domain
Controller
Synchronize
Ethernet
Vnet/IP
SNTP Time Master Computer
Server (SENG etc.)
Synchronize
Vnet/IP
Vnet/IP time synchronization
SCS SCS
Figure B2.7.1-2 Implementing Time Synchronization (Vnet/IP — Synchronize to UTC)
n For Vnet/IP — Not Synchronize to the Coordinated Universal Time

(UTC)
Configure a station connected to the Vnet/IP domain as the SNTP server. Times on the com-
puters within the Vnet/IP domain are synchronized using the Vnet/IP time synchronization
function. Time synchronization of the entire system is achieved by synchronizing the time on
the domain controller to the SNTP server.
TIP When a station is used as the SNTP server, the system time is not synchronized to UTC but to the time on
the hardware of the SNTP server.
• On the computers connected on Vnet/IP, do not use the Windows W32Time service to
perform time synchronization. If used, times on the computers are synchronized to the
time on the domain controller and synchronization with the SNTP server is prevented.
• On the domain controller, use the Windows W32Time service to synchronize its time with
the SNTP server.
Domain
Controller
Synchronize
Ethernet
Vnet/IP
SNTP Time Master
Computer Computer
Server (SENG etc.)
Vnet/IP
Vnet/IP time synchronization
SCS SCS
Figure B2.7.1-3 Implementing Time Synchronization (Vnet/IP — Not Synchronize to UTC)

l Setting a Station as the SNTP Server

1. Use an administrative user account to log on to the station you want to set up as the
SNTP server.
2. Right-click the following file and select [Run As Administrator].
(Drive of ProSafe-RS software medium):\ProSafe-RS\TOOLS\BeNtpServer.cmd
The Command Prompt window appears and displays "Enable NTP Server? (y/n/quit)."
TIP If the IT security settings have been configured to apply software restriction policies, right-click [Command
Prompt] and select [Run As Administrator]. Then, run the program in the Command Prompt that is opened.
3. Enter "y," and then press the [Enter] key.

B2.7.2 Implementing Time Synchronization When

Integrated with CENTUM
When the system is integrated with CENTUM, set up time synchronization by following the ex-
planation provided in the manual of CENTUM. If the system consists of multiple V net do-
mains or a mixture of Vnet/IP domain and V net domain, also follow the explanation in the
manual of CENTUM.
SEE
ALSO For more information about how to set up time synchronization in Windows domain environment for a system
integrated with CENTUM, refer to:
B2.7, "Setting Up Time Synchronization in Windows Domain Environment" in CENTUM VP Installation
(IM 33J01C10-01EN)

<B3. Setup of an SENG or a Computer Installed with Only AD Server> B3-1
B3. Setup of an SENG or a Computer

Installed with Only AD Server
This section describes the tasks required for setting up an SENG or a computer installed with
only AD Server.
IMPORTANT
In a ProSafe-RS system, you need to decide on one computer for use as the license manage-
ment station. The license management station can be set up on a computer where SENG
runs.
Among stations of the system, you must set up the license management station first. Then,
set up the computers that will be used as license-assigned stations. The software packages
installed on the license-assigned stations become available for use after the licenses are dis-
tributed from the license management station and accepted on the license-assigned stations.
If an independent license management station is desired, you can also set it up as the com-
SEE
ALSO For more information about how to set up the computer dedicated to license management, refer to:
Have the following item at hand before new installation of the ProSafe-RS software.
Also have the following items at hand if the SENG is to be used as a license management
station. These are required when distributing licenses.
• ProSafe-RS license medium
• ProSafe-RS license sheet (with project ID)

<B3.1 Setting Up the Hardware> B3-2
B3.1 Setting Up the Hardware

This section describes the settings for a Vnet/IP interface card to be installed in SENG. In the
case of a computer installed with only AD Server and SENG that runs on a virtual machine,
setting is not required because a Vnet/IP interface card is not used.
CAUTION
When removing and installing the cards to set DIP switches, take measure to prevent the
damages caused by static electricity.
SEE
ALSO For more information about antistatic measures, refer to:
Appendix 4., “Antistatic Precautions When Handling Hardware” on page App.4-1
n Front panel of the Vnet/IP interface card

• RDY lamp
This lamp illuminates to indicate that the card is working properly as the result of the peri-
odic diagnosis.
• RCV lamp
This lamp illuminates when a signal is received.
• SND lamp
This lamp illuminates when a signal is sent.
• Vnet/IP connector
These connectors are used for connecting with the Layer2 Switch.
The connector type is RJ45.
The front panel of VI702 is shown as follows:
MODEL
VI702
STYLE
S1
RCV lamp BUS1

RCV
BUS 1 Vnet/IP
side connector
SND lamp SND
RDY
RDY lamp
RCV lamp BUS2

RCV
BUS 2 Vnet/IP
side connector
SND lamp SND
U
H
F
Figure B3.1-1 Vnet/IP Interface Card (VI702)

IMPORTANT
Note the following points when installing and uninstalling the VI702.
• Always install the VI702 before installing the control bus driver and Vnet/IP open commu-
nication driver.
If the VI702 is installed after the control bus driver, the VI702 is not recognized. In this
case, delete the driver, install the VI702, and then install the driver again.
• If the control bus driver and Vnet/IP driver are installed and you want to uninstall the
VI702, delete these drivers first. If this procedure is not followed, an error dialog box will
be displayed after restarting the PC and communication might not be possible.
n Setting Up the Vnet/IP Interface Card

You need to install a Vnet/IP interface card (VI702) in the computer that is to be connected on
a Vnet/IP network.
VI702 is for PCI Express.
The Vnet/IP interface card has DIP switches for setting the domain number, station number
and action mode. The combination of domain number and station number determines the sta-
tion address.
You must set the DIP switches before you configure network settings.
This section describes how to set the DIP switches.
DIP switches
Domain number Station number
DOMAIN
SW1
STATION
SW2
Operating mode
SW4
Figure B3.1-2 Locations of DIP Switches
l Setting the Domain Number

A domain is a collection of stations that are connected on one control bus network. Set a do-
main number from 1 to 31 (1 to 16 when integrating with CENTUM).

DOMAIN NO.
P 0 0 (MSB)(LSB)
1 1 2 3 4 5 6 7 8
0
Domain number (5 bits)

Fixed to 0 (2 bits)
Parity of the domain number (1 bit) (odd parity)
MSB : Most Significant Bit

LSB : Least Significant Bit
Figure B3.1-3 Domain Number Setting DIP Switches
SEE
ALSO For more information about domain numbers and corresponding DIP switch positions, refer to:
“n Domain Numbers and DIP Switch Positions” on page App.1-1
l Setting the Station Number

Station numbers should be set in the range of 1 to 64; it is recommended to set starting from
64 in the descending order.
STATION NO.
P (MSB) (LSB)
1 1 2 3 4 5 6 7 8
0
Station number (7 bits)

Parity of the station number (1 bits) (odd parity)
MSB : Most Significant Bit

LSB : Least Significant Bit
Figure B3.1-4 Station Number Setting DIP Switches
SEE
ALSO For more information about station numbers and corresponding DIP switch positions, refer to:
“n Station Numbers and DIP Switch Positions” on page App.1-2
l Action Mode Switch

SW4 on the printed circuit board is the action mode switch.
Use the card with all the bits of this DIP switch set to OFF (factory set defaults). The meaning
of DIP switch bits are as follows:
Bit number
1
2
3
4
O
F
F
A B C D
Figure B3.1-5 Action Mode Switch
Table B3.1-1 DIP Switch Usage

DIP switch ON DIP switch OFF Remarks
A (bit 1) - Always OFF Reserved
B (bit 2) 100 Mbps 1 Gbps Communication speed (Default: OFF)
C (bit 3) Force Auto Negotiation (Default: OFF)
D (bit 4) - Always OFF Reserved

l Precautions on Installing the Vnet/IP Interface Card

• Install VI702 in the computer after setting up Windows but before configuring the network
settings.
• Install network drivers when you restart the computer after installing VI702. Follow the
procedure in this manual to install the drivers.
• If you reuse VI702 that was used in another system for a stand-alone ProSafe-RS sys-
tem, erase the settings in the VI702 before installing it in the computer. When using such
VI702 in a system integrated with CENTUM, you do not need to erase the settings in the
VI702.
SEE
ALSO For more information about the procedure to install the network driver in a computer, refer to:
• B3.3.1, “Installing the Control Bus Driver” on page B3-19
• B3.3.2, “Installing the Vnet/IP Open Communication Driver” on page B3-21
For more information about how to erase the internal settings of a VI702 card, refer to:
Appendix 2., “Procedure for Erasing VI702 Internal Settings” on page App.2-1
l Installing the Vnet/IP Interface Card

After you have set the station address and action mode on the VI702 card, follow these steps
to install it in the computer:
1. Turn off the power of the computer. For safety, remove the power plug from the outlet.
2. Remove the cover of the main unit of the computer.
3. Unscrew the screws fixing the slot cover and remove the slot cover.
4. Insert the VI702 card in the corresponding slot and fix it to the slot.
5. Mount the cover back on the computer.
6. Connect both the BUS1 and BUS2 cables to VI702 and Layer 2 switch. There is no need
to turn off the power of the Layer 2 switch.
7. Connect the power cord of the computer back to the outlet and turn on the computer.
8. Make sure that the RDY lamp on VI702 is lit.
9. Write the station address on the label that comes with the VI702 card and paste it in the
front or other easy-to-see location of the computer.
l Attaching the Vnet/IP Station Address Label

You need to write the decided domain number and the station number to the station address
seal attached to the VI702. And then stick the seal at the front side of the computer where the
VI702 is installed or any other place that can be easily noticed.
STATION ADDRESS
DOMAIN NO. STATION NO.
Figure B3.1-6 Station Address Label

l Procedures for removing the Vnet/IP interface card
IMPORTANT
Before removing the Vnet/IP interface card, uninstall the control bus driver and Vnet/IP open
communication driver.
2. Disconnect the cables for both BUS1 and BUS2. There is no need to disconnect the ca-
bles from the Layer2 switch.
3. Remove the VI702 from the slot.
SEE
ALSO For more information about the procedure for uninstalling the driver, refer to:
C5.1.2, “Uninstalling the Network Drivers” on page C5-5

<B3.2 Setting Up Windows> B3-7
B3.2 Setting Up Windows

Before installing the ProSafe-RS software, you need to change the Windows settings on your
computer to the recommended settings.
This configuration is performed on the computer where the Windows OS has been installed.

B3.2.1 Setting of Common Windows OS Items

This section describes how to set the items common to Windows 10 and Windows Server
2016.
n File System
Ensure that the file system is in the NTFS format. If it is already formatted in the FAT format,
reinstall the operating system and reformat partitions into NTFS. Partitions not installed with
OS should also be formatted into NTFS.
n System Performance
Follow these steps to configure the system performance setting:
1. Sign in as an administrative user.
3. Select [System and Security] > [System] > [Advanced system settings].
4. Select the [Advanced] tab and click [Settings] in the Performance section.
The Performance Options dialog box appears.
5. On the [Visual Effects] tab, select [Let Windows choose what’s best for my computer].
6. Click [OK].
n Virtual Memory
ProSafe-RS does not require virtual memory configuration. However, if the ProSafe-RS and
CENTUM VP software coexist on the same computer, virtual memory should be configured
according to the instruction of CENTUM VP.
n Power Options
This section describes how to configure the Power Options settings. Some of the items in the
explanation may not be displayed on your computer, depending on the computer's hardware
configuration. If not displayed, the function of that item is not available on your computer.
1. Log on as an administrative user.
3. Select [Hardware and Sound] > [Power Options].
The Power Options window appears.
TIP For Windows Server, select [Hardware] > [Power Options].
4. Select [High performance] under Preferred plans and click [Change plan settings] on the
right side.
The Edit Plan Settings window appears.
TIP If High performance does not appear under Preferred plan, click [Show additional plans]. Select [High per-
formance] and then click [Change plan settings] on the right side.
5. Click [Change advanced power settings].

The Power Options dialog box appears, showing the advanced settings.

TIP Depending on the computer configuration, the items of unavailable functions will not be displayed in the step
results hereafter.
6. In the Power Options dialog box, set as follows:

Hard disk
[Turn off hard disk after]: Never
Sleep
[Sleep after]: Never
[Allow hybrid sleep]: Off
[Hibernate after]: Never
[Allow wake timers]: Disable
Power buttons and lid
[Power button action]: Shut down
Display
[Turn off display after]: Never
7. Click [OK].
TIP Configure the UPS settings after installing the ProSafe-RS software.
SEE
ALSO For more information about setting up UPS services, refer to:

B3.2.2 Setting of Items Specific to Windows 10

This section describes how to set the items specific to Windows 10.
n Turning Off Fast Startup

You must turn off fast startup before installing the control bus driver or Vnet/IP open communi-
cation driver.
Follow these steps to turn off fast startup:
1. Use Windows Explorer to open the WIN10 folder under the following path in the ProSafe-
RS software medium.
(Drive of ProSafe-RS software medium):\ProSafe-RS\TOOLS\WIN10
2. Right-click [HiberbootDisabled.bat], and select [Run as administrator] from the context
menu.
The Command Prompt appears.
3. Confirm that the value of [HiberbootEnabled] is 0 as shown in the following figure.
Figure B3.2.2-1 Command Prompt
4. Hit the [Enter] key to restart the computer.
n Windows Defender
The Windows Defender software detects and removes spy ware.
It is recommended to turn off this function because it is not used with this product.
In a domain environment, turn off Windows Defender on domain member PCs at a time by
means of a domain management operation such as Group Policies.
In a workgroup environment, turn off Windows Defender by using the Local Group Policy Edi-
tor.
l Turning Off Windows Defender in Local Group Policy Editor

Follow these steps to turn off Windows Defender:
2. Open Command Prompt.
3. Enter gpedit.msc.
Local Group Policy Editor appears.
4. In the left pane, select [Computer Configuration] > [Administrative Templates] > [Windows
Components] > [Windows Defender].
5. In the right pane, double-click [Turn off Windows Defender].
The Turn off Windows Defender dialog box appears.
6. Select [Enabled] and click [OK].

TIP In Windows 10 LTSC 2019, the user interfaces are displayed as follows.
• [Windows Defender] is displayed as [Windows Defender Antivirus].
• [Turn off Windows Defender] is displayed as [Turn off Windows Defender Antivirus].
n Defragment and Optimize Drives

The Defragmenter Tool can be used to reorganize the fragmented files on computer hard disk
so as to improve the computer performance. Since the performance of this product may be
affected when defragmenter is running, it is recommended to disable the schedule of the peri-
odic disk defragmentation.
Moreover, you may manually start the disk defragmenter when you feel the disk performance
is getting worse or when you perform system maintenance.
2. Open Control Panel.
3. Select [System and Security] > [Administrative Tools] > [Defragment and Optimize
Drives].
The Optimize Drives window appears.
4. Click [Change settings].
The Optimize Drives dialog box appears.
5. Clear the [Run on a schedule (recommended)] check box and click [OK].
Figure B3.2.2-2 Optimize Drives dialog box
n Disabling the Automatic Cleanup Task

A function is added to automatically clean up old files when update programs are applied.
Execution of Automatic cleanup may cause the degradation in system performance. For that
reason, we recommend disabling Automatic cleanup for this product.
Follow these steps to disable the automatic cleanup task:
3. Select [System and Security] > [Administrative Tools] > [Task Scheduler].
The Task Scheduler window appears.
4. In the left pane, select [Task Scheduler (Local)] > [Task Scheduler Library] > [Microsoft] >
[Windows] > [Servicing].

5. In the middle pane, right-click [StartComponentCleanup] and select [Disable].
n DCOM Settings
When Default Authentication Level in DCOM settings is set to [None], installation of applica-
tions such as redistributable modules fails. When installing this product, set the Default Au-
thentication Level to [Connect].
Follow these steps to set Default Authentication Level to [Connect].
3. Select [System and Security] > [Administrative Tools] > [Component Services].
The Component Services window appears.
Figure B3.2.2-3 Component Services window
4. Select [Console Root] > [Component Services] > [Computers].

5. Right-click [My Computer] and select [Properties].
The My Computer Properties dialog box appears.

Figure B3.2.2-4 My Computer Properties dialog box
6. Open the [Default Properties] tab, from the Default Authentication Level drop-down list,
select [Connect], and then click [OK].
7. Restart the computer.

B3.2.3 Setting of Items Specific to Windows Server 2016

This section describes how to set the items specific to Windows Server 2016.
n Password Setting
Because security is enhanced in Windows Server 2016, complexity may be required when
you set a user password or you may not be able to set a password as intended.
In this case, do the following:
3. Select [System and Security] > [Administrative Tools] > [Local Security Policy].
The Local security policy window appears.
4. In the left pane, select [Security Settings] > [Account Policies] > [Password Policy].
A list of policies is displayed.
5. In the right pane, double-click [Password must meet complexity requirements].
The properties dialog box for the Password must meet complexity requirements appears.
6. Select [Disabled] and click [OK].
7. Confirm that Password must meet complexity requirements setting is disabled.
n Windows Defender
The Windows Defender software detects and removes spy ware.
It is recommended to turn off this function because it is not used with this product.
In a domain environment, turn off Windows Defender on domain member PCs at a time by
means of a domain management operation such as Group Policies.
In a workgroup environment, turn off Windows Defender by using the Local Group Policy Edi-
tor.
l Turning off Windows Defender in Local Group Policy Editor

Follow these steps to turn off Windows Defender:
3. Enter gpedit.msc.
Local Group Policy Editor appears.
4. In the left pane, select [Computer Configuration] > [Administrative Templates] > [Windows
Components] > [Windows Defender].
5. In the right pane, double-click [Turn off Windows Defender].
The Turn off Windows Defender dialog box appears.
6. Select [Enabled] and click [OK].
n Defragment and Optimize Drives

The Defragmenter Tool can be used to reorganize the fragmented files on computer hard disk
so as to improve the computer performance. Since the performance of this product may be
affected when the defragmenter is running, it is recommended to disable the schedule of the
periodic disk defragmentation.

Moreover, you may manually start the disk defragmenter when you feel the disk performance
is getting worse or when you perform system maintenance.
3. Select [System and Security] > [Administrative Tools] > [Defragment and Optimize
Drives].
The Optimize Drives window appears.
4. Click [Change settings].
The Optimize Drives dialog box appears.
5. Clear the [Run on a schedule (recommended)] check box and click [OK].
Figure B3.2.3-1 Optimize Drives dialog box
n Disabling the Automatic Cleanup Task

A function is added to automatically clean up old files when update programs are applied.
Execution of Automatic cleanup may cause the degradation in system performance. For that
reason, we recommend disabling Automatic cleanup for this product.
Follow these steps to disable the automatic cleanup task:
3. Select [System and Security] > [Administrative Tools] > [Task Scheduler].
The Task Scheduler window appears.
4. In the left pane, select [Task Scheduler (Local)] > [Task Scheduler Library] > [Microsoft] >
[Windows] > [Servicing].
5. In the middle pane, right-click [StartComponentCleanup] and select [Disable].
n DCOM Settings
When Default Authentication Level in DCOM settings is set to [None], installation of applica-
tions such as redistributable modules fails. When installing this product, set the Default Au-
thentication Level to [Connect].
Follow these steps to set Default Authentication Level to [Connect].

3. Select [System and Security] > [Administrative Tools] > [Component Services].
The Component Services window appears.
Figure B3.2.3-2 Component Services window
4. Select [Console Root] > [Component Services] > [Computers].

5. Right-click [My Computer] and select [Properties].
The My Computer Properties dialog box appears.

Figure B3.2.3-3 My Computer Properties dialog box
6. Open the [Default Properties] tab, from the Default Authentication Level drop-down list,
select [Connect], and then click [OK].

<B3.3 Configuring Network Settings> B3-18
B3.3 Configuring Network Settings

To use the control bus, you need to install the control bus driver. If Vnet/IP is used as the con-
trol bus, you need to install the Vnet/IP open communication driver as well.
This section describes how to install the control bus driver and the Vnet/IP open communica-
tion driver.
If you use the built-in Ethernet interface of the computer or an over-the-counter Ethernet card,
read the attached instruction manual and install the proper Ethernet driver accordingly.
In the case of SENG that runs on a virtual machine, install the Vnet/IP Interface Package on
the virtual machine. Also, do not install the Vnet/IP open communication driver.
TIP On a network where there is a virtual machine with the Vnet/IP Interface Package installed, it cannot be con-
figured when only Vnet/IP is installed.
After installing the driver and interface package, set up the Windows network.

B3.3.1 Installing the Control Bus Driver

This section describes the procedure for installing the control bus driver.
n Precautions at Installation
Mount a control bus interface card or Vnet/IP interface card in computers to be connected on
a control bus network. In addition, you must install the control bus driver. Observe the follow-
ing precautions when you install the control bus driver.
• Before installing the control bus driver, be sure to install a control bus interface card or
Vnet/IP interface card in the computer.
• For Windows 10, be sure to check that fast startup is turned off before installing the con-
trol bus driver. If fast startup is not turned off, turn it off and restart the computer.
• If you installed the control bus driver without installing a control bus interface card or
Vnet/IP interface card by mistake, uninstall the control bus driver. Then, install a control
bus interface card and install the driver again.
• If you want to change the slot in which a control bus interface card or Vnet/IP interface
card is installed, uninstall the control bus driver first and then change the slot. After
changing the slot, install the driver again.
• When you remove a control bus interface card or Vnet/IP interface card from the comput-
er where the control bus driver was installed with the card installed, uninstall the driver
before you remove the card from the slot.
TIP • When installing the control bus driver, restarting the computer is basically not required. However, restart
the computer if a dialog box indicating completion of the installation (restarting required) is displayed.
• After you install the driver, you need to configure network settings.
SEE
ALSO For more information about turning off fast startup, refer to:
“n Turning Off Fast Startup” on page B3-10
n Notes on Using SCS Simulator

To use the SCS simulator, an environment where ProSafe-RS is integrated with CENTUM is
mandatory. You can run the SCS simulator even on a computer where a control bus interface
card or Vnet/IP interface is not mounted; however, you must always install the control bus
driver on such computers. Observe the following precautions when you install the control bus
driver on a computer where these cards are not mounted in order to use the SCS simulator.
• Install the control bus driver, and then configure Windows network settings.
• If you use the expanded test functions to run SCS simulators on multiple computers, in-
stall the control bus driver in all the computers on which you run the SCS simulator with-
out mounting a control bus card. If mounted, you cannot launch the SCS simulator re-
motely.
TIP • If a control bus card is not mounted when you install the control bus driver, a control bus driver of the
version for use without a control bus card is installed. This driver is used when the SCS simulator is run
without mounting a control bus card.
• To reuse or divert a computer installed with a without-a-control-bus-card version of control bus driver for
use in actual plant operation, uninstall the control bus driver, mount a control bus card, and then install
the control bus driver again.
• The control bus driver should be installed according to the procedure for installing the
control bus driver.

• For the IP address for the control bus driver on each computer, set the address of control
bus, “domain number (dd) .station number (ss)”.
Example: 172.16.dd.ss
Note that dd.ss must not overlap with the addresses of the other stations. In particular, it
must not overlap with the “domain number.station number” used for SCS and FCS.
n Installation Procedure
er.exe in the top folder of the ProSafe-RS software medium.
3. On the installation menu, click [Control Bus Driver].
A dialog box appears, prompting you to confirm the setup.
4. Select [INSTALL] and click [OK].
A dialog box appears, confirming to execute the installation.
5. Click [OK].
TIP • If the Windows Security dialog box appears, select the [Always trust software from “Yokogawa Electric
Corporation”] check box, and click [Install].
• Do not click [Don’t Install] on the Windows Security dialog boxes. If clicked, an error occurs.
6. When the message telling successful installation is displayed, click [OK].

TIP If you have added or deleted any other devices before you install the control bus driver, a message prompting
you to restart the computer may be displayed. In such a case, be sure to restart the computer.

B3.3.2 Installing the Vnet/IP Open Communication Driver

When Vnet/IP is used as the control bus, the Vnet/IP open communication driver also needs
to be installed. If Ethernet is also used, the installed Vnet/IP open communication driver must
be disabled.
This section describes the procedure for installing the Vnet/IP open communication driver.
IMPORTANT
When the Vnet/IP interface card is mounted, always install the Vnet/IP open communication
driver even if Vnet/IP open communication is not used.
n Precautions at Installation
• Before installing the Vnet/IP open communication driver, be sure to install a Vnet/IP inter-
face card in the computer. You cannot install the driver if the card is not installed.
• For Windows 10, be sure to check that fast startup is turned off before installing the
Vnet/IP open communication driver. If fast startup is not turned off, turn it off and restart
the computer.
• If you want to change the slot in which a Vnet/IP interface card is mounted, uninstall the
Vnet/IP open communication driver and control bus driver and then change the slot. After
changing the slot, install the drivers again.
• When removing a Vnet/IP interface card from a computer after the Vnet/IP open commu-
nication driver is installed, uninstall the driver before you remove the card from the slot.
TIP • When installing the Vnet/IP open communication driver, restarting the computer is basically not required.
However, restart the computer if a dialog box indicating completion of the installation (restarting re-
quired) is displayed.
• When Ethernet is also used, configure network settings after you install the Vnet/IP open communication
driver and disable the driver.
When Ethernet is not used, configure network settings after you install the Vnet/IP open communication
driver.
SEE
ALSO For more information about turning off fast startup, refer to:
“n Turning Off Fast Startup” on page B3-10
3. On the installation menu, click the [Vnet/IP Open com driver].
5. Click [OK].

• Do not click [Don’t Install] on the Windows Security dialog box. If clicked, an error occurs.

TIP If you have added or deleted any other devices before you install the Vnet/IP open communication driver, a
message prompting you to restart the computer may be displayed. In such a case, be sure to restart the com-
puter.

B3.3.3 Installing the Vnet/IP Interface Package on a Virtual

Machine
When using the virtualization platform, you need to install the Vnet/IP Interface Package on a
virtual machine.
Follow these steps to install the Vnet/IP Interface Package on a virtual machine.
The procedures explained here should be performed on the guest OS of the virtual machine.
IMPORTANT
• You do not need to install a Vnet/IP interface card in the virtualization host computer.
• When multiple products coexist in one virtual machine, you do not need to install the
Vnet/IP Interface Package as long as a Vnet/IP Interface Package has already been in-
stalled on another product.
• After installing the Vnet/IP Interface Package, you need to configure the Windows net-
work settings on the virtual machine.
SEE
ALSO For more information about overview of virtualization platform and precautions on using ProSafe-RS with a
virtual machine, refer to:
A7., “Virtualization platform” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)
For more information about details of the virtualization platform, refer to:
• Virtualization Platform Setup (IM 30A05B20-01EN)
• Virtualization Platform Planning and Implementation Guide (TI 30A05B10-01EN)
n Precautions When Installing the Vnet/IP Interface Package

Observe the following precautions when you install the Vnet/IP Interface Package.
l Precautions at First-time Installation

Install the Vnet/IP Interface Package before applying IT security. If you install the Vnet/IP In-
terface Package for the first time on a computer after applying IT security, you must apply IT
security again.
TIP After IT security is applied, you do not need to apply IT security again when you reinstall the Vnet/IP Interface
Package.
l Precautions at Reinstallation
Reinstalling the Vnet/IP Interface Package resets the password of the Vnet/IP Interface Pack-
age execution user. If you have changed the password, set it again.
n Procedure to Install the Vnet/IP Interface Package

Follow these steps to install the Vnet/IP Interface Package.
l Preparation
Install Windows update as a preparation.
Download and apply the following Windows update program. If it is not applied, the installa-
tion of Windows update fails.

• Servicing stack updates for Windows 10, version 1607 in July 14, 2020
In addition, download and apply the following Windows update program. If it is not applied,
error log overflow occurs in system log collection in RIP Listener.
• Cumulative update for Windows 10, version 1607 in August 11, 2020
l Procedure 1: Enable the RIP Listener Service

In Windows Server 2016, the RIP Listener service is disabled by default, so you must enable
the RIP Listener service. Follow these steps to enable the RIP Listener Service:
1. Sign in to the guest OS on the virtual machine as an administrative user.
2. Run the Command Prompt as Administrator.
3. Run the following command:
dism /online /enable-feature /featurename:rasrip /all
4. Confirm that the message, “The operation completed successfully.” appears.
5. Check that the RIP Listener service has been enabled.
a. Open Control Panel.
b. Select [System and Security] > [Administrative Tools] > [Service].
The Services window appears.
c. Confirm that RIP Listener is shown and its Startup Type is [Automatic].
TIP If the Default Authentication Level of DCOM is set to “None,” you cannot enable the RIP Listener service.
SEE
ALSO For more information about how to change the default authentication level of DCOM to “Connect”, refer to:
“n DCOM Settings” on page B3-15
l Procedure 2: Install the Vnet/IP Interface Package

Follow these steps to install the Vnet/IP Interface Package.
TIP If you have added or deleted any other devices before you install the Vnet/IP Interface Package, a message
prompting you to restart the computer may be displayed. If displayed, be sure to restart the virtual machine.

2. Copy an ISO format file of the ProSafe-RS software medium and paste it into a folder on
the host OS.
nect].

full-screen.
7. Select [Media] > [DVD Drive] > [Insert Disk].

8. Select the copied ISO format file of the ProSafe-RS software medium and click [Open].
er.exe in the top folder of the ISO format file of the ProSafe-RS software.
11. Click [OK].
• Do not click [Don’t Install] on the Windows Security dialog box. If clicked, an error occurs.
l Procedure 3: Set the Domain Number and Station Number Managed by the
Vnet/IP Interface Package
When the installation of the Vnet/IP Interface Package is complete, the Vnet/IP Interface Man-
agement Tool appears. Using this tool, set the domain number and station number that will be
managed by the Vnet/IP Interface Package. Follow these steps to set the domain number and
station number.
TIP You can also set the domain number and station number managed by the Vnet/IP Interface Package later.
You must restart the virtual machine to reflect the settings.
1. Open the Settings tab of the Vnet/IP Interface Management Tool.

2. Set the domain number in [Domain No] and the station number in [Station No], and then
click [Save].
TIP You can set a number in the range from 1 to 31 as the domain number (1 to 16 in the case of CENTUM inte-
gration), and from 1 to 64 as the station number. If both domain number and station number are set to 0,
Vnet/IP communication is disabled and communication to the control network is not possible.
On a virtual machine where you run an FCS simulator that can be operated through remote connection from
another HIS by installing the Expanded Test Functions and SCS Simulator Package, set both the domain
number and the station number to 0.
Note that the license of Vnet/IP Interface Package is not required when using only the test function with the
domain number and the station number set to 0.
3. Click [CLOSE], and restart the virtual machine.

SEE
ALSO For more information about Vnet/IP interface management tool, refer to:
“n Changing the Domain Number and Station Number” on page App.3-1

l Procedure 4: Activate License of the Vnet/IP Interface Package

Before you can use the Vnet/IP Interface Package, you must activate the license for the pack-
age. After installing the ProSafe-RS software, distribute and accept the license of the Vnet/IP
Interface Package.

B3.3.4 Configuring Windows Network Settings

You must configure the Windows network settings after installing the network driver.
This section explains the procedures for configuring Windows network settings related to con-
trol bus, Vnet/IP open communication, and Ethernet.
n Cautions on Cable Wiring

When the cable is wired for network connection, the Set Network Location dialog box may ap-
pear.
TIP In Windows 10 and Windows Server 2016, a network charm bar may appear.
SEE
ALSO For more information about the Set Network Location dialog box and network charm bar, refer to:
C7.2.1, “Precaution on Network Cable Connection” on page C7-4
n Checking the Card for Control Bus

Check the card for control bus that is installed on the computer.
l When a Control Bus Interface Card is Installed

In a system using V net, a control bus interface card is installed in computers. In this case,
configure Windows network settings for control bus communications and Ethernet communi-
cations.
l When a Vnet/IP Interface Card is Installed

In a system using Vnet/IP, a Vnet/IP interface card is installed in computers.
In this case, a combination of either control bus communications and Ethernet communica-
tions or control bus communications and Vnet/IP open communications is used. Configure the
Windows network settings according to the network configuration of the system.
TIP The Vnet/IP open communication refers to Ethernet communication performed on bus 2 of Vnet/IP.
In a system using Vnet/IP open communications, bus 1 is normally used for control bus communications and
bus 2 is used for Ethernet communications. If bus 1 fails, bus 2 is used for both control bus communications
and Ethernet communications.
n Vnet/IP Network Configurations and Windows Network Settings

Vnet/IP network configurations and their required Windows network settings are describes as
follows.

Ethernet
(Ethernet communication)
172.17.1.64 172.17.1.63 172.17.1.62
E E E
Computer 1 Computer 2 Computer 3
IP IP
192.168.1.128 192.168.1.126
Vnet/IP
Bus 1 (Control communication)
192.168.129.128 192.168.129.126
E: Ethernet Interface Card or Onboard NIC

IP: Vnet/IP Interface Card
Figure B3.3.4-1 Network Configuration and Interface (Vnet/IP and Ethernet are Installed)
Computer 1 Computer 2 Computer 3
IP IP IP
192.168.1.128 192.168.1.126 192.168.1.124
192.168.129.128 192.168.129.126 192.168.129.124
Vnet/IP
Bus 2 (Vnet/IP open communication)
IP: Vnet/IP Interface Card
Figure B3.3.4-2 Network Configuration and Interface (Only Vnet/IP is Installed)
Table B3.3.4-1 Network Configurations and Network Connections to be Set Up on Windows

Network connection to be set up on
Network Configuration Computer (Example in the figures)
Windows
Connected to Vnet/IP and Ethernet Control bus, Ethernet, and Vnet/IP open
(Computers 1 and 2) communications(*1)
Vnet/IP + Ethernet
Connected to Ethernet only (Com-
Ethernet communications
puter 3)
Connected to Vnet/IP (Ethernet
Control bus, Ethernet, and Vnet/IP open
Vnet/IP only communication on bus 2) (Comput-
communications(*2)
ers 1 to 3)
*1: After installing the Vnet/IP open communication driver, you need to disable the corresponding device.
*2: You need to disable the Ethernet device.
SEE
ALSO For more information about network construction when using Vnet/IP open communication, refer to:
Vnet/IP Network Construction Guide (Legacy Edition) (TI 30A10A10-01E)
n Cautions on Using Vnet/IP

On the computers connected on Vnet/IP, you need to disable the unused devices according to
the network configuration.

l When Vnet/IP and Ethernet are Installed
IMPORTANT
In a system where both Vnet/IP and Ethernet are Installed, Vnet/IP open communications are
not used. Even in this case, you need to install the Vnet/IP open communication driver and
disable the driver on computers installed with a Vnet/IP interface card.
Ethernet
172.17.1.62
Vnet/IP
Vnet/IP
Disable Vnet/IP open communication
Figure B3.3.4-3 When Vnet/IP and Ethernet are Installed
On a computer installed with a Vnet/IP interface card, follow these steps to disable the
Vnet/IP Open communication driver:
3. Select [System and Security] > [System] > [Device Manager].
Device Manager appears.
4. Unfold Network adapters.
5. Select [Vnet/IP Open Communication Driver (BUS2)] and then click the Disable button on
the toolbar.

[Disable] button
Figure B3.3.4-4 Disabling the Vnet/IP Open Communication Device
l When Only Vnet/IP is Installed

Disable Ethernet
Vnet/IP
Vnet/IP
Figure B3.3.4-5 When Only Vnet/IP is Installed
On a computer in a system where only Vnet/IP is installed, follow these steps to disable the
Ethernet device:
Device Manager appears.
4. Unfold Network adapters.
5. Select the Ethernet device and then click the Disable button on the toolbar.
n Prohibitions
Do not use the following features in ProSafe-RS.
• Internet Connection Sharing (ICS)
• Bridge Connection
• Homegroup

l Internet Connection Sharing (ICS)

Do not select the [Allow other network users to connect through this computer’s Internet con-
nection] check box on the Sharing tab in the properties dialog box for V net, VnetIPOpen, or
Ethernet (these connection names are set in the procedures described later).
TIP Internet Connection Sharing (ICS) is for sharing the internet connection by the computers in a small scale
office network or home network.
l Bridge Connection
Do not use bridge connection. If bridge connection is created in the computer, not only the
control bus communication of the computer becomes abnormal, but also the communication
of the whole control bus network may be jeopardized. (If the bridge connection is already cre-
ated, you need to delete the bridge connection.)
l Homegroup (Windows 10)

In a ProSafe-RS system, folders and printers are shared by using the file sharing function for
the workgroup/network environment as with the earlier RS versions. For this reason, select
[No] on the network charm bar.
n Procedure 1: Rename Local Area Connections

A network after the installation is named “Local Area Connection.” The network can be identi-
fied more easily if you rename the local area connection.
Rename the local area connections as necessary according to the network configuration of
the system.
2. Select [Network and Internet] > [Network and Sharing Center].
The Network and Sharing Center window appears.
3. Select [Change adapter settings].
The Network Connections window appears.
TIP If connections are not displayed here, the corresponding installations have failed or the drivers are not work-
ing properly. Address the issues so that the connections are displayed here.
4. Right-click each of the Local Area Connection icons and select [Rename] to change the
name.
Table B3.3.4-2 Renaming of Network Connections

Display on Network Connections win-
Network type Name
dow
Ethernet Ethernet driver names Ethernet
Control bus Yokogawa Vnet Adapter Vnet
Vnet/IP Open Communication Driver
Vnet/IP open communication VnetIPOpen
(BUS2)

Figure B3.3.4-6 Network Connections – V net Network (After Renaming)
Figure B3.3.4-7 Network Connections – Vnet/IP Network (After Renaming)
TIP In the instruction manuals until ProSafe-RS R2.03, it is instructed to change the name of control bus commu-
nication connection when Vnet/IP is used to “VnetIP” rather than “Vnet.”
SEE
ALSO For more information about the network settings for a virtual machine, refer to:
B3.4, “Notes on Using a Virtual Machine” on page B3-38
n Procedure 2: Configure Properties

In the properties of each type of network connection, you need to configure the items to be
used.
Configure the properties as necessary according to the network configuration of the system.
Table B3.3.4-3 List of Items Used for Network Connections

Usage of the item (*1)
Item
Ethernet VnetIPOpen Vnet
Client for Microsoft networks Yes Yes No
QoS packet scheduler Yes Yes No
File and printer sharing for Microsoft networks Yes Yes No
Microsoft Network Adapter Multiplexor Protocol
No No No
(*2)
Microsoft LLDP Protocol Driver
Yes Yes No
(*2)
Yokogawa Vnet Protocol No No Yes
Continues on the next page

Table B3.3.4-3 List of Items Used for Network Connections (Table continued)
Item
Ethernet VnetIPOpen Vnet
Internet protocol version 6 (TCP/IPv6) No No No
Internet protocol version 4 (TCP/IPv4) Yes Yes Yes
Link-Layer Topology Discovery Mapper I/O Driver Yes Yes No
Link-Layer Topology Discovery Responder Yes Yes No
*1: Yes: Select the check box, No: Clear the check box
*2: Windows 10, Windows Server 2016
TIP Items in the table, except “Yokogawa Vnet Protocol,” are installed during the Windows OS installation.
SEE
ALSO For more information about how to set the network adapters of the virtual machine, refer to:
“n Configure Properties” on page B3-38
l V net Properties
1. In the Network Connections window, right-click [Vnet] and select [Properties].
The Vnet Properties dialog box appears.
2. Configure Vnet according to “Table List of Items Used for Network Connections.”
3. After the setting is complete, click [OK].
l VnetIPOpen Properties
1. In the Network Connections window, right-click [VnetIPOpen] and select [Properties].
The VnetIPOpen Properties dialog box appears.
2. Configure VnetIPOpen according to “Table List of Items Used for Network Connections.”
l Ethernet Properties
1. In the Network Connections window, right-click [Ethernet] and select [Properties].
The Ethernet Properties dialog box appears.
2. Configure the Ethernet according to “Table List of Items Used for Network Connections.”
n Procedure 3: Set IP Addresses

On Windows, DHCP is enabled by default after a network driver is installed. However, since
ProSafe-RS does not use DHCP, you need to set IP addresses. You need to set IP addresses
also when the system is used in the domain environment. Set the IP addresses according to
the network configuration of the system.
SEE
ALSO For more information about how to set IP addresses of the virtual machine, refer to:
“n Set IP Addresses” on page B3-39
l Setting IP Address for Vnet

1. In the Network Connections window, right-click the Vnet icon and select [Properties].
The Vnet Properties dialog box appears.
2. Select [Internet Protocol Version 4 (TCP/Ipv4)] and click [Properties].

The Internet Protocol Version 4(TCP/Ipv4) Properties dialog box appears.
3. Select [Use the following IP address] and set the IP address, subnet mask, and default
gateway. Set the IP address to a standard value that is determined based on the station
address of the computer as long as there is no special reason.
TIP The standard values for Vnet are as follows:
IP address: 172.16.Domain Number.Station Number(*1)

Subnet Mask: 255.255.0.0
Default gateway: No setting is required.
*1: If the network address overlaps with the network address of the existing environment, you can use an address other than
172.16.
4. After the setting is complete, click [OK]. You do not need to restart the computer.
l IP Address for VnetIPOpen

This setting is not required when Vnet/IP is used together with Ethernet.
1. In the Network Connections window, right-click the VnetIPOpen icon and select [Proper-
ties].
The VnetIPOpen Properties dialog box appears.
2. Select [Internet Protocol Version 4 (TCP/IPv4)] and click the [Properties].
The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box appears.
3. Select [Use the following IP address] and specify the following values for the IP address,
subnet mask, and default gateway.
• If the computer is to be used in an existing environment, specify the values used in
that network environment.
• If the computer is to be used in a new environment, specify the standard values de-
termined based on the station address.
TIP The standard values for VnetIPOpen are as follows:
IP address: 192.168.<128 + domain number>.<129 + station number>(*1)

Subnet Mask: 255.255.255.0
Default gateway: Specify the IP address of L3SW if another Vnet/IP domain exists
*1: Normally, use a standard value. However, you can also use other address.
l Setting IP Address for Ethernet

1. In the Network Connections window, right-click the Ethernet icon and select [Properties].
The Ethernet Properties dialog box appears.
2. Select [Internet Protocol Version 4(TCP/IPv4)] and then click [Properties].
The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box appears.
3. Select [Use the following IP address] and set the IP address, subnet mask, and default
gateway for Ethernet as follows:
• If the computer is to be used in an existing environment, specify the values used in
that network environment.
• If the computer is to be used in a new environment, specify the standard values de-
termined based on the station address.

TIP The standard values for Ethernet are as follows:
IP address: 172.17.Domain Number.Station Number(*1)

Subnet Mask: 255.255.0.0
Default gateway: No setting is required.
*1: Normally, use a standard value. However, you can also use other address.
IMPORTANT
• In workgroup environment, do not change the settings for DNS server address and the
settings accessed by clicking [Advanced].
• In Windows domain environment, you need to set the DNS server address according to
the settings of Windows domain server.
n Setup Procedure 4: Change Computer Name

It is recommended to set the station names used in the ProSafe-RS system as the computer
names.
2. Select [System and Security] > [System] > [Advanced system settings].
3. In the Computer Name tab, click [Change].
The Computer Name/Domain Changes dialog box appears.
4. Enter the station name as the new computer name (case-insensitive) for the computer.
Figure B3.3.4-8 Computer Name/Domain Changes Dialog Box
5. Click [OK].

A message box appears to prompt for restarting the computer.
n Procedure 5: Repair TCP/IP Settings

Before you install the ProSafe-RS software, run the TCP/IP Inconsistency Detect Tool. If any
inconsistency is found, use the TCP/IP Inconsistency Repair Tool and configure the TCP/IP
settings again.
TIP On a computer where the control bus driver or Vnet/IP open communication driver had ever been uninstalled,
the TCP/IPv4 network settings of IP addresses, subnet masks, and default gateway addresses may be lost
every time the computer is restarted. This problem is caused by errors of the Windows OS.
l Running the TCP/IP Inconsistency Detect Tool

1. Use Windows Explorer to open the TOOLS directory under the following path in the
ProSafe-RS software medium.
(Drive of ProSafe-RS software medium):\ProSafe-RS\TOOLS
TIP TCP/IP Inconsistency Detect Tool is installed in the following folder when you install the ProSafe-RS software:
(ProSafe-RS Installation Folder)\ProSafe-RS\YOKOGAWA\net\tool
2. Right-click [TcpipInconsistencyDetector.cmd], and select [Run as administrator] from the

context menu.
Messages are displayed according to the inconsistencies detected.
3. Click [OK] to end the tool.
If no inconsistency is detected, the computer can be connected on the network normally.
If no inconsistency is detected, the Windows system continues to work but the network con-
nection may not. You need to use the TCP/IP Inconsistency Repair Tool and then configure
the TCP/IP network settings again.
l Running TCP/IP Inconsistency Repair Tool
IMPORTANT
TCP/IP Inconsistency Repair Tool resets the TCP/IP settings of all the network interface cards
that are installed in the computer. Therefore, before you run the TCP/IP Inconsistency Repair
Tool, you need to write down or save the current settings of the following TCP/IPv4 informa-
tion for every network interface card:
• IP Address
• Subnet Mask
• Default Gateway
1. Use Windows Explorer to open the TOOLS directory under the following path in the
ProSafe-RS software medium.
(Drive of ProSafe-RS software medium):\ProSafe-RS\TOOLS
TIP TCP/IP Inconsistency Repair Tool is installed in the following folder when you install the ProSafe-RS soft-
ware:
(ProSafe-RS Installation Folder)\ProSafe-RS\YOKOGAWA\net\tool

2. Right-click [TcpipInconsistencyRepair.cmd], and select [Run as administrator] from the
context menu.
Messages are displayed according to the inconsistencies detected.
3. If no inconsistency is detected in the network settings, click [OK] to end the tool.
The computer can be connected on the network normally.
4. If any inconsistency is detected, click [Yes]
The network settings are reset and a message appears, prompting you to restart the
computer.
5. Click [Yes] to restart the computer.
6. After the computer is restarted, re-configure the settings on the Internet Protocol Version
4 (TCP/IPv4) Properties windows for all the network interface cards.

<B3.4 Notes on Using a Virtual Machine> B3-38
B3.4 Notes on Using a Virtual Machine

When using a virtual machine, in addition to the control bus and Ethernet, you must configure
the control network (Vnet/IP) and the remote UI network settings.
n Rename Local Area Connections

Set the name of the local area connection of the virtual machine as follows.
Table B3.4-1 Renaming of Network Connections

Display on Network Connections win-
Network type Name
dow (*1)
Control bus Yokogawa Vnet Adapter Vnet
Ethernet Microsoft Hyper-V Network Adapter #n Ethernet
Control network 1 Microsoft Hyper-V Network Adapter #n VnetIPBUS1 (*2)
Control network 2 Microsoft Hyper-V Network Adapter #n VnetIPBUS2 (*2)
Remote UI network Microsoft Hyper-V Network Adapter #n RemoteUINetwork
*1: These are the default names, where n = 1, 2, ...., which means the virtual NIC number.
*2: Be sure to set these names. The names are not case-sensitive.
l Confirming the Network Type

Follow these steps to confirm the network type:
1. In the Network Connections window, right-click on a network and select [Properties].
2. Open the Network tab, and click [Configure].
3. Open the Advanced tab and confirm the Value that is displayed when you select Hyper-V
Network Adapter Name in Properties.
The device name that was set when the virtual machine was built is displayed.
TIP For the Value that you confirm in the step 3, contact to the engineer who configured the virtual machine.
n Configure Properties
In the properties of each type of network connection, you need to configure the items to be
used. Configure the properties as shown in the following table.
Table B3.4-2 List of Items Used for Network Connections

Item Control Control Control Remote UI
Ethernet
bus network 1 network 2 network
Client for Microsoft Networks No Yes No No Yes
QoS Packet Scheduler No Yes No No Yes
File and Printer Sharing for Microsoft Networks No Yes No No No
Microsoft Network Adapter Multiplexor Protocol No No No No No
Microsoft LLDP Protocol Driver No Yes No No Yes
Yokogawa Vnet Protocol Yes (*2) No No No No
Internet protocol version 6 (TCP/IPv6) No No No No No
Internet protocol version 4 (TCP/IPv4) Yes Yes Yes Yes Yes
Link-Layer Topology Discovery Mapper I/O
No Yes No No Yes
Driver

<B3.4 Notes on Using a Virtual Machine> B3-39
Table B3.4-2 List of Items Used for Network Connections (Table continued)
Item Control Control Control Remote UI
Ethernet
bus network 1 network 2 network
Link-Layer Topology Discovery Responder No Yes No No Yes
*1: Yes: Select the check box, No: Clear the check box
*2: Do not clear the check box for “Yokogawa Vnet Protocol.”
n Set IP Addresses
You do not need to set the IP address, subnet mask, and default gateway for the control net-
work. They are automatically set by the Vnet/IP Interface Management Tool based on the set-
tings values of the domain number and station number managed by the Vnet/IP Interface
Package.
For the control bus, Ethernet, and remote UI network, it is recommended to set the IP ad-
dress, subnet mask, and default gateway to the following values.
Table B3.4-3 IP Address

Control bus Ethernet Remote UI network
IP Address 172.16. Domain number. 172.17. Domain number. 172.18. Domain number.
Station number Station number Station number
Subnet Mask 255.255.0.0 255.255.0.0 255.255.0.0
Default gateway No setting is required. No setting is required. No setting is required.
If the existing environment and network addresses overlap, IP addresses other than the rec-
ommended values can be used for the control bus, Ethernet, and remote UI network. Howev-
er, you cannot set the address 192.168.xx.yy to the IP address of the control bus, Ethernet, or
remote UI network. If you do, communication to the control network is impossible.

<B3.5 Installing the ProSafe-RS Software> B3-40
B3.5 Installing the ProSafe-RS Software

This section describes how to install the ProSafe-RS software.
n Administrative User who Performs New Installation

When installing the ProSafe-RS software for the first time on a computer, the installation must
be performed by an administrative user who belongs to the group shown in the following ta-
ble.
The user who has installed the software is automatically added to the PSF_MAINTENANCE
group.
Table B3.5-1 Groups to Which the User Who Performs New Installation Belongs
Security model and user management type to be applied
Standard model
Legacy model Standalone management/linked Domain/Combination manage-
domain management ment
• Domain user who belongs to
the Domain Admins domain
group
Local user who belongs to the Ad- Local user who belongs to the Ad- • Domain user who belongs to
ministrators local group ministrators local group the Administrators local group
• Local user who belongs to the
Administrators local group(*1)
(*2)
*1: The domain user name and password must be entered during installation.
*2: When this user applies IT security and uses iDefine interface package, the following steps must be performed as a domain
user who belongs to the Domain Admins domain group or as a domain user who belongs to the Administrators local group.
1. Run the 32 bit Command Prompt (%SystemDrive%\Windows\SysWOW64\cmd.exe) as Administrator.
2. Run either of the following batch files appropriate to the user management type.
%ProgramFiles(x86)%\YOKOGAWA\IA\iPCS\Platform\Security\Program
For Domain management: PSF_SetupSMSvcHostConfigDOM.cmd
For Combination management: PSF_SetupSMSvcHostConfigCMB.cmd
TIP If the user management type is Domain or Combination management, install the software after the computer
is added to the domain.
Follow these steps to install the ProSafe-RS software:
2. Terminate all running applications, including resident programs such as anti-virus soft-
ware.

Figure B3.5-1 Installation Menu
4. Click [ProSafe-RS Software] in the installation menu.

5. If a dialog box appears, confirming to install Windows redistributable modules, click [In-
stall].
TIP This dialog box appears when the Windows redistributable modules required to run ProSafe-RS are not al-
ready installed.
The following modules are necessary for ProSafe-RS:
• Microsoft .NET Framework 4.7.2
• Microsoft Visual C++ 2017 Redistributable Package
• Microsoft Visual C++ 2008 Redistributable Package
• Microsoft Access Database Engine 2016
If you click [Cancel], the installation of the ProSafe-RS software is discontinued.
Restarting the computer may be required after installing the modules. If required, restart the computer and
then continue the ProSafe-RS installation.
Installation starts.
6. After the installation is completed, click [Close].

The window closes.
IMPORTANT
If Microsoft Access Database Engine 2016 cannot be installed due to cancellation during in-
stallation of the redistributable module, an error occurs. In that case, click [OK]. To continue
the installation, install ProSafe-RS again.
7. If the following dialog box appears, restart the computer and log on again using the same
user account.

Figure B3.5-2 User Rights Setting Confirmation Dialog Box
TIP Restarting the computer here grants the currently logged on user the rights required to perform the subse-
quent installation tasks.
Installation of the ProSafe-RS software starts and the Welcome dialog box appears.
8. Click [Next].
A dialog box for entering user information and the installation folder appears.
Figure B3.5-3 User Information Dialog Box
TIP • If a different version of control bus driver or Vnet/IP open communication driver is already installed, a
dialog box appears, prompting you to update the driver. Confirm the message and click [OK]. To update
the control bus driver, uninstall the existing driver and then install the new one after you install the
ProSafe-RS software. To update the Vnet/IP open communication driver, install the new driver after you
install the ProSafe-RS software.
• After updating the Vnet/IP open communication driver, disable the driver if the computer is to be connec-
ted to Ethernet.
9. Enter the user name and company name. It is recommended not to change the installa-
tion folder from the default location.
TIP • The user name and company name must be set within 100 characters.
• If you want to change the installation folder, click [Browse] and specify a new location within 50 charac-
ters.
• The language is determined automatically by the system language: if the system language is Japanese,
the Japanese version software is installed, otherwise, the an English version is installed.

10. Click [Next].
The Confirm Settings dialog box appears.
11. Confirm that the installation settings are correct, and click [Install].
Installation of the ProSafe-RS software is started.
12. When the installation complete dialog box appears, perform either of the following opera-
tions.
• If you install only ProSafe-RS, select [Yes, I want to set up IT security now.] and click
[Finish]. The IT Security Tool then starts.
• If you install another YOKOGAWA product, select [No, I want to install other software
products.] and click [Finish] to complete the installation.
nn.nn
Revision of
ProSafe-RS
Figure B3.5-4 Installation Completed Dialog Box
IMPORTANT
After you have installed other YOKOGAWA products, be sure to run the IT Security Tool to
configure IT security settings. The settings on the IT Security Tool will be valid to all the instal-
led products.
If you do not configure IT security settings, the products will not function properly.
SEE
ALSO For more information about configuring the IT security settings, refer to:

<B3.6 Configuring IT Security Settings> B3-44
B3.6 Configuring IT Security Settings

After installing the ProSafe-RS software, you need to configure settings to strengthen Win-
dows IT security.
To configure IT security for linked domain management, use IT Security Tool and Domain Link
Management Tool. For user management types other than linked domain management, use
IT Security Tool to configure IT security settings.
IMPORTANT
• The security model of IT security settings must be consistent in the entire system. Ensure
that the user management type is unified to either standalone management or manage-
ment using a domain controller. You can mix computers in domain management, combi-
nation management, or linked domain management.
• If you select the Legacy model, restrictions related to Windows are in effect in some envi-
ronments. For that reason, we recommend you select the Standard model.
• If you operate the computer in the Standard model with linked domain management, ap-
ply IT security settings for the Standard model with standalone management. Next, join
the computer to the domain and set with Domain Link Management Tool.
• If the computer contains YOKOGAWA products that do not support linked domain man-
agement and you use the installed YOKOGAWA product in a domain environment, set
the user management type to domain management or combination management with IT
Security Tool.
• If you have changed any security settings from their default values, always save the se-
curity settings by using the Save function of the IT Security Tool to enable security set-
tings to be restored at computer failure.
• After you have activated the license of the SOE OPC Interface Package, be sure to run
the IT Security Tool from the Start menu.
• Security settings customized by other than the IT Security Tool are overwritten with the
setting information held by the IT Security Tool when the IT Security Tool is run. If you
want to use the same security settings as before running the IT Security Tool, customize
them again after running the IT Security Tool.
Note that upgrading will run the IT Security Tool and overwrite the security settings.
TIP Even when a domain controller is used to perform consolidated management of IT security settings, be sure
to set IT security on each client. After setting IT security on all clients, use the domain controller to set up
consolidated management of IT security settings.
SEE
ALSO For more information about precautions for coexistence with other YOKOGAWA product, refer to:
B3.6.2, “Precautions for Coexistence with Other Product” on page B3-50
For more information about details of the IT security settings, refer to:
6.1, “IT Security Tool” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
For more information about the procedure for performing consolidated management of IT security settings
with a domain controller, refer to:
6.10, “Active Directory-Based Consolidated Management of IT Security Settings” in ProSafe-RS Security
Guide (IM 32P01C70-01EN)

B3.6.1 Running the IT Security Tool

This section describes the procedure for configuring the IT security settings following the
completion of ProSafe-RS software installation.
IMPORTANT
If the following YOKOGAWA products have been installed and they do not support IT security
version 2.0, the selection of IT security version 1.0 cannot be changed.
• CENTUM VP
• PRM
If they support IT security version 2.0, the IT security version can be kept or changed.
Follow these steps to run the IT Security Tool:

1. When the ProSafe-RS software installation is complete, a dialog box appears. Select
[Yes, I want to set up IT security now.] and click [Finish].
nn.nn
Revision of
ProSafe-RS
Figure B3.6.1-1 ProSafe-RS Setup Dialog Box (Completed)

TIP If you are intending to select [No, I want to install other software products.] after the completion of installation,
install other software products, and then run the IT Security Tool, start the IT Security Tool from the Start
menu and click [Settings] on the menu.

TIP The text To use linked domain management, configure it and then link the domain below Standalone Manage-
ment is displayed when all of YOKOGAWA system products installed on the computer support the linked do-
main management.
Figure B3.6.1-2 IT Security Tool (Setup)
3. In the Select security model section, select either [Standard Model] or [Legacy Model].
TIP If you select [2.0] for Select IT security version, only the [Standard model] can be selected.
4. In the Select user management section, select [Domain Management], [Combination

Management], or [Standalone Management].
TIP • When you select the Legacy model, you cannot change the user management type from Standalone
management.
• When operating with linked domain management, select the standalone management in the Standard
model.
• If you select [Standalone Management] on a Windows domain member computer, a confirmation mes-
sage is displayed. You can go on by clicking [OK].
5. If you do not need to configure the individual setting items, click [Next]. IT security setting
starts. When the setup is complete, the Setup Completed page appears. If there is any
setting items that have failed, the failed items are displayed. To reconfigure the individual
setting items, perform the following steps.
TIP If IT security version 2.0 is selected, a confirmation dialog box appears. To apply the current settings, click
[Yes].
a. To reconfigure the individual setting items, click [Details].

The Select Setting Items page appears.

Figure B3.6.1-3 Select Setting Items Page (When IT Security Version 2.0 Is Selected)
b. Select or clear the check boxes of the items you want to change.
Under [Current Value], the value currently set for the applicable setting item is dis-
played according to the following table.
IMPORTANT
The group policy settings that were distributed from the domain controller are not displayed.
Local group policy settings are displayed.
Table B3.6.1-1 Content displayed in Current Value

Content displayed Description
Actual value The value actually set is displayed. For example, Enabled, Disabled,
30, 0, etc., is displayed. (*1)
[Not defined] This is displayed for a setting item relating to security options, for which
no value is set.
[Not configured] This is displayed for a setting item for the group policy management
template, for which no value is set.
[Not applied] This is displayed for a setting item that takes multiple values, for which
IT security has never been applied.
[Applied] This is displayed for a setting item that takes multiple values, for which
IT security has been applied at least once.
*1: Even when the set value is a character string in the Security Policy window, it may be managed as a value in the OS, in which
case the value is displayed.
TIP It is recommended not to change the settings when the Standard model is selected.
c. Click [Next].

Figure B3.6.1-4 Confirm Setting Information Page (When IT Security Version 2.0 Is Selected)
TIP If the settings specified are different from the default values of the security model, a warning dialog box ap-
pears.
To apply the current settings, click [Yes]. If you click [No], you will return to the Select Setting Items page.
d. Confirm the settings and click [Next].

TIP If this tool was used in the past to configure security settings without opening the Select Setting Items page,
the last configured IT security settings are applied. If these settings and the default settings of the selected
security model do not match, a warning dialog box appears.
To apply the current settings, click [Yes]. If you click [No], you will return to the IT Security Settings page.
When the setup is complete, the Setup Completed page appears. If there is any set-
ting items that have failed, the failed items are displayed.
6. Select the [Restart now] check box and click [Finish].
The IT Security Tool is exited and the computer is restarted automatically.
IMPORTANT
If any setup failures are displayed, contact YOKOGAWA Service.
TIP The "Program Compatibility Assistant" dialog box may appear after the security settings configuration is com-
pleted. Even when this dialog box appears, the settings have been configured successfully, so click [Cancel]
to close it.

SEE
ALSO For more information about the procedure for importing the IT security settings, refer to:
32P01C70-01EN)
For more information about changing the IT security settings, refer to:
n Notes on the Case when NetBIOS over TCP/IP is Disabled

When the Standard model is selected, you can configure to disable NetBIOS over TCP/IP.
With domain management, combination management, or linked domain management, Net-
BIOS over TCP/IP is disabled by default.
If it is disabled, you need to make the following settings for name solution.
• Standalone management
In the LMHOSTS file of each station, set the computer names of the stations it needs to
access.
Location of the LMHOSTS %Systemroot%\system32\drivers\etc
file:
%Systemroot% is the directory where the Windows OS is
installed. Usually, it is C:\Windows.
Example script in the The following is an example of accessing HIS0124.
LMHOSTS file:
########## lmhosts
172.17.1.24 HIS0124 #PRE
Table B3.6.1-2 LMHOSTS File Settings

Station type Stations to be set in the LMHOSTS file
License management station All license-assigned stations
• License management station
• Computer that holds project files
(File server computer; if integrated with CENTUM, computer that
License-assigned station
holds CENTUM project database)
• To use the Forced I/O Viewer function, the computer on which SCS
projects are saved and the computer which receives the distribution.
• Domain management, combination management, or linked domain management

In the DNS server, set the license management station and all the license-assigned sta-
tions.

B3.6.2 Precautions for Coexistence with Other Product

Precautions to be heeded when a YOKOGAWA product that supports IT security settings co-
exists on a ProSafe-RS computer are explained.
n Installing the ProSafe-RS Software After Installing Other Product

When installing the ProSafe-RS software after installing other product that does not support
IT security version 2.0, only IT security version 1.0 can be selected.
When installing the ProSafe-RS software after installing other product that supports IT securi-
ty version 2.0, the IT security version can be kept or changed.
n Installing Other Product After Installing the ProSafe-RS Software

If IT security Version 2.0 is set during the installation of the ProSafe-RS software and then IT
security settings are configured during the installation of other product that does not support
IT security version 2.0, the following warning dialog box will appear.
Figure B3.6.2-1 Warning Dialog Box
When changing to IT security version 1.0, continue configuring the IT security settings.
When changing to IT security version 2.0, close the IT security tool and uninstall other prod-
ucts, then re-install other products that are compatible with IT security version 2.0.

B3.6.3 Running Domain Link Management Tool

To configure IT security for linked domain management, use Domain Link Management Tool.
Adding the corresponding domain group to the members of the local group for the product in-
stalled on the computer by using the Domain Link Management Tool is called linking the do-
main. Conversely, deleting the domain group from the members of the local group is called
unlinking the domain.
IMPORTANT
• The domain can be linked if the following conditions are met.
• All of YOKOGAWA system products installed on the computer support the linked do-
main management.
• The IT security settings for standalone management are applied to the installed prod-
ucts with IT Security Tool.
• The computer is added to the Domain.
• You can link or unlink the domain for all of YOKOGAWA system products installed on the
computer at once.
• If you install another YOKOGAWA system products after linking domains, you must con-
figure security with IT Security Tool and link the domain. The same applies to upgrading
the revision or the version of the installed products.
SEE
ALSO For more information about how to add client computers to the domain, refer to:
For more information about notes on the case when NetBIOS over TCP/IP is disabled, refer to:
“n Notes on the Case when NetBIOS over TCP/IP is Disabled” on page B3-49
For more information about IT Security Tool, refer to:
6.1, “IT Security Tool” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
For more information about Domain Link Management Tool, refer to:
6.2, “Domain Link Management Tool” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
n Linking the domain with Domain Link Management Tool

Follow these steps to link the domain:
1. Sign in as a local user who belongs to both the Administrators group and PSF_MAINTE-
NANCE group of the local computer.
2. Start Domain Link Management Tool.

Figure B3.6.3-1 Domain Link Management Tool
3. In Domain Link Management Tool, select [Link] in the Select the link status section.
4. To change the recommended settings of NetBIOS over TCP/IP setting, perform the fol-
lowing step.
Clear the [Disabling NetBIOS over TCP/IP] check box.
TIP If the security model is set to Standard model with IT Security Tool, the setting of the Disabling NetBIOS over
TCP/IP check box is switched to the recommended settings in conjunction with the settings of the Select the
link status.
5. In Domain Link Management Tool, click [Execute].

The domain user authentication dialog box appears.
6. Enter the user name and password of the domain user and click [OK].
The corresponding domain group is added to the member of the local groups related to
the products installed on your computer. Also, NetBIOS over TCP/IP setting is configured.
TIP The user name and password that you enter in the domain user authentication dialog box do not have to be
those of the domain administrator.
7. In Domain Link Management Tool, click [Close].

The Domain Link Management Tool closes.
n Error messages and countermeasures

When attempting to link the domain, an error message will be displayed and the process will
not be performed depending on the conditions. Check the current status of the products in-
stalled on the computer and take necessary measures.
The following table describes the error messages and countermeasures when you cannot run
the process for linking domain.
Table B3.6.3-1 Error messages and countermeasures

the error messages Remedy
The computer is not joined to the do- Join the computer to the domain.
main.
This account information you entered is Domain user authentication has failed. Enter the correct account
incorrect. information.

Table B3.6.3-1 Error messages and countermeasures (Table continued)
the error messages Remedy
Any products that support linked do- All of YOKOGAWA system products installed on the computer
main management are not installed. must support the linked domain management. Perform either of
(*1) the following measures:
• Change the user management type to domain management or
The products that do not support linked combination management.
domain management are installed. • Uninstall the products that do not support linked domain man-
agement and link the domain.
IT security is not configured. (*1) With IT Security Tool, apply the security settings for standalone
management.
Linked domain management is not to Change to Standard model with standalone management.
be configured for the Legacy model
computer.
Standalone management is not ap- Change the user management type to standalone management.
plied.
Failed to connect to the domain con- Check the network settings and cabling between the computer and
troller. domain controller.
The group required for linked domain Create necessary domain group.
management does not exist in the do-
main.
*1: This error does not occur in Domain Link Management Tool for File Server.
SEE
ALSO For more information about how to add client computers to the domain, refer to:
For more information about installation of the product, refer to:
For more information about configuring network settings, refer to:
B3.3, “Configuring Network Settings” on page B3-18
For more information about how to create domain groups, refer to:
• B2.3, “Configuring Security Settings for the Domain Controller” on page B2-6
• B2.4, “Creating Domain Users” on page B2-13
For more information about how to configure IT security settings with IT Security Tool for the first time, refer
to:
For more information about the procedure for displaying the current status with Domain Link Management
Tool, refer to:
6.2, “Domain Link Management Tool” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
For more information about the procedure for changing the IT security settings, refer to:

<B3.7 Distributing and Accepting Licenses> B3-54
B3.7 Distributing and Accepting Licenses

Licenses are the rights to use ProSafe-RS software packages.
To make the installed software packages available for use, you need to distribute the licenses
from the license management station to license-assigned stations and accept the licenses on
each license-assigned station. This process of making software packages available for use is
called “activation of software packages.”
In a ProSafe-RS system, there is always one license management station and other stations
are license-assigned stations. The license management station can be set up on a computer
where SENG runs.
SEE
ALSO For more information about distributing and accepting licenses, refer to:

<B3.8 Creating User Accounts> B3-55
B3.8 Creating User Accounts

Create accounts for ProSafe-RS.
When the Standard model is selected in IT security configuration, rights to access the installa-
tion folder, registries, etc. are set by the IT Security Tool, based on the access rights granted
to the ProSafe-RS user groups. Therefore, you need to register the created user as a mem-
ber of the appropriate ProSafe-RS user group according to the user's role, such as engineer
and maintenance personnel.
This section describes the procedures for the cases where the security settings of the Stand-
ard model with Standalone management or the Legacy model are applied.
When you create local user accounts for Standard model with linked domain management,
domain management, and combination management, create them in the same way as for
Standard model with standalone management. When you create domain user accounts for
Standard model with linked domain management, domain management, and combination
management, create them on the domain controller.
SEE
ALSO For more information about how to create domain user accounts, refer to:
B2.4, “Creating Domain Users” on page B2-13
n Limitation on User Account Names

• 20 characters at maximum.
• Space, tabs, and multi-byte characters such as half-width katakana and Chinese charac-
ters (kanji) cannot be used.
TIP When the Access Control and Operation History Management Package is used and Windows authentication
mode is specified, different limitations are applied.
SEE
ALSO For more information about the limitations on user account names when using Windows authentication mode
of the Access Control and Operation History Management Package, refer to:
“n Creating User Accounts in Windows Authentication Mode” on page B4-8

B3.8.1 When the Standard Model with Standalone

Management Security Settings are Applied
When the security settings of Standard model with Standalone management are applied, user
accounts should be created on each computer.
Follow these steps to create a user account:
1. Logon as an administrative user.
3. Select [System and Security] > [Administrative Tools] > [Computer Management].
The Computer Management window appears.
4. On the tree view in the left pane of the window, select [System Tools] > [Local Users and
Groups] > [Users].
5. Select [Action] > [New User].
The New User dialog box appears.
6. Add a user account. (The rest of the steps shows an example of adding a new user ac-
count, OPERATOR.)
7. Right-click the user you have created and select [Properties], and then click [Add] on the
Member of tab.
8. Select an appropriate user group for the created user and click [OK].
Figure B3.8.1-1 Select Groups
TIP A user who belongs to the administrative group (PSF_MAINTENANCE) must also be a member of the Ad-
ministrators group.
9. In the user properties dialog box, confirm that the group you selected has been added to
the Member of list.

B3.8.2 When the Legacy Model of Security Settings are

Applied
The procedure for creating user accounts is the same as that for creating user accounts on a
Standalone management computer. However, with the Legacy model, Windows groups
PSF_xxxx are not supported. So, there is no need to add the created users to these groups.
SEE
B3.8.1, “When the Standard Model with Standalone Management Security Settings are Applied” on page
B3-56

<B3.9 Configuring Windows Environment Settings for Each User> B3-58
B3.9 Configuring Windows Environment

Settings for Each User
After creating user accounts, configure the required Windows environment settings for each
user.

B3.9.1 Setting of items common to Windows 10 and

Windows Server 2016
This section describes how to set the items common to Windows 10 and Windows Server
2016.
n Showing Icons on the Task Tray

On license-assigned stations running Windows 10 or Windows Server 2016, you must set so
that the License Agent icon is always shown on the task tray.
1. Sign in using the user account for which the License Agent icon should be displayed.
3. Select [Appearance and Personalization] > [Taskbar and Navigation].
The Settings window appears.
4. Select [Select which icons appear on the taskbar] under [Notification area].
5. Set [Always show all icons in the notification area] to [Off], and set [License.Agent.Task-
Tray] to [On].
6. Click the [×] button to close the window.
n Display Properties
The procedure for setting the display properties is explained as follows.
1. Sign in using the user account for which to set display properties.
3. Select [Appearance and Personalization] > [Personalization].
The Personalization window appears.

Figure B3.9.1-1 Personalization Window
4. From Windows Default Themes, select [Windows].

5. Select [Desktop Background].
The Settings window appears.
Figure B3.9.1-2 Settings Window

6. From the Background drop-down list, select [Solid Colors] and select a desired back-
ground color.
7. Close the Settings window.
Return to the Personalization window
8. Select [Screen Saver].
The Screen Saver Settings dialog box appears.
Figure B3.9.1-3 Screen Saver Settings Dialog Box
9. From the Screen Saver drop-down list, select [(None)], and then click [OK].
n Stopping the Inactive Window Scrolling Function

In Windows 10 and Windows Server 2016, inactive windows can be scrolled with the mouse
wheel. Stop this function because it can cause malfunction of the system.
Follow these steps to stop the inactive window scrolling function:
1. Sign in with the user account for which to disable scrolling of inactive windows.
2. Open the Settings window.
3. Select [Devices].
4. In the left pane, select [Mouse & touchpad].
The Mouse page appears.

Figure B3.9.1-4 Mouse Page
5. Turn off [Scroll inactive windows when I hover over them].


B3.9.2 Setting of Items Specific to Windows 10

This section describes how to set the items specific to Windows 10.
n Suppressing Toast Notifications Regarding Windows Firewall

If your OS is Windows 10 Enterprise 2016 LTSB or Windows 10 IoT Enterprise 2016 LTSB
and the IT security model is Legacy model, suppress toast notifications regarding Windows
Firewall.
Follow these steps to suppress toast notifications:
TIP This setting is not required if the OS is Windows 10 Enterprise 2019 LTSC or Windows 10 IoT Enterprise
2019 LTSC and the IT security model is Legacy model.

3. Select [System and Security] > [Windows Firewall].
The Windows Firewall window appears.
4. In the left pane, click [Turn Windows Firewall on or off].
5. Select [Turn off Windows firewall] in the private network settings, public network settings,
and domain network settings. However, you need to configure the domain network set-
tings only in domain environments.
6. Click [OK].
7. Sign out and sign in again using the user account for which to turn off toast notifications
regarding Windows Firewall.
9. Select [System and Security] > [Security and Maintenance].
The Security and Maintenance window appears.
10. On the left pane, click [Change Security and Maintenance settings].
11. Clear the [Network firewall] check box under Security messages.
12. Click [OK].
TIP • If the [Network firewall] check box is grayed out, wait for a few minutes until it is enabled.
• If a toast notification [Turn on Windows firewall] appears, carry out the above procedure without clicking
the toast notification.
l Precautions when using Windows 10 Enterprise 2019 LTSC or Windows 10

IoT Enterprise 2019 LTSC
This section describes precautions when the OS is Windows 10 Enterprise 2019 LTSC or
Windows 10 IoT Enterprise 2019 LTSC and the IT security model is Legacy model.
• What to do when a toast notification regarding Windows Firewall appears
If a toast notification appears, close it. If you click the toast notification to open the Set-
tings window, close it without doing anything.
You cannot enable or disable Windows Firewall in the Settings window that opens when
you click the toast notification.
• How to check the firewall state
In Legacy model, the firewall is disabled in a proper state. You can check the firewall
state in the following ways.

On the left pane of the Local Group Policy Editor, open the properties of [Windows De-
fender Firewall with Advanced Security], the [Firewall state] is displayed as [Disabled].
Alternatively, in Control Panel, open [Windows Defender Firewall], and [Disabled] and
[Some settings are managed by your system administrator] are displayed.
TIP You can check the firewall state for the Standard model in the following ways.
On the left pane of the Local Group Policy Editor, open the properties of [Windows Defender Firewall with
Advanced Security], the [Firewall state] is displayed as [Not Configured].
Alternatively, in Control Panel, open [Windows Defender Firewall], and [Enabled] is displayed.

<B3.10 Configuring the Uninterruptible Power Supply (UPS) Service> B3-65
B3.10 Configuring the Uninterruptible Power

Supply (UPS) Service
You can install uninterruptible power supply (hereinafter referred to as UPS) software and
make various settings to protect data in the computer at power supply failures.
n UPS Software Setting

Specify the UPS battery operation time so that the computer can continue operation with the
UPS battery without shutting down even if a power supply error (for example, power interrup-
tion) occurs for a short period of time. Use several seconds as a guideline for setting the UPS
battery operation time.
TIP Although the UPS battery operation time can be set longer than several seconds, the computer should be
shut down at a power interruption of several seconds for safety reasons.
SEE
ALSO For more information about the UPS software that can coexist with ProSafe-RS, refer to:
“● Software that can coexist with ProSafe-RS” in “■ Software requirements for SENG” in A1.2, “Software
requirements” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

<B4. Configuring the Functions Specific to SENG> B4-1
B4. Configuring the Functions Specific

to SENG
This section describes how to configure the following settings for the functions specific to
SENG.
• Setting the manual browsing environment
• Settings of Project Database Folder
• Settings for Message Cache Tool
• Settings Required for OPC Communication
• Setup when Using the Access Control and Operation History Management Package

<B4.1 Setting the Manual Browsing Environment > B4-2
B4.1 Setting the Manual Browsing Environment

Configure Adobe Acrobat Reader to view the online manuals and the Help files for PROFI-
NET Configurator.
n Adobe Acrobat Reader Settings

In the Adobe Acrobat Reader settings, make sure that the [Open cross-document links in
same window] check box is selected.
• The [Open cross-document links in same window] check box can be displayed by select-
ing [Preferences] - [Documents] from the [Edit] menu of Adobe Acrobat Reader. You must
set this setting for each logon user.
n Copying the Help Files for PROFINET Configurator

The Help files for PROFINET Configurator are stored in the software medium of ProSafe-RS.
As the Help files are not installed automatically on the computer, copy them from the software
medium as necessary.
• Stored location
<Media drive of ProSafe-RS>:\ProSafe-RS\PDFFILE\PROFINET_Configurator\en\
• Help files
SYCONnet netFrame YOKOGAWA S2LP131.pdf
SYCONnet netDevice YOKOGAWA S2LP131.pdf
PROFINET IO Controller YOKOGAWA S2LP131 DTM.pdf
YOKOGAWA PROFINET IO Generic Device DTM.pdf

<B4.2 Settings of Project Database Folder> B4-3
B4.2 Settings of Project Database Folder

This section explains the procedure for strengthening the security of project databases.
n Strengthening the Security of the Project Database on SENG PC

When ProSafe-RS software is installed, C:\RS-Projects folder is automatically created as the
default location for saving project data. By running the IT Security Tool after the installation,
security reinforcement is done for this default folder.
Shown below is the procedure for reinforcing security when you place the project database in
a location other than the default folder on an SENG PC and have it shared with other comput-
ers.
1. Create a new folder for storing project data.
2. Log on as an administrative user belonging to the PSF_MAINTENANCE group and as-
sign the share name RS-Projects to a folder to which the project database is to be stored.
3. Grant full control access permissions to Everyone.
4. Launch the IT Security Tool from the Start menu and configure security settings without
changing the security model and user management type.
n Strengthening the Security of Version Control Tool's Check-in

Folder
If you place the Version Control Tool's check-in folder on an SENG PC, follow these steps to
strengthen the security of the folder.
1. Create a new folder for use as the check-in folder of Version Control Tool.
2. Log on as an administrative user belonging to the PSF_MAINTENANCE group and as-
sign the share name RS-Share to the check-in folder.
3. If the folder should be shared with other computers, grant full control access permissions
to Everyone.
4. Launch the IT Security Tool from the Start menu and configure security settings without
changing the security model and user management type.

<B4.3 Settings for Message Cache Tool > B4-4
B4.3 Settings for Message Cache Tool

If you want to check the status of data collection by other stations using the Message Cache
Tool, the following setups are required.
n On Workgroup Member Computers

1. Create a user account on the station whose status of data collection shall be checked.
The user account name and password should be the same as the user account of the
computer that uses the Message Cache Tool.
2. Make the created user account created in step 1 belong to the PSF_ENGINEER user
group.
n On Windows Domain Member Computers

Register users of the Message Cache Tool to the PSF_ENGINEER user group.

<B4.4 Settings Required to Use the Forced I/O Viewer Function> B4-5
B4.4 Settings Required to Use the Forced I/O

Viewer Function
To use the Forced I/O Viewer function, settings must be made on the computer where SCS
projects are saved and the computer to which to distribute SCS projects.
n Setting on the Computer where SCS Projects are Saved

The Forced I/O Viewer Setup Tool acquires the SCS projects to be distributed to Forced I/O
Viewer from the computer in which the SCS projects are stored.
Follow these steps to set up the computer where SCS projects are saved:
1. Assign the share name RS-Projects to the upper folder of the RS project folder that con-
tains the SCS projects.
If the share name RS-Projects is assigned already, no setting is required.
2. Create a user account with the same user name and password as the user account that
uses the Forced I/O Viewer Setup Tool. If the IT security model is the Standard model,
add the created user account to the PSF_ENGINEER or PSF_MAINTENANCE group.
SEE
ALSO For more information about how to assign the share name RS-Projects, refer to:
“n Strengthening the Security of the Project Database on SENG PC” on page B4-3
n Settings on the Computer to which to Distribute SCS Projects

Follow these steps to set up the computers to which to distribute SCS projects, such as a
computer where Forced I/O Viewer will be used and SENG that shares the registration file:
1. Assign the share name RS-ForcedIO to the following folder:
<ProSafe-RS installation drive>:\Program Files (x86)\ProSafe-RS\YOKOGAWA\hmi\
ForcedIO
2. In the Share Permission of the share name RS-ForcedIO, grant full control access per-
missions to Everyone.
IMPORTANT
The share name is “RS-ForcedIO” with “RS-” added to the beginning of the folder name. It is
different from the folder name.
3. Create a user account with the same user name and password as the user account that
uses the Forced I/O Viewer Setup Tool. If the IT security model is the Standard model,
add the created user account to the PSF_ENGINEER or PSF_MAINTENANCE group.
4. If the IT security model is the Standard model, add the user account that uses the Forced
I/O Viewer to the PSF_OPERATOR group.

<B4.5 Settings Required for OPC Communication > B4-6
B4.5 Settings Required for OPC

Communication
This section describes how to make settings required to perform OPC communication when
the Standard model of IT security settings are selected on an SENG PC running the SOE
OPC Interface Package. If the Standard model of security settings is applied, access to
DCOM will be set. By this setting, only users belonging to ProSafe-RS user groups can ac-
cess the SOE OPC interface.
n Setting when Using Packages Performing OPC Communication with

SENG PC
When you are using packages (OPC clients) that perform OPC communication with SENG
PC (OPC servers), you must make the setting explained here.
l In the Case of Standalone Management or When Combination

Management is Applied on Some Computers
Perform the following procedure on an SENG PC performing OPC communication.
1. Create a program user of the OPC client package. Set the same user name and pass-
word as those on the client computer.
2. Make the created program user belong to the PSF_OPC user group.
l In the Case of Domain Management or When Combination Management is

Applied on All Computers
• In the case of package that can join the domain
1. Make a computer that runs the OPC client package join the domain.
2. Register the package program user to the domain and make it belong to the
PSF_OPC user group.
• In the case of package that cannot join the domain
Perform the following procedure on the SENG PC performing OPC communication.
1. Create a program user of the OPC client package. Set the same user name and
password as those on the computer running the package.
2. Make the created program user belong to the PSF_OPC_LCL user group.
SEE
ALSO For more information about the settings for a computer where the SOE OPC Interface Package and
CENTUM VP ExaOPC Interface Package coexist, refer to:
D1.1.4, “CENTUM VP Standard Operation and Monitoring Function and ProSafe-RS SOE OPC Interface
Package” on page D1-8
For more information about the settings for using Exaquantum as an OPC client, refer to:
D1.4.1, “ProSafe-RS SOE OPC Interface Package and Exaquantum PIMS Server” on page D1-27
l In the Case of Linked Domain Management

• In the case of package that can join the domain
1. Make a computer that runs the OPC client package join the domain.
2. Register the package program user to the domain and make it belong to the
PSF_OPC user group.
• In the case of package that cannot join the domain

<B4.5 Settings Required for OPC Communication > B4-7
Perform the following procedure on the SENG PC performing OPC communication.
1. Create a program user of the OPC client package. Set the same user name and
password as those on the computer running the package.
2. Make the created program user belong to the PSF_OPC user group.

<B4.6 Setup when Using the Access Control and Operation History Management Package > B4-8
B4.6 Setup when Using the Access Control and

Operation History Management Package
In ProSafe-RS R3.01 or later, it is possible to manage operation histories on SENG by using
the Access Control and Operation History Management Package. This section describes the
operations required to use this package.
SEE
ALSO For more information about the precautions to be followed when setting the access control/operation history
management function, refer to:
E., “Access Control/Operation History Management functions” in Engineer's Reference Manual (IM
32P04B10-01EN)
n Windows User Groups to which Administrators and Engineers

Belong
There are two types of personnel in a system where the access control and operation history
management is applied: “administrators of access control and operation history management”
(hereinafter referred to as “administrator” in this section) and “engineers.”
After creating user accounts for administrators and engineers, add them to the Windows user
groups shown in the following table.
Table B4.6-1 Windows User Groups to which Administrators and Engineers Must Belong
Personnel Windows user group to belong to
Standard or Strengthened model Legacy model
Administrator Either of the following: Group with administrator privilege
PSF_MAINTENANCE (*1)
PSF_MAINTENANCE_LCL (*1)
Engineer One of the following: Any group
PSF_OPERATOR
PSF_ENGINEER
PSF_OPERATOR_LCL
PSF_ENGINEER_LCL
*1: Users belonging to these groups must also have the Windows administrator privileges. Make them also belong to the Admin-
istrators or Domain Admins group.
n Security Model and User Authentication Mode

If you select the Standard model with the IT Security Tool, you can select either ProSafe au-
thentication mode or Windows authentication mode as the user authentication mode of the
operation history management function on SENG. By default, ProSafe authentication mode is
selected.
If you select the Legacy model with the IT Security Tool, only ProSafe authentication mode is
available.
You can configure user authentication modes by using the operation history management set-
ting tool included in the Access Control and Operation History Management Package.
SEE
ALSO For more information about security models, refer to:
2., “Security Models” in ProSafe-RS Security Guide (IM 32P01C70-01EN)
n Creating User Accounts in Windows Authentication Mode

In Windows authentication mode, Windows user names are used to log on to the SENG func-
tions and authenticate users.

IMPORTANT
When you use Windows authentication mode, create Windows users following the naming
convention below, rather than the Windows naming convention. This naming convention is the
same as the naming convention for engineers.
The naming convention for users in Windows authentication mode is as follows:
Table B4.6-2 User Naming Convention in Windows Authentication Mode

Number of characters Up to 16 characters
Character type Alphanumeric characters and the following symbols can be used: ! # $
%()-.^_{}~
Restriction Upper-case characters only (*1)
For the head character, alphanumeric characters and the following
symbols can be used: ^ _ { } ~
Names ending with a period cannot be used.
*1: Only upper-case characters can be used for engineer names to be registered in the Engineers’ Account Builder. Although
both upper-case and lower-case characters can be used on the Windows side, they are not distinguished; use upper-case
characters only.
You can set passwords within 63 characters using alphanumeric characters and symbols.
• Passwords are case-sensitive.
• The following symbols and space character are allowed:
!"#$%&'()*+,-./:;<=>?@[\]^_{|}~
SEE
ALSO For more information about how to create Windows user accounts, refer to:

B4.6.1 Setup Procedure when Using Access Control and

Operation History Management Functions
This section describes the setup procedure you should perform after installing the ProSafe-
RS software when using the operation history management functions. If you want to introduce
the access control and operation history management functions later, perform the procedure
at a proper timing.
Perform the following tasks after creating administrator and engineer user accounts on Win-
dows.
1. Add the Windows accounts for administrators and engineers to their respective appropri-
ate user groups.
2. Configure security settings for the operation history database.
3. On a computer granted with the licenses of the Safety System Engineering and Mainte-
nance Function and the Access Control and Operation History Management Package,
use the Operation History Management Setup Tool and Engineers’ Account Builder to
perform required setting.
SEE
ALSO For more information about how to create Windows user accounts, refer to:
For more information about the explanation of the procedure involved in making security settings for opera-
tion history management databases, refer to:
B4.6.2, “Security Settings for the Operation History Database” on page B4-11
For more information about the precautions to be followed when setting the access control/operation history
management function, refer to:
E2.2, “Setting up Access Control/Operation History Management” in Engineer's Reference Manual (IM
32P04B10-01EN)

B4.6.2 Security Settings for the Operation History Database

The administrator must specify the folder for storing the operation history database by using
the operation history management setting tool. Set the security of the folder for storing the op-
eration history database at proper timing before starting to use the operation history manage-
ment function.
This section explains the procedures to configure security settings when the operation history
database is placed on an SENG PC and when it is placed on a file server. After performing
these procedures, the administrator and engineers can access the operation history database
folder.
n Setting when Operation History Databases are Placed on SENG PC

If you place an operation history database on an SENG PC, perform the following procedure
to reinforce the security of the folder for storing the operation history database.
1. Create a new folder for storing the operation history database.
2. Log on to the system as an administrative user who belongs to the PSF_MAINTENANCE
group and assign the sharing name “RS-Share” to the folder for storing the operation his-
tory database.
3. If the folder needs to be shared with other computers, grant a full control permission to
Everyone.
4. Launch the IT Security Tool from the Start menu and execute it again without changing
the setting made the last time it was executed.
n Setting when Operation History Databases are Placed on a File

Server
If you place an operation history database on a computer not installed with the ProSafe-RS
software and allow SENG to access the database via a network, perform the procedure to re-
inforce security of the file server.
SEE
ALSO For more information about the procedure for reinforcing the security of the file server, refer to:
B5., “Setting Up a File Server” on page B5-1

<B5. Setting Up a File Server> B5-1
B5. Setting Up a File Server

Provide a file server in the system, and you can access the files placed on this server comput-
er from other computers. On a file server, you may place a project database, the check-in
destination folder for Version Control Tool, and/or the operation history database of the Ac-
cess Control and Operation History Management Package, allowing access to these databa-
ses via the network.
This section describes how to set up a file server computer for the following cases:
• Computer that serves only as a file server
• Computer that serves as both a file server and an SENG
• Computer that serves as both a file server and a license management station
n Item to be Prepared
Have the following item at hand before you set up a file server.
n File System
Ensure that the file system is in the NTFS format.

<B5.1 Setting Up a Computer that Serves Only as a File Server > B5-2
B5.1 Setting Up a Computer that Serves Only as

a File Server
This section describes how to set up a computer that is used only as a file server.
IMPORTANT
• When sharing a file server between CENTUM VP and ProSafe-RS and operating with
other than linked domain management, use the IT Security Tool for file server and domain
controller whose revisions are R6.04 or later to set IT security for CENTUM VP.
• When sharing a file server between CENTUM VP and ProSafe-RS and operating with
linked domain management, you must build a file server between the products of revi-
sions that support linked domain management. Use the IT Security Tool for file server and
domain controller of the product of revisions that support linked domain management and
the Domain Link Management Tool for File Server. CENTUM VP supports linked domain
management with R6.08 or later software revisions.
• When sharing a file server with a product that does not support linked domain manage-
ment and using it in a domain environment, operate with domain management or combi-
nation management.
n Installing Windows Update Programs (Windows Server 2012 R2)

Download and apply the Windows update programs.
SEE
ALSO For more information about downloading the Windows Server 2012 R2 update programs, refer to:
“n Downloading the Windows Update Programs (Windows Server 2012 R2)” on page B1-4
n Disabling the Automatic Cleanup Task (Windows Server 2016 or

Windows Server 2012 R2)
When using Windows Server 2016 or Windows Server 2012 R2 as a file server, disable Auto-
matic cleanup task.
SEE
ALSO For more information about the procedure for disabling the Automatic cleanup task, refer to:
“n Disabling the Automatic Cleanup Task” on page B3-15
n Administrative User who Performs the Setup

A file server must be set up by an administrative user who belongs to the groups shown in the
following table.

Table B5.1-1 Groups to Which the Administrative User Who Sets Up a File Server Belongs
Standard model
Legacy model Standalone management/Linked do-
Domain/Combination management
main management
• Domain user who belongs to the Do-
main Admins domain group and
PSF_MAINTENANCE domain group
• Domain user who belongs to the Ad-
Local user who belongs Local user who belongs to the Adminis-
ministrators local group and
to the Administrators lo- trators local group and PSF_MAINTE-
PSF_MAINTENANCE local group
cal group NANCE local group
• Local user who belongs to the Ad-
(*1)
n Procedure 0: Procedure for Placing an SCS Project on Another PC

Such as a File Server
If an SCS project is newly placed on a file server PC that is different from the SENG PC, files
in the SCS project database may be corrupted while the SCS project is operated on the
SENG PC. When you are going to place an SCS project on a PC such as a file server which
is different from the SENG PC that operates the SCS project, make sure to implement the
avoidance described in SEE ALSO to prevent file corruption in the SCS project database.
SEE
ALSO For more information about avoidance, refer to:
“■ Precautions when Placing the SCS Project on Another PC such as a File Server” in 1.2, “Engineering”
in ProSafe-RS Release Information (IM 32P01A50-01EN)
n Procedure 1: Install Microsoft Visual C++ 2017 Redistributable

Package
Before you can run the IT Security Tool, you must install the Microsoft Visual C++ 2017 redis-
tributable package.
SEE
ALSO For more information about the procedure for installing the Microsoft Visual C++ 2017 redistributable pack-
age, refer to:
“n Installation of Microsoft Visual C++ 2017 Redistributable Package” on page B2-6
n Procedure 2: Create an Administrative User

Perform one of the following procedures according to the security model to be applied.
TIP In the case of the Legacy model, this operation is not required because the setup can be performed by an
existing user.
l Standard Model with Standalone Management/Linked Domain

Management
1. Log on as a member of the Administrators group.
2. Create the PSF_MAINTENANCE group.

3. Add the user to be set as the administrator to the Administrators and PSF_MAINTE-
NANCE groups.
TIP If any other YOKOGAWA product coexists in the computer, the user also needs to be a member of the MAIN-
TENANCE group of the coexisting product. For example, if CENTUM VP coexists, also add the user to the
CTM_MAINTENANCE group.
l Standard Model with Domain/Combination Management

Follow these steps to designate a local group user as an administrator:
TIP To use a domain group user as an administrative user, this operation is not required because the user already
exists.
1. Log on to Windows as a user with administrative rights.

2. Create the PSF_MAINTENANCE local group.
3. Add the domain user or local user to be set as the administrator to the Administrators lo-
cal group and PSF_MAINTENANCE local group.
TIP • After the IT Security Tool is run, the name of the PSF_MAINTENANCE group you have created will
change to PSF_MAINTENANCE_LCL.
• If any other product coexists in the computer, the user also needs to be a member of the MAINTE-
NANCE group of the coexisting product. For example, if CENTUM VP coexists, also add the user to the
CTM_MAINTENANCE group.
n Procedure 3: Create and Set Up Shared Folders

In order to reinforce the security of folders that store databases using the IT Security Tool, you
must name the target folders with the following share names:
• Project database
Share name: RS-Projects
• Operation history database and check-in destination folder of Version Control Tool
Share name: RS-Share
IMPORTANT
If the share name does not match the name above, the IT Security Tool is not able to rein-
force the folder security. Be sure to set the share name above using the following procedure
so that you can reinforce security.
l Creating a New Folder

2. Start Windows Explorer and create a folder in which the project folders are to be placed.
3. On the Sharing tab in the properties of the folder that is created, click [Advanced Shar-
ing].
4. Select [Share this folder] and set RS-Projects or RS-Share as the share name.
5. Click [Permissions], and grant full control to [Everyone] in the Share Permissions tab.
This access permission setting will be changed when you run the IT Security Tool.

l When a Shared Folder is Already Created on the File Server

Before configuring IT security settings, add a share name, “RS-Projects” or “RS-Share,” to the
folder. The folder will be included in the process of IT security setting configuration and ac-
cess permissions setting will be applied. Share names that were previously set up do not
need to be deleted.
IMPORTANT
If a folder with the share name “RS-Projects” or “RS-Share” has already been created for an-
other purpose on an existing file server, change the existing share name to another name.
Since the access permissions are granted to folders with the share name “RS-Projects” or
“RS-Share” during configuration of IT security settings, unintended settings will be applied if
these share names are not assigned to appropriate folders.
If IT security settings have been applied to an unintended folder, delete the permissions set
during the configuration of IT security settings and set the original access permissions based
on the setting of another folder, such as the C:\Windows folder.
n Procedure 4: Save the Initial Data of the IT Security Settings
IMPORTANT
• Before you run the IT Security Tool to configure IT security settings for the first time, be
sure to save the security settings on the computer.
• On a file server, when changing the IT security settings, you need to use the initial data
saved beforehand to restore the security settings, and then apply them again. Therefore,
the following saved data of IT security settings is required.
• When the user management type is standalone management or linked domain man-
agement in Standard model:
Data saved before the first application of IT security settings in the standalone state
• When the user management type is Domain management or Combination manage-
ment in Standard model:
Data saved before applying IT security settings after adding to the domain
• When configuring the security settings for the second time onward, basically the security
settings need not be saved. However, to configure the security settings by using the IT
Security Tool of R3.01 to R4.02 and change the IT security version to 2.0 by using the IT
Security Tool of R4.03 or later, save the initial security setting data again.
• To save the initial security setting data again, restore the security settings that were
saved before by using the IT Security Tool. If the file server is a member of the domain,
determine which of the two sets of initial data will be recovered based on whether or not
to keep the file server as the member of the domain. Then, perform this procedure to
save the security settings. From then on, the data you have saved again will be used
when the security settings are initialized; accordingly, keep the saved data in a safe
place.
Follow these steps to save the security settings:


3. Click [Setting IT Security (File server/domain controller use)].
Figure B5.1-1 IT Security Tool Menu
TIP If the file server is a member of a domain, when restoring the initial security settings on the file server, the
initial data should have two types, either the initial data for a standalone computer or the initial data for a
member of domain.
If you do not have the initial data for a standalone file server computer, you need to remove the file server
from the domain temporarily and then save the security settings as the initial data for the standalone comput-
er.
4. Click [Save].
The Specify destination page appears.
5. Specify the destination folder and enter following setting items.
• Distinguished Name
• Support Product
• Support OS
• File Version
TIP The [Distinguished Name] and [File Version] are omissible.
6. Click [Next].
The Type default account password page appears.
7. Enter the password for use as the initial account password and click [Next].
The Type password (Encryption Key) page appears.

TIP This initial password will be set when the account saved with this tool is recovered. If the saved accounts are
not found on the computer when you recover the accounts, new accounts are created. This password will be
set as the initial password for the newly created account.
Even when multiple accounts have been created, the same initial password is assigned to all.
If the set password does not meet the password policy in the environment where the account is to be recov-
ered, an error will occur when recovering an account.
This password is set as the initial password for the account. Accordingly, you will be prompted to change the
password when you log on for the first time using this account.
8. Enter the password for encrypting the saved data, and click [Next].
Saving of the security settings starts.
IMPORTANT
• If this password (encryption key) is lost, the saved security settings cannot be restored.
The password (encryption key) must be carefully kept by the customer.
• The password (encryption key) must be at least one character.
• The password can consist of upper-case and lower-case alphanumeric characters and
the following symbols: ` ~ ! @ # $ % ^ & * ( ) _ + - = { } | \ : " ; ' < > ? , . /
9. When the saving is completed, click [Finish].

If the saving failed, the details of the failure are displayed.
10. On the IT Security Tool menu, click [Close].
TIP If any save failures are displayed, contact YOKOGAWA Service.
n Procedure 5: Configure with IT Security Tool
IMPORTANT
If you operate with linked domain management, do not add the computer to the domain be-
fore you configure the settings with IT Security Tool.
Follow these steps to configure the file server with IT Security Tool:
1. From the IT Security Tool Menu, click [Setup].
A confirmation dialog box appears
2. If you have saved the above mentioned initial security setting data, click [OK].
TIP If you have not saved the initial security setting data, click [Cancel] to return to the tool's menu and save the
security settings.
The Select Security Model page appears.

Figure B5.1-2 Select Security Model
4. From the Setting Model drop-down list, select a security model for the file server.
You can select from the following four models:
Table B5.1-2 Security Models for a File Server

Model Description
Select this model to apply Legacy model to the file
File Server Legacy Model (*1)
server, regardless of the user management type.
Select this model to apply Standard model to the file
File Server Standard Model with Standalone Man-
server when the user management type is Stand-
agement
alone management or Linked domain management.
File Server Standard Model with Domain Manage-
server when the user management type is Domain
ment
management.
File Server Standard Model with Combination Man-
server when the user management type is Combina-
agement
tion management.
*1: If you select [2.0] for Select IT security version, you cannot select the file server legacy model.
5. Click [Next].
TIP If you click [Detail] here, the Select Setting Items page appears.
6. The subsequent steps are the same as those for the settings with IT Security Tool after
installing the ProSafe-RS software.

TIP If the file server is shared with CENTUM VP, start the IT Security Tool for file server and domain controller
from the installation menu of CENTUM VP software medium and set IT security for CENTUM VP as well. Use
the software medium of the following revisions depending on the user management type.
• Linked domain management: R6.08 or later
• Other than Linked domain management: R6.04 or later
SEE
ALSO For more information about operation of IT Security Tool after the ProSafe-RS software is installed, refer to:
For more information about the procedure for importing the IT security settings, refer to:
32P01C70-01EN)
n Procedure 6: Create Accounts on the File Server for Users who

Access Project Data
On the file server computer, create accounts for users who access the project data, according
to the selected security model and user management type.
l Standard Model with Linked Domain Management/Combination

Management
When you create accounts of local users who access project data, create them in the same
way as for “● Legacy/Standard Model with Standalone Management.”
On the domain controller, add the accounts for accessing projects. No account needs to be
created if already created.
SEE
ALSO For more information about how to create domain user accounts, refer to:
l Standard Model with Domain Management

On the domain controller, add the accounts for accessing projects. No account needs to be
created if already created.
l Legacy/Standard Model with Standalone Management

Perform the following procedure on the file server.
1. Create a user account.
The user name and the password must be the same as those of the SENG PCs from
which the projects are accessed.
2. Register the user you have created to the same group as that on the SENG PCs which
access the file server.
TIP If the Standard model is applied, the following user groups have been created during the procedures so far.
• PSF_MAINTENANCE
• PSF_OPERATOR
• PSF_ENGINEER
• PSF_OPC

n Procedure 7: Configure Settings for Operating with Linked Domain

Management
When operating with linked domain management, join the computer to the domain and then
configure settings using Domain Link Management Tool for File Server.
IMPORTANT
The Domain Link Management Tool for File Server in the ProSafe-RS software medium links/
unlinks the domain only for the local group related to ProSafe-RS. If the file server is shared
by CENTUM VP and ProSafe-RS, use the Domain Link Management Tool for File Server in
the software medium of each product to set each.
Follow these steps to configure settings for operation with linked domain management:
1. Join the computer to the domain.
2. Sign in as a local user who belongs to both the Administrators group and PSF_MAINTE-
NANCE group of the local computer, or a domain user who belongs to both the Domain
Admins and PSF_MAINTENANCE groups of the domain.
3. Use Windows Explorer to open the following folder in the ProSafe-RS installation medi-
um.
<Drive of ProSafe-RS software medium>:\ProSafe-RS\SECURITY\
4. In the folder, double-click DomainLinkManagementToolForRSFileServer.cmd.
The Domain Link Management Tool for File Server starts.
5. The subsequent steps are the same as those for the settings with Domain Link Manage-
ment Tool after installing the ProSafe-RS software.
TIP • If you start the Domain Link Management Tool as an administrative user of a local group, the domain
user authentication dialog box appears in the procedure for linking the domain. The user name and
password that you enter in the dialog box do not have to be those of the domain administrator.
• If the file server is shared with CENTUM VP, use the Domain Link Management Tool for File Server in
the software medium of CENTUM VP to configure the settings to link the domain for CENTUM VP as
well.
SEE
ALSO For more information about the settings with Domain Link Management Tool after the ProSafe-RS software is
installed., refer to:
B3.6.3, “Running Domain Link Management Tool” on page B3-51
l Error Messages and Countermeasures

Depending on the conditions when starting Domain Link Management Tool for File Server, an
error message may be displayed and the tool cannot be started. Take the necessary meas-
ures.
The following table describes the error messages and countermeasures when you cannot
start Domain Link Management Tool for File Server.
Table B5.1-3 Error messages and countermeasures

Error messages Countermeasures
This tool cannot be started simultaneously with the Exit the IT Security Tool.
IT security tool.

Table B5.1-3 Error messages and countermeasures (Table continued)
This tool does not support computers without the IT For a file server dedicated computer, set the IT se-
security settings for the file server of R4.06.00 or lat- curity for the file server of R4.06.00 or later, and then
er. start Domain Link Management Tool for File Server.
For computers with ProSafe-RS software or license
management software installed, start Domain Link
Management Tool from the Start menu.
n Procedure 8: Create the Project Folder on the File Server and Start
the Operation
• Project database
From an SENG PC, create an RS project under the shared folder “RS-Projects” created
in Procedure 3.
• Check-in folder of Version Control Tool
On an SENG PC, use the Version Control Tool to specify a folder under the shared folder
“RS-Share” created in Procedure 3 as the check-in destination folder, and start project
operation.
• Operation history database
On an SENG PC, use the operation history management setting tool to specify a folder
under the shared folder “RS-Share” created in Procedure 3 as the top folder of the opera-
tion history database, and start the access control and operation history management
function.

<B5.2 Setting Up the File Server Function on an SENG or a Computer Installed with Only AD Server >
B5-12
B5.2 Setting Up the File Server Function on an

SENG or a Computer Installed with Only
AD Server
This section describes the required settings when you use a computer that has been set up
as an SENG or installed with only AD Server, also as a file server.
TIP On an SENG, the project database is created under the installation folder by default. The procedure descri-
bed in this section is for the case when the project database is placed in a location other than the installation
folder.
1. Set up the computer as an SENG or as a computer installed with only AD Server.

TIP • If the user management type of IT security setting is domain or combination management, set up after
the computer is added to the domain.
• You do not need to configure IT security settings during this setup.
2. If an SCS project is newly placed on a file server PC that is different from the SENG PC,
files in the SCS project database may be corrupted while the SCS project is operated on
the SENG PC. When you are going to place an SCS project on a file server, make sure to
implement the avoidance described in SEE ALSO to prevent file corruption in the SCS
project database.
3. On the computer, create and set up the shared folder.
4. Start the IT Security Tool from the Start menu and configure IT security settings.
TIP When operating with linked domain management, set the standalone management in the Standard model.
5. Select one of the following depending on the user management type.

• Go to the step 5 to operate with linked domain management.
• Go to the step 7 to operate with user management type other than linked domain
management.
7. Start Domain Link Management Tool from the Start menu and link the domain.
8. Create a project folder in a location under the shared folder of the computer.
IMPORTANT
When you set up the file server function on an SENG or a computer with only AD Server in-
stalled, you must use the IT Security Tool and Domain Link Management Tool that are started
from the Start menu.

<B5.2 Setting Up the File Server Function on an SENG or a Computer Installed with Only AD Server >
B5-13
SEE
ALSO For more information about how to create the project folder on the file server, refer to:
“n Procedure 8: Create the Project Folder on the File Server and Start the Operation” on page B5-11
For more information about new setup of SENG, refer to:
B3., “Setup of an SENG or a Computer Installed with Only AD Server” on page B3-1
For more information about the shared folder settings, refer to:
“n Procedure 3: Create and Set Up Shared Folders” on page B5-4
For more information about creating accounts for users who access the project database, refer to:
“n Procedure 6: Create Accounts on the File Server for Users who Access Project Data” on page B5-9
For more information about avoidance against file corruption in the SCS project database, refer to:

<B5.3 Setting Up the Computer that Serves as Both File Server and License Management Station >
B5-14
B5.3 Setting Up the Computer that Serves as

Both File Server and License Management
Station
This section describes the setup required for the computer that serves as both a file server
and a license management station.
n Setup Procedure
1. Install the license management software.
TIP If the user management type of IT security setting is domain or combination management, set up after the
computer is added to the domain.
2. If an SCS project is newly placed on a file server PC that is different from the SENG PC,
files in the SCS project database may be corrupted while the SCS project is operated on
the SENG PC. When you are going to place an SCS project on a file server, make sure to
implement the avoidance described in SEE ALSO to prevent file corruption in the SCS
project database.
3. On the dialog box that appears on completion of the installation, select [No, I want to in-
stall other software products.] and click [Finish].
4. Configure the shared folder settings required for a file server.
5. Start the IT Security Tool from the Start menu and configure IT security settings.
TIP When operating with linked domain management, set the standalone management in the Standard model.

• The steps are completed if you operate with user management type other than linked
domain management.
8. Start Domain Link Management Tool from the Start menu and link the domain.
IMPORTANT
When you configure a computer for use as both a file server and a license management sta-
tion, you must use the IT Security Tool and Domain Link Management Tool that are started
from the Start menu.
SEE
ALSO For more information about installing only the license management software, refer to:
For more information about the shared folder settings, refer to:
“n Procedure 3: Create and Set Up Shared Folders” on page B5-4
For more information about avoidance against file corruption in the SCS project database, refer to:

<B6. Setting Up the Computer Dedicated to License Management> B6-1
B6. Setting Up the Computer Dedicated

to License Management
You can use a computer as the license management station by installing only the license
management software on it.
This section describes the procedure for setting up the computer dedicated to license man-
agement.
Have the following item at hand before installing the license management software.
n Administrative User who Performs the Installation

The administrative users shown in the following table should install the license management
software:
Table B6-1 Administrative User Who Installs the License Management Software
Standard Model
Legacy Model Standalone management/Linked do-
Domain/Combination Management
main management
main Admins domain group
Local user who belongs
Local user who belongs to the Adminis- • Domain user who belongs to the Ad-
to the Administrators lo-
trators local group ministrators local group
cal group
ministrators local group(*1)
n Setting Up a License Management Station

This section describes the procedure for setting up a license management station.
l Set Up Windows
The following table shows the Windows setting items. Configure the items that are required
for the OS being used.
Table B6-2 Windows Setting Items

Windows setting item Windows OS (*1)
Windows 10 Windows Server 2016
File System Yes Yes
Power Options Yes Yes
Turning Off Fast Startup Yes -
Windows Defender Yes Yes
Disk Defragmenter Yes Yes
DCOM Settings Yes Yes

*1: Yes: Configuration required; -: Not available on the OS.
SEE
l Install the License Management Software

Follow these steps to install the license management software.
3. Click [Install License Manager Software].
The Welcome dialog box appears.
TIP If the Windows redistributable modules required to run ProSafe-RS are not installed, a dialog box appears,
prompting you to install such modules. Follow the instruction of the dialog box.
4. Click [Next].
The User Information dialog box appears.
TIP If a different version of control bus driver is already installed, a dialog box appears, prompting you to update
the driver. However, you do not need to install the control bus driver on a computer dedicated to license man-
agement. Click [OK] to close the dialog box.
5. In the User Information dialog box, enter the name and company name, select the instal-
lation folder, and confirm the language for installation, and click [Next].
6. Review the installation settings and click [Install].
A dialog box showing the installation progress appears, and when the license manage-
ment software installation is complete, the Installation Complete dialog box appears.
7. Select [Yes, I want to set up IT security now.] and click [Finish].
8. Go on to configure the security settings.
TIP • When deleting the ProSafe-RS function and installing only the license management software after instal-
ling ProSafe-RS, first sign in using an administrative user account and uninstall ProSafe-RS, and then
install the license management software.
• When operating with linked domain management, set the standalone management in the Standard mod-
el.

• The steps are completed if you operate with user management type other than linked
domain management.
11. Sign in as an administrative user, start Domain Link Management Tool, and link the do-
main.

IMPORTANT
• If you want to manage other product's licenses on the computer dedicated to license
management, you also need to install the license management software from the soft-
ware medium of that product.
• Settings for using a license management dedicated computer, use IT Security Tool and
Domain Link Management Tool started from the Start menu.
SEE
ALSO For more information about IT security settings, refer to:
For more information about how to uninstall the ProSafe-RS software, refer to:
C5.1.1, “Uninstalling the ProSafe-RS Software” on page C5-3
l Create User Accounts

Create accounts for the users who manage licenses.
SEE
For more information about the user who manages licenses, refer to:
1.2.2, “User privileges in License Manager” in License Management Guide (IM 32P01C60-01EN)
l Configure Windows Environment Settings for Each User

The following table shows the Windows setting items that must be configured for each user.
Configure the items that are required for the OS being used.
Table B6-3 Windows Setting Items Required for Each User

Windows setting item Windows OS (*1)
Windows 10 Windows Server 2016
Showing Icons on the Task Tray Yes Yes
Stopping the Inactive Window Scrolling Func- Yes Yes
tion
*1: Yes: Configuration required; -: Not available on the OS.
SEE
ALSO For more information about configuring Windows environment settings for each user, refer to:

<B7. Configuring the Hardware of SCS and Devices for Connection between Domains> B7-1
B7. Configuring the Hardware of SCS

and Devices for Connection
between Domains
Configure the hardware of SCS and devices used for connection between domains, such as
V net routers and L3 switches.
• On the processor module of SCS, set the V net or Vnet/IP address.
• If a V net router (AVR10D) is used to connect a Vnet/IP domain and a V net domain, the
V net router address should be set on the CENTUM side.
CAUTION
When removing and installing the cards to set DIP switches, take measure to prevent the
damages caused by static electricity.
SEE
ALSO For more information about antistatic measures, refer to:
Appendix 4., “Antistatic Precautions When Handling Hardware” on page App.4-1
For more information about hardware of SCS, refer to:
B., “Components of SCS” in Hardware User's Guide (IM 32P06C10-01EN)
For more information about setting the processor module of SCS, refer to:
B4.2, “Processor module” in Hardware User's Guide (IM 32P06C10-01EN)
For more information about configurations for N-IO Node Interface Unit, refer to:
F2.1, “Configuring the N-IO node interface unit” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about setting up the hardware when using V net routers, bus converters, and communi-
cation gateway, refer to:
CENTUM VP Communication Devices (IM 33J50D10-01EN)

<B8. Installing the Functions that Operate with CENTUM VP Licenses> B8-1
B8. Installing the Functions that

Operate with CENTUM VP Licenses
The test function and SOE Viewer of ProSafe-RS operate in coordination with CENTUM VP
packages. You can set up a computer so as to use only these functions without using other
SENG functions. First, grant the computer licenses (at least one license for the test functions)
of the CENTUM VP packages that operate in coordination.
Then, install the ProSafe-RS software from the ProSafe-RS software medium. Licenses for
ProSafe-RS software packages are not required.
TIP When you move the CENTUM package from a computer where the function that operates with CENTUM VP
licenses is used, fully install the ProSafe-RS software also on the new computer.
n Installation on the Computer for Running SCS Simulator

SCS simulator is used in combination with the CENTUM packages listed in the following ta-
ble. Licenses for ProSafe-RS packages are not required.
Table B8-1 CENTUM Packages Required for SCS Simulator

Model CENTUM VP package name
VP6E5420 Test Function
VP6E5426 FCS Simulator Package
Perform the following tasks on the computer where the SCS simulator is used. Either task can
be performed first.
• Install CENTUM software and grant a license for any of the CENTUM packages in the ta-
ble.
• Install ProSafe-RS software.
SEE
ALSO For more information about installing the CENTUM VP Software, refer to:
CENTUM VP Installation (IM 33J01C10-01EN)
n Installation on the Computer for Integration of CENTUM SOE Viewer

In the case of system configurations integrating CENTUM, it is possible to display SOE (Se-
quence of Events) of SCS on the CENTUM SOE Viewer. This is referred to as integration of
CENTUM SOE Viewer. The ProSafe-RS software package licenses are not required.
Perform the following tasks on the computer. Either task can be performed first.
• Install CENTUM software and grant a license for the CENTUM SOE Viewer package
(VP6P6920).
• Install ProSafe-RS software.
In order to display SOE of SCS on the CENTUM SOE Viewer, it is necessary to connect the
computer and SCS via V net or Vnet/IP.
SEE
ALSO For more information about granting a license of CENTUM SOE Viewer Package (VP6P6920), refer to:
License Management (IM 33J01C20-01EN)

<C. Maintenance> C-1
C. Maintenance
This section describes the tasks required in the operation and maintenance of stations after
they have been newly set up.

<C1. Adding Licenses and Changing License Assignments> C1-1
C1. Adding Licenses and Changing

License Assignments
This section describes how to add licenses, which is required to add new software packages
on a station, and how to change the assignments of licenses, which is required to migrate
software packages between stations.

<C1.1 Adding a License> C1-2
C1.1 Adding a License

The procedure for loading an additionally purchased license on the license management sta-
tion is the same as the procedure for new installation.
SEE
ALSO For more information about how to load an additionally purchased license on the license management sta-
tion, refer to:
3.1, “Reading additional licenses on a license management station” in License Management Guide (IM
32P01C60-01EN)

<C1.2 Changing License Assignments> C1-3
C1.2 Changing License Assignments

Use the License Manager on the license management station to add the license for the soft-
ware package additionally required on a license-assigned station.
Also use the License Manager on the license management station to remove the license for
the software package no longer required on a license-assigned station.
These operations are called “changing license assignments.”
SEE
ALSO For more information about changing license assignments, refer to:
3.2, “Modifying licenses” in License Management Guide (IM 32P01C60-01EN)

<C2. Setting Up the Windows Domain Environment Later> C2-1
C2. Setting Up the Windows Domain

Environment Later
This section describes the procedure for the case when you want to change the system that
has been built as a Standalone management system to a Domain management system.
n Workflow
Start
Set up the domain controller

for the domain controller
Create domain users
Add domain users

to domain groups
Add existing stations

to the domain
Change user management type

on the existing stations
End
Figure C2-1 Workflow for Setting Up the Windows Domain Environment Later
n Setup Procedure
1. Prepare a computer to be used as the domain controller and configure a domain control-
ler on it.
3. Create domain users.
4. Add the domain users to domain groups.
5. Select one of the following depending on which type you want to change the user man-
agement type for the existing station.
• Go to the step 6 to change to linked domain management.
• Go to the step 9 to change to domain management or combination management.
6. Add the client computer stations to the domain.

<C2. Setting Up the Windows Domain Environment Later> C2-2
7. Link the domain with Domain Link Management Tool.
8. Go to the step 11.
9. Add the client computer stations to the domain.
10. On each station, change the user management type to Domain management or Combi-
nation management.
11. Synchronize the time of the stations within the domain.
SEE
ALSO For more information about configuring the domain controller, refer to:
B2.2, “Configuring the domain controller” on page B2-5
For more information about configuring IT security settings on the domain controller, refer to:
B2.3, “Configuring Security Settings for the Domain Controller” on page B2-6
For more information about how to create domain users and add them to domain groups, refer to:
For more information about how to add client computers to a domain, refer to:
For more information about how to set up time synchronization within a domain, refer to:
For more information about changing the user management type, refer to:
6.4.2, “For File Server or Domain Controller” in ProSafe-RS Security Guide (IM 32P01C70-01EN)

<C3. Backing Up the System> C3-1
C3. Backing Up the System

To be prepared for system failures, it is recommended to back up the system periodically. The
files in the folders listed in the following table should be regularly backed up:
Table C3-1 Folder Backups

Contents Folder Registry When to back up
• When changes have been made to
the system; for example, after pro-
Backup of entire Win- Entire reg-
All hard disk gram installation or completion of
dows istry
setup.
• After closing all applications
Automation Design Mas-
- - -
ter Database (ADMDB)
ProSafe-RS engineering
SCS project folders - After closing the SENG software
data
When you back up a system where the Standard model of IT security settings is applied, log
on to Windows as an administrative user who has the right to access ProSafe-RS-related
folders.

<C3.1 Backing Up the Entire Windows > C3-2
C3.1 Backing Up the Entire Windows

This section describes how to back up the entire Windows.
n Backing Up Entire Windows

Back up Windows using a commercially available software program in preparation against
disk trouble.
n Creating Windows Repair Disk

Installing various application programs on a computer can cause troubles: for example, Win-
dows does not start up, or you cannot log on to Windows. In such cases, if you have a system
repair disk and boot disk, you can restore the system to the state at the time you created
these disks.
To be prepared for Windows troubles, create a system repair disk and boot disk when you
have changed the state of the system by installing a program, changing hardware configura-
tion, etc.
SEE
ALSO For more information about how to create a repair disk, refer to:
Windows-related manual or the web site of Microsoft Corporation

<C3.2 Backing Up the ProSafe-RS Engineering Data > C3-3
C3.2 Backing Up the ProSafe-RS Engineering

Data
After performing engineering operations, be sure to back up the engineering data.
n Backing Up Projects
You can copy the ProSafe-RS folders to a backup medium using Windows Explorer. It is also
possible to use commercially available backup software to back up the folders.
The SCS project folders should be backed up using Version Control Tool.
SEE
ALSO For more information about Version Control Tool, refer to:
F5., “Version control” in Engineer's Reference Manual (IM 32P04B10-01EN)
n Backing Up to AD Project
Be sure to back up the RS project to AD project before backing up ADMDB or exporting the
AD project.
SEE
ALSO For more information about how to back up projects to an AD project, refer to:
C1.1, “Tools for management of AD Server and AD projects” in Engineer's Reference Manual (IM
32P04B10-01EN)

<C4. Upgrading the ProSafe-RS Software > C4-1
C4. Upgrading the ProSafe-RS Software

This section explains the procedure to follow when upgrading the ProSafe-RS software and
tasks to be performed after upgrading.
To upgrade the software from the current version to the latest version, perform the tasks
in ”Installation for Upgrading”.
To use the added or modified features, read the all cautionary notes including from the current
version to the latest version, and perform the tasks in “Settings after Upgrading ProSafe-RS
Software”.

<C4.1 Installation for Upgrading > C4-2
C4.1 Installation for Upgrading

This section explains the procedure to upgrade the ProSafe-RS software already installed on
a computer to a newer version or revision.
TIP For example, as when upgrading from R3.02 to R4.01, an upgrade where the number next to R is incremen-
ted by 1 or more is referred to as a version upgrade. On the other hand, as when upgrading from R4.02 to
R4.03, an upgrade where the number immediately next to R remains the same is referred to as a revision
upgrade.
The procedure is different between an upgrade of the version and an upgrade of the revision
of ProSafe-RS software and some steps are separately explained. Refer to descriptions ap-
propriate to respective cases.
SEE
ALSO For more information about the procedure for upgrading the version of ProSafe-RS Software, refer to:
C4.1.1, “Upgrading the Version of ProSafe-RS Software” on page C4-4
For more information about the procedure for upgrading the revision of ProSafe-RS Software, refer to:
C4.1.2, “Upgrading the Revision of ProSafe-RS Software” on page C4-8
n Precautions for Revision Upgrade

Observe the following precautions when you upgrade the ProSafe-RS software.
• If the revision of ProSafe-RS prior to the revision upgrade is R4.03 or later, distribute and
accept the upgrade license. If the installation is performed without distributing and accept-
ing the upgrade license, an error dialog will appear and you will not be able to complete
the installation.
This is not necessary if the upgrade license has already been accepted.
• When you upgrade the ProSafe-RS software, install a new revision of software without
uninstalling the earlier revision.
If you uninstall R4.03 or later revision of ProSafe-RS software, a new revision of ProSafe-
RS software cannot be installed. In that case, reinstall the uninstalled ProSafe-RS soft-
ware again and then install the new revision.
IMPORTANT
The software release number must be the same between all the SENGs which is for engi-
neering SCS projects in the RS project, and SENGs which is for engineering SCSs that per-
form inter-SCS safety communication each other. Also, you must upgrade the revision of SCS
projects that perform inter-SCS safety communication.
• Once opening an existing SCS project or creating a new SCS project using newer revi-
sion software in SENG, the SCS project cannot be opened using older revision software.
• The SCS system program release number of SCSs in a system should basically be the
same, but mixture of different release numbers is allowed.
n Upgrading the Revision of Products When Two or More Upgrade

License Support Products are Installed
When CENTUM VP R6.04 or later and ProSafe-RS R4.03 or later, both of which support up-
grade licenses, are installed on the same computer, follow these steps to upgrade them:
1. Distribute the upgrade licenses of the respective coexisting products.

2. Upgrade the revision of each product.
Prepare the following items so that they are at hand before upgrading the ProSafe-RS soft-
ware.
• ProSafe-RS license medium
• ProSafe-RS license sheet (with project ID)
n User Who Performs Update Installation

When update installation is performed, IT security settings are configured following the instal-
lation of the ProSafe-RS software. Update installation must be performed by a user who be-
longs to the groups shown in the following table.
Table C4.1-1 Groups to Which the User Who Performs Update Installation Belongs
Currently applied se- Security model and user management type to be applied
curity model and user Standard model
management type Legacy model
Standalone type Domain/Combination type
main Admins domain group and
PSF_MAINTENANCE domain group
(*1)
Local user who belongs to the Administra-
Legacy model tors local group and PSF_MAINTE-
NANCE local group
(*1)
(*1) (*2) (*3)
Local user who belongs to the Administra-
Standalone (*1)
tors local group and PSF_MAINTE-
type • Local user who belongs to the Ad-
NANCE local group
(*1) (*2) (*3)
Standard main Admins domain group and
model PSF_MAINTENANCE domain group
(*1)
Domain/ Local user who belongs to the Administra-
Combina- tors local group and PSF_MAINTE-
PSF_MAINTENANCE_LCL local
tion type NANCE_LCL local group (*4)
group (*1)
PSF_MAINTENANCE_LCL local
group (*1) (*2) (*3)
*1: Log on while the computer is added to the domain.
*3: When this user applies IT security and uses iDefine interface package, the following steps must be performed as a domain
user who belongs to the Domain Admins domain group or as a domain user who belongs to the Administrators local group.
1. Run the 32 bit Command Prompt (%SystemDrive%\Windows\SysWOW64\cmd.exe) as Administrator.
2. Run either of the following batch files appropriate to the user management type.
%ProgramFiles(x86)%\YOKOGAWA\IA\iPCS\Platform\Security\Program
For Domain management: PSF_SetupSMSvcHostConfigDOM.cmd
For Combination management: PSF_SetupSMSvcHostConfigCMB.cmd
*4: Remove the computer from the domain before you change the IT security setting.

C4.1.1 Upgrading the Version of ProSafe-RS Software

The following flowchart illustrates the flow of installation for upgrading the version of ProSafe-
RS software.
Start
Set up Windows
Update network drivers
Install the new version

of ProSafe-RS software
End
Figure C4.1.1-1 Flow of installation for upgrading the version
n Set Up Windows
Configure Windows settings.
SEE
ALSO For more information about procedures for setting up Windows, refer to:
n Installing Latest Network Driver

Before upgrading the software, install the latest network driver (included in the new ProSafe-
RS software version to be installed).
This section explains how to update the control bus driver, Vnet/IP open communication driv-
er, and the Vnet/IP Interface Package.
l Updating the Control Bus Driver

Follow these steps to update the control bus driver:
1. Uninstall the control bus driver.
2. Install the latest version of the control bus driver.
3. Configure Windows network settings.
SEE
ALSO For more information about the uninstallation procedure of control bus driver, refer to:
“n Uninstalling Control Bus Driver” on page C5-5
For more information about installing the control bus driver, refer to:
B3.3.1, “Installing the Control Bus Driver” on page B3-19
For more information about the procedure for configuring Windows network settings, refer to:
B3.3.4, “Configuring Windows Network Settings” on page B3-27

l Updating the Vnet/IP Open Communication Driver

The procedure to update the Vnet/IP open communication driver is the same as the proce-
dure to install the Vnet/IP open communication driver. If it is necessary to update the Vnet/IP
open communication driver, you can select [INSTALL] in the Setup dialog box.
Follow these steps to update the Vnet/IP open communication driver:
1. Install the latest version of the Vnet/IP open communication driver.
2. Be sure to restart the computer after updating the Vnet/IP open communication driver.
SEE
ALSO For more information about installing the Vnet/IP open communication driver, refer to:
B3.3.2, “Installing the Vnet/IP Open Communication Driver” on page B3-21
l Updating the Vnet/IP Interface Package

If a virtual machine is used, update the Vnet/IP Interface Package.
Follow these steps to update the Vnet/IP Interface Package:
1. Uninstall the Vnet/IP Interface Package.
2. Install the latest Vnet/IP Interface Package.
SEE
ALSO For more information about the procedure to uninstall the Vnet/IP Interface Package, refer to:
“n Uninstalling the Vnet/IP Interface Package on a Virtual Machine” on page C5-7
For more information about the procedure to install the Vnet/IP Interface Package, refer to:
B3.3.3, “Installing the Vnet/IP Interface Package on a Virtual Machine” on page B3-23
l Checking Inconsistency in TCP/IP Settings

After updating the network driver, run the TCP/IP Inconsistency Detection Tool. If any incon-
sistency is detected in the settings, use the TCP/IP Inconsistency Repair Tool and then con-
figure the TCP/IP settings again.
SEE
ALSO For more information about the TCP/IP Inconsistency Detect Tool and TCP/IP Inconsistency Repair Tool, re-
fer to:
“n Procedure 5: Repair TCP/IP Settings” on page B3-36
n Procedure for Update Installation

Follow these steps below to upgrade the ProSafe-RS software.
ware.

3. Insert the ProSafe-RS software medium to the drive. The ProSafe-RS installation menu
appears.
If the installation menu does not appears, double-click Launcher.exe in the top folder of
the software medium using Explorer.
4. Click [ProSafe-RS software].
The Welcome dialog box appears if all the Windows redistribution modules required for
ProSafe-RS have been installed. Proceed to step 6.
The dialog box for confirming module installation appears if any of Windows redistribution
modules required for ProSafe-RS have not been installed.
5. Click [Install] in the module installation confirmation dialog box. Module installation starts.
The window closes.
IMPORTANT
If the installation fails, reinstall referring to the installation procedure for the new setup.
7. If the dialog box for confirming the privilege setting appears, reboot the computer and log
on again.
a. Click [OK] and reboot the computer.
b. After rebooting the computer, log on again as the same user. The Welcome dialog
box appears automatically.
8. Click [Next] in the welcome dialog box.
ted to Ethernet.
9. Check the installation settings in the Confirm Settings dialog box and click [Install]. The
installation of ProSafe-RS starts and the dialog box showing installation progress status
appears.
10. When you have completed the installation of the ProSafe-RS software, the installation
complete dialog box appears.
If there are no products to be installed subsequently, select [Yes, I want to set up IT se-
curity now.] and click [Finish].
TIP If you intend to continue to install other YOKOGAWA products, select [No, I want to install other software
products.] and click [Finish].
IMPORTANT
If you select [No, I want to install other software products.] here, you must perform IT security
settings when you install the last product.

SEE
ALSO For more information about the installation procedure for new setup, refer to:
“n Installation Procedure” on page B3-40
For more information about configuring the IT security settings, refer to:
n Additional Execution of IT Security Configuration

If you are upgrading from R2 where the standard model of security settings are applied, you
must configure IT security settings again in this way: after configuring the IT security settings
following the installation of the product, reboot the computer and then start the IT Security
Tool from the Start menu to configure the IT security settings.
n Tasks Related to Licenses

In the case of a version upgrade, perform the tasks related to licenses after configuring IT se-
curity.
SEE
ALSO For more information about tasks related to licenses, refer to:

C4.1.2 Upgrading the Revision of ProSafe-RS Software

The following flowchart illustrates the flow of installation for upgrading the revision of ProSafe-
RS software.
Start
Upgrade license No
required?
Yes
Add upgrade licenses
Distribute upgrade licenses
Set up Windows
Update network drivers
Install the new revision

of ProSafe-RS software
End
Figure C4.1.2-1 Flow of installation for upgrading the revision
SEE
ALSO For more information about details of the upgrade license, refer to:
n Adding an Upgrade License

Adding an upgrade license enables you to distribute the upgrade license. If an upgrade li-
cense is necessary, add the upgrade license by using License Manager on the license man-
agement station.
n Distributing an Upgrade License

Distributing an upgrade license enables you to install upgrades of the ProSafe-RS software
on a license-assigned station. If an upgrade license is necessary, distribute the upgrade li-
cense to the license-assigned station from the license management station.
TIP • If an upgrade license is distributed alone, the license will be accepted automatically.
• The upgrade license can be distributed simultaneously with a software license. In such case, by accept-
ing the license on the license-assigned station, the upgrade license and software license will both be ac-
cepted.

SEE
ALSO For more information about how to add and distribute an upgrade license, refer to:
5., “Working with upgrade licenses” in License Management Guide (IM 32P01C60-01EN)
n Setting Up Windows
Configure Windows settings.
SEE
ALSO For more information about procedures for setting up Windows, refer to:
n Installing Latest Network Driver

Before upgrading the software, install the latest network driver (included in the new ProSafe-
RS software version to be installed).
This section explains how to update the control bus driver, Vnet/IP open communication driv-
er, and the Vnet/IP Interface Package.
l Updating the Control Bus Driver

Follow these steps to update the control bus driver:
1. Uninstall the control bus driver.
2. Install the latest version of the control bus driver.
SEE
ALSO For more information about the uninstallation procedure of control bus driver, refer to:
“n Uninstalling Control Bus Driver” on page C5-5
For more information about installing the control bus driver, refer to:
B3.3.1, “Installing the Control Bus Driver” on page B3-19
l Updating the Vnet/IP Open Communication Driver

The procedure to update the Vnet/IP open communication driver is the same as the proce-
dure to install the Vnet/IP open communication driver. If it is necessary to update the Vnet/IP
open communication driver, you can select [INSTALL] in the Setup dialog box.
Follow these steps to update the Vnet/IP open communication driver:
1. Install the latest version of the Vnet/IP open communication driver.
2. Be sure to restart the computer after updating the Vnet/IP open communication driver.
SEE
ALSO For more information about installing the Vnet/IP open communication driver, refer to:
B3.3.2, “Installing the Vnet/IP Open Communication Driver” on page B3-21

l Updating the Vnet/IP Interface Package

If a virtual machine is used, update the Vnet/IP Interface Package.
Follow these steps to update the Vnet/IP Interface Package:
1. Uninstall the Vnet/IP Interface Package.
2. Install the latest Vnet/IP Interface Package.
SEE
ALSO For more information about the procedure to uninstall the Vnet/IP Interface Package, refer to:
“n Uninstalling the Vnet/IP Interface Package on a Virtual Machine” on page C5-7
For more information about the procedure to install the Vnet/IP Interface Package, refer to:
l Checking Inconsistency in TCP/IP Settings

After updating the network driver, run the TCP/IP Inconsistency Detection Tool. If any incon-
sistency is detected in the settings, use the TCP/IP Inconsistency Repair Tool and then con-
figure the TCP/IP settings again.
SEE
fer to:
n Procedure for Update Installation

Follow these steps below to upgrade the ProSafe-RS software.
ware.
3. Insert the ProSafe-RS software medium into the drive. The ProSafe-RS installation menu
appears.
If the installation menu does not appear, double-click Launcher.exe in the top folder of the
software medium using Explorer.
4. Click [ProSafe-RS software].
The Welcome dialog box appears if all the Windows redistribution modules required for
ProSafe-RS have been installed. Proceed to step 6.
The dialog box for confirming module installation appears if any of Windows redistribution
modules required for ProSafe-RS have not been installed.
5. Click [Install] in the module installation confirmation dialog box. Module installation starts.
The window closes.
IMPORTANT
If the installation fails, reinstall referring to the installation procedure for the new setup.

7. If the dialog box for confirming the privilege setting appears, reboot the computer and log
on again.
a. Click [OK] and reboot the computer.
b. After rebooting the computer, log on again as the same user. The Welcome dialog
box appears automatically.
8. Click [Next] in the welcome dialog box.
ted to Ethernet.
9. Check the installation settings in the Confirm Settings dialog box and click [Install]. The
installation of ProSafe-RS starts and the dialog box showing installation progress status
appears.
10. When you have completed the installation of the ProSafe-RS software, the installation
complete dialog box appears.
If there are no products to be installed subsequently, select [Yes, I want to set up IT se-
curity now.] and click [Finish].
TIP If you intend to continue to install other YOKOGAWA products, select [No, I want to install other software
products.] and click [Finish].
IMPORTANT
If you select [No, I want to install other software products.] here, you must perform IT security
settings when you install the last product.
SEE
ALSO For more information about the installation procedure for new setup, refer to:
“n Installation Procedure” on page B3-40
For more information about configuring the IT security settings, refer to:

<C4.2 Settings after Upgrading ProSafe-RS Software > C4-12
C4.2 Settings after Upgrading ProSafe-RS

Software
This section describes the tasks and precautions required after upgrading the SENG soft-
ware.
Because the SCS databases and SCS system programs that SENG manages are basically
upward compatible, there is no need to modify the engineering data created with earlier ver-
sion software. However, in order to use the new features supported by the newer SCS system
program, re-creation of the SCS project or offline downloading of database to SCS may be
required after upgrading the SENG.
TIP For computers that do not have Adobe Acrobat installed, we recommend that you upgrade the software for
viewing online manuals to the recommended version of Adobe Acrobat Reader described in this manual.
SEE
ALSO For more information about configuration of Adobe Acrobat Reader, refer to:
B4.1, “Setting the Manual Browsing Environment” on page B4-2
For more information about release numbers of the SENG software in each software release and compatibili-
ty in inter-SCS safety communication between different revisions, refer to:
Appendix 6., “Compatibility between Revisions and Cautionary Notes for Upgrading” on page App.6-1

C4.2.1 Updating the engineering data after an upgrade

To maintain the use of existing engineering data after you upgrade the ProSafe-RS software,
you must upgrade the AD Server data, and upgrade the revision of the AD project data and
the RS project data before you start the engineering.
n Procedure for starting engineering

The following figure shows the procedure for starting engineering.
Start
Upgrade AD Server data
Upgrade the AD project
Upgrade the RS projects
End
Figure C4.2.1-1 Procedure for starting engineering
TIP For some steps in this procedure, upgrading may not be required. In this case, do not quit the engineering at
such a step and proceed to the next step.
n Upgrading the AD Server data

The following AD Server data should be upgraded:
• Back-up and restore history of the ADMDB
• Export and import history information of AD projects
• Option settings
To perform this task, use the ADS Administration Tool on the computer with AD Server.
l Upgrading the AD Server data

Follow these steps to upgrade the AD Server data:
1. Log on to the computer with AD Server. If the IT security model is the Standard model or
Strengthened model, log on as a member of the ADS_MANAGER or ADS_MANAG-
ER_LCL group.
2. Start the ADS Administration Tool.
If upgrading of the AD server data is required, the AD Server Data Upgrade Dialog Box
appears.
3. Click [OK].
Data upgrade starts. When the upgrade is complete, the Upgrade Complete Dialog Box
appears.
4. Click [Close AD Server Administration Tool].
The AD Server restarts to complete the data upgrade.

TIP Performing this task does not upgrade AD project data.
n Upgrading an AD project
You must upgrade the AD project data.
To perform this task, use AD Organizer on a computer with the safety system generation func-
tion.
If there are multiple computers with the safety system generation function, you can use any of
these computers.
l Upgrading an AD project
IMPORTANT
Before you upgrade an AD project, you must exit AD Organizer on all computers except for
the computer that you are about to upgrade.
Follow these steps to upgrade an AD project:

1. Log on to the computer with the safety system generation function as a user having rights
to modify all data in the AD project.
TIP During upgrade of an AD project, AD project files are checked out, updated, and checked in. If you log on as
a user who does not have modifying access rights, upgrade of the AD project fails with an error.
You must log on as a user whose user role is RS Lead Engineer and whose access scope is All Scope.
2. Start AD Organizer.
If upgrading of an AD project is required, the Upgrade dialog box appears.
3. Click [Yes].
The upgrade for the AD project starts. When the upgrade is complete, the Update Com-
plete dialog box appears.
IMPORTANT
While revision upgrade of the AD project proceeds, make sure that communication between
AD Server and AD Organizer is not interrupted. If the communication is interrupted, upgrade
of the AD project fails with an error.
When upgrading the AD project fails with an error due to an interruption, check to see if there
are any checked-out files in the AD project. If there are any, forcibly cancel the checked-out
status by using the ADS Administration Tool and start AD project upgrade again.
4. Click [OK].
SEE
ALSO For more information about how to check the Checked-out Status of AD project files, refer to:
C1.2.5, “Forcibly canceling the checked-out status of currently checked-out files” in Engineer's Refer-
ence Manual (IM 32P04B10-01EN)
n Upgrading an RS project
You can upgrade an RS project on a computer with the safety system generation function.

If there are multiple computers with the safety system generation function, perform the tasks
on any one of the computers.
l Upgrading an RS project
Follow these steps to upgrade an RS project:
1. Log on as a user with rights to modify the RS project.
For example, log on with the rights of a user whose user role is RS Lead Engineer or RS
Engineer.
2. Start AD Organizer.
3. Upgrade all SCS projects under the RS project.
4. In System Structure Navigator, select the RS project.
5. From the sub menu of System Structure Navigator, select [Back up].
6. Click [Yes].
The upgraded RS project is backed up.

C4.2.2 Upgrading an SCS project

After you install the latest revision on SENG or AD Server and upgrade an AD project and an
RS project, open SCS projects. The SCS projects are upgraded. Steps are described in the
following procedure A.
n Procedure A: Opening SCS Projects

Use SCS Manager to open an SCS project in an earlier revision. The SCS project is upgra-
ded.
You can upgrade the SCS project without interrupting SCS operation. The scope of online
changes is the same as the earlier revision.
IMPORTANT
• If you upgrade an SCS project, you must upgrade the SCS projects of all the SCSs that
perform inter-SCS safety communication with this SCS. Otherwise, an error may occur
during build.
• When opening a project of R4.05 or later, specify PRJlibrary.accdb. When opening a proj-
ect before R4.05, specify PRJlibrary.mdb. PRJlibrary.mdb is converted to PRJli-
brary.accdb by upgrading the revision.
• The SCS project created by an earlier revision cannot be opened in Read-Only mode.
Such SCS projects must be opened in Read-Write mode. To open the project with pass-
word, the password needs to be entered and then open the project in the Read-Write sta-
tus.
• It is necessary to use the newer revision SCS Manager at least once to open the library
created by older revision SCS Manager.
Follow these steps to call SCS Manager from AD Organizer:

1. In System Structure Navigator, select the SCS project you want to upgrade and select
[SCS Manager] from the context menu.
If upgrading of the SCS project is required, a dialog box appears, asking you whether to
upgrade the SCS project.
2. Click [Yes].
Upgrading of the SCS project starts. When the upgrade is complete, the Upgrade Com-
plete dialog box appears.
3. Click [OK].
SCS Manager starts, and the steps are completed.

C4.2.3 Cautionary notes for upgrading to R4.06

This section provides cautionary notes and actions required for a revision upgrade from R4.05
to R4.06. When you upgrade, also read the cautionary notes for upgrading to the previous
versions that were issued after the software version currently installed on your computer and
perform the required tasks for each upgrade.
IMPORTANT
When integrating ProSafe-RS with CENTUM VP, use the R6.08 or a later version of CENTUM
VP for the installation on the same computer.
In R4.01 or later, be sure to register the RS project in an AD project regardless of the engi-
neering method.
SEE
ALSO For more information about creating an AD project, refer to:
“■ Creating AD projects” in C1.2.1, “Creating and deleting AD projects” in Engineer's Reference Manual
(IM 32P04B10-01EN)
For more information about how to register RS projects in an AD project, refer to:
C1.2.3, “Registering RS projects in the AD project” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about cautionary notes when upgrading the revision to ProSafe-RS R4.05, refer to:
Appendix 6.6, “Cautionary Notes for Revision Upgrade to R4.05” on page App.6-17
For more information about the detailed operation procedure required after the revision upgrade, refer to:
C4.2.4, “Procedures for using new functions” on page C4-20
n Software revisions
The respective software release numbers of R4.06 are as follows:
Software release number R4.06.xx (*1)
• SENG software release number: R4.06.xx(*1)
• SCS system program release number: R4.06.xx (*1)
*1: The last two digits of the revision number will be changed in accordance with the software revisions after the release of
R4.06.00.
The database revision of an SCS project that is created by SENG with software release num-
ber R4.06.xx will be R4.06.00.
l Control bus drivers

The control bus drivers that are installed on the computer must be upgraded to the version
supplied in R4.06.
n Basic procedure for upgrading

To use the added or modified features, install the ProSafe-RS software R4.06 or later and
open the existing SCS projects (“Procedure A”).
SEE
ALSO For more information about operations of “Procedure A”, refer to:
“n Procedure A: Opening SCS Projects” on page C4-16

l Support of displaying the list of AD Suite work files

To use the displayed list of AD Suite work files, you must perform “Procedure A” on an SENG
of R4.06.
l Improved AD Suite functions

To use the following improved AD Suite functions, you must perform “Procedure A” on an
SENG of R4.06.
• Improved grid rule function
• Improved revision history function
• Improved functions of Safety I/O Editor, Safety Communication I/O Editor, Safety I/O Pa-
rameter Profile Editor, and IOM Definition Editor
l POU password
In iDefine 1.16.6 or later, you can set a password for POU. To refer to POU with SCS Manag-
er by using the POU password set in iDefine, you must perform “Procedure A” on SENG of
R4.06.
n Procedures for using added and modified features

The basic upgrading procedures are not enough to use the following features that have been
added or modified in R4.06. After you upgrade the SENG software to R4.06, you must per-
form offline download to the SCS and other operations. The following procedures are required
to use the new features.
SEE
ALSO For more information about operation “Procedure B” to “Procedure F” for using new functions, refer to:
l SCS supporting SIL2 (LISC70)

To use the SCS supporting SIL2 (LISC70), you must perform “Procedure C” on an SENG of
R4.06.
l Added system functions and function block

To use the system functions (NUMBITS_8/NUMBITS_16) and the system function block
(SYS_CH_OUTEN) added in R4.06, you need to perform “Procedure C” on an SENG of
R4.06. NUMBITS_8/NUMBITS_16 and SYS_CH_OUTEN cannot be used on SSC10 and
SSC60.
n Steps when an SCS project is already placed on another computer

such as a file server
If an SCS project is already placed on a file server PC that is different from the SENG PC,
files in the SCS project database may be corrupted while the SCS project is operated on the
SENG PC. When an SCS project is already placed on a PC such as a file server which is
different from the SENG PC that operates the SCS project, make sure to implement the
avoidance described in SEE ALSO to prevent file corruption in the SCS project database.
SEE
ALSO For more information about avoidance, refer to:

n Cautionary notes for upgrading when ALE111 is used

You must be careful when upgrading the system if ALE111 is used for Modbus slave or DNP3
communication.
SEE
ALSO For more information about the precautions when upgrading a system where ALE111 is used for Modbus
slave or DNP3 communication , refer to:
“n Cautionary Notes for Upgrading When ALE111 is Used” on page App.6-5

C4.2.4 Procedures for using new functions

This section describes the detailed operation procedures required after the revision upgrade,
which is described in the precautions for upgrade of each revision.
After upgrading the ProSafe-RS software, the following procedures need to be performed.
What procedure needs to be performed depends on what new features to be used. User
needs to run the following procedures in accordance with each guideline of the revision up-
grade procedure.
• Procedure B: Master Database Offline Download
• Procedure C: Creating New SCS Project and Offline Download
• Procedure D: Setting Definition Items for New Features and Offline Download
• Procedure E: Clean Project, Build, and Offline Download
• Procedure F: Setting Definition Items for New Features, Clean Project, Build, and Offline
Download
SEE
ALSO For more information about procedure A: opening SCS projects, refer to:
For more information about the procedures to use new features in each revision, refer to:
For more information about procedure of upgrading the system while maintaining the existing engineering da-
ta, refer to:
C4.2.1, “Updating the engineering data after an upgrade” on page C4-13
n Procedure B: Master Database Offline Download

For using the new features, this procedure may be necessary.
After upgrading the SENG, perform Master Database Offline Download to the SCS. Re-test-
ing of SCS application is not required.
The outline of the procedure is as follows:
1. Run Procedure A.
2. Offline download to the SCS using Master Database Offline Download.
SEE
ALSO For more information about the procedure of Master Database Offline Download, refer to:
I4.4, “Master database offline download” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
n Procedure C: Creating New SCS Project and Offline Download

For using the new features, this procedure may be necessary.
After upgrading SENG, create a new SCS project and remake the existing SCS project and
then offline download the SCS project.
The procedure is the same as creating a new SCS project. And it is roughly as follows:
1. Create a new project and enter all the project settings.
The existing SCS project can be upgraded to a later revision by using Import/Export func-
tions. Upgrading the SENG to a newer revision and creating a new SCS project, the
whole existing project data can be transferred to the new SCS project.

TIP If the new SCS project uses a library, the library must be opened by a new-revision SCS Manager. However,
if the library POU uses FB/FU supported only by a new revision, create a new library.
When you have upgraded an SENG, you must ensure that all SCS projects and library are of the same revi-
sion as the upgraded SENG.
Follow these steps to upgrade the revision of SCS and library:
1. Open each original library projects to upgrade. Then, copy the library to the predetermined folder, LI-
BRARIES, of the SCS project that uses the library.
2. Open each SCS project to upgrade.
If a project-level password is set for the SCS project or library, you have to enter the password and open it in
ReadWrite mode in order to upgrade. If you do not know the password, contact the creator of the SCS project
and library.
2. Run build, and check the project data using Integrity Analyzer/Cross Reference Analyzer.
3. Offline download the project.
IMPORTANT
The SCS project and library created by an SENG in a revision later than the currently used
revision cannot be used.
• The SCS project created or opened by a new revision of SENG cannot be opened by an
SENG in an earlier revision.
• The library created or opened by a new revision of SENG cannot be added to the SCS
project of an earlier revision.
SEE
ALSO For more information about the procedures for transferring the existing SCS project using Import/Export func-
tions, refer to:
E2., “Import/Export function” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about the procedure for migrating existing SCS projects engineered by I/O list engineer-
ing, refer to:
“■ Regenerating an SCS project with the new revision” in E3.3, “Data transfer procedure during SCS
project regeneration” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about areas in which re-testing is required after using the Import/Export function, refer
to:
“■ Confirming a regenerated project” in E3.3, “Data transfer procedure during SCS project regeneration”
in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
For more information about procedures for offline download, refer to:
“● Offline download process in I/O list engineering” in “■ Procedure for offline download” in C7., “Offline
download to the target SCS” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
n Procedure D: Setting Definition Items for New Features and Offline

Download
Some new features require this procedure.
Install the new revision of SENG software, set the definition items for the new features, and
offline download the project.
The procedure is as follows:
1. Using SCS Manager, open the old-revision project.
2. Set the definition items for the new features.

The items to be set are described in the section of upgrading procedures for each soft-
ware release number.
3. Run Build. Then use Integrity Analyzer and Cross Reference Analyzer for approval
check.
IMPORTANT
Even if all POUs are displayed in green in the result of checking by Cross Reference Ana-
lyzer, further check is required if Cross Reference Analyzer is unable to detect differences re-
lated to the definition items of the new features.

SEE
ALSO For more information about the items that cannot be detected by Cross Reference Analyzer, refer to:
“■ Other changes not detectable by Cross Reference Analyzer” in C5.2.5, “Precautions on Cross Refer-
ence Analyzer” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)
n Procedure E: Clean Project, Build, and Offline Download

After upgrading the SENG, run Clean Project and Build for the existing project, and offline
download the project.
2. Run Clean Project.
check. In the check using Cross Reference Analyzer, make sure that all POUs are dis-
played in green.
n Procedure F: Setting Definition Items for New Features, Clean

Project, Build, and Offline Download
This procedure consists of “Procedure D” plus Clean Project.
2. Set the definition items for the new features.
The items to be set are described in the section of upgrading procedures for each soft-
ware release number.
3. Run Clean Project.
check.

IMPORTANT
Even if all POUs are displayed in green in the result of checking by Cross Reference Ana-
lyzer, further check is required if Cross Reference Analyzer is unable to detect differences re-
lated to the definition items of the new features.

SEE
ALSO For more information about the items that cannot be detected by Cross Reference Analyzer, refer to:
“■ Other changes not detectable by Cross Reference Analyzer” in C5.2.5, “Precautions on Cross Refer-
ence Analyzer” in Engineering Guide Vol. 1 (IM 32P01C10-01EN)

<C4.3 Upgrading the Computer Dedicated to License Management > C4-24
C4.3 Upgrading the Computer Dedicated to

License Management
This section describes how to upgrade the computer dedicated to license management.
n Upgrade Procedure
1. When upgrading from R4.02 or earlier, set up Windows.
2. Install only the license management software from the ProSafe-RS software medium.
TIP When upgrading the computer dedicated to license management, you can install the license management
software in the same way as when it is installed for the first time. However, you are not required to enter the
following items because the data already set are applied.
• Name
• Company name
• Installation folder

4. When upgrading from R4.02 or earlier, configure Windows environment settings for each
user.
SEE
For more information about setting up Windows, refer to:
For more information about installing the license management software, refer to:
For more information about configuring Windows environment settings for each user, refer to:

<C5. Uninstalling the ProSafe-RS Software > C5-1
C5. Uninstalling the ProSafe-RS

Software
This section describes how to uninstall the ProSafe-RS software and network drivers. Proce-
dures are provided for the following two cases:
• Uninstallation on SENG
• Uninstallation on the computer dedicated to license management
Note, however, that uninstalling the ProSafe-RS software does not remove the project data-
base, user settings, registries, and so on. If you need to remove ProSafe-RS software com-
pletely, reinstall your operating system.

<C5.1 Uninstallation on SENG> C5-2
C5.1 Uninstallation on SENG

This section describes the procedures for uninstallation on SENG.

C5.1.1 Uninstalling the ProSafe-RS Software

If you uninstall the ProSafe-RS software, the license management software is also uninstal-
led. However, the license management data, IT Security Tool, and project data will not be de-
leted.
TIP The IT Security Tool is also used by YOKOGAWA products other than ProSafe-RS. Therefore, even if you
uninstall the ProSafe-RS software, the Start menu setting, programs and files of the IT Security Tool will not
be removed. To completely uninstall the IT Security Tool, you need to uninstall all the products that use the IT
Security Tool and then run the command for uninstalling the IT Security Tool.
n Deleting and Deactivating the Licenses

If there are any active licenses distributed on the SENG PC, delete the licenses to deactivate
the software packages before uninstalling the ProSafe-RS software.
SEE
ALSO For more information about how to deactivate software packages on a computer, refer to:
“■ Deleting a license from a license-assigned station” in 3.2.1, “Modifying license assignments” in Li-
cense Management Guide (IM 32P01C60-01EN)
n Uninstallation Procedure
After deactivating the packages (deleting the licenses), follow these steps to uninstall the
ProSafe-RS software:
2. Select [Programs] > [Programs and Features].
The Programs and Features window appears.
Figure C5.1.1-1 Programs and Features
3. Select [YOKOGAWA ProSafe-RS] and click [Change].

4. Click [Next].
A dialog box for confirming the uninstallation appears.
5. Click [Remove].
Uninstallation starts and a dialog box showing the progress of uninstallation appears.

TIP If any active license is found, a dialog box appears confirming the continuation of the uninstallation process.
Select [Yes] to continue the uninstallation. The active licenses are deactivated at this point.
However, the license information on the license management station remains unchanged. Update the license
information on the license management station as necessary.
6. If a User Account Control dialog box appears, click [Yes] or [Allow].

TIP If you leave the User Account Control dialog box without clicking [Yes] or [Allow], the dialog box closes auto-
matically. Then, a dialog box indicating failure of uninstallation appears, and the uninstallation is discontinued.
In this case, run the uninstallation again.
7. In the uninstallation complete dialog box that appears upon completion of the uninstalla-
tion, do either of the following operations.:
• To restart the computer now, select [Yes, I want to restart my computer now.] and
click [Finish].
• To restart the computer later, select [No, I will restart my computer later.] and click
[Finish].

C5.1.2 Uninstalling the Network Drivers

This section describes how to uninstall the network drivers.
n Disabling the Control Bus Driver (Windows 10)

In Windows 10, before you uninstall the control bus driver, be sure to disable the control bus
driver.
Follow these steps to disable the control bus driver:
3. Select [Network and Internet] > [Network and Sharing Center].
The Network and Sharing Center window appears.
4. Select [Change adapter settings].
The Network Connections window appears.
5. Right-click [Yokogawa Vnet Adapter] and select [Disable].
An error dialog box regarding disabling connection appears.
6. Click [OK].
8. Perform steps 1 to 4.
9. In the Network Connections window, confirm that the Vnet driver is disabled.
TIP If the control bus driver is not disabled, perform the procedure from step 2 again.
n Uninstalling Control Bus Driver

Follow these steps to uninstall the control bus driver:
2. Terminate all applications that are running.
3. Set the ProSafe-RS software medium in the drive.
4. Click [Control Bus Driver].
The following dialog box appears.

Figure C5.1.2-1 Setup Selection Dialog Box
5. Select [UNINSTALL] and then click [OK].

A dialog box appears, confirming the uninstallation.
6. Click [OK].
The uninstallation starts.
tion, click [OK].
IMPORTANT
After uninstalling the driver, run the TCP/IP Inconsistency Detection Tool.
If any inconsistency is detected, use the TCP/IP Inconsistency Repair Tool and then configure
the TCP/IP settings again.
SEE
fer to:
n Uninstalling the Vnet/IP Open Communication Driver

Follow these steps to uninstall the Vnet/IP open communication driver:
3. Set the ProSafe-RS software medium in the drive.
4. Click [Vnet/IP Open com driver].
The following dialog box appears.

Figure C5.1.2-2 Setup Selection Dialog Box
5. Select [UNINSTALL] and then click [OK].

6. Click [OK].
tion, click [OK].
IMPORTANT
SEE
fer to:
n Uninstalling the Vnet/IP Interface Package on a Virtual Machine

Follow these steps to uninstall the Vnet/IP Interface Package:
The procedures explained here should be performed on the guest OS of the virtual machine.
IMPORTANT
• If multiple products coexist in the virtual machine, if you uninstall the license product with
the Vnet/IP Interface Package enabled, after restarting the virtual machine, Vnet/IP com-
munication cannot be performed from other products.
• Unlike computers with a Vnet/IP interface card installed, if you uninstall the Vnet/IP Inter-
face Package from a virtual machine, the virtual machine results in a Station Fail status
immediately.

l Procedure 1: Uninstall the Vnet/IP Interface Package

Follow these steps to uninstall the Vnet/IP Interface Package:
3. Sign out from the guest OS on the virtual machine.
5. Copy an ISO format file of the ProSafe-RS software medium and paste it into a folder on
the host OS.
nect].
full-screen.
10. Click [Media] > [DVD Drive] > [Insert Disk].

11. Select the copied ISO format file of the ProSafe-RS software medium and click [Open].
er.exe in the folder where the ISO format file of the ProSafe-RS software is stored.
A setup selection dialog box appears.
13. Select [UNINSTALL] and click [OK].
14. Click [OK].
tion, click [OK].
16. Restart the virtual machine.
IMPORTANT

SEE
fer to:
l Procedure 2: Disable the RIP Listener Service

This section describes how to disable the RIP Listener service.
IMPORTANT
Disabling of the RIP Listener service may fail when the Default Authentication Level of DCOM
is configured to [None]. In this case, change to [connection].
Follow these steps to disable the RIP Listener service on Windows Server 2016:
2. Run the Command Prompt as Administrator.
3. Run the following command:
dism /online /disable-feature /featurename:rasrip
4. Confirm that the message, “The operation completed successfully.” appears.
SEE
ALSO For more information about how to change the default authentication level of DCOM to “Connect”, refer to:
“n DCOM Settings” on page B3-15

<C5.2 Uninstallation on the computer Dedicated to License Management > C5-10
C5.2 Uninstallation on the computer Dedicated

to License Management
This section describes the procedure for uninstalling the license management software on the
computer dedicated to license management.
n Running the Uninstallation

Follow these steps to uninstall the license management software:
3. Select [Programs] > [Programs and Features].
The Programs and Features window appears.
4. From the program list, select [YOKOGAWA ProSafe-RS] and click [Change].
5. Click [Next].
A dialog box for confirming the uninstallation appears.
6. Click [Delete].
Uninstallation starts and a dialog box showing the progress of uninstallation appears.
tion, do either of the following operations.:
• To restart the computer now, select [Yes, I want to restart my computer now.] and
click [Finish].
• To restart the computer later, select [No, I will restart my computer later.] and click
[Finish].

<C6. Reinstalling the ProSafe-RS Software> C6-1
C6. Reinstalling the ProSafe-RS

Software
This section describes how to reinstall the ProSafe-RS Software. The procedures are ex-
plained for the cases when changing and not changing the computer to be used. For each
case, the reinstallation procedure is explained for license-assigned stations and for the li-
cense management station.

<C6.1 When the Computer Used is the Same > C6-2
C6.1 When the Computer Used is the Same

This section describes the procedure for reinstalling the ProSafe-RS software to restore the
software when the installed file gets damaged or deleted accidentally. The assumption is that
the computer on which the software is to be installed is the same as before.
The software cannot be reinstalled by overwriting the software already installed. You must first
uninstall the ProSafe-RS software and install the ProSafe-RS software again.
n Reinstallation for a License-Assigned Station

This section describes the reinstallation procedure for a license-assigned station.
The flow of reinstallation is as follows.
Start
Reinstallation
Uninstall
Install
Configure IT Security Settings
Redistribute Licenses from

License Management Station
Configure Function-Specific
Settings
Finish
Reinstallation
Figure C6.1-1 Flow of Reinstallation for a License-Assigned Station
l Uninstall the ProSafe-RS Software

Uninstall the ProSafe-RS software.
SEE
ALSO For more information about uninstallation procedure, refer to:
C5.1.1, “Uninstalling the ProSafe-RS Software” on page C5-3
l Install the ProSafe-RS Software

Install the ProSafe-RS software.
SEE
l Configure IT Security Settings

Configure IT security settings in the same way as that for a new installation of the ProSafe-RS
software.

SEE
l Redistribute Licenses from the License Management Station

Redistribute the licenses from the license management station.
SEE
ALSO For more information about redistributing licenses from the license management station, refer to:
3.4, “Redistributing licenses to license-assigned stations” in License Management Guide (IM
32P01C60-01EN)
l Configure Function-Specific Settings

Configure the settings specific to the functions that run on the SENG.
SEE
n Reinstallation for the License Management Station

This section describes the reinstallation procedure for the license management station. The
license management station can be a computer installed with the ProSafe-RS software or a
computer dedicated to license management, where only the license management software is
installed. You need to perform reinstallation according to the type of the license management
station.

Start
Reinstallation
Back Up License Project (*1)
Uninstall
Install
Yes Are License

Projects Displayed in
License Manager?
No
Restore License Project
Redistribute Licenses to
License-assigned Stations (*2)
Settings (*2)
Finish
Reinstallation
*1: If the license project backup is already created, this task is not required.
*2: These tasks are not required for the computer dedicated to license management.
Figure C6.1-2 Flow of Reinstallation for the License Management Station
l Back Up the License Projects

Back up the license projects managed on the computer.
SEE
ALSO For more information about the procedure for backing up license projects, refer to:
3.6, “Backing up and restoring a license project” in License Management Guide (IM 32P01C60-01EN)
l Uninstall the ProSafe-RS Software

Uninstall the ProSafe-RS software. For a computer dedicated to license management, unin-
stall the license management software.
SEE
ALSO For more information about the procedure for uninstallation on an SENG PC, refer to:
C5.1, “Uninstallation on SENG” on page C5-2
For more information about the procedure for uninstallation on the computer dedicated to license manage-
ment, refer to:
C5.2, “Uninstallation on the computer Dedicated to License Management” on page C5-10

l Install the ProSafe-RS Software

Install the ProSafe-RS software. For a computer dedicated to license management, install the
license management software.
SEE
For more information about how to install the license management software, refer to:
l Configure IT Security Settings

Configure IT security settings in the same way as that for a new installation of the ProSafe-RS
software.
SEE
l Restore the License Projects

Start the License Manager and then check if license projects are displayed. If not displayed,
you need to restore the license projects from the backup.
SEE
ALSO For more information about the procedure for restoring license projects, refer to:
“■ Restoring a license project in another license management station” in 3.6, “Backing up and restoring a
license project” in License Management Guide (IM 32P01C60-01EN)
l Redistribute Licenses to License-Assigned Stations

Redistribute the licenses to the license-assigned stations.
SEE
32P01C60-01EN)
l Configure Function-Specific Settings

Configure the settings specific to the functions that run on the SENG.
SEE

<C6.2 When the Computer Used is Not the Same > C6-6
C6.2 When the Computer Used is Not the Same

This section describes the procedure for reinstallation on a different computer when the com-
puter installed with the ProSafe-RS software can no longer be used due to damage or other
reasons.
n Reinstallation for a License-Assigned Station

This section describes the reinstallation procedure for a license-assigned station.
The procedure is the same as that for a new setup of SENG except that you need to restore
the data that were backed up.
Start
Reinstallation
Set Up the Hardware
Set Up Windows
Set Up the Network
Install
Restore Backed Up Data
Redistribute Licenses from

License Management Station
Create User Accounts
Configure Windows Environment

Settings for Each User
Set Up UPS Service
Configure Function-Specific Settings
Set Up for Connection with

Other Systems
Finish
Reinstallation
Figure C6.2-1 Flow of Reinstallation for a License-Assigned Station

IMPORTANT
For the station name of the new computer, specify the same name as that set on the previous
computer.
SEE
ALSO For more information about the procedures for a new setup of SENG, refer to:
• B3., “Setup of an SENG or a Computer Installed with Only AD Server” on page B3-1
• B4., “Configuring the Functions Specific to SENG” on page B4-1
• D1., “Connecting YOKOGAWA products” on page D1-1
l Restore the Backed Up Data

Restore the backed up data on the new computer.
SEE
ALSO For more information about the backed up data, refer to:
C3., “Backing Up the System” on page C3-1
n Reinstallation for the License Management Station

The license management station can be a computer installed with the ProSafe-RS software or
a computer dedicated to license management. You need to perform reinstallation according to
the type of the license management station.
The procedure is the same as that for a new setup except that the following tasks are in-
volved:
• Back up license projects
• Restore the backed up data
• Restore the license projects
• Redistribute licenses to the license-assigned stations

Start
Reinstallation
Back Up License Project
Set Up the Hardware (*1)
Set Up Windows (*1)
Set Up the Network (*1)
Install
Restore Backed Up Data
Restore License Project
Redistribute Licenses to
License-assigned Stations (*1)
Create User Accounts (*1)
Configure Windows Environment

Settings for Each User (*1)
Set Up UPS Service (*1)
Settings (*1)
Set Up for Connection with

Other Systems (*1)
Finish
Reinstallation
*1: For the computer dedicated to license management, these tasks are not required
or may be omitted according to the circumstances.
Figure C6.2-2 Flow of Reinstallation for the License Management Station
IMPORTANT
For the station name of the new computer, specify the same name as that set on the previous
computer.

SEE
ALSO For more information about the procedures for a new setup of SENG, refer to:
• B3., “Setup of an SENG or a Computer Installed with Only AD Server” on page B3-1
• B4., “Configuring the Functions Specific to SENG” on page B4-1
• D1., “Connecting YOKOGAWA products” on page D1-1
For more information about the procedure for a new setup of a computer dedicated to license management,
refer to:
l Back Up the License Projects

Back up the license projects managed on the previous computer.
SEE
ALSO For more information about procedures for backing up license projects, refer to:
3.6, “Backing up and restoring a license project” in License Management Guide (IM 32P01C60-01EN)
l Restore the Backed Up Data

Restore the backed up data on the new computer.
SEE
ALSO For more information about the backed up data, refer to:
C3., “Backing Up the System” on page C3-1
l Restore the License Projects

Restore the license projects from the backup.
SEE
ALSO For more information about the procedure for restoring license projects, refer to:
“■ Restoring a license project in another license management station” in 3.6, “Backing up and restoring a
license project” in License Management Guide (IM 32P01C60-01EN)
l Redistribute Licenses to License-Assigned Stations

Redistribute licenses to the license-assigned stations.
SEE
32P01C60-01EN)

<C7. Troubleshooting> C7-1
C7. Troubleshooting
This section describes the causes of and remedies for problems that may occur.

<C7.1 Windows Related Troubleshooting> C7-2
C7.1 Windows Related Troubleshooting

This section describes how to handle problems related to Windows.
n Note on User Account Control

If you log on as a non-administrative user and try to start the installer, the User Account Con-
trol dialog box appears. Click [No] and log on again as an administrative user, and then start
the installer again.
n The System Locks Up

Contact YOKOGAWA service.
n Computer Operation Becomes Unstable

If the operation of the computer that was working normally has become unstable, do the task
described below.
l Cause
Incompatible software was installed.
l Remedy
Uninstall the incompatible software you have installed.
SEE
ALSO For more information about software that can coexist with ProSafe-RS, refer to:
“● Software that can coexist with ProSafe-RS” in “■ Software requirements for SENG” in A1.2, “Software
requirements” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

<C7.2 Troubleshooting Related to Network> C7-3
C7.2 Troubleshooting Related to Network

This section describes how to handle problems related to the network.

C7.2.1 Precaution on Network Cable Connection

With Windows 10 and Windows Server 2016, a network charm bar may appear from the right
side of the desktop when the cable is wired. If it appears, select [No].
Figure C7.2.1-1 Network Charm Bar

C7.2.2 Problems Related to Installation and Deletion of

Drivers
This section provides troubleshooting related to the installation and deletion of network driv-
ers.
IMPORTANT
Some operations require administrative rights, and a User Account Control dialog box may
appear when you try to do such operations. You can continue with the operation by clicking
[Yes], [Continue], or [Allow] (if the user has administrator rights).
n Confirming Installation Result

Check if the network driver is properly installed. If the driver is not operating property, install it
again.
l Adapter Driver for Control Bus Driver

When the control bus driver is added, the adapter driver “Yokogawa Vnet Adapter” appears
under Network Adapters on Device Manager.
If the adapter driver does not start properly, "!" appears on the adapter driver icon.
Follow these steps to display Device Manger:

Figure C7.2.2-1 Adapter Driver Added Properly
l Protocol Driver for Control Bus Driver (Windows 10, Windows Server 2016)
When the control bus driver is added, the protocol driver is installed together with the adapter
driver.
The operating condition of the protocol driver can be checked in Command Prompt.
Follow these steps to check the operating condition of the protocol driver:
1. Sign in as a general user or administrative user.
3. Enter sc query VLTDI, and then press the [Enter] key.
The condition of the protocol driver is shown. If RUNNING is shown under STATE, the
driver is operating properly.

Figure C7.2.2-2 Protocol Driver Operating Properly
l Vnet/IP Open Communication Driver

When the driver is added, “Vnet/IP Open Communication Driver (BUS2)” appears in Network
Adapters in Device Manager.
If the driver does not start successfully, the “!” symbol appears next to the network adapter
icon.
Follow these steps to display Device Manger:

Figure C7.2.2-3 Adapter Driver Added Properly
n Control Bus Driver is Successfully Installed but Does Not Start

The control bus driver may not start normally due to wrong connection of the bus cables or
mistakes in address setting. In this case, VLNIC errors are recorded in the System log of
Event Viewer.

Figure C7.2.2-4 Event Viewer Recording VLNIC Errors (System)
1. Double-click a VLNIC error.

The Event Properties dialog box appears.
Select “Friendly View” Error code
Figure C7.2.2-5 Event Properties
2. Look up the error code in the following table. If the problem is caused by the bus configu-
ration and/or address setting, make sure that the settings are correctly made and shut
down the computer. Then start up the computer again.
Table C7.2.2-1 Error Codes Generated when Starting the Driver

Code (*1) Meaning
000101** RAM parity error (failure of VF702/VF701/VI702/VI701 card)

Table C7.2.2-1 Error Codes Generated when Starting the Driver (Table continued)
Code (*1) Meaning
000102** RAM read/write error (failure of VF702/VF701/VI702/VI701 card)
000109** Address overlap error
00010a** Bus configuration error (wrong bus connector connection)
00010b** Dip switch station number parity error
00010c** Dip switch domain number parity error
00010d** Inappropriate dip switch station number setting
00020013 Illegal station number (may be detected in the case of bus connector connection mis-
takes)
*1: In the code, a 2-digit number 00 is displayed at the position of ** for VF702/VF701 while others for VI702/VI701.
If the driver still does not start, other possible causes may be a failure of the control bus inter-
face card or Vnet/IP interface card, or conflicts with other devices.
Replace the control bus interface card or Vnet/IP interface card, or remove the other devices
from the computer.
n Duplicate Instances of the Installer

You cannot start two instances of the installer. If you start a second instance, a warning mes-
sage appears. Click [OK] and terminate the installer you started later.
The processing of the installer started first continues.
n Error Message is Displayed during Network Driver Installation – 1

If an error message is displayed when you click [Don't Install] in the Windows Security dialog
box that appears during installation of a network driver, perform the following tasks.
Figure C7.2.2-6 Windows Security Dialog Box (for Network Adapter)
Figure C7.2.2-7 Error Message (for Network Adapter)

l Control Bus Driver

1. After restarting the computer, click [Control Bus Drier] on the installation menu.
2. If the control bus driver can be deleted, delete it and then restart the computer.
3. Install the control bus driver again.

Start the installer again.

If an error message is displayed when you did not click [Do not install] in the Windows Securi-
ty dialog box (for confirming installation of the network protocol or network adapter) that ap-
pears during installation of a network driver, perform the following tasks.

1. After restarting the computer, click [Control Bus Driver] on the installation menu.
2. Perform either of the following operations:
• If the control bus driver can be deleted, delete it and restart the computer. Then, in-
stall the driver again.
• If the control bus driver cannot be deleted, restart the computer and install the driver
again.

1. Start the installation menu again and click [Vnet/IP Open Communication Driver].
2. Perform either of the following operations:
• If the driver can be deleted, delete it and restart the computer. Then, install the driver
again.
• If the driver cannot be deleted, restart the computer and install the driver again.

Previously functioning Ethernet communications may fail, generating an error message.
l Cause
• Hardware, such as the Ethernet adapter card and Ethernet cable, is not connected prop-
erly.
• The network binding is not correctly set.
• The TCP/IP communication settings are not correct (IP address, subnet mask, etc.)
l Remedy
• Check the hardware, Ethernet adapter card, and the Ethernet cable.
• In Control Panel, check the “Network and Sharing Center” settings.

n Restarted the Computer After Deleting the Driver without Removing

the Control Bus Interface Card or Vnet/IP Open Interface Card from
the Computer
The actions you should take are described for the control bus driver and for the Vnet/IP open
communication driver.

If you restart the computer after deleting the control bus driver without removing the control
bus interface card from the computer, Windows judges that the control bus interface card is a
newly added device and displays the following dialog box.
Figure C7.2.2-8 Found New Hardware Dialog Box
Click [Ask me again later] here. Then, if you do not install the control bus driver, shut down
the computer and remove the control bus interface card.

If you restart the computer after deleting the Vnet/IP open communication driver without re-
moving the Vnet/IP interface card from the computer, Windows judges that the Vnet/IP inter-
face card is a newly added device and prompts you to install the driver for it.
In this case, ignore the prompting message and do not install the driver.

<D. Connection with Other Products> D-1
D. Connection with Other Products

ProSafe-RS can be connected with YOKOGAWA products, such as CENTUM VP, PRM, and
Exaquantum.
When connecting to these products, you may need to change the IT security settings.
This section describes the information and procedures on how to connect various products af-
ter installation.

<D1. Connecting YOKOGAWA products> D1-1
D1. Connecting YOKOGAWA products

This section describes the settings that are required to connect YOKOGAWA products.
For each connection case, an integration code is assigned. You must perform the tasks that
are required for the corresponding integration code of your connection case.
IMPORTANT
• Ensure that the security model and the user management type of the products that you
are connecting are the same.
• If the Strengthened model is applied to the products that you want to connect, contact
YOKOGAWA.
SEE
ALSO For more information about security models, user management types, users and groups, and security set-
tings, refer to:
n Integration code
The format of the integration code is as follows:
(Package code 1) - (Package code 2) - (Integration type) - (Revision number)
The following table describes the elements of an integration code.
Table D1-1 Integration code elements

Element Description
Package code The code that is assigned to a software package that can be installed independ-
ently on a computer.
First package code is the package code of product 1, and Second package code is
the package code of product 2.
Integration type The connection setup of various products. The possible values are:
• 01: When products are installed and operated on the same computer, and they
cannot communicate or share files with each other.
• 02: When products are installed and operated on separate computers, and they
can communicate or share files with each other.
• 03: When products are installed and operated either on the same computer or
on separate computers, and they can function together by communicating or
sharing files with each other.
Revision number The version or revision number of the products that you want to connect.
When the required connection procedures change on release of new versions or
revisions, this revision number is incremented.
The revision number can be from 01 to 99.

<D1. Connecting YOKOGAWA products> D1-2
IMPORTANT
• You cannot install two products that have integration type 02 on the same computer.
• In the user's manuals of a product, the settings that are required to connect with other
products are explained. However, information about the settings for connection that is
provided in the user's manuals may be inconsistent between the connected products. The
reason is that different products are released at different timings. To get the latest infor-
mation, refer to the user's manuals of both products to check the product version number
and the revision number of the integration code for their combination, and use the most
recent setting procedure.
l Package codes
The following table describes the package codes of various YOKOGAWA products.
Table D1-2 Package codes

Package code Product Package
0101 CENTUM VP CENTUM VP Standard Operation and Monitoring Function (*1)
0102 CENTUM VP System Builder Function
0108 CENTUM VP Report Package
0121 CENTUM VP Engineering Server Function
0153 CENTUM VP SOE Viewer Package
0196 CENTUM VP Project Database
0201 ProSafe-RS Safety System Engineering and Maintenance Function
0202 ProSafe-RS SOE OPC Interface Package
0203 ProSafe-RS CENTUM VP Integration Package
0204 ProSafe-RS CI Server Integration Package
0205 ProSafe-RS Engineering Server Function
0251 ProSafe-RS SOE Viewer Package
0252 ProSafe-RS iDefine for ProSafe-RS
0253 ProSafe-RS Forced I/O Viewer Package
0296 ProSafe-RS Project Database
0299 ProSafe-RS License Manager
0301 PRM Plant Resource Manager Field Communications Server
0302 PRM Plant Resource Manager Server
0351 PRM Plant Resource Manager DeviceViewer
0352 PRM PRM Client
0401 Exaopc Exaopc OPC Interface Package
0801 Exaquantum PIMS Server
0851 Exaquantum Explorer Client
1202 STARDOM STARDOM FCN/FCJ OPC Server
*1: As an optional function for this package, Exaopc OPC Interface Package (for HIS) is available. Consolidated Alarm Manage-
ment Function (CAMS for HIS) is included in Standard Operation and Monitoring Function.

<D1.1 CENTUM VP and ProSafe-RS > D1-3
D1.1 CENTUM VP and ProSafe-RS

This section describes the settings when connecting CENTUM VP and ProSafe-RS.
IMPORTANT
• When you install CENTUM VP and ProSafe-RS on the same computer, ensure that the
software revision of CENTUM VP is R6.08.00 or later and the software revision of
ProSafe-RS is R4.06.00 or later.
• Linked domain management is supported by CENTUM VP R6.08.00 or later and
ProSafe-RS R4.06.00 or later software revisions.

D1.1.1 CENTUM VP Standard Operation and Monitoring

Function and ProSafe-RS Safety System
Engineering and Maintenance Function
By connecting CENTUM VP Standard Operation and Monitoring Function and ProSafe-RS
Safety System Engineering and Maintenance Function, you can use CENTUM integration
function of ProSafe-RS.
n Using CENTUM integration function of ProSafe-RS

The following table shows the connection information. For required procedures for connec-
tion, read the descriptions that follow the table.
Table D1.1.1-1 Connection information

Integration code 0101-0201-03-05
Product 1 Standard Operation and Monitoring Function of CENTUM VP R5.01 or later (*1)
Product 2 Safety System Engineering and Maintenance Function of ProSafe-RS R3.01 or later
(*1)
Security model Legacy model Standard model
User manage- - Standalone management Domain/Combination/Linked do-
ment type main management (*2)
Required proce- None Refer to "● When the Standard model is applied."
dures
*1: When you install CENTUM VP and ProSafe-RS on the same computer, ensure that the software revision of CENTUM VP is
R6.08.00 or later and the software revision of ProSafe-RS is R4.06.00 or later.
*2: Linked domain management is supported by CENTUM VP R6.08.00 or later and ProSafe-RS R4.06.00 or later software revi-
sions.
l When the Standard model is applied

For Standalone management, perform this setting on the computer where the ProSafe-RS
safety system engineering and maintenance function is used and the computer where the
CENTUM VP standard operation and monitoring function is used. For Domain, Combination,
or Linked domain management, perform this setting on the domain controller.
1. Add the ProSafe-RS user account to CENTUM VP groups according to the following ta-
ble.
Table D1.1.1-2 ProSafe-RS groups and their corresponding CENTUM VP groups

ProSafe-RS group CENTUM VP group
PSF_MAINTENANCE CTM_MAINTENANCE or CTM_MAINTENANCE_LCL
PSF_MAINTENANCE_LCL CTM_MAINTENANCE or CTM_MAINTENANCE_LCL
PSF_ENGINEER CTM_ENGINEER and CTM_ENGINEER_ADM
PSF_OPERATOR CTM_OPERATOR
PSF_OPC CTM_OPC or CTM_OPC_LCL
PSF_OPC_LCL CTM_OPC or CTM_OPC_LCL
PSF_UTL None
2. Add the CENTUM VP user account to ProSafeRS groups according to the following table.

Table D1.1.1-3 CENTUM VP groups and their corresponding ProSafe-RS groups
CENTUM VP group ProSafe-RS group
CTM_MAINTENANCE PSF_MAINTENANCE or PSF_MAINTENANCE_LCL
CTM_MAINTENANCE_LCL PSF_MAINTENANCE or PSF_MAINTENANCE_LCL
CTM_ENGINEER PSF_ENGINEER
CTM_ENGINEER_ADM PSF_ENGINEER
CTM_OPC PSF_OPC or PSF_OPC_LCL
CTM_OPC_LCL PSF_OPC or PSF_OPC_LCL
SEE
ALSO For more information about how to create user accounts and add them to groups in Domain, Combination, or
Linked domain management, refer to:
For more information about how to create user accounts and add them to groups in Standalone management,
refer to:
B3-56


Function and ProSafe-RS SOE Viewer Package
By connecting CENTUM VP Standard Operation and Monitoring Function and ProSafe-RS
SOE Viewer Package, you can view historical information of CENTUM VP HIS on ProSafe-
RS SOE Viewer.
n Viewing Historical Information of CENTUM VP on ProSafe-RS SOE

Viewer

Product 2 SOE Viewer Package of ProSafe-RS R3.01 or later (*1)
dures
sions.

For Standalone management, perform this setting on the computer where ProSafe-RS SOE
Viewer is used. For Domain, Combination, or Linked domain management, perform this set-
ting on the domain controller.
• When enabling collaboration with products installed on the same computer
Add the user account for using ProSafe-RS SOE Viewer to the CTM_OPERATOR group.
• When enabling collaboration with products installed on different computers
Register the user account for using ProSafe-RS SOE Viewer to the computer where
CENTUM VP HIS runs. The user name and password of the user account to be regis-
tered must be the same as those of the user account that uses ProSafe-RS SOE Viewer.
Add the registered user account to CTM_OPERATOR group.
SEE
refer to:
B3-56

D1.1.3 CENTUM VP SOE Viewer Package and ProSafe-RS

Safety System Engineering and Maintenance
Function
By connecting CENTUM VP SOE Viewer Package and ProSafe-RS Safety System Engineer-
ing and Maintenance Function, you can view SOE events of ProSafe-RS on CENTUM VP
SOE Viewer.
n Viewing SOE events of ProSafe-RS on CENTUM VP SOE Viewer


Product 1 SOE Viewer Package of CENTUM VP R5.01 or later (*1)
(*1) (*2)
User manage- N/A Standalone management Domain/Combination/Linked do-
dures
*2: The ProSafe-RS software package licenses are not required.
sions.

Add the user account for using CENTUM VP SOE Viewer to the PSF_OPERATOR group.
For Standalone management, perform this setting on the computer where CENTUM VP SOE
Viewer is used. For Domain, Combination, or Linked domain management, perform this set-
ting on the domain controller.
SEE
refer to:
B3-56


Function and ProSafe-RS SOE OPC Interface
Package
This section explains the required settings when Exaopc OPC Interface Package (for HIS) of
CENTUM VP and SOE OPC Interface Package of ProSafe-RS are installed on the same
computer.
If the computer installed with both packages comes under either of the following cases, per-
form all the procedures explained for each case.
• The computer installed with both packages is designated as the OPC server for OPC
communication.
• The computer installed with both packages uses OPC client services.
• In a Domain, Combination, or Linked domain management system, the computer instal-
led with both packages is designated as the OPC server on an OPC client computer that
is not a member of the domain.
n When the computer installed with both packages is designated as

the OPC server to communicate with

Product 2 SOE OPC Interface Package of ProSafe-RS R3.01 or later (*1)
User manage- - Standalone management Domain/Combination/Linked domain
ment type management (*2)
dures
sions.

On the OPC server computer, add the user account for using OPC client services on OPC
client computers to the CTM_OPC and PSF_OPC groups.
For Domain, Combination, or Linked domain management, perform this setting task on the
domain controller. For Standalone management, create on the OPC server computer a user
account with the same name as the local user who uses OPC client services on the OPC cli-
ent computer, and add the user account to the CTM_OPC and PSF_OPC groups.
SEE
refer to:
B3-56

l Users who use OPC client services

The following table shows the users who use OPC client services:
Table D1.1.4-2 Users who use OPC client services

OPC client service User
Report Package User who logged on to Windows
Access Administrator Package (FDA:21 CFR Part 11 User who logged on to Windows
compliant)
OPC client other than CENTUM VP product.(*1) Users who use OPC client services
*1: Functions created using CENTUM Data Access Library are also included.
n When the computer installed with both packages uses OPC client
services

Product 2 SOE OPC Interface Package of ProSafe-RS R3.01 or later (*1)
dures
sions.

Add the user account for using OPC client services to the CTM_OPC and PSF_OPC groups.
For Standalone management, perform this setting on OPC client computers. For Domain,
Combination, or Linked domain management, perform this setting on the domain controller.
SEE
refer to:
B3-56
l Users who use OPC client services

The following table shows the users who use OPC client services:

Table D1.1.4-4 Users who use OPC client services
Access Administrator Package (FDA:21 CFR Part 11 User who logged on to Windows
compliant)
FCS Data Setting/Acquisition Package (PICOT) User who logged on to Windows
Consolidated Alarm Management Function (CAMS User that was specified when setting up the OPC
for HIS) A&E server connection
OPC client other than CENTUM VP product (*1) Users who use OPC client services
l When FCS Data Setting/Acquisition Package (PICOT) is used

If FCS Data Setting/Acquisition Package (PICOT) (LHS6710) and HIS type single sign on are
used, also perform the following setting:
For Standalone or Linked do- On the computer running the package, add OFFUSER to
main management: the PSF_OPC group.
For Domain or Combination On the computer running the package, add OFFUSER to
management: the PSF_OPC_LCL group.
n When the computer installed with both packages is designated as

the OPC server to communicate with on the OPC client computer
that is not a member of the domain
The following table shows the connection information for the case where Domain or Combina-
tion management is applied and the computer installed with both packages is designated as
the OPC server on the OPC client computer that is not a member of the domain. For required
procedures for connection, read the descriptions that follow the table.

Product 2 ProSafe-RS SOE OPC Interface Package of ProSafe-RS R3.01 or later (*1)
Security model Standard model
User management type Domain/Combination/Linked domain management (*2)
Required procedures Refer to "● Required procedures for connection."
sions.
l Required procedures for connection

On the OPC server computer, create a user account with the same name as the local user
who performs OPC communication on the OPC client computer, and then add the user ac-
count to the following groups.
For Domain or Combination management: CTM_OPC_LCL and PSF_OPC_LCL groups
For Linked domain management: CTM_OPC and PSF_OPC groups

SEE
ALSO For more information about how to create user accounts and add them to groups in Standalone management,
refer to:
B3-56
For more information about how to create user accounts and add them to groups in Domain, Combination, or
l Local Users Who Use OPC Client Service

The following table shows the local users who use OPC client services:
Table D1.1.4-6 Local Users Who Use OPC Client Service

OPC client other than CENTUM VP product (*1) Users who use OPC client services


Function and ProSafe-RS Forced I/O Viewer Package
You can use ProSafe-RS Forced I/O Viewer Package on a computer where CENTUM VP
Standard Operation and Monitoring Function is installed.
TIP You cannot install ProSafe-RS Forced I/O Viewer Package on a computer where ProSafe-RS Safety System
Engineering and Maintenance Function is installed.
n Viewing the ProSafe-RS forced-I/O information

The following table describes the connection information. This table also describes the infor-
mation for connecting with other CENTUM VP packages.

The same applies to the following combinations:
0102-0253-01-02, 0108-0253-01-02, 0109-0253-01-02, 0110-0253-01-02,
0111-0253-01-02, 0112-0253-01-02, 0113-0253-01-02, 0114-0253-01-02,
0118-0253-01-02, 0119-0253-01-02, 0120-0253-01-02, 0121-0253-01-02,
0152-0253-01-02, 0153-0253-01-02, 0199-0253-01-02
Product 1 Standard Operation and Monitoring Function of CENTUM VP R6.06 or later
(*1)
Product 2 Forced I/O Viewer Package of ProSafe-RS R4.05 or later (*1)
User management type - Standalone manage- Domain/Combination/
ment Linked domain manage-
ment (*2)
Required procedures Read the reference that follows the table.
sions.
SEE
ALSO For more information about the settings required to use Forced I/O Viewer Package, refer to:
B4.4, “Settings Required to Use the Forced I/O Viewer Function” on page B4-5

D1.1.6 CENTUM VP System Builder Function and ProSafe-

RS CENTUM VP Integration Package
By using ProSafe-RS CENTUM VP Integration Package, you can build an integrated system
of CENTUM VP and ProSafe-RS.
n Building a system by integrating CENTUM VP and ProSafe-RS


Product 1 System Builder Function of CENTUM VP R5.01 or later (*1)
Product 2 CENTUM VP Integration Package of ProSafe-RS R3.01 or later (*1)
User manage- - Standalone manage- Domain/Combination/Linked domain
ment type ment management (*2)
dures
sions.

• When CENTUM VP project is placed on a computer where SCS Manager is used:
Add the user account for using SCS Manager of ProSafe-RS to the CTM_ENGINEER
and PSF_ENGINEER groups.
For Standalone management, perform this setting on the computer where SCS Manager
is used. For Domain, Combination, or Linked domain management, perform this setting
on the domain controller.
• When CENTUM VP project is placed on a computer where SCS Manager is not used:
For Standalone management, create a user account with the same name as the user
who uses SCS Manager on the computer where the CENTUM VP project is placed and
then add the user account to the CTM_ENGINEER group.
For Domain, Combination, or Linked domain management, add the user account for us-
ing SCS Manager to the CTM_ENGINEER group on the domain controller.
SEE
refer to:
B3-56


RS Safety System Engineering and Maintenance
Function
By connecting CENTUM VP System Builder Function and ProSafe-RS Safety System Engi-
neering and Maintenance Function, you can perform simulation tests of SCS using SCS simu-
lator of ProSafe-RS.
n Enabling SCS simulation tests using SCS simulator


(*1)
dures
sions.

Add all the user accounts for using SCS Manager of ProSafe-RS or System View of CENTUM
VP to the CTM_ENGINEER and PSF_ENGINEER groups.
For Standalone management, perform this setting on the computer where SCS Manager of
ProSafe-RS and System View are used. For Domain, Combination, or Linked domain man-
agement, perform this setting on the domain controller.
SEE
refer to:
B3-56

D1.1.8 CENTUM VP Engineering Server Function and

ProSafe-RS Safety System Engineering and
Maintenance Function
When the CENTUM VP engineering server function and ProSafe-RS safety system engineer-
ing and maintenance function are connected, the AD Suite client function and server function
work in collaboration so that I/O list engineering and change management function can be
used.
n Performing engineering and maintenance of a ProSafe-RS safety

system by using a CENTUM VP engineering server

Product 1 Engineering Server Function of CENTUM VP R6.02 or later (*1)
(*1)
Required proce- Refer to "● When the Refer to "● When the Standard model is applied."
dures Legacy model is ap-
plied."
sions.
l When the Legacy model is applied

On the AD Suite client computer and AD Suite server computer, create Windows users who
use this function.
Use the ADS Administration Tool to register the Windows users to the engineering server.

use this function.
Add the user accounts to the CTM_ENGINEER and PSF_ENGINEER groups. For Stand-
alone management, perform this setting task on the computer where the CENTUM VP engi-
neering server is used and also on the computer where the ProSafe-RS safety system engi-
neering and maintenance function is used.
For Domain, Combination, or Linked domain management, perform this setting on the domain
controller.
SEE
ALSO For more information about how to create user accounts and add them to groups, refer to:
C1.2, “Management of AD projects” in Engineer's Reference Manual (IM 32P04B10-01EN)


RS Engineering Server Function
When the CENTUM VP system generation function and ProSafe-RS engineering server func-
tion are connected, the AD Suite client function and server function work in collaboration so
that the module-based engineering and change management function can be used.
n Generating a CENTUM VP system using a ProSafe-RS engineering

server

Product 1 Engineering Server Function of ProSafe-RS R4.01 or later (*1)
Required proce- Refer to "● When the Refer to "● When the Standard model is applied."
dures Legacy model is ap-
plied."
sions.

use this function.

use this function.
Add the user accounts to the CTM_ENGINEER and PSF_ENGINEER groups. For Stand-
alone management, perform this setting task on the computer where the CENTUM VP system
builder function is used and also on the computer where the ProSafe-RS engineering server
function is used.
For Domain, Combination, or Linked domain management, perform this setting on the domain
controller.
SEE
ALSO For more information about how to create user accounts and add them to groups, refer to:
C1.2, “Management of AD projects” in Engineer's Reference Manual (IM 32P04B10-01EN)

<D1.2 ProSafe-RS and iDefine > D1-17
D1.2 ProSafe-RS and iDefine

This section describes the settings when connecting ProSafe-RS and iDefine.
IMPORTANT
• iDefine for ProSafe-RS can be installed on the same computer as ProSafe-RS software
packages and collaborates with the Safety System Engineering and Maintenance Func-
tion.
In ProSafe-RS R4.05 or later, you can install the combination of iDefine for ProSafe-RS,
ProSafe-RS, and CENTUM VP on a same computer.
You cannot install iDefine for ProSafe-RS on a computer where CENTUM VP SOE Serv-
er Package is installed.
• When you install ProSafe-RS and iDefine for ProSafe-RS on the same computer, install
ProSafe-RS first and then iDefine for ProSafe-RS in succession. After installing iDefine
for ProSafe-RS, configure IT security settings.
• The combination of versions between ProSafe-RS and iDefine for ProSafe-RS is fixed.
For example, ProSafe-RS R4.06 can collaborate only with iDefine for ProSafe-RS 1.16.6.
SEE
ALSO For more information about the available combination of versions between ProSafe-RS and iDefine for Pro-
Sefe-RS, refer to:
“■ Use of iDefine” in A1.2, “Software requirements” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

D1.2.1 ProSafe-RS Safety System Engineering and

Maintenance Function and iDefine for ProSafe-RS
Connecting the ProSafe-RS Safety System Engineering and Maintenance Function and
iDefine for ProSafe-RS enables exchange of engineering data between ProSafe-RS and
iDefine. It also enables execution of ProSafe-RS logic simulation test, SCS simulation test,
and target test from iDefine by using iDefine Test Manager.
n Exchanging engineering data between ProSafe-RS and iDefine, and

using iDefine Test Manger

Product 2 iDefine for ProSafe-RS 1.16.6 or later
User management - Standalone man- Domain/Combina- Linked domain
type agement tion management management (*1)
Required proce- Refer to "● When Refer to "● When Refer to "● When Refer to "● When
dures the Legacy model is the Standard model the Standard model the Standard model
applied." is applied with is applied with Do- is applied with
Standalone man- main or Combina- Linked domain
agement." tion management." management."
*1: Linked domain management is supported by ProSafe-RS R4.06.00 or later software.

• When installing on the same computer
No procedure is requited.
• When installing on separate computers
On the computer where you run the ProSafe-RS Safety System Engineering and Mainte-
nance Function, create the logon users of the computer where you run iDefine. For the
users that you create, use the same user names and passwords as those of the users on
the computer where you run iDefine.
l When the Standard model is applied with Standalone management

Add the users who use iDefine to one of the following groups:
• PSF_OPERATOR
• PSF_ENGINEER
• PSF_MAINTENANCE
In addition, add the users who perform communication with iDefine Test Manager through
iDefine to the PSF_ENGINEER group.
1. On the computer where you run the ProSafe-RS Safety System Engineering and
Maintenance Function, create the logon users of the computer where you run
iDefine. For the users that you create, use the same user names and passwords as
those of the users on the computer where you run iDefine.

2. Add the created users to the PSF_ENGINEER group on the computer where you run
the ProSafe-RS Safety System Engineering and Maintenance Function.
SEE
refer to:
B3-56
l When the Standard model is applied with Domain or Combination

management
• PSF_OPERATOR
• PSF_OPERATOR_LCL
• PSF_ENGINEER
• PSF_ENGINEER_LCL
• PSF_MAINTENANCE
• PSF_MAINTENANCE_LCL
iDefine to the PSF_ENGINEER or PSF_ENGINEER_LCL group.
1. On the domain controller, add the computer that you run iDefine to the domain and
create the logon users of the computer where you run iDefine.
2. Add the created users to the PSF_ENGINEER group.
SEE
ALSO For more information about how to create user accounts and add them to groups in Domain or Combination
management, refer to:
l When the Standard model is applied with Linked domain management

• PSF_OPERATOR
• PSF_ENGINEER
• PSF_MAINTENANCE
1. On the domain controller, add the computer that you run iDefine to the domain and
create the logon users of the computer where you run iDefine.
2. Add the created users to the PSF_ENGINEER group.
SEE
ALSO For more information about how to create user accounts and add them to groups in Linked domain manage-
ment, refer to:

D1.2.2 ProSafe-RS functions other than Safety System

Engineering and Maintenance Function and iDefine
for ProSafe-RS
This section describes the settings when installing ProSafe-RS functions other than Safety
System Engineering and Maintenance Function and iDefine for ProSafe-RS on the same
computer.
n Installing ProSafe-RS SOE OPC Interface Package and iDefine for

ProSafe-RS on the same computer
The following table describes the connection information. This table also describes the infor-
mation for connecting with other ProSafe-RS packages. For required procedures for connec-

The same applies to the following combinations:
0203-0252-01-04, 0204-0252-01-04, 0205-0252-01-04, 0251-0252-01-04,
0296-0252-01-04, 0299-0252-01-04, 0253-0252-01-02
Product 1 SOE OPC Interface Package of ProSafe-RS R4.06 or later
Product 2 iDefine for ProSafe-RS 1.16.6 or later
User management - Standalone man- Domain/Combina- Linked domain
type agement tion management management (*1)
Required proce- None Refer to "● When Refer to "● When Refer to "● When
dures the Standard model the Standard model the Standard model
is applied with is applied with Do- is applied with
Standalone man- main or Combina- Linked domain
agement." tion management." management."
*1: Linked domain management is supported by ProSafe-RS R4.06.00 or later software.
l When the Standard model is applied with Standalone management

• PSF_OPERATOR
• PSF_ENGINEER
• PSF_MAINTENANCE
SEE
refer to:
B3-56
l When the Standard model is applied with Domain or Combination

management
• PSF_OPERATOR
• PSF_OPERATOR_LCL

• PSF_ENGINEER
• PSF_ENGINEER_LCL
• PSF_MAINTENANCE
• PSF_MAINTENANCE_LCL
iDefine to the PSF_ENGINEER or PSF_ENGINEER_LCL group.
SEE
ALSO For more information about how to create user accounts and add them to groups in Domain or Combination
management, refer to:
l When the Standard model is applied with Linked domain management

• PSF_OPERATOR
• PSF_ENGINEER
• PSF_MAINTENANCE
SEE
ALSO For more information about how to create user accounts and add them to groups in Linked domain manage-
ment, refer to:

<D1.3 ProSafe-RS and PRM> D1-22
D1.3 ProSafe-RS and PRM

This section describes the settings when connecting ProSafe-RS and PRM.
IMPORTANT
• Linked domain management is supported by ProSafe-RS R4.06.00 or later and PRM
R4.04.00 or later software revisions.
• When you install ProSafe-RS and PRM client on the same computer, ensure that the soft-
ware revision of ProSafe-RS is R4.04.00 or later and PRM is R4.02.00 or later. When you
install ProSafe-RS and PRM on the same computer with linked domain management, en-
sure that the software revision of ProSafe-RS is R4.06.00 or later and the software revi-
sion of PRM is R4.04.00 or later.

D1.3.1 ProSafe-RS SOE OPC Interface Package and PRM

Server
Connecting the ProSafe-RS and PRM Server enables PRM to retrieve ProSafe-RS messag-
es. To perform OPC communication with PRM, the SOE OPC Interface Package is required.
No setting is required on the PRM Server.
IMPORTANT
PRM Server and ProSafe-RS software cannot be installed on the same computer.
n Enabling PRM to retrieve messages from ProSafe-RS

The following table shows the connection information. The required procedures of connecting
the products are provided after the table.

Integration 0202-0302-02-04
code
Product 2 Plant Resource Manager Server of PRM R3.20 or later
Security mod- Legacy model Standard model
el
User manage- - Standalone man- Domain/Combination man- Linked domain
ment type agement agement management (*1)
Required pro- Refer to "● When Refer to "● Setting the logon type with Standard model", "● Creating
cedures the Legacy model is internal user accounts with Standard model".
applied."
*1: Linked domain management is supported by ProSafe-RS R4.06.00 or later and PRM R4.04.00 or later software revisions.

Follow these steps to set the logon type:
1. Log on as a user with administrative rights.
2. Start SOE OPC Parameter Setting.
The SOE OPC Interface Settings dialog box appears.
3. In the OPC Security Settings section, click [Edit].
The Select Logon Type dialog box appears.
4. Select [Automatically logon the designated user for connecting OPC server].
5. Select [Default user of R2.03 and earlier versions].
6. Click [OK].
l Setting the logon type with Standard model

Follow these steps to set the logon type:
1. Log on to the SENG as a member of the PSF_ENGINEER or PSF_ENGINEER_LCL
group.
3. In the OPC Security Settings section, click [Edit].
The Select Logon Type dialog box appears.

4. Select [Automatically logon the designated user for connecting OPC server].
5. Select [Default user of R2.03 and earlier versions].
6. Click [OK].
l Creating internal user accounts with Standard model

Follow these steps to create PRM and ProSafe-RS user accounts:
1. On the SENG, create the PRM_PROCESS and PRM_PROCESS2 user accounts by per-
forming these steps:
a. Log on to the SENG as a user with administrative rights.
b. Insert the PRM installation media Disc 1 into the DVD drive, and navigate to the fol-
lowing folder:
<DVD drive>:\PRM\SecuritySettingUtility
c. Double-click [CreateInternalUserAccount.exe].
The PRM_PROCESS and PRM_PROCESS2 user accounts are created and auto-
matically added to one of the following groups:
Standalone management: PSF_OPC
Domain management: PSF_OPC_LCL
Combination management: PSF_OPC or PSF_OPC_LCL
Linked domain management: PSF_OPC
2. On the PRM Server computer, create the PSF_PROCESS user account by performing
these steps:
a. Log on as a user with administrative rights.
b. Insert the ProSafe-RS software medium into the DVD drive, and navigate to the fol-
lowing folder:
<DVD drive>:\ProSafe-RS\SECURITY
c. Double-click [ProSafe.Security.CreateProSafeProcess.exe].
The PSF_PROCESS user account is created.

D1.3.2 PRM Client and Forced I/O Viewer Package

You can use ProSafe-RS Forced I/O Viewer Package on a computer where PRM Client is in-
stalled.
TIP You cannot install ProSafe-RS Forced I/O Viewer Package on a computer where ProSafe-RS Safety System
Engineering and Maintenance Function is installed.
n Viewing the ProSafe-RS forced-I/O information

The following table describes the connection information.

Product 1 PRM Client of PRM R4.02 or later(*1)
Product 2 Forced I/O Viewer Package of ProSafe-RS R4.05 or later (*1)
User management - Standalone man- Domain manage- Linked domain manage-
type agement ment or Combina- ment (*2)
tion management
Required proce- Read the reference that follows the table.
dures
*1: When you install ProSafe-RS and PRM on the same computer with linked domain management, ensure that the software
revision of ProSafe-RS is R4.06.00 or later and the software revision of PRM is R4.04.00 or later.
*2: Linked domain management is supported by ProSafe-RS R4.06.00 or later and PRM R4.04.00 or later software revisions.
SEE
ALSO For more information about the settings required to use Forced I/O Viewer Package, refer to:
B4.4, “Settings Required to Use the Forced I/O Viewer Function” on page B4-5

<D1.4 ProSafe-RS and Exaquantum> D1-26
D1.4 ProSafe-RS and Exaquantum

This section describes the settings when connecting ProSafe-RS and Exaquantum.

D1.4.1 ProSafe-RS SOE OPC Interface Package and

Exaquantum PIMS Server
Connecting the SOE OPC Interface Package and Exaquantum PIMS Server enables the
Exaquantum PIMS Server to collect SOE data from SCS through the OPC interface.
n Enabling Exaquantum to collect SOE data from SCS

To use Exaquantum PIMS Server as an OPC client and perform OPC communication with an
SENG running the SOE OPC Interface Package, you need to perform the settings described
below.
tion, read the descriptions that follow the table. The logon type setting on the SENG and the
setting to use Exaquantum as an OPC client are mandatory in all cases.
IMPORTANT
As a basic rule, the security model and user management type must be consistent in the
products to be connected. However, ProSafe-RS and Exaquantum can be connected even if
different security model or user management type is applied.
Table D1.4.1-1 Connection information: ProSafe-RS SOE OPC Interface Package and Exaquantum
R2.60 or later
Product 2 PIMS server of Exaquantum R2.60 or later
User manage- - Standalone management Domain/Combination manage-
ment type ment
Required proce- Refer to "● Setting the Refer to "● Setting the logon type" and "● When the Standard
dures logon type" and "● model is applied to both products."
When the Legacy model
is applied to both prod-
ucts."
Table D1.4.1-2 Connection information: Different security model - Case 1

Security model Standard model (ProSafe-RS)
Legacy model (Exaquantum)
User manage- Standalone management Domain/Combination management
ment type of
ProSafe-RS
Required proce- Refer to "● Setting the logon type" and "● When the Standard model is applied to
dures ProSafe-RS and the Legacy model to Exaquantum."
Table D1.4.1-3 Connection information: Different security model - Case 2


Table D1.4.1-3 Connection information: Different security model - Case 2 (Table continued)
Security model Legacy model (ProSafe-RS)
Standard model (Exaquantum)
ment type of
Exaquantum
Required proce- Refer to "● Setting the logon type" and "● When the Legacy model is applied to
dures ProSafe-RS and the Standard model to Exaquantum."
Table D1.4.1-4 Connection information: Legacy model applied ProSafe-RS and Exaquantum version
earlier than R2.60
Product 2 PIMS server of Exaquantum R2.20 or later but earlier than R2.60
Security model Legacy model (ProSafe-RS)
- (Exaquantum)
User manage- -
ment type
Required proce- Refer to "● Setting the logon type" and "● When the Legacy model is applied to both
dures products."
Table D1.4.1-5 Connection information: Standard model applied ProSafe-RS and Exaquantum version
earlier than R2.60
Product 2 PIMS server of Exaquantum R2.20 or later but earlier than R2.60
Security model Standard model (ProSafe-RS)
- (Exaquantum)
ment type of
ProSafe-RS
Required proce- Refer to "● Setting the logon type" and "● When the Standard model is applied to
dures ProSafe-RS and the Legacy model to Exaquantum."
SEE
ALSO For more information about the details on setting up an OPC client, refer to:
C3., “Setup for using the OPC client” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)
l Setting the Logon Type

To connect Exaquantum with an SENG (OPC server) running the SOE OPC interface pack-
age of ProSafe-RS R3.01.00 or later, you need to set the logon type on the SENG before-
hand. After performing this setting, perform the required setting on Exaquantum.
1. Log in to the system as a user belonging to PSF_ENGINEER or PSF_ENGINEER_LCL.
3. Click the [Edit] in [OPC Security Settings].
A dialog box where you can select a type of logon to the OPC server appears.

Figure D1.4.1-1 Select Logon Dialog Box
4. Select [Automatically logon the designated user for connecting OPC server.] and then
[Default user of R2.03 and earlier versions], and click [OK].
l When the Legacy model is applied to both products

1. Set the logon type on the SENG.
2. Add an Exaquantum program user on the SENG.
TIP The user name and password of the Exaquantum program user should be as follows:
User name: Quantumuser (default user name, changeable with a supplied tool)
Password: quantumuser (default password, changeable with a supplied tool)
3. On the SENG, create the same user account as the logon user account for running
Exaquantum.
4. On the SENG and the computer installed with Exaquantum, perform the setting for using
Exaquantum as an OPC client.
l When the Standard model is applied to both products

2. Configure the DCOM settings on the SENG. For procedures, refer to the user's manual
"Engineering Guide Vol.2".
3. On the SENG, create QTM_PROCESS, which is the Exaquantum program user account.
a. Insert the Exaquantum software medium and start the command prompt window,
then move to the following folder.
(Drive):\Tools
b. Run the following command.
CreateQTMProcess.exe
The QTM_PROCESS user account is created.
4. Add the QTM_PROCESS user you have created to the following user group on the
SENG.
• In the case of standalone management or when combination management is applied
on some computers: PSF_OPC
• In the case of domain management or when combination management is applied on
all computers: PSF_OPC_LCL

Exaquantum and add the created user account to the PSF_OPC group.
6. On the computer installed with Exaquantum, create the PSF_PROCESS user account.
a. Insert the ProSafe-RS software medium and start the command prompt window, then
move to the following folder.
(Drive):\ProSafe-RS\SECURITY
ProSafe.Security.CreateProSafeProcess.exe
7. Add the PSF_PROCESS user you have created to the following user group on the com-
puter installed with Exaquantum.
on some computers: QTM_OPC
all computers: QTM_OPC_LCL
SEE
ALSO For more information about configuring the DCOM settings, refer to:
“■ DCOM settings” in C2.2, “Overview of product security settings” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)
l When the Standard model is applied to ProSafe-RS and the Legacy model
to Exaquantum
2. Configure the DCOM settings on the SENG. For procedures, refer to the user's manual
"Engineering Guide Vol.2".
3. Add an Exaquantum program user on the SENG.
TIP The user name and password of the Exaquantum program user should be as follows:
User name: Quantumuser (default user name, changeable with a supplied tool)
Password: quantumuser (default password, changeable with a supplied tool)
4. Add the Quantumuser user you have created to the following user group on the SENG.
on some computers: PSF_OPC
all computers: PSF_OPC_LCL
Exaquantum and add the created user account to the PSF_OPC group.
6. On the computer installed with Exaquantum, create the PSF_PROCESS user account.
a. Insert the ProSafe-RS software medium and start the command prompt window, then
move to the following folder.
(Drive):\ProSafe-RS\SECURITY
ProSafe.Security.CreateProSafeProcess.exe

SEE
ALSO For more information about configuring the DCOM settings, refer to:
“■ DCOM settings” in C2.2, “Overview of product security settings” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)
l When the Legacy model is applied to ProSafe-RS and the Standard model
to Exaquantum
2. On the SENG, create QTM_PROCESS, which is the Exaquantum program user account.
a. Insert the Exaquantum software medium and start the command prompt window,
then move to the following folder.
(Drive):\Tools
CreateQTMProcess.exe
The QTM_PROCESS user account is created.
Exaquantum.
4. On the computer installed with Exaquantum, create the EXAUSER user account. The
password should also be EXAUSER.
5. Add the EXAUSER user you have created to the following user group on the computer
installed with Exaquantum.
on some computers: QTM_OPC
all computers: QTM_OPC_LCL

<Appendix 1. Setting Switches> App.1-1
Appendix 1. Setting Switches

You can set the domain number and station number by configuring the setting switches on the
printed circuit board of the control bus interface card and Vnet/IP interface card.
n Domain Numbers and DIP Switch Positions

The following table lists the domain numbers and corresponding setting switch positions for
the control bus interface card and Vnet/IP interface card. Set the DIP switches as shown in
the table to adjust to the required domain number.
Table Appendix 1-1 Domain Numbers and DIP Switch Positions

DIP switch bit number(*1)
Domain number
1 2 3 4 5 6 7 8
1 0 0 0 0 0 0 0 1
2 0 0 0 0 0 0 1 0
3 1 0 0 0 0 0 1 1
4 0 0 0 0 0 1 0 0
5 1 0 0 0 0 1 0 1
6 1 0 0 0 0 1 1 0
7 0 0 0 0 0 1 1 1
8 0 0 0 0 1 0 0 0
9 1 0 0 0 1 0 0 1
10 1 0 0 0 1 0 1 0
11 0 0 0 0 1 0 1 1
12 1 0 0 0 1 1 0 0
13 0 0 0 0 1 1 0 1
14 0 0 0 0 1 1 1 0
15 1 0 0 0 1 1 1 1
16 0 0 0 1 0 0 0 0
17 1 0 0 1 0 0 0 1
18 1 0 0 1 0 0 1 0
19 0 0 0 1 0 0 1 1
20 1 0 0 1 0 1 0 0
21 0 0 0 1 0 1 0 1
22 0 0 0 1 0 1 1 0
23 1 0 0 1 0 1 1 1
24 1 0 0 1 1 0 0 0
25 0 0 0 1 1 0 0 1
26 0 0 0 1 1 0 1 0
27 1 0 0 1 1 0 1 1
28 0 0 0 1 1 1 0 0
29 1 0 0 1 1 1 0 1
30 1 0 0 1 1 1 1 0
31 0 0 0 1 1 1 1 1

*1: Bit 1: Odd parity, Bits 2, 3: Fixed to 0, Bits 4 to 8: Domain number
n Station Numbers and DIP Switch Positions

The following table lists the station numbers and corresponding setting switch positions for
the control bus interface card and Vnet/IP interface card. Set the DIP switches as shown in
the table to adjust to the required station number.
Table Appendix 1-2 Station Numbers and DIP Switch Positions

DIP switch bit numbers (*1)
Station number
1 2 3 4 5 6 7 8
1 0 0 0 0 0 0 0 1
2 0 0 0 0 0 0 1 0
3 1 0 0 0 0 0 1 1
4 0 0 0 0 0 1 0 0
5 1 0 0 0 0 1 0 1
6 1 0 0 0 0 1 1 0
7 0 0 0 0 0 1 1 1
8 0 0 0 0 1 0 0 0
9 1 0 0 0 1 0 0 1
10 1 0 0 0 1 0 1 0
11 0 0 0 0 1 0 1 1
12 1 0 0 0 1 1 0 0
13 0 0 0 0 1 1 0 1
14 0 0 0 0 1 1 1 0
15 1 0 0 0 1 1 1 1
16 0 0 0 1 0 0 0 0
17 1 0 0 1 0 0 0 1
18 1 0 0 1 0 0 1 0
19 0 0 0 1 0 0 1 1
20 1 0 0 1 0 1 0 0
21 0 0 0 1 0 1 0 1
22 0 0 0 1 0 1 1 0
23 1 0 0 1 0 1 1 1
24 1 0 0 1 1 0 0 0
25 0 0 0 1 1 0 0 1
26 0 0 0 1 1 0 1 0
27 1 0 0 1 1 0 1 1
28 0 0 0 1 1 1 0 0
29 1 0 0 1 1 1 0 1
30 1 0 0 1 1 1 1 0
31 0 0 0 1 1 1 1 1
32 0 0 1 0 0 0 0 0
33 1 0 1 0 0 0 0 1

Table Appendix 1-2 Station Numbers and DIP Switch Positions (Table continued)
DIP switch bit numbers (*1)
Station number
1 2 3 4 5 6 7 8
⋅ ⋅
⋅ ⋅
⋅ ⋅
60 1 0 1 1 1 1 0 0
61 0 0 1 1 1 1 0 1
62 0 0 1 1 1 1 1 0
63 1 0 1 1 1 1 1 1
64 0 1 0 0 0 0 0 0
*1: Bit 1: Odd parity, Bits 2 to 8: Station number

<Appendix 2. Procedure for Erasing VI702 Internal Settings > App.2-1
Appendix 2. Procedure for Erasing VI702

Internal Settings
If you intend to reuse a VI702 card used in another system for a stand-alone ProSafe-RS sys-
tem, erase the settings within the card using the following procedure.
2. Set the DIP switches (SW1) for the domain number on the VI702 as follows:
Table Appendix 2-1 Setting of DIP Switches for Domain Number Setting (SW1)
Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8
1 1 0 0 0 0 0 1
Parity MSB LSB
3. Set the DIP switches (SW2) for the station number on the VI702 as follows:
Table Appendix 2-2 Setting of DIP Switches for Station Number Setting (SW2)
Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8
0 0 0 0 0 0 0 1
Parity MSB LSB
4. Check that Bit 1 through Bit 4 of the DIP switches (SW4) for the Action Mode are all set to
the off position on the VI702.
5. Remove the cover of the computer.
6. Insert the VI702 in the corresponding slot and fix the card.
7. Put back the cover of the computer.
8. Do not connect the cable to either BUS1 or BUS2.
9. Put back the power cord of the computer.
10. Start the computer, and then go to BIOS setting panel instead of starting Windows. If the
Windows started, it is necessary to shutdown and switch off the computer, and start the
computer for BIOS setting again.
11. Wait for about a minute after BIOS setting panel appears.
13. Remove the VI702 from the slot.
SEE
ALSO For more information about how to display the BIOS setting window, refer to:
The manual of the computer

<Appendix 3. Vnet/IP Interface Management Tool> App.3-1
Appendix 3. Vnet/IP Interface

Management Tool
By using the Vnet/IP Interface Management Tool, you can set the domain number and station
number managed by the Vnet/IP Interface Package.
n Changing the Domain Number and Station Number

Follow these steps to set the domain number and station number managed by the Vnet/IP In-
terface Package:
2. Select [YOKOGAWA Virtualization] > [VnetIP interface management tool] from the Start
menu.
Vnet/IP interface management tool starts.
3. Open the Settings tab of the Vnet/IP interface management tool.
4. Set the domain number in [Domain No] and the station number in [Station No], and then
click [Save].
TIP You can set a number in the range from 1 to 31 as the domain number (1 to 16 in the case of CENTUM inte-
gration), and from 1 to 64 as the station number. If both domain number and station number are set to 0,
Vnet/IP communication is disabled and communication to the control network is not possible.
On a virtual machine where you run an FCS simulator that can be operated through remote connection from
another HIS by installing the Expanded Test Functions and SCS Simulator Package, set both the domain
number and the station number to 0.
Note that the license of Vnet/IP Interface Package is not required when using only the test function with the
domain number and the station number set to 0.
5. Click [CLOSE], and restart the virtual machine.
n Operation Status of the Vnet/IP Interface Package

The [Monitor] shows the following information:
• Version information of the Vnet/IP Interface Package
• Operation status of the Vnet/IP Interface Package
• Domain number and station number
• Presence of different Vnet/IP firmware versions
l Version information
The version number of the Vnet/IP Interface Package is displayed.
l Operation status
One of the following five operation statuses is displayed.
Stop: Indicates that the Vnet/IP Interface Package is not functioning.
Starting: Indicates that the domain number, station number, and configuration are
being checked before the package goes into operation.
Waiting the li- Indicates that the package is waiting for the license to be granted.
cense:
Working: Indicates that the package is operating properly.

Stop (error mes- Indicates that the package is not functioning.
sage):
l Domain number and station number

The domain number and station number are displayed.
l Presence of different Vnet/IP firmware revisions

The revision information of the Vnet/IP firmware is displayed. If more than one of stations use
old firmwares, they are delimited with a comma.
Display exam- 06R, 13L
ple:
Meaning: The Vnet/IP firmware implemented on the right side card of station num-
ber 6 and the Vnet/IP firmware implemented on the left side card of station
number 13 are old.
n What to Do When an Error Occurs

When using the Vnet/IP Interface Management Tool, error messages may appear. This sec-
tion explains the conditions for error messages to occur and countermeasures.
l Invalid Windows service registration

• Message
Invalid Windows service registration
• Condition for occurrence
This error message is generated when any one of the Vnet/IP Interface Package serv-
ices, “YWVNT BKNET Service,” “YWVNT VnetIP Stack Service,” and “YWVNT VnetIP
Privileged Service” is not registered as Windows service, or the Vnet/IP Interface Pack-
age services are not configured to start automatically.
• Remedy
Install the Vnet/IP Interface Package again.
SEE
ALSO For more information about the procedure to install the Vnet/IP Interface Package, refer to:
l BUS1 not found

• Message
BUS1 not found
This message is generated when the name of control network 1 is invalid.
• Remedy
Rename control network 1 to VnetIPBUS1.
SEE
ALSO For more information about how to change the name of control network 1, refer to:
“n Rename Local Area Connections” on page B3-38

l BUS2 not found

• Message
BUS2 not found
This message is generated when the name of control network 2 is invalid.
• Remedy
Rename control network 2 to VnetIPBUS2.
SEE
ALSO For more information about how to change the name of control network 2, refer to:
“n Rename Local Area Connections” on page B3-38
l Invalid domain number or station number

• Message
Invalid domain number or station number
This message is generated when the domain number or station number managed by the
Vnet/IP Interface Package are invalid.
• Remedy
Using the Vnet/IP Interface Management Tool, check the domain number and station
number managed by the Vnet/IP Interface Package and set to the correct values.
SEE
ALSO For more information about how to set the domain number and station number managed by the Vnet/IP Inter-
face Package, refer to:
l Station of the specified domain number and station number already exists
• Message
Station of the specified domain number and station number already exists
This message is generated when the same domain number or station number are already
used for another station.
• Remedy
Using the Vnet/IP Interface Management Tool, check the domain number and station
number managed by the Vnet/IP Interface Package and set to the correct values.
SEE
ALSO For more information about how to set the domain number and station number managed by the Vnet/IP Inter-
face Package, refer to:
l IT security not applied

• Message
IT security not applied

This message is generated when IT security has not been applied after installation of the
Vnet/IP Interface Package.
• Remedy
Apply IT security.

<Appendix 4. Antistatic Precautions When Handling Hardware > App.4-1
Appendix 4. Antistatic Precautions When

Handling Hardware
When doing maintenance work, take the following precautions to avoid electrostatic problems.
• When storing or carrying parts for maintenance, put them in an antistatic bag. (When
shipped, they are placed in an antistatic bag labeled with cautions against electrostatic
problems.)
• Wear a wrist strap with a 1M ohm grounding resistor then ground the wrist strap.
• When working on the bench, place the parts on a conductive sheet grounded via a 1 M
ohm resistor and wear wrist strap. Keep static-chargeable plastic materials away from the
parts.
• Never touch the parts with bare hands, without using a wrist strap and a conductive
sheet.
Wrist strap Conductive sheet
1M ohm
1M ohm
Grounding resistance
of 1 M ohm
Wrist strap
When working with a product with battery on

Connect the wrist strap to the grounding terminal or a conductive sheet, set the battery ON/OFF
unpainted part of the frame (grounded). switch to the OFF position or remove the battery.
Figure Appendix 4-1 Using a Wrist Strap
The wrist strap and conductive sheet are available from YOKOGAWA sales agents.

<Appendix 5. Customization at Installation of Windows 10 > App.5-1
Appendix 5. Customization at Installation

of Windows 10
This section describes how to customize Windows settings during installation of Windows 10
Enterprise 2016 LTSB.
TIP You do not need to perform this customization on Windows 10 IoT Enterprise 2016 LTSB installed computers
provided by YOKOGAWA.
n Procedure for Customization at installation of Windows 10

1. The following screen appears during installation of Windows 10 Enterprise 2016 LTSB.
Figure Appendix 5-1 Screen That Appears When Installing Windows 10
Click [Customize].
The Customize Settings window appears.

<Appendix 5. Customization at Installation of Windows 10 > App.5-2
Figure Appendix 5-2 Customize Settings Window
2. Set all settings to [Off].

3. Click [Next] to continue installing Windows 10 Enterprise 2016 LTSB.

<Appendix 6. Compatibility between Revisions and Cautionary Notes for Upgrading > App.6-1
Appendix 6. Compatibility between

Revisions and Cautionary
Notes for Upgrading
IMPORTANT
Be sure to take a backup of the whole project before upgrading ProSafe-RS.
This section provides the compatibility information for earlier versions of ProSafe-RS software
released in the past and the cautionary notes for upgrading that were published at the time of
each release. In this section, users can confirm the procedures for using the new features
supported in each release in the past and the important descriptions about SCS specifications
that were released in the past as the compatibility information.
When you upgrade ProSafe-RS, install only the software of the release number you want to
use. However, for the required procedures after the installation, read the cautionary notes for
upgrading for all release numbers between the release number of the software currently in-
stalled on your computer and the release number of the software you want to use.

<Appendix 6.1 Cautionary Notes for Upgrading to R4.01 > App.6-2
Appendix 6.1 Cautionary Notes for Upgrading to

R4.01
This section provides cautionary notes for upgrading from R3.02.20 to R4.01. When you up-
grade, also read the cautionary notes for upgrading to the previous versions that were issued
after the software version currently installed on your computer and perform the required tasks
for each upgrade.
IMPORTANT
Use the R6.02 or a later version of CENTUM VP when integrating ProSafe-RS with CENTUM
VP.
In R4.01, be sure to register the RS project in the AD project regardless of the engineering
method.
SEE
ALSO For more information about compatibility and cautionary notes for upgrading up to ProSafe-RS R3.02.10, re-
fer to:
Appendix 4., "Compatibility between Revisions and Cautionary Notes for Upgrading" in Installation for
ProSafe-RS R3 (IM 32Q01C50-31E)
For more information about cautionary notes when upgrading the revision to ProSafe-RS R3.02.20, refer to:
C5., "Upgrading to R3.02.20" in Installation for ProSafe-RS R3 (IM 32Q01C50-31E)
For more information about creating an AD project, refer to:
(IM 32P04B10-01EN)
n Software Revisions
The respective software release number of R4.01 is as follows:
• SENG software release number: R4.01.xx (*1)
R4.01.00.
l Inter-SCS Safety Communication

The release number of the SCS system program of an SCS that performs Inter-SCS safety
communication with SCS with system program version R4.01 must be of R1.01.30 or later.
If Vnet/IP is used for route of the Inter-SCS safety communication, the system programs on
the SCSs must be of R1.02 or later.
l Control Bus Drivers

You do not need to update the control bus driver if the control bus driver provided in R3.02.20
is installed on the computer.
SEE
ALSO For more information about how to update the control bus driver, refer to:
“l Updating the Control Bus Driver” on page C4-4

n Basic Procedures for Upgrading

open the existing SCS project.
n Procedure for Using Added and Modified Features

The following functions that have been added or modified in R4.01 cannot be used in the ba-
sic upgrading procedures. Once you have upgraded the SENG software to R4.01, offline
download to the SCS and other operations are required. The procedures to use the respec-
tive functions are described below.
SEE
ALSO For more information about settings after upgrading software, refer to:
l New station (S2SC70)

To use the S2SC70 station, which is newly added in R4.01, you need to perform "Procedure
C" on an SENG of R4.01 or later. In S2SC70, N-IO systems can be used.
l Annunciator messages with tag names

To use annunciator messages with tag names, "Procedure D" must be performed on an
SENG of R4.01 or later. To use annunciator messages with tag names, set the applicable pa-
rameters in a Builder.
l Modbus/TCP subsystem communication

To use subsystem communication using the Modbus/TCP protocol, "Procedure C" must be
performed on an SENG of R4.01 or later.
l I/O List Engineering of AD Suite

To use I/O List Engineering of AD Suite that has been added in R4.01, "Procedure C" must be
performed on an SENG of R4.01 or later. In R4.01, be sure to register the RS project in the
AD project regardless of the engineering method. You should then create and set an SCS
project; otherwise, I/O List Engineering cannot be implemented. To upgrade an existing SCS
to start I/O List Engineering, you need an I/O list matching the definitions of the original SCS
project.
l History Management Function of AD Suite

To use the history management function of AD Suite that has been added in R4.01, "Proce-
dure A" must be performed on an SENG of R4.01 or later. In R4.01, be sure to register the RS
project in the AD project regardless of the engineering method.


R4.02
This section provides cautionary notes for upgrading from R4.01 to R4.02. When you up-
for each upgrade.
IMPORTANT
VP.
In R4.01 or later, be sure to register the RS project in the AD project regardless of the engi-
neering method.
SEE
ALSO For more information about cautionary notes when upgrading the version to ProSafe-RS R4.01 from an earli-
er version, refer to:
Appendix 6.1, “Cautionary Notes for Upgrading to R4.01” on page App.6-2
(IM 32P04B10-01EN)
R4.02.00.


You do not need to update the control bus driver if the control bus driver provided in R3.02.20
is installed on the computer.
n Basic Procedure for Upgrading


l Integration with External Engineering Tool

To use the feature for integration with iDefine, an external engineering tool, that has been
added in R4.02, "Procedure A" must be performed on an SENG of R4.02 or later.

sic upgrading procedures. After you have upgraded the SENG software to R4.02, offline
SEE
l Duplexed Interface for DNP3 Communication

To use the duplexed interface for DNP3 communication that has been added in R4.02, "Pro-
cedure C" must be performed on an SENG of R4.02 or later. The duplexed interface for DNP3
communication is available only in SSC57.
l Support for the RoHS Directive Compliant Processor Module SCP451-□3

To use the RoHS directive compliant processor module SCP451-□3, "Procedure B" must be
performed on an SENG of R4.02 or later. The RoHS directive compliant processor module
SCP451-□3 can be used in SSC50 and SSC57.
n Cautionary Notes for Upgrading When ALE111 is Used

communication.
During the first online change download after SENG has been upgraded, the latest communi-
cation program for ALE111 is also downloaded. Because ALE111 is restarted in this process,
communication with the Modbus or DNP3 master s is disabled temporarily. Therefore, you
must perform online change download with appropriate timing after the upgrade.
For the details, read the following descriptions:
l Upgrade Procedure When ALE111 is Used for Modbus Slave

Communication
If ALE111 is used for Modbus slave communication and you are upgrading from R4.01.00 or
earlier to R4.02.00 or later, follow these steps to download the latest communication program
to ALE111:

IMPORTANT
• You can build the SCS project without changing the ALE111 definitions. If you perform
an online change download the first time after running a build, the latest communication
program is downloaded to ALE111, even if no change has been made to the communi-
cation definitions for the ALE111.
• The latest communication program will be downloaded to ALE111 also when you per-
form an online change download after modifying only the definitions not relevant to
ALE111.
• During online change download, communication with the Modbus master is disabled.
(*1)You must perform an online change download only when no problem is caused even
if the communication with the Modbus master is interrupted.
• When upgrading the system, if you also want to perform modification of application that
requires addition of communication modules other than ALE111 for Modbus slave com-
munication at the same time, you must observe the following precautions. You must first
perform the following steps 1 through 5 to download the latest program to the existing
ALE111, and then modify the application. If you do not follow this procedure, upgrading
of the communication program may fail. If failed, offline downloading to the SCS is re-
quired.
*1: Even if the communication interface with the Modbus master is duplexed by using two ALE111 modules, the communication
is disabled during online change download.
1. Upgrade ProSafe-RS from R4.01.00 or earlier to R4.02.00 or later.

2. Run a build for the SCS project regardless of whether you have made changes.
3. Using Integrity Analyzer and Cross Reference Analyzer, perform an approval check.
TIP Differences in the communication program are not displayed.
4. Run an online change download.

5. Confirm the revision number of the communication program.
The revision number of the communication program that is downloaded in R4.02.00 or
later is R4.02.00. When the online change download is complete, confirm that the com-
munication program of R4.02.00 has been downloaded to all ALE111 modules by using
IOM Report. You can find the revision number of the communication program at the ad-
dress 0x0120 in the IOM Report for ALE111.

Figure Appendix 6.2-1 IOM Report for ALE111 Used for Modbus Slave Communication
If you want to perform modification of application at the same time, perform step 6.
6. Perform modification of the application that requires addition of communication modules
other than ALE111 for Modbus slave communication.
l Upgrade Procedure When ALE111 is Used for DNP3 Communication

If ALE111 is used for DNP3 communication and you are upgrading from R4.01.00 or earlier to
R4.02.00 or later, follow these steps to download the latest communication program to
ALE111:

IMPORTANT
• You can build the SCS project without changing the ALE111 definitions. If you perform
an online change download the first time after running a build, the latest communication
program is downloaded to ALE111, even if no change has been made to the communi-
cation definitions for the ALE111.
• The latest communication program will be downloaded to ALE111 also when you per-
form an online change download after modifying only the definitions not relevant to
ALE111.
• During online change download, communication with the DNP3 master is disabled. You
must perform an online change download only when no problem is caused even if the
communication with the DNP3 master is interrupted.
• When upgrading the system, if you also want to perform modification of application that
requires addition of communication modules other than ALE111 for DNP3 communica-
tion at the same time, you must observe the following precautions. You must first per-
form the following steps 1 through 5 to download the latest program to the existing
ALE111, and then modify the application. If you do not follow this procedure, upgrading
of the communication program may fail. If failed, offline downloading to the SCS is re-
quired.
1. Upgrade ProSafe-RS from R4.01.00 or earlier to R4.02.00 or later.

2. Run a build for the SCS project regardless of whether you have made changes.
3. Using Integrity Analyzer and Cross Reference Analyzer, perform an approval check.
TIP Differences in the communication program are not displayed.
4. Run an online change download.

5. Confirm the revision number of the communication program.
The revision number of the communication program that is downloaded in R4.02.00 or
later is R4.02.00. When the online change download is complete, confirm that the com-
munication program of R4.02.00 has been downloaded to all ALE111 modules by using
IOM Report. You can find the revision number of the communication program at the ad-
dress 0x0120 in the IOM Report for ALE111.

Figure Appendix 6.2-2 IOM Report for ALE111 Used for DNP3 Communication
If you want to perform modification of application at the same time, perform step 6.
6. Perform modification of the application that requires addition of communication modules
other than ALE111 for DNP3 communication.


R4.03
This section provides cautionary notes for upgrading from R4.02 to R4.03. When you up-
for each upgrade.
IMPORTANT
VP.
In R4.01 or later, be sure to register the RS project in the AD project regardless of the engi-
neering method.
SEE
(IM 32P04B10-01EN)
For more information about cautionary notes when upgrading the version to ProSafe-RS R4.01 from an earli-
er version, refer to:
R4.03.


The control bus drivers that are installed on the computer should be upgraded to the version
supplied in R4.03.



sic upgrading procedures. After you have upgraded the SENG software to R4.03, offline
SEE
l Device Reset Function

To use the device reset function with SAI143, you need to perform “Procedure C” on an
SENG of R4.03 or later.
l Function Blocks for Fire and Gas Devices

To use the function blocks for fire and gas devices HSDTR and GASDTR, which are newly
added in R4.03, you need to perform “Procedure C” on an SENG of R4.03 or later.
l Alarm Suppression Function During Device Reset

To use the Alarm Suppression Function During Device Reset, you need to perform “Proce-
dure C” on an SENG of R4.03 or later. The Alarm Suppression Function During Device Reset
cannot be used with SSC57.
l Chattering Alarm Suppression Function

To use the Chattering Alarm Suppression Function, you need to perform “Procedure C” on an
SENG of R4.03 or later. The Chattering Alarm Suppression Function cannot be used with
SSC57.
l Digital I/O Module (S2MDV843)

To use the digital I/O module S2MDV843 newly added in R4.03, you must follow the “Proce-
dure C” on SENG of R4.03 or later. S2MDV843 can be used with an S2SC70 N-IO system.

communication.
SEE
slave or DNP3 communication, refer to:
n Cautionary Notes When Opening a New Revision AD Project from an

Older Revision AD Organizer
From AD Organizer that was installed from the ProSafe-RS R4.01 or R4.02 software medium,
you cannot open AD projects created by using AD Organizer of ProSafe-RS R4.03 or later or
AD projects upgraded to R4.03 or later.
In such a case, apply one of the following compatibility patches:
• Compatibility patch for R4.01: R4.01.34
• Compatibility patch for R4.02: R4.02.01

TIP • Also after an AD project has been upgraded, SCS projects of different revisions can exist together in the
AD project.
• If you want to continue engineering of older revision SCS projects that are contained in the AD project
without upgrading them, you must open the AD project from the corresponding older revision AD Organ-
izer.
• For how to obtain the compatibility patches, contact YOKOGAWA.

<Appendix 6.4 Cautionary Notes for a Revision Upgrade to R4.03.10 > App.6-13
Appendix 6.4 Cautionary Notes for a Revision

Upgrade to R4.03.10
This section provides cautionary notes for a revision upgrade from R4.03 to R4.03.10. When
you upgrade, also read the cautionary notes for upgrading to the previous versions that were
issued after the software version currently installed on your computer and perform the re-
quired tasks for each upgrade.
IMPORTANT
VP.
neering method.
SEE
ALSO For more information about cautionary notes when upgrading the revision to ProSafe-RS R4.03, refer to:
(IM 32P04B10-01EN)
The respective software release number of R4.03.10 is as follows:
Software release number R4.03.10 (*1)
• SENG software release number: R4.03.10 (*1)
• SCS system program release number: R4.03.10 (*1)
R4.03.10.

communication with SCS with system program version R4.03.10 must be R1.01.30 or later.

supplied in R4.03.10.

To use the added or modified features, install the ProSafe-RS software R4.03.10 or later and

<Appendix 6.4 Cautionary Notes for a Revision Upgrade to R4.03.10 > App.6-14
l Safety Communication I/O Editor

To use Safety Communication I/O Editor of AD Suite, you must perform "Procedure A" on an
SENG of R4.03.10.
If I/O list engineering had been selected and subsystem communication had been defined
with a version earlier than R4.03.10, from here on you must perform engineering by using
Safety Communication I/O Editor. Use Communication I/O List Output Tool to create a safety
communication I/O list.
SEE
ALSO For more information about Operations of “Procedure A”, refer to:
For more information about how to create a safety communication I/O list, refer to:
“■ Communication I/O List Output Tool” in Appendix 3.4, “Major changes in R4” in Engineering Guide
Vol. 1 (IM 32P01C10-01EN)

The following functions that have been added or modified in R4.03.10 cannot be used in the
basic upgrading procedures. After you have upgraded the SENG software to R4.03.10, offline
SEE
ALSO For more information about details of the operation procedure introduced in each function, refer to:
l Fire and Gas Communication

To use fire and gas communication for connecting with wireless gas detectors, you must per-
form "Procedure C" on an SENG of R4.03.10. Fire and gas communication can be used with
S2SC70 only.
l Expanding the Number of Data Allocated for Subsystem Communication

With subsystem communication, to expand the number of data that can be allocated to an in-
stance of a subsystem communication FB, you must perform "Procedure C" on an SENG of
R4.03.10.

communication.
SEE

<Appendix 6.5 Cautionary Notes for Revision Upgrade to R4.04 > App.6-15
Appendix 6.5 Cautionary Notes for Revision

Upgrade to R4.04
This section provides cautionary notes for revision upgrade from R4.03.10 to R4.04. When
you upgrade, also read the cautionary notes for upgrading to the previous versions that were
issued after the software version currently installed on your computer and perform the re-
quired tasks for each upgrade.
neering method used.
SEE
(IM 32P04B10-01EN)
For more information about cautionary notes when upgrading the revision to ProSafe-RS R4.03.10, refer to:
Appendix 6.4, “Cautionary Notes for a Revision Upgrade to R4.03.10” on page App.6-13
For more information about settings after upgrading software, refer to:
R4.04.00.

communication with SCS with system program version R4.04 must be R1.01.30 or later.
If Vnet/IP is used in the route of the inter-SCS safety communication, the system programs on

supplied in R4.04.

SEE

<Appendix 6.5 Cautionary Notes for Revision Upgrade to R4.04 > App.6-16
l Changing the Setting Range of IOP Lower Limit Detection Level

To change the setting range of the IOP lower limit detection level and transmitter error lower
limit detection level for AI channels, you must follow “Procedure A” by using SENG of R4.04.
This feature is applicable to the AI channels of SAI143-H style 3 or later and S2MMM843.
l Functional Improvement of AD Organizer

To use the improved method for starting SCS Manager from AD Organizer and to use the
read-only mode of the Safety I/O Editor and the Safety Communication I/O Editor, you must
follow “Procedure A” by using SENG of R4.04.

communication.
SEE

<Appendix 6.6 Cautionary Notes for Revision Upgrade to R4.05> App.6-17
Appendix 6.6 Cautionary Notes for Revision

Upgrade to R4.05
This section provides cautionary notes for revision upgrade from R4.04 to R4.05. When you
upgrade, also read the cautionary notes for upgrading to the previous versions that were is-
sued after the software version currently installed on your computer and perform the required
tasks for each upgrade.
neering method used.
SEE
(IM 32P04B10-01EN)
For more information about the detailed operation procedure required after the revision upgrade, refer to:
R4.05.00.

communication with SCS with system program version R4.05 must be R1.01.30 or later.
If Vnet/IP is used in the route of the inter-SCS safety communication, the system programs on

supplied in R4.05.
n Cautionary notes on License Management Software in which its

vulnerability is resolved
In ProSafe-RS R4.05.00, the vulnerability of License Management Software has been re-
solved. Therefore, if you use a computer in which ProSafe-RS R4.05.00 or later is installed as
a license management station and you want to distribute licenses and distribute master licen-
ses from it, you can distribute only to the license-assigned stations in which the vulnerability is
resolved.

The following table shows the products and their revision numbers in which the vulnerability is
resolved.
Table Appendix 6.6-1 The revision number of products in which the vulnerability is resolved
Product Revision number
CENTUM VP R6.07.00 or later
ProSafe-RS R4.05.00 or later
PRM R4.03.00 or later
l Cautionary notes on a mixture of vulnerability-resolved computers and

vulnerability-unresolved computers
• You cannot distribute licenses or distribute master licenses through network if there is a
mixture of vulnerability-resolved computers and vulnerability-unresolved computers in a li-
cense project.
• If there is a mixture of vulnerability-resolved computers and vulnerability-unresolved com-
puters in a license project, contact YOKOGAWA.

SEE
ALSO For more information about Operations of “Procedure A”, refer to:
l Safety I/O Parameter Profile of AD Suite

To use the safety I/O parameter profile of AD Suite, you must perform "Procedure A" on an
SENG of R4.05.
l Improved AD Suite Functions

To use the following improved AD Suite functions, you must perform "Procedure A" on an
SENG of R4.05.
• Improved workflow of AD Suite and iDefine
This functional improvement is available when collaborating with iDefine 1.16.5 or later.
• Improved Safety I/O Editor, IOM Definition Editor, and System Structure Navigator
l Improved Logic Simulation Test Function

To use the improved logic simulation test function, you must perform "Procedure A" on an
SENG of R4.05. This functional improvement is available when collaborating with iDefine
1.16.5 or later. However, it is not available with SCSV1.

The basic upgrading procedures are not enough to use the following functions that have been
added or modified in R4.05. After you have upgraded the SENG software to R4.05, offline
SEE
ALSO For more information about details of the operation procedure introduced in each function, refer to:

l Skipping the Password Dialog Box for Manual Operation FBs

To use the function to skip the Password dialog box for manual operation FBs, you must per-
form "Procedure F" on an SENG of R4.05. This function is not available with SCSU1 and
SCSV1.
When using this function, configure the parameter on the SCS Constants Builder after up-
grading to R4.05, and then offline download the project. Thereafter, you can change the pa-
rameter by online change download. This function does not work when used in combination
with HIS of CENTUM VP before R6.07.
l Forced I/O Viewer Function

To use the Forced I/O Viewer function, you must perform "Procedure B" on an SENG of
R4.05. This function is not available with SCSV1.
l Support of the CPU Module S2CP471

To use the CPU module S2CP471, you must perform "Procedure B" on an SENG of R4.05.
S2CP471 can be used in SSC60 and S2SC70.
n Notes When Aliases are Defined for User-defined Columns in AD

Organizer
This section describes the behavior when the system is upgraded if an alias of a user-defined
column already defined is identical to the name of a standard column such as “Typical” that
has been added to the Safety I/O Editor and Safety Communication I/O Editor in R4.05. It al-
so describes the data migration procedure required in such a case.
SEE
ALSO For more information about details of the data migration procedure required on iDefine after the upgrade, re-
fer to:
iDefine User Guide (PR03076-MAN-970_01)
l Column Names After the Upgrade

If an alias of a user-defined column already defined is identical to the name of a newly added
standard column, the alias name of the user-defined column is changed during the upgrade.
An underscore “_” is added to the beginning of the original alias name.
(Example) When the alias name is Typical
After upgraded to R4.05, the alias name becomes “_Typical”.
l Migrating the Data of the Duplicate Column

The data of the original user-defined column remains after the upgrade. You can use a grid
rule to migrate the data to a new standard column. In the Grid Rule Editor, create a grid rule
for data copying.
For example, to copy the data of the _Typical column to the Typical column, configure the set-
tings in the Define Rule window as follows:
• Select [Set] for Rule Type and [Typical] for Target Column.
• Set nothing in the Condition section.
• In the Action section, select [Column Name] for the operand type and set [_Typical] as
the name of the column to be operated.
By running the created rule, the data of the _Typical column is copied to the Typical column.
Confirm the result, and delete the data of the _Typical column.


communication.
SEE

Rev-1
Revision Information
Title : Installation Guide
Manual No. : IM 32P01C50-01EN
Feb. 2021/7th Edition/R4.06 or later
A1, B2.1, B2.2, Deleted descriptions of unsupported OS.
B2.3, B2.4, B3.2,
B3.3, B3.9, B5.1,
B6, C4.1, C7.2
A2.2, B1.2, B2.1, Added descriptions about linked domain management.
B2.3, B2.5, B3.5,
B3.6, B3.8, B4.5,
B5.1, B5.2, B5.3,
B6, C2
B1.2 Added or deleted descriptions about downloading Windows update programs.
B3.2.2, B3.9.2 Added descriptions of Windows 10 Enterprise 2019 LTSC.
B3.5, C4.1 Updated descriptions of redistributable modules.
C4.1, C4.2 Updated descriptions of actions after the installation for an upgrade or after up-
grading ProSafe-RS software.
C4.2.3 Added descriptions of upgrading to R4.06.
D1 Updated the package code 0204 from FAST/TOOLS Integration Package to CI
Server Integration Package.
D1.1 Added descriptions about linked domain management to the information for con-
necting CENTUM VP and ProSafe-RS.
D1.2 Updated descriptions of the information for connecting ProSafe-RS and iDefine,
and added descriptions about linked domain management.
D1.3 Added descriptions about linked domain management to the information for con-
necting ProSafe-RS and PRM.
Apr. 2019/6th Edition/R4.05
Introduction Updated description of registered trademarks and trademarks.
B1.2, B2.3, Updated descriptions of Windows update programs.
B3.2.3, B3.2.5,
B3.3.3, B5.1
B1.2, B2.3, B3.6, Updated descriptions of IT security.
B5.1
B3.5, C4.1.1, Updated descriptions of redistributable modules.
C4.1.2
B3.6, B4.4 Added descriptions of the Forced I/O Viewer function.
C4.1.1, C4.1.2 Added descriptions of updating the Vnet/IP Interface Package.
C4.2 Updated descriptions due to the change in project database format.
C5 Added descriptions of updating to R4.05.
D1.1.5 Added information about connecting CENTUM VP and Forced I/O Viewer Pack-
age.
D1.2 Updated information for connecting ProSafe-RS and iDefine.
D1.3.2 Added information about connecting PRM Client and Forced I/O Viewer Package.

Rev-2
Aug. 2018/5th Edition/R4.04
Introduction Updated description of registered trademarks of YOKOGAWA.
A2.2.2, A2.2.3, Added descriptions about virtualization platform.
B1.3, B3.1, B3.3,
B3.3.3, B3.4,
C6.1.2, Appendix
3
B1.2, B2.3, Added descriptions of Windows update programs.
B3.2.3, B3.2.5,
B5.1
B2.1 to B2.3, Added descriptions of Windows Server 2016
B3.2.1, B3.2.4,
B3.3.4, B3.9.1,
B6, C8.2.1
B2.3, B3.5, B5.1 Changed descriptions of redistributable package
B2.3, B3.2.2, Added descriptions of disabling the Automatic cleanup task.
B3.2.4, B5.1
B3.2.2, B3.2.5, Deleted description of .NET Framework 3.5.1
B3.5, B6
B3.2.2, B3.2.4 Added descriptions of DCOM Settings
B3.5, C4.1 Added description of using iDefine interface package.
B3.9.2 Added descriptions about suppressing toast notification regarding Windows Fire-
wall.
C4.1 Added procedure for upgrading the revision of products when two or more up-
grade license support products are installed.
C4.1.1 Added the upgrading the version of ProSafe-RS software.
C4.1.2 Added the upgrading the revision of ProSafe-RS software.
C5 Added descriptions of upgrading to R4.04
D1.1 Updated description of the information for connecting CENTUM VP and ProSafe-
RS.
D1.2 Updated description of the information for connecting ProSafe-RS and iDefine.
Oct. 2017/4th Edition/R4.03.10
B3.4 Deleted precautions when installing ProSafe-RS and CENTUM, or ProSafe-RS
and PRM, on the same computer.
B4.1 Added descriptions of the Help files for PROFINET Configurator.
C4.1 Added descriptions of the upgrade license.
C4.2 Added descriptions of I/O list engineering.
C4.3 Added descriptions of how to start engineering after upgrading the ProSafe-RS
software.
C5 Added descriptions of updating to R4.03.10.
C6.1 Added precautions for uninstallation when ProSafe-RS and CENTUM VP are in-
stalled on the same computer.
May 2017/3rd Edition/R4.03
Entire manual Updated descriptions of the Start menu.
Introduction Deleted Windows Vista from Trademark Acknowledgments.
B2 Updated descriptions of configuring the security settings on the domain controller

Rev-3
B3.2, B3.5, B3.8, Deleted descriptions of Windows Vista and Windows Server 2008.
C9.2
B3.2, B3.3, B3.4, Added descriptions of Windows 10
B3.8, B6, C8.2,
Appendix 4
B3.3, C8.2 Updated descriptions of configuring network settings
B3.4, B5, B6, Updated descriptions of security groups
C4.1
B3.5, C8 Updated descriptions of IT security settings. Moved descriptions of the IT Security
Tool and IT security-related maintenance to the Security Guide.
B6, C4.1, C4.3 Added descriptions of setting up Windows.
D1, D1.1 Updated descriptions of CENTUM VP and ProSafe-RS
D1.2 Updated descriptions of the connection information for ProSafe-RS and iDefine.
Appendix 5.2 Updated descriptions of cautionary notes for upgrading when ALE111 is used.
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."
A1, A2.1 Added descriptions of iDefine.
B3.1 Updated descriptions of removing the Vnet/IP interface card.
C8.1.1 Added descriptions of a computer on which only AD Server is installed and a com-
D1, D1.2 Added information about connecting ProSafe-RS and iDefine.
D1.3 Updated descriptions of ProSafe-RS and PRM.
Appendix 4 Added descriptions of compatibility between revisions and cautionary notes for up-
grading.
Dec. 2015/1st Edition/R4.01
Newly published.
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

Im32p01c50 01en

Uploaded by

Copyright:

Available Formats

Im32p01c50 01en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Im32p01c50 01en

Uploaded by

Copyright:

Available Formats

User's ProSafe-RS

Manual ProSafe-RS Lite

7th Edition : Feb. 2021 (YK) IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

Safety Precautions for Use

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

Indicates that a component such as a power supply switch is turned OFF.

n Notes on Handling User's Manuals

n Warning and Disclaimer

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

Indicates precautions to avoid a danger that may lead to minor or

IMPORTANT Indicates important information required to understand operations or

Indicates referenced content.

l Commonly Used Conventions throughout the User's Manuals

l Conventions Used to Show Key or Button Operations

l Conventions of a User-defined Folder

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

n Explanation of Hardware and Software Behaviors in the User's

n Definitions of Node and Module Terms

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

n Full Names and Simplified Terms

Table Info-1 Full Names and Simplified Terms

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

Copyright and Trademark Notices

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

IM 32P01C50-01EN 7th Edition

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

IM 32P01C50-01EN 7th Edition

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

IM 32P01C50-01EN 7th Edition

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

IM 32P01C50-01EN 7th Edition

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

IM 32P01C50-01EN 7th Edition

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

A1. How to Read This Document

n Structure of This Document

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

A2. Overview of Setup Tasks

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

A2.1 Before You Set Up

n Installation and Licensing of Software Packages

License Management Station SENG

Figure A2.1-1 License Distribution

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

A2.2 Procedures for New Setup

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00

A2.2.1 Setup Procedure for a ProSafe-RS System

Prepare for setup

Build the system in a domain Yes

Set up a computer installed

Set up the computer dedicated

Preparation before starting

The system is built in Yes

*1: You may set up the domain environment at a later stage.

Figure A2.2.1-1 Setup Procedure for a ProSafe-RS System

n Prepare for Setup

IM 32P01C50-01EN 7th Edition : Feb.24,2021-00