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.
Please add Manual data entry functionannality to PI Vision.
1. The Technical Request Checklist
Target Tags/Attributes: Provide a list of the PI Tags or AF Attributes where data will be entered.
Permissions (Security):
Confirm that your user group has Write Access to the specific PI Tags in the Data Archive.
Confirm you have Write Access to the AF Attributes.
Data Validation Rules: We need limits (e.g., "The value must be between 0 and 100").
Audit Requirements: (Standard PI Tags track the "Value" and "Timestamp," but an audit trail usually requires PI AF Audit Mapping).
2. Standard Use Cases for PI Vision MDE
A. Lab & Quality Results
Scenario: A lab technician tests a sample every x hours. The results (pH, density, purity) are not automated.
Goal: Instead of using an Excel sheet, the tech enters the value directly into a PI Vision dashboard so operators can see the quality data alongside real-time pressure and flow trends.
B. Operator Rounds & Manual Inspections
Scenario: An operator walks the floor and reads a local pressure gauge that isn't wired to the PLC.
Goal: Recording "Visual Inspections" or "Oil Levels" directly into PI to ensure the data is centralized for long-term reporting.
C. Integration with Event Frames
Scenario: A machine trips. The PI System knows when it stopped, but not why.
Goal: The operator selects a "Reason Code" (e.g., "Motor Overheat" or "No Feedstock") from a dropdown menu in PI Vision to categorize the event for later analysis or enter any manual data for that event
@AVEVA, Any update on this since Aug 2022?