introduction hardware and software requirements new in version 10.2 coming in version 11 integration...

52

Upload: hayden-dinsdale

Post on 30-Mar-2015

216 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device
Page 2: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device Connectivity Small Application Fundamentals Efficient Integration Techniques Networked Applications Business Systems Connectivity

Agenda

Page 3: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Trihedral

Background‣ 25 years developing HMI software

‣ Global customer base

Corporate OfficesCanadaScotlandUnited States

Page 4: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Mobile Internet Client (MIC) for smart phones and tablets SlippyMaps Tag hierarchy Distributed Historian Support Redesigned security manager with user group support Application Version Control Improved Alarm Dialler Acknowledgements

VTScada 10 – New Features

Page 5: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

More than 150 water/wastewater Integrators throughout North America South America Europe Australia The Middle East

Trihedral provides Wonderware, iFix, Fix32 database conversion services

Local System Integrators

Page 6: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

What is SCADA?

Page 7: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Typical SCADA Users

Page 8: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Communications

Page 9: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Serial (wired) Radio Dial-up Cellular Satellite Ethernet (wired and wireless) Mixed

Communication Mediums

Page 10: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Protocol Drivers Industry standard (Modbus, DF1, etc) Proprietary Report-by-exception (BSAP, DNP3, text messaging, etc) Time-stamped Data-loggers

Telemetry/Polling Methodology Standard - Base station PLC used for site-to-site comms. Advanced – Eliminate base station

◦ Online tuning of polling cycle◦ Ease of troubleshooting◦ Fast poll mode for selected stations

Connectivity

Page 11: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

System Architecture

Page 12: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

The VTScada Concept – Efficient Resource Use Provide software functionality to eliminate hardware Use hardware resources efficiently Include all software components in an integrated package

The result Reduced hardware cost and maintenance Reduced system complexity/component interdependencies Improved reliability

Page 13: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

What is a Tag?

A VTScada tag represents a variable value Tags are the primary building block of SCADA applications All VTScada software licenses are sold by tag limit rather

than page limit Systems can start with a small tag limit and expand over

time

Page 14: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

VTScada License Categories

Full installation (thick) license◦ Required where;

Running services (I/O drivers, historian, alarm server, Internet server)

Developing applications Supporting optional components (alarm dialer, OPC server,

etc)

Thin client –i.e. browser-base client◦ Used for;

Remote monitoring and control (laptops, tablets, handheld devices)

Concurrent access by a pooled group of clients

Page 15: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Full Installation Licenses

Runtime – Any situation where development is not required. Includes

Full Development – Includes Runtime license features. Used in any situation where application development tasks will be performed

Feature Feature Feature

Monitoring Control Alarms

Reporting Security I/O Drivers

Historian Trending Data export

Polling management

Operator logbook

Page 16: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Optional components

Optional Components – Can be added to a Full Installation license

Option Description

Internet Server automatically added when thin clients purchased

OPC Server 3rd party connectivity to VTS real-time data

ODBC Driver SQL connectivity to VTS Historian and real-time data

Web Services 3rd party connectivity to VTS functionality and data

Version Control can only be added to Full Development license

Alarm Dialer voice, email, text message alarm callout

Page 17: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Thin Clients

VTS Internet Client◦ Same graphical displays and features as Runtime license◦ Cannot be used for any VTS services

VTS Mobile Internet Client◦ Text interface for use on handheld devices◦ Monitoring, control, alarms management◦ Mapping interface

Page 18: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Installation

A single installation installs all basic SCADA features

The VTScada License is a 25 character software key (no hardware dongles in most countries.) Defines◦ Tag limit◦ Runtime or Full Development◦ All options the customer has purchased◦ The pool of Thin Clients

As a result, adding new options and Thin Clients or increasing the tag limit is as easy as installing a new key.

Page 19: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

A SCADA Architecture Example

Page 20: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Very Simple SCADA Architecture

Connection to field devices Requires

◦ Monitoring and control ◦ Alarms management◦ Historian with trending

Page 21: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Very Simple SCADA Architecture

I/O drivers are included with purchase of software Server 1 performs as both server and client No separate Historian computer. VTS Historian is included

in license

Page 22: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Adding Alarm Notification

Alarm notification via the Alarm Dialer can use Auto-generated voice dialout Email Text messaging (SMS)

Page 23: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Reliability Through Redundancy

Redundant connectivity to all Ethernet PLCs. Redundant VTS Historian and alarms management Server 2 can be another user interface.

Page 24: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Redundant I/O and Notification

Convert all serial devices to Ethernet to allow communication failover.

No server level computer hardware required.

Page 25: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Adding Local Users

Purchase Runtime or Development licenses based on type of user activity

Page 26: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Adding Remote Access Users

Server’s 1 and 2 automatically provide remote access redundancy.

No Terminal Services or Microsoft CALs required.

Page 27: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Connecting to Business Systems

Users can select from OPC, ODBC or web services connectivity

No Terminal Services or Microsoft CALs required.

Page 28: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Adding Operator Interface Terminals (OIT) Single Interface for all users (Reduced training) Automatic deployment of changes to all user interfaces

Page 29: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Architecture Concepts Applied

Page 30: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Wastewater Collections

Application in focus

Gainesville, FL Wonderware and Dataflow

conversions Centralized configuration of 3

SCADA systems ‘Thin’ operator client licenses Redundant server failover Geographically separated servers

Page 31: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Water Treatment

Application in focus

Fountain Hills, AZ

Multi-plant application Redundant Internet networks

(DSL, Cable) Soft control of remote hardware

Page 32: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Wastewater Treatment

Application in focus

Ocala, FL

FIX and DataFlow database conversion

Distributed, redundant Historian Redundant Alarms Notification Remote laptop connectivity Mobile Internet Client

Page 33: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Water Distribution

Application in focus

Warren County, OH

Wonderware replacement Distribution system and Water

Treatment XLReporter for monthly operating

reports Data extraction using ODBC Server

Page 34: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Hydrology

Application in focus

Southwest Florida Water Management District, FL

River system management Custom RTU programming

interface Datalogger history extraction Public web interface

Page 35: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

VTScada Licensing Summary

Page 36: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Operating System Compatibility

In TestingRelease mid

2013

Supported

Page 37: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Version 10 - Supporting Efficient, Smart Integration

Page 38: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Traditional SCADA Tags Structures

ExampleLS046_P1RunStat (Lift station 46 Pump 1 Running

Status)

Page 39: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

In the Real World, Consistency is the Key to Saving Time and Money

Common equipment and processes reduce installation, training and maintenance costs

Common equipment and processes have typical instrumentation with similar monitoring and control requirements

Equipment is generally standardized by manufacturer (e.g. All liftstations at utility XYZ use Flygt pumps)

There will always be anomalies. Not everything can be standardized.

Page 40: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

In the SCADA World, Consistency is the Key to Saving Time and Money

Common configurations (tags, interfaces) reduce development, training and maintenance costs

Common equipment and process tags can be represented by VTScada’s Parent/Child tag methodology

SCADA standardization is more flexible than the real world, allowing equipment serving the same purpose (e.g. Lift station pumps) to be represented the same even if they are from different manufacturers

There will always be anomalies. Not everything can be standardized.

Page 41: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Why the Parent/Child Tag Metaphor?

CONTROL NETWORK

PLC 1

MOTOR

START/STOP RUNNINGETC

PLC X

PORT

DRIVER 1Inherits Port

Number

CONTEXT

INPUT 1 Inherits DRIVER address and CONTEXT description

INPUT 2 Inherits DRIVER address and CONTEXT description

ETC

DRIVER X

Page 42: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Let’s Revisit our Tags

Page 43: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Putting it all together

Tags are structured in a clear, ordered manner Graphics support the tag structures Where anomalies exist, they are easily addressed through

copy/paste tools

The Moral: Good planning upfront can significantly reduce integration

time.

Page 44: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Applied Networking

Page 45: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Cyber SecurityCommon VTS cyber security applications

Page 46: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Physically separated backup for efficient computer resource use

Distributed Redundancy

Application in focusGeorgetown, KY

Automated Intellution database conversion

Water plant, WW treatment plants, lift stations, and water towers

SCADAPacks, Master ScadaPack 32, Microhard Spectra 900 spread spectrum radios

In house development OPC Server

Page 47: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Centralized Monitoring and ControlAutonomous control – Centralized management

Application in focusColchester, NS

Centralized monitoring and control of 4 separate WWTP applications

Central server capable of backup I/O server functionality

Page 48: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Multi-Plant Application ManagementAutonomous control – Centralized management

Application in focusSacramento, CA

Shared security, and development platform

Distributed historian Each location can function

independently if WAN unavailable

Page 49: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Distributed Historians

Page 50: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Our developers, programmers, and engineers provide the most accessible, reliable and comprehensive support in the industry.

Technical Support

Standard‣ Phone and email‣ Remote Access

Available Upon Request

‣ Onsite support‣ 24/7 support

Page 51: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

"As long as Trihedral keeps offering this level of customer support, there will always be VTScada at Gainesville.”Tom Wallace, Gainesville Regional Utilities, FL

Customer Testimonials

“I can state unequivocally that 'providing quality products with exceptional services' is not only part of your (Trihedral’s) mission statement, but that it really is part of your business culture." Craig Corzine, President, CSE Engineering Inc., CA

"It paid for itself within half an hour of installation." Phil Porter, Plant Manager, Foster-Wheeler, CA

"Absolutely, Trihedral is the way to go. I tell everybody that. I wouldn’t even look at anyone else. The support that I receive and the functionality I get from the system are more than I could have asked for. “ Mark Utesch, SCADA Instrumentation, City of Altamonte Springs, FL

Page 52: Introduction Hardware and Software Requirements New in Version 10.2 Coming in Version 11 Integration and Experience Licensing and Architecture Field Device

Call us1 (800) 463-2783

(Toll-free in North America)

Write [email protected]

Visit our websitewww.trihedral.com

Visit the VTScada Software Forumwww.trihedral.com/forum

© Trihedral Engineering Limited 2011

More Information