The OSIsoft Product Development Roadmap

The OSIsoft Product Development Roadmap
Bryan Owen, Cyber Security Manager Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Agenda Life before the Roadmap New Organization Roadmap Principles
The PRs in details Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Challenges OSIsoft is platform focused
Useful to many industries Avoid vertical, stovepipe applications But development teams were focused on individual products Focus on their own responsibilities Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Examples (improvements needed)
String tags Module Database Module-Relative ProcessBook displays several years after MDB release Annotations Sub-second data Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Product Development Roadmap
Describe development orientations over a 5 years period Objectives Communication What will we deliver? Predictability When will we deliver it? Value Make sure to deliver the "right" product Copyright © 2007 OSIsoft, Inc. All Rights Reserved

A Core Roadmap Principle
No platform feature is “released” until it is available to the user Copyright © 2007 OSIsoft, Inc. All Rights Reserved

This means… Many pieces must be in place: Database Visualization
Analysis Infrastructure “SDK” Copyright © 2007 OSIsoft, Inc. All Rights Reserved

OSIsoft: new directions
New Sources of Input: Technical Steering Committee (internal) Strategic Influence Groups (external) New Technologies New Delivery Mechanisms The Platform Releases Over the past few years we have begun to realize that to ensure the long-term growth of OSIsoft, we need to plan more strategically to align with our existing customers as well as evolving technology. The service oriented architecture of Microsoft’s upcoming Windows2007/Office2007 platform provides a different user experience. Much of this technology moves applications from the client to the server. OSIsoft is closely aligning our products to this methodology to align with coming technologies. We have focused our development efforts on delivering all of our services on a single release schedule. This will simplify our customers requirements for product installation and updates. Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Product Development Roadmap process
Copyright © 2007 OSIsoft, Inc. All Rights Reserved 9 9

The central theme: SEA Simple Enterprise Aware Available (highly)
Eliminate redundancies, simplify choices and focus on usability. Everywhere. Enterprise Aware Ready to keep customers in business. Meet enterprise needs and expand our presence. Available (highly) Whenever, wherever, and however customers need it. We are available if – and only if – a user can use our system. Simple – we want to make our software simpler to use, deploy, and manage. We also want to make OSIsoft easier to buy from and do business with. Enterprise aware – this means we handle the demands of an enterprise. This means security, localization, scalability and of course business processes (ours and integrating with yours). Available – basically, to serve the enterprise, we need to always have our platform available and ensure that our information gets to its destination (no matter who, or what that is) consistently, even in the face of high demand. Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Product Roadmap principles
Feature and Service Oriented Not product or server oriented Reduced feature duplication Unexposed features are not a feature Focus on the Enterprise Fit in place Leverage existing infrastructure Easy to manage Deployment Maintenance Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Initiatives Smart Connectors Managed PI Event Frames Localization
Business gateways Asset connectors Managed PI Event Frames Localization New UI Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PI System “Platform” Aspects and Services
Drivers Characteristics Aspects Services (Features) Initiatives Timelines Engineering Plan Copyright © 2007 OSIsoft, Inc. All Rights Reserved 13

Delivery on the Promise
Platform Releases Align product releases around a theme Ensure that “features reach the user” Testing will be done across products in the PR Commitment to a release schedule Platform Release 1 is released… Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Platform Release Themes
PR 1 = High Availability (HA) PR 2 = Data Directory and Notifications Delivery 1 – Notifications and High Availability Delivery 2 – Initial Data Directory Support PR 3 = Enterprise Data Access and Analysis And beyond … Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PI Server Recent History (2001-2006)
2001 PI 3.3, ModuleDB, BatchDB, COM Connector, ACE 1.0 PI 3.3 SR1/SR2, ACE 1.1/2.0 (.Net) 2004 PI /364 (Million Point), ACE 1.2/2.1 2005 PI (Online Backups, License Manager) 2006 ACE (VS2005), PI (Windows Patch) PI (Unix/64-bit), PI (HA/PR1) * projection Copyright © 2007 OSIsoft, Inc. All Rights Reserved

High Availability Definition
“Ability of a system to tolerate faults and continue to provide service according to its specifications” Dr. Kalinsky “Design Patterns for HA” For mission-critical applications, this means: Data availability No unplanned downtime Acceptable performance under load The PI System has High Availability features today Already a robust platform, but single points of failure Can you really afford any downtime? Copyright © 2007 OSIsoft, Inc. All Rights Reserved

