ppt template - invensysiom.invensys.com/en/usergroupspresentationsdallas2013/wonderwar… · ww...

WW INFO-06Wonderware Historian for InTouchUsers

Presented by:Ray Norman, Invensys

System Consultant

@InvensysOpsMgmt / #SoftwareRevolution

/Wonderware HMI

social.invensys.com

© 2013 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries.All third party trademarks and service marks are the proprietary marks of their respective owners.

Presented by:Ray Norman, Invensys

System Consultant/Wonderware

/company/Wonderware

Agenda

•Historian 101– It’s Important

•InTouch Trend/HistData Review

•Wonderware Historian/Client Overview

•Commissioning Wonderware Historian in 6 (0) Minutes

•InTouch and Historian Client Trend Integration

•Transitioning to System Platform

Slide 3







Agenda







Slide 4







Historian 101

“If you don't know where youare going,you'll end up someplaceelse.”

― Yogi Berra

Slide 5

A Historian Is…A storage repository for time-based information – a Database

But a Historian is much more than a database

– A Historian stores process data - lots of it

– A Historian lets you retrieve the process data – sensibly

– A Historian Transforms the process data into Information

A complete system to enable you to make the best use of this data

Wonderware Historian does this, elegantly

“Store data at the resolution of your Process – Retrieve at theresolution of the Problem you are trying to Solve”

Slide 6

A storage repository for time-based information – a Database

But a Historian is much more than a database

– A Historian stores process data - lots of it

– A Historian lets you retrieve the process data – sensibly

– A Historian Transforms the process data into Information

A complete system to enable you to make the best use of this data

Wonderware Historian does this, elegantly

“Store data at the resolution of your Process – Retrieve at theresolution of the Problem you are trying to Solve”

A Gold Mine !

Slide 7

Agenda







Slide 8







InTouch Trend

Slide 9

InTouch Trend Advantages

• Built-In to InTouch (“Free”)

• Wizard driven Configuration

• Historical data access withHistData

• Scriptable

• “Good Enough”

Slide 10

• Built-In to InTouch (“Free”)

• Wizard driven Configuration

• Historical data access withHistData

• Scriptable

• “Good Enough”

InTouch Trend Disadvantages

• Complex Distributed History

• Terminal Services Limitations

• HistData Limitations

• Requires InTouch Runtime

• Limited Tag Count (Scale)

Slide 11

• Complex Distributed History

• Terminal Services Limitations

• HistData Limitations

• Requires InTouch Runtime

• Limited Tag Count (Scale)

Agenda







Slide 12







Wonderware Historian

Wonderware Historian Solution:

Store Analog, String, and Boolean data at full resolution

– Optional Swinging Door, Time and Value dead-band for Analog

Time-Series data storage with industry-standard retrieval (OLE DB -SQL)

T-SQL Extensions for Time Series Data

– Cyclic, Delta, Full, Best Fit retrieval resolution control

–Analog Aggregate Transformation (Avg, Max – Time at Max, Min –Time atMin, Std. Dev., Integral, To Discrete)

–Discrete Aggregate Transformation (Count, Total, Max, Min, Round Trip)

Answer Process Questions with Actionable Information

Slide 13

Wonderware Historian Solution:

Store Analog, String, and Boolean data at full resolution

– Optional Swinging Door, Time and Value dead-band for Analog

Time-Series data storage with industry-standard retrieval (OLE DB -SQL)

T-SQL Extensions for Time Series Data

– Cyclic, Delta, Full, Best Fit retrieval resolution control

–Analog Aggregate Transformation (Avg, Max – Time at Max, Min –Time atMin, Std. Dev., Integral, To Discrete)

–Discrete Aggregate Transformation (Count, Total, Max, Min, Round Trip)

Answer Process Questions with Actionable Information

Organize information in the context ofyour production.Production Context•Lots•Materials•Recipes•Operators•Machines•Shifts•Plants•Products

Slide 14

Production Context•Lots•Materials•Recipes•Operators•Machines•Shifts•Plants•Products

