Lenze VisiWinNet VisiWinNET Smart - Handbuch (Seite 180)

Project example
Creating a visualisation
Creating other forms and navigating between them
4
l
180 SHP−VWNS DE/EN 6.1
4.4.2 Creating other forms and navigating between them
It is rare that a visualisation application will be able to manage with only one screen view.
The usual and more useful approach is to divide it into different screen views according to
the way in which the plant functions or according to its logic. Starting from a central
overview, the user can make use of command buttons to change to the parts of the
application that concern him and then make his entries and carry out his observations
there. In this context, it is necessary to bear in mind that functions are enabled in relation
to particular individuals. For example, it is usual that only a technician and not the
operating personnel are allowed access to a Service page.
Basic structure of a visualisation application
A basic consideration when a visualisation application is being set up is the way in which
the screen views are divided up. The following is a typical example:
Central overview
Log-on dialogue
Messages
Details
Service/Technical
Parameterisation
Data update
Recipes
Personnel
administration
Each of the function blocks shown here represents a screen view. The hierarchy shows how
the forms are to be logically linked to each other, i.e. which form can be called and from
where. If, for example, you are in the central overview and want to gain access to the
individual function blocks underneath it, at least five command buttons are necessary.
It is a question of taste whether screen pages that are parallel to each other need to be
logically linked to each other. However, one exception is without doubt an alarm view page
that it should always be possible to reach from any part of the application.