Transcript Wonderware Historianr 2012 R2 (11.0)

Slide 1
WW HMI SCADA-01
What’s New in
Wonderware Historian 2012 R2
Elliott Middleton
Product Manager
© 2012 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.
Look back…
Slide 3
New Historian Unit Sales
In System
Platform
Standalone
Historian
2006
2007
2008
2009
2010
Fiscal Year
Slide 4
2011
2012
New Standalone Historian Revenue
First Full Year Of
Historian 10.0
Growth Is Enterprise
Licenses
R-IDAS
Enterprise
Express
Standard
2009
2010
2011
Fiscal Year
Slide 5
2012
New Large Tag Historian Units
First Full Year Of
Historian 10.0
150,000
100,000
2009
2010
2011
Fiscal Year
Slide 6
2012
Historian 9.0 Architecture
SQL Server
Retrieval
History Blocks
“Pull” Data
Acquisition
“Push” Data
Acquisition
Slide 7
Storage
Historian 10.0 Architecture
SQL Server
Retrieval
IDAS/
SuiteLink
History Blocks
Storage
Engine
“Pull” Data
Acquisition
“Push” Data
Acquisition
Storage
Replication
Acquisition
Application
Server
Historian
New “historian”
hidden within 10.0
Slide 8
Replication
Organized for faster retrieval
More efficient use of disk I/O
via caching
Create tags & start collecting
when Historian is offline
10.0
Slide 9
Doesn’t “fragment” on
updates
Storage Engine Retrieval Performance
Legacy
Storage
>2x
faster
Storage
Engine
Retrieval time for 3-months of
1-second data for 1 tag using “best
fit” with 1-hour period*
*YMMV
Slide 10
Look forward…
Slide 11
The Most Amazing
Wonderware Historian Ever
Continued
• World-class desktop tools
• Rich query capability
• Low management cost & effort
All new integration with Application Server
Significantly higher tag counts
Redundant Historians
SQL Server 64-bit support (2008 R2 and 2012)
New Toolkit
Slide 12
Historian 2012 R2 Architecture
SQL Server
Retrieval
IDAS/
SuiteLink
“Pull” Data
Acquisition
“Push” Data
Acquisition
Application
Server <3.6
Slide 13
Most changes apply only here
History Blocks
Storage
Engine
Classic
Storage
Application
Server >3.5
“Push” Data
Acquisition
Replication
Acquisition
Historian
SMC Status Panel Name Changes
Historian 10.0
Slide 14
Historian 2012 R2
Upgrading
Application
Server <3.6
Upgrade Historian First
1. During upgrade, Engine goes into
store-forward
2. After upgrade is complete, Engine
forwards data and resumes
3. Engine continues using Classic
Storage until it is upgraded
4. After Engine upgrade, using new
Storage
Historian 10.0
Upgrade Platform First
1. After upgrade is complete, Engine
immediately goes into store-forward
2. Remains in store-forward until
Historian is upgraded
3. After Historian upgrade, using new
Storage
Not Recommended
No data loss in either scenario
Slide 15
Application Server: Trivial To Historize
But…
Network/firewall challenges
Must be online to start
Historian tag data not always current
History loss on Engine failover
Slide 16
Engine Data Acquisition Throughput
150,000
100,000
10.0
2012 R2
50,000
0
Sustained
Burst
Values Per Second
Slide 17
Late
Historian-Application Server
10.0
2012 R2
Historian
Client
Wonderware
Historian
What happens?
+
Application
Server
Control System
Slide 18
• Engine goes into
store-forward
• New attributes not
historized
• Engine goes into
store-forward
• New attributes also
enter store-forward
Historian-Application Server
10.0
2012 R2
Historian
Client
Wonderware
Historian
What happens?
Application
Server
1
Slide 19
n
• All Engines exit
store-forward at
once
• Can overwhelm
server & network
• Server manages
store-forward exit
• Prevents
overloading
Scalability Targets
150,000 values/second
500,000 tags
(e.g. ~3 second update rate)
Example test load on
workstation hardware
(Hyper-Threaded)
Slide 20
Stress Testing
? values/second
? tags
Slide 21
Oh
wow!
Reliable Data Acquisition
Historian
Client
Wonderware
Historian
Application
Server
Control System
On failover, history gap from:
• Detecting failure
• Starting engine from checkpoint*
• Subscribing to I/O*
• Initializing history* N/A for 2012 R2
Redundant
Engines
Redundant DI
Objects
140
120
100
80
60
40
20
0
System
Platform
2012
System
Platform
2012 R2
* Varies by number of objects
Slide 22
High Availability
Historian
Client
Wonderware
Historian
Application
Server
Multiple Clients
Redundant Historians (2012 R2)
Stratus
VMware/Hyper-V Cluster
Redundant Engines
Redundant DI Objects
Control System
Slide 23
Reliable
Access
Reliable
Collection
Configuring Redundant Historians
MYHISTORIAN02
MYHISTORIAN01
Slide 24
Configuring Redundant Historians
MYHISTORIAN02
MYHISTORIAN01
Slide 25
Configuring Redundant Historians
MYHISTORIAN02
MYHISTORIAN01
Slide 26
How Does This Compare To:
High Availability Virtualization
• Con: Susceptible to software failures, OS reboots, etc.
• Con: Complex infrastructure, IT support required (SAN)
• Con: Special setup/software for geographically distributed solutions
• Neutral: License cost (more expense for geographically distributed)
Stratus
• Con: Susceptible to software failures, OS reboots, etc.
• Con: Premium hardware (cheaper to use
conventional hardware x2)
• Con: Does not provide geographically distributed solution
• Pro: Single system to maintain
• Pro: No extra Historian license (redundant is +20%)
Slide 27
How It Works
Historian
Client
B
A. Client retrieves “partner” name
B. On a failure, automatically switches
A
H1
H2
Wonderware
Historian
1
1. Engine retrieves “partner” name
2. Sends same data to “partner” with
independent store-forward channels
2
Limitations
• No “self healing” of drive, history blocks,
etc.
• Updates/inserts (SQL, CSV) must be
repeated
• Client won’t switch on “store-forward”
Application
Server
Control System
(optional)
H1 & H2 can be in the same or different locations
Slide 28
Historian 2012 R2 Communications
SQL Server
Retrieval
SuiteLink
(Single TCP Port)
Storage
Engine
“Pull” Data
Acquisition
“Push” Data
Acquisition
Application
Server <3.6
Slide 29
Application
Server >3.5
“Push” Data
Acquisition
Storage
COM/DCOM
Named Pipes
Replication
Acquisition
Historian
WCF
(Single TCP Port)
“Data Compression” (aka “Filtering”)
No
Deadband
80
80
4:5
80
?
100
Slide 30
Example
• Every fifth value is identical
to the previous value
• 25% of remaining values are
close to previous
• %50 of remaining values
change at a steady rate
Data Compression
10.0
No
Deadband
Slide 31
Value
Deadband
2012 R2
Rate
Readband
Rate
Deadband
80
60
30
30
80
60
60
30
80
80
80
30
100
100
100
100
Engine Historian Editor
Slide 32
Bandwidth Limits
Will thrash in and out
of store-forward
Unlimited (0)
Physical
500
Physical
500
Physical
500
375
Streaming
375
125
Limit
300
175
Streaming
200
200
Streaming
175
200
200
Available for store-forward
Available for other applications
Inadequate bandwidth
Slide 33
Limit
375
200
200
Storage Timestamp Limitations
Historian 9.0
InSQL 8.0
Expanded Real-time
(only for “late data” tags)
Late data
-5:00
“Values in the past did not fit
within the real-time window”
Thoughput
~10x
Realtime
-0:30
Future
“Now”
“Timestamp overwritten;
values in future”
x
Time Series Data
Historian 2012 R2 (AppServer)
Slide 34
“Now”
“Late” Data: One Timeline for Storage
Example: constant 5-minute latency
Store-Forward
(3 minutes)
Source timestamp
Stored On Disk
No “gap” indication stored on disk
Server Time
8:00
Slide 36
8:05
8:10
8:15
“Real Time” Data: Two Timelines
Example: constant 5-minute latency
Store-Forward
(3 minutes)
Source timestamp
Extended Store-Forward
(2 minutes)
?
Stored On Disk
What timestamp
forOrder
“gap”?
Out Of
Out of sequence
Server Time
8:00
8:05
8:10
Why is this a challenge?
Slide 37
8:15
System Platform 2012 R2 “Late Data”
No data is discarded, regardless of age & settings
“Late Data”
•Engine disconnects are not marked in data stream
•No latency between Engine & Historian
“Real-time Data”
•Disconnects are marked
•On reconnects, tags remain in store-forward until
source latency is passed
Slide 38
Replication Naming Scheme
Slide 39
Using CSV Files For Data Acquisition
500 CSV files, each for 1,000 tags
100%
10.0
2012 R2
0%
Processing
Time
Slide 40
#
Streams
Retrieval Time
64-bit Microsoft SQL Server Support
Historian Architecture
• OLE DB Provider runs in SQL Server process
• Some interprocess communication via shared memory
• 64-bit SQL Server  64-bit Historian
(mostly, but not all)
Solution in Historian 2012 R2:
• Native 64-bit Microsoft SQL Server Support
• Native 64-bit Historian OLE DB Provider
• 64-bit Process Address Space
• Ability to utilize all installed RAM
Higher scalability will require 64-bit
Phasing out support for case-sensitive collation
Slide 41
Historian Toolkit Compatibility
Historian 9.0 Toolkit
• Continues to work with Historian 9.0-11.0
• No updates for this release
• Uses DCOM for communication
Historian 11.0 Toolkit
• Query history for all tags, including Summary Tags
• Only works with Historian 2012 R2 (aka 11.0)
• Only .NET 4.0, Application Server 2012 R2 (aka 3.6)
• Uses single TCP port for communications
• All new interface (though mapping is straightforward)
• Does not include tag listing (use SQL)
Slide 42
The most amazing Wonderware Historian ever
Slide 43