1 / 37

The Norwegian Elhub

The Norwegian Elhub. Standards, models and conceptual approach Per Øyvind Berg-Knutsen Statnett SF. The Norwegian Elhub http://www.elhub.no/ Standards, models and conceptual approach Per Øyvind Berg-Knutsen Statnett SF. Agenda. Introduction to the Elhub project

brier
Download Presentation

The Norwegian Elhub

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Norwegian Elhub Standards, models and conceptual approach Per Øyvind Berg-Knutsen Statnett SF

  2. The Norwegian Elhub http://www.elhub.no/ Standards, models and conceptual approach Per Øyvind Berg-Knutsen Statnett SF

  3. Agenda • Introduction to the Elhub project • Elhub and the Norwegian power utility market • Developing Elhub coremodels • Information assets developed • Transforming Elhub processes into standard messages • CIM-ebIX harmonisation • Harminization needs

  4. The current Norwegian powerutilitymarket Suppliers DSO's 1 A About 130 DSOs About 110 energysuppliers 2 B 3 C 4 D … … ~1M business processes per year (supplierchanges, customermoves, masterdata updates) About 2.8M meteringpoints

  5. The current Norwegian powerutilitymarket Suppliers DSO's 1 A About 130 DSOs About 110 energysuppliers 2 B 3 C 4 D … … ~1M business processes per year (supplierchanges, customermoves, masterdata updates) About 2.8M meteringpoints

  6. The future Norwegian powerutilitymarket "today everyone talks with everyone" "Everyone talks with Datahub" Suppliers DSO's Suppliers DSO's 1 A 1 A Metered values Master data End-user inform. Switching Moving Settlement data 2 B 2 B to 3 C 3 C 4 D 4 D HUB … … … … Elhub willinclude DATA storage in addition to being a communicationshub

  7. Key aspectsof Elhub processes Processing time Is data available? • Data processing: After-the-fact • Settlement and reconciliation • Reporting • Preliminary and final processing • Business processes: • Future (holding) • Current (beingexecuted) • Past (reversals) Yes No Preliminary processing Final processing Assumed or empiricalvalues Actualmeteredvalues

  8. Introduction to the Elhub project 2016: Elhub go-live • The Elhub is scheduled to go live on 1 October 2016 • The Elhub will be theauthoritativesourceonsuch data in themarket, althoughtheMetered Data Collectorwill be collectingthese from the meters • Statnett will be setting up a data hub (Elhub) for storing collectingmetered data from AMS meters to be installed in themarket by 2019 • The project has currently a public tender for an overall solution for the Elhub • The basis for all ofthefollowinginformation has beensharedwith and in themarket, although most in Norwegian • The considerationsleading up to decisions have beendeveloped in cooperationwithparties in themarket Data responsibilityshift from marketactors to Elhub 2019: AMR transformationcomplete Status: Public tender for solution Models and descriptionsexist in Norwegian Documentsdeveloped in cooperationwithmarketactors

  9. Regional cooperation and influence • Regional harmonization • HNR – Harmonised Nordic Retail market • NBS – Nordic Balance Settlement • Wide consensus oncommonmarket bases an processes • SE, DK, FI, NO • Denmark • Developed a data hub in 2012 • Cooperation provide Elhub with vital experiences • Business processsimilarities • Sweden, Finland • Starting up • Expectsignificant business processsimilarities

  10. Existing standards vs. Elhub needs Wholesalemarket area Market business process area Electric utility Customer area CIM functionalcoverage ENTSO-E functionalcoverage ebIXfunctional coverage

  11. Existing standards vs. Elhub needs Wholesalemarket area Market business process area Electric utility Customer area Elhub needs CIM functionalcoverage ENTSO-E functionalcoverage ebIXfunctional coverage ebIXfunctional coverage

  12. Elhub in a CIM context Elhub functional area National adaptations to ebIX Metered data collection Business processes ENTSO-E functionalcoverage ebIXfunctional coverage Data storage Settlement & Reconcil. Nordic Balance Settlement Calc. & Aggreg.

  13. Elhub modelcoverage and approach Elhub functional area • Top-downapproach • Required data for marketprocesses • Calculations • What, why, and to whichparties? • Resultinginformationassets: • Elhub base models • Market entitystatemodel • Data exchangemessages Metered data collection Business processes Data storage Settlement & Reconcil. Calc. & Aggreg.

  14. Elhub modelcoverage and approach Elhub functional area • Top-downapproach • Required data for marketprocesses • Calculations • What, why, and to whichparties? • Resultinginformationassets: • Elhub base models • Market entitystatemodel • Data exchangemessages Metered data collection Business processes Data storage Settlement & Reconcil. Calc. & Aggreg.

  15. Elhub base models • Rolemodel – definingroles and theirassociations • Information model – defininginternalinformationentities and theirlogicalrelations • Security model – definingkeyconsiderations for access to informationentities by different roles as defined in therolemodel

  16. Elhub base models • Rolemodel – definingroles and theirassociations • Information model – defininginternalinformationentities and theirlogicalrelations • Security model – definingkeyconsiderations for access to informationentities by different roles as defined in therolemodel

  17. Elhub base models • Rolemodel – definingroles and theirassociations • Information model – defininginternalinformationentities and theirlogicalrelations • Security model – definingkeyconsiderations for access to informationentities by different roles as defined in therolemodel

  18. Market partiesinvolved Actorsinvolved Market structureinformation Personal information

  19. Elhub base models • Rolemodel – definingroles and theirassociations • Information model – defininginternalinformationentities and theirlogicalrelations • Security model – definingkeyconsiderations for access to informationentities by different roles as defined in therolemodel

  20. - The Elhub Security Model • Meteredvalues = personal information • Names and identitiesmust be protected • Contractsarecommercially sensitive information • Third partiesexpected to becomekeyplayers • Solution: Twolevelsofaccess: • Implicitaccess • explicitaccess

  21. Elhub modelcoverage and approach Elhub functional area • Top-downapproach • Required data for marketprocesses • Calculations • What, why, and to whichparties? • Resultinginformationassets: • Elhub base models • Market entitystatemodel • Data exchangemessages Metered data collection Business processes Data storage Settlement & Reconcil. Calc. & Aggreg.

  22. Elhub modelcoverage and approach Elhub functional area • Top-downapproach • Required data for marketprocesses • Calculations • What, why, and to whichparties? • Resultinginformationassets: • Elhub base models • Market entitystatemodel • Data exchangemessages Metered data collection Business processes Data storage Settlement & Reconcil. Calc. & Aggreg.

  23. - Meteringpoint State Model • Aggregated from: • Physicalstate (meteringpoint) • Contractual binding to Grid Access Provider (DSO) • Contractual binding to Balance Supplier • Combined and simplified for Elhub purposes…

  24. State modelproperties • 2 (3) physicalstates • 3 contractualstates • 10 aggregatedstates • 31 statetransformations

  25. Logicalmarketprocessmessages • Processdescriptionsusing "processcomponents" • "Processcomponents" = logicalmessagestructures • per marketparty, with parameters • 46 processcomponents=> 36 physical Elhub messages • 133 combinations: Processcomponents and parameters

  26. Elhub modelcoverage and approach Elhub functional area • Top-downapproach • Required data for marketprocesses • Calculations • What, why, and to whichparties? • Resultinginformationassets: • Elhub base models • Market entitystatemodel • Data exchangemessages Metered data collection Business processes Data storage Settlement & Reconcil. Calc. & Aggreg.

  27. Elhub modelcoverage and approach Elhub functional area • Top-downapproach • Required data for marketprocesses • Calculations • What, why, and to whichparties? • Resultinginformationassets: • Elhub base models • Market entitystatemodel • Data exchangemessages Metered data collection Business processes Data storage Settlement & Reconcil. Calc. & Aggreg.

  28. Data exchangemessages • Message namesfollowebIX standard withextendeddescriptivenames • Messages arecomposed from two parts: Header and Payload • Header definemarket party and process bindings, including • Document Type Description (UN/CEFACT and ebIXcodes) • Business ProcessDescription (ebIXcodesonly) • Payloadcontainkey data elements, structuredintoxmlentites • 37 ebIXbasedentities used or adaptedfor nationaluse (not final)

  29. Examplexmlmessage: RequestStartOfSupply • Contents, e.g., type definitions and formats ofeachmessagearecurrentlybeingdefined in more detail, basedonebIX base classes • Definitions arebeingdevelopedusingSparx Enterprise Architect <?xml version="1.0" encoding="UTF-8"?> <rsm:RequestStartOfSupplyxmlns:rsm="un:unece:260:data:EEM" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="un:unece:260:data:EEM elhub_RequestStartOfSupply.xsd">             <rsm:HeaderEnergyDocument>                         <rsm:Identification>1234567890</rsm:Identification>                         <rsm:DocumentTypelistAgencyIdentifier="6">392</rsm:DocumentType>                                  <rsm:Creation>2014-02-19T09:30:47Z</rsm:Creation>                         <rsm:SenderEnergyParty>                                    <rsm:IdentificationschemeAgencyIdentifier="9">9875673213456</rsm:Identification>                         </rsm:SenderEnergyParty>                         <rsm:RecipientEnergyParty>                                    <rsm:IdentificationschemeAgencyIdentifier="9">1223323131312</rsm:Identification>                         </rsm:RecipientEnergyParty>             </rsm:HeaderEnergyDocument>             <rsm:ProcessEnergyContext>                         <rsm:EnergyBusinessProcesslistAgencyIdentifier="260">E03</rsm:EnergyBusinessProcess>                         <rsm:EnergyBusinessProcessRolelistAgencyIdentifier="6">DDQ</rsm:EnergyBusinessProcessRole>                         <rsm:EnergyIndustryClassification>23</rsm:EnergyIndustryClassification>             </rsm:ProcessEnergyContext>             <rsm:PayloadMPEvent>                         <rsm:StartOfOccurrence>2014-03-01T00:00:00Z</rsm:StartOfOccurrence>                         <rsm:MeteringPointUsedDomainLocation>                                    <rsm:IdentificationschemeAgencyIdentifier="9">570987465325465781</rsm:Identification>                         </rsm:MeteringPointUsedDomainLocation>                         <rsm:BalanceResponsibleInvolvedEnergyParty>                                    <rsm:IdentificationschemeAgencyIdentifier="9">5983675234543</rsm:Identification>                         </rsm:BalanceResponsibleInvolvedEnergyParty>                         <rsm:BalanceSupplierInvolvedEnergyParty>                                    <rsm:IdentificationschemeAgencyIdentifier="9">3456775654441</rsm:Identification>                         </rsm:BalanceSupplierInvolvedEnergyParty>                     </rsm:PayloadMPEvent> </rsm:RequestStartOfSupply>

  30. CIM-ebIXharmonisation • Levels of harmonization: • Market framework (legal and regulatory) • Market models and -entity states • Overall processes and sequences

  31. Key model development considerations Regulatory Processes& calculations Market structure Privacy and security Market Performance Message content Standards

  32. Questions? Per Øyvind Berg-Knutsen Architect, Elhub project / Principal at DevoteamConsulting (per.oyvind.berg.knutsen@devoteam.com)

More Related