AVEVA™ PI System™ Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status Completed
Product AVEVA™ PI Server
Categories Notifications
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Enable authentication headers for SOAP and REST Web Service Notifications

There's no way to configure headers for Notification Rules associated with a PI AF Services v2017 SP1 Elements with a SOAP or REST Web Service Endpoint.  Authenticated web services, such as our company's Maximo's meter data inbound service requires a MAXAUTH header with a base64-encrypted username:password string.  As a result, you can't use PI as a source of data for Maximo's condition-based maintenance triggers and automated asset meter reading updates, if Maximo uses authentication on its web services.  That's a fairly common scenario with a high rate of return on the PI-Maximo integration efforts for a lot of customers.
  • ADMIN RESPONSE
    Aug 20, 2022
    This is in PI Server 2017 R2, available now on https://techsupport.osisoft.com/
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    This feature is very much needed. We need to be able to specify the Message Header from PI Notifications when calling with POST a REST web service
  • Guest
    Reply
    |     Aug 20, 2022
    Note that in 2017 R2 we are planning on including basic authentication via the standard HTTP Authorization header. The specific ask here (a custom header for authentication that is understood only by Maximo) will have to wait for a future version.
  • Guest
    Reply
    |     Aug 20, 2022
    The request isn't specific to Maximo - enabling a standard HTTP authorization in the SOAP header will allow Maxmio's web service to accept the payload.
  • Guest
    Reply
    |     Aug 20, 2022
    The feature added in 2017 R2 was for authentication of the SOAP payload, not for managing headers within the payload. PI remains unusable as a secure source of data for Maximo without it.