Analyze information at the resolution ofyour problems.

•Information returned quickly•Conversion to the problem domain

–Trends–Statistics, Integration of rates (Totalizing)–Time in State–Time period Statistics–…

•Time spent deciding not mining

Slide 15

•Information returned quickly•Conversion to the problem domain

–Trends–Statistics, Integration of rates (Totalizing)–Time in State–Time period Statistics–…

•Time spent deciding not mining

Alert and notify when deviations occur.

•Alarm generation on any value•Real-time engine to evaluate conditions•Visualization to device of choice

–Operator Workstation–Browser–Mobile Device

•E-mail of periodic summaries and alerts.•External notification to outside parties.

Slide 16

•Alarm generation on any value•Real-time engine to evaluate conditions•Visualization to device of choice

–Operator Workstation–Browser–Mobile Device

•E-mail of periodic summaries and alerts.•External notification to outside parties.

Correct problems and take actionsimmediately.

•Real-time Command and Control•Adapt processes and operations to productvariations

•Corrective action

•All processes require a Historian – Analog ANDDiscrete!

Slide 17

•Real-time Command and Control•Adapt processes and operations to productvariations

•Corrective action

•All processes require a Historian – Analog ANDDiscrete!

Wonderware Historian Functionality

Value, Data QualityStorage, Compression

Delivers Informationto users

ConfigurationInterfaces

Open Retrieval Interface

Slide 18

Value, Data QualityStorage, Compression

ConfigurationInterfaces

Collects dataOpen Interfaces for Collection

Historian Architecture - Data Acquisition

Historian uses Microsoft SQL Server as the Database Engine for accessto data

However we make extensions to this to enable efficient storage andretrieval

Microsoft SQL Server

Slide 19

Time-Series Data Storage

Wonderware Historian CoreI/O


Data Acquisition & Storage CompressionData Acquisition:

– We need to asynchronously acquire field data from many different data sources

– We must store data as fast as it comes in

– We need to store the data at high resolution (lossless)

– We need flexibility in Storage Strategy–Full

–Time/Value Deadband

–Swinging Door

Data is compressed for efficiency

– Typically 98% compression (lossless), as well as higher with some

minor high frequency information loss (swinging door)

Acquisition Sources PLCs, DCS, RTU, etc.. OPC, SuiteLink, DDE InTouch Application ServerC APISQL

Slide 20

Data Acquisition:

– We need to asynchronously acquire field data from many different data sources

– We must store data as fast as it comes in

– We need to store the data at high resolution (lossless)

– We need flexibility in Storage Strategy–Full

–Time/Value Deadband

–Swinging Door

Data is compressed for efficiency

– Typically 98% compression (lossless), as well as higher with some

minor high frequency information loss (swinging door)

Acquisition Sources PLCs, DCS, RTU, etc.. OPC, SuiteLink, DDE InTouch Application ServerC APISQL

Moore Siemens Honeywell Allen Bradley Yokogawa Modicon

Database?

I can use Access/MySQL/SQL Server/Oracle

- so why do I need a specialized Historian?

Using a simple database as a historian – doesn’t quite work

– Databases are transaction based, Process information is asynchronouslytime based

– Databases were designed for Transactional Data

– Storage and Retrieval is not straightforward

– Plants generate a lot of data, often across slow, distributed networks and atvarying rates

The sheer quantity of data can be is a problem

Slide 21

I can use Access/MySQL/SQL Server/Oracle

- so why do I need a specialized Historian?

Using a simple database as a historian – doesn’t quite work

– Databases are transaction based, Process information is asynchronouslytime based

– Databases were designed for Transactional Data

– Storage and Retrieval is not straightforward

– Plants generate a lot of data, often across slow, distributed networks and atvarying rates

The sheer quantity of data can be is a problem

Data Quantity – A Problem

Imagine a plant, with 1,000 data points to be stored, every second

Each point needs to have stored

– Its Value, its Timestamp, its Quality…

– Probably no less than 10 bytes per record…

How much data?

