1 / 22

Task Force API Accounting Process Implementation

Task Force API Accounting Process Implementation. Usage of Accounting process for different topologies V1.0, 14.09.2010.

york
Télécharger la présentation

Task Force API Accounting Process Implementation

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. Task Force API Accounting Process Implementation Usage of Accounting process for different topologies V1.0, 14.09.2010

  2. Use of T-, W-, Z- and local Code in the„Implementation Guide Accounting and Settlement Process”and consideration of special cases:- tie-line with three ends- coupling/ maintenance bus bar

  3. Content 1. Use of EIC-Codes and local Codes in MVD und EAR-Documents 2. Example of exchange of MVD und EAR 3. Special case: tie-lines with three ends 4. Special case: coupling/ maintenance bus bar

  4. 1 Use of EIC-Codes and local Codes in MVD und EAR-Documents

  5. EAR doc Process overview MVD doc USD doc The UCTE Accounting and Settlement pyramid

  6. The UCTE Accounting and Settlement process: Provided documents The UCTE Accounting and Settlement process is based on the following documents 1. Measurement Value Document (MVD) used for the verification of Accounting Point Relevant data on meter data level: message types SOMA and (SOVM: only for internal use, no data exchange with neighboring TS0) Identification of Accounting Point Relevant data by official10T-Code for tie-lines, (identification of optional additional meter data by locally assigned code or localZ-Code for meters) 2. Energy Account Report (EAR) used for the matching of the Accounting Point data on accounting data level:message type SOAM for matching between TSO and SOVA for agreed values for exchange via Publication Framework Identification of Accounting Point data by official10Z-Code for accounting point 3. UCTE Settlement Report (USR) used for the information of the UCTE Parties about the Settlement results:message types CBSR and CASR Identification of Accounting Point data by official10Z-Code for accounting point

  7. Identified by an local Code for meters Identified by an EIC T Code Use of Meter Measurement data in MVD document

  8. Local Codes in order to identify meters • See IG Accounting: Page 19 -21, line 410 - 462,especially line 460: use of MVD Mandatory: 10-T-code best „composition“ of meter data Optional: Local Code for main meter Optional: Local Code for back-up meter

  9. Explanation to page 6 Accounting Point Relevant data shall (must) (mandatory) be exchanged in MVD (10T-Code).These are the meter data , that are necessary in order to calculate the Accounting point, hence accounting point relevant. If for example the meter data of both ends of a tie.line are used for the calculation of the accounting point (e.g. Accounting point is on middle of tie-line or on border point), the meter data of boths ends of the tie-line are accounting relevant data and have to be exchanged.. Each partner is sending in MVD the best “composition” (mandatory with 10-T-Code) of the available meter data from his station (Main meter, back-up meter) (see IG Accounting line ???). In normal cases the best collection of meter data is the pure main meter. In addition to the best “composition” of meter data (mandatory with 10-T-Code) in the MVD the original data from main meter and back-up meter or tele-mesurement etc. (assigned with a local code in the MVD) can (optional) be exchanged in the MVD in order to make transparent, how the best “composition” of meter data was made.

  10. Excerpt of IG Accounting Excerpt of IG Accounting: Line 429: In the UCTE process to establish the Accounting Point Relevant data the following rules for identification are to be used: Line 431 · Accounting Point Relevant data are identified with an ENTSO-E assigned EIC "10T„-code. Line 433 · Meter Measurement data are identified with a locally assigned code or an EIC "Z“-code issued by the Local Issuing Office.

  11. Abstract MVD and EAR MVD (for SOMA) Accounting Point Relevant data are identified with an ENTSO-E assigned EIC "10T„-code. (Mandatory) Meter Measurement data are identified with a locally assigned code or an EIC "Z„- code issued by the Local Issuing Office. (optional) EAR (for SOAM) Agreed Accounting Point data are identified with an ENTSO-E assigned official EIC "10Z„-code. (Mandatory)

  12. 2 Examples MVD-/EAR-Document

  13. Measurement Value Document (MVD) Tie-line 10T-DE-FR-00005A TSO B TSO A Available data Available data Accounting point: 10Z-DE-FR-000050 main, back-up local code main, back-up local code SOMA in MVD Mandatory Accounting relevant data in official T-Code „10T-DE-FR-00005A“ for tie-line Accounting relevant data in official T-Code„10T-DE-FR-00005A“for tie-line Optional Main and/or back-up meter data withlocal Code from TSO A Main and/or back-up meter data with local Code from TSO B

  14. Energy Account Report (EAR) TSO B TSO A Available data after receiving SOMA from TSO A Available data after receiving SOMAfrom TSO B Accounting point: 10Z-DE-FR-000050 Accounting point relevant data Accounting point relevant data calculation of accounting point by means of the accounting relevant data from TSO A and TSO B calculation of accounting point by means of the accounting relevant data from TSO A and TSO B official 10Z-Code for accounting point SOAM in EAR Accounting relevant data in official 10Z-Code „10Z-DE-FR-00005A“ Accounting relevant data in official 10Z-Code „10Z-DE-FR-00005A“

  15. Energy Account Report (EAR) National exception: 10T-DE-DE-02701S TSO B TSO A Accounting point: 10Z-DE-DE-02701I TSO A TSO B Remote reading local Code Back-up main Accounting relevant dataofficial 10Z-Code „10Z-DE-DE-02701I“ Accounting relevant data official10Z-Code „10Z-DE-DE-02701I“

  16. 3 Special case: Tie-line with 3 ends

  17. Tie-line with 3 ends (1)(Sum of accounting point) 10T-DE-DE-04710H TSO B TSO A Local Code Meter C Accounting point 1 Note: only possible if bothaccounting point are at one TSO Local Code Meter D Accounting point 2 MVD: • the accounting relevant data is sum of meter C and D with official 10T-Code„10T-DE-DE-04710H“ • optional meter data of meter C with local code • optional meter data of meter D with local code EAR: • Accounting data is sum of meter C and D with official 10Z-Code „10Z-DE-DE-047107“

  18. Note: this is possible , if accounting point 1 is at TSO B and accounting point 2 is at TSO C(!). Tie-line with 3 ends (2) (split into two lines) Line 1: 10T-DE-DE-04710H TSO B TSO A Local Code Meter C Accounting point 1 Line 2: 10T-DE-DE-04711F Local Code Meter D Accounting point 2 MVD: • accounting relevantdata of point 1 with official 10T-Code „10T-DE-DE-04710H“ • accounting relevantdataof point 2withoffical 10T-Code „10T-DE-DE-04711F“ EAR: • accounting data with official 10Z-Code „10Z-DE-DE-047107“ • accounting data with offical 10Z-Code „10Z-DE-DE-047115“

  19. 4 Special case: Coupling / maintenance bus bar

  20. Coupling/ maintenance bus bar (1) 10T-DE-DE-047092 TSO B TSO A Donau-West z.B. „100“ Accounting point Metering US Z Z „100“ „0“ SS2 SS1 Coupling Donau-West

  21. Coupling/ maintenance bus bar (2) 10T-DE-DE-047092 TSO B TSO A Donau-West Accounting point Metering Accounting Accounting point relevant data in MVD with 10T Code. Optional exchange of coupling data in MVD with local Code

More Related