Trending Assets Properties

prerequisites before using asset properties to build a trend in grafana, ensure creating an asset are configured in factry historian configuring the factry historian datasource plugin for grafana docid\ q9t7hxoxsknylawporfdd is correctly set up in grafana default usage to trend asset properties, either create a new dashboard or use the explore functionality next, select the factry historian datasource plugin as the data source if it's not selected by default, then select the assets tab select an asset from the asset tree by clicking the assets field select one or more properties from the properties field this field will be polulated by all asset properties configured on the selected asset select an aggregation function and aggregation window the defaults are mean and $ interval the $ interval variable is available in grafana, and will adjust the aggregation window depending on the selected time range in the panel/dashboard optionally, select a fill type for aggegration windows where not data is present optionally adapt the grouping by statement by default, data will be grouped by status optionally filter on tags for more information, consult tags & labels docid\ zb70hnsdfnj3sj42myjxi information optionally filter on values (e g only return values >= 0) optionally limit the max amount of returned values asset properties vs measurements docid\ xqwlemdcnfff3 0h gmms are the raw time series records stored by factry historian they are tied directly to a sensor or signal (e g mixer01 tt101 for a temperature tag) docid\ cr6hbrdsl8fsuvlvm20if are a semantic layer on top of measurements they link measurements to specific equipment and provide human friendly context (e g mixer 1 → temperature ) when and why to use asset properties easier to navigate users can search by asset hierarchy instead of remembering tag codes cleaner queries “ mixer 1 temperature ” instead of “ plc1 dbt10 tt101 ” consistent naming asset properties are centrally managed in historian configuration using regular expressions consult query with regular expressions docid\ ofg2npmyrn4zkznsonpe7 using grafana variables to populate dropdown lists dropdown filters make dashboards more interactive operators can pick which assets or asset properties to display filter with asset supports multi select using query with regular expressions (view trends from several assets at once) create a grafana variable listing available assets use that variable in your factry datasource query to dynamically switch assets example grafana variable filter with asset property also supports multi select (compare multiple properties across one or more assets) create a grafana variable listing property names use that variable in your factry datasource query to toggle which properties are displayed combine asset and property filters using both filters together allows you to create very targeted dashboards operators can first select one or more assets (e g all mixers in a line) then, they can refine which properties to show (e g temperature and pressure ) this makes it possible to quickly compare the same property across multiple assets, or compare different properties within the same asset a combined filter setup is especially useful for cross asset comparisons e g trending temperature for all pumps in a plant multi property diagnostics e g showing vibration, temperature, and current on the same motor troubleshooting no data returned if a property does not return data, check whether it is mapped correctly to a measurement in historian error when using mean with boolean/string the factry datasource automatically falls back to last if you apply the mean aggregation function on boolean or string data to keep meaningful results, either split queries into multiple datasources on the panel (numeric in one query with mean, string/boolean in another with last) or explicitly set the aggregation to last for non numeric data