7 Features of the ProSafe-RS

Workbench software

Copyright Ó2005 Yokogawa System Center Europe B.V.

Table of contents

7 Features of the ProSafe-RS Workbench software .........................................................7-1

7.1 Features of the ProSafe-RS Workbench software...................................................... 7-3
7.1.1 Chapter objectives ................................................................................................ 7-4
7.1.2 Self-documenting or document generator .............................................................. 7-5
7.1.2.1 Selecting the desired “print” information (Table Tab) ........................................ 7-6
7.1.2.2 Selecting the Options Tab.................................................................................. 7-8
7.1.3 Database Validity Check Tool and Master Database Restoring.............................. 7-9
7.1.3.1 Procedure to execute the Validity Check...........................................................7-10
7.1.3.2 Check Results...................................................................................................7-11
7.1.4 Master Database Restoring Function....................................................................7-12
7.1.5 Version Control ...................................................................................................7-13
7.1.5.1 Procedure for using Version Control.................................................................7-15
7.1.6 Integrity Analyzer................................................................................................7-23
7.1.6.1 Appearance of the Integrity Analyzer................................................................7-24
7.1.6.2 Steps to Run the Safety Analyzer ......................................................................7-26
7.1.7 Cross Reference Analyzer....................................................................................7-29
7.1.7.1 Appearance of the Integrity Analyzer................................................................7-30
7.1.7.2 Steps to Run the Cross Reference Analyzer ......................................................7-32

7-2 RSWB rev 1.2

7.1 Features of the ProSafe-RS Workbench software
This section expands the student's skills in working with the ProSafe-PLC Set software by using the
features provided by the menu bar.

RSWB rev 1.2 7-3

7.1.1 Chapter objectives
After completing this section, the student will be able to use:
· Document generator or Self-documenting
· Database Validity Check Tool
· Master Database Restoring function
· Version Control

7-4 RSWB rev 1.2

7.1.2 Self-documenting or document generator
With the Document Generator it is possible to print out all information concerning the created project.
Information such as graphical presentation of the POUs and also variable lists, binding lists, modbus
addressing etc.
In the figure below the options of the document generator is illustrated.
It is possible to print from the file menu, the print icon or from one of the builders.
In the next sub-paragraph the contents and the layout will be described.

Figure 7-1

RSWB rev 1.2 7-5

7.1.2.1 Selecting the desired “print” information (Table Tab)
When Print is selected you may you may select a number of options available in the Main menu of the
Document Generator.

Figure 7-2

The numbers in the next paragraphs refer to the numbers in Figure 7-2.
1. Two options are available: the cover page and the table of contents
o Cover page:
It is possible to create a bitmap for the cover page. If you omit this then automatically
the Comment of the project, the directory name and the SCSddss name will be
printed.
2. If this option is not selected then all information (in Figure 7-2 balloon 3 and 4) will not be
printed
o The project can theoretically contain more then 1 configuration which can on its turn
contain more resources. All descriptions are the comments defined in the properties in
the workbench.
3. This option displays the configuration specific information.
Information like:

7-6 RSWB rev 1.2

 o Station type
o Station address
o IP number
o CS3000 related information
o Set Cycle time
4. In the resource option you will find information about:
o Used I/O modules
o I/O parameters per I/O card
o Global variables
o Information about Alarm Priorities (CS3000 related information)
o The POUs (the Programs)
Because the size of a sheet is not exactly defined, the size of the information on a
printed sheet will be automatically scaled.

RSWB rev 1.2 7-7

7.1.2.2 Selecting the Options Tab

Figure 7-3

7-8 RSWB rev 1.2

7.1.3 Database Validity Check Tool and Master Database Restoring
As explained in the paragraph “Mandatory Information – Read this first” you know that the ProSafe-
RS has three major databases:

o The Work Database

The Work Database is the database which is stored on the SENG. This Work Database is not
per definition the same as the Master Database
o The Master Database
The Master Database is the database stored on the SENG but which has been downloaded to
the SCS during an on-line change download or off-line download
o The SCS Database
The SCS Database is the database stored on the SCS. This database must be identical to the
Master Database.

The Database Validity Check Tool checks the consistency between the three databases.
Of course is this procedure only useful if all three components have been connected to each other.

Figure 7-4

RSWB rev 1.2 7-9

7.1.3.1 Procedure to execute the Validity Check
The Database Validity Check tool can be activated by selecting the following option from the Link
Architecture window:
1. From the Tools menu select Engineering
2. From the Engineering menu select Database Validity Check Tool
3. From the Database Validity Check Tool activate the Check Start button

Figure 7-5

7-10 RSWB rev 1.2

7.1.3.2 Check Results

Figure 7-6

RSWB rev 1.2 7-11

7.1.4 Master Database Restoring Function
There will only be a Master Database if it has been downloaded to the real SCS database.
Once it has been downloaded it is of importance to keep the three databases consistent.
For example: You have created a new project, built it and download it to the SCS. In this case all
three databases are consistent (Work, Master and SCS).
If you make a new build without downloading this information to the SCS then the Work database
will be different form the Master and SCS.

