Corrected Workpaper 1 of Skipping Stone for November 9-10 WGQ BPS Meeting

Levels of Confirmation Examples and Questions

Pipeline to Pipeline Confirmation Information (Note that all information below is from perspective of Conf Requester)

Part A-1. Questions regarding Confirmation information exchanges involving Pathed Pipeline to Pathed Pipeline information exchange:

1)Do the below listed 2 examples (Example 1 is where the Conf Requester is contractually Delivering(D)and Example 2 where the Conf Requester is contractually Receiving (R)) characterize the data elements associated with the “level of confirmation” (based upon contractual flow direction) used between 2 pathed pipelines?

  1. If not, please explain.
  2. And; in so explaining, please identify those additional data elements you would consider “required” from your perspective (i.e., Mandatory (M) or Business Conditional (BC) and if applicable Sender’s Option (SO)).
  3. And, if there are still other data elements exchanged (their content not indicators) what are they; and if you are sending them as Mutually Agreed (MA) data elements, do you require them to be sent back to you?

2)Do the Conf Requesting PLs consider the Conf Party’s applicable condition for provision of contractual info (both Service Requester Contract and Up/DnStream Contract info) in the Conf Response by the Conf Party to be BC (i.e., the Conf Party must send it back to you (the Conf Requester)once you (the Conf Requester) has put contractual info in the Conf Request) or do you (the Conf Requester) consider such info in the Conf Response to be MA (i.e., regardless of whether it is in the Conf Request, the Conf Party may not echo it back)?

  1. Note that the EDI condition with respect to Conf Party returning the Conf Requester’s Service Requester Contract info is in fact MA.

3)Do the Conf Requesting PLs consider the Conf Party’s applicable condition for provision of Service Requester info) in the Conf Response by the Conf Party to be BC (i.e., the Conf Party must send it back to you (the Conf Requester) once you (the Conf Requester) has put your Service Requester info in the Conf Request) or do you (the Conf Requester) consider such info in the Conf Response to be MA (i.e., regardless of whether it is in the Conf Request, the Conf Party may not echo it back)?

  1. Note that the EDI condition with respect to Conf Party returning the Conf Requester’s Service Requester info is in fact MA.

Part A-2. Additional Questions regarding Confirmation information exchanges involving Pathed Pipeline to Pathed Pipeline information exchange:

1)Do the below listed 2 examples (Example 3 (Delivering)and Example 4(Receiving)) provide sufficient information exchange to accomplish confirmation (based upon contractual flow direction) if it were to be the default used between 2 pathed pipelines?

  1. If not, please explain.

Part B-1. Questions regarding Confirmation information exchanges involving Pathed Non-Threaded (PNT) Pipeline to PNT Pipeline information exchange:

1)Do the below listed 2 examples (Example 5(Delivering)and Example 6 (Receiving)) characterize the data elements associated with the “level of confirmation” (based upon contractual flow direction) used between 2 PNT pipelines?

  1. If not, please explain.
  2. And; in so explaining, please identify those additional data elements you would consider “required” from your perspective (i.e., Mandatory (M) or Business Conditional (BC) and if applicable Sender’s Option (SO)).
  3. And, if there are still other data elements exchanged (their content not indicators) what are they; and if you are sending them as Mutually Agreed (MA) data elements, do you require them to be sent back to you?

Part B-2. Additional Questions regarding Confirmation information exchanges involving PNTPipeline to PNT Pipeline information exchange:

1)Do the below listed 2 examples (Example 7(Delivering)and Example 8(Receiving)) provide sufficient information exchange to accomplish confirmation (based upon contractual flow direction) if it were to be the default used between 2 pathed pipelines?

  1. If not, please explain.

Part C-1.Questions regarding Confirmation information exchanges involving Pathed Pipeline to PNT Pipeline information exchange:

1)In the below, is a table into which data can be entered to identify (from the perspective of Pathed Pipelines in the Conf Requester Role) that data which they exchange with PNT Pipelines and that which they get back.

2)Example 9 is (Delivering) and Example 10 is (Receiving)

3)Also in the below, in the column that indicates NAESB Condition, place your condition (both as Sender of Conf Requests and as receiver of Conf Responses).

  1. Note if you have different flavors with different pipelines or different flavors when you are contractually receiving versus when you are contractually delivering , please copy the table and provide pertinent examples.

