Historian 10 Whats New?

Presentation Details
► What is a Historian – and Why Do I Need
One?
► Wonderware Historian Overview
► Technology Support
► Wonderware Historian 10.0 New Features
► Licensing
► Summary
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 complete system to enable you to make the best use of

this data

► Wonderware Historian does this, elegantly

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
asynchronously time based
• Storage and Retrieval is not straightforward
• Plants generate a lot of data, often across slow, distributed
networks and at varying rates
► The sheer quantity of data can be is a problem
Data Quantity – The 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
Real World Example

► An Integrated Mining Site (South Africa)

• Furnace – stores 2,000 data points per second
• Site – stores 24,000 data updates per second
► Data updates stored:
• >2 billion daily, or over 700 billion annually
• Equivalent to a 350 PB RDBMS database
• (Remember – 50x RDBMS overhead!)
► Compare with London Stock Exchange
• 15 August 2009 – total number of trades was 11,329,182
• This plant does in one day almost 200x the monthly
transactions of the London Stock Exchange!
Time Series Data – The
Problem
► A standard database is good at answering record based
queries:
• How many widgets have we in stock?
• How much did this customer spend last year?
► It is not so good at answering time based questions:
• How long was this motor running?
• How many times was the temperature high for over 10
minutes?
• How many more cycles has this pump before we should
service it?
• How many periods of downtime less than 3 minutes have we
had?
► A Historian is designed to answer these types of queries
► A relational database is NOT
Relational Retrieval Challenges

► Independent Records
• Not samples from a continuum
Can‟t infer values between samples
►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

Wonderware Historian Solution:

Time-series data storage with industry-standard
retrieval
Why Wonderware Historian?

► Wonderware Historian is a solution to the

RDBMS option
► Low Customer Risk
• Installed Base over 25,000 licenses sold
• Optimal use of COTS - Microsoft SQL Server
►Low Lifecycle Costs with System Platform:
• “Checkbox” configuration from Application Server
• Tag importer for conventional InTouch applications
• Automatically manages historical storage
• Monitor operations with system tags
► Highly scalable: from collection-only node
up to clustered system
How Does a Historian Work?
► Key Features of Wonderware Historian

• Data acquisition
• Storage, compression
• Retrieval
 Wonderware Historian
Functionality
Delivers data to users

Open Retrieval Interface

Configuration Value, Data Quality

Interfaces Storage, Compression

Open Interfaces for Collection

Collects data
Historian Architecture - Data
Acquisition
► Historian uses Microsoft SQL Server as the
Database Engine
► However we make extensions to this to
enable efficient storage
Microsoft SQL Server

I/O Wonderware Historian Core

Time-Series Data Storage

Data Acquisition &
Compression
Data Acquisition Challenges:
We need to asynchronously acquire field
data
We must store data much times faster than
Acquisition Sources
standard databases PLCs, DCS, RTU, etc..
OPC, SuiteLink, DDE

We need to store a lot of data InTouch

Application Server

Data is compressed for efficiency

Moore Siemens Honeywell Allen Bradley Yokogawa Modicon
Typically 98% compression
Historian Architecture -
Retrieval
► Once data is stored, we need to be able to
retrieve it
► For Reporting
► For Analysis
► We enable retrieval using standard SQL
Queries
► (SQL is an Open database language)
► We extend SQL to work with our time-
series data
► We also provide tools, so you don‟t need
to know SQL!
Data Retrieval Clients
► We deliver data to users
► - In a format you need

► Wonderware Historian Clients

(ActiveFactory)
► Provide Trend and other graphical views

► Wonderware Information Server

► Provides table based views
► Also can host Historian Clients
 Historian Technology Support

Technology 9.0 10.0

Operating Windows 2000 Windows XP SP3 (32-bit only)
System Windows XP Windows Server 2003 SP2 (32)
Windows Server 2003 Windows Server 2008 SP2 (32/64)
Windows Vista SP2 (32/64)
SQL Server 2000 2005 SP3: 3.3 ms resolution
2005 2008 SP1 (32-bit only): 1 ms

No cluster support planned

 Historian Compatibility
Product Release
Application Server 3.0 SP2, 3.1 SP2
InTouch 10.0 SP2, 10.1 SP2
ActiveFactory 9.2*, 10.0
Information Server 3.1, 4.0

• “In place” upgrades from Historian 9.0 (all patch levels)

• Upgrades from earlier versions require upgrade to 9.0

* Summary tags are not supported in 9.2.

What‟s New in Historian 10.0?
► With Historian 10.0 Wonderware introduces
key new functionality
► Tiered Storage Capability
► Retrieval Enhancements
► Improved ArchestrA Namespace
Integration
► The new multi-tiered architecture capability
• Enables smaller tier 1 Historian to feed to tier 2 for replication
• Enables tier 1 Historian to send aggregated or summary data
to tier 2
• Enables local data access for tier 1 data in distributed
architectures
Historian 9.0 Architecture
ActiveFactory

Microsoft SQL Server

Core

Storage System
I/O
History Blocks
Historian 10.0 Architecture
ActiveFactory

Microsoft SQL Server

“Tier 1” Engine “Tier 2” Engine

From
I/O Tier 1
Tiered Historian – Typical
Architecture
Tier-2
Centralized reporting
& system of record