HA Features before PR 1 Distributed Data Collection, Storage & Computation PI to PI Interface + PI Auto Point Sync Support for Online PI Server Backup Support for Microsoft Cluster Technology Integration with 3rd party Fault Tolerant/HA solutions Distributed Data Collection, Storage & Computation Nodes with Buffering & Caching Existing redundancy and recovery mechanisms Support for true Online Backup Microsoft VSS technology in PI Support for Microsoft Cluster Technology Integration with 3rd party Fault Tolerant/HA solutions Stratus Technologies, Marathon Technologies, HP, EMC, ... PI-to-PI Interface Performance greatly improved recently More powerful when paired with Auto Point Sync (PI-APS) Copyright © 2007 OSIsoft, Inc. All Rights Reserved

SIG requests for High Availability
What you asked us to provide: Ability for Clients (ProcessBook) to select among Replicated Servers Changes to Configuration Data (points, modules) regularly synchronized between Replicated Servers Near-Identical Time-series Data distributed from PI Interfaces (within compression specs) Copyright © 2007 OSIsoft, Inc. All Rights Reserved

OSIsoft interprets SIG requests
automatically What you’ve got: Ability for Clients (ProcessBook) to select among Replicated Servers Changes to Configuration Data (points, modules) regularly synchronized between Replicated Servers Near-Identical Time-series Data distributed from PI Interfaces (within compression specs) any PI SDK based + static load distribution or in real-time (+ no changes to your displays!) Copyright © 2007 OSIsoft, Inc. All Rights Reserved

The value of HA in PR 1 More uptime during server outages
Planned Unplanned Automatic failover for data consumers Automatically publish changes from a primary to secondary servers Multiple configurations possible Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PI Replication Architecture
PI Server Collection of identical PI Servers exposed as one (Collective) One Primary Server accepts configuration changes (e.g. points, modules) and produces a change log Secondary Servers automatically synchronize with the Primary change log Interface Nodes Identical time-series data distributed to all PI Servers by new buffering services Client Access Layer Transparent PI SDK connection management Existing and new Clients benefit from HA Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PI SDK in HA Environment
Three connection modes: Need Primary Prefer Primary Don’t Care OSIsoft clients applications in PR1 will declare mode of connection Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PI API in HA Environment
PI API is not aware of the Collective Includes PI Interfaces PI API and Interfaces are being enhanced to support disconnected startup Copyright © 2007 OSIsoft, Inc. All Rights Reserved

High Availability PI: Architecture
Clients: ProcessBook, DataLink, BatchView, RtWebParts, Custom Application… System Management Tools AppServers: AF, RtBLS, RtReports, ACE PI SDK Discovery, Failover, Failback, Load Distribution Services API Buffering PI Collective Secondary PI Server Primary PI Server Secondary PI Server(s) Configuration Changes Configuration Changes API Buffering Services PI Interfaces API Buffering Services PI Interfaces Failover Mechanisms Copyright © 2007 OSIsoft, Inc. All Rights Reserved

ProcessBook – What Users Will See at Failover
Copyright © 2007 OSIsoft, Inc. All Rights Reserved

ProcessBook – After Recovery

ProcessBook – User Can Click “Revert” Button

PI Replication Benefits
Seamless connection and failover to replicated servers from any PI SDK client No change to your displays, spreadsheets, and portal pages System scalability, load distribution Support for systems of all sizes No specialized hardware requirement Geographic availability, e.g. disaster recovery Administration comparable to a single PI Server Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PI Replication Future … Data Mining, Business Intelligence Services
Aggregated, Federated PI Server Enterprise Data Center PI Server Node … Data Mining, Business Intelligence Services PI Clients Client Access Layer PI Caching Server Regional Center 2 Regional Center 1 Aggregated PI Server PI Interfaces Site A Secondary PI Server Primary PI Interfaces Site B Secondary PI Server Primary Archive Mirroring Primary PI Server Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PR 1 = High Availability PR 2 = Data Directory, Notifications, HA Delivery 1 – UC 2007 Delivery 2 – Q1 2008 PR 3 = Enterprise Data Access and Analysis Copyright © 2007 OSIsoft, Inc. All Rights Reserved

