Mobile Bay Pipeline Company

Second Revised Volume No. 1

 Contents / Previous / Next / Main Tariff Index

Effective Date: 08/01/1998, Docket: RP98-329-000, Status: Effective

Third Revised Sheet No. 185 Third Revised Sheet No. 185 : Effective

Superseding: Superseding Second Revised Sheet No. 185

GENERAL TERMS AND CONDITIONS

(Continued)

1.3.17 If requested by a shipper or supplier on a transportation service

provider’s system, the transportation service provider should offer at

least one pool.

1.3.18 Deliveries from receipt points should be able to be delivered

directly into at least one pool and delivery points should be able

to receive quantities from at least one pool, excluding non-contiguous

facilities.

1.3.23 Ranking should be included in the list of data elements.

Transportation service providers should use service requester provider

rankings when making reductions during the scheduling process when

this does not conflict with tariff-based rules.

1.3.24 When used, Package ID should be supported for nominating, scheduling,

confirming, allocating , and invoicing (sales and purchase), and not

required for transportation invoicing.

1.3.25 Use of the Package ID is at the discretion of the service requester,

and if sent, should be accepted and processed by the service provider.

1.3.27 The key should be composed of: service requester contract (Service

Agreement), transaction type, upstream party, upstream contract (when

applicable), receipt location (as applicable), downstream party, (as

applicable) downstream contract (when applicable), delivery location

(as applicable), package ID, capacity type indicator (where mutually

agreed), service provider activity code (where mutually agreed). Upon

receipt by a service provider from a service requester of a

transaction whose key elements match those previously received by the

service provider from the service requester, the service provider

should then process the begin date/time and end date/time consistent

with the intentions of the standard 1.3.7 and then process the rest of

the transaction’s data elements consistent with the applicable

standards to determine the business results. When data is not

supplied (e.g. is not applicable, is not supported or is not mutually

agreed upon) the pertinent portion to the key would be determined to

be null.

1.3.28 For current in-kind fuel reimbursement procedures, fuel rates should

be made effective only at the beginning of the month.

1.3.29 For in-kind fuel reimbursement methods, Service Providers should not

reject a nomination for reasons of rounding differences due to fuel

calculation of less than 5 Dth.

1.3.30 For in-kind fuel reimbursement methods, Service Providers should

provide, if applicable, a fuel matrix for receipt and delivery point

combinations. The Service Requesters should not be responsible for

calculating and totaling fuel based on each zone or facility

traversed.

1.3.31 The transportation priority for fuel should be the same as the level

of service as the transaction to which it applies.