When planning the diagram hierarchy, the following rules of thumb apply:
Make a
logical structure that relates directly to the monitored process
Let the
hierarchy reflect an increasing degree of detail by making the operator
move from overview diagrams to more detailed diagrams
Use overview
diagrams. See details below.
Design
for fluent access for operators
Access to diagrams
When designing operator access to diagrams, you have two options:
Place the
diagram name in the Diagram menu
by using the Name to Menu option
Make an
overview diagram with click-sensitive fields or buttons that open sub-diagrams
By making an overview diagram for a whole area, the operator can supervise
the alarm status for that area from one diagram. The field or button representing
the diagram where an object is affected by an alarm will blink.
Consider carefully which diagrams
to include in the Diagram menu,
as you can include max. 19 diagrams per area. Of course, you are not limited
to defining 19 diagrams, the remaining ones will merely have to be accessed
via click-sensitive fields or buttons.
Overview diagrams
It is highly recommended to make overview diagrams for the following
reasons:
They provide
easy access to other diagrams. The operator just clicks a field or button
representing the diagram.
They reflect
the diagram hierarchy
They make
the supervision task much easier by limiting the number of diagrams to
monitor
They give
instant indications of alarms at area or diagram level
See AlsoHow To