Figure 51 – AssetPSRDetails message: EnergyConsumer element. Figure 52 – AssetPSRDetails message: EnergySource element. Figure 53 – AssetPSRDetails message: ExternalNetworkInjection element. Figure 54 – AssetPSRDetails message: FrequencyConverter element. Figure 55 – AssetPSRDetails message: GroundingImpedance element. Figure 56 – AssetPSRDetails message: NonRotatingEnergy element. Figure 57 – AssetPSRDetails message: PetersenCoil element. Figure 58 – AssetPSRDetails message: PowerTransformer element. Figure 59 – AssetPSRDetails message: PowerTransformerEnd element. Figure 60 – AssetPSRDetails message: TransformerTank element.
analytics 2 Asset management system obtains the analytics scores for the assets of interest GET AM-ADS AM-ADS AssetScores Step 7 – Analytics system identifies asset conditions that require intervention Scenario Scenario Name : Step No. Event Service Information Producer (Actor) Information Receiver (Actor) Information Exchanged 1 Analytics system sends asset health events to asset management system CREATED AM-ADS AM-ADS AssetHealthEvents 2 Asset management system send in work request to maintenance management system for assets with health events that require intervention CREATED AM-ADS MC-MAI WorkRequest Replacement of Asset Description of the Use Case Name of Use Case Use Case Identification ID Domain(s) Name of Use Case Asset Management, Asset Planning, Maintenance & Work Management. Replace a failing or failed asset Version Management Version Management Version Management Changes / Version Date Name Author(s) or Committee Domain Expert Area of Expertise / Domain / Role Title Approval Status draft, for comments, for voting, final 1 2016.11.01 IEC TC57 WG14 / Gowri Rajappan Gowri Rajappan Asset Management / IEC TC57 WG14 Part 4 (Asset Management) Team Lead Replace a failed asset Draft Scope and Objectives of Use Case Scope and Objectives of Use Case
Step 5 – Asset replacement work status is updated Scenario Scenario Name : Asset replacement work status is updated Step No. Event Service Information Producer (Actor) Information Receiver (Actor) Information Exchanged 1 Work management system reports work status upon a change CREATED MC-SCHD NO-NMON AM-ADS MC-MAI MaintenanceOrder 2 Asset management system requests work status GET AM-ADS MC-MAI AssetWork
(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.