CIM for Asset Registry and Big
Data Asset Health Analytics
Gowri Rajappan
12 November 2014
Doble Engineering Company
Global Leader in T&D Engineering Services
Founded 1920
2
Asset Management
• Failure is costly
–
–
–
–
Replacement
Revenues lost
Fines incurred
Loss of goodwill
• What to do?
– Monitor assets
– Detect/predict failure
signature
What more?
• How do we optimize asset utilization?
• How do we make assets live longer?
• How do we optimize costs around the asset?
3
Asset Management
The systematic and coordinated activities and practices ISO 55002:
through which an organization optimally and sustainably 3 Terms and
Definitions
manages its assets and asset systems, their associated
performance, risks and expenditures over their life cycles for
the purpose of achieving its organizational strategic plan.
ISO 55002:
Demonstrates to Regulators, Shareholders and
4.2 Understanding the
Stakeholders a managed process
needs and expectations of
stakeholders
• Repeatable, defensible, systematic
• Produces optimal investment and risk management
decisions
• Facilitates continuous improvement
4
What It Means
Behooves us to use all relevant asset information…
5
Data Aggregation
Challenging to bring the data together
6
Use Case: Risk-based Power
Transformer Load Management
• System contingencies and planned outages necessitate
overloading.
– Overloading = accelerated aging & likelihood of failure.
• Certain assets – e.g., old and critical units – require careful
load monitoring and management.
• The asset use must be balanced against the loss of life and
replacement cost.
• Load management considerations apply to both Asset
Management and Operations:
– Asset Management: Survey and set loading limits for power
transformers.
– Operations: In case of contingencies or planned outages,
allocate additional transformer load in a manner that keeps the
likelihood of failure low and takes acceptable additional aging.
Transformer Aging and Failure
Transformers age with use, principally due to thermal insulation
deterioration. There are three contributing effects that are functions
of temperature:
• Pyrolisis: thermal ageing of cellulose
• Oxidation: up to 3x speed-up due to oxygen dissolved in the oil
• Hydrolysis: up to 15x speed-up due to moisture
When the transformers
ultimately fail, degradation
of paper insulation and
accumulation of mechanical
damage from through faults
are the reasons.
Data for Transformer Load
Management
• The analytics in IEEE C57.91 provide the basis for transformer load
management. These calculations need disparate data:
–
–
–
–
Nameplate information: EAM system.
Condition monitoring data: SCADA historian, LIMS.
Operational history: SCADA historian.
Weather: Weather service.
• Assessment output could be provided to a user, EAM system, or
operations scheduling system.
• Two expensive yet fragile ways in which data is provisioned:
– Manual data collection.
– Custom system integration.
• Better solution (cheaper lifecycle cost, robust): standards-based
integration.
Case for CIM-based Asset Registry
• Facilitate data integration for a variety of asset analytics.
• A central directory of assets.
– Containing asset classification information, such as
manufacturer, design, location, criticality.
– Pointers to operational data, condition monitoring data,
laboratory test data, work history, etc.
– CIM for common semantic model and standards-based
integration.
• Analytics queries the Asset Registry for asset class of
interest, retrieves references, and retrieves data necessary
for analytics.
Asset Registry
CIM Models and Messages
• Asset-related CIM models central to the asset registry.
• CIM extensions being made in CIM Asset Health Focus Community
(AHFC).
– AHFC consists of CIM experts (TC57 WG13/WG14 members) and asset
management SMEs from industry/utilities.
– Some extensions: modeling of all large asset/components for which
utilities want to track/manage lifecycle, fine-grained asset lifecycle
model, time/frequency series measurements for condition monitoring
and SCADA data.
• The work includes definition of an Asset Decision Support business
function and CIM messages to provide data for this business
function.
– Messages for asset-related data profiles such as nameplate, laboratory
test data, field inspection data, work, condition monitoring data, etc.
– To be incorporated in 61968-4 (CIM for Asset Management) standard.
Asset Model Overview
IdentifiedObject
IdentifiedObject +AssetInfo
AssetInfo
0..1
+AssetInfo
IdentifiedObject
+AssetModel
AssetFunction
AssetModel
0..1
+
+
+
+
+
0..1
configID :String [0..1]
firmwareID :String [0..1]
hardwareID :String [0..1]
password :String [0..1]
programID :String [0..1]
ProductAssetModel
+
+
+
+
+
corporateStandardKind :CorporateStandardKind [0..1]
modelNumber :String [0..1]
modelVersion :String [0..1]
usageKind :AssetModelUsageKind [0..1]
weightTotal :Weight [0..1]
+ProductAssetModels
+M anuf acturer OrganisationRole
0..*
0..1
Ma nuf act u r er
+Assets 0..*
Hazar d
IdentifiedObject
Asset
+
+
+
+
+
+
+
+
+
+
+
+
acceptanceTest :AcceptanceTest [0..1]
critical :Boolean [0..1]
electronicAddress :ElectronicAddress [0..1]
initialCondition :String [0..1]
initialLossOfLife :PerCent [0..1]
lifecycle :LifecycleDate [0..1]
lotNumber :String [0..1]
purchasePrice :Money [0..1]
serialNumber :String [0..1]
status :Status [0..1]
type :String [0..1]
utcNumber :String [0..1]
+OrganisationRoles
+Assets
0..*
0..*
OrganisationRole
AssetLocationHazard
AssetOrganisationRole
AssetOwner
AssetUser
+Assets
Ma int a iner
0..*
Document
+Assets
+P r ocedures
0..*
0..*
«A HFC»
+ positionNumber :Integer [0..1]
+
+
+
instruction :String [0..1]
kind :ProcedureKind [0..1]
sequenceNumber :String [0..1]
+Procedure
AssetContainer
+AssetContainer
0..1
0..1
IdentifiedObject
0..1 +AssetContainer
ComMedia
Procedure
Seal
+Seals +
+
0..*
+
+
appliedDateTime :DateTime [0..1]
condition :SealConditionKind [0..1]
kind :SealKind [0..1]
sealNumber :String [0..1]
+ProcedureDataSets
0..*
Document
ProcedureDataSet
+
completedDateTime :DateTime [0..1]
Asset Lifecycle Modeling
IdentifiedObject
InfAssets::FailureEvent
Common::ActivityRecord
+ActivityRecords
+
+
+
+
+
+
+
+
+
createdDateTime :DateTime [0..1]
reason :String [0..1]
severity :String [0..1]
status :Status [0..1]
type :String [0..1]
AHFCAssets::
AssetBaselineLifeExpectancyEvent
AHFCAssets::
AssetBaselineConditionEvent
0..*
+Assets
corporateCode :String [0..1]
failureIsolationMethod :FailureIsolationMethodKind [0..1]
faultLocatingMethod :String [0..1]
location :String [0..1]
+
0..*
+
+
condition :AssetConditionKind [0..1]
expectedLife :Time [0..1]
lossOfLifePercent :PerCent [0..1]
«enumer ation»
AHFCAssets::
AssetConditionKind
IdentifiedObject
AHFCAssets::
AssetLifecycleStateEvent
Assets::Asset
+
+
+
+
+
+
+
critical :Boolean [0..1]
electronicAddress :ElectronicAddress [0..1]
lotNumber :String [0..1]
purchasePrice :Money [0..1]
serialNumber :String [0..1]
type :String [0..1]
utcNumber :String [0..1]
«A HFC Deprecate»
+ acceptanceTest :AcceptanceTest [0..1]
+ initialCondition :String [0..1]
+ initialLossOfLife :PerCent [0..1]
+ lifecycle :LifecycleDate [0..1]
+
0..*
+AssetContainer
0..1
Assets::AssetContainer
+
+
+
AHFCAssets::
AssetAcceptanceTestEvent
+
+
success :Boolean [0..1]
type :String [0..1]
«C ompo und»
Common::Status
+
+
+
+
dateTime :DateTime [0..1]
reason :String [0..1]
remark :String [0..1]
value :String [0..1]
dateTime :DateTime [0..1]
success :Boolean [0..1]
type :String [0..1]
«C ompound»
Assets::LifecycleDate
+
+
+
«A HFC M odif y»
+ currentLifecycleState :AssetLifecycleStateKind [0..1]
+Assets
«C ompound,A HFC Remo ...
Assets::AcceptanceTest
state :AssetLifecycleStateKind [0..1]
manufacturedDate :Date [0..1]
receivedDate :Date [0..1]
retiredDate :Date [0..1]
«A HFC»
+ latestInServiceDate :Date [0..1]
+ latestOutOfServiceDate :Date [0..1]
+ latestRefurbishedDate :Date [0..1]
«A HFC M odif y»
+ latestInstalledDate :Date [0..1]
+ latestRemovedDate :Date [0..1]
+ purchasedDate :Date [0..1]
new
rebuilt
overhaulRequired
other
«enumer ation»
AHFCAssets::
AssetLifecycleStateKind
planned
manufactured
purchased
received
installed
inService
outOfService
removed
refurbished
retired
Illustrative Analytic Application
• Identify assets and available data from Asset Registry:
– Get all transformers > x years old (identified from Asset Registry
classification data).
• Get necessary data using reference provided by Asset Registry:
– Get nameplate data (data from WAMS).
– Get online temps, dissolved gas/moisture, etc. data for time window
(from SCADA historian).
– Get laboratory data for dissolved gas/moisture ( from LIMS).
• Calculate loading impact on the transformers.
– Aging factors at set time intervals – e.g., hourly.
– Risk of bubble formation at peak loading time intervals?
– Determine if new loading limits need to be imposed for any of the
analyzed transformers.
Asset Registry-enabled Asset
Management Environment
• Work with integration pattern used by the utility: ESB,
SOAP/REST web services, etc.
• Once in place, ease of deploying any new asset analytic
or software: only have to browse the Asset Registry to
determine if all needed data is available.
• Use of common CIM “language” enables better
communication between owners of different data
systems and leads to better use of the enterprise data.
• Elucidates standardization and dissemination of best
practices to the industry.
Our Experience
• We have developed an asset analytics product – Doble
Asset Risk Management System (ARMS).
– CIM for asset information.
– 61850-harmonized CIM for measurements.
– CIM-based Business Intelligence/analytics.
• Incorporating capabilities that enable Strategic Asset
Management:
– Risk Management framework
• Take into account criticality.
• Identify low frequency events that have high impact.
– Asset and conditional alerts.
– Asset watch list.
17
Our Experience
• Challenging to develop ahead of standards development.
– Anticipate the direction/shape the standards would take.
– Contribute to the standards development.
– Design flexibly to change system as necessary when standards
become available.
• There is pent-up demand for asset health analytics-based
strategic asset management product.
– Big data processing technology needed to realize this is mature.
– Secure cloud architecture for economies of scale proven,
available, and supported by NIST standards.
– CIM standards for enterprise integration of this capability in
development and will be available in the near future.
18
References / Acknowledgements
• IEEE Std C57.91, “IEEE Guide for Loading Mineral-OilImmersed Transformers.”
• Ken Elkinson, Greg Topjian, Matt Lawrence & Tony McGrail,
“Aspects of Power Transformer Asset Management,” IEEE
T&D Conference, Orlando, May 2012.
• Kristina Lukin & Bill Yturralde (SDG&E) and Ken Elkinson,
Matt Kennedy, Matt Lawrence & Tony McGrail (Doble),
“Transformer Condition and Loading Evaluation,” CIRED
22nd International Conf on Electricity Distribution,
Stockholm, June 2013.
Contact
Gowri Rajappan, Ph.D.
grajappan@doble.com
617-926-4900
Doble Engineering Company
Watertown, MA
20