The Value of Data Management in PR 2
Delivery 1 Notifications (supported by AF 2.0) Enhancement to security model More features added to High Availability User manual for Data Quality management Support for Microsoft Office SharePoint Server (MOSS) and Office 2007 Copyright © 2007 OSIsoft, Inc. All Rights Reserved

The Value of Data Management in PR 2
Delivery 2 Data Directory exposed (AF 2.x) Structured Data, Concepts and Applications Asset Centric User Interaction Displays, Reports Further support for Notifications Delivery Channels, Visualization Support for future data Integration for our NOC (use case) Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PR2: AF 2.0 & Notifications AF 2.0 Notifications Evolution of AF 1.x
Enterprise asset model “Data directory” PI Data Other data Notifications First rollout of the PIANO project Begin video at 13:57 fade into full screen Video Add PIP with slide in BR at 14:05 Copyright © 2007 OSIsoft, Inc. All Rights Reserved

“Foundation” AF 2.0 is… A flexible enterprise asset model
Relationships between the assets: Hierarchical Flow network Not just one type of relationships Access to: Relational and web service data PI data Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PR2 names… Why three names for this meta data layer? Data Directory
The concept (asset centric, heterogeneous data) Foundation Code name for development AF 2.0 The actual product to support the concept Copyright © 2007 OSIsoft, Inc. All Rights Reserved

The Data Directory in PR 2 Delivery 1 & 2
Asset Model supported by AF 2.0 PI Archive Time-Series Information Structural Information Honeywell Interface ABB Interface Delta-V Interface Rockwell Interface How many of you use the MDB to model your plant or process? Foundation assets are analogous to models. With version 2.0 of the AF/Foundation, you will have even more powerful modeling. … … SCM RDBMS MES Honeywell ABB Delta-V Rockwell Structural Data Sources Time Series Data Sources Copyright © 2007 OSIsoft, Inc. All Rights Reserved 37

Functional Breakdown of Foundation
Process Objects These are the “data” equivalent of the ProcessBook symbol library Reactors Crystallizers Valves Mixers etc. You create these as “templates” and then can use them in: Displays Calculations Copyright © 2007 OSIsoft, Inc. All Rights Reserved 38

AF Templates Create asset templates Attach Reuse Notifications
Calculations Visualization Parameters Other Database Targets Reuse Update with chucks example Copyright © 2007 OSIsoft, Inc. All Rights Reserved 39

Process objects. Other features:
Objects are created from templates Templates can inherit from templates Valves 2-State Valve 3-State Valve Attributes can be hierarchical Temperature Hi Limit Lo Limit Attributes can create PI-tags automatically Objects track history Useful where process connectivity changes Useful for doing analysis on old data Copyright © 2007 OSIsoft, Inc. All Rights Reserved 40

AF Data References Map Element Attributes to external data sources
Reading an Attribute Value accesses other Data References as needed Element Attributes are part of an asset template and apply to each instance of an asset Request for Asset Efficiency Element Model Efficiency Formula Data Reference =Production/Plan Production PI Point Plan select value from prod_plan where… PI Reactor 1 RDB Reactor1.Efficiency Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Functional Breakdown of AF
Models and Hierarchies Process objects are often related to one another T 101 Reactor 101 For example Reactor 101 Has a Temperature Sensor T101 attached Transfers material to Centrifuge 101 Centrifuge 101 Copyright © 2007 OSIsoft, Inc. All Rights Reserved 42

Creating Assets Distillation Cracker Boiler Crystallization

Build Relationships - Models
Distillation Plant 1 Hierarchy Cracker Boiler Role-based Connectivity Models Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Analyses – in PR3 … Collection based analysis Connectivity based
Uptime Alarming Equipment based analysis h = 65% h = 90% h = 74% h = 94% Mass Balance Composition tracking Efficiency KPI Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Value of Foundation Speed the development of displays and applications
Why Applications? Every year, customers present their valuable applications built on PI We want to provide tools that make this easier for them Why Displays? This is how you use our technology to derive value We want to provide tools accessible for all levels of users No longer need to define multiple modules for a class of equipment – use a template No longer need to lookup tags or create data sets just in PB – element attributes let you set that up on the server Copyright © 2007 OSIsoft, Inc. All Rights Reserved 46

