Model-driven Asset Management

for Condition-Based Maintenance

Using the CIM Data Engineering Toolkit and the PI Historian
ABB Network Management, Kansas City Power & Light (KCPL) and the Electric Power Research
Institute (EPRI) have completed an R&D project to implement a Data Mining function based on
the CIM DE Toolkit and the OSIsoft PI Historian. The resulting product is an advanced
Model-driven Asset Management function that KCPL will use as a Condition-Based Maintenance
application for transformers and breakers.
Although the data stored in the PI Historian is
very useful for evaluating the history of the
electrical network, it was of limited use for
tracking the condition of actual physical assets.
Other than the tags required for State
Estimation, no information in the DE, EMS, or PI
intrinsically links any data to a location in the
electrical network. Even for data that can be
located in the electrical network, no intrinsic data
indicates which Asset was in use at any given
time in history. The history of an object could
be determined through manual investigation, but
not through any time-feasible method.
KCPL recognized the need to distinguish between the physical assets and the functional components
that make up the EMS electrical network model. It is not uncommon for an asset to be relocated so
that its role in the EMS model has changed even though its identity has not. This changing
relationship between an Asset and its location in the electrical network can complicate the problem of
maintenance when using only the data and tools available in a conventional EMS-Historian
deployment.
To solve this problem, an R&D project was conducted by ABB, KCPL and EPRI, with the following
objectives:
1. Use the new PI Analysis Framework (AF) functionality to implement a CIM-compliant representation
of the KCPL system in the Historian, so that historical data can be accessed in terms of this model
as an alternative to using the more conventional access methods based on the ID of a telemetered
or calculated "point". In this context, "CIM-compliant" means a complete representation, in terms
of the CIM, of the KCPL electrical system, including all electrical devices, along with their static
attributes and normal connectivity.
2. Extend the CIM model as needed, both in the CIM DE and in the PI AF, to represent the distinction
between the electrical components of the network model and the corresponding physical assets,
especially with respect to their association with the telemetered and/or calculated data (i.e.,
Measurements) produced by the EMS.

3. Use the existing CIM DE as the single source of the network model for both the EMS and the PI AF.
The interface to the EMS continues to use the existing export application but the interface to the PI
AF is a GID compliant interface consisting of a GDA server, GDA client(s), and a message bus.
4. Expand the "scope" of the CIM DE network model to include detailed electrical facilities up to and
including the medium voltage distribution feeder breakers. Also add any "dual model" extensions
needed to support exporting a more simplified representation of these new facilities to the EMS
system (e.g., a single injection in place of a group of distribution feeders) while exposing the
detailed model via the GDA server for export to the PI AF.
The implementation started in the Data Engineering component. The CIM Asset package was added
to the DE Toolkit database, allowing the users to associate real-world Assets with locations in the
electrical network, and to associate telemetry with the Assets. This allows PI to track historical data for
Assets separately from the historical data for the electrical network using performance calculations.
Various tools and user interface enhancements were created to assist with entering the new data.
The PI AF database was added to store a history-enabled copy of the electrical network and Assets.
The data in AF is stored using CIM classes and properties. AF is able to directly retrieve data from the
PI database for specific Assets or electrical equipment. AF provides programming APIs to access the
model data and historical telemetry so that reports can be created from the data stored in AF and PI.
In this case, a report was created to determine the last time a breaker Asset was opened so that
breakers could be identified for routine maintenance.
The SISCO UIB solution was used to create a CIM GDA bus to draw data from the DE Toolkit into the
AF database.
The new implementation and the underlying infrastructure are illustrated in figure 1 below:

GDA Bus (IBM MQ/SISCO UIB)

ABB DE
GDA
Service

SISCO PI AF
Adapter &
Model
Synchronizer

GDA Clients

OSIsoft PI
AF

AF Clients

Preexisting Components

ABB CIM DE
Toolkit

ABB
Network
Manager
EMS

OSIsoft PI
Historian

Figure 1 Technical Overview

In addition to the Condition-Based Maintenance application, this new technology will allow KCPL to
implement new analysis and reporting functions of significant economic and technical benefit.
Condition-Based Maintenance
Application

Desktop access
Paging/email notification
Web access

AF

PI Server

PI Server

..

GDA
Asset
Management
System

..

CIM DE
Environment

Network Manager
EMS

Figure 2 Functional Overview

field devices