tc 57 cim user group meeting june 2010 milano 1 technical committee 57 power systems management and...
TRANSCRIPT
1
TC 57
CIM user Group Meeting June 2010 Milano
Technical Committee 57POWER SYSTEMS MANAGEMENT AND ASSOCIATED INFORMATION EXCHANGE
TC 57
CIM user Group Meeting June 2010 Milano
Cyril Effantin EDF R&D
TC 57 – WG16Cim Market Extensions for EU
CIM and ENTSO-E Market EDI harmonizationFor transmission market EDI
leveraging a Common approach for derivating CIM into XML exchanged data
3
TC 57
CIM user Group Meeting June 2010 Milano
Agenda
Introduction
Aims of the IEC ENTSO-E Market EDI standards harmonization
Methodological framework
Short methodology examples
Conclusion
5
TC 57
CIM user Group Meeting June 2010 Milano
ENTSO-E (European Network of Transmission System Operators for Electricity http://www.entsoe.eu/)
Harmonization Works started in 2005 within IEC-ETSO collaboration (European Transmission System Operators)
from July 2009, ETSO is now fully merged into ENTSO-E
~ 500 million citizen served
650 GW Generation230 000 km EHV-HV lines1 500 000 km MV/LV lines
Demand: 3 000 TWh/year
Exchanges: 300 TWh/year
Investments by 2030
for T&D: ~500G€
ENTSO-E: 42 TSOs from 34 countries
7
TC 57
CIM user Group Meeting June 2010 Milano
Strategic targets
Market unbundling has distributed Business Processes across various Energy Stakeholders, typically : Scheduling Capacity allocation and nomination Reserve management Customer switching Settlement Calculations…
This however requires coordination of standards across stakeholders
Standardisation is a key element for IT Total Cost of Ownership reduction through : Harmonization of business processes Improved component reusability Market Interfaces Reduced integration costs
8
TC 57
CIM user Group Meeting June 2010 Milano
Aims of IEC - ENTSO-E Market EDI standards harmonization
CIM Market Extension CME creation Mainly north American vision of the market in 2003 Taking into account European market design : OTC Over the counter market
not modelled
Harmonization benefits Integrating the European market standard defined by ENTSO-E Market EDI works
into IEC• Harmonized European role model• Enhance IEC standards with business processes• Many business processes already modelled by ENTSO-E• Extensive business exchanged messages• Reuse of the ENTSO-E implementation guides• Building of a working framework based on UN/Cefact specification
Hosting the European profile as IEC international standards Taking advantage of the standardization community
9
TC 57
CIM user Group Meeting June 2010 Milano
How to achieve the convergence work ?Building of the CME (CIM Market Extensions)
Energy
Scheduling
Market
OperationsReservation Financials
ENTSO-E
ESS
ENTSO-E
ECAN
ENTSO-E
ERRP
ENTSO-E
ESP
WG14 - 61968
CIM
Distribution Part
WG13 - 61970
CIM
Transmission Part
WG 16 - 62325
CIM
Market
Extensions
European IEC Profile
North American IEC Profile
2 IEC
Task forces
Methodological Framework
+
Harmonized ENTSO-E EbIX EFET Role model
10
TC 57
CIM user Group Meeting June 2010 Milano
The ENTSO-E ebIX EFET Harmonized Role Model
ConsumerProducer
Production metering point
Consumption metering point
National area Certificate areaCBT
ETSO CBTNordpool
FranceGermanySpain
Nordpool
Pyrennées (France-Spain)TenneT AuctionEngland - Wales
RTE - RWE border
Germany
Dutch certificat market
RWEnetE-ONRTEEltra?EliaTennetREENGC
RWEnetE-ONRTEEltraEliaTennetREENGC
Seeland (island of Copenhagen)Bornholm (DK island connected to SE)belong to different control balance areas but the same market balance area
Some control balance areas are under another and do not report to a higher control entity than the first
UCTE
UCTE interconnected group
Coordination center zone
nn
Is composed of
coordination center operator
Netted inter center exchange schedule (CCT)
manages
Control block
nn
is composed of
Control block operator
(netted) inter block exchange schedule (CBS)
(Netted) control block exchange schedule (CBS)
manages
Capacity market area
Allocated capacity area
Common capacity area
Control entity 0..10..1
Controlled by
Grid operator
Balance group
Market area
Control area 1..n1..n
is composed of
Local market area
control area operator
(netted) inter area exchange schedule (CAX)
(netted) control area exchange schedule (CAX)
1..n1..n
manages
Market operator
Transmission capacity allocator
11
Facilitates
Operates
Operates
Billing agent
Market balance area
1..n1..n
Is composed of
1..n1..n
is composed of
operates
Profile maintenance party
Imbalance settlement responsible
sends invoicing information to
1..n1..n
Controls financially
Metered data aggregator
Sends data to
Sends metering information
Metered Data Responsible
Sends validated metered data
Domains: green: dual responsibilityClear ETSO responsibilityRed undefinedRoles:Clear ETSO responsibilityBlue EBix responsibilityBusiness actor dual responsibility
System operator
Provides capacity for
Receives capacity from
Exchanges cross border capacity (CAS)
(netted) balance exchange schedule (CAX)
Reports schedules to
declares constraints to
provides available transfer capacity
controls
Sends finalised schedules to
Trade responsible party
Unit Functional group
11
belong to
Metering point administrator
Production responsible party
sends schedule to
Consumption responsible party
sends schedule to
Balance responsible party
Trades internally with
Trades externally with
sends schedules to
provides bids to
may be financially responsible for
11
must have
Deals within
sends schedules to
obtains category profiles from
Makes contracts with
Grid access provider Balance supplier
Is contracted with
Is contracted withmay have grid usage contract with
Metering point
0..n0..n
Meters
0..n0..n
Is composed of
11
Meter administrator
administers meter information for
Meter operator
1..n
0..1
1..n
0..1
Maintains meters
Meter
1..n
operates and maintains
1..n
Metered data collector
Sends metered data
Register
1..n1..n
has
1..n1..n
has
1..n1..n
Administrates
1..n
collects data from
1..n
Party connected to the grid
has a firm energy contract withis contracted with
11
Has a balance delivery contract with
Local metering point
0..n0..n
Is balance responsible for
Provides access to
Supplies to
1..n
uses
1..n
Exchange metering point
Metering grid area
11Is operated by11
Part of1..n1..n
Operates
1..n1..n
Is composed of
1..n1..n
Contains
connects
Role Model1. Harmonisation of vocabulary2. Definition of terms3. Identification of roles and domains
IdentificationRoles of actors
IdentificationFunctional domains
Identificationgeographical domains
Balancing Area
Capacity AreaGrid Connecting Party
11
TC 57
CIM user Group Meeting June 2010 Milano
The ENTSO-E Market EDI Role Model the ENTSO-E concepts behind the scene
15
Version 2 Release 0 ETSO Standard Presentation 2005-06
Information flow approach
An actorCan have ROLES
different
In the same process
And he may exchange different types of document
Day ahead schedulingIntra dayTransits
System operation closureMetered data aggregation
Imbalance settlement
System operatorBalance responsible party
Imbalance settlement responsibleControl block manager
…All Roles that are possible may be
found in the ETSO Role Model
Balance responsible scheduleAllocated capacity scheduleControl block area schedule
Confirmation reportFinalised schedule
Regulation dataImbalance report
All documents use 100% compatible XML Schemas and DTDs
12
TC 57
CIM user Group Meeting June 2010 Milano
Example of ENTSO-E Market EDI UML Business Processes
13
TC 57
CIM user Group Meeting June 2010 Milano
How to achieve the convergence work ?Building of the CME (CIM Market Extensions)
Energy
Scheduling
Market
OperationsReservation Financials
ENTSO-E
ESS
ENTSO-E
ECAN
ENTSO-E
ERRP
ENTSO-E
ESP
WG14 - 61968
CIM
Distribution Part
WG13 - 61970
CIM
Transmission Part
WG 16 - 62325
CIM
Market
Extensions
European IEC Profile
North American IEC Profile
2 IEC
Task forces
Methodological Framework
+
Harmonized ENTSO-E EbIX EFET Role model
14
TC 57
CIM user Group Meeting June 2010 Milano
Common Methodological framework based on UN/Cefact CCTS
UN/Cefact (United Nations/Centre for Trade Facilitation and Electronic Business)
CCTS (Core Component Technical Specification)
• CCTS Gives a working framework to enhance semantic, interoperability in electronic data exchanges
• In particular, it helps to link business processes data exchanges with a common global information model (such as the CIM model)
ex: ENTSO-E Scheduling Process
15
TC 57
CIM user Group Meeting June 2010 Milano
Common methodological framework inspired from UN/Cefact CCTS (Core Component Technical Specification) standard
DMS OMS
Exchanged Dataanalysis
1
Message Conceptual Model
orMessageAssembly
(Exchanged at app interfaces)
4
Business Process Study:
Ex: outage Management
Contextual Modelor Business
Information Entity( Profiles )
3(Sub-Set, Constraints, restrictions)
5 Implementation Message Model ou
Syntax Binding
Technological derivation XSD, OWL,RDFS, SQL …etc
XML Exchanged Data
Validation
Information Modelor Core
Components( CIM )
2
CIM extensions
16
TC 57
CIM user Group Meeting June 2010 Milano
Information ModelCIM + Market
Extensions CME
(Extended CIM)
Regional Contextual Model
Message Assembly
Model
Message Implementation
syntactic Model
Profiling the CIM
Contextual Model Based on a parent model
With eventual restrictions.No additions possible to the parent model
Message Conceptual Model
XSD
Profiling Derivation
Implementation Derivation
Document Contextual Model
BasedOn
BasedOn
Application to WG16Market Domain
17
TC 57
CIM user Group Meeting June 2010 Milano
Information Model
Contextual Model
Extended CIM
Schedule Contextual Model
Style Market Profile 1
Style Market Profile N
Bid Contextual Model
XSD
…
Schedule Assembly Model
Bid Assembly Model
Message Assembly
Model
Document
Contextual Models
XSDMessage
Implementation syntactic Models
Regional
Contextual Models
…
Profiling Derivation
Implementation Derivation
18
TC 57
CIM user Group Meeting June 2010 Milano
XSD Schedule Document
Schedule Document message
Confirmation Document Message
Message Assembly
XSD Confirmation Document
Message Implementation
syntactic Models
Schedule Document
Business Processes
projects Scheduling Capacity Allocation
Confirmation Document
Reserve Management
Document Contextual Models
Settlement …
UML Information Model Extended CIM
UML Information Profiles European Style Market
Profile
North American Style Market
Profile
WG16 Methodological frameworkModeling
Rules
19
TC 57
CIM user Group Meeting June 2010 Milano
Model Derivation by theexample
CIM LEVELclass CIM Information Model
IdentifiedObject
Common::Document
+ category: String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: Status [0..1]+ lastModifiedDateTime: AbsoluteDateTime [0..1]+ revisionNumber: String [0..1]+ status: Status [0..1]+ subject: String [0..1]+ title: String [0..1]
IdentifiedObject
Common::Organisation
+ postalAddress: StreetAddress [0..1]+ streetAddress: StreetAddress [0..1]
IdentifiedObject
InfCommon::MarketRole
+ status: Status [0..1]
«Suppressed»+ kind: MarketRoleKind [0..1]
«proposed»+ type: String [0..1]
+Organisation
0..*
+Document
0..*
+MarketRoles
0..*«informative»
+Organisations
0..*
20
TC 57
CIM user Group Meeting June 2010 Milano
Model Derivation by theexample
European Style Market Profile
class European Style Market Profi le
«ACC»ESMPClasses::Organisation
{root,leaf}
+ aliasName: PartyID_String
«ACC»ESMPClasses::MarketRole
{root,leaf}
+ type: MarketRoleKind_String
«ACC»ESMPClasses::Document
{root,leaf}
+ aliasName: ID_String [0..1]+ category: MessageKind_String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: Doc_Status [0..1]+ revisionNumber: VersionCode_String [0..1]+ title: ID_String [0..1]
+marketRole
0..1
+sender_organisation
1
+subject_organisation
0..1
+receiver_organisation
1
class CIM Information Model
IdentifiedObject
Common::Document
+ category: String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: Status [0..1]+ lastModifiedDateTime: AbsoluteDateTime [0..1]+ revisionNumber: String [0..1]+ status: Status [0..1]+ subject: String [0..1]+ title: String [0..1]
IdentifiedObject
Common::Organisation
+ postalAddress: StreetAddress [0..1]+ streetAddress: StreetAddress [0..1]
IdentifiedObject
InfCommon::MarketRole
+ status: Status [0..1]
«Suppressed»+ kind: MarketRoleKind [0..1]
«proposed»+ type: String [0..1]
+Organisation
0..*
+Document
0..*
+MarketRoles
0..*«informative»
+Organisations
0..*
21
TC 57
CIM user Group Meeting June 2010 Milano
Model Derivation by theexample
European Style Market Profile
class European Style Market Profi le
«ACC»ESMPClasses::Organisation
{root,leaf}
+ aliasName: PartyID_String
«ACC»ESMPClasses::MarketRole
{root,leaf}
+ type: MarketRoleKind_String
«ACC»ESMPClasses::Document
{root,leaf}
+ aliasName: ID_String [0..1]+ category: MessageKind_String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: Doc_Status [0..1]+ revisionNumber: VersionCode_String [0..1]+ title: ID_String [0..1]
+marketRole
0..1
+sender_organisation
1
+subject_organisation
0..1
+receiver_organisation
1
class CIM Information Model
IdentifiedObject
Common::Document
+ category: String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: Status [0..1]+ lastModifiedDateTime: AbsoluteDateTime [0..1]+ revisionNumber: String [0..1]+ status: Status [0..1]+ subject: String [0..1]+ title: String [0..1]
class ESMPPrimi...
«primitive»String
{root,leaf}
class ESMPDataTypes
«Datatype»MessageKind_String
{root,leaf}
+ value: MessageTypeList
tagsETSOBusinessTerm = MessageType
22
TC 57
CIM user Group Meeting June 2010 Milano
Model Derivation by theexample
Contextual Message for Schedule Documentclass European Style Market Profi le
«ACC»ESMPClasses::Organisation
{root,leaf}
+ aliasName: PartyID_String
«ACC»ESMPClasses::MarketRole
{root,leaf}
+ type: MarketRoleKind_String
«ACC»ESMPClasses::Document
{root,leaf}
+ aliasName: ID_String [0..1]+ category: MessageKind_String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: Doc_Status [0..1]+ revisionNumber: VersionCode_String [0..1]+ title: ID_String [0..1]
+marketRole
0..1
+sender_organisation
1
+subject_organisation
0..1
+receiver_organisation
1
class Schedule Contextual Message Model
«ABIE»Schedule Contextual Model::
Document{root,leaf}
+ aliasName: ID_String+ category: MessageKind_String+ createdDateTime: AbsoluteDateTime+ revisionNumber: VersionCode_String
«ABIE»Schedule Contextual Model::
Market_Organisation{root,leaf}
+ aliasName: PartyID_String
«ABIE»Schedule Contextual Model::
MarketRole{root,leaf}
+ type: MarketRoleKind_String+subject_organisation
0..1
+sender_organisation
1+receiver_organisation
1
+marketRole
1
23
TC 57
CIM user Group Meeting June 2010 Milano
class Schedule Contextual Message Model
«ABIE»Schedule Contextual Model::
Document{root,leaf}
+ aliasName: ID_String+ category: MessageKind_String+ createdDateTime: AbsoluteDateTime+ revisionNumber: VersionCode_String
«ABIE»Schedule Contextual Model::
Market_Organisation{root,leaf}
+ aliasName: PartyID_String
«ABIE»Schedule Contextual Model::
MarketRole{root,leaf}
+ type: MarketRoleKind_String+subject_organisation
0..1
+sender_organisation
1+receiver_organisation
1
+marketRole
1
Model Derivation by theexample
Schedule Document Assembly level
class Schedule Contextual Message Model
«MBIE»Document
+ aliasName: ID_String+ category: MessageKind_String+ createdDateTime: AbsoluteDateTime+ receiver_organisation.aliasName: PartyID_String+ receiver_organisation.marketRole.type: MarketRoleKind_String+ revisionNumber: VersionCode_String+ sender_organisation.aliasName: PartyID_String+ sender_organisation.marketRole.type: MarketRoleKind_String+ subject_organisation.aliasName: PartyID_String [0..1]+ subject_organisation.marketRole.type: MarketRoleKind_String [0..1]
24
TC 57
CIM user Group Meeting June 2010 Milano
One more complicated ENTSO-E message derived through the methodology
XSD
class ESMP Schedule Document Assembly
«MBIE»RegularIntervalSchedule
{root,leaf}
+ endTime: AbsoluteDateTime+ startTime: AbsoluteDateTime+ timeStep: Seconds
«MBIE»RegularTimePoint
{root,leaf}
+ sequenceNumber: Integer+ value1: Float
«MBIE»TimeSeries
{root,leaf}
+ agreement.aliasName: ID_String [0..1]+ agreement.category: CapacityContractKind_String [0..1]+ aliasName: ID_String+ businessType: BusinessKind_String+ in_energyArea.aliasName: AreaID_String [0..1]+ in_organisation.aliasName: PartyID_String [0..1]+ measurementPoint.aliasName: MeasurementPointID_String [0..1]+ objectAggregation: ObjectAggregationKind_String+ out_energyArea.aliasNAme: AreaID_String [0..1]+ out_organisation.aliasName: PartyID_String [0..1]+ product: EnergyProductKind_String+ unit.name: MeasurementUnitKind_String+ version: VersionCode_String
«MBIE»TimeSeries_ActivityRecord
{root,leaf}
+ category: ReasonCode_String+ reason: String [0..1]
«MBIE»Document
{root,leaf}
+ aliasName: ID_String+ category: MessageKind_String+ createdDateTime: AbsoluteDateTime+ domain_energyArea.aliasName: AreaID_String [0..1]+ matchingPeriod_timeSchedule.startDateTime: AbsoluteDateTime [0..1]+ matchingPeriodtimeSchedule.endDateTime: AbsoluteDateTime [0..1]+ process.classificationType: ClassificationKind_String+ process.processType: ProcessKind_String+ receiver_organisation.aliasName: PartyID_String+ receiver_organisation.marketRole.type: MarketRoleKind_String+ revisionNumber: VersionCode_String+ sender_organisation.aliasName: PartyID_String+ sender_organisation.marketRole.type: MarketRoleKind_String+ subject_organisation.aliasName: PartyID_String [0..1]+ subject_organisation.marketRole.type: MarketRoleKind_String [0..1]
+regularIntervalSchedule 1
+timePoint 1..*
+timeSeries 0..*
+reason_activityRecord 0..1
XML NDR
Naming and Design Rules
25
TC 57
CIM user Group Meeting June 2010 Milano
Proposed CIM Extensions
With Scheduling and Capacity Allocation processes studies we have the following new CIM classes : Process TimeSeries BidTimeSeries Auction Price MeasurementPoint
26
TC 57
CIM user Group Meeting June 2010 Milano
Proposed CIM Extensions inside IEC62325 package
27
TC 57
CIM user Group Meeting June 2010 Milano
CIM Issues about combined shared CIM packages
28
TC 57
CIM user Group Meeting June 2010 Milano
Un/Cefact based methodology facilitated the CIM ENTSO-E Market EDI harmonization.
Having a whole information model giving the next step for future European work, EDI harmonization.
The methodological framework reduced the number of added new classes into the CIM to cover all ENTSO-e market exchanged messages through their business processes.
Feedback on the common methodological approach
TC 57
CIM user Group Meeting June 2010 Milano
Thank you for your attention.