Click to edit title

Click to edit sub-title

Task Force APIAccounting Process ImplementationSOMA document validation processV1.0, 24.3.2011

9:01, Send TSO_A-SOMA V1

TSO A TSO B

Internal data collec- tion and validation

Data available

Data available

9:02, neg. ACK, Data not yet available

Assemble SOMA

Assemble SOMA

Validate SOMA=> but no data

9:20, Send TSO_B-SOMA V1

9:2x, pos. ACK on TSO_B-SOMA V1

Wait for TSO B

- Validate SOMA=> Everything OK

- Prepare SOMA V2 9:2x, Send TSO_A-SOMA V2 (content = TSO_A-SOMA V1) - Validate SOMA

=> Everything OK

TSO_B-SOMA done

TSO_A-SOMA done9:3x, pos. ACK on TSO_A-SOMA V2

Note: The used times are only for illustration purposed

Internal data collec- tion and validation

Possible SOMA validation process «good case»

9:19

9:00

9:01, Send TSO_A-SOMA V1

TSO A TSO B

Internal data collec- tion and validation

Data available

Data available

9:02, neg. ACK, Data not yet available

Assemble SOMA

Assemble SOMA

Validate SOMA=> but no data

9:20, Send TSO_B-SOMA V1

9:2x, pos. ACK on TSO_B-SOMA V1

Wait for TSO B

- Validate SOMA=> Everything OK

- Prepare SOMA V2 9:2x, Send TSO_A-SOMA V2 (content = TSO_A-SOMA V1)

9:2x+, neg. ACK, Data outside tolerance

- Validate SOMA=> Outside tolerance

- Analyse problem- ev. call TSO B- ev. adjust data- Prepare SOMA V3

TSO_B-SOMA done

Discuss problem

9:30, Send TSO_A-SOMA V3

Phone call

- Validate SOMA=> Everything OK

TSO_A-SOMA done9:3x, pos. ACK on TSO_A-SOMA V3

Note: The used times are only for illustration purposed

Internal data collec- tion and validation

Possible SOMA validation process «bad case»

9:19

9:00