Be able to use RTQP to access PI Points and Config strings (DA Directly)
Use case:
create a dashboard that lets me know the amount of bad data (tags) mapped to our AF.

(eg. “Bad Input”, “Calc Failed”, etc)

Our system has numerous tags and it is impossible to monitor them one by one.

The RTQP engine has allowed us to query massive amount of AF Attributes to get their current values easily.

Some AF attributes have been excluded in our system. For that case, we are not interested whether or not the values are bad.

Hence I would like to know if I can filter out any AF Attributes that are ‘excluded’ in my query.

The resulting query will give me current values of the attributes that are bad.

Without knowing the tag names, it is impossible to rectify those bad inputs. We would need to open up AF again and trace the AF path to find out the tag names.

It also limits our ability to deep dive on root cause using the same query. (eg. Multiple tags from the same interface are showing bad inputs – this is impossible without knowing the tag names).

When making use of the GetValue transposed function when creating a new Template specific Data Model, we can see that under the hood it makes us of the AF SDK call AFData.InterpolatedValue method to capture the data at a specified timestamp provided in the transposed function. This method does make use of any Retrieval Modes.

It would be good for this GetValue transposed function to make use under the hood of the AF SDK call AFData.RecordedValue method instead since this method offers the possibility of using Retrieval Modes like "AtOrBefore" which is really useful to capture the last archived value before the timestamp provided.

This would provide a more faithful aspect of the behavior of the process.

When you create a template-specific event view, event frames based on derived templates are also returned. However, attributes which are overridden in the derived template return empty. This means more complicated queries using UNION ALL must be used.

As a user, when I use a derived template with an overridden attribute, it is often because I need to change the way that attribute is calculated in a subset of cases. However, I still want to be able to create a view easily for all of this data.

For example, I have a "Batch" template with "Pounds Produced". However, for a specific case, the "Pounds Produced" calculation needs to be different. I still want to easily be able to create an event view for all my batches.

Currently, PI SQL Commander Lite is bundled with PI SQL Client, PI OLEDB Enterprise, and PI ODBC Driver.

It is a very useful tool for PI OLEDB Provider, which does not bundle it. To use it, another provider needs to be installed to obtain PI SQL Commander Lite indirectly.

The version of PI SQL Commander Lite that is bundled with each provider is the latest version of PI SQL Commander Lite at the time of the provider's release. This means that the latest versions of each provider could have different versions of PI SQL Commander Lite bundled with them.

Manageability of PI SQL Commander Lite would be easier if it were a standalone download.

It would be useful to be able to access a specific row from a PI SQL Client call. For example if I query muiltiple attributes indicating some KPI ordered from highest to lowest returning 1000 rows, I might want to show only the top 10. The TOP function is supported in SQL Client, but the Table Lookup DR in AF only allows you to find the first row.

It would be useful if either the row number, 1..n, was returned or the table lookup DR would allow you to pick a specific row. This would then allow you to show the top n results in a table in applications such as PI Vision.

The current version of PI DAS (RTQP Engine) does not support the definition of default values for table-valued function parameters. This is a rather bleak omission, in my view. For example, the following will fail to create the table-valued function:

CREATE FUNCTION [MOMS].[fact].[getInstrumentOperationalDataSummaries]
(
@StartTime DateTime,
@EndTime DateTime,
@TimeStep TimePeriod,
@TimeType String = 'MostRecentValue'
)
AS
SELECT i.*
,s.Value

FROM MOMS.dim.InstrumentsBase i

CROSS APPLY [MOMS].[fact].[Instrument Base Template_GetSummaries]
(
i.ElementID, --Element ID
@StartTime, --Start Time
@EndTime, --End Time
@TimeStep, --Time Step
@TimeType --Time Type
) s

It should not. It is most reasonable to wish to provide a default value for TimeType in the above example. And T-SQL supports it, just by the way.

Please add a "Canonical UOM Per UOM" or "UOM Per Canonical UOM" column (not necessarily with those exact names) to the UnitOfMeasure table. This column would contain the conversion factor needed to convert between the UOM and the canonical UOM, similar to the "Canonical" column in PI System Explorer when you are viewing a UOM class.

With this in place, a user can easily convert a value to any unit by first converting from the value's default UOM to the canonical UOM of the value's UOM class, and then convert from the canonical UOM to the desired UOM. This would take 2 joins or lookups against the UnitOfMeasure table.

Alternatively, or perhaps in addition to the above, add support for a CONVERT function that works like so:
CONVERT(number, fromUOM, toUOM)
This would be more similar to the CONVERT function in Excel than the Convert function in PI Asset Analytics.