Presentation is loading. Please wait.

Presentation is loading. Please wait.

PI System Roadmap Regional Seminar Series Southern California

Similar presentations


Presentation on theme: "PI System Roadmap Regional Seminar Series Southern California"— Presentation transcript:

1 PI System Roadmap Regional Seminar Series Southern California
John Baier Director, Product Management OSIsoft, LLC January 21, 2010

2 Functional Groups of The PI System
Performance Improvement Operational Visibility Knowledge Management Product Quality Lean Manufacturing Asset Management Situational Awareness The Deliver Information for Meaningful, Better Business Decisions Visuals The PI System The Turn Valuable Real-Time Data Into Actionable Information Analytics The PI System is categorized by three major product functions. They are classified in a somewhat self-explanatory way in order to help customers identify relevant functionality. Today, these product packages contain many familiar products, but in time (over the next year to two years) some of these products will become more tightly coupled, and less like independent sets of products that a user will have to decipher and implement. This should also make it easier for a user to understand and buy. The three groups, from bottom to top are The Server, The Analytics, and The Visuals. These names describe their primary logical functionality. Some products may share a presence in several product groups, however their predominant functionality will be represented in a grouping. The Server gives our customers that all-important real-time reference platform upon which they can build applications, reports, and visualizations. Without this layer, they won't have a consistent way to use the information available to them. In other words: many versions of the truth (which is less than ideal). The Analytics provide the server-based analytical functionality and products for The PI System. This now includes PI Analytics (logically) which are the familiar Performance Equations, Totalizers, Alarm, and RTSQC etc. Don't think about it in a deployment sense. That will change soon enough with PIANO and the roadmap. This is LOGICALLY where this functionality lives. It doesn't matter where the actual applications are getting installed. This is a way to help users think about our platform. The Visuals are basically all the client products that talk to The PI System. Both Thin and Smart (or Rich) clients are represented in The Visuals. When we consider the Thin Clients, think of them as a "portal" (note the lower case "p") into the other PI System components… a way to see what's going on. Do NOT think of this as a "Portal" or allow users to get scared off by the name. We are not a portal vendor, but we make parts that can enhance their portal's functionality. Anything that we make that has a face on it will like here. So that may mean that certain visual elements may logically live here (like the RtReports Generator) even though they must get installed elsewhere. All these groupings exist to help users understand the function of our products, not help them navigate product names or install the products we ship them. The Gather, Organize, Distribute, and Store Data from Many Sources Server Structure / Asset Data Real-Time Data Custom Data IT Data Relational Data Web Services ERP / Maintenance 2 2 2

3 Aspects of The PI System
Cross Functional Aspects of the PI System The Deliver Information for Meaningful, Better Business Decisions Visuals The Turn Valuable Real-Time Data Into Actionable Information Scalable Available Reliable Extensible Secure Interoperable Analytics Across the PI System, we are constantly working to make our products scalable, available, etc. The Gather, Organize, Distribute, and Store Data from Many Sources Server 3 3 3

4 Roadmap Themes for 2009-2010 Security Scalability High Availability
64-bit Support High Availability Single Data Directory Model – AF Office 2010 Integration Usability / Productivity Improvements

5 The Servers

6 HA / Failover / Mgt. Services System Management Tools
The PI Servers 4/12/20174/12/2017 The Servers The Analytics The Visuals Data Access Services Web Services OLE DB ODBC OPC / HDA JDBC Module Database PI Notifications HA / Failover / Mgt. Services AF System Management Tools PI Archive Custom Programming At Platform Release 2 we introduce the concept of a “Data Directory” instead of the Module Database and Analysis Framework. The Data Directory is a collection of many features of the platform. The PI AF 2.0 component is the first output of the Foundation development initiative. PI AF 2.0 is an entirely new infrastructure compared to PI AF 1.x. It now requires some version of SQL Server 2005. The Data Directory and the initial delivery of PI AF 2.0 is the beginning of having a more generalized way of finding and accessing data in The PI System. The new database being introduced will do the Analysis Framework type functions as well as some of the Module Database functions. For backward compatibility reasons, the Module Database is still shipped with PI and old AF applications will still work. More will happen with the Data Directory in PR 3 and beyond. Also, further work will be going on in the Failover and High Availability functions of The Server. Also, features like future data, and better security integration, and data quality are being added incrementally to all the functions listed in the diagram. Smart Connectors Smart Connectors represent all of OSIsoft's connectivity technology. The primary members are Interfaces (which connect to systems that usually provide streaming or real-time data), Asset Connectors (an emerging class of connectors that synchronize hierarchal information about assets) and Business Gateways (currently the closest product we have for this are the RLINK Gateways, but others will come). The goal of any member of the Smart Connector family is to connect to a foreign system and pull as much information into The PI System as possible with as little effort as possible. Development is ongoing to ease the configuration burden experienced by a user. Technologies like AutoPointSync, the Interface Configuration Utility, and new tools will have to be further automated or created in order to achieve the goal of near-zero configuration. In the future, many target devices may require an Interface, an Asset Connector, and a Business Gateway. The goal is to be able to deploy all these technologies seamlessly if required. The first Asset Connectors will be introduced at the time that PR 2 is released. These Asset Connectors will have a similar design to our Real-time Interfaces in that they will have a core of technology like UNIINT that keeps the PI AF 2.0 database in sync with a foreign system. The work to create an Asset Connector will become fairly well known, just like the work needed to create a new Real-time Interface. Business Gateways will also start to be introduced around the time frame of PR 2. They will take on some of the tasks of RLINK. They may require calculations, asset data, and real-time data in order to perform their tasks. The idea being that we develop a meaningful connection to business systems or maintenance systems without duplicating our data up in those systems. Even though the PI Analytics are not listed in The Server, the PIANO project will be in its first release at Platform Release 2. This release will allow some of the traditional PI Analytics to be hosted in another server (grouped with The Analytics). In the Data Access family, there will be some changes in the PI OLEDB provider to make it faster and more useful for large Extract, Transform, and Load operations. Also, an OLEDB provider will be introduced for PI AF 2.0. Data Storage, Management Services, Audit Trail, Batch RLINK Real-time Interfaces Structure / Asset Data ERP / Maintenance SAP / JD EDWARDS / MAXIMO Real-Time Data DCS / PLC / SCADA / OPC HISTORIANS / INTERFACES COM CONNECTORS Custom Data APIs / SDKs IT Data IT MONITOR Relational Data OLEDB / ODBC ORACLE / SQL Web Services SOA / EXTERNAL DATA LEGACY APPS Copyright © 2007 OSIsoft, Inc. All Rights Reserved 6 6 6

