4 Replies Latest reply on Feb 21, 2018 11:43 AM by Cheerion

    Templating multiple fuels


      We are currently setting up some AF templates which will allow us to calculate produced energy, operating hours and the fuel consumption power plant by power plant.
      From maintenance point of view, we would like to include as much calculations as possible in a template. But with this ideology in mind, we are running into an issue.


      We are burning 7 different types of fuel in our different power plants. Not all types of fuel are burned in each power plant and this is leading to a templating issue.

      For each fuel, we have a flow measurement connected to the PI server. We are connecting this flow measurement to our template to calculate the total fuel consumption.

      As said above, some fuels are not applicable for a particular power plant. This means there is no flow measurement for this fuel on this power plant. So no PI tag to link to the attribute (with PI point reference).
      This leads to an 'error message' in the attribute as the pi point (default value: '0') is not available on the server. An more over, I also have some issues with the analysis as it blocks the execution of all calculations because some attributes are erroneous.


      Before asking for your advise/feedback, I already thought about 2 solutions which I would like to share with you:

      1. Create 1 tag which is used if a fuel is not applicable on that particular power plant. We would write one value (an unreal one) to 01/01/2010. This would avoid both issue (attribute and analysis error).
      2. Create a template for produced energy and operating hours as this is equal for each power plant. Then start creating the derived templates for the different fuel combinations. This will be a hugh effort regarding maintenance. First to create them all and afterwards to adapt them all if we want to add or change something.


      I hope other people had this issue in the past and were able to tackle this issue. I would be appreciated a lot if you would share your experience with me.

        • Re: Templating multiple fuels
          Rhys Kirk

          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.

          2 of 2 people found this helpful
          • Re: Templating multiple fuels

            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.

            1 of 1 people found this helpful