PI System Roadmap Regional Seminar Series August 11, 2009 Tom Hosea Product Manager OSIsoft, Inc. August 11, 2009

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

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

Roadmap Themes for 2009 Security Server Scalability 64-bit Support AF Support for all products

The Visuals

The Visuals within the PI System 4/22/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 6 6

PI ProcessBook

Requests Addressed in PI ProcessBook 3.1 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 8

Symbol Formatting Toolbar Easy formatting from tool bar Copy palette from one trend to another

Format Paintbrush

Zoom In / Zoom Out 2x

Hide/Show Individual Traces

Details Pane Events Annotations

Vertical Trends

Copyright © 2007 OSIsoft, Inc. All Rights Reserved Trend Regression Line Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Statistics: ToolTips and Details Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Data Favorites

Drag and Drop Configuration From Favorites list From Search results From other applications (e.g., Excel) Add to existing trends Create new symbols (Trend, XY plot, Bar, Value) Build mode only Data Favorites window

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

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

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

PI ProcessBook 3.2 Element Relative Displays

PI WebParts / iViews

Typical Uses Integration and Collaboration Access to Process Information Analysis and Reporting iViews example PI WebParts example

RtWebParts Roadmap RtWebParts 2.2 (September 2008) 8 Language Packs (March 2009) 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

PI WebParts Roadmap PI WebParts 3.0 (Q4 2009) PI WebParts 4.0 (2010) Product will be officially rebranded PI WebParts Support for 64-bit operating systems Support for AF PI WebParts 4.0 (2010) Support for Microsoft Silverlight Support for Sharepoint 2010

PI DataLink

Copyright © 2007 OSIsoft, Inc. All Rights Reserved OSIsoft and Microsoft Microsoft Global ISV Industry Partner for 2009!! Microsoft Office Business Application Partner 2009!! OSIsoft is a Gold Certified and Global ISV Partner Partnership for 15+ years Office 2007 Invited to the Developer Advisory Council Member of the Technology Adoption Program Results in new DataLink for Excel Services product Office 2010 Part of Technology Adoption Program New integration capabilities forthcoming Finalist – ISV/Software Solutions Partner of the Year Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PI DataLink and DataLink for Excel Services 4/22/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 29

DataLink and DLES Roadmap DataLink 4.1 (Current) Support for automatic updating DataLink for Excel Services 4.1 (Q4 2009) Support for 64-bit SharePoint 2007 See “OSIsoft Products and Office 2007 Compatibility FAQ” on Tech Support site

The Visuals - Roadmap Updated August 2009

PI Analytics

The Analytics within the PI System 4/22/2017 The Analytics The Server The Visuals Advanced Computing Engine (ACE) PI Notifications RtReports Enterprise Services 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 80-100% about the crunching, then it definitely lives in The Analytics! PI Analytics (PI Performance Equations, PI Totalizers, PI Alarms, PI RTSQC) 33 33

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 Custom AF Data References Custom AF Analysis Rules Custom applications (AF SDK) 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 80-100% about the crunching, then it definitely lives in The Analytics!

The Analytics Landscape Goal 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) 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 80-100% about the crunching, then it definitely lives in The Analytics!

PI Notifications

What’s coming with PI Notifications 1.1? Performance improvements Up to 10,000 Notifications with multiple rules Up to 60,000 events/minute Notification templates Release candidate for August 2009 Native Office Communication Server (OCS) delivery channel Scheduled for release in August 2009 Shipped as a new plug-in for v1.1

PI Notifications templates

The Servers

HA / Failover / Mgt. Services System Management Tools The Servers 4/22/20174/22/2017 The Servers The Analytics The Visuals Data Access 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 4040 40 40

The PI Server

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.

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

PI Server WIS 3.4.380 – Value Proposition Easier to manage Windows Integrated Security More secure Authentication from the OS More flexible Combine users/groups Backwards compatible Smooth transition Consistent with AF security 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.

The PI AF Server

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

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

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

New with AF 2.1 – ‘Big ticket items’ High Availability Conceptually Very similar to HA for the PI Server Automatic Failover for clients SQL replication for the AF database Notifications support New Notifications template object 64 bit support Ready for Localization support

Other Enhancements Performance improvements Indexed attributes for faster searches AF Tables automatic refresh Enhanced Table Lookup Data References Interpolation/Extrapolation Summaries XML Import/Export command line tool Supports editing and deleting

From PI MDB to PI AF

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 Gradual upgrade process from MDB to AF The back-end first, and then the applications

Asset Centric PI: AF Element DB 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.

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.

MDB to AF delivered by the PI Server 3.5 PI Server version 3.5 delivers the MDB to AF subsystem Migration Synchronization Requirements: AF Server 2.1 must be installed PI Server Upgrade only from 3.4.380 MDB uses PI security AF uses Windows security 3.4.380 supports Windows security 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 When: PI Server 3.5 around end of the year.

Data Access

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 OPC OPC DA/HDA Server OPC UA Server SDKs (for partners/developers) PI SDK AF SDK

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 BusinessObjects, 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!

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

PI Data Access Roadmap PI Data Services (Baseline Services) (Q4 2009) Support both 32-bit and 64-bit providers PI Web Services Technical Preview (Current) OSIsoft vCampus online, hosted environment PI OLEDB 3.3 (Current) PI JDBC 1.0 (Q3 2009) JDBC-OLEDB Bridge for Windows and Linux PI System OLEDB 1.0 (Q4 2009) AF data access

PI Data Access Roadmap (continued) OPC DA/HDA Server 1.2.6 (Current) Achieved OPC Foundation Self-Certification Logo PI OPC UA Server Technical Preview (August) OSIsoft vCampus online, hosted environment PI SDK 1.3.8 (Current) Support both 32-bit and 64-bit providers AF SDK 2.1 (August) PI SDK 1.4.0 (Q4 2009) Client-side buffering for manually entered data, ACE calculations writing to PI, and custom SDK-based interfaces

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)

OSIsoft vCampus

OSIsoft vCampus Offering Includes access to all PI System programmatic interfaces: PI SDK PI AF/PI AN SDK PI OLEDB/ODBC OPC DA/HDA/UA Server Development license for programmatic interfaces Runtime client access licensing (CAL) Programming examples and documentation Community collaboration site Forums Blogs

OSIsoft vCampus Website

Update from August 2009

PI Interfaces

Emerson DeltaV Advanced Interface Configuration Tags Assets Emerson DeltaV & Syncade PI System Time-series data Batch and events data Batches Electronic Work Instructions 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. Time-series Batch

Update from August 2009

Update from August 2009

Update from August 2009

PI Roadmap – Major Release Summary Server: PI AF 2.1 – August 2009 (64-bit, HA) PI Notifications 1.1 – September 2009 (OCS, Templates) PI Server 3.4.380 – September 2009 (Security) PI Data Services – December 2009 (64-bit) PI Server 3.5 – 4Q 2009 (MDB to AF) Client: PI ProcessBook 3.2 – September 2009 (AF relative displays) PI WebParts 3.0 – 4Q 2009 (64-bit) PI AF 2.1 – August 2009 (sets the stage for others) PI Notifications 1.1 (OCS) – September 2009 PI Server 3.4.380 – 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