Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our 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.

Status No status
Product Edge Data Store
Categories General
Created by Guest
Created on Nov 6, 2025

DeviceStatus stream not exposed as streamReference in Health asset types

Description

EDS automatically publishes at least two Health assets:

  • StorageHealth

  • DataCollectorHealth

Both assets provide a DeviceStatus stream, but this stream is not declared as a streamReference in the asset type definition.

As a result:

  • The DeviceStatus stream cannot be mapped to the Asset Status

  • The built-in Asset Status feature cannot be used, even though the status data already exists


Functional Impact

Asset Status is a key feature to:

  • Monitor industrial connectivity health

  • Keep an historical view of device and adapter status

Although the status information is already produced (DeviceStatus stream), it cannot be leveraged without modifying AVEVA‑provided asset types.


Requested Improvement

  • Add DeviceStatus as a streamReference in Health asset types

  • Provide the default mapping to Asset Status

  • Apply this improvement consistently to all adapters exposing DeviceStatus or similar health streams


Rationale

Technically, users can manually modify asset types to reassign streams and map the status.
However, this forces customers to customize AVEVA asset types, which should be avoided as much as possible for maintainability and upgrade safety.

Since the DeviceStatus stream already exists, exposing it properly in the asset type would be a low-effort, high-value improvement.

  • Attach files