In practice:
You connect a new PC to the Vnet where the SCS is connected.
You can only get the information from the SCS if you have the Master Database on the new PC.
After this action you can use the Master Database Restoring Function to make the Work and Master
Database consistent with each other.

7-12 RSWB rev 1.2

7.1.5 Version Control
You can use Version Control for the following purposes (see also the figure below):
o Version Control of Project Data
Save engineering data at a project milestone or at the end of engineering in different disks
(check-in).
o Backing up Project Data
Checked-in data can be used as backup data. Checked-in project data can be checked-out and
restored.
o Projects of Engineering Targets when Large-scale Changes are made
When making large-scale changes to a SCS project, it is a good idea to perform engineering
tasks on temporarily copied project data, rather than editing the active project data directly;
this way, the active project data can be replaced with the new project data at the end of
engineering.

Figure 7-7

Version Control Tool manages the history of changes of SCS projects and assists the user with system
upgrading tasks. Version Control Tool allows saving project data of an SCS project at a certain point
with a version number (check-in) and restoring project data of a certain version (check-out).

The user can perform the following operations in Version Control Tool.
o Checking in project data
o Checking out project data
o Deleting versions
o Deleting all check-in data related to a project
o Viewing version information

RSWB rev 1.2 7-13

 o Printing version information
o Specification of check-in folder
o Specification of SCS projects to be managed

7-14 RSWB rev 1.2

7.1.5.1 Procedure for using Version Control
1. You can activate the Version Control from the start menu (see figure below).

Figure 7-8

RSWB rev 1.2 7-15

 Once the Version Control Tool has been activated the following display will show up.

Figure 7-9

2. If a new version control system has to be set up, the figure above doesn’t contain any
information (in the case above you see on the left side ‘All SCS projects’ and on the right side
the versions).
3. Create a Folder (preferably on another drive than where the RS projects are located).
This can be done by selecting Tools from the version control tool (a), b and c as shown in the
figure below.

7-16 RSWB rev 1.2

 Figure 7-10

4. Make sure that the folder where the RS projects (the work databases directory) are located
have been set as Shared.
This can be done as shown in the figure below. From Windows Explorer select the directory
where the RS projects are stored, click with right mouse button (a), select properties (b),
select the tab Sharing (c) and select the option “Share this folder”. Then select the tab
“Security” (d) and change the security for everyone to Allow

RSWB rev 1.2 7-17

 Figure 7-11

7-18 RSWB rev 1.2

 5. After you have created a Folder where the check-in data will be stored from the different
resources (SCSddss), you have to Register a Project. Execute steps a (select from file ->
Register Project) and b (-> enter or browse Project Top) as illustrated in the figure below.

Figure 7-12

RSWB rev 1.2 7-19

7.1.5.1.1 Checking in a Version (from work database to a Version).

1. The following steps should be executed (see also the next figure):
a. Activate the Check-in button (or from the menu edit -> check-in)
b. File in the pop-up menu. The version number can also be changed.
c. Press the Check-in button
d. The result will be a generated version (e). Errors will be displayed in the message
area (f)

Figure 7-13

7-20 RSWB rev 1.2

7.1.5.1.2 Check-out Procedure (From stored version back to Project
Database/work database)

1. Versions which have been checked-in (from Work -> storage) can be checked-out (from storage -
> work). Use the next figure for activating the check-out procedure.
a. Activate the Check-out button (or select from the menu edit -> check-out)
b. Select from the Version control Tool the version you want to check-out (restore to the
work database)
c. Select a Project Folder (or select “Other Folder” with the Browse option).
o If you select “Project Folder” then this folder will have the same structure as
the structure in version you want to restore (check-out). Actually the folder
will be cleared before check-out.
If you select “Other Folder” then a Merge of folders will occur. Files which
have the same names will be overwritten.
Note:
o If you create a new folder, please remember that folder names should not
contain spaces. Not correct is: My Documents
d. After pressing OK two messages (e) will be appear after each other. This is to warn you
that certain files will be overwritten.
e. Watch the Message window for errors.

RSWB rev 1.2 7-21

 Figure 7-14

7-22 RSWB rev 1.2

7.1.6 Integrity Analyzer
The Safety (or Integrity) Analyzer checks if your application is suitable for Safety Applications.
It checks if the used functions and FB are interference free, in other words: checking for use of
Functions or Function Blocks that are not formally validated as being “safe”.

If the Analyzer detects such a situation it will report this. If this has been done unintentionally, the
application logic must be modified. Make changes to the application logic, perform a build operation
and then analyze the application logic with Integrity Analyzer again.

If there is a program that intentionally makes use of functions normally prohibited from use in terms
of safety, you can approve their use. (Of course, such approval can only be made based on the
professional judgment of the engineer, who is presumed trained and qualified to make such judgment.
The Integrity Analyzer simply warns the engineer and requires that he must make specific approval
for such usage)