What do we mean by applications?
Alarm Management Analyzer Performance Automated Generation Control Automated Reports Balanced Scorecards Baseline Best Practices Batch Quality Monitor Certificate Of Analysis Compliance Documentation Condition Based Maintenance (CBM) Continuous Emissions Monitor (CEM) Control Loop Monitor Corporate Data Warehouse Customer Load Management Data Reconciliation Down-hole Systems In O&G Production Downtime Monitoring E-Commerce Energy Management System Environmental Compliance Monitor General Ops Docn And Equipment Specs Hazardous Waste Tracking Hierarchical Process Data Views Hydrogen Manufacturing And Distribution Incident Investigations Inventory Management IT / Systems Monitoring Key Performance Indicators (Kpi) Lab Quality Data Integration LNG Terminal Operating Assistance LNG Terminal Operations Reports Maintenance History Or Status Maintenance Lockout Procedures Manual Data Recording Manufacturing Intelligence Data Material Balance Material Usage Tracking Multi-Plant Equipment Performance Monitor O&G Production Remote Monitoring O&G Production Well Testing Operating Envelope Data Operations Data Warehouse Operations Desktop Operator Handover Operator Training Paper Machine Felt Monitoring Paper Machine Grade Management Paper Machine Lost Opportunity Module Paper Machine Performance Monitor Pipeline Equipment Remote Monitor Pipeline Leak Detection Support Pipeline Operations Planning Pipeline Pigging Schedule For Paraffin Removal Pipeline Solar Turbine Efficiency Remote Monitor Plant Performance Overviews Power Delivery Capability For Gas Turbines Power Generation Fleet Outage Management Power Generation Supplier Scheduling Power Turbine Trip Monitor Process Monitoring Process Performance Analysis Product Compliance Reporting Product Development Trials Product Pricing Product Separation In Multi-Product Pipelines Production Data Integration To ERP Production Plan Versus Target Data Production Plan Versus Actual Data Pulp And Paper Mill Steam Energy Monitor Pulp Mill Tracking Quality Monitoring/Analysis Reliability Centered Maintenance Support Reservoir Control And Production Operations Root-Cause Analysis Shared Inventory Management Service Shift Production Monitor Six Sigma SPC/SQC Production Quality Control Steam Turbine Performance Analysis Substation Load Monitoring Substation Transformer Asset Management Supply Chain Management T&D Network System Load Forecasts T&D Network System Load Planning T&D Substation Equipment Monitoring Tanker Fleet Current/Past Locations Total Effective Equipment Productivity Transmission Line Capacity Planning Transmission Network Diagrams Transmission Network Frequency Monitor Troubleshooting Equipment Startups Utilities Management Virtual On-Line Analyzer In Refining Waste Treatment Monitor Weather Data Import Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PIANO – PR2 Part of and built on Foundation Service spanning products
Delivery 1 Notifications with basic Analyses and equations Escalations Delivery 2 More visualization and delivery channels Continue with PIP slide in BR Fade to black at 14:53, end of the video clip. Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Example – Email Notification

Example – Acknowledgements

Notification – Summary
Triggering events from both PI and non-PI data Delivering events to any end point Historizing all the actions Reusable Components Notification View Notification Configurator Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PR 1 = High Availability (HA) PR 2 = Data Directory and Notifications Delivery 1 – Notifications and High Availability Delivery 2 – Initial Data Directory Support PR 3 = Enterprise Data Access and Analysis Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PR3: Enterprise Release
Foundation driven products Data Directory HA Smart Connectors BaseLineServices 3 Data Access OPC UA PIANO Analysis Rules Archive sets Event Frames Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Shifting Platform Usage
4/19/2017 Shifting Platform Usage Time Series Time Series Centric Data Access Connectivity Context Analytics Data Access Operations Centric Time Series Our customer base and market has traditionally been an extremely time-series focused community. This will always be our core differentiator from other platforms. However, as business has become more aware of the criticality of manufacturing to their business, our data has become more critical. To help adjust to the needs of our market and to help differentiate ourselves from the competition, the Product Development Roadmap has called for a increasing focus on the metadata that surrounds the time series data that we always record. The PDR defines new services in the platform that extend the utility of the data to audiences beyond the plant floor. The Data Directory and Data Access services take on more prominence as a wider audience needs to find and access the data that we will be / are housing. Context (Data Directory) Connectivity Analytics Copyright © 2007 OSIsoft, Inc. All Rights Reserved 60 60

