2 of 2 people found this helpful
Your #1 is perfectly acceptable and something I've done in the past - actually for the assets where the PI Point is not applicable then I used a custom system digital state to mark the events in the "holding points".
Whether the PI Point exists or not, you can wrap BadVal() function in your analyses to prevent breaking them.
Also, for unwanted attributes on an Asset you can use the "Excluded" property on the Attribute so it doesn't show up in searches or most applications.
Thanks for your insight!
1 of 1 people found this helpful
A slightly different approach I have used is to create child templates for each of the fuel types. You could design each template to suit the data applicable to that fuel type, and apply conversions to ensure that energy usage is presented in consistent units for all fuels, with consistent attribute naming.
You could then select the applicable child element, depending on the fuel used in any plant, and reference the energy usage in the parent element.
I will try to implement this. Thanks for your insight!