Presentation Transcript

1. PBWW111 Introducing ArchestrA System Platform 2012

   John Krajewski Sr. Product Manager HMI/Supervisory Invensys proprietary & confidential
2. Invensys Enterprise Control Offerings Corporate Systems Industry Solutions Services: Consulting, Project Execution, Learning, Operational Improvement, Maintenance & Support Partner Ecosystem Corporate Operations Management Invensys and Third Party Manufacturing / Production Operations Automation Invensys and Third Party Enterprise Control System IT Platform Integration and Collaboration Platform
3. Where The Offerings We Will Discuss Fit Within TheInFusion Enterprise Control System
4. Pillars of Operational Excellence and Focus of This Discussion Operational Excellence Level 3 (Multi-plant/Multi-site) Environment And Safety People Level 2 (Plant Floor/Area) Asset Level 1 (Resource/Asset) Control
5. ArchestrA System Platform 2012and Clients Application Server 2012 Historian 2012 Information Server 2012 InTouch 2012 Historian Client 2012
6. Major Release Themes Reduce Barrier to Entry Security Improvements Support Shift to Server Consolidation Strengthen GEO-SCADA Capabilities Core Runtime Improvements
7. ArchestrA System Platform Topology Engineering Station Engineering Station Workstation Visualization Node Visualization Node Historian Information Server I/O Data Server Galaxy Repository AutomationObject Server AutomationObject Server
8. ArchestrA® Topology InTouch InTouch Engineering Station Engineering Station IDE IDE Workstation InTouch InTouch Bootstrap Bootstrap Bootstrap Bootstrap Galaxy Rep. Historian Info Server Bootstrap Bootstrap Bootstrap Bootstrap Bootstrap IO Server Visualization Node Visualization Node Historian Information Server I/O Data Server Galaxy Repository Bootstrap AutomationObject Server AutomationObject Server
9. ArchestrA System Platform 2012 with InTouch 2012 DVD 1 install disc Wonderware Application Server Wonderware Historian Server Wonderware Information Server InTouch Historian Client Role Based Install
10. Invensys proprietary & confidential Installation User Interface
11. Invensys proprietary & confidential Licensing A single ArchestrA.LIC file can handle all products on the DVD. InTouch Application Server Historian Historian Client Information Server NOT Server based licensing…yet
12. Major Release Themes Reduce Barrier to Entry Security Improvements Support Shift to Server Consolidation Strengthen GEO-SCADA Capabilities Core Runtime Improvements
13. Electronic Signatures Problem Statements Prior to 2012 The permissions for verifier and the operator initiating a change are the same which can result in operators verifying each others work. The currently logged in user is the only user that can perform an electronic signature. The secured/verified writes do not indicate to the operator the reason for his action. The operator cannot enter a comment with the electronic signature. The stored electronic record does not indicate that an electronic signature was executed. No facility for requiring an electronic signature with an alarm acknowledgement.
14. New Secured Write Dialog AppServer 2012 Release Reason for Signature Field Attributes – Associated Description Other Attributes – Object Description Script Function – Custom Message Point Being Written Value Being Written User Entered Comment Credentials Username/Password SmartCard/PIN
15. New Verified Write Dialog AppServer 2012 Release Reason for Signature Point/Value Being Written User Entered Comment Credentials Username/Password SmartCard/PIN
16. New “Can Verify Writes” Functional Permission Role Definition New Functional Permission
17. SignedWrite Script Function SignedWrite( Attribute, Value, ReasonDescription, Comment_Is_Editable, Comment_Enforcement, Predefined_Comment_List);
18. Electronic Record Storage – New Information Alarm Comment Field - 1024 Characters Max (truncated) Reason for Signature User Entered Comment Verified, Secured, or Unsecured Type of Write Verified, Secured, or Unsecured
19. Signed Alarm Acknowledgement User Entered Comment Credentials Username/Password SmartCard/PIN
20. SignedAlarmAck Script Function SignedAlarmAck( Alarm_List, Signature_Reqd_for_Range, Min_Priority, Max_Priority, Default_Ack_Comment, Ack_Comment_Is_Editable, TitleBar_Caption, Message_Caption);
21. Multi-User Kiosk Usage All Signed Writes allow entering a different username than the currently logged on user. Combined with new SignedWrites, SignedAlarmAck, and/or Smart Cards can be used to create a shared Kiosk where all actions are tracked to the user without having to log in/out of the application. Shared Workstation Operator1 Operator2 Operator3
22. Major Release Themes Reduce Barrier to Entry Security Improvements Support Shift to Server Consolidation Strengthen GEO-SCADA Capabilities Core Runtime Improvements
23. Provides High Availability
24. Provides Disaster Recovery
25. Use of VLANs for Communication VLANs Supported for all Node to Node Communications
26. Major Release Themes Reduce Barrier to Entry Security Improvements Support Shift to Server Consolidation Strengthen GEO-SCADA Capabilities Core Runtime Improvements
27. Buffered Data – Problem Statements If multiple field values are received during an AppEngine scan period all but the last are folded. Streaming values from a buffered source must be very slow (one value per scan period) in order to process alarms/history. Data with higher resolution that the scan period cannot be historized.
28. Buffered Data - Configuration Field Attributes
29. Buffered Data - Configuration User Defined Attributes
30. Runtime Result Example Not Buffered Buffered
31. Runtime Result Example Object Viewer
32. Major Release Themes Reduce Barrier to Entry Security Improvements Support Shift to Server Consolidation Strengthen GEO-SCADA Capabilities Core Runtime Improvements
33. Deployment – Mx Value Fragmentation GR Before After MS Default Heap LFH Need Block this size… Cannot allocate due to Heap fragmentation … 32 Byte Segment 16 Byte Segment Problems – Mx Value Fragmentation Using Microsoft's default Heap Due to fragmentation cannot get new blocks Shared by all aagr.exe memory requests Solution – LFH Create Low Fragmentation Heap Designed to target/organize segment types Exclusive for Mx Values Not shared with other aagr.exe requests 1st successful 40-node bench cascade deployment
34. Deployment – Timeouts (Objects) Before After GR AOS GR AOS Engine1 GR Engine1 GR Obj_001 Obj_001 Obj_002 Bootstrap Obj_002 Bootstrap Obj_... Obj_... Obj_...n Obj_...n Must be < 5 mins Problems – Timeouts Typically deploying chunks of 200 objects Engine heartbeat only at beginning and end of all objects being started Mid to large engines easily timeout during startup Causes deployment failures Solution – Frequent Heartbeats Modify “object category package” Notify the bootstrap between object start-ups Notify the bootstrap at least every 5 seconds between objects
35. Deployment – Timeouts (Engines) Before After GR GR AOS AOS Engine1 Engine1 GR GR Engine2 Engine2 Bootstrap Bootstrap Engine3 Engine3 Engine4 Engine4 Engine5 Engine5 Engine6 Engine6 Pair of HB < 30 secs Problems – Timeouts Typically deploying engines in pairs Deployment Heartbeat is for the pair Either startup combination exceeding 30 seconds results in deployment failure Solution – Frequent Heartbeats Modify “Engine category package” Deploy engines individually rather than pairs Internal increase of timeout for engine deployment from 30 secs -> 5 minutes
36. Deployment – Platform Changes Before After GR GR Platform change Must undeploy and redeploy ALL Platform change Just redeploy Platform Problems – Any change to the Platform Large Platform deployments can take 1+ hour All Hosted objects are undeployed Including redundant Engine Leads into potential plant down scenarios described earlier Solution – Just Redeploy Platform object Shuts down all Hosted objects instead of undeploying Reploys only Platform changes Redundant engines can run in partner Can redeploy within 1 minute (if manually shutting down or failing over engines before redeploy)
37. Redundancy – Failover Once Before After Problems – setting mixed in redundant implementation IDE help instructs not to enable in redundant engine Implementation operates also in redundant environment In case engine crash, redundant partner will detect and failover, but can never fail back (orphaned partner) Solution – Manage internally Removed option from user (Improved defaults) Applies to both Platform and Engine objects Engines is always restarted if crash/hang detected. Failover stability improved
38. Redundancy – Restart on Switch Before After Problems – Too many settings Checkbox added to enable restarting the engine process when switching to standby Should not be user configurable Too many user settings to configure Solution – Manage internally Removed option from user (Improved defaults) Engines is always restarted when switching to Standby. Failover stability improved
39. Redundancy – Illegal States Before After Problems – Illegal redundant engine states Engines in Active/Active or Standby/Standby or Failed to start (limbo) Timing problems in engine state detection In Limbo case, must completely recover both nodes Recover includes unsupported operations Solution – Corrected Engine Sync Status Algorithm Increased Engine Startup timeout from 30 secs to 5 mins Corrected handling of transitional states (i.e. both engines in transition / startup) Failover stability improved
40. Major Release Themes Reduce Barrier to Entry Security Improvements Support Shift to Server Consolidation Strengthen GEO-SCADA Capabilities Core Runtime Improvements
41. Thank You