The Road Ahead: Bridging Platform Releases 1 and 2. Ken Marsh Service Manger OSI Software Asia

Transcription

1 The Road Ahead: Bridging Platform Releases 1 and 2 Ken Marsh Service Manger OSI Software Asia

2 The Platform Release What is it? What is the benefit to you?

3 An Example PI Notificiations Affects at least six different components: Analysis Framework PI System Explorer Tool SDK for Programmatic Access ProcessBook Add-In Desktop Alert Client Web Acknowledgement/Comment

4 Platform Release Timeline

5 Functional Groups of The PI System The Visuals The Analytics The Server Deliver Information for Meaningful, Better Business Decisions Turn Valuable Real-Time Data Into Actionable Information Gathers, Organizes, Distributes, and Stores Data from Many Sources Structure / Asset Data Real-Time Data Custom Data IT Data Relational Data Web Services ERP / Maintenance

6 Direction Platform Release 1 High Availability PI Bridge Release Analysis Framework 2 Windows Security HA Enhancements Future Data Platform Release 2 Partitioning 64-bit PI

7 in PR1 Major Features N-Node Replication of All Metadata HA Services through the PI SDK Easier Deployment, Configuration, and Maintenance Behind the Scene New Metadata Infrastructure New Interface Buffering Enhanced Backup Infrastructure New and Improved SMT

8 Core Today time High-Speed Data Future Data Slow/Lab Data Archive Files Event Queue Snapshot Table Point Database

9 Core with Partitioning Slow, Lab Data Future Data High-Speed Data time Dedicated Snapshot, Queue, and Archives Point Database Partitions

10 Point Count

11 Startup Time

12 Archiving Rate

13 Snapshot Rate

14 Archive Query Rate

15 Recent Security Changes in PI

16 WIS: Simplified Diagram Windows Authentication Identity Mapping Active Directory Security Principals PI Identities Authorizatio n Access Control Lists PI Secure Objects

17 PI High Availability

18 Motivations: Why High Availability? Network Failure Hardware Failure Administrative/User Failure Upgrades and Migrations Hardware Operating System Software (Patches) Applications Software

19 The Business Case for HA Inconvenient to Unacceptable Performance Report Can not be updated because network down Production Report Inaccurate because data acquisition stopped due to software crash Regulatory Data Emissions data lost due to hardware failure Condition-based Maintenance Work orders not generated due to misconfigured IP address Power Outage Transformer overheat goes unnoticed during system upgrade Inconvenient Unacceptable

20 High Availability PI Features Software and Hardware Fault-Tolerant System Interface Failover, Buffering, Replication, SDK Services Near-Independent, Physically Separated Servers No hardware/network restrictions, no limit on server nodes General Benefits Availability, end-user sees one logical system Scalability, system load can be distributed Flexibility, accommodates your environment For IT and Management Simple to configure and manage Simple disaster recovery

21 PI Replication Architecture System Management Tools Thin Clients: RtPortal, RtWebParts, Rich Clients: ProcessBook, DataLink, Custom Application PI-SDK Secondary Secondary PI PI Server Server Configuration Changes Primary Primary PI PI Server Server Secondary (s) Collective Identical Time-Series Data Buffering Services PI Interfaces Failover Mechanism Data Buffering Services PI Interfaces

22 PI Replication Future Data Mining, Business Intelligence Services Enterprise Data Center Node Node Node Node Node Node Node Node Aggregated, Federated Aggregated, Federated PI Clients Regional Center 1 Aggregated Aggregated Regional Center 2 Aggregated Aggregated Client Access Layer PI Caching Server Site A Site B Archive Mirroring Primary Primary Secondary Secondary Primary Primary Secondary Secondary Primary Primary PI PI Interfaces Interfaces PI PI Interfaces Interfaces

23 AF 2.0

24 Shifting Platform Usage Time Series Centric Operations Centric Connectivity Time Context Series Time Series Context (Data Directory) Analytics Data Access Data Access Connectivity Analytics

25 What is AF 2.0? The best of PI MDB and PI AF 1.x combined and a lot more!

26 Why tree structure? Structure is your knowledge applied to your data Structure helps you: Keep track of your assets and data Store your domain expertise Rapidly build applications and displays Find information in user-friendly way

27 AF 2.x: Not Bound to PI Data Data Directory AF 2.0 Asset Database PI Archive Structural Information Time-Series Information Honeywell ABB Delta-V Rockwell Interface Interface Interface Interface SCM RDBMS MES Structural Data Sources Honeywell ABB Delta-V Rockwell Time Series Data Sources

28 AF upgrade utility

29 Migration from PI MDB

30 PI Notifications

31 The Server The Analytics The Visuals Windows Server 2003 SQL Server 2005 Windows Server 2003 Visual Studio.NET PI Archive AF Context Database Real-Time Interfaces RLINK Data Access MCN HealthMonitor PI Alarm RtAlerts Performance Eq. PI Totalizer PI ACE Real Time SQC RtReports Sigmafine

32 The Server The Analytics The Visuals Windows Server 2003 SQL Server 2005 Windows Server 2003 Visual Studio.NET PI Archive AF Context Database PI Notifications Real-Time Interfaces RLINK Data Access PI Analytics MCN HealthMonitor RtReports Sigmafine

33 PI Notifications A new alerting paradigm from OSIsoft Historized alerting Highly available scheduling Escalation Extensible delivery Integration with OSI client tools

34 PI Notification Notification Process Trigger Contacts Content Delivery Acknowledgement

35 Visualization for PI Notifications

36 Platform Releases PR 1 = High Availability (January 2007) Bridge Release (Q1 2008) Introduce AF 2.0 as infrastructure Initial PI Notifications release UI enhancements, MOSS adoption Server throughput, HA, and security improvements PR 2 = Data Directory and Notifications + HA Visualization of AF 2.0 metadata Closer UI integration with PI Notifications PR 3 = Enterprise Data Access and Analysis

37 Any Questions? Thank you!