Setup guide

OSx Migration Cookbook August 30, 2006
10 – Hierarchy
OSx Screen
Hierarchy
PCS 7 Plant
Hierarchy
OSx has a concept of a Screen Hierarchy where at runtime,
graphics can be configured so that you can navigate from one
graphic to the next. The navigation topology is a flat graph with up,
down, left, right and home directions. In OSx this hierarchy is
optional. Many implementations navigate via buttons on graphics
or via the graphics selection list.
PCS 7 has a similar hierarchy concept and it is not optional.
Navigation is primarily done through this hierarchy. Navigation via
a graphics selection list is also available, but not the preferred
method. The PCS 7 hierarchy is a tree structure based on up to 49
root graphics.
You implement the PCS 7 hierarchy by creating a folder structure
in the DBA plant view. Each folder is associated with a graphic in
the hierarchy. Normally that graphic has the same name as the
folder, but that can be changed. You then add elements such as tags
and action requests to these folders. Normally you design and create
your hierarchy prior to adding tags and action requests unless you
are using the hierarchy features of the tag auto-assign or the action
request import functions.
The design of this hierarchy is critical as this is how operators will
access process graphics to interact with your process. Unlike OSx,
there is no action request summary. Accessing an action request is
done through its symbol and to get access to that symbol you have
to display the graphic on which the action request’s symbol is
located.
DBA gives you several automated ways to start your hierarchy.
When installing tags or action requests you can create folders based
on the process group descriptions or the parent tags. You will still
need to manually edit the hierarchy by creating, deleting, moving,
and renaming folders to get it the way you want it to be.
25