– 86,000,000+ records daily; 30+ billion annually – over 300GB raw

– An RDBMS typically has a 50x overhead – 15TB+ annually

This is a small example!

– Many plants have much more points, and need online data for years

Slide 22

Imagine a plant, with 1,000 data points to be stored, every second

Each point needs to have stored

– Its Value, its Timestamp, its Quality…

– Probably no less than 10 bytes per record…

How much data?

– 86,000,000+ records daily; 30+ billion annually – over 300GB raw

– An RDBMS typically has a 50x overhead – 15TB+ annually

This is a small example!

– Many plants have much more points, and need online data for years

Data Retrieval


Slide 23

OLE DB Provider

Relational Retrieval Challenges

Independent Records

– Not samples from a continuum

– Can’t infer values between samples

– Can’t relate samples w/o the same timestamp

– Can’t interpolate Time

All Data Treated Equally

– Data quality not factored into aggregate calculations

– No distinction between low-level noise

& significant value changes

– No time weighting for aggregate calculations

– Max/Min calculations do not return timestamp

Slide 24

Independent Records

– Not samples from a continuum

– Can’t infer values between samples

– Can’t relate samples w/o the same timestamp

– Can’t interpolate Time

All Data Treated Equally

– Data quality not factored into aggregate calculations

– No distinction between low-level noise

& significant value changes

– No time weighting for aggregate calculations

– Max/Min calculations do not return timestamp

Data Retrieval

– Historian Introduction

405060708090

100

Slide 25

January 1, 12:00:00 AM January 1, 12:05:00 AM January 1, 12:10:00 AM

010203040

Data Retrieval

Slide 26

AnalogSummaryHistory

Slide 27

StateSummaryHistory

Slide 28

Analog and String State History

Slide 29

Historian Clients

Slide 30

The Face of Wonderware HistorianBringing plant data to life!

Desktop

•Historian Client Trend•Historian Client QueryMicrosoft Office Integration:

•Historian Client Workbook (Excel)•Historian Client Report (Word)

Slide 31

•Historian Client Trend•Historian Client QueryMicrosoft Office Integration:

•Historian Client Workbook (Excel)•Historian Client Report (Word)

Trend

Slide 32

Query

Slide 33

Report

Slide 34

Workbook

Slide 35

Information Server Reporting Website

Out of the boxfunctionality –simply runinstall to getstartedUse theHistorian ClientDesktopapplications tocreate contentUse InformationServer to sharethe information

Slide 36

Out of the boxfunctionality –simply runinstall to getstartedUse theHistorian ClientDesktopapplications tocreate contentUse InformationServer to sharethe information

Why Wonderware Historian?

Low Customer Risk

– Installed Base over 70,000 licenses sold

– Optimal use of COTS - Microsoft SQL Server

Fast Installation and Quick ROI

– “Checkbox” configuration from Application Server

– Tag importer for conventional InTouch applications

– CSV/SQL bulk Load options

Automatically manages historical storage

– Circular, Alternate, Buffer, Permanent

Superior Historian Client Tools

– Trend, Query, Workbook

Slide 37

Low Customer Risk

– Installed Base over 70,000 licenses sold

– Optimal use of COTS - Microsoft SQL Server

Fast Installation and Quick ROI

– “Checkbox” configuration from Application Server

– Tag importer for conventional InTouch applications

– CSV/SQL bulk Load options

Automatically manages historical storage

– Circular, Alternate, Buffer, Permanent

Superior Historian Client Tools

– Trend, Query, Workbook

Agenda




•Commissioning Wonderware Historian in 6(0) Minutes



Slide 38




•Commissioning Wonderware Historian in 6(0) Minutes



Commissioning Wonderware Historian in6(0) Minutes• Installation of Microsoft SQL Server/Service Packs (40 min)

• Prerequisites (.NET 4.5, etc) and Rebooting (15 Min)

• Installation of Historian, InTouch Tag Import (6 min)

• YMMV

– (All time record – 27 min. SQL Server, Historian and InTouch Tag Import)

