As a power user or admin, I would like the ability to create child events (EFs) or sub events within AF Analytics SO THAT I can migrate EFGen configurations to something that can be applied to a template and not configured by tags and SO THAT my users can analyze finer time periods of events.

Most common trigger behaviors for a child event are:
* Pulse: values are 0/1 or ON/OFF
* Step: values change and upon each transition, current in-progress event is closed and a new one is created
* Step Continuous: An event is also captured in the OFF/0 state.
* A trigger expression.

The Name of the child event can come from:
* Active (trigger) tag value
* A Static name
* Another tag value at the time of creation (or delayed)

Currently PI ACE calculations are used to verify if the data from redundant sensors is trustworthy. The PI ACE module implements Covariance and Max-Covariance calculations. The customer would like to move from PI ACE to Asset Analytics and is facing the issue that Asset Analytics is corrently not offering any extensibility nor Covariance / Max-Covariance functions. The Attachment describes the desired functions based on the PI ACE code.
 
The function description is attached with "Correlation Analysis Use Case_public.pdf".
Things we clarified / detailed more are:
 
- PI Data Archive doesn't support Array data types and there's not much sense in doing that. Hence inputs for both functions would be 2 numerical data streams.
- Function definition assumes the event count for both inputs to be equal which can be problematic with PI Points because of Exception and Compression. Hence functionality was detailed to make the first input the master, retrieve archived data (inside time boundaries) for the master, and use timestamps to get timed (interpolated) data for the second input.
- Both inputs (tag1 and tag2) must have 100% good data for the specified period.
- In case of a failed calculation the function is supposed to return “Calc. Failed”.

Wondering if there's interest in basic linear regression calculations, e.g. slope, intercept, R2, to analyze data.
Sample use cases:

1. Calculate the rate of withdrawal from oil wells to stay within compliance limits
2. Calculate linear performance curve based on normalized production to normalized energy consumption to determine motors that are failing
3. Determine when a manufacturing process has reset based on when a slope flattens out
4. Help operators control plant by looking at slope.  Currently using an Excel spreadsheet that must be constantly refreshed.

The slope and intercept calculations in combination with PI Sever's support for predictive data would be cool.  Imagine being able to extrapolate historical data and identify whether you're on a fast track to success or failure.

The components that could go into the separate calculations of slope, intercept, r, and r^2 are similar to current calculations for standard deviation (StDev already exists in Asset Analytics).
In addition to StDev, Excel has the following functions--

* Slope(known Y's, known X's)
* Intercept(Y's, X's)
* RSQ(Y's, X's) – r^2
* Correl(Y's, X's) – correlation, r

Idea:
Add basic out-of-the-box calculations in Asset Analytics that mirrors Excel functions for linear regression with a syntax of (attribute, start time, end time, optional: % good).  Construct is similar to the current equation in Asset Analytics, StdDev.

* Slope(attribute, start time, end time, optional: % good)
* Intercept( )
* RSQ( )

More complex expressions would be better in specific packages, but those 3 would be strong building blocks.

The need and desire is there to be able to further customize event frame names via AF Analysis. I would like the ability to name my event from an Attribute value. In my case this would pull in the BatchID and give the event frame a name of 1001, 1002 and so on for new events.

We can do this in Event Frames Generator but it's not ideal when we only need to correct events for one element we end up touching all of them during a restart or backfill. Doing this via Analysis would be a great benefit to us and others.

Please see the link below for more information on this from other users.

https://pisquare.osisoft.com/thread/9064

Request : Being able to show Attribute values from other Elements other than the attributes on the Referenced Element for the Message in Notification 2016.

Description : From the old version, it was possible for a notification message to display a value not only the target element but also an attribute of other elements (by browsing down elements and selecting the attribute)

In the 2016 version, it does not allow for the user to choose attributes in other elements but only the attributes of the Referenced (or targeted) Element.

The screenshot (Attached file) shows a relative path of an attribute but this is when the user already had a notification rule on the previous version and migrated it. Newly created notification does not have this feature.