Fundamentals

Pages 1 to 20 in your workbook

 A Tour of VTScada
• WEB
– Script based, using its own programming language
• VTS
– Visual Tag System. Added a graphical development
environment
• VTScada
– Originally an OEM layer for VTS, providing Water &
WW tools.
– Now, it’s all VTScada
(running on its own programming language)
 The VAM
• VTScada Application Manager.
• Six VTScada controls at the bottom:
– New application, Internet Server, Help, Theme,
Information, Stop
• Five controls for each application:
– Delete, Configure, Import File Changes, Run, Stop
• Can be hidden from operators.
 Pages – An operator’s view
• Hold the visual portion of your application.
• Full screen or pop-up.
• Many, many configuration options.
• Unlimited in number.
– You can limit the number of simultaneous pop-ups.
• Access by security privilege.
• Built-in pages include: Alarms, HDV, Reports,
Operator Notes, Internet Client Monitor, Site
Maps.
 Navigation
• List menu & tiled menu.
– Two versions of the same structure.
• Pinned pages on the navigation bar
– Operator controlled.
• History buttons (Previous & Next).
– Just there. But you control the title bar.
• Hotboxes & page buttons.
– In-page links to other pages.
 Tags
• Represent “things”
– Ports, device drivers, I/O addresses, alarms, loggers,
calculations, ...
• I/O tags subject to your license count limit.
• Configuration can be controlled by expressions.
• Can be disabled.
• You can build your own complex types to
represent equipment.
 Security
• Create an account for each user.
• Create a role to define privileges for groups.
• Roles can contain roles, inheriting privileges.
• Create rules that limit privilege scope to tag
groups.
• Create custom privileges to protect output
tags and pages.
• Many administrative options.
 Alarms
• Often, the most important part of the
application.
• Built into many types of tag.
• Add new alarm tags as required at no cost.
• Many tools in the alarm page for managing the
display and working with alarms.
• Build a custom alarm interface in any page.
• Storage of every operator action as event alarms.
 Alarm Notification System
• Optional component.
• Notify operators of alarms by voice, email, or
SMS-text (, or pager).
• Allow acknowledgement of alarms by the
same.
• Create rosters to control who is contacted
when, how and for what.
 Network Configuration
• Run your application on multiple workstations.
• Automatic fail-over to a defined list of backup
servers.
• Load distribution: one workstation can take the
load of alarm management while the another
takes the load of logging. Define independent
fail-over lists.
• Automatic data backup to multiple workstations.
 Internet & Mobile Access
• An Internet connection is like a run-time
connection.
• The Mobile interface is optimized for phones
where the display area is small and bandwidth
charges are expensive.
• Both allow remote monitoring, control, and
alarm management.
• Neither allow configuration of the user interface.
 Version Control
• Uses a proprietary distributed version control
system.
• Unlimited storage of every configuration
change, logged by user, workstation and time
stamp.
• Unlimited ability to switch to earlier or later
versions, cherry-picking changes from
intermediate steps.
 Application Properties
• How to open.
• Display / Alarms / Other.
• Advanced mode.
– OEM properties versus local properties
– Sections
– When to Edit, Copy or Insert
 The Help Files
• Includes a powerful search tool, an index, and
a glossary.
• Topics grouped for different audiences:
operators, administrators, developers and
programmers.
• Includes a tutorial for developers, covering
most of what you will learn in this course.