7 3 concurrent releases for 3 themes
PI Server with Windows Integrated Security Released September 21, 2009 PI AF 2.1 Released September 1, 2009 PI Notifications 1.1 Released September 30, 2009 Integration with Windows Security High Availability More Scalability and Manageability

8 Security PI AF 2.x uses Windows Security since the first release
The PI Server can leverage Windows authentication mechanism PI Notifications leverages both PI AF and the PI Server security

9 High Availability The PI Server has been HA for 3 years
Released in Q1 2007 PI Notifications has been HA since the first release Released in Q1 2008 PI AF 2.1 is now Highly Available

10 Scalability and Manageability
Better performance, scalability and throughput for the PI Server, PI AF and PI Notifications Support for 64bits Native support for the PI Server and PI AF PI Notifications tested as a 32bits running on 64bits New PI SMT 3 plug-ins to manage the new security model Improved manageability for PI Notifications leveraging PI AF Notifications templates

11 PI Server WIS Technical Overview and Value proposition

12 WIS Value Proposition True Single Sign-On (SSO) Easier to Manage
User Accounts in Windows/AD Only Leverage AD Tools and Security Policies Upgrade Experience Backward Compatibility Simply Requires PI SDK 1.3.6 Features Integrates Windows authentication providers into the PI system architecture— more flexible configuration and a more secure PI Server Supports Active Directory and Windows Local Users/Groups— enterprise-wide, user-friendly human interface for security configuration Single sign-on eliminates need for separate PI Server login—greater speed and ease of operation Authentication performed using Microsoft Security Support Provider Interface (SSPI)— no unencrypted passwords sent over network Highly granular access control for all your PI Secure Objects, such as Points and Modules – supports compliance with data protection standards No redundant configuration steps required to define PI users and groups—eliminates the administrative burden of managing a separate user and password database Existing PI System security model still supported—protects your current investment Upgrade involves no loss of configuration and no migration steps—enhances security performance now and adds flexibility to improve over time.

13 WIS Value Proposition More Secure More Flexible
SSPI*-based Kerberos or NTLM** Server-Side Authentication Control No More Default User More Flexible Unlimited Access Control Lists (ACLs) Features Integrates Windows authentication providers into the PI system architecture— more flexible configuration and a more secure PI Server Supports Active Directory and Windows Local Users/Groups— enterprise-wide, user-friendly human interface for security configuration Single sign-on eliminates need for separate PI Server login—greater speed and ease of operation Authentication performed using Microsoft Security Support Provider Interface (SSPI)— no unencrypted passwords sent over network Highly granular access control for all your PI Secure Objects, such as Points and Modules – supports compliance with data protection standards No redundant configuration steps required to define PI users and groups—eliminates the administrative burden of managing a separate user and password database Existing PI System security model still supported—protects your current investment Upgrade involves no loss of configuration and no migration steps—enhances security performance now and adds flexibility to improve over time. *Security Support Provider Interface ** NT LAN Manager

14 New with the PI Server 3.4.380 Release
Improved System Management Tools (PI SMT 3.3)

15 New with the PI Server 3.4.380 Release

16 New with the PI Server 3.4.380 Release
Setup Secure configuration by default, with database consistency checks during upgrade

17 New with the PI Server 3.4.380 Release
PI Backups Added support for incremental backups, verified backups, and a full backup history

18 New with the PI Server 3.4.380 Release
PI Network Manager Major stability and performance enhancements, better handling of connections across unreliable/slow networks High Availability, Scalability Certificate-based authentication between PI Collective members Configurable file size limit on Point and Module Databases beyond 2GB

19 Clients apps and the 3.4.380 release
Clients apps only need to upgrade the PI SDK (released in Q3 2008) to take advantage of the new Security Model Most clients, like PI ProcessBook 3.x and PI Datalink 4.x are already shipping with the PI SDK 1.3.6

