AVEVA™ Products 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, select the product of your interest in the left column. Then 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 will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status Will not implement
Portfolio area Enterprise SCADA Server
Products Krunch and Data Manipulation Realtime Schema
Created by Guest
Created on Feb 17, 2022

RELATED IDEAS

Request for year to be added to the runtime structure

We've previously added an additional "year" field to the runtime structure to track hours per year for a 7.5 project. I'd like to request an enhancement to OASyS 2021 to add "year" to the runtime structure please. I see that there's a runtimeyear.json file that seems to have year but it only appears to be used by compressor. Or is there a way to get runtimeyear to work with other telemetered tables that I just couldn't find? (I searched through the docs but no mention of using it with other tables).

Copied from OGPM-3183

Expectation

add "year" to the runtime structure

Idea business value

Project enhancement from 7.5 version.
Idea Type Improvement
Idea priority 4 – Important to my company
User Persona Developer / Integrator
Work in
OASYS-478 Request for year to be added to the runtime structure
Work status
  • Attach files
  • Admin
    Jake Hawkes
    Reply
    |     Sep 28, 2023

    Will close due to no activity

  • Admin
    Jake Hawkes
    Reply
    |     Jun 2, 2023

    Bump

  • Admin
    Jake Hawkes
    Reply
    |     Feb 22, 2022

    Thanks Natalie - which tables are a must-have for you for this feature? Would it be calendar year or some other epoch?

    I notice you are requesting this to be added to ES2021, which unfortunately is not possible as it breaks the existing upgradability for that version. I will have it estimated for consideration in ES2024

    Do you have a plan-B?

  • Guest
    Reply
    |     Feb 22, 2022

    The original request was to add it to the baseline structure datatype and then to have it updated the same way as the other baseline fields within that structure get updated. Then it would be used/displayed/historized the same way as the other runtime fields (i.e. on a display, in a report, etc).

  • Admin
    Jake Hawkes
    Reply
    |     Feb 17, 2022

    Is the request to add this to the baseline structure datatype, so that it appears in every table?

    Is it also requested that it would be updated by the baseline krunch?

    Are there any other requirements on how this field would be used/displayed/historized?

    Would an alternative be to add it as a custom field outside of the structure, and then updated it with a Krunch Pipeline step?