Enterprise Goals Allow users to browse or search objects across their enterprise model. For users that always work within a specified area, search and browse objects that are associated with the specified area, and not expose the entire enterprise model. Because of scalability and availability concerns, there must be a way to support multiple physical servers that store the logical objects. Provide browsing and searching user interface components that enable users of our client applications to find the logical object (and thus the desired data). Provide the ability to easily “join” an existing Foundation server into an enterprise model. Provide the ability in the enterprise model to browse and search PI Servers and PI tags. The AF-SDK should be able to connect to multiple enterprise models systems. Some logical objects will need to be isolated to an area, so that a change to the logical object will affect, at most, the users that view that area. Provide a way to determine the dependencies within the enterprise model. Copyright © 2007 OSIsoft, Inc. All Rights Reserved

Enterprise Benefits Data Directory User Benefits (TSC)
Unified search and use of datasets enterprise wide Fast, responsive queries Shared Data Directory between other trusted domains Data Directory ease of configuration and maintenance Reusable data definitions Private and public workspaces for users Pass context between applications Copyright © 2007 OSIsoft, Inc. All Rights Reserved

PIANO Goals After PR2: After PR3:
No more new custom notification logic in products No more new scheduling logic in products After PR3: No more new custom analysis code in products Copyright © 2007 OSIsoft, Inc. All Rights Reserved

What is an Event Frame? An Event Frame is a time series data type that may be defined by two times instead of one and is optionally accompanied by supporting data Batches Discrete Manufacturing Transfers Alarm and Event Interfaces Events/Incidents/Excursions/Accidents – PIANO Analysis Demand/Generation forecast analysis for power Equipment start up and shutdowns Copyright © 2007 OSIsoft, Inc. All Rights Reserved 64

Event Frame Initiative Scope
Customers monitor their processes for anomalies and then conduct analyses to find root causes Most, if not all analyses revolve around a named event with start time and end time Some of these events will never need to be stored – but the analysis techniques are the same Copyright © 2007 OSIsoft, Inc. All Rights Reserved 65

PR1 The Servers 4/19/20174/19/2017 6767 Analytics The Visuals The
Data Access RtBaseline Services for Thin Clients OLEDB ODBC OPC / HDA Module Database Analysis Framework Failover / Management Services PI Archive MCN HealthMonitor & System Management Tools Data Storage, Management Services, Audit Trail, Batch Custom Programming RLINK This is the detailed view of The Server at Platform Release 1 (the High Availability release). It goes into far more detail than is usually necessary to describe what the product grouping has within it. But since we're all really technology savvy, we should talk about it a little. Notice that the PI Archive is there. But also notice that the analytical components of “PI” are not here. They are in The Analytics (remember, it’s a logical grouping). But, that's neither a problem or a mistake. The PIANO development initiative (PIANO is NOT a product or product name) that is ongoing is really going to change and enhance the way calculations are done within the whole platform (i.e. not just on one PI Archive). So since the results of the PIANO development initiative are going to fundamentally change the way we can do calculations, we should focus on PI's core abilities: time series data collection, distribution, and management. Also, the failover and management services are represented in this diagram. They are functions that are not necessarily separate subsystems of The Server, but they are logical functions that show up in order to support the Enterprise Agreement customers and for our users to do Failover in the High Availability PI System. The box next to the PI Archive represents a “Context Database” where non-time series data is stored. This is a vague representation and "mashup" of Module Database and Analysis Framework's capabilities. These product capabilities are being rationalized in the Foundation development initiative (again, like PIANO, the Foundation initiative is NOT a product name, it will result in new functionality and potentially some new products). The functions this will serve are contextual representations of data and relationships between entities in our databases and a way to find the data you're looking for without doing a tag search. This is not directly bolted to PI like the Module Database was. It is more autonomous like Analysis Framework is. As might be imagined, the Real-time Interfaces are all of our interfaces and COM Connectors. We’re making the distinction between “real-time” and “non-real-time” here because in Platform Release 2 we’re going to create some “Asset Synchronizers” that treat structural and asset data in a similar way to how we connect and archive streaming data. The Custom Programming box represents user or integrator created programs that will update the Module Database or Analysis Framework automatically from other “asset systems” that might have a useful equipment structure for PI users. There are only a few of these that we know of, but they will get replaced in some instances (and on the next slide) by a type of technology called “Asset Synchronizers”. See Platform Release 2. RLINK and MCN HealthMonitor are both ways of collecting and manipulating special kinds of data that can be used to enrich the data collected in PI. Customers find great value out of these products when used in conjunction with PI. The product development roadmap will make the core functionalities of both products more tightly integrated with all the other components in The Server (i.e. more like a platform). They work together today, but our job is to make it easier for our customers to realize the benefits of deploying this type of technology. The Data Access layer in The Server are all the various ways that we get data out of the platform. Look for this to be enhanced as the platform evolves according to the roadmap. This is one of the single most important areas in the platform. Structure / Asset Data Real-time Interfaces ERP / Maintenance RLINK SERVERS & GATEWAYS SAP / JD EDWARDS / PEOPLESOFT MAXIMO / INDUS / MIMOSA 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 67 6767 67