20 The PI AF Server

21 PI is about time series … and tags!
PI Archive T2 T3 PI Server: View of all your real-time process data wherever you need it Highly scalable High performance Rapid deployment and easy to configure and maintain Become an essential tool to process engineers around the globe Points database centric: a list of all the points collected from sensors throughout your process. As # of points increases, and the people viewing the data have less expertise in the PI server, a new problem arises: What data should I look at? How do I find my data? These are problems that OSIsoft has been addressing of late. One of the ways we are doing this is by adding new ways to get at your real-time data that has been stored in PI for years… How many tags can you memorize? Does your job description call for memorizing tag names? How consistent is your tag naming convention? What about turnover and new people learning the tags? Next: Context data. T4

22 But Tags mostly relate to assets
PI Archive T2 T3 Physical context or logical context in the case of a plant, line or grouping or abstraction of assets. Accomplished with the MDB and AF 2.0. Show Oil rig and then tank and talk about how the question is more in the context of the plant than the database. Also mention that if you have two oil rigs, you can build displays or calculations to look at an oil rig generically and then apply the context of which oil rig you are concerned with to see the right calculation or visualization. T4

23 Who is using AF today? Oil &Gas Shell, Chevron, TOTAL
Power Generation, T&D AMI, Xcel Energy, AEP, DTE, KCPL, Hydro-Quebec Pulp & Papers Appleton, International Paper, Tembec Data Centers Microsoft, HP, Cornell

24 PI AF 2.1 Technical Overview and Value proposition

25 High Availability Value proposition
Network Failure Administrative/User Failure Upgrades and Migrations Hardware Operating System Software (Patches) Applications Software Software Failure – although Microsoft, Emerson, and OSIsoft test our software – software systems in a time of change can fail. Hardware Failure – servers have become remarkably more reliable but failures can still happen Network Failure – networks have also become more reliable, but also much more complex. These also provide some risk. Administrative/User Failure – when putting in new firewalls, or performing software, hardware, or networking upgrades, or performing administrative procedures, people make mistakes and those mistakes can result in data and availability loss. Operating System upgrades – patches for security are increasingly sensitive – also new versions of the operating system software are do this year and High Availability will assure that data and users will not be interrputed as this is tested and implemented Emerson/OSIsoft upgrades – Emerson and OSIsoft are continuously improving their products. Get the newest DeltaV and PI features without interruptions to data or users. Hardware upgrades / migrations – migrating to a new platform can be done without data or access loss.

26 PI High Availability Architecture
System Management Tools PI SDK ProcessBook, DataLink, RtWebParts, Notifications, ACE, etc. PI Server Collective Secondary PI Server Secondary Metadata Replication Metadata Replication Time-Series Data Data Collection & Buffering

27 High Availability for AF 2.1
Support for Clustering, Mirroring, and Replication (HA) Conceptually very similar to HA for the PI Server Automatic Failover for clients SQL replication for the AF database Mirrored SQL Servers R/W Witness AF Server AF SDK Library Clustered SQL Server AF SDK Library R/W AF Server

28 AF 2.1 HA Collective Express Standard Enterprise Express Standard
AF SDK Library PI Notifications, AF-based PI Clients (WebParts, ProcessBook, DataLink, etc.) PI System Explorer AF Server Collective Secondary Primary Secondary Health Status Health Status SQL Server Replication SQL Server Replication R/O R/W R/O SQL Server Express (primary) Standard Enterprise SQL Server Express (secondary) Standard Enterprise

29 AF 2.1/SQL Server HA Deployments
Non-HA SQL Cluster SQL Mirror AF Collective (Replication) HA Writes No Yes HA Reads Load Balanced Reads Max Distance between SQL Servers N/A tens of meters km thousands of km Read Access during Upgrade? Read/Write Access during OS/SQL Upgrade? Read/Write Access during AF upgrade? Not while upgrading Primary Special Hardware Required? Minimum SQL Server Edition Required Express Standard Primary: Standard Secondary: Express None Good Better Best HA Services

30 64 bit support 2.0 Server was 64-bit capable
Can use either 32 or 64 bit SQL Server 2005 or 2008 Same install kit for 32 vs. 64 bit versions of AF Client or AF Server PI System Explorer can run as a 32 bit application on 64 bits

31 Clients apps and the AF 2.1 Release
PI ProcessBook 3.1 exposes native AF2 datasets PI ProcessBook 3.2 will also support Element Relative Displays (ERDs) – released on Monday (September 21th) ! Limited support in PI DataLink through the AF compatibility layer PI AF support in PI Webparts schedule for year end Beta version of a new AF Configuration add-in for Excel targeted for Q

32 PI Enterprise Server 2010 – PI MDB to PI AF

33 Motivation for MDB to AF upgrade
Moves you forward AF is the future for PI applications AF is richer, more scalable and more flexible Protects your investment No customer left behind policy MDB based solutions keep working Automatic Migration and Synchronization Gradual upgrade process from MDB to AF The back-end first, and then the applications

34 Asset Centric PI: AF Element DB Synch
Module Database AF Element Database PI Asset Subsystem This slide could be removed. It illustrates that we will eventually deprecate the MDB in favor of AF.

