1 / 42

WW HMI SCADA-01 What’s New in Wonderware Historian 2012 R2

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.

dyllis
Download Presentation

WW HMI SCADA-01 What’s New in Wonderware Historian 2012 R2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WW HMI SCADA-01What’s New in Wonderware Historian 2012 R2 Elliott Middleton Product Manager

  2. Look back…

  3. New Historian Unit Sales In System Platform Standalone Historian 2006 2007 2008 2009 2010 2011 2012 Fiscal Year

  4. New Standalone Historian Revenue First Full Year Of Historian 10.0 Growth Is Enterprise Licenses R-IDAS Enterprise Express Standard 2009 2010 2011 2012 Fiscal Year

  5. New Large Tag Historian Units First Full Year Of Historian 10.0 150,000 100,000 2009 2010 2011 2012 Fiscal Year

  6. Historian 9.0 Architecture SQL Server Retrieval History Blocks “Pull” Data Acquisition Storage “Push” Data Acquisition

  7. Historian 10.0 Architecture SQL Server Retrieval History Blocks Storage Engine IDAS/ SuiteLink “Pull” Data Acquisition Storage Replication Acquisition “Push” Data Acquisition Application Server Historian New “historian” hidden within 10.0

  8. Replication • Organized for faster retrieval • More efficient use of disk I/O via caching • Create tags & start collecting when Historian is offline • Doesn’t “fragment” on updates 10.0

  9. 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

  10. Look forward…

  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

  12. Historian 2012 R2 Architecture SQL Server Retrieval Most changes apply only here History Blocks Storage Engine IDAS/ SuiteLink Application Server >3.5 “Pull” Data Acquisition Classic Storage “Push” Data Acquisition “Push” Data Acquisition Replication Acquisition “Push” Data Acquisition Application Server <3.6 Historian

  13. SMC Status Panel Name Changes Historian 10.0 Historian 2012 R2

  14. Upgrading Application Server <3.6 Historian 10.0 Upgrade Historian First Upgrade Platform First During upgrade, Engine goes into store-forward After upgrade is complete, Engine forwards data and resumes Engine continues using Classic Storage until it is upgraded After Engine upgrade, using new Storage After upgrade is complete, Engine immediately goes into store-forward Remains in store-forward until Historian is upgraded After Historian upgrade, using new Storage Not Recommended No data loss in either scenario

  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

  16. Engine Data Acquisition Throughput 150,000 100,000 10.0 2012 R2 50,000 0 Sustained Burst Late Values Per Second

  17. Historian-Application Server 10.0 2012 R2 Historian Client Wonderware Historian What happens? • Engine goes into store-forward • New attributes not historized • Engine goes into store-forward • New attributes also enter store-forward + Application Server Control System

  18. Historian-Application Server 10.0 2012 R2 Historian Client Wonderware Historian What happens? • All Engines exit store-forward at once • Can overwhelm server & network • Server manages store-forward exit • Prevents overloading Application Server 1 n

  19. Scalability Targets 150,000 values/second 500,000 tags (e.g. ~3 second update rate) Example test load on workstation hardware (Hyper-Threaded)

  20. Stress Testing ? values/second ? tags Oh wow!

  21. Reliable Data Acquisition • On failover, historygap from: • Detecting failure • Starting engine from checkpoint* • Subscribing to I/O* • Initializing history* Historian Client N/A for 2012 R2 Wonderware Historian 140 120 RedundantEngines 100 80 Application Server 60 40 Redundant DI Objects 20 0 System System Control System Platform Platform 2012 R2 2012 * Varies by number of objects

  22. High Availability Historian Client Multiple Clients Reliable Access Redundant Historians (2012 R2) Stratus VMware/Hyper-V Cluster Wonderware Historian Redundant Engines Application Server Reliable Collection Redundant DI Objects Control System

  23. Configuring Redundant Historians MYHISTORIAN02 MYHISTORIAN01

  24. Configuring Redundant Historians MYHISTORIAN02 MYHISTORIAN01

  25. Configuring Redundant Historians MYHISTORIAN02 MYHISTORIAN01

  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%)

  27. How It Works Client retrieves “partner” name On a failure, automatically switches Historian Client B A Engine retrieves “partner” name Sends same data to “partner” with independent store-forward channels H1 H2 Wonderware Historian 1 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

  28. Historian 2012 R2 Communications SQL Server Retrieval SuiteLink (Single TCP Port) Storage Engine Application Server >3.5 “Pull” Data Acquisition Storage “Push” Data Acquisition Replication Acquisition “Push” Data Acquisition “Push” Data Acquisition Application Server <3.6 Historian COM/DCOM Named Pipes WCF (Single TCP Port)

  29. “Data Compression” (aka “Filtering”) No Deadband 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 rate 80 4:5 ? 80 100

  30. Data Compression 10.0 2012 R2 No Deadband Value Deadband Rate Readband Rate Deadband 80 60 30 30 30 80 60 60 80 80 80 30 100 100 100 100

  31. Engine Historian Editor

  32. Bandwidth Limits Will thrash in and out of store-forward Unlimited (0) Physical 500 500 Physical 300 Physical 500 125 375 Streaming 175 175 375 Limit 375 Streaming 200 200 200 Streaming 200 200 Limit 200 Available for store-forward Available for other applications Inadequate bandwidth

  33. Storage Timestamp Limitations Historian 9.0 InSQL 8.0 Late data Expanded Real-time (only for “late data” tags) Real-time Future -5:00 -0:30 “Now” “Values in the past did not fit within the real-time window” “Timestamp overwritten; values in future” ~10x x Thoughput Time Series Data Historian 2012 R2 (AppServer) “Now”

  34. “Late” Data: One Timeline for Storage Example: constant 5-minute latency Store-Forward (3 minutes) Source timestamp 8:00 8:05 8:10 8:15 Stored On Disk No “gap” indication stored on disk Server Time

  35. “Real Time” Data: Two Timelines Example: constant 5-minute latency Store-Forward (3 minutes) Source timestamp Extended Store-Forward (2 minutes) ? 8:00 8:05 8:10 8:15 Stored On Disk What timestamp for “gap”? Out Of Order Out of sequence Server Time Why is this a challenge?

  36. 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

  37. Replication Naming Scheme

  38. Using CSV Files For Data Acquisition 500 CSV files, each for 1,000 tags 100% 10.0 2012 R2 0% Processing # Streams Retrieval Time Time

  39. 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

  40. 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)

  41. The most amazing Wonderware Historian ever

More Related