30808_LAB SafeView Overview
30808_LAB SafeView Overview
Contents
Create a Workspace File (Round Robin)............................................................................................. 3
The objective of this Lab is to provide you with the skills necessary to implement appropriate
workspaces for Operators to perform their job. You will use the SafeView Graphical Workspace
Editor (GWE) to implement the workspaces.
After completion of this module, you will have the skills and knowledge to:
Modify an existing (Round Robin) workspace configuration
Implement a different (First Match) workspace configuration
Prerequisites
Introduction
SafeView is a software program developed by Honeywell to enable you to manage the placement of
windows within the Experion PKS Station. SafeView allows you to organize the windows so that
they are easier to find and provides Operators with a consistent and reliable view to the process.
The goal of this unit is for you to become familiar with SafeView fundamentals. These include the
following:
Understand the importance of using SafeView
Identify workspace groups and windows
Design a Match Statement
Identify window properties
These fundamentals will enable you to design effective workspaces.
ATTENTION
Lab Procedure
Modify a Workspace
Step Action
1 If you have performed the previous lab as per pre-defined course sequence then do not
perform this step, else copy the D_100.htm and T_100.htm displays from C:\
ProgramData\Honeywell\Experion PKS\Client\DisplayDB to C:\ProgramData\
Honeywell\Experion PKS\Client\Abstract
Step Action
3 The SafeView window appears displaying the initial tree view workspace named
Untitled.
The primary view provided by the Graphical Workspace Editor (GWE) is a tree view.
The tree view can be expanded to display the structure of a given workspace
configuration, including window groups and specifications. Each of the workspace
components can be individually viewed and edited by using property page dialogs.
5 Browse to the Abstract folder and double-click 2WinRR.WDL to open the workspace file
(or select the filename and then select Open).
Step Action
6 Notice the “Placeholders” that appear behind the SafeView Editor. The Placeholders
show the current two window Round Robin configuration; additional windows have also
been added for the faceplate and a navigation panel display. (You can select the title bar
of the SafeView Editor to move it around the screen to see the various placeholders.)
To show or hide the Placeholders, click the Placeholder menu and from the pull-down
menu. Select “Show All or Hide All “.
The Show All option is selected by default. Leave it as default.
7 Select File > Save As and save this file in the abstract folder as 4WinRR.wdl.
Step Action
In the Workspace Constants tab, you can define constant “names” and values.
It is sometimes more convenient to use constants (aliases) to define the values
you are going to use multiple times within the workspace definition file rather
than using pixel definitions.
Constant “names” (which represent pixel values) can be used to position and
size windows.
Step Action
ATTENTION
The constant
“mainheight” = 100 is the ~ size allocated for the
Menu Area/Message and Command Zones of Station
“statusheight” = 57 is the ~ size allocated for Station’s
status/alarm zone.
While defining constants, User can use expression to
calculate a new value. For example, in above
screenshot Customwidth and Customheight are
obtained by calculations.
Step Action
11
ATTENTION
If you receive the following message, click NO in response to: Update the current
workspace with the current constants?
The property window for operator_views will close after a response is made to the
SafeView Editor dialog box.
Step Action
12 Double click operator_views to open the properties again, and select the
Startup Commands tab.
Under Startup Commands you can enter commands to invoke an application
when the workspace loads (for example, Station.exe).
If there are no startup commands defined, type the following in the Startup Command
box:
C:\Program Files (x86)\Honeywell\Experion PKS\Client\Station\Station.exe
If there are no startup commands listed and you have to enter a Station startup
command as shown above, select the Move to List button. Station will now
automatically open when this SafeView file is launched.
ATTENTION
To populate a window with a custom display at startup, append the Station startup
command with /windows displayname.htm. To add a display startup command,
Select the Move to Edit button and modify the Station launch command. To call
the navigation display nav.htm (which is in your abstract folder), add the string
/windows nav.htm after the Station startup command, if necessary.
The Station and display startup command will read:
C:\Program Files (x86)\Honeywell\Experion PKS\Client\Station\Station.exe
/windows nav.htm
ATTENTION
Step Action
13 Click the PLUS (+) button to the left of operator_views. This expands the workspace.
14 Click the PLUS (+) button to the left of Main. This expands the Main group.
The Main (top level) group directly contains 4 windows (navigation, Status, Main and
Faceplate) – it also contains 1 additional “window groups”. (Recall that each window in a
first match group has its own match expressions – therefore, navigation, Status, Main
and Faceplate will all have individual match criteria for their windows.)
The First Match group type is the only Safeview definition that allows subgroups (such
as the Faceplates and Unit 1 groups that appear in our Safeview file.)
Click Cancel to close the Window Group dialog box.
ATTENTION
Step Action
Step Action
18 Click on the Window Style tab. This is where the size, position constraints, and window
properties for each window are defined.
19 Repeat the above steps (17 & 18) to view the match expression and window styles for
the StatusWindow, MainWindow and FaceplateWindow1.
The StatusWindow has been configured to catch the alarm/status bar in Station
and will not be modified in this lab.
The MainWindow has been configured to catch the top portion of Station – the
menu, toolbar, and command area and message zone. This will not be modified
in your lab exercise.
The FaceplateWindow1 has been configured to catch the faceplate in station
and will not be modified in this lab.
Step Action
Note the Initial X: Y Position. This is the top left corner of the window where the
faceplates will be displayed.
Close the Window Specification dialog after reviewing the entries.
Step Action
21 Expand the Unit1 group. Two windows have been configured for this group,
CustomWindow1 and CustomWindow2.
This is the part of the SafeView file that will be modified to add CustomWindow3 and
CustomWindow4; therefore, the height of the CustomWindows in this workspace must be
changed.
First, double-click Unit1 to view the Window Group dialog.
Note the Group Type (Round Robin). Recall that for a Round Robin Window Group, the
match expression is relevant to all windows in the group. The name Unit1 is the name of
the window group – any/all windows in this Round Robin group will catch displays with a
Unit1 category as shown in the match expression. Also notice the Match Expression and
the use of wild cards (?*). In a Round Robin configuration, the match expression will
apply to ALL windows in the group. Only First Match has an individual window match
expression. Also note that Unit 1 has a Default Match Expression enabled. This means
that this group will catch all displays that do not have a specific category defined on their
Details tab.
Select Cancel when done viewing the Window Group.
Step Action
Double-click on CustomWindow2.
In the Initial Size section, modify the height for window 2:
Initial Position
X: 540
Y: 100
Initial Size
Width: 540
Height: 420
Step Action
23 With CustomWindow2 still highlighted in your SafeView Editor, select the Window Spec
button twice to add two more windows to the Unit1 group just below
CustomWindow2.
24 Double click NewWindow1 and rename the window to CustomWindow3; repeat the
renaming process for CustomWindow4.
Step Action
Step Action
Step Action
28 Another way to resize your windows in Safeview is to drag the border/edge of a window
to get the proper fit and size, and then use the “Update from Layout” icon (which writes
the exact pixel location and window size back to each window’s specification tab).
Notice that when a window has been “graphically” resized, an asterisk * appears in the
window title to indicate a change has been made and the layout must be updated.
Step Action
30
To validate your work and check for errors, click the on the toolbar.
Fix any errors, and resave your workspace, if required.
31 Close the workspace editor, and close any open applications, including Station.
Step Action
33 The SafeView workspace is launched, and the Station application window opens (recall
that Station.exe was listed in the Startup Commands). However, Station opens either
“full screen” or in a smaller window because it has not yet been set for the multi-window
environment of SafeView.
Select Hide on the Control Panel (remember Ctrl+Alt+W to recall the Safeview
Control Panel).
We will now modify the connection properties of Station for a multi-window configuration.
Select Station > Connection Properties as shown below.
ATTENTION
Step Action
Step Action
35 Station will realign within the multi-window environment. The Status bar will appear at
the bottom of your SafeView configuration and the Menu, Toolbar and command zones
will be placed into the top region. However, if the following message box appears due to
the changed configuration, select Cancel and complete Steps 38 and 39.
If no message box appears, go to Step 40.
Step Action
37 Start your 4WinRR SafeView file again. Refer to Step 33, if necessary. Your screen
should look similar to the following example after launching your 4WinRR SafeView
workspace.
ATTENTION
Step Action
38 Using the Navigation window buttons, call displays D_100, E_100, Depropanizer, and
T_100. Click on the point 11_AC12 in the display D_100 to open it’s faceplate.
Note the Round Robin placement of displays.
39 Test the various workspace indicators (icons) at the top right of each window to become
familiar with the functions of SafeView. Also, select a loop shape in your display to call
the faceplate.
Now that you know how to modify an existing workspace, we will design a new workspace.
Example First Match Safeview Workspace
ATTENTION
Step Action
1 Select Start > Honeywell Experion Tools > SafeView Graphical Editor.
2 Select File > Open and open your previous RoundRobin SafeView file (4WinRR).
Select File > Save As and save your workspace as FirstMatch in the Abstract.
The StatusWindow at the bottom will allow access to Station alarms. (The criteria for
the MainWindow and StatusWindow are already defined in your existing workspace
file.)
2 The Main grouping for this workspace configuration will be a First Match group (as
shown below) and contains four windows: Navigation, StatusWindow, MainWindow,
trendwindow and CustomWindow1. (Reminder: Each window in a First Match group
has its own match expression.)
ATTENTION
4 Select Main Window and add New Window Spec from Component.
Then add New Group.
Select New group1 and add New Window Spec.
6 There will also be 1 sub group configured that belong to the Main group. The Faceplates
sub group will be a Round Robin type and contains 2 windows; FaceplateWindow1 and
FaceplateWindow2.
Note and write the match expression. This window grouping (FaceplateWindow1 and
FaceplateWindow2) will catch any display with a category that contains the word
faceplate.
7 Open CustomWindow1.
ATTENTION
The primary window to be used for process displays (the Window Specification shown
above) has an Initial X:Y Position of 0 and100.
The size of the window is 1100 and 563. (By default, “Zoom to fit” is turned on in
Station, so our operating displays should fit well into this window.)
Similarly, for FaceplateWindow2 change the Initial Y Position to 520 -- all other
settings remain the same as that of the FaceplateWindow1.
10 The Navigation window is shown next. Because this window is part of the First Match
“Main” group, it will have its own match expression.
Note: Any display with the word navigation in its category will be managed and
displayed in this window. The frequent use of wild cards is to ensure all displays are
managed.
12 The trendwindow is shown in the following example. Because this window is part of the
First Match Main group, it has its own match expression.
Notice that the Default box is checked for this window. The default match expression
applies only to First Match groups and applies only to the match type category (not title
or module). In other words, any graphic that does not find a specific match expression
(based on its category) will default to this window.
ATTENTION
This is a newly added window; note the boxes that are checked in the Styles section.
14 Recall that in previous illustrations, pixel counts were used for size and position.
Sometimes it is more convenient to use workspace constants to define the values you
are going to use multiple times within the workspace definition file. These “alias” names
(known as constants) can then be used to size and place windows instead of defining
pixel sizes.
To view or define constants, double-click on the top-level operator_views, and
click on the Workspace Constants tab in the Property window.
The constants defined in your previous 4WinRR.wdl SafeView workspace may
need to be changed for your First Match configuration.
To view the Startup Commands for your First Match configuration, select the tab Startup
Commands.
The following is an example of a Startup Command. This command will call up
Station and Nav.htm on SafeView startup.
ATTENTION
15 Begin Lab Practice: Given the previous design criteria, create a First Match workspace
to be used in an operating environment.
When finished, your “running” SafeView workspace should resemble the following
example.
Observe that the windows are positioned and sized according to the WDL file
configuration in SafeView Graphical Editor.