Train and Truck Loading Sample Clauses

Train and Truck Loading. (a) Customer shall use reasonable efforts to coordinate the arrival of all Trucks and Non-Party Trains at the Terminals in accordance with the agreed Nominations. Provider shall use its commercially reasonable efforts to accommodate such adjustments to Arrival Times as Customer’s rail or truck transportation provider may reasonably request. Customer shall provide Provider with as much advance notice as possible with respect to any alteration to any Nomination, including any change in the proposed Arrival Time, Train or Truck size, and Tank Car or Truck dimensions. Customer shall additionally permit Provider to coordinate any alterations to an agreed Arrival Time directly with the applicable rail or truck transportation provider, as applicable. (b) In accordance with such agreed Arrival Times, Customer shall have the right to bring its Non-Party Trains and Trucks to the Terminals for purposes of loading and unloading, as applicable, Customer Hydrocarbons (in accordance with and to the extent agreed in accordance with the Agreement, including the Nomination provisions hereof). Provider shall use its commercially reasonable efforts to provide the Terminals Services, NGL Services or Crude Oil Loading Services, as applicable, with respect to such Customer Hydrocarbons in a timely manner. Customer shall use reasonable efforts to cause all Trucks and Non-Party Trains to depart from the Terminals in a timely manner following the applicable loading or offloading of such Nominated Customer Hydrocarbons. (c) Customer shall notify Provider of any Transportation Event as soon as possible, but in any event not less than one Business Day after the occurrence of such event. TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**).
Sample 1Sample 2See All (14)
AutoNDA by SimpleDocs

Related to Train and Truck Loading

  • Loading RPMG shall schedule the loading and shipping of all outbound corn oil purchased hereunder, but all labor and equipment necessary to load trucks and rail cars and other associated costs shall be supplied and borne by Producer without charge to RPMG. Producer shall handle the corn oil in a good and workmanlike manner in accordance with RPMG’s written requirements and normal industry practice. Producer shall maintain the truck and rail loading facilities in safe operating condition in accordance with normal industry standards and shall visually inspect all trucks and rail cars to assure (i) cleanliness so as to avoid contamination, and (ii) that such trucks and railcars are in a condition suitable for transporting the corn oil. RPMG and RPMG’s agents shall have adequate access to the Ethanol Facility to load Producer’s corn oil on an industry standard basis that allows RPMG to economically market Producer’s corn oil. RPMG’s employees shall follow all reasonable safety rules and procedures promulgated by Producer and provided to RPMG reasonably in advance and in writing. Producer shall supply product description tags, certificates of analysis, bills of lading and/or material safety data sheets that are applicable to all shipments. In the event that Producer fails to provide the labor, equipment and facilities necessary to meet RPMG’s loading schedule, Producer shall be responsible for all costs and expenses, including without limitation actual demurrage and wait time, incurred by RPMG resulting from or arising in connection with Producer’s failure to do so.

  • Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection. 2.1.1 Each Party, at its own expense, shall provide transport facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA selected by PNG.

  • Vessels (A) All of the vessels described in the Registration Statement, the General Disclosure Package and the Prospectus, except for the Contracted Vessels (each of which a Subsidiary has contracted to acquire), are owned directly by Subsidiaries); each of the vessels listed on Schedule F-1 (the “Owned Vessels”) hereto has been duly registered as a vessel under the laws and regulations and flag of the jurisdiction set forth opposite its name on Schedule F-1 in the sole ownership of the Subsidiary set forth opposite its name on Schedule F-1 and no other action is necessary to establish and perfect such entity’s title to and interest in such vessel as against any charterer or third party; each such Subsidiary has good title to the applicable Owned Vessel, free and clear of all mortgages, pledges, liens, security interests and claims and all defects of the title of record except for those liens arising under Credit Facilities, each as disclosed in the Registration Statement, the General Disclosure Package and the Prospectus, and such other encumbrances which would not, in the aggregate, result in a Material Adverse Effect; and each such Owned Vessel is in good standing with respect to the payment of past and current taxes, fees and other amounts payable under the laws of the jurisdiction where it is registered as would affect its registry with the ship registry of such jurisdiction except for failures to be in good standing which would not, in the aggregate, result in a Material Adverse Effect. Upon delivery to and acceptance by the relevant Subsidiary under the MoAs and the Newbuilding Contracts described in the Registration Statement, General Disclosure Package and Prospectus, each of the vessels listed on Schedule F-2 hereto and specified as being under contract (the “Contracted Vessels”) for delivery to and acceptance by a Subsidiary will be duly registered as a vessel under the laws of the jurisdiction set forth opposite its name on Schedule F-2, or under the laws of a generally accepted shipping industry flag jurisdiction, in the sole ownership of the Subsidiary set forth opposite its name on Schedule F-2, on such date, each such Subsidiary will have good title to the applicable Contracted Vessel, free and clear of all mortgages, pledges, liens, security interests, claims and all defects of the title of record, except for any mortgages, pledges, liens, security interests or claims arising from any financing arrangement which the Company or Subsidiary may enter to finance the acquisition of the Contracted Vessel and except such encumbrances which would not, in the aggregate, result in a Material Adverse Effect; and each such Contracted Vessel will be in good standing with respect to the payment of past and current taxes, fees and other amounts payable under the laws of the jurisdiction where it is registered as would affect its registry with the ship registry of such jurisdiction. (B) Each Owned Vessel is, and the Company will use reasonable commercial efforts to ensure that each Contracted Vessel will be, operated in compliance with the rules, codes of practice, conventions, protocols, guidelines or similar requirements or restrictions imposed, published or promulgated by any Governmental Authority, classification society or insurer applicable to the respective vessel (collectively, “Maritime Guidelines”) and all applicable international, national, state and local conventions, laws, regulations, orders, Governmental Licenses and other requirements (including, without limitation, all Environmental Laws), except where such failure to be in compliance would not have, individually or in the aggregate, a Material Adverse Effect. The Company and each applicable Subsidiary are, and with respect to the Contracted Vessels will be, qualified to own or lease, as the case may be, and operate such vessels under all applicable international, national, state and local conventions, laws, regulations, orders, Governmental Licenses and other requirements (including, without limitation, all Environmental Laws) and Maritime Guidelines, including the laws, regulations and orders of each such vessel’s flag state, except where such failure to be so qualified would not have, individually or in the aggregate, a Material Adverse Effect. (C) Each Owned Vessel is, and each Contracted Vessel will be, classed by any of Lloyd’s Register of Shipping, American Bureau of Shipping, Det Norske Veritas or a classification society which is a full member of the International Association of Classification Societies and each Owned Vessel is, and the Company will use reasonable commercial efforts to ensure each Contracted Vessel will be, in class with valid class and trading certificates, without any overdue recommendations.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Metering The Interconnection Customer shall be responsible for the Connecting Transmission Owner’s reasonable and necessary cost for the purchase, installation, operation, maintenance, testing, repair, and replacement of metering and data acquisition equipment specified in Attachments 2 and 3 of this Agreement. The Interconnection Customer’s metering (and data acquisition, as required) equipment shall conform to applicable industry rules and Operating Requirements.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!