ww hmi scada-01 what’s new in wonderware historian 2012 r2
DESCRIPTION
WW HMI SCADA-01 What’s New in Wonderware Historian 2012 R2. Elliott Middleton Product Manager. Look back…. New Historian Unit Sales. In System Platform. Standalone Historian. 2006. 2007. 2008. 2009. 2010. 2011. 2012. Fiscal Year. New Standalone Historian Revenue. - PowerPoint PPT PresentationTRANSCRIPT
Slide 1
© 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.
WW HMI SCADA-01What’s New in Wonderware Historian 2012 R2
Elliott MiddletonProduct Manager
Slide 3
Look back…
Slide 4
New Historian Unit Sales
In System Platform
2006 2007 2008 2009 2010 2011 2012
Standalone Historian
Fiscal Year
Slide 5
New Standalone Historian Revenue
2009 2010 2011 2012Fiscal Year
R-IDASEnterpriseExpressStandard
First Full Year Of Historian 10.0
Growth Is Enterprise Licenses
Slide 6
New Large Tag Historian Units
Fiscal Year2009 2010 2011 2012
150,000 100,000
First Full Year Of Historian 10.0
Slide 7
Historian 9.0 Architecture
SQL Server
Retrieval
History Blocks
Storage
“Pull” Data Acquisition
“Push” Data Acquisition
Slide 8
Historian 10.0 ArchitectureSQL Server
Retrieval
History Blocks
Storage
“Pull” Data Acquisition
“Push” Data Acquisition
StorageEngine
ReplicationAcquisition
New “historian” hidden within 10.0
ApplicationServer
IDAS/SuiteLink
Historian
Slide 9
Replication
Organized for faster retrievalMore efficient use of disk I/O via cachingCreate tags & start collecting when Historian is offlineDoesn’t “fragment” on updates
10.0
Slide 10
Storage Engine Retrieval Performance
Retrieval time for 3-months of 1-second data for 1 tag using “best fit” with 1-hour period*
*YMMV
LegacyStorage
StorageEngine
>2xfaster
Slide 11
Look forward…
Slide 12
The Most Amazing Wonderware Historian EverContinued• World-class desktop tools• Rich query capability• Low management cost & effortAll new integration with Application ServerSignificantly higher tag countsRedundant HistoriansSQL Server 64-bit support (2008 R2 and 2012)New Toolkit
Slide 13
“Push” Data Acquisition
Historian 2012 R2 Architecture
SQL Server
Retrieval
History Blocks
ClassicStorage
StorageEngine“Pull” Data
Acquisition
ReplicationAcquisition
“Push” Data Acquisition
“Push” Data Acquisition
ApplicationServer <3.6
IDAS/SuiteLink
Historian
ApplicationServer >3.5
Most changes apply only here
Slide 14
SMC Status Panel Name Changes
Historian 10.0 Historian 2012 R2
Slide 15
Upgrading
Historian 10.0ApplicationServer <3.6
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
Upgrade Historian First1. After upgrade is complete, Engine
immediately goes into store-forward2. Remains in store-forward until
Historian is upgraded3. After Historian upgrade, using new
Storage
Upgrade Platform First
Not Recommended
No data loss in either scenario
Slide 16
But…Network/firewall challengesMust be online to startHistorian tag data not always currentHistory loss on Engine failover
Application Server: Trivial To Historize
Slide 17
Engine Data Acquisition Throughput
0
50,000
100,000
150,000
Sustained Burst Late
10.02012 R2
Values Per Second
Slide 18
Historian-Application Server
Wonderware Historian
Control System
ApplicationServer
HistorianClient
What happens?
• Engine goes into store-forward
• New attributes not historized
10.0
• Engine goes into store-forward
• New attributes also enter store-forward
2012 R2
+
Slide 19
Historian-Application Server
Wonderware Historian
ApplicationServer
HistorianClient
What happens?
• All Engines exit store-forward at once
• Can overwhelm server & network
10.0
• Server manages store-forward exit
• Prevents overloading
2012 R2
1 n
Slide 20
Scalability Targets150,000 values/second
500,000 tags (e.g. ~3 second update rate)
Example test load on workstation hardware (Hyper-Threaded)
Slide 21
Stress Testing? values/second
? tags Oh wow!
Slide 22
020406080
100120140
Platform2012
SystemPlatform2012 R2
System
* Varies by number of objects
Reliable Data Acquisition
Wonderware Historian
Control System
ApplicationServer
Redundant DI Objects
RedundantEngines
HistorianClient
On failover, history gap from:• Detecting failure• Starting engine from checkpoint*• Subscribing to I/O*• Initializing history* N/A for 2012 R2
Slide 23
High Availability
Wonderware Historian
Control System
ApplicationServer
HistorianClient Multiple Clients
StratusVMware/Hyper-V Cluster
ReliableCollection
ReliableAccess
Redundant Historians (2012 R2)
Redundant DI Objects
Redundant Engines
Slide 24
Configuring Redundant Historians
MYHISTORIAN01
MYHISTORIAN02
Slide 25
MYHISTORIAN01
MYHISTORIAN02
Configuring Redundant Historians
Slide 26
MYHISTORIAN01
MYHISTORIAN02
Configuring Redundant Historians
Slide 27
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 28
B
How It Works
Wonderware Historian
Control System
ApplicationServer
HistorianClient
1
A. Client retrieves “partner” nameB. On a failure, automatically switches
A
1. Engine retrieves “partner” name2. Sends same data to “partner” with
independent store-forward channels
Limitations• No “self healing” of drive, history blocks,
etc.• Updates/inserts (SQL, CSV) must be
repeated• Client won’t switch on “store-forward”
H1 H2
H1 & H2 can be in the same or different locations
2
(optional)
Slide 29
Historian 2012 R2 Communications
SQL Server
Retrieval
Storage
StorageEngine“Pull” Data
Acquisition
ReplicationAcquisition
“Push” Data Acquisition
“Push” Data Acquisition
SuiteLink(Single TCP Port)
COM/DCOMNamed Pipes
WCF(Single TCP Port)
“Push” Data Acquisition
ApplicationServer <3.6
Historian
ApplicationServer >3.5
Slide 30
“Data Compression” (aka “Filtering”)
100
80
80
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 rate4:5
80
No Deadband
?
Slide 31
Data Compression
100
80
80
No Deadband
80
100
80
60
Value Deadband
60
100
80
60
Rate Readband
30
100
30
30
RateDeadband
30
10.0 2012 R2
Slide 32
Engine Historian Editor
Slide 33
Bandwidth Limits
300
200
Physical
Streaming
500
200
Unlimited (0)
Available for other applications
Inadequate bandwidth
175
Physical
Streaming
500
375
Will thrash in and out of store-forward
375
175
200
Physical
Streaming
500
200
Limit 375125
Available for store-forward
200
Limit 200
Slide 34
Storage Timestamp Limitations
-5:00 -0:30 “Now”
Real-time FutureExpanded Real-time
(only for “late data” tags)Late data
xThoughput ~10x
Historian 9.0
Historian 2012 R2 (AppServer)
“Values in the past did not fit within the real-time window” “Timestamp overwritten;
values in future”
Time Series Data
“Now”
InSQL 8.0
Slide 36
“Late” Data: One Timeline for Storage
Source timestamp
Example: constant 5-minute latency
8:00 8:05 8:10 8:15
Stored On Disk
Server Time
Store-Forward(3 minutes)
No “gap” indication stored on disk
Slide 37
“Real Time” Data: Two Timelines
Source timestamp
Example: constant 5-minute latency
8:00 8:05 8:10 8:15
Stored On Disk
Server Time
Extended Store-Forward(2 minutes)
Store-Forward(3 minutes)
Out Of Order?
What timestamp for “gap”?
Why is this a challenge?
Out of sequence
Slide 38
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 39
Replication Naming Scheme
Slide 40
ProcessingTime
Retrieval Time
10.02012 R2
Using CSV Files For Data Acquisition500 CSV files, each for 1,000 tags
100%
0%#
Streams
Slide 41
64-bit Microsoft SQL Server SupportHistorian 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 RAMHigher scalability will require 64-bitPhasing out support for case-sensitive collation
Slide 42
Historian Toolkit CompatibilityHistorian 9.0 Toolkit• Continues to work with Historian 9.0-11.0• No updates for this release• Uses DCOM for communicationHistorian 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 43
The most amazing Wonderware Historian ever