35 Asset Centric PI: AF Element DB
ProcessBook Webparts DataLink PI ACE Custom AF based Applications AF Element Database PI Asset Subsystem Module Database This slide could be removed. It illustrates that we will eventually deprecate the MDB in favor of AF.

36 PI Enterprise Server 2010 delivers the MDB to AF subsystem Migration
Synchronization Requirements: AF Server 2.1 must be installed Must upgrade PI Server to first Most applications can use AF natively Some will continue to use MDB for now Release in 2Q 2010 Basic requirements for the upgrade. Batch (removed slide so here’s the scoop): PI Batch data stays on the PI Server All PI Batch clients work as usual All PI Batch units will be migrated PI Server Upgrade only from MDB uses PI security AF uses Windows security supports Windows security PI Enterprise Server 2010 requires first going to , this may only be temporary upgrade, but it is necessary.

37 Data Access

38 HA / Failover / Mgt. Services System Management Tools
The PI Servers 4/12/20174/12/2017 The Servers The Analytics The Visuals Data Access Services Web Services OLE DB ODBC OPC / HDA JDBC Module Database PI Notifications HA / Failover / Mgt. Services AF System Management Tools PI Archive Custom Programming At Platform Release 2 we introduce the concept of a “Data Directory” instead of the Module Database and Analysis Framework. The Data Directory is a collection of many features of the platform. The PI AF 2.0 component is the first output of the Foundation development initiative. PI AF 2.0 is an entirely new infrastructure compared to PI AF 1.x. It now requires some version of SQL Server 2005. The Data Directory and the initial delivery of PI AF 2.0 is the beginning of having a more generalized way of finding and accessing data in The PI System. The new database being introduced will do the Analysis Framework type functions as well as some of the Module Database functions. For backward compatibility reasons, the Module Database is still shipped with PI and old AF applications will still work. More will happen with the Data Directory in PR 3 and beyond. Also, further work will be going on in the Failover and High Availability functions of The Server. Also, features like future data, and better security integration, and data quality are being added incrementally to all the functions listed in the diagram. Smart Connectors Smart Connectors represent all of OSIsoft's connectivity technology. The primary members are Interfaces (which connect to systems that usually provide streaming or real-time data), Asset Connectors (an emerging class of connectors that synchronize hierarchal information about assets) and Business Gateways (currently the closest product we have for this are the RLINK Gateways, but others will come). The goal of any member of the Smart Connector family is to connect to a foreign system and pull as much information into The PI System as possible with as little effort as possible. Development is ongoing to ease the configuration burden experienced by a user. Technologies like AutoPointSync, the Interface Configuration Utility, and new tools will have to be further automated or created in order to achieve the goal of near-zero configuration. In the future, many target devices may require an Interface, an Asset Connector, and a Business Gateway. The goal is to be able to deploy all these technologies seamlessly if required. The first Asset Connectors will be introduced at the time that PR 2 is released. These Asset Connectors will have a similar design to our Real-time Interfaces in that they will have a core of technology like UNIINT that keeps the PI AF 2.0 database in sync with a foreign system. The work to create an Asset Connector will become fairly well known, just like the work needed to create a new Real-time Interface. Business Gateways will also start to be introduced around the time frame of PR 2. They will take on some of the tasks of RLINK. They may require calculations, asset data, and real-time data in order to perform their tasks. The idea being that we develop a meaningful connection to business systems or maintenance systems without duplicating our data up in those systems. Even though the PI Analytics are not listed in The Server, the PIANO project will be in its first release at Platform Release 2. This release will allow some of the traditional PI Analytics to be hosted in another server (grouped with The Analytics). In the Data Access family, there will be some changes in the PI OLEDB provider to make it faster and more useful for large Extract, Transform, and Load operations. Also, an OLEDB provider will be introduced for PI AF 2.0. Data Storage, Management Services, Audit Trail, Batch RLINK Real-time Interfaces Structure / Asset Data ERP / Maintenance SAP / JD EDWARDS / MAXIMO Real-Time Data DCS / PLC / SCADA / OPC HISTORIANS / INTERFACES COM CONNECTORS Custom Data APIs / SDKs IT Data IT MONITOR Relational Data OLEDB / ODBC ORACLE / SQL Web Services SOA / EXTERNAL DATA LEGACY APPS Copyright © 2007 OSIsoft, Inc. All Rights Reserved 3838 38 38

39 Data Access Products Collection of all products that offer programmatic data access to all or part of the PI System SQL tools PI OLEDB Provider PI JDBC Driver PI ODBC Client Web Services PI Web Services (CTP available on OSIsoft vCampus) OPC OPC DA/HDA Server OPC UA Server (CTP available on OSIsoft vCampus) SDKs (for partners/developers) PI SDK AF SDK CTP – Customer Technology Preview

40 Use Cases for Data Access
Integrate with 3rd party products (SQL, Office, SAP) Create reports (SQL Reporting Services, Crystal Reports, Cognos, etc) Share PI data on the Web (SharePoint, ASP.NET, etc) Enterprise Application Integration – EAI (BizTalk, Tibco, etc) Extract, Transform and Load PI data – ETL (SQL, SAP BO, etc) Combine PI with data in other systems (SQL, Oracle, etc) Online Analytical Processing – OLAP (SQL) Visualize with HMI (OPC clients) Develop custom interfaces to PI system Manage PI systems Support virtually any custom application in any programming language on any platform!