Slide 39

• Installation of Microsoft SQL Server/Service Packs (40 min)

• Prerequisites (.NET 4.5, etc) and Rebooting (15 Min)

• Installation of Historian, InTouch Tag Import (6 min)

• YMMV

– (All time record – 27 min. SQL Server, Historian and InTouch Tag Import)

Install Historian

Slide 40

Agenda







Slide 41







InTouch and Historian Client TrendIntegration

Slide 42

Leveraging Dual Historians on Top ofInTouch

Slide 43

IDAS IDAS

Agenda







Slide 44







Taking it to the Next Level w/ SystemPlatform

• System Platform Offers Compelling Historian Solutions:

–Superior Data Acquisition Availability

–App Engine Redundancy / Redundant DI Object

–Dual Historians (Don’t Forget 25k/7 Day as an Option!)

–Tiered Historians

•InTouch is the Configuration Source

•Creating the Simple Object.PV

•Galaxy Dump/Galaxy Load

Slide 45

• System Platform Offers Compelling Historian Solutions:

–Superior Data Acquisition Availability

–App Engine Redundancy / Redundant DI Object

–Dual Historians (Don’t Forget 25k/7 Day as an Option!)

–Tiered Historians

•InTouch is the Configuration Source

•Creating the Simple Object.PV

•Galaxy Dump/Galaxy Load

Leveraging Dual Historians & AppServer on Top of InTouch

SP2012R2Historian 11

Slide 46

HCAL HCAL


Slide 47

Leveraging Dual Historians & AppServer on Top of InTouchConvert InTouch DB to App Server Model1. Create Simple Analog with PV UDA

2. Extend with Input and History

3. Create one instance

4. Galaxy Dump the instance

a) Remove unnecessary columns

5. DB Dump the InTouch App

a) Sort each IO group by “Logged”

b) Remove unnecessary columns

6. Copy InTouch Dump Columns to GR Dump Columns

a) Prepend DIObject.ScanGroup to Item Name

7. GR Load

8. Deploy

Slide 48

Convert InTouch DB to App Server Model1. Create Simple Analog with PV UDA

2. Extend with Input and History

3. Create one instance

4. Galaxy Dump the instance

a) Remove unnecessary columns

5. DB Dump the InTouch App

a) Sort each IO group by “Logged”

b) Remove unnecessary columns

6. Copy InTouch Dump Columns to GR Dump Columns

a) Prepend DIObject.ScanGroup to Item Name

7. GR Load

8. Deploy


Slide 49


Slide 50


Slide 51


Slide 52


Slide 53

Leveraging Dual Historians & AppServer on Top of InTouchTo Test:

• 2,000 Simple Analog Objects

• Live Data

• Reactor Demo on separate Machine (Live Data Source)

Slide 54


Slide 55

Leveraging Dual Historians & AppServer on Top of InTouch – 5K IO

Slide 56

Historian 11 and the ExistingInTouch/Historian User• Historian 11 has significant capabilities for the existing

InTouch/Historian User

• Adding Simple Local Historian (25K/7Day)• Historian Client Availability

• Adding System Platform with Massaged InTouch GR Load• Superior Data Availability

– NOTE: The addition of SP to an existing Historian DB adds the .PV to the TagName

– Tag Rename Utility for History Blocks

– Reports may have to be Massaged

– Use Tiered Historian to maintain existing TagName!

Slide 57

• Historian 11 has significant capabilities for the existingInTouch/Historian User

• Adding Simple Local Historian (25K/7Day)• Historian Client Availability

• Adding System Platform with Massaged InTouch GR Load• Superior Data Availability

– NOTE: The addition of SP to an existing Historian DB adds the .PV to the TagName

– Tag Rename Utility for History Blocks

– Reports may have to be Massaged

– Use Tiered Historian to maintain existing TagName!

Questions???

Ray Norman

[email protected]

Slide 58

ppt template - invensysiom.invensys.com/en/usergroupspresentationsdallas2013/wonderwar… · ww...

Documents