All ideas

This is a followup to discussions with Roger Palmen and Rick Davin about their excellent writeups on the topic of EF Duration attributes; see Event Frame duration - easy way in AF2.6 or higher & Duration attribute on an Event Frame - Part 1 , ...

I would like to have the option to disable the feature introduced in PI System Explorer 2018 SP2 to pop up the following message when an Enumeration set does not match the name of a digital set in the PI Data Archive: "An AFEnumerationSet matching...

Some metadata can be used in Analyses, which is helpful, but means constantly running an analysis on static data in order to use it at all in AF, which is inefficient, and we have been told to pull in data as a linked table into AF, which seems un...

For background, I primarily do work for pharmaceutical companies, where they say "you should have some level of anxiety when you are working in production environments". Often, I have to create a list of PI tags, but there may be errors in the spr...

It's about a known problem referenced here : https://softwaresupportsp.aveva.com/en-US/knowledge/details/000089196?lang=en_US Article Number 89196 :Referenced Event Frame Templates based on Derrived Element Templates are not always preserved throu...

The PI Square blogs on containers are enticing. I am looking forward to rapid deployment of OSIsoft products in containers.

Following KB01345 & 000036461 we have to manually add dependency where applicable. Please consider adding similar service dependency than we have via PI ICU for new interface (depend on pibufss): - AFService depend on relevant MSSQL$ service ...

Currently, PI SMT will only allow archives to be reprocessed according to it's original type. User would like to be able to choose whether to reprocess the archives from fixed to dynamic or vice versa.

Allow analyses to have both Scheduled and Event triggers, rather than having to choose just one of the triggering mechanisms

Use case: 1. An element has an attribute that looks up information on equipment configuration (ex: a pump rate) 2.  Due to an equipment change, the lookup table and the element were increased in version 3. A backfill needed to be performed o...