AVEVA Product Feedback


Add a new idea Subscribe
Status Completed
Categories Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Support full dimensional analysis

As a user of Asset Analytics I would like the UOMs to be consistent and meaningful throughout the calculations that might involve various complex operations so that the written output values are meaningful and with the correct units.
  • ADMIN RESPONSE
    Aug 20, 2022
    There are at least 3 items in this idea. 1) ability to designate analysis output UOM - this is currently possible via the Convert() function, 2) ability to retain UOM in some situations - this is currently possible in that if all the inputs to an analysis all UOM from the same class, the analysis output would retain the UOM, 3) (title) Support full dimensional analysis - this is very broad and can involve many things - for example, converting from mass to volumetric flow automatically. These types of full dimensional analysis is not currently in our development plan.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    It should be possible to coerce or force the output units and disregard the inputs when required. This would be useful for empirical calculations where the output units might not be directly related to the inputs.
  • Guest
    Reply
    |     Aug 20, 2022
    In response to PatrickCrummie, even if the calculation is empirical, the constants that are used in the empirical calculation would still have a unit. It never makes sense to disregard the unit.
  • Guest
    Reply
    |     Aug 20, 2022
    I fully support this suggestion. It is very easy for people to make a mistake with the units and think that they have a meaningful output. This is especially the case when you use a function like TagTot, whose output unit is the input unit multiplied by the number of days being integrated, and it is easy to forget that TagTot assumes days instead of hours or seconds.
  • Guest
    Reply
    |     Aug 20, 2022
    Stephen, as I've mentioned before, the behaviour that you describe in 2) is incorrect for cases like TagTot. In your example in 3), I think that you have the wrong idea of dimensional analysis. It's less about being able to change dimensions easily and more about forbidding the user from describing dimensionally invalid calculations (e.g. adding a value in inches to a value in pounds).