41 PI Web Services and PI Data Services
Query Data PI Web Services PI Data Services Session Management Caching Update Management PI SDK AF SDK External Data RDBMS Web Services The PI System PI Server AF Server PI Notifications Event Frames

42 PI Data Access Roadmap PI Web Services 2010 (2Q 2010)
OSIsoft vCampus CTP available now PI OLEDB 3.3 (Released) Support both 32-bit and 64-bit providers PI OLEDB 2010 (2Q 2010) Support for entire PI system, both Tags and AF PI JDBC 1.0 (Released) JDBC-OLEDB Bridge for Windows and Linux, OSIsoft vCampus

43 PI Data Access Roadmap (continued)
OPC DA/HDA Server (Released) Achieved Self-Certification Logo from OPC Foundation PI OPC UA Server Technical Preview (Released) OSIsoft vCampus online, hosted environment PI SDK (Released) Support for both 32-bit and 64-bit providers AF SDK 2.1 (Released) PI SDK (1Q 2010) Client-side buffering for manually entered data, ACE calculations writing to PI, and custom SDK-based interfaces

44 Key Differentiators for Data Access
Support for: Standards Multiple programming languages Multiple hardware and operating system platforms Updates and asynchronous calls for better performance and scalability Simplifies buffering for data writes to ensure no data loss Provides low-level access to all PI system data (including metadata)

45 OSIsoft vCampus

46 OSIsoft vCampus Offering
Includes access to all programmatic interfaces to PI System: AF/AN SDK, PI OLEDB/ODBC, PI SDK, OPC DA/HDA/UA Server Development license for programmatic interfaces Runtime licensing is separate – PAL Programming examples and documentation PI Virtual Campus – community collaboration site Forums Blogs

47 OSIsoft vCampus Website

48 OSIsoft Product Roadmap
Server PI Server ( ) AF (2.1) Notifications (1.2) ACE SMT ( ) Audit Viewer (1.3.x) Edge Processing Analytics TBD Data Access PI SDK (1.4.x) PI API (1.6.2) PI OLEDB Provider (4.0.x) PI Data Services (3.0.x) PI JDBC (1.1.x) OPC UA Server (1.0.x) PI Web Services (1.0.x) OSISoft-MDUS (1.0.x) CTP TBD

49 PI Interfaces

50 HA / Failover / Mgt. Services System Management Tools
The PI Servers 4/12/20174/12/2017 The Servers The Analytics The Visuals Data Access Services Web Services OLE DB ODBC OPC / HDA JDBC Module Database PI Notifications HA / Failover / Mgt. Services AF System Management Tools PI Archive Custom Programming At Platform Release 2 we introduce the concept of a “Data Directory” instead of the Module Database and Analysis Framework. The Data Directory is a collection of many features of the platform. The PI AF 2.0 component is the first output of the Foundation development initiative. PI AF 2.0 is an entirely new infrastructure compared to PI AF 1.x. It now requires some version of SQL Server 2005. The Data Directory and the initial delivery of PI AF 2.0 is the beginning of having a more generalized way of finding and accessing data in The PI System. The new database being introduced will do the Analysis Framework type functions as well as some of the Module Database functions. For backward compatibility reasons, the Module Database is still shipped with PI and old AF applications will still work. More will happen with the Data Directory in PR 3 and beyond. Also, further work will be going on in the Failover and High Availability functions of The Server. Also, features like future data, and better security integration, and data quality are being added incrementally to all the functions listed in the diagram. Smart Connectors Smart Connectors represent all of OSIsoft's connectivity technology. The primary members are Interfaces (which connect to systems that usually provide streaming or real-time data), Asset Connectors (an emerging class of connectors that synchronize hierarchal information about assets) and Business Gateways (currently the closest product we have for this are the RLINK Gateways, but others will come). The goal of any member of the Smart Connector family is to connect to a foreign system and pull as much information into The PI System as possible with as little effort as possible. Development is ongoing to ease the configuration burden experienced by a user. Technologies like AutoPointSync, the Interface Configuration Utility, and new tools will have to be further automated or created in order to achieve the goal of near-zero configuration. In the future, many target devices may require an Interface, an Asset Connector, and a Business Gateway. The goal is to be able to deploy all these technologies seamlessly if required. The first Asset Connectors will be introduced at the time that PR 2 is released. These Asset Connectors will have a similar design to our Real-time Interfaces in that they will have a core of technology like UNIINT that keeps the PI AF 2.0 database in sync with a foreign system. The work to create an Asset Connector will become fairly well known, just like the work needed to create a new Real-time Interface. Business Gateways will also start to be introduced around the time frame of PR 2. They will take on some of the tasks of RLINK. They may require calculations, asset data, and real-time data in order to perform their tasks. The idea being that we develop a meaningful connection to business systems or maintenance systems without duplicating our data up in those systems. Even though the PI Analytics are not listed in The Server, the PIANO project will be in its first release at Platform Release 2. This release will allow some of the traditional PI Analytics to be hosted in another server (grouped with The Analytics). In the Data Access family, there will be some changes in the PI OLEDB provider to make it faster and more useful for large Extract, Transform, and Load operations. Also, an OLEDB provider will be introduced for PI AF 2.0. Data Storage, Management Services, Audit Trail, Batch RLINK Real-time Interfaces Structure / Asset Data ERP / Maintenance SAP / JD EDWARDS / MAXIMO Real-Time Data DCS / PLC / SCADA / OPC HISTORIANS / INTERFACES COM CONNECTORS Custom Data APIs / SDKs IT Data IT MONITOR Relational Data OLEDB / ODBC ORACLE / SQL Web Services SOA / EXTERNAL DATA LEGACY APPS Copyright © 2007 OSIsoft, Inc. All Rights Reserved 5050 50 50

