1 / 12

Task Force API Accounting Process Implementation

Task Force API Accounting Process Implementation. Automatic running parts of the ENTSO-E CE accounting process V1.3, 19.11.2010. Accounting process sequence flow. File name convention. October 9, 2014. 3. Automatic running part of Acc. Process Sequence 2 respectively 4:.

elwyn
Download Presentation

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 APIAccounting Process Implementation Automatic running parts of the ENTSO-E CE accounting process V1.3, 19.11.2010

  2. Accounting process sequence flow File name convention October 9, 2014 3

  3. Automatic running part of Acc. Process Sequence 2 respectively 4: • Latest at Gate Closure the meter data validation system will automatically send the SOMA document if it was not already sent before. (Seq. 2+4). As an option a SO can also send the SOMA document before 10:00 am, when available. • Note: If at “Cut Off Time” no matched data are provided, the CB and CC will use ZERO values instead of the mismatching data in the following settlement process October 9, 2014 4

  4. Accounting process sequence flow File name convention October 9, 2014 5

  5. Automatic running part of Acc. Process Sequence 3 respectively 5: • Once the SOMA is available the receiver will automatically validate the contend of the document against the associated limits, like fixed in the bilateral agreement, and will answer immediately with an automatic generated ACK (Seq. 3+5) (For more information please view the Ack-Document). If a limit is violated a negative ACK is send and the manual process starts.(Manuel process means: Looking for acceptable data. This can be with or without help of the neighboring SO). Once the problem is solved the automatic process continues. October 9, 2014 6

  6. Accounting process sequence flow File name convention October 9, 2014 7

  7. Automatic running part of Acc. Process Sequence 6: • Once an positive ACK (Seq. 3) was received and the associated SOMA message (if any) from the neighbor is available and agreed (Seq. 5), the SOVM message (containing the accounting relevant data) is assembled and send automatically (Seq. 6). October 9, 2014 8

  8. Accounting process sequence flow File name convention October 9, 2014 9

  9. Automatic running part of Acc. Process Sequence 7: • Once the SOVM message is received the accounting system automatic calculates the accounting point data, (Consideration of losses if bilateral agreed) generates the SOAM document and sends it to the relevant neighboring SO.Note 1: the SO are obliged to agree on accounting point data latest until “Cut Off Time”Note 2: If at “Cut Off Time” no matched data are provided, the CB and CC will use ZERO values instead of the mismatching data in the following settlement process October 9, 2014 10

  10. Accounting process sequence flow File name convention October 9, 2014 11

  11. Automatic running part of Acc. Process Sequence 8 and 9: • Immediately after the SOAM message is received, the matching SO will automatically match the contend of the document against his data. Once the matching has been performed a positive respectively negative ACK (Seq 8) will be send. If the data do not match the automatic process is interrupted and the manual process starts. (Manuel process means: Discover and solve the problem. Under normal circumstances data should match. Once the problem is solved the automatic process continues.) • Once a positive ACK (Seq. 8) on the SOAM message is received the SOVA (Seq. 9) message is generated and send. October 9, 2014 12

More Related