310 likes | 490 Views
Syntax, Communication and Message Standard. Nordic Ediel Group. Nordic Balancing System. Syntax, Communication and Message Standard. NBS info day, April 29 th 2014. Syntax. Nordic Ediel Group. History. NEG is founded. Ediel Nordic Forum is founded (1995).
E N D
Nordic Ediel Group Nordic Balancing System Syntax, Communication and Message Standard NBS info day, April 29th 2014
Nordic Ediel Group History NEG is founded Ediel Nordic Forumis founded (1995) NEG Project for Nordic (TSO) Energy Market Model for data exchange (NEMM) (2008) NTC (2014) eSett Oy established (Dec. 2013) ebIX® is founded (2003) 1995 1998 2001 2004 2007 2010 2013 ETSO/TF-14 (2001) ENTSO-E/WG-EDI (2009) ebIX® starts Customer Switching project with Eurelectric(2006) ENTSO-E starts cooperationwith IEC (2010) Ediel starts participating in UN/CEFACT (1997) ebIX® starts cooperationwith IEC (2013) ebIX®, EFET and ENTSO-E Harmonisation Group is founded (2003)
UNA:+.? ' UNB+UNOC:3+1234567890123:14:….. UNH+1+MSCONS:D:96A:ZZ:E2NO6A' BGM+7+AAA000240+9+NA' DTM+137:200212101201:203' DTM+163:200211020000:203' DTM+164:200212030000:203' DTM+ZZZ:1:805' NAD+FR+987654321:NO3:82 …. Syntax Two alternatives: • EDIFACT • XML <rsm:Header> <rsm:Identification>AAA000240</rsm:Identification> <rsm:DocumentTypelistAgencyIdentifier="260">7</rsm:DocumentType> <rsm:Creation>2014-01-09T09:30:47Z</rsm:Creation> <rsm:SenderEnergyParty> <rsm:IdentificationschemeAgencyIdentifier="9">9876543210987</rsm:Identification> </rsm:SenderEnergyParty> <rsm:RecipientEnergyParty> <rsm:IdentificationschemeAgencyIdentifier="9">1234567890123</rsm:Identification> </rsm:RecipientEnergyParty> </rsm:Header>
Why XML • The Danish Datahub have already implemented XML documents based on ebIX® and ENTSO-E standards • Nord Pool Spot will offer XML interface spring 2014 • No existing alternative to XML for ENTSO-E documents • Most other markets (Banks, Health care, Transport…) has migrated, or has started to migrate to XML • NBS requires changes to all systems and changing syntax seems like a small additional cost Conclusion: • XML is the best choice for NBS message syntax
NBS requirements for means of communication • Same standard for all Nordic countries • Encryption (parts of the market) • Typically for bids to the different markets • Compression (XML are large) • The new formats will be notably bigger • Must handle both: • many-to-many communication (FI, NO, SE) • one-to-many communication (DK, i.e. datahub)
Possible protocols • SMTP • Used in Norway and Sweden today • FTP • Used in Finlandtoday • Web Services • Used in Denmark today • E.g. AS4 or ebMS 3.0 • Not seen as realistic without a central hub, hence not further elaborated • MADES • Astrong candidate for a common Nordic communication platform
MADES (MArket Data Exchange Standard) • General communication standard • based on web-services • developed by ENTSO-E to facilitate reliable and secure exchange of documents • Supports • Encryption • compression • Authentication • non-repudiation • Published by IEC as Technical Specification (2013) • The ECP (ENTSO-E Communication Platform) is free for the industry
Status • NBS has not yet made a decision regarding means of communication • Comments from the industry are welcomed!
NBS message exchangesBusiness Requirement Documentation • NBS has asked the Nordic Ediel Group (NEG) to specify the message exchanges related to NBS. This includes a set of Business Requirement Specifications (BRS): • BRS for NBS, version 1r4 (between NBS and market actors) • BRS for NBS, TSO/NPS communication, version 1r2(between NBS and TSO/NPS) • Overview of information exchange • sequence diagrams • Harmonised roles used in Nordic settlement • role model and definitions of roles • Process areas • UseCases, activity diagrams and process descriptions • Data view • Class diagrams and attribute usage
NBS message exchangesTechnical Documentation • NBS User Guide for XML documents • Detailed description of data elements, formats, codes…. • Example XML files • Aggregated_Data_per_MGA_for_Settlement_Responsible-E31-E44.xml • EAR-Example.xml • ESS-Schedule-Example.xml • ESS-Confirmation-Example.xml • Validated_Data_for_Settlement_for_Aggregator-E66-E44.xml • Aggregated_Data_per_Neighbouring_Grid_for_Settlement_Responsible-E31-E44.xml • Validated_Data_for_Settlement_for_Aggregator-MGA-E66-E44.xml • Common Nordic XML rules and recommendations • Acknowledgement process • Basic rules for dates, times and periods • …
NBS Scheduling PhaseExchange Load Profile Shares (before the delivery month) • Arrow 1 is not handled in the first version of NBS • Arrow 2 and 3 are published on web
NBS Scheduling Phase Report tradefrom Elspotand Elbas (before operational hour) • Green arrows are document in NBS BRS for TSO/NPScommunication • Blue arrows are documentedin other BRSs from NEG
NBS Scheduling Phase Report bilateral trade • Black arrows are documented in NBS BRS • Green arrows are document in NBS BRS for TSO/NPScommunication • Blue arrows are documentedin other BRSs from NEG
NBS Scheduling Phase Plan production • Green arrows are document in NBS BRS for TSO/NPScommunication • Blue arrows are documentedin other BRSs from NEG
NBS Scheduling Phase Report trade from Balance Regulation Market • Green arrows are document in NBS BRS for TSO/NPScommunication • Blue arrows are documentedin other BRSs from NEG
NBS Metering and Settlement PhaseExchange Metered data for End Customer billing • Blue arrows are documentedin other BRSs from NEG
NBS Metering and Settlement Phase Exchange metered datafor imbalance settlement (2 – 13 days after delivery day) • Black arrows are documented in NBS BRS • Red arrows are document in NBS BRS, but proposed removed form NBS BRSs (not part of NBS scope) • Arrow 10 will be published on web
NBS Metering and Settlement Phase Settle imbalance • Aggregated consumption per MGA will be further split into: • Interruptible consumption • Pumped • etc. • Blue arrows will be published on web • Black arrows are documented in NBS BRS
NBS Reconciliation Phase Reconcile (not part of the first phase of NBS) • Arrow 1 will be detailed by HNR • Arrow 2 is an internal dataflow within the DSO • Black arrows is not handled in the first version of NBS
Acknowledgements • NBS will use the ENTSO-E acknowledgement process • NBS will acknowledge all documents received • NBS expect an acknowledgement in return for all documents sent • The ENTSO-E acknowledgement document is simplified in comparison to the documents used today (CONTRL/APERAK) • One structure • Less detailed codes
The main processes and data exchanges have been specified, however some issues still remain • How to exchange master data (structure data), such as • MBA-MGA and MGA-MGA relations • Party information (IDs, responsibilities, roles, contacts …) • Address register • Test portal • Maintenance requests to ebIX® and ENTSO-E • Intermediate Nordic solutions will be used until/unless accepted by ebIX® and ENTSO-E • Specification of technical details • Identification schemes • Identification of Time Series • Rules for Direction, Delta value, signing convention
Links to documentation • www.nbs.coop • BRS for NBS, between NBS and market actors • www.ediel.org, Nordic Balance Settlement (NBS) • BRS for NBS, including flows outside of NBS • BRS for NBS, TSO/NPS communication • NBS User Guide for XML documents • Example XML files • www.ediel.org, Nordic TSO XML Project • Common Nordic XML rules and recommendations
Thank you for your kind attention! <?xmlversion="1.0" encoding="UTF-8"?> <ResponsibleForPresentation> <Name>Jan Owe</Name> <Email>jan.owe@svk.se</Email> <Company>Svenska kraftnät</Company> <Url>http://www.svk.se</Url> </ResponsibleForPresentation> <ResponsibleForPresentation> <Name>Jari Hirvonen</Name> <Email>jari.hirvonen@fingrid.fi</Email><Company>Fingrid</Company> <Url>http://www.fingrid.fi</Url> </ResponsibleForPresentation> <ResponsibleForPresentation> <Name>Ove Nesvik</Name> <Email>ove.nesvik@edisys.no</Email><Company>Edisys Consulting AS</Company> <Url>http://www.edisys.no</Url> </ResponsibleForPresentation>