NEXT TO TRACK DCD EVENTS AND RUN A REPORT WEEKLY/ MONTHLY/YEARLY
WE ARE TRACKING IN ADMS AND NEED A WAY TO SEND VIA EAMIL. scada point ids Bin 00014-00018 on reclosers.
Paul Unrast

Add an editable field to the table so that I can add targets for the data. I can put targets in text boxes next to the table, but they don't sort along with the table data.

Provide detailed display statistics so that displays can display content can be analyzed. For example, this information can be used to evaluate display quality.

Anywhere that you can show a tag name you should be able to show an alias instead. For instance, tables only allow you to show the tag name and not an alias.

As a PI Vision administrator, it would be useful to be able to track and audit changes (creation, edits, deletion) to PI Vision displays.

To be able to add business data coming from existing business systems into PI Vision displays.

I would like to have the possibility to add an extra column to tables that contains the settings of an attribute. In my case I want to see the PI-Tag-Names that are used for the attributes of an element.

We need the ability choose event-weighted averages in the Table similar to what is offered in DataLink.

Be able to print a display to be used as a 'report'. Include printing / saving as a .pdf. Consider an option to print the colors so it looks good on white paper.

Be able to print a trend and use it as a report. Include printing / saving to PDF. Consider changing colors on the trend to make it look nice when printed to a white paper.

If you align value items to left or right it does not work in longer period of time.
The items move depending on digit numer displayed (attachement VALUES):
1. Good to have option set decimal digits,
2. Good to have option TEXT SIZE,
3. Do not change VALUE ITEM size dynamicaly - let me do that by options.

For reporting reasons I need a table with more than one timestamp (see my dilettantish manipulated screenshot). The time range should be the time range of the disyplay (of course). The options should be time step (e.g. seconds, minutes, hours, days, months, years,...) and value retrieval method (automatic, at or before time, exact time,...).

We are utilizing future data and would like to utilize a Limit on a formula that uses future data. However my static limit does not extend into the future like I think it should. My goal is to see what future dates my temp might exceed my limit. I don’t want to create a future tag for this value. I would think that since it’s just a attribute value with no pinpoint or formula references that the data would just extend into the future. Can this be added as an enhancement to the next version of PI Vision?

It would be great if could use functions like "bom" (and similar, e.g. bod, bonm) in the PI-Vision timebar. New functions like "beginning of year", for example, would also be great

For pharmaceutical environment is would be an great option to indicate on displays (e.g. Coresight) whether or not an AF attribute’s value or a PI tag’s archive value has been manually edited. The way of indication dosn't really matter, could be a color, footnote, label, ...