Tier-1
Local troubleshooting &
buffering Application
I/O Server
InTouch
 Tiered Historian – Data
Replication
Tier 2 Example:
1-second data
Replicate all data
for selected or all
tags

Tier 1 Example: 1-second data

Tiered Historian – Summary
Data
Tier 2 Example:
5-minute, hourly, daily data
“Summary” Tag
Many aggregate
values for each

Tier 1 Example: 1-second data

 Tiered Historian – Multiple Tier-
2
New York London
“Local Tiered” – Summary
Replication

Alternative to existing Summary System

Robust Tiered Historians
► Store-forward between tiers
► Spread load across period when possible
► Propagate From Tier 1
• Store-forward events
• Inserts/Updates
• “Late” Data
► Up to 150,000 tags can be stored per
Historian
Retrieval Modes & State Calculations
ValueState RoundTrip
Min MinContained
Max MaxContained
Average AvgContained
Total TotalContained
Percent PercentContained
MinContained
MaxContained
AvgContained
TotalContained
PercentContained
Retrieval & Industry Affinity
Process Hybrid/Discrete
Best Fit Time-in-State
Integral Integer Counter
Time-weighted Average Round Trip
Interpolated
Rate-of-Change
Minimum/Maximum
Floating point Counter
New in 10.0 Competitive differentiator
New Retrieval Filtering
Filter
Sigma Filter
Analog To Discrete
Snap To

New in 10.0 Competitive differentiator

Application Server Namespace

Object Tagname

Contained name
9.2
IDE
Names In Application Server
Hierarchical Name

Object Tagname

Contained Name

Attribute Reference
Application Server Namespace
ActiveFactory

ArchestrA IDE
Hierarchical Names In
Historian Client 10.0
► Supported In
• Trend
• Query
• Workbook (Excel)
• Report (Word)
• Controls
TagName/
► In Trend Impacts Hierarchical
Name Toggle
• All Tag Labels
• Tag Picker
Pricing and Licensing Updates
► Historian 10.0 is available in two license
options:
• As a stand alone product
• As a part of the System Platform
► With System Platform 4.0
• All System Platform bundles with 5,000 or more history now
will include Tier-2 capable Enterprise Historian
As a stand-alone product
• All Enterprise licenses include Tier 2 capability
• New entry-level 5,000 tag Enterprise Historian introduced
($19,000)
• New license-free low-end Historian
• Functional and version upgrades available
License Levels
► For Stand Alone Historian
► Standard Edition:
• Tag Sizes 500; 5,000; 25,000; 70,000; 100,000
Enterprise Edition:
• Tag Sizes 15,000; 25,000; 70,000; 100,000; 150,000
System Platform Historian Sizes (various I/O
options)
• 250; 1,000; 5,000; 12,000; 50,000; 100,000; 150,000

Note – All Historian Clients will need a WWCAL

(Client Access License)
Entry Level Historian
► Historian 10.0 enables you to implement a
small, free Historian
► Running Historian 10.0 with no license file:
• Historian is limited to 32 user configured stored data points
(tags)
• Retrieval is limited to 7 days (although storage is not)
• This Historian can function as a Tier-1 feed to a Tier-2
Historian
• This Historian can also be used with a local Historian Client
(e.g. Trend)
Example scenarios
• Local storage and analysis for small automation island
• Outstation in geographically distributed SCADA network
• Small data repository for local reporting
Licensing Examples
► Scenario: Stand Alone Tier-1 Historians
with Summary to Tier-2
• Three 5,000 tag Standard Historians
• One Tier-2 Historian for aggregate data
► Licenses Required:
• 3 x 5,000 tag „Any‟ (Standard/Personal…)
• 1 x 12,000 tag Enterprise
Licensing Examples
► Scenario: Disaster Recovery style system
• Three 5,000 tag Standard Historians with Replication

► Licenses Required:
• 3 x 5,000 tag „Any‟ (Standard/Personal…)
• 2 x 12,000 tag Enterprise
Licensing Examples
► Scenario: System Platform with Summary
History to Tier-2
► License Options:
• System Platform with 5,000 History tags or more
or
• Enterprise Historian sized as appropriate

plus
• Tier 1 licenses as appropriate
• Platforms as appropriate
Licensing Examples
► Scenario: SCADA System
► Tier-1 Historians on small „islands‟
► License Options:
• Enterprise Historian sized as appropriate*
plus
• Tier-1: No licenses required!
• (for 32 tags or smaller)

* Or could be System Platform with at least

5,000 history tags
Licensing Examples

► Scenario: Local Summary

► Using Tier-2 capability
within a single node
► License Required:
• Any Historian license
• Does not need to be Enterprise
Summary
► Historian 10.0 is a major release of the best
selling Historian
► Historian 10.0 delivers more value
• For regulatory compliance needs
• For SCADA and networked applications
• For data acquisition and archiving in a disaster recovery
scenario
• For analysis and process improvement
► Updates to supported operating systems
and databases
• All components now 64-bit operating system compatible
• Latest SQL Server (2008) supported
Summary

► Later update for Wonderware Information

Server
• However, System Platform 4.0 and Historian 10.0 licensing
supports this new version which will be available soon as free
upgrade

► Customer FIRST Shipment will include new

System Platform
• System Platform 4.0 and Historian 10.0 upgrades are included
with a Customer FIRST subscription
Powering intelligent plant
decisions in real time.