Chris Nelson – OSIsoft Senior Developer

Name: Chris Nelson – OSIsoft Senior Developer
Uploaded: 2017-08-22T04:07:27+00:00
Duration: PTM29S16
Channel: Douglas Walters
Description: Chris Nelson – OSIsoft Senior Developer

Chris Nelson – OSIsoft Senior Developer
RtReports Chris Nelson – OSIsoft Senior Developer

Agenda Overview Benefits and Differentiators Version 3.0 New Features
Product Demonstration Using Predefined actions and Style sheets to build a Case Report Future planned Enhancements Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Overview – Goals of RtReports
Improve employee efficiency Reports built and regenerated without programming Library of processing rules and formatting rules allow for rapid report generation Enhance knowledge management and collaboration Reports available on-demand, via the Web Reduce variability in reporting Information workers retrieve information from the same audited source Generate tamper-proof reports Using the Library of processing rules and formatting rules assures standardization of reports Improve manufacturing agility Accelerate product release through automatic comparison with specification data and generation of C of A Automate environmental reports Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Overview - What is RtReports?
RtReports is OSIsoft’s Web reporting product Allows our customers to easily build complex, repeatable reports for the RtPM Platform Enables our customers to easily manage the change of reports through configuration Provides secure internet based access to reports Supports the need to produce reports compliant with government regulations such as 21 CFR Part 11 and Title V permits Streamlines the review and approval of production and environmental reports Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Benefits and Differentiators
Report Template Versioning Flexible context meta-data Extensible data retrieval calls Library of processing rules and formatting rules allow for rapid report generation Compliance Edition Workflow You may ask yourself why use RtReports? I will go through the five main reasons that differentiate RtReports from other reporting products. There are mutlple other reasons based on your requirements, but these five reasons separate RtReports from other products with similar architectures (meaning web based reporting solutions). Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Differentiator - Report Template Versions
No other reporting solution provides the change management of the report template like RtReports! No other reporting solution provides a means to associate versions of a report template with a specific context for the life of that context! Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Differentiator - Report Template Versions
V1 V2 Day Day Day Day Day 5 Execute Inventory Report 5 New Tanks Add to Production Execute Inventory Report Inventory Report V1 -> V2 V1 V2 Inventory Report V2 Effective Date Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Differentiator – Flexible content meta-data
Flexible context meta-data No other reporting solution gives you the ability to configure a hierarchical context structure You can use RtReports to map and monitor your business process Which Batch processing steps should be included in the report Which Time ranges, Assets and attributes should be included in the report Which Cases, Assets, and attributes should be included in the report Once you have mapped your business process you can retrieve specific, actionable data based on the context of your business process Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Differentiator - Batch Context Mapping
Now you can configure heterogeneous data queries based on your business context Did the Oxygen level violate an upper limit during the Cell Culture Operation? Did the Inoculate Operation last at least 10 minutes in the 500 Liter Bioreactor? Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Differentiator - Time & Asset Context Mapping
WEEKLY EXCURSION SUMMARY REPORT Report Start Date 1-Jan-06 Report End Date 8-Jan-06 Factory FACTORY 1 MONDAY TUESDAY # of Excursions Per Day 22 31 # of Excursions Shift 1 4 7 # of Excursions Shift 2 8 6 # of Excursions Shift 3 10 18 WEDNESDAY THURSDAY 25 2 FRIDAY SATURDAY 42 11 21 A plant manager would like to compare the number of excursions for a day against the number of excursions for a shift for each of his 4 factories Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Business Process Time Contexts Calculations based on Daily Time Ranges Calculations based on Shift Time Ranges Asset Contexts Tanks in Factory 1 Tanks in Factory 2 Tanks in Factory 3 Tanks in Factory 4 In order to understand what the Plant Manager is looking for, you must break down the business process. The Business Process at a very high level breaks down like this slide Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Time Template creates a weekly time period Time Template sub divdes the weekly time range into daily time ranges Element Template maps to all Factory 1 Tanks Element Template maps to all Factory 2 Tanks Element Template maps to all Factory 3 Tanks Element Template maps to all Factory 4 Tanks Time Template sub divdes the weekly time range into eight hour time ranges corresponding to the 3 shift intervals Now you can configure heterogeneous data queries based on your business context Did any Heat Exchanger in Factory 1 violate an environmental limit? Did any Heat Exchanger violate a process efficiency limit for Shift A? Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

You execute a report with a specific context (Batch, Time Range, Case) This context is usually at a summary level You need to decompose it in order to extract the proper information You do this in RtReports by configuring time and context templates to decompose the summary context to match your business process You then configure actions to implement your data queries based on where you are in your business process You execute a report with a composite or summary context. For example, when you run a batch report, you usually execute the report associated with the PI Batch. But you need to report on the cycle time of the unit procedures, specific calculations based on phase start and end times. RtReports allows you to define this report by decomposing the main PI Batch object to mimic the batch process, which is your business process. Another example is a Weekly Production Report. A weekly production report usually has calculations based on Days, Hours, Shifts, etc. RtReports allows you to define a data structure that will decompose that high level time range into actionable context. Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Differentiator - Extensible data retrieval calls
Built in Result Definitions Trend Summary Calculations Summary Value, Summaries, Expression Summaries Recorded and Interpolated Values Exact Time Values Calculations (Execute a PI-PE Equation) PI Batch Properties and EVT String Pool Tags RtBaseLine Data Sets (External relational and web service data sources) Call a ACE Calculation through an RtBLS web service data set Analysis Framework data references Executed based on the Time and Asset context of your business process Another major differentiator of RtReports is that we present data retrieval to the user in PI Terminology and are able to supply all the functionality that you are used to with other OSIsoft Products, such as Datalink and ProcessBook. Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Average Summary Result Definition executed for the Day Time Range for the Temperature Alias for all Tanks in Factory 1 Maximum Summary Result Definition executed for the Day Time Range for the Pressure Alias for all Tanks in Factory 1 Minimum Summary Result Definition executed for the Day Time Range for the Level Alias for all Tanks in Factory 1 Average Summary Result Definition executed for the Day Time Range for the Glycol Supply Alias for all Tanks in Factory 2 Average Summary Result Definition executed for the Day Time Range for the Nitrogen Supply Alias for all Tanks in Factory 4 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Journal Action State Machine Build custom logic through IF…Then…Else statements for conditional data retrieval Executed based on the Time and Asset context of your business process STATE 1 IF Temperature > UpperLimit Then 2 Else 1 STATE 2 IF ExcursionDuration > DurationLimit Then 3 Else IF Temperature < UpperLimit Then 1 Else 2 3 STATE 3 You can now define a result definition associated with the time range framed by this excursion For example, Return the Maximum Temperature and Pressure during the excursion Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

The Maximum Temperature for all Factories is a Key Performance Indicator. This Action will determine if a Temperature sensor violated any limits Factory 2 Key Performance Indicator is the Glycol Supply Temperaturer. This Action will determine if the Glycol Temperature violated a threshold and display a Trend Factory 3 Key Performance Indicator is the Flow Rate on the Air Scrubber. This Action will determine if the Flow Rate violated a threshold and display a Trend Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Differentiator - Action and Style Sheet Libraries
Report standardization is promoted through A library of pre-defined actions (business rules) A library of style sheets (formatting rules) OR PI Data Report Template Report Business Rules Action 789 Action aaa Action 123 Action xyz Action abc + = AND/OR Formatting Rules RtReports provides a library of processing rules called PreDefined Actions. The Action Library permits importing and exporting these rules; which facilitates standardization of these business rules and maximizes their re-use. RtReports provides a library of formatting rules called Style sheets. Style sheets allow reports to be build out of smaller formatting components, which facilitates standardization of report formatting. Style sheets can be imported and exported for easy collaboration across the enterprise. Style Sheet xyz External Data Modular Report Building Is Achieved Through A Standard Library of Business and Formatting Rules Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

The Central Theme: SEA Simple Enterprise Aware Highly Available
Eliminate redundancies, simplify choices and focus on usability. Everywhere. Enterprise Aware Ready to keep customers in business. Meet enterprise needs and expand our presence. Highly Available Whenever, wherever, and however customers need it. We are available if – and only if – a user can use our system. By now – you have seen this slide many times. The SEA Change is a central theme that is permeating every day life at OSIsoft. RtReports 3.0 is a great example of making sure development is aimed at these objectives. 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 © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Version 3.0 New Features Supporting Enterprise Aware and High Availability File based Report Cache RtReports now takes advantage of disk space by building a file based report cache Report Execution Manager A new module was implemented to support running reports and components across several machines. Performance gains Numerous performance enhancements were implemented in the Report Generator and Report Execution Manager The following enhancements to RtReports addressed performance bottlenecks. After the release of Version 2.3, we took a hard look at the architecture and what would improve performance for RtReports running at the plant level or a regional level. The first thing we realized is that we need to increase the size of our cache. In Version 2.3, the cache was resident in memory. This seemed like a great idea until we saw the size of our customers reports. It became obvious that we needed to utilize the disk capacity on the RtReports Server. The next area we concentrate on was how to delegate components across several machines in order to scale. We separated the back end into logical components and allowed them to run on different machines. In order to make this all work, we created a new component that would control all the remote components and provide feedback and status to the user. This new component is the Report Execution Manager. Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Version 3.0 New Features Concentrated on Broader Applicability
Time Report Templates Build reports for time ranges and recurrence patterns Case Report Templates Build reports for Analysis Framework cases SIG directed functionality enhancements External Data Sources Include relational and web service data sets using RtBaseline Services RtReports Standard and Compliance Editions A major amount of development time was spent increasing the performance, scalability, and availability for Version 3.0; However, we also listened to you our customers. The following functionality enhancements were the highest priority of the RtReports Development team. With Version 3.0, RtReports can be your web enabled, real-time, production reporting system. Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

RtReports 2.x Architecture
Active Directory Domain RtPortal RtBaseline RtAnalytics Smart Client RtReports Editor Trust Thin Client RtReports Generator PI Server Module Database Batch Database RtReports Server IIS Generator Editor Internet Explorer RtReports Architecture RtReports is primarily a server based product that lives as a component of RtAnalytics in the RtPM Platform. There are Smart Client and Thin Client portions that live in RtPortal, but those are centered on configuration and consumption of reports. The RtReports server components do the analysis and rendering of the reports. RtReports Parts: RtReports Web Server PI-RTREPORTS-SRV RtReports Editor PI-RTREPORTS-EDIT RtReports Generator (Web viewer thin client) PI-RTREPORTS-GEN-C RtReports has two major components: RtReports Generator: .NET Web application that searches stored data within a PI Server aggregates that data according to specifications identifies deviations from critical process limits maintains comments and approval history generates pre-configured reports. RtReports Editor: .NET Windows application used to create and modify report specifications (called Report Templates) for selecting data, aggregating it, formatting it, and collecting electronic signatures for reviews PI Server Requirements Using RtReports requires a functioning PI Server version or greater, including an established Module Database and Batch Database. RtReports Web Server Hardware/Software Requirements Hardware Requirements The minimum hardware requirements for RtReports Server are as follows: Pentium III 1GHz PC 2 Gigabytes RAM 30 gigabytes hard drive Operating System Requirements One of the following operating systems is required: Microsoft Windows 2000 (Professional, Server, or Advanced Server) SP1 or higher Microsoft Windows 2003 Note: On a Windows 2000 Professional platform, Microsoft limits the number of concurrent users. Server Software Requirements In addition to the Windows operating environment, the following software is required for successful RtReports installation: Microsoft Internet Information Server (IIS) 5.0 or greater Microsoft Word XP or greater Microsoft Explorer 5.5 or greater Notes about RtReports: -Report templates are stored on one designated PI Server. -Other PI Servers can be accessed and RtReports Editors can build reports for them. -Reports cannot mix data from multiple PI Servers. -Report Generator can run reports against any accessible PI Server. Internet Explorer Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

RtReports 3.0 Architecture
Active Directory Domain RtBaseline RtAnalytics RtPortal Smart Client RtReports Editors Trusted Connections PI Server Module Database Analysis Framework RtBaseline Services* RtReports Server Windows Server 2003 Internet Explorer Emphasize RtReports is now based on RtBaseline Services and can consume data from both the Module Database and the Analysis Framework. Thin Client RtReports Generator Transactional, Web service, and other data Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

RtReports Futures RtReports Version 3.1 Multiple Batch/Case Reports
Report Properties storage in Annotations RtReports Web Parts Publish Web Services Enhancements needed to support High Availability Platform Release We are planning a release of RtReports with the following features to coincide with the High Availability release later in this year. It will include Multiple Batch/Case Reports, Moving the storage of Report Properties from PI Modules to PI Annotations, RtReports Web Parts, and Published Web Services. Any enhancements needed to support High Availability will be included in this release. Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved.

Platform Release Timeline
4/20/2017 Platform Release Timeline RtReports 3.2 After this conference, we will start an initiative to decompose RtReports into a core set of features, functions, and services to simplify the report creation process. Another release of RtReports will coincide with the Data Directory release. Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 29

Chris Nelson – OSIsoft Senior Developer

Similar presentations

Presentation on theme: "Chris Nelson – OSIsoft Senior Developer"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Chris Nelson – OSIsoft Senior Developer

Similar presentations

Presentation on theme: "Chris Nelson – OSIsoft Senior Developer"— Presentation transcript:

Similar presentations

About project

Feedback