Product Units Delivered Outside of the United States Sample Clauses

Product Units Delivered Outside of the United States. For Product units delivered by Rivian or a third party engaged by Rivian or Amazon outside of the United States, Amazon will have the right at the Rivian Manufacturing Facility or an alternative site agreed to by the Parties (the “Non-US Inspection Location” and together with the US Inspection Location, the “Inspection Location”) to conduct any nondestructive inspection or testing for a period of forty-eight (48) hours following the close of business of the date that the Product unit arrives at Non-US Inspection Location to determine whether the Product is Conforming (the “Non-US Inspection Period” and together with the US Inspection Period, the “Inspection Period”). Notwithstanding the foregoing, if the final assembly for a Product occurs at a location other than the Rivian Manufacturing Facility, the Parties will agree on an amendment to this Work Order to address terms that will apply to allow Amazon to perform inspections at the final assembly location. If Amazon fails to notify Rivian that Amazon rejects a Product unit for Non-Conformity prior to the expiration of the Non-US Inspection Period, the Product unit will be deemed accepted by Amazon, and payment will be due for that Product unit. If Amazon rejects a Product unit for Non-Conformity during the Non-US Inspection Period, such rejection will be handled in accordance with Section 3.7(B). Amazon’s acceptance of a Product unit under a Purchase Order will not be deemed acceptance of any other Product unit under the same or different Purchase Order, and Amazon may provide separate acceptance of each Product unit under any Purchase Order. Amazon’s acceptance of Product units will not relieve Rivian of any of its obligations under the Agreement.
AutoNDA by SimpleDocs

Related to Product Units Delivered Outside of the United States

  • Increasing Seat Belt Use in the United States E.O. 13043, amended by E.O. 13652, requires Recipients to encourage employees and contractors to enforce on-the-job seat belt policies and programs when operating company- owned, rented or personally-owned vehicle.

  • DATABASE OF RESTRICTED SUPPLIER The process of restriction is used to exclude a company/person from conducting future business with Transnet and other organs of state for a specified period. No Bid shall be awarded to a Bidder whose name (or any of its members, directors, partners or trustees) appear on the Register of Tender Defaulters kept by National Treasury, or who have been placed on National Treasury’s List of Restricted Suppliers. Transnet reserves the right to withdraw an award, or cancel a contract concluded with a Bidder should it be established, at any time, that a bidder has been restricted with National Treasury by another government institution.

  • Inventions Assigned to the United States I agree to assign to the United States government all my right, title, and interest in and to any and all Inventions whenever such full title is required to be in the United States by a contract between the Company and the United States or any of its agencies.

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that Xxxxx has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

  • Notice of Restricted Transfer Any Person who acquires or attempts or intends to acquire Beneficial Ownership or Constructive Ownership of Shares that will or may violate Section 13.2(a) or any Person who would have owned Shares that resulted in a transfer to the Trust pursuant to the provisions of Section 13.2(b) shall immediately give written notice to the Company of such event or, in the case of such a proposed or attempted transaction, give at least 15 days prior written notice, and shall provide to the Company such other information as the Company may request in order to determine the effect, if any, of such Transfer or Non-Transfer Event on the Company’s qualification as a REIT.

  • Outside the United States If you acquired the software in any other country, the laws of that country apply.

  • Unbundled Digital Loops 2.3.1 BellSouth will offer Unbundled Digital Loops (UDL). UDLs are service specific, will be designed, will be provisioned with test points (where appropriate), and will come standard with OC and a DLR. The various UDLs are intended to support a specific digital transmission scheme or service. 2.3.2 BellSouth shall make available the following UDLs, subject to restrictions set forth herein:

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59

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