Ideas

See the attached picture. The picture also reveals other parts of PI System Explorer that are not translated. The picture and the idea for this suggestion come from https://pisquare.osisoft.com/s/feed/0D58W00006XNrBuSAL.

Currently it's not possible to use attributes that are based on a PI Point Data Reference with RelativeTime or TimeRange settings as triggers for analyses with event-triggered scheduling. You get the "No valid triggering inputs found" error. The r...

When using the recorded values function in Analysis, Time weighted totals and averages assumes that the data is continuous and not discrete. This creates issues with data streams that are both discrete and require time weighting functions. Ideally...

Have a way to automatically have services restart, potentially tied to a health trigger value in a tag.

Have a way to detect if data is missing.

In the description of the tuning parameter Archive_AutoArchiveFileSize, "occurs" is misspelled as "occurrs". This misspelling is also followed by a semicolon instead of a period.

Go to PI System Management Tools. In the View menu, we see "Plug-Ins". If we click on Settings in the View menu, we see "plugins".

In PI System Management Tools → Operation → Tuning Parameters, add a "Unit" column and a "Takes Effect" column. Not only does this prevent having to click on the tuning parameter to know its unit, but it also shortens the tuning parameter's descr...

Currently, every PI System Management Tools plug-in has buttons at the top. To know what a button does, you must hover over it and read the tooltip. If the PI SMT is maximized, the buttons usually use up very little of the horizontal space availab...

In the PI Annotations Editor, which is accessible by clicking on "Annotations" after right-clicking on a value in the Archive Editor, if you make changes to the annotations and try to close the PI Annotations Editor without saving, the following m...