51 Emerson DeltaV Advanced Interface
Configuration Tags Assets Emerson DeltaV & Syncade PI System Time-series data Batch and events data Intro: this is an example for how we are increasing the depth of PI’s integration with control systems. This is only for Version 10.3 of DeltaV. Earlier versions have a different integration story. DeltaV is Emerson’s brand for DCS and Syncade their brand for MES is Syncade This diagram is a simplification of the many sources and destinations for the data. You can buy the components now. We are working on bundling these… For now the bundles are called Smart Connectors. Batches Electronic Work Instructions Time-series Batch

52 OSIsoft Product Roadmap – Interfaces
General Interfaces AutoPointSync (1.2.6) PI UFL (3.2.0) RDBMS (3.17.0) ICU (1.5.0) TBD OPC Interfaces PI OPC UA Interface (1.0) PI OPC Interface / DA (2.4.0) TBD TBD Batch Interfaces Emerson DeltaV (1.0) Rockwell FT Batch (1.0) ABB 800xA (1.0) Siemens Simatic PCS7 (1.0) Wonderware InBatch (1.0) GE iBatch (1.0) Honeywell TotalPlant Batch (1.0) Updated Jan CJC Power Meter Interfaces Elster (1.0.x) Tiilliant Unity (1.0.x) Grid Net PolicyNet (1.0.x) Silver Springs Network UtilityIQ (1.0.x)

53 PI Analytics

54 The Analytics within the PI System
4/12/2017 The Analytics The Server The Visuals Advanced Computing Engine (ACE) PI Notifications RtReports AF Analytics Members of The Analytics group of products are, in some cases, unrelated to each other, but very related to the components of The Server. These products or functions are all analytical in nature (RtReports does quite a bit of analysis prior to generating a report). These are usually centrally installed applications that post results back to The Server. Some may have dedicated clients for use and configuration purposes, however the actual client components will live in The Visuals. The parts that live in The Visuals are the components that render the analytics or reports, not the applications doing the calculation work. The Analytics logically house the PI Analytics group, such as Performance Equations, Totalizers, RTSQC, and Alarm live in this product group now. This is largely due to the PIANO development initiative and the product roadmap. These functions will be able to reference more than one PI Server and also more than just PI data. Therefore, binding them to PI really isn't correct anymore even though this will be haw these elements are delivered in the next release. The other major products in The Analytics are fairly self explanatory. They need a home since they aren't quite clients, and aren't quite servers, or are a blend of everything. So a product that has several parts may get split up between different families (logically speaking). This is especially true if they have different licensing bases (such as RtReports and Sigmafine). If it's split up, the part that crunches goes in The Analytics. The part with a face on it lives in The Visuals. If it's % about the crunching, then it definitely lives in The Analytics! PI Analytics (PI Performance Equations, PI Totalizers, PI Alarms, PI RTSQC) 54 54

55 The Analytics Landscape
Configuration Programming Specific Content PI Tags PI PE, PI Totalizers, PI Alarms, PI RT SQC PI ACE, PI SDK (Custom applications) Generic Content PI Module DB None PI AF AF Analysis Rules PE syntax AF formula DR syntax Additional ARs (roll-up etc.) Clock & Event based scheduling Export results to PI tags Custom AF Data References Custom AF Analysis Rules Custom applications (AF SDK) Goal Members of The Analytics group of products are, in some cases, unrelated to each other, but very related to the components of The Server. These products or functions are all analytical in nature (RtReports does quite a bit of analysis prior to generating a report). These are usually centrally installed applications that post results back to The Server. Some may have dedicated clients for use and configuration purposes, however the actual client components will live in The Visuals. The parts that live in The Visuals are the components that render the analytics or reports, not the applications doing the calculation work. The Analytics logically house the PI Analytics group, such as Performance Equations, Totalizers, RTSQC, and Alarm live in this product group now. This is largely due to the PIANO development initiative and the product roadmap. These functions will be able to reference more than one PI Server and also more than just PI data. Therefore, binding them to PI really isn't correct anymore even though this will be haw these elements are delivered in the next release. The other major products in The Analytics are fairly self explanatory. They need a home since they aren't quite clients, and aren't quite servers, or are a blend of everything. So a product that has several parts may get split up between different families (logically speaking). This is especially true if they have different licensing bases (such as RtReports and Sigmafine). If it's split up, the part that crunches goes in The Analytics. The part with a face on it lives in The Visuals. If it's % about the crunching, then it definitely lives in The Analytics!

