How can we improve PI Interfaces?

Migrate the PI ICU settings away from the PI Module Database

PI ICU settings are currently the main reason why the PI Module Database continues to live on even the most up-to-date PI systems. Please consider migrating the PI ICU settings from the PI Module Database to the PI Asset Framework or a separate file.

This way, PI administrators have 1 less legacy PI feature to worry about eventually migrating and 1 less legacy PI feature that they need to keep visible in PI System Management Tools.

21 votes
Sign in Sign in with OSIsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Kenneth Barber shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in Sign in with OSIsoft
Signed in as (Sign out)
Submitting...
  • MAl commented  ·   ·  Flag as inappropriate

    Interesting idea the one of the AF, even if I have some doubt about how reliable could be the Windows authentication: PI interface node and PI server are normally segregated by firewalls and not in the same domain. In similar cases (i.e. when using a PI EMDVB interface to Event Frames) we happened to get some inexplicable unauthorized errors that later disappeared again inexplicably. Today (with PI MDB) we set easily a PI trust and just open port 5450/tcp.

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED