CIM User Group – SACLAY - June 2019 IEC 62325: CIM profiling applied to European market exchanges

Karyn JEAN FRANCOIS – André MAIZENER AGENDA

1. CIM FOR MARKET 2. CIM ORGANIZATION 3. IEC 62325 4. EUROPEAN STYLE MARKET PROFILE 5. EXAMPLE: ESMP PROFILING APPLIED TO BALANCING PROCESS 6. RTE EXPERIENCE

© Copyright RTE 2019 1

CIM for Market CIM for Market

CIM is a Common Information Model.

➢ CIM is an abstract model that represents all the major objects in power systems and market operations.

➢ CIM is composed of IEC 61970-301, IEC 61968-11 and IEC 62325-301.

➢ The CIM IEC 62325-301 caters for the introduction of the objects required for the operation of Electricity Markets.

© Copyright RTE 2019 Toward interoperability: Smart Grid Architecture Model (SGAM)

© Copyright RTE 2019 Smart Grid plane: information layer

Information Management

Power System Primary Equipment Market

Enterprise

Operation

Station Generation Zones Transmission Field (Hierarchy) Distribution Process DER Domains Customer (Home, Building, Industry, EV, Mobility)

© Copyright RTE 2019 Smart Grid plane – CIM key components

CIM (IEC 61968, IEC 61970, IEC 62325) one of the pillars of Smart Grid, for grid management and market communication

• Energy Management Systems • Distribution Management • Market Communication

IEC 61850 one of the core standards Market providing interoperability in field and station of Smart Grids Enterprise Operation • Substation automation • Distribution automation Station • Distributed Energy Resources Generation Zones • Hydro Power Transmission Field (Hierarchy) Distribution Process Power System DER Primary Equipment Domains Customer (Home, Building, Industry, EV, Mobility) © Copyright RTE 2019 Smart Grid plane – Communication layer

MADES (IEC 62325-503) MArket Data ExchangeS for the IEC 62325-351 Profile :

• Defines protocols for deregulated energy market communications

• Specifies a standard for a decentralized common communication platform based on international IT protocol standards Market

Enterprise

Operation

Station Generation Zones Transmission Field (Hierarchy) Distribution Process Power System DER Primary Equipment Domains Customer (Home, Building, Industry, EV, Mobility) © Copyright RTE 2019 2

CIM organization International level organisation IEC (International Electrotechnical Commission)

TC 57: Technical committee POWER SYSTEMS MANAGEMENT AND ASSOCIATED INFORMATION EXCHANGE

© Copyright RTE 2019 TC57 covers the supply side of Smart Grid

Energy management systems (61970)

Deregulated energy market communications (62325)

Distribution management systems (61968)

Market

Enterprise

Operation

Station Generation Zones Transmission Field (Hierarchy) Distribution Process DER Domains Customer (Home, Building, Industry, EV, Mobility) © Copyright RTE 2019 European level organization ENTSO-E (European Network of Transmission System Operators for Electricity)

▪ Market Committee: CIM EG (CIM Expert Group), related to the WG 16.

▪ System Operations Committee: PT CGM (Project Team Common Grid Model), related to the WG 13.

43 TSOs from 36 countries are members of ENTSO-E © Copyright RTE 2019 RTE’s role and commitment

➢ RTE was one of the main initiators and designers of the European Methodology, alongside EDF, Alstom (GE), KEMA and ZAMIREN.

➢ RTE has been continuously and actively contributing to TC 57 since 2006.

➢ RTE participates in ENTSO-E CIM Expert Group (ENTSO-E CIM EG): ▪ Ms. Greta MUNNECKE BONNARY is CIM EG Convenor ▪ M. Paul PLESSIEZ is an active member of CIM EG

© Copyright RTE 2019 3

IEC 62325 Deregulated energy market communications IEC 62325 Methodology

301 CIM is only an abstract model → profiles have to be defined to handled business processes. information model CIM Interoperability tests are only carried out on a profiling derivation 351 given profile, not on CIM !

style market … style market profile 1 profile n A profile is the basic outline of all the regional information that is required to satisfy a contextual contextual model models specific business environment

schedule bid document contextual … contextual contextual model model models

implementation derivation message 451-n schedule assembly bid assembly assembly model model model

message implementation xsd xsd syntactic model © Copyright RTE 2019 ESMP and NASMP

Item European Style North American Market Profile Style Market Profile Market approach Zonal approach and third party access Nodal approach (based on EU regulations)

Profile modelling Profile modelling in UML, using Profile modelling using web ontology methodologies EnterpriseArchitect. langage OWL The methodology has been standardized. The methodology is not standardized

Volumetry of CIM for ESMP contains 25 classes, from CIM for NASMP contains about 200 classes which all profiles are derived classes

© Copyright RTE 2019 62325-301: CIM for Market

Common classes used at the international level European style market classes Northern American style market classes

© Copyright RTE 2019 4

European Style Market Profile Key features and Methodology 62325-351 : European Style Market Profile

class EuropeanStyleMarketProfile

«ACC» +MarketDocument 0..* MarketParticipant «ACC» +MarketRole M a r ketRole «ACC» + description: String [0..1] MarketDocument «ACC» +MarketParticipant + electronicAddress: ElectronicAddress [0..1] 0..1 + type: MarketRoleKind_String + mRID: PartyID_String [0..1] P r ocess + createdDateTime: ESMP_DateTime [0..1] +Process 0..* + description: String [0..1] + name: String [0..1] + classificationType: ClassificationKind_String [0..1] 0..* + docStatus: Action_Status [0..1] + phone1: TelephoneNumber [0..1] + processType: ProcessKind_String [0..1] «ACC» + mRID: ID_String [0..1] + streetAddress: StreetAddress [0..1] +Names Na me + revisionNumber: ESMPVersion_String [0..1] 0..* + status: Action_Status [0..1] + name: String + title: PayloadId_String [0..1] +MarketParticipant 0..* + type: MessageKind_String [0..1] +Names

+AceTariffType 0..* 0..*

«ACC» «ACC» +Original_MarketDocument 0..1 AttributeInstanceComponent AceTariffType «ACC» + attribute: String [0..1] +Names AnalogValue + type: TariffKind_String +AttributeInstanceComponent «ACC» + attributeValue: AttributeValue_String [0..1] MarketEvaluationPoint 0..* + description: String [0..1] + position: Position_Integer [0..1] 0..* +Names + mRID: String [0..1] +AceTariffType 0..1 +DateAndOrTime 0..* + mRID: MeasurementPointID_String + name: String [0..1] +AttributeInstanceComponent 0..* + name: String [0..1] 0..* «ACC» + timeStamp: DateTime [0..1] DateAndOrTime +MarketEvaluationPoint 0..1 + value: ESMP_Float [0..1] ▪ ESMP provides a unique basis + date: Date +Names 0..* +Names 0..* +AnalogValues 0..* + time: Time [0..1]

+DateAndOrTime 0..* +Domain 0..1 «ACC» +Point 0..* «ACC» P r ice «ACC» Ana log from which all the profiles Doma in «ACC» + amount: Amount_Decimal [0..1] + description: String [0..1] P oint + category: PriceCategory_String [0..1] + mRID: AreaID_String +Price + measurementType: AnalogType_String [0..1] + direction: PriceDirection_String [0..1] + name: String [0..1] + position: Position_Integer [0..1] + minValue: ESMP_Float [0..1] 0..* + quality: Quality_String [0..1] + mRID: AnalogID_String [0..1] related to specific business + quantity: Decimal [0..1] +Price + name: String [0..1] + secondaryQuantity: Decimal [0..1] +Domain 0..* +Domain 0..* + normalValue: ESMP_Float [0..1] 0..* +TimeSeries 0..* + positiveFlowIn: ESMPBoolean_String [0..1] + unitMultiplier: UnitMultiplier [0..1] «ACC» + unitSymbol: UnitSymbol [0..1] +Price TimeSer ies

processes are derived 0..* + businessType: BusinessKind_String [0..1] «ACC» +Measurements 0..* +Quantity + cancelledTS: ESMPBoolean_String [0..1] Auction «ACC» + curveType: CurveType_String [0..1] +Auction +Quantity Qua ntity 0..* + description: String [0..1] + allocationMode: AllocationMode_String [0..1] «ACC» + mRID: ID_String [0..1] 0..* + cancelled: ESMPBoolean_String [0..1] AggregateNode 0..* + quality: Quality_String [0..1] + name: String [0..1] + category: Category_String [0..1] + quantity: Decimal [0..1] + mRID: MeasurementPointID_String [0..1] +Quantity + mRID: ID_String [0..1] + type: String [0..1] + objectAggregation: ObjectAggregationKind_String [0..1] + product: EnergyProductKind_String [0..1] + paymentTerms: PaymentTerms_String [0..1] 0..* +AggregateNode 0..* + version: ESMPVersion_String [0..1] + rights: RightsKind_String [0..1] +Detail_Quantity 0..* + type: AuctionKind_String [0..1] ▪ Classes and associations from «ACC» RegisteredResource +Period 0..* + description: String [0..1] «ACC» +Period + mRID: ResourceID_String [0..1] +RegisteredResource Time_Period + name: String [0..1] 0..* the CIM are restricted, thus + timeInterval: ESMP_DateTimeInterval 0..* +MarketObjectStatus 0..*

+Reason 0..* +Reason 0..* +MarketObjectStatus «ACC» MarketObjectStatus «ACC» +Reason 0..1 improving ease of +Reason + status: Status_String Rea son 0..* +PSRType 0..1 +Reason «ACC» 0..* + code: ReasonCode_String Series_Period +Period «ACC» + text: ReasonText_String [0..1] 0..* M ktP SRTy pe +Point + resolution: Duration 0..* +MktPSRType + timeInterval: ESMP_DateTimeInterval + psrType: PsrType_String implementation and cost 1..* +TimeSeries 0..* +PSRType 0..1 0..* «ACC» +PowerSystemResources 0..* +Location 0..1 +PowerSystemResources 0..1 +FlowDirection FlowDirection +FlowDirection «ACC» «ACC» efficiency. +Location + direction: DirectionKind_String «ACC» 0..1 0..1 +EquipmentContainer MktGeneratingUnit Loca tion VoltageLevel 0..1 0..1 + mRID: ResourceID_String [0..1] + mRID: String [0..1] +Point + highVoltageLimit: ESMP_Voltage + name: String [0..1] + name: String [0..1] + nominalP: ESMP_ActivePower [0..1] 0..*

«ACC» BidTimeSeries +ConstraintDuration 0..* + blockBid: ESMPBoolean_String [0..1] +Currency_Unit 0..1 «ACC» + direction: DirectionKind_String [0..1] ConstraintDuration «ACC» + divisible: ESMPBoolean_String [0..1] + duration: Duration [0..1] Currency_Unit + linkedBidsIdentification: ID_String [0..1] + type: String [0..1] + minimumActivationQuantity: Decimal [0..1] + name: CurrencyCode_String + stepIncrementQuantity: Decimal [0..1]

+MarketAgreement 0..* +Measurement_Unit 0..* «ACC» «ACC» MarketAgreement +Measurement_Unit Measure_Unit + createdDateTime: ESMP_DateTime [0..1] 0..1 + name: MeasurementUnitKind_String + mRID: ID_String [0..1] + type: CapacityContractKind_String [0..1]

© Copyright RTE 2019 ESMP Key Features

➔ESMP provides a unique common language that is reusable.

➔ESMP proposes a set of messages that are easily hands-on. The messages are precise, comprehensive and interoperable. They promote the responsibility of each sender on the exactitude of the message content.

➔Each standards are formalized by the users, and defined through an implementation guide.

➔Within ESMP, the creation and the normalization of a profile can be quickly performed, and accelerated by the use of open-source standard tools (CIMContextor and CIMSyntaxgen). This ensures ease of implementation, cost- efficiency and technical performance.

© Copyright RTE 2019 Creation of a profile within IEC 62325

▪ Definition of CIM components for Market in part 301

▪ Creation of a ESMP (European Style Market Profile) in part 351, containing all the ACCs: it is based on differents classes from CIM: 61968-11, 61970-301 and 62325-301

▪ Creation of contextual models (ABIEs) and assembly models (MBIE) in relation to specific business processes in parts 451-x : o Acknowledgement 451-1 o ESS 451-2 o ECAN 451-3 o EAR 451-4 o …

▪ Two main documents describe the process: Rules defined in IEC 62361-100 ❖ IEC 62325-450: Framework for energy market communications - Part 450: Profile and context modelling rules

ACC: aggregate core component ❖ IEC 62361-100: IEC TC57 XML Naming and Design Rules for ABIE: aggregate business information entity MBIE: message business information entity CIM Profiles to XML Schema Mapping © Copyright RTE 2019 ESMP Generic Profiling Methodology

• Identify the overall context and the business process 1

• Identify the roles and specify the business use cases Harmonized Role Model, use cases 2

• Identify and model the business process Implementation Guide, Sequence Diagram 3

• Define the business objects and their attributes Data Model, Core components 4

• Describe the dependancy tables and the codes used 5 Code List, Dependency Tables

XSD • Define the file formats The standard formats are in XSD but can be easily 6 transposed into other technical formats (JSON, CSV, etc)

The methodology is reliable, robust, and comprehensive and lays on a complete definition of business use cases and sequence diagrams © Copyright RTE 2019 Specific market business processes

class Schedule assembly model

«MBIE» Schedule_MarketDocument

+ mRID: ID_String Examples of business processes + revisionNumber: ESMPVersion_String + type: MessageKind_String + process.processType: ProcessKind_String + process.classificationType: ClassificationKind_String + sender_MarketParticipant.mRID: PartyID_String derived from the ESMP: + sender_MarketParticipant.marketRole.type: MarketRoleKind_String + receiver_MarketParticipant.mRID: PartyID_String + receiver_MarketParticipant.marketRole.type: MarketRoleKind_String + createdDateTime: ESMP_DateTime + schedule_Time_Period.timeInterval: ESMP_DateTimeInterval + domain.mRID: AreaID_String ▪ Capacity allocation and nomination (ECAN) + subject_MarketParticipant.mRID: PartyID_String [0..1] + subject_MarketParticipant.marketRole.type: MarketRoleKind_String [0..1] + matching_Time_Period.timeInterval: ESMP_DateTimeInterval [0..1]

▪ Scheduling (ESS) +TimeSeries 0..* «MBIE» TimeSer ies

+ mRID: ID_String + version: ESMPVersion_String + businessType: BusinessKind_String ▪ Accounting and Settlement (ESP) + product: EnergyProductKind_String + objectAggregation: ObjectAggregationKind_String + in_Domain.mRID: AreaID_String [0..1] + out_Domain.mRID: AreaID_String [0..1] + marketEvaluationPoint.mRID: MeasurementPointID_String [0..1] + in_MarketParticipant.mRID: PartyID_String [0..1] ▪ Transparency Processes + out_MarketParticipant.mRID: PartyID_String [0..1] + marketAgreement.type: CapacityContractKind_String [0..1] + marketAgreement.mRID: ID_String [0..1] + measurement_Unit.name: MeasurementUnitKind_String + curveType: CurveType_String [0..1] ▪ Short to Medium-Term Adequacy (SMTA) +Period 1..*

«MBIE» Series_Period

+ timeInterval: ESMP_DateTimeInterval + resolution: Duration

+Point 1..* +Reason 0..1

«MBIE» «MBIE» P oint +Reason Rea son

+ position: Position_Integer 0..* + code: ReasonCode_String + quantity: Decimal + text: ReasonText_String [0..1] © Copyright RTE 2019 IEC 62325 standards

IEC 62325 Current status Vote IEC 62325 301 IS Ed.2 2018-03-12 CIM for Market 450 IS Ed.1 2013-04-29 Methodology (profile & context modelling rules) 351 IS Ed.2 2016-06-15 ESMP 451-1 IS Ed.2 2017-01-30 Acknowledgment 451-2 IS Ed.1 2014-05-08 Market scheduling IS Ed.1 2014-07-09 451-3 AMD1 2017 Ed.1.1 2017-05-05 Transmission capacity 451-4 IS Ed.2 2017-04-11 Settlement and reconciliation 451-5 IS Ed.1 2015-02-017 Status request and problem statement

451-6 IS Ed.2 2018-05-08 Transparency 451-7 57/2064/NP Balancing 451-8 New Work Item Proposal HVDC Link 451-10 57/2087/CD Energy Consumption Data (My Energy Data) 503 IS Ed.1 2015-02-13 Data Exchange 504 TS Ed.1 2015-05-19 Web services