PR2 The Servers 4/19/20174/19/2017 6868 Smart Connectors Analytics The
Visuals The Data Access RtBaseline Services for Thin Clients OLEDB ODBC OPC / HDA Data Directory Failover / Management Services PI Archive Data Storage, Audit Trail, Batch (Module Database) PI AF 2.0 MCN HealthMonitor & System Management Tools Smart Connectors Asset Connectors Business Gateways 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. Structure / Asset Data Real-time Interfaces ERP / Maintenance RLINK SERVERS & GATEWAYS SAP / JD EDWARDS / PEOPLESOFT MAXIMO / INDUS / MIMOSA 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 68 68 6868

PR3 The Servers 4/19/20174/19/2017 6969 Smart Connectors Analytics The
Visuals The Data Access Web Services OLEDB ODBC OPC / HDA Data Directory Event Frames & Batch Directory Services Failover / Management Services Audit PI Archive PI AF 2.0 MCN HealthMonitor & System Management Tools Datastorage Smart Connectors Asset Connectors Business Gateways At Platform Release 3, The Server starts to become further distributed. This is an estimated view of what may happen. Exact development plans haven’t been solidified yet, however some highlights include the following: More Asset Connectors added to the Smart Connector family Further automated configuration and management of Interfaces, Asset Connectors, and Business Gateways Release of some Business Gateways (targets not established yet, but many candidates exist) Interfaces will gain more distributed calculation and “compression testing” capabilities which will help the server scale by distributing the load across several boxes Further Failover and High Availability support will be introduced. This will help create aggregated PI Systems that can pass subsets of information between collective members instead of all the data in each archive. This will further eliminate the need for PI to PI interfaces except for special cases. Also, Failover support will be more platform-wide allowing elements in The Analytics and the Data Directory grouping to behave in a more highly available fashion. In the Data Access family of functionality, more comprehensive standards-based access will be available. This includes Web services to the entire platform. Also, a single OLEDB presence for all the information in The Server will be available (instead of several OLEDB providers). The Data Directory will also gain generalized Event Frame support to help users analyze repetitive events in all our clients in a more intuitive fashion than today’s Batch Database and Batch Subsystem. Directory Services will also be enhanced to help create a more federated PI System. This means that we’re moving further away from a single-server-centric model. The Directory Services help a user ask for resources or information without knowing the exact location of the information they’re requesting. Today, users must know a single server name or a collective name. Directory Services will allow a user to come into contact with more data without knowing the specifics of their server topology. This will help The PI System scale to meet the needs of a distributed enterprise. Structure / Asset Data Real-time Interfaces ERP / Maintenance RLINK SERVERS & GATEWAYS SAP / JD EDWARDS / PEOPLESOFT MAXIMO / INDUS / MIMOSA 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 69 6969 69

PR1 The Analytics Server The Visuals The
4/19/2017 Analytics The Server The Visuals The Windows Server 2003 Visual Studio.NET Advanced Computing Engine (ACE) RtAlerts RtReports Compliance & Standard Sigmafine Enterprise Services Facility Monitor 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 (Performance Equations, Totalizers, Alarm, RTSQC) PR1 Copyright © 2007 OSIsoft, Inc. All Rights Reserved 70 70

