(informative) Analytics Models and Information Exchange 0 and Annex F described the models and messages used to obtain asset and measurement data that analytics need. This annex describes the analytics model and information that is provided by the analytics to other systems. Figure G.1 shows the model pertaining to analytics. There are four key concepts in the analytics model and the messages supported by this standard, namely: Analytics: The Analytic class describes the analytic kind, scoring methodology, – it’s and the Document instance that details the analytic. Scores computed by analytics: The AnalyticScore and its child classes model the score produced from the execution of an analytic. Health events identified by analytics: The AssetHealthEvent class provides the details of a health event identified by the execution of an analytic. Asset grouping: The AssetGroup class provides the means to group assets upon which analytic could be executed. This is useful for fleet analytic or feeder analytic. Figure G.2 shows an illustrative analytics information exchange. In this scenario, a Maintenance and Inspection (MAI) sub-function, which could be part of a work management system, is interested in analytic assessment of individual assets. The MAI queries the relevant Asset Decision Support (ADS) sub-function, which could be part of an analytic package, to first discover the available analytic capabilities using the Analytics message, and then obtain analytic assessment of specific assets using the AssetAnalytics message. Figure G.2 also depicts a second ADS sub-function, ADS1, which could be part of a planning application, interested in analytics of groups of assets for instance, fleet analytics. In this – case, ADS1 queries ADS to first discover the available group analytics, using the Analytics message, and then obtain the group assessments, using the AssetGroupAnalytics message. Finally, upon the detection of a significant asset health event, the analytic package may create an AssetHealthEvent, which is communicated using the AssetHealthEvent message to interested systems in Figure G.2, MAI receives this message, which may be used to take – preventive or corrective action. Figure G.1 Analytic related model. – Figure G.2 Illustrative analytics information exchange. –
(informative) Analytics Models and Information Exchange 0 and Annex F described the models and messages used to obtain asset and measurement data that analytics need. This annex describes the analytics model and information that is provided by the analytics to other systems. Figure G.1 shows the model pertaining to analytics. There are four key concepts in the analytics model and the messages supported by this standard, namely: Analytics: The Analytic class describes the analytic – it’s kind, scoring methodology, and the Document instance that details the analytic. Scores computed by analytics: The AnalyticScore and its child classes model the score produced from the execution of an analytic. Health events identified by analytics: The AssetHealthEvent class provides the details of a health event identified by the execution of an analytic. Asset grouping: The AssetGroup class provides the means to group assets upon which analytic could be executed. This is useful for fleet analytic or feeder analytic. Figure G.2 shows an illustrative analytics information exchange. In this scenario, a Maintenance and Inspection (MAI) sub-function, which could be part of a work management system, is interested in analytic assessment of individual assets. The MAI queries the relevant Asset Decision Support (ADS) sub-function, which could be part of an analytic package, to first discover the available analytic capabilities using the Analytics message, and then obtain analytic assessment of specific assets using the AssetAnalytics message. Figure G.2 also depicts a second ADS sub-function, ADS1, which could be part of a planning application, interested in analytics of groups of assets – for instance, fleet analytics. In this case, ADS1 queries ADS to first discover the available group analytics, using the Analytics message, and then obtain the group assessments, using the AssetGroupAnalytics message. Finally, upon the detection of a significant asset health event, the analytic package may create an AssetHealthEvent, which is communicated using the AssetHealthEvent message to interested systems – in Figure G.2, MAI receives this message, which may be used to take preventive or corrective action. Figure G.1 – Analytic related model. Figure G.2 – Illustrative analytics information exchange.
IEC-61968-4_Edition2_CDV.docx