Académique Documents
Professionnel Documents
Culture Documents
ProjectReport
TerrySaxton,XtensibleSolutions
HerbFalk,SISCO
DaveBecker,EPRI
November17,2009
WhyDoWeCareAboutHarmonization?
SmartGridinitiativeisallaboutinteroperability
InteroperabilityFrameworkwithprioritizedactions
CommonSemanticModel
1of5crosscuttingandoverarchingissues
A common semantic model for application level communications is necessary in several
areas of the Smart Grid. Key areas, for example, are the integration of utility Transmission
and Distribution field operations with Information Technology and Back Office Systems and
ultimately with Customer Premise Systems
KeyActions DevelopaCommonSemanticModel
NIST should work with IEC TC57, NEMA, ASHRAE SPC 135, and OASIS to devise a
common semantic model (using, for example, XML Schema and XML). The objective will
be to unify the models of CIM (IEC61970, IEC61968, MultiSpeak) and IEC 61850 including
correspondences with ANSI C12.19 and ASHRAE 135 to form a common representation of
information models constructed by these standards efforts for the Smart Grid.
Ref:EPRIReporttoNISTontheSmartGridInteroperabilityStandardsRoadmap,Section6.1.3,
CommonSemanticModel,August10,2009
BenefitsofCommonSemanticModel
Otherbenefitsofcommonsemanticmodel:
Extend IEC 61968 and MultiSpeak standards for DER: IEC 61968 needs DER and PEV
models, but should be harmonized with the existing DER object models in IEC 61850-7420, as well as all on-going DER 61850 development. IEC 61850-7-420 has architectural
issues to be addressed.
Extend IEC 61850 standard from substation to control center: Since the data in the
substation uses the IEC 61850 information model, this data should be reported to the
control center using the same information model. This will also simplify the harmonization
efforts between the models of data collected from the field and the CIM.
TheNISTRoadmapclearlydefinestheneedforacommon
semanticmodelandthedesiretouse61850forcommunicating
fromsubstationsandDERtotheControlCenterandback
officesystems
ThereareseveralActorsthatcouldbeinvolvedinthisinformation
exchange(e.g.Planning,Operations,SCADA,Substation/Protection
Engineering,Maintenance,etc.)
Thefocusofthispresentationisoncreatingacommonsemanticmodel
fortheCIMand61850substationautomationstandards
EPRICIM61850HarmonizationProject
Goals
Approachharmonizationthroughdevelopmentofaunified
UMLmodelandapplicationofthe3layerTC57Reference
Architecture
Enabletheentryandupdateofsubstationconfigurationdataonce
Enableaccesstorealtimedatafrom61850devicestodirectlyfeed
SCADAandbackofficesystemsbasedontheCIMstandards
Informationlayer extendedCIMtosupportgeneralized61850model
concepts
Businesscontextlayer todefineprofilesforgeneratingSCLfiles
Implementationlayer tospecifysyntaxforinformationexchange
EPRIcontractedwithXtensibleSolutionsandSISCOto
completethisproject
IECTC57ThreeLayerArchitecture
Information and Semantic Models
CIM UML
InformationModel
Definesallconceptsneededforexchange
ofoperationalloadflowmodels
Context
Profile
Message Syntax
Schema
Reusedparts
Newextensions
Contextuallayerrestrictsinformationmodel
SpecifieswhichpartofCIMisusedfor
staticmodelexchange
Mandatoryandoptional
Restrictions
Butcannotaddtoinformationmodel
Filesyntax
Canrelabelelements
Changeassociationstodefinesingle
structureformessagepayloads
Mappingstovarioustechnologiescanbe
defined
HarmonizationMethodology
61850 UML
Model
rg
Me
Me
r ge
CIM UML
Model
e
Unified UML
Model
Business context
(Profile)
Apply 61850
Domain Context
Information Model
Implementation
Generate XML
Document
Profile for
Substation
Configuration
SCL XML
Document
61850
N&DR
61850
Standards
(SCL XML
Schema)
IEC61970CIMUMLModelPackages
IEC61970CIM Version
{root}
+
+
LoadM odel
Outage
Protection
ControlArea
Generation
Production
(from Generat ion)
Wires
S CADA
GenerationDynamics
Equivalents
Contingency
OperationalLimits
T opology
M eas
Core
Global
Domain
CIMEquipment
Containers
Core: :
ConnectivityNodeContainer
Core: :
GeographicalRegion
+Region
0..1
+Regions
0..*
Core: :
S ubGeographicalRegion
Core: :
EquipmentContainer
Core: :
Pow erS ystemResource
+MemberOf_EquipmentContainer
0..1
+Region
+Region
0..1
0..1
+Lines
+Contains_Equipments
0..*
0..*
Plant
Line
+Substations
+MemberOf_Substation
0..*
Core: :
S ubstation
0..1
+MemberOf_Substation
+Contains_VoltageLev els
1
0..*
Core: :
VoltageLevel
+MemberOf_VoltageLev el
0..1
0..* +Contains_Bay s
+Contains_Bay s 0..*
Core: : Bay
Core: :
Equipment
61850SCLObjectModel
1
Function
Functional/substation structure
Subfunction
Substation
1
1
1
Transformer
1
Voltage
level
Bay
Equipment
1
1
SubEquipment
Phase
0..2
Terminal
1..*
AccessPoint
1..*
1
Communication structure
CBR
DIS
1
ConnectivityNode
1
0..*
LNode
1
0..*
Client access points
1
0..*
1
Server
LDevice
1..*
0,1
Subnetwork
0,1
IED
0,1
Router
Clock
VTR
Data
1..*
BuildingtheUnifiedModel
Reverse
Engineer/
Analysis
Information Model
CIM UML
Context
Message Syntax
Combined
UML
61850 UML
Model
Merge
61850 XML
Schemas
Vision:ThreeLayerArchitecturefor
SCLFileExportandImport
Information Model
Conforms to extended
IEC 61970-301 CIM
with new 61850 packages
Unified
UML Model
Context
Conforms to
new 61850
SCL Profile
Specification
ReusedCIMparts
New61850extensions
61850 SCL
Profile
Contextuallayerrestrictsinformationmodel
SpecifieswhichpartofCIMisusedforSCL
fileexport/import
Mandatoryandoptional
Restrictions
Butcannotaddtoinformationmodel
61850 XML
Schema
Filesyntax
Canrelabelelements
Changeassociationstodefinesingle
structureformessagepayloads
Mappingstovarioustechnologiescanbe
defined
Message Syntax
Conforms to
IEC 61850-7-6
SCL Specification
with some mods
UnifiedModel
Definesallconceptsneededforexporting
andimportingSCLfiles
InterfaceDesign
Useschemastodesignpopulators andtransformers
DiagramsimilartoCPSM(CommonPowerSystem
Model)softwaretogenerateinstancefiles
Example:SchemafromCIMforLoadFlow
ModelExchange
Power
System Data
CIM
(in UML)
UML
to RDF
Transformers
ref
ere
nc
es
Exporter
Enterprise
Architect
CIM as
XML/RDF specifies
Schema
Power
System Data
as
XML/RDF
Harmonization
Use Case
Interfaces
Based on
Network Extension Interface 1
Use Case 1
Use Case
HarmonizationUseCases
1. ExportanSCLSSD/SCDXMLfilefromaNetworkModelManagerand
Repository(NMMR)wheretheoperations/planningmodelismaintained
Single,commonmodelforplanning,operations,andsubstationengineering
2. UpdateanEMSloadflowmodelmaintainedinaNMMRfromanimported
SCLXMLfile
CreatetheabilitytoimportanSCLfileintomodelingapplicationsbasedonthe
unifiedmodelsothataloadflowmodelcanbeappropriatelyupdatedwith
fieldchangesmadebyasubstationengineerduringactualinstallationor
equipmentreplacement
Includestopologyupdatesaswellaschangesinequipmentproperties,
suchasoperationallimits
3. SCADAdataimportfrom61850devices
Terminology
SCL SubstationConfigurationLanguage
SSD SystemSpecificationDescription(Substation othercontentoptional)
SCD SubstationConfigurationDescription(Substation,IEC,Communication)
Othersdefined
InterfaceforUseCase1
Substation/ProtectionEngineeringto61850
SystemConfigurator
SCLSSDfiletypehasthefollowingXMLelements(attributesnot shown)
SubstationSection
VoltageLevel
PowerTransformer
TransformerWinding
TapChanger
Voltage
Bay
ConductingEquipment
Thisincludesallprimaryequipmentincludingbreakersandswitchesasneededforan
operationalmodel
SubEquipment
Thisaddsthedetailneededforrepresenting3phases
Terminal
ConnectivityNode
cNodeName (relativetoBay)addedbySSengineer
Lnode
SubstationHarmonization
Substationharmonization
Needtoagreetocommondefinitions recommendations
made
SourcesincludeIECGlossary,IECTC57Glossary,IEC
61970/61968,IEEEDictionary
UpdatetoCIMUMLtoaddmissingclasses
Addnewobjects/enumerationsinSCLtoalignequipment
typeswithCIMPSRs
AdditionalPSRs added
- Added
AddednewSCLItems
TotPredefinedCommonConductingEquipmentEnum,
thefollowingenumerationvaluesareproposedtobe
added:
BBS BusBarSection
CND Conductor
CON Connector
EnergyConsumer
RINV RectifierInverter
SCMP SeriesCompensator
TotPredefinedGeneralEquipmentEnum,thefollowing
enumerationvaluesareproposedtobeadded:
GEN GeneratingUnit
PROT ProtectionEquipment
Alignmentlookslike:
Harmonization
Use Case
Interfaces
Based on
Network Extension Interface 1
Use Case 1
Use Case
Interface
Use Case 2
HarmonizationUseCases
1. ExportanSCLSSD/SCDXMLfilefromaNetworkModelManagerand
Repository(NMMR)wheretheoperations/planningmodelismaintained
Single,commonmodelforplanning,operations,andsubstationengineering
2. UpdateanEMSloadflowmodelmaintainedinaNMMRfromanimported
SCLXMLfile
CreatetheabilitytoimportanSCLfileintomodelingapplicationsbasedonthe
unifiedmodelsothataloadflowmodelcanbeappropriatelyupdatedwith
fieldchangesmadebyasubstationengineerduringactualinstallationor
equipmentreplacement
Includestopologyupdatesaswellaschangesinequipmentproperties,
suchasoperationallimits
3. SCADAdataimportfrom61850devices
Terminology
SCL SubstationConfigurationLanguage
SSD SystemSpecificationDescription(Substation othercontentoptional)
SCD SubstationConfigurationDescription(Substation,IEC,Communication)
Othersdefined
InterfaceforUseCase2
SubstationConfigurationDBtoNMMR
SCLSCDfiletypehasthefollowingXMLelements
SubstationSection(sameasUseCase1)
IEDSection
CommunicationsSection
Proposedlinkageof61850toPSRs
Harmonization
Use Case
Interfaces
Based on
Network Extension Interface 1
Use Case 1
Use Case
Interface
Use Case 2
Interface
Use Case 3
HarmonizationUseCases
1. ExportanSCLSSD/SCDXMLfilefromaNetworkModelManagerand
Repository(NMMR)wheretheoperations/planningmodelismaintained
Single,commonmodelforplanning,operations,andsubstationengineering
2. UpdateanEMSloadflowmodelmaintainedinaNMMRfromanimported
SCLXMLfile
CreatetheabilitytoimportanSCLfileintomodelingapplicationsbasedonthe
unifiedmodelsothataloadflowmodelcanbeappropriatelyupdatedwith
fieldchangesmadebyasubstationengineerduringactualinstallationor
equipmentreplacement
Includestopologyupdatesaswellaschangesinequipmentproperties,
suchasoperationallimits
3. SCADAdataimportfrom61850devices
Terminology
SCL SubstationConfigurationLanguage
SSD SystemSpecificationDescription(Substation othercontentoptional)
SCD SubstationConfigurationDescription(Substation,IEC,Communication)
Othersdefined
InterfaceforUseCase3
61850FieldDevicestoSCADA
SCADAdata/controlimport/exportfrom61850
devices
SCLSCDfile,importedintoNNMR/unifiedmodel
(UseCase2)hastheinformationto:
DefinecommunicationaddressingforSCADA
Defineremotepoints
Mayhavedefinitionoflimitsanddeadbands as
initialvalues.
Needtobeabletousethisinformationtoconfigurethe
SCADAmodelandbeabletodrivethe61850SCADA
acquisitioninterface
Thenuseunifiedsemanticmodeltounambiguouslymap
61850datatoCIMrepresentation(andviceversa)
RecommendationsforHarmonization
NeedpersistentIDs addedRDFID(equivalenttordf:id inCIM
XML)
SCLfileshaveinternalreferentialintegritythroughtheuseof names
Whenmerged/importedintoaunifiedmodel,nameswillbe
duplicated
Useofnamesalsomeansthatitisdifficulttopickupchanges
Unitsneedtobealigned
Measurements
SCADAandControl
Communicationsexpanded
NeedtomakebetteruseofProfiles(Layer2)torestrictgeneral
CIMmodelforspecificbusinesspurposeratherthancreating
specializedUMLmodels
ProjectStatusandPlans
Status
Businessusecasesandinterfacesdefined
Commonsemanticmodel(unifiedUMLmodel)developed
ReuseandextensionofexistingCIMtoaddmissing61850concepts
AvailableonSparx EnterpriseArchitect
PresentedtoIECTC57asproposalforCIMand61850SCLchanges
Plansfor2010
Addressnewusecase AssetandConditionBasedMaintenance(CBM)
applicationimportofdatafrom61850substationdevices
DefineaprofileforexportingSCLSSDfilesfromacommonnetworkmodel
manager
DefineprofiletoimportanSCLSCDfileintocommonnetworkmodelmanager
Enablemodelingapplicationsbasedontheunifiedmodeltobe
appropriatelyupdatedwithfieldchangesmadebyasubstationengineer
duringactualinstallationorequipmentreplacement
Includestopologyupdatesaswellaschangesinequipmentproperties,such
asoperationallimits
Demonstrationandinteroperabilitytests
PresenttoSGIPaspartofoverallSGsemanticmodel
TogetherShapingtheFutureofElectricity