As an RTReports administrator I would like to have the ability to incorporate comments and annotations that users attach to Event Frames .  For example, I would like generate a notification report for a unit over a period of time - PI notifications now stores acknowledgments, comments, approvals and I think severity in the AF database.  when generating my notification report I would like to incorporate this data into my report.

Provide additional Time Format setting for Duration, other than “xx days xx hours xx minutes xx seconds”

As an report designer, I would like to be able to choose the position of the legend on Trends.

Provide more power and flexibility to who approves reports. Currently, you can set the order of approvals.

It would be nice to be able to determine who or which approval track a report goes to or undertakes based on the results of the batch (IE which alarms were tripped during the batch)

As the report designer and/or integrator, I would like the ability to delete “released” reports used for demo/testing purposes. Specifically, when having to test how the official print looked, or e-signature capability, or to show the customer how those items worked. Without that utility, testing “released” functionality is a lot harder.

Provide the possability to send notifications based on the approval-cycle status of the report.
For example: In a "two-steps" approval cycle, send a notification to the final approval group when the first group approved the report.

Currently, non-recurring time based RtReports do not properly resolve the "Generated By" report info parameter. Instead of displaying the user, these printed reports display the text "Generated By".

On the other hand, batch reports and officially printed recurring time based reports resolve this parameter properly.

In order to provide a consistent behavior, non-recurring time based reports should be able to make use of this report feature.

When editing the report Criteria in RtReports, editing the text fields leaves the "OK" button grayed out. In the attached screenshot, the user has edited the "Recipe" criteria field and then clicked into the "Product" criteria field. The "OK" button remains grayed out. The same behavior also exists if you use the Tab key to change fields.

Currently, the user must hit the Enter key in order to have the changes picked up, which enables the "OK" button. This can be confusing, especially for new users that do not know of this requirement.

Provide the ability to control the font or position of the Official Print in the Editor and Generator.

Provide the ability to export report template list from RtReports Editor.

Provide a native 64-bit version of the RtReports Server.

Provide the ability to use domain groups to define RtReports group membership on the RtReports server

Provide the ability to show a Time Zone Information with date time on a Report.
(Feedback captured)

As a RtReports user, I would like the context level I select in the RtReports Generator to be the context used in the generated report. For example, if I click on a PIUnitBatch I would expect to see only data from within the start and end time of the PIUnitBatch. The current behavior is to crawl up to the top level of the batch structure and use that for the context of the generated report.

I would like to be able to access RtReports review data programmatically (e.g. via ODBC) so we can track which reports are ready to be reviewed by Manufacturing/QA.
It would also allow us to monitor the time taken to complete reviews and help drove improvements in lot release times.

Provide the ability to tune the RtReports Server to get more report generation throughput.

Make user's preference of View (Batch, Equipment etc.) in the RtReports Generator a user-specific setting

Allow an option to have objects to be displayed on a specific page in the Page Footer

It would be useful to have the possibility to include EFs in a Time Based Template.

For example:

• if downtime events are recorded as Event Frames, I would like to report on all the downtime EFs occurred in the last month (for example), including acknowledges and annotations.


• Using PI Connector for Siemens Simatic PCS7, conditions end-up in PI Event Frames accompanied with a related set of static and dynamic attributes. Having the possibility of including Conditions EFs in a time based report could be useful.

The current RtReports does not have any "next line" control character/object that customer is using Text object: </br> which is not recommended by OSIsoft developer