1 / 4

SOMA Validation Process Implementation and Data Handling Scenarios

This document outlines the implementation of the SOMA validation process, detailing both a successful and a problematic case for internal data collection and validation. It covers the step-by-step procedures for handling data requests and the corresponding acknowledgments (ACK/neg. ACK) depending on the availability and quality of data. With timestamps provided for illustrative purposes, the document serves as a guide to ensure effective communication and data management between TSO A and TSO B.

noelle-mcdowell
Download Presentation

SOMA Validation Process Implementation and Data Handling Scenarios

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 SOMA document validation process V1.0, 24.3.2011

  2. TSO B TSO A Possible SOMA validation process «good case» Internal data collec- tion and validation Internal data collec- tion and validation Data available 9:00 9:01, Send TSO_A-SOMA V1 Assemble SOMA Validate SOMA=> but no data 9:02, neg. ACK, Data not yet available Wait for TSO B 9:19 Data available 9:20, Send TSO_B-SOMA V1 Assemble SOMA - Validate SOMA=> Everything OK - Prepare SOMA V2 9:2x, pos. ACK on TSO_B-SOMA V1 TSO_B-SOMA done 9:2x, Send TSO_A-SOMA V2 (content = TSO_A-SOMA V1) - Validate SOMA => Everything OK 9:3x, pos. ACK on TSO_A-SOMA V2 TSO_A-SOMA done Note: The used times are only for illustration purposed

  3. TSO B TSO A Possible SOMA validation process «bad case» Internal data collec- tion and validation Internal data collec- tion and validation Data available 9:00 9:01, Send TSO_A-SOMA V1 Assemble SOMA Validate SOMA=> but no data 9:02, neg. ACK, Data not yet available Wait for TSO B 9:19 Data available 9:20, Send TSO_B-SOMA V1 Assemble SOMA - Validate SOMA=> Everything OK - Prepare SOMA V2 9:2x, pos. ACK on TSO_B-SOMA V1 TSO_B-SOMA done 9:2x, Send TSO_A-SOMA V2 (content = TSO_A-SOMA V1) - Validate SOMA => Outside tolerance 9:2x+, neg. ACK, Data outside tolerance - Analyse problem- ev. call TSO B- ev. adjust data- Prepare SOMA V3 Phone call Discuss problem 9:30, Send TSO_A-SOMA V3 - Validate SOMA => Everything OK 9:3x, pos. ACK on TSO_A-SOMA V3 TSO_A-SOMA done Note: The used times are only for illustration purposed

More Related