PR2 The Analytics Server The Visuals The
4/19/2017 Analytics The Server The Visuals The Windows Server 2003 Visual Studio.NET Advanced Computing Engine (ACE) PI Notifications (based on PIANO work) Scheduler RtReports Compliance & Standard Sigmafine Enterprise Services Facility Monitor At Platform Release 2, The Analytics will have a few major updates delivered from the PIANO initiative. One of them is a major rewrite of RtAlerts on top of a new calculation engine. It has many new features and fully utilizes the Foundation components within The Server in Platform Release 2. Also, the first cut of the new unified PI Analytics will be introduced. This is a new engine that will replace many of the PI subsystems that handle Performance Equations, Alarm, and RTSQC functions. This engine will be built on top of the Foundation work in The Server in Platform Release 2. That means that you can trigger notifications, analyses and more with PI tags or element attributes within the PI AF 2.0. Enterprise Services (mainly Facilities Monitor) will start making an appearance in The Analytics in PR 2. The Enterprise Services are designed to expose valuable information from The Server, with some processing from elements within The Analytics, and deliver the information to an ERP system. Facility Monitor in particular is targeted to SAP and xMII. However, the delivery mechanism is via Web services (this should be part of the Data Access in The Server). The work, however, is done in The Analytics which draws information from The Server – both the PI Archive and PI AF Ideally, more and more of these services could be introduced. They are essentially calculations based on structures and raw data that are delivered as Web services. Facility Monitor covers a few specific use cases that will help different customers understand how their operations are managing their power consumption. Because of the plug-in nature of The Analytics, more Enterprise Services should be able to be introduced incrementally. The Scheduler that is being introduced in The Analytics is centralized and available to schedule any work in The Analytics. Work will need to be done in order to ensure that existing members of The Analytics can use the new Scheduler, however having a single scheduling engine should enhance routine operations across The PI System (beyond just analysis). Because of the compatibility work in PR 2, existing AF 1.x and Module Database applications (like Sigmafine and BatchView) will continue to work at the release of The Server. The user may have to install a new SDK on any clients that access legacy functions, but otherwise should not have to recompile or edit their applications and displays. PI Analytics (new PE, Alarm, and RTSQC engine based on PIANO work) PR2 Copyright © 2007 OSIsoft, Inc. All Rights Reserved 71 71

PR3 The Analytics PI Analytics Server The Visuals The
4/19/2017 Analytics The Server The Visuals The Windows Server 2003 Visual Studio.NET PI Analytics Configurable Analytics (PE, Alarm, Totalizer, and RTSQC engine) Advanced Analytics (Using Visual Studio.NET) PI Notifications (based on PIANO work) RtReports Compliance & Standard Scheduler Sigmafine Enterprise Services Facility Monitor and more… At Platform Release 3, work from PIANO initiative will be introduced to enable users to transition away from both the Analysis Framework Analysis Rules and the Advanced Computing Engine analyses and into the new PI Analytics engine in The Analytics. This new engine will work off of the PI AF 2.0 that was introduced at PR 2 of The Server. It has the sets of capabilities that users expect from ACE and AF, but has been re-engineered so that The PI System can achieve its scalability goals. It will host both the Configurable Analytics that users normally create using PE syntax as well as the more Advanced Analytics that customers create in Visual Studio.NET. PI Analytics will also be able to run Totalizers in the PIANO features released with Platform Release 3 of The Analytics. Also, near PR 3, work will be done on RtReports, Sigmafine, and other applications within The PI System in order to ensure it takes advantage of new features that were introduced in The Server. They may not be part of the Platform Release, but introduced as incremental features. PR3 Copyright © 2007 OSIsoft, Inc. All Rights Reserved 72 72

What can you do? Stay Informed Give us your feedback
Attend the User Conference Read the Technical Support newsletter Give us your feedback SIG Call or write us Copyright © 2007 OSIsoft, Inc. All Rights Reserved

The OSIsoft Product Development Roadmap

Similar presentations

Presentation on theme: "The OSIsoft Product Development Roadmap"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

The OSIsoft Product Development Roadmap

Similar presentations

Presentation on theme: "The OSIsoft Product Development Roadmap"— Presentation transcript:

Similar presentations

About project

Feedback