o Downloading to an SCS cannot be performed before the analysis by Integrity Analyzer and
Cross Reference Analyzer is approved (Cross Reference is explained in the next sub
paragraph).
o Simulation (virtual test on a PC without connection to a SCS) can be done without using the
Integrity Analyzer, although bypassing the Integrity Analyzer is not recommended.

RSWB rev 1.2 7-23

7.1.6.1 Appearance of the Integrity Analyzer.

Figure 7-15

7-24 RSWB rev 1.2

Description of the steps depicted in the figure above:
a. With the menu option Analyze you can start analysis with or without history, generate
reports (in MS word), and Authorize potentially unsafe usage.
Analyze with history means that the Analyzer compares the current run with the previous
run. If it detects unsafe usage which have been approved the previous time, they will be
approved in the current run as well.
Without history the analyzer will execute the check as if it never has been executed
before.
b. Reports in Microsoft word
c. If there are detected unsafe conditions the analyzer will report this. If the user approves
the unsafe condition(s) the program can be downloaded to the real SCS (first the cross
reference analyzer must be executed).
d. The project tree can be sorted as it has been defined in the workbench or on alphabetical
order using the POU name.
e. Detailed information about certain POUs, the language, size, functions or variables can be
shown on the right side of the screen, by selecting one of these options.

RSWB rev 1.2 7-25

7.1.6.2 Steps to Run the Safety Analyzer
The following steps must be executed to start the Safety Analyzer
1. Build the Project. This must be done before you can start the Analyzer. The Analyzer will
respond with an error and will request for compiling/recompiling.
2. Select form the Link/Hardware Architecture the Tools menu, then Engineering followed by the
option Integrity Analyzer.

Figure 7-16

3. If the Integrity Analyzer does not find any errors it will respond a screen similar to the figure
below. You can unfold the SCS0102 to see details.

Figure 7-17

7-26 RSWB rev 1.2

4. In cases an error is found, the Tree will already be unfolded with red colors indicating where the
error is found. The error shown in the figure below caused by the fact that the program was
changed without recompilation. This change can be found in the POU water_inject. The other
POUs are producing errors because no TIC code is generated (no compiled version).

Figure 7-18

5. In cases where a warning is found a yellow color will be displayed.

Figure 7-19

6. You can only continue with a warning if you authorize it. Authorizing can be done by selecting

RSWB rev 1.2 7-27

 the menu option Analyze -> Authorize.

Figure 7-20

7. After clicking the option in the list above the system will respond with a list of Non-compliances
which are acknowledged. If it has been approved , the program can be downloaded.

Figure 7-21

7-28 RSWB rev 1.2

7.1.7 Cross Reference Analyzer
The Cross Reference Analyzer is for localizing the scope of retesting when application logic is
modified. It shows, on screen or on printouts,
o the difference between the application previously downloaded (which runs currently on SCS)
and the application to be downloaded soon
o as well as the extent of impact in case of downloading.
o You can check programs that require re-testing, and print the analysis results. Cross
Reference Analyzer detects programs that depend on the changed program as programs
requiring re-testing. A list of programs requiring re-testing is displayed; they can be approved
upon checking the analysis results of each program.

If unintended program changes or dependencies are evident, the application logic must be re-
modified. Modify the application logic, perform a build operation and then analyze the application
logic with Cross Reference Analyzer again. If no program is found for retesting, retesting will not be
performed. However, since certain modifications on items may not be discovered as requiring
retesting, these modified items need to be tested accordingly.

o Downloading to an SCS cannot be performed before the analysis by Integrity Analyzer and
Cross Reference Analyzer is approved.
o Cross Reference Analyzer detects the differences between the application currently running in
an SCS and the application to be downloaded. It does not detect differences with an
application running in a virtual test. In a virtual test, it is possible to execute and test an
application logic on a PC without having to perform analysis by both analyzers.

RSWB rev 1.2 7-29

7.1.7.1 Appearance of the Integrity Analyzer.

Figure 7-22

Description of the steps depicted in the figure above:

7-30 RSWB rev 1.2

 a. With the menu option Analyze you can start analyzing with or without history, generate
reports (in MS word), and Authorize differences.
Analyze with history means that the Analyzer compares the current run with the previous
run. If it detects differences which have been approved the previous time, they will be
approved in the current run as well.
Without history the analyzer will execute the check as if it never has been executed
before.
b. Reports in Microsoft word
c. If there are detected differences the analyzer will report this. If the user approves the
difference(s) the program can be downloaded to the real SCS (first the Integrity analyzer
must be executed).
d. The project tree can be sorted as it has been defined in the workbench or on alphabetical
order using the POU name.
e. Detailed information about certain POUs, the language, size, functions or variables can be
shown on the right side of the screen, by selecting one of these options.

RSWB rev 1.2 7-31

7.1.7.2 Steps to Run the Cross Reference Analyzer
The following steps must be executed to start the Safety Analyzer
1. Build the Project. This must be done before you can start the Analyzer. The Analyzer will
respond with an error and will request for compiling/recompiling.
2. Select form the Link/Hardware Architecture the Tools menu, then Engineering followed by the
option Cross Reference Analyzer.

Figure 7-23

7-32 RSWB rev 1.2