© Copyright RTE 2019 IEC 62325 open-source tools

➔To ease the creation of profiles, two open-source EnterpriseArchitect extensions are used :

❑ CIMCONTEXTOR for the IsBasedOn management (classes and associations) and PropertyGrouping (aggregation) in compliance with 62325-450

❑ CIMSYNTAXGEN for the generation of the XSD in compliance with IEC 62361-100 and for the IEC or ENTSO-E documentation

➔ CIMCONTEXTOR and CIMSYNTAXGEN are only tools; any other tools could be used as long as they comply with IEC 62325-450 (IS) and IEC 62361-100 (IS) © Copyright RTE 2019 5

Example : ESMP profiling applied to the Balancing Process Balancing Process profiling

➔ Contribution of RTE and experts from ENTSO-E CIM EG

➔ Supervised within TC 57 WG 16

➔ Strong contribution of Japan National Committee.

➔ Kick-off meeting and discussion about Balancing process in Tokyo in may 2019 at CRIEPI (Central Research Institute Of Electric Power Industry)

➔ The review of the 62325-451-7 Committee Draft is pending

© Copyright RTE 2019 Balancing Process: Overall Context and Business Use Case

The Balancing business process enables TSOs to ensure the maintenance of system frequency within a predefined stability range, and compliance with the amount of reserves needed with respect to the required quality.

❖ According to the European Balancing Guidelines, European common platforms will operate the exchange of balancing energy from frequency restoration reserves and replacement reserves .

❖ They shall apply a model with merit-order lists, in order to ensure cost- efficient activation of bids.

❖ Each European common platform will be mandated by the TSOs for the management and the exchange of standard products for balancing energy.

Within this use case, 3 main roles have been identified : ✓ TSOs (acting as LFC Operators) ✓ a MeritOrderList Responsible ✓ Balancing Service Providers (BSP) © Copyright RTE 2019 Balancing business process

© Copyright RTE 2019 Profiling Example: ReserveBid_MarketDocument

ReserveBid Contextual Model ReserveBid Assembly Model

© Copyright RTE 2019 6

RTE’s experience implementing ESMP Market Documents RTE’s policy on use of CIM Market Documents

❖ The French law promoted a standardized approach of market information exchanges. This was confirmed by the French National Regulation Authority (CRE). The main objective was to harmonize and to normalize the data exchanges between all Market Participants (TSO, traders, aggregators…)

❖ The use of a common model and of standard series facilitates any evolution in the future: it enables seamless integration and evolution of applications.

❖ RTE was a precursor and an early adopter of CIM market standards. The first standard series were adopted in 2004 (ENTSO EDI documents: EAR, ESS, Ack…)

❖ RTE has deliberately chosen to use CIM Market documents to ensure ease of use and interoperability: implementation guides are shared between all Market Participants.

© Copyright RTE 2019 Key Figures of French Electricity Market

❖ Number of Actors : ~ 110 Third Parties ❖ Volumetry of Market Documents exchanged by RTE every year :

Business Process CIM Market Documents per year Wholesales Markets ~ 150 000 Schedules received (ESS) (PEB Energy Blocks Exchanges) ~ 1 million ConfirmationReports or AnomalyReports sent Transmission and Capacity Allocation ~ 10 000 ECAN Market Documents exchanged Processes with other TSOs or platforms (CASC, CWE MC, JAO,CORESO…): auction specifications, bids, allocation results, Net Transfer Capacity,…

~ 100 000 Schedules exchanged (ESS)

Transparency Process ~ 175 000 Publication Market Documents sent (information sent to ENTSO-E Transparency Platform) load, generation, transmission, accepted offers, activated reserves, prices of reserved capacity, price of activated balancing reserves, unavailabilities, planned maintenances… Balancing Process Coming soon ! (TERRE, PICASSO and MARI projects) © Copyright RTE 2019 ESMP in a nutshell

❖ Fruitful methodology for standardizing Electricity Market exchanges ❖ Comprehensive coverage of the main business processes of European Electricity Market

❖ Impressive volume of CIM standard documents exchanged every year ❖ Large adoption within European Electricity Market: Over a thousand of stakeholders using the standards on a daily basis

❖ Expansion into other countries or areas: Soon adopted in Japan !

© Copyright RTE 2019 Thank you for your attention !