Confirmation Levels and Data Examples for BPS Discussion

This content provides detailed information on levels of confirmation and working examples for discussions related to Business Process Solutions (BPS). It includes examples of base data sets, upstream and downstream pipe locations, and parties involved in the confirmation process. The explanation covers how quantities are confirmed, scheduled, and cuts are applied by both upstream and downstream pipes based on contract priorities and ranks.

• Confirmation
• BPS
• Data Examples
• Upstream Pipe
• Downstream Pipe

andr_677 Follow

Uploaded on Sep 23, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. CONFIRMATIONS Levels of Confirmation Working Example for BPS discussion

2. Point of view for discussion Upstream Pipe Downstream Pipe Location

3. Base Example Sample Data for Confirmations examples Base Data Set Upstream Pipe transactions Downstream Pipe Transactions Dn Pkg ID Up Pkg ID SR SRK Pkg ID Dn Pty Dn K Qty SR SRK Pkg ID Up Pty Up K Qty A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100

4. First Level One Party Upstream Party or Downstream Party If Downstream Pipe is requesting the confirmation Then Downstream pipe provides that pipeline s upstream party and requested quantity information to the upstream pipe. This may mean that the downstream party has to sum across more than one of their service requesters to accumulate the quantity to the upstream party level Upstream Pipe confirms the quantities at the requested level Upstream pipe matches the provided upstream parties and quantities to the service requesters on Upstream pipe. After confirming, Upstream pipe uses the confirmed quantities to schedule upstream pipe. If there are any reductions, upstream pipe uses its contract priorities and ranks to determine how to apply the cuts to each service requester The parties selected for cut by Upstream Pipe are now used by Downstream Pipe to make corresponding cuts Downstream Pipe cuts will use the tariff terms and shipper ranks for determining which transactions are cut.

5. First level One Party First Level - One Party Base Data Set Upstream Pipe transactions Downstream Pipe Transactions REQUESTED INFO (from downstream pipeline point of view) Up Party SR SRK Pkg ID Dn Pty Dn K Dn Pkg ID Qty SR SRK Pkg ID Up Pty Up K Up Pkg ID Qty Qty A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100 A B 1000 200

6. First level One Party Matches? Party Quantities Match! How to determine which of blue goes to A/B? And Red to A/B? What pipeline rules solve this? First Level - One Party Base Data Set Upstream Pipe transactions Downstream Pipe Transactions REQUESTED INFO (from downstream pipeline point of view) Up Party SR SRK Pkg ID Dn Pty Dn K Dn Pkg ID Qty SR SRK Pkg ID Up Pty Up K Up Pkg ID Qty Qty A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100 A B 1000 200

7. Pipeline rule solutions Since Upstream Party A was delivering gas to multiple parties on the downstream pipeline, then downstream pipeline must have rules in place to determine how to split any reductions for Upstream Party A across downstream pipeline s shippers. After determining the shipper split, then downstream party can use contracts, ranks or other methods to distribute any cuts. Upstream pipeline now knows the quantities for each of their shippers and, if any cuts apply, can use upstream pipeline s methods to distribute them.

8. Second Level Two Parties Upstream Party and Downstream Party If Downstream Pipe is requesting the confirmation Then Downstream pipe provides the upstream party/service requester combination and requested quantity for each combination to the upstream pipe Downstream pipe determines this by summarizing the nominations at the confirmation location to this level of detail Upstream Pipe confirms the quantities at the requested level Upstream pipe matches the upstream party/ service requester combinations and quantities to the summarized service requester/downstream parties listed for the shippers on Upstream pipe. After confirming, Upstream pipe uses the confirmed quantities to schedule upstream pipe. If there are any reductions, upstream pipe uses its contract priorities and ranks to determine the cuts within the upstream party/service requester combination The parties selected for cut by Upstream Pipe are now used by Downstream Pipe to make corresponding cuts Downstream Pipe cuts will use the tariff terms and shipper ranks for determining which transactions are cut.

9. Second Level - Two Parties Second Level - Two Parties Base Data Set Upstream Pipe transactions Downstream Pipe Transactions REQUESTED INFO (from downstream pipeline point of view) Dn Pkg ID Up Pkg ID SR SRK Pkg ID Dn Pty Dn K Qty SR SRK Pkg ID Up Pty Up K Qty Up Pty SR Qty A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100 A A B B Blue Red Blue Red 600 400 100 100

10. Second Level - Two Parties Matches? All Party Quantities Match! Second Level - Two Parties Base Data Set Upstream Pipe transactions Downstream Pipe Transactions REQUESTED INFO (from downstream pipeline point of view) Dn Pkg ID Up Pkg ID SR SRK Pkg ID Dn Pty Dn K Qty SR SRK Pkg ID Up Pty Up K Qty Up Pty SR Qty A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100 A A B B Blue Red Blue Red 600 400 100 100

11. Second Level Now pipeline looks at all of the contracts nominated for A/Blue and determines which contract to fill first (Firm, IT, other rules). Then pipeline looks at all of the nominations related to the first contract filled and uses shipper provided ranks to determine which to fill first. Currently, the Service Requester is MA in the confirmations dataset.

