AVEVA™ PI Server

Showing 1271

Notifications Subscriptions Notify Option defaults to "Start and End"

Many EFs are poor health in nature such that notifying the user when the event is ended is very important. Many users don't realize that this is an option. Either make start and end the default or present all choices more visibly to the user. This...

Guest about 2 years ago in AVEVA™ PI Server / Notifications 0 No status

4 VOTE

Ability to modify SOAP xml format

There are some cases when the sender wants to modify the format of the SOAP xml itself. Currently Notifications service constructs a XML request including all the variables provided by the wsdl.

Guest about 2 years ago in AVEVA™ PI Server / Notifications 0 No status

4 VOTE

Allow dots in JSON property names when using REST Delivery Endpoints

When configuring a Noification with a REST Delivery Endpoint, there is no way to escape a dot (".") so it doesn't gets interpreted as a path delimiter. There are cases when the dot must be part of the property name. One way to solve it would be to...

Guest about 2 years ago in AVEVA™ PI Server / Notifications 2 No status

4 VOTE

Allow multiple Notification Message Formats for the same Notification

For Notifications which send on Event Start and Event End, it would be useful to have the ability to have multiple Message Formats for the same Notification (one to send out at start, one to send out at end). Advantages: -Can include "End Time" ...

Guest about 2 years ago in AVEVA™ PI Server / Notifications 0 No status

4 VOTE

Filter expression '<tagname>'="string" syntax should allow wildcards

Performance Equations syntax for filtering in SMT and Datalink should allow wildcards for strings: For instance, ''="*substring*" interprets the * as a literal character rather than as a wildcard. To achieve the desired filter, it is currently po...

Guest about 2 years ago in AVEVA™ PI Server / System Management 0 Declined

4 VOTE

Clearly label or group together obsolete/deprecated/legacy features

PI System Management Tools is littered with legacy features. By grouping them together or clearly labeling them as "legacy" or similar, the user knows which features to use or migrate away from without having to look up each feature individually.

Kenneth Barber about 2 years ago in AVEVA™ PI Server / System Management 5 Declined

4 VOTE

Normalized view of the Database Security Table

Currently, the Security column in the Database Security Table uses the following notation for its values (example): piadmin: A(r,w) | piadmins: A(r,w) | PI Readers: A(r) | PIWorld: A(r) This crams multiple PI Identities and access types into a si...

Kenneth Barber about 2 years ago in AVEVA™ PI Server / System Management 1 Declined

4 VOTE

Collect more information about the host operating system environment. For example: is it running Windows Core

As a system administrator or as an upgrade implementation planner, I need to know the operating system environment that is hosting the software. mPI (Managed PI) collects information about the host OS version, whether physical or virtualized, and ...

Guest about 2 years ago in AVEVA™ PI Server / System Management 0 Declined

4 VOTE

Use full names and supported ranges in the Point Type dropdown menu in the Point Builder

Consider writing out each point type in full and putting the range of numbers that is supports beside the point type name, making sure the the names are aligned in their own "column" and that the ranges are aligned in their own "column". Examples...

Kenneth Barber about 2 years ago in AVEVA™ PI Server / System Management 0 Declined

4 VOTE

Allow PIWorld and piusers to be deleted

Nobody should be using the "PIWorld" PI Identity or the "piusers" PI Group. The most that we can do at the moment is disable them. It would be much better if we can just delete them and never look back.

Kenneth Barber about 2 years ago in AVEVA™ PI Server / System Management 1 No status

Please enter your email address

FILTER BY CATEGORY