56 StreamInsight Platform
.NET C# LINQ StreamInsight Application Development StreamInsight Application at Runtime Event sources Event targets Input Adapters Output Adapters StreamInsight Engine Devices, Sensors Pagers & Monitoring devices Standing Queries KPI Dashboards, SharePoint UI 1 Web servers Query Logic Query Logic 4 2 3 Trading stations Event stores & Databases Query Logic Stock ticker, news feeds Event stores & Databases

57 Power Consumption Monitoring
Visualize Process Information Complex Aggregations/ Correlations AF / PI PI Interface Query Query 1 2 Power Meter Interface Query 3

58 PI Notifications 1.1 Technical Overview and Value proposition

59 PI Notifications Architecture reminder
Others data sources PI ProcessBook PI DataLink MyPI PI Notifications Delivery chanels: Web services OCS v1.0 Custom developed PI Server

60 PI AF support for PI Notifications 1.1
Performance Improvements (start-up and retrieval) Notification Templates enable rapid and automatic creation of maintainable notifications Notification Element Notification Template Element Template Note unseen efforts as well integrating analysis

61 New with the PI Notifications 1.1 release
Notification templates Automate the creation and maintenance process

62 New with the PI Notifications 1.1 release
Performance improvements Can support up to 10k Notifications with multiples rules per Notifications server Can process up to 60k events/minute

63 New with the PI Notifications 1.1 release
Native Office Communication Server R2(OCS)delivery channel v1.0 released in November 2009 Support presence and Instant Messaging (IM) Ships as a plug-in for PI Notifications 1.1 Applications available for major cell phones Windows Mobile BlackBerry iPhone Can use service to send an SMS message (offered by most wireless providers)

64 Clients apps and the PINo 1.1 Release
Improved Notifications pane for PI ProcessBook Support for Notifications reporting in PI DataLink No support in PI Webparts yet

65 OSIsoft Meter Data Unification System (MDUS)

66 OSIsoft Meter Data Unification System
Package of software products and services Software products AMI Interfaces PI Server (PI Data Archive and PI AF) Analytics Framework Web service based interface to SAP Utilities EhP 4 OSIsoft Utilities Gateway Services Pre-sale consulting Architecture and implementation Support

67 OSIsoft MDUS Overview

68 What is the SAP EBS? SAP Endorsed Business Solution contract is a joint development/marketing/sales /support agreement for OSIsoft to license “OSIsoft MDUS” into SAP Utilities customer base, specifically for AMI. Meter Data Unification System. The enabling real-time infrastructure. Application level integration with Solution Qualification to ensure end-to-end business processes for AMI. OSIsoft MDUS is a complimentary solution selected by SAP Product and Industry groups. Product roadmap guided by SAP based on Cooperative Development Agreement Endorsed by SAP sold by OSIsoft See the great work done so far 

69 The Visuals

70 The Visuals within the PI System
4/12/2017 Local Computer The Visuals The Server The Analytics Mobile Device or Browser Graphic Authoring Analysis Reporting Manual Entry PI ProcessBook PI DataLink PI WebParts / iViews for SAP Need to revise this diagram, need a good overall diagram for visuals. This is just a placeholder PI DataLink for Excel Services PI ActiveView PI Manual Logger 70 70

71 PI ProcessBook

72 PI ProcessBook Recent Releases
ProcessBook 3.1 (Released October 2008) Windows security integration PI Notifications integration Trending enhancements ProcessBook 3.2 (Released September 2009) AF Element Relative Displays Display Playback Display Browsing and Bookmarking Office Communicator collaboration integration Statistical Quality Control (SQC) symbol now included 72

73 PI ProcessBook 3.1

74 Requests Addressed in PB 3.1 (Released)
Easier Symbol Formatting Quick Trend Zoom & Pan Data Details in a table Annotations on PI events Vertical Trends available Linear Regression Line on trends Tooltip Statistics on all dynamic symbols Drag and Drop symbol configuration 74

75 Trend Formatting Scroll Zoom Revert

76 Hide/Show Individual Traces

77 Details Pane Data Statistics Point Attributes

78 PI Notifications ProcessBook display as content
ProcessBook display linked as content Instant trend Pass time context to display 78

79 Data Favorites Search Create new Symbols Drag and Drop Favorites
To Display Elements From Search From Favorites To Other applications (Microsoft Excel) Favorites

80 Localization ProcessBook and ActiveView BatchView English French
German Spanish Simplified Chinese Japanese Korean Russian (coming soon) Brazilian Portuguese (coming soon) BatchView 80

81 PI ProcessBook 3.2

82 PB 3.2 - AF Element Relative Displays

83 PB 3.2 - Display Browsing and Bookmarking

84 PB 3.2 - Office Communicator Integration

85 ProcessBook Playback Feature

86 ProcessBook Playback Feature

87 ProcessBook Playback Feature

88 ProcessBook Playback Feature

89 ProcessBook Playback Options

90 PI DataLink

91 DataLink and DataLink for Excel Services
4/12/2017 PI DataLink: Excel add-in for access to real-time and historical PI data PI DataLink for Excel Services (DLES): DataLink spreadsheets on the Web DataLink DataLink for Excel Services 91

