We have come across a number of occasions where we want to bring in the last good value of an attribute as an input to an analytics.  But there is no way to do this without additional attributes and analytics.  It would be convenient if a function existed that brought in the last good value of the attribute.  This is particularly useful when your data source is known to send NULL value frequent which translate into No Data or Bad Input.  One specific example:

We have a number of analytics that only run if one of our engine is on.  But the SCADA system we get run status from flakes out often and PI records it as No Data.  When SCADA flakes out, we assume Last Good Value.  Meaning if the engine was on before the outage, we consider it on until SCADA returns and tells us otherwise.  But if we bring the run status into an analytic, it uses the value No Data and breaks everything.  Instead of No Data, we should be able to wrap that attribute in a LGV function that will report On instead of No Data.

Read access to the PIPOINT table is required for most identities. Pointsecurity and Datasecurity currently use the settings on the PIPOINT table as the default. New points will generally give read access to most identities because of these defaults. This makes it difficult to configure an identity with read access to some points, but not all points (common when giving external contractors limited access).

Additionally, for best practice security, buffer identities need read access to Pointsecurity, but read/write access to Datasecurity. There is currently no way to configure this combination as a default.

Adding two new tables (ex. PTSECDEFAULT and DATASECDEFAULT) that are used for these defaults, instead of pulling directly from PIPOINT, will fix all of these issues.

If an Analysis is triggered on "Any Input", and the inputs have the same timestamp but come in after each other, the Analysis is only triggered at the first input.

For example: We have a simple Analysis which summarizes 2 tag.
The first tag comes in a 14:00, with timestamp 14:00. This triggers the calculation. The second tag comes in at 14:02 also with timestamp 14:00. Now the calculation in not triggered anymore.

We've also discussed this with Techsupport, and they came with the following statement: "With Event Triggered, the first value to come into the PI DA is used by the Analysis Service. Other events with the same timestamp are ignored."
We would expect that the Analysis would be triggered again if the timestamp is greater or equal to the last incoming event.

I know, that notifications are not sent for event frames older than 72 hours, but that 3 days is still too long.

Usually we just want to recalculate  Event Frames to have a proper statistic about the past in reports. The notification is used to alert users about current situation. It is very confusing when we are sending out 2 days old messages.

It is even more problematic, if we just recalculate EventFrames. Recalculation means, that the notifications for the same issues are sent out second times.

I understand that these backfilled notifications might be useful sometimes, but it would be very great to have an option to turn them off.

From a varying number of child elements (all sharing the same template), I want to find the most recent timestamp of a same template-based attribute, and output the value with timestamp to an attribute in the parent element.
In addition, constantly (event-triggered/periodic) comparing the timestamps of these child element attributes and always output the "newest" value to the parent element attribute.

Example:

From 3 child elements, all sharing the same template with attribute "ALARM", I want to have the most recent value comparing the 3 "ALARM"s, and have this timestamp and value in an attribute in the parent element.

Suggestions for enhancement:

- Function in Rollup Analysis which compares timestamps of template based attributes and outputs the most recent timestamp (with value!).

As a PI user, I want to be able to visualize and analyze the SQC violations that are generated by the SQC rules. 

The ability to save SQC outputs such as  Mean, median, mode, stdev, Cpk, max, min, 1-5 sigma zones, ucl, lcl in the following ways

1) the EF associated with the SQC rule - essentially the alarm event
2) an EF associated with a process event.  I want SQC summaries added as EF attributes bound by process event frames
3) AF clients.  I want to be able to add Cpk, sigma etc for any applicable AF attribute to a PI vision screen and have the results reflect the timerange on the screen.

The feature added in 2017 R2 was for authentication of the SOAP payload, not for managing headers within the payload.  PI remains unusable as a secure source of data for Maximo without it because you can't configure a MAXAUTH header.

There's no way to configure headers for Notification Rules associated with a PI AF Services v2017 SP1 Elements with a SOAP or REST Web Service Endpoint.  Authenticated web services, such as our company's Maximo's meter data inbound service requires a MAXAUTH header with a base64-encrypted username:password string.  As a result, you can't use PI as a source of data for Maximo's condition-based maintenance triggers and automated asset meter reading updates, if Maximo uses authentication on its web services.  That's a fairly common scenario with a high rate of return on the PI-Maximo integration efforts for a lot of customers.