12. Third Level Two contracts Up Party + Up Contract and Down Party + Down Contract If Downstream Pipe is requesting the confirmation Then Downstream pipe provides the up party + up contract/ service requester + service requester contract combination and requested quantity for each combination to the upstream pipe Downstream pipe determines this by summarizing the nominations at the confirmation location to this level of detail Upstream Pipe confirms the quantities at the requested level Upstream pipe matches the up party + up contract/service requester + service requester contract combinations and quantities to the same summarized level listed for the transactions on Upstream pipe. After confirming, Upstream pipe uses the confirmed quantities to schedule upstream pipe. If there are any reductions, upstream pipe uses its contract priorities and ranks to determine the cuts within the up party + up contract/service requester + service requester contract combination The contracts selected for cut by Upstream Pipe are now used by Downstream Pipe to make corresponding cuts Downstream Pipe cuts may be to firm contracts selected by Upstream Pipe processes

13. Third Level Two Contracts Base Data Set Upstream Pipe transactions Downstream Pipe Transactions REQUESTED INFO (from downstream pipeline point of view) Dn Pkg ID Up Pkg ID SR SRK Pkg ID Dn Pty Dn K Qty SR SRK Pkg ID Up Pty Up K Qty Up Pty Up K SR SR K Qty A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100 A A A A A A A A B B A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 Blue blue red red red blue blue red blue red blue1 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 200 200 100 100 100 100 100 100 100 100

14. Third Level Two Contracts Matches? Base Data Set Upstream Pipe transactions Downstream Pipe Transactions REQUESTED INFO (from downstream pipeline point of view) Dn Pkg ID Up Pkg ID SR SRK Pkg ID Dn Pty Dn K Qty SR SRK Pkg ID Up Pty Up K Qty Up Pty Up K SR SRK Qty A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100 A A A A A A A A B B A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 Blue blue red red red blue blue red blue red blue1 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red1 200 200 100 100 100 100 100 100 100 100

15. Third Level Since confirming party has determined the quantity for each contract, then the pipeline s rules of filling the firm transportation first will not apply. Ranks will be used when multiple nominations apply for a upstream party + upstream contract/service requester + service requester contract combination.

16. Fourth Two package IDs Up Party + Up Contract + Up Package and Down Party + Down Contract + Down Package If Downstream Pipe is requesting the confirmation Then Downstream pipe provides the up party + up contract + up package/service requester + service requester contract + package ID combination and requested quantity for each combination to the upstream pipe Downstream pipe determines this by summarizing the nominations at the confirmation location to this level of detail Upstream Pipe confirms the quantities at the requested level Upstream pipe matches the up party + up contract + up package/service requester + service requester contract + package ID combinations and quantities to the same summarized level listed for the transactions on Upstream pipe. After confirming, Upstream pipe uses the confirmed quantities to schedule upstream pipe. If there are any reductions, upstream pipe uses its contract priorities and ranks to determine the cuts within the up party + up contract + up package/service requester + service requester contract + package ID combination The line items selected for cut by Upstream Pipe are now used by Downstream Pipe to make corresponding cuts Only transactions where the package ID matches or there is no package id (therefore null matches) are confirmed

17. Fourth Level Two Package IDs Base Data Set Upstream Pipe transactions Downstream Pipe Transactions Requested Info: Dn Pkg ID SR SRK Pkg ID Dn Pty Dn K Qty SR SRK Pkg ID Up Pty Up K Up Pkg ID Qty (from downstream pipeline point of view) blue1 987 blue1 876 blue2 765 blue2 654 red1 543 red2 432 red2 321321 blue1 8787 blue2 9898 red1 909 blue1 5454 red1 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123 234 345 456 567 123123 234234 2323 3434 4545 1212 6565 blue blue blue blue red red red blue blue red blue red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 321321 8787 9898 909 5454 2121 100 100 100 100 100 100 100 100 100 100 100 100 blue blue blue blue red red red blue blue red blue red A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100

18. Fourth Level Two Package IDs Matches? Base Data Set Upstream Pipe transactions Downstream Pipe Transactions Requested Info: Dn Pkg ID SR SRK Pkg ID Dn Pty Dn K Qty SR SRK Pkg ID Up Pty Up K Up Pkg ID Qty (from downstream pipeline point of view) blue1 987 blue1 876 blue2 765 blue2 654 red1 543 red2 432 red2 321321 blue1 8787 blue2 9898 red1 909 blue1 5454 red1 2121 A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A1 A2 A2 A2 B1 B1 123blue 234blue 345blue 456blue 567red 123123red 234234red 2323blue 3434blue 4545red 1212blue 6565red blue1 blue1 blue2 blue2 red1 red2 red2 blue1 blue2 red1 blue1 red2 987 876 765 654 543 432 100 100 100 100 100 100XXXXXXXX 100XXXXXXXX 100 100 100XXXXXXXX 100XXXXXXXX 100XXXXXXXX blue blue blue blue red red red blue blue red blue red A A A A A A A A A A B B A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 B2 B1 123 234 345 456 567 1234 234234 2323 3434 45454 12121 6565 100 100 100 100 100 100 100 100 100 100 100 100 321321 8787 9898 909 5454 2121

19. Fourth Level Since the confirming party has confirmed at the package ID level, in most cases, the quantity is applied at the nomination level. If the shipper did not provide a package id then there may be summarized nomination quantities and the ranks may be used. Or, if one side provided package id s and the other side did not, then the quantity may be cut.