Confirmation Requesting Pipeline (Conf Rqstr) / Confirmation Responding Pipeline (Conf Party)
NAESB / Pipeline A / NAESB / Pipeline B
Condition / Data Elements / Content / Condition / Data Elements / Content
Example 9 / Contractual Direction / D / Contractual Direction / D
Example 9 / Service Requester / Code or Name / Service Requester / Code or Name
Example 9 / Service Requester Contract / A's K / Service Requester Contract / A's K
Example 9 / Quantity / XXX / Quantity / XXX
Example 9 / Dnstream Entity (i.e., Dnstream Service Requester) / Code or name / Dnstream Entity (i.e., Dnstream Service Requester) / Code or name
Example 9 / Dnstream Contract / B's K / Dnstream Contract / B's K
Example 9 / Other element 1 (Fill-in) / Other element 1 (Fill-in)
Example 9 / Other element 2 (Fill-in) / Other element 2 (Fill-in)
Example 9 / Other element 3 (Fill-in) / Other element 3 (Fill-in)
Example 10 / Contractual Direction / R / Contractual Direction
Example 10 / Service Requester / Code or Name / Service Requester / Code or Name
Example 10 / Service Requester Contract / A's K / Service Requester Contract / A's K
Example 10 / Quantity / XXX / Quantity / XXX
Example 10 / Upstream Entity (i.e., Upstream Service Requester) / Code or name / Upstream Entity (i.e., Upstream Service Requester) / Code or name
Example 10 / Upstream Contract / B's K / Upstream Contract / B's K
Example 10 / Other element 1 (Fill-in) / Other element 1 (Fill-in)
Example 10 / Other element 2 (Fill-in) / Other element 2 (Fill-in)
Example 10 / Other element 3 (Fill-in) / Other element 3 (Fill-in)

Part D-1. Questions regarding Confirmation information exchanges involving PNT Pipeline to Pathed Pipeline information exchange:

1)In the below, is a table into which data can be entered to identify (from the perspective of PNT Pipelines in the Conf Requester Role) that data which they exchange with Pathed Pipelines and that which they get back.

2)Example 11 is (Delivering) and Example 12 is (Recieving)

3)Also in the below, in the column that indicates NAESB Condition, place your condition (both as Sender of Conf Requests and as receiver of Conf Responses).

  1. Note if you have different flavors with different pipelines or different flavors when you are contractually receiving versus when you are contractually delivering, please copy the table and provide pertinent examples.

Confirmation Requesting Pipeline (Conf Rqstr) / Confirmation Responding Pipeline (Conf Party)
NAESB / Pipeline A / NAESB / Pipeline B
Condition / Data Elments / Content / Condition / Data Elments / Content
Example 11 / Contractual Direction / D / Contractual Direction / D
Example 11 / Service Requester / Code or Name / Service Requester / Code or Name
Example 11 / Service Requester Contract / A's K / Service Requester Contract / A's K
Example 11 / Quantity / XXX / Quantity / XXX
Example 11 / Dnstream Entity (i.e., Dnstream Service Requester) / Code or name / Dnstream Entity (i.e., Dnstream Service Requester) / Code or name
Example 11 / Dnstream Contract / B's K / Dnstream Contract / B's K
Example 11 / Other element 1 (Fill-in) / Other element 1 (Fill-in)
Example 11 / Other element 2 (Fill-in) / Other element 2 (Fill-in)
Example 11 / Other element 3 (Fill-in) / Other element 3 (Fill-in)
Example 12 / Contractual Direction / R / Contractual Direction
Example 12 / Service Requester / Code or Name / Service Requester / Code or Name
Example 12 / Service Requester Contract / A's K / Service Requester Contract / A's K
Example 12 / Quantity / XXX / Quantity / XXX
Example 12 / Upstream Entity (i.e., Upstream Service Requester) / Code or name / Upstream Entity (i.e., Upstream Service Requester) / Code or name
Example 12 / Upstream Contract / B's K / Upstream Contract / B's K
Example 12 / Other element 1 (Fill-in) / Other element 1 (Fill-in)
Example 12 / Other element 2 (Fill-in) / Other element 2 (Fill-in)
Example 12 / Other element 3 (Fill-in) / Other element 3 (Fill-in)

1