92 DataLink and DLES Roadmap
DataLink 4.1 (Released) Support for automatic updating DataLink for Excel Services 4.1 (Released December 2009) Support for 64-bit SharePoint 2007 See “OSIsoft Products and Office 2007 Compatibility FAQ” on Tech Support site PI DataLink 2010 (1H 2010) Support for Office 2010 Better Business Intelligence Support

93 PI WebParts / iViews

94 PI Web Parts - Typical Uses
Integration and Collaboration Access to Process Information Analysis and Reporting

95 PI WebParts today … RtWebParts 2.2 (September 2008 - Released)
PI Web Parts 3.0 (December 2009 – Limited Release) 8 Language Packs (Released for 2.2, 3.0 in April 2010) Japanese Simplified Chinese Korean French Brazilian Portuguese German Spanish Russian Eight Language Pack setup kits are provided for the RtWebParts 2.2 release; Chinese (Simplified), French, German, Japanese, Korean, Portuguese (Brazil), Russian and Spanish. The English version of RtWebParts 2.2 is a prerequisite for each of the eight Language Packs. RtWebParts 2.2 includes several enhancements to facilitate the use of reverse proxy servers based on Microsoft Internet Security and Acceleration (ISA) Server 2006.  Previous versions of RtWebParts were not compatible with the use of front-end, reverse proxy servers. Specifically, the following problems were observed:        When a client user attempted to perform certain operations that relied on web service calls, for example tag searches, PI module data browsing or time range changes, the underlying web service calls were made using an internal, unsecure http address, since RtWebParts did not account for the possibility of a reverse proxy server.  As a result, access to the web server was denied and javascript error messages appeared in the client’s browser.        When an ISA server is configured to use Forms-based Authentication for external users, certain control characters (e.g. CRLF) are inserted into URL query strings, which caused the Ad hoc Trend and Ad hoc SVG features to fail.        When the Selected File property of an RtGraphic web part was configured using an internal link to a document library, attempts to load that web part from an external client would fail.        Hyperlink behaviors in table-based web parts (RtTable, RtTimeSeries and RtValues) would not work for external users if they were configured with fully-qualified internal site URLs. General Web Part Issues In version 2.1, RtWebParts could not be loaded on the same page with other web parts that were not derived from the SharePoint Web Part class.  Attempts to do so would result in InvalidCastException errors.  RtWebParts v2.2 removes this limitation. RtBatchTable q  RtWebParts 2.2 includes a fix for a problem that occurred with RtBatchTable connections in RtWebParts 2.1. Previously, when an RtBatchTable web part was configured as a connection provider, selecting a running batch (one with no end time) in the results list would cause invalid values to be sent to the connected consumer web part.  Specifically, values for the following columns would be incorrect: Module Path, Batch Type, Status, Unit Heading Procedure and Recipe. RtMessenger Fixes

96 PI WebParts Roadmap PI WebParts 3.0 (Released in December 2009)
Product officially rebranded PI WebParts Support for 64-bit operating systems (server side) Support for AF No Support for MDB Fine for AF applications, but MDB based apps must wait PI Enterprise Server 2010 will provide MDB->AF support necessary if you rely on MDB access in Web Parts PI Web Parts 2010 (1H 2010) Support for Office 2010

97 OSIsoft Product Roadmap
Client Desktop ProcessBook (3.2) DataLink (4.1.1) Manual Logger (2.3.x) ProfileView (2.2.x) Web PI WebParts (3.0.x) ActiveView (3.2.x) DataLink Excel Services (4.0.3)

98 2009-2010 Roadmap Note: Future release dates are approximate.
1Q-2Q 2009 3Q-4Q 2009 1Q 2010 2Q 2010 3Q-4Q 2010 1Q-2Q 2011 Client PI ProcessBook PI ActiveView PI WebParts PI DataLink PI DataLink for Excel Services PI Manual Logger RtReports Data Access PI OLEDB PI JDBC PI ODBC PI Web Services PI SDK PI OPC DA/HDA Server Server PI Enterprise Server PI AF PI Notifications PI Batch PI ACE PI Analytics Interfaces PI OPC DA (OPCInt) PI OPC HDA (OPCHDAInt) PI OPC Alarms & Events (opcae) PI to PI Relational Database (RDBMS) PI Universal File Loader (UFL)

99 PI Roadmap – Important Releases
Server: PI Server – Released September 2009 (Security) PI AF 2.1 – August 2009 (64-bit, HA) Released PI Notifications 1.1 – September 2009 (OCS, Templates) PI Data and Web Services – December 2009 (64-bit) PI Enterprise Server 2010 – 2Q 2010 (MDB to AF) Clients: PI ProcessBook 3.2 – Released September 2009 (AF relative displays, Usability) PI WebParts 3.0 – Released December 2009 (64-bit, AF Support) PI DataLink 4.1 for Excel Services (64-bit) - Released December 2009 PI WebParts and DataLinkx 2010 – Office 2010 PI AF 2.1 – August 2009 (sets the stage for others) PI Notifications 1.1 (OCS) – September 2009 PI Server – September 2009 PI Server 3.5 (MDB to AF) – 4Q 2009 PI Data Services – October 2009 Clients: PI ProcessBook 3.2 – September 2009 (add AF relative displays) PI WebParts 3.0 – 4Q 2009

100


Download ppt "PI System Roadmap Regional Seminar Series Southern California"

Similar presentations


Ads by Google