Dependencies and Compatibilities Sample Clauses

The "Dependencies and Compatibilities" clause defines the requirements and conditions regarding how a product, service, or software interacts with other systems, components, or technologies. It typically outlines any necessary third-party tools, platforms, or versions that must be present for proper operation, and may specify which combinations are supported or prohibited. This clause ensures that all parties are aware of technical prerequisites and limitations, thereby reducing the risk of integration issues and clarifying responsibilities for maintaining compatibility.
Dependencies and Compatibilities. Trimble makes no warranty or guarantee with respect to any Dependencies, Compatibilities, or other factors outside of ▇▇▇▇▇▇▇’▇ control, including their continued availability or compatibility.
Dependencies and Compatibilities. (a) Offerings may (i) require certain dependencies, including, without limitation, internet connection, electronic communications, hardware, data connections, operating systems, third-party products and services, other ▇▇▇▇▇▇▇ products and services, satellite signals, etc. (collectively, “Dependencies”), and (ii) allow compatibility and/or interoperability with other products or services made available by Trimble, Customer, or a third party (collectively, “Compatibilities”). (b) Dependencies and Compatibilities may require payment of a separate fee and are governed by their respective terms of service, end user license agreement, or other agreement, and not by the Agreement. Unless otherwise expressly agreed upon by the parties in writing, Customer is responsible for all Dependencies and Compatibilities. Trimble may modify the Offerings from time to time, and Trimble does not guarantee that the Offerings will continue to operate or be compatible with any Dependencies or Compatibilities. Trimble makes no warranty or guarantee, and will have no liability or obligations under the Agreement, with respect to any Dependencies, Compatibilities, or other factors outside of ▇▇▇▇▇▇▇’▇ control. (c) Customer represents and warrants that it shall, and shall use best efforts to require any provider of any Dependencies and Compatibilities to: (i) establish and maintain industry standard technical, organizational, physical, and administrative safeguards designed to ensure the security and integrity of the Offerings; and
Dependencies and Compatibilities. (a) The Offering may (i) require certain dependencies, including, without limitation, internet connection, electronic communications, hardware, data connections, operating systems, third-party products and services, other Trimble products and services, satellite signals, etc. (collectively, “Dependencies”), and (ii) allow compatibility and/or interoperability with other products or services made available by Trimble, Customer, or a third party (collectively, “Compatibilities”). (b) Dependencies and Compatibilities may require payment of a separate fee and are governed by their respective terms of service, end user license agreement, or other agreement, and not by the Agreement. Unless otherwise expressly agreed upon by the parties in writing, Customer is responsible for all Dependencies and Compatibilities. Trimble may modify the Offering from time to time, and Trimble does not guarantee that the Offering will continue to operate or be compatible with any Dependencies or Compatibilities. Trimble makes no warranty or guarantee, and will have no liability or obligations under the Agreement, with respect to any Dependencies, Compatibilities, or other factors outside of ▇▇▇▇▇▇▇’▇ control. (c) Customer represents and warrants that it shall, and shall require any provider of any Dependencies and Compatibilities to: (i) establish and maintain industry standard technical, organizational, physical, and administrative safeguards designed to ensure the security and integrity of the Offering; and (ii) comply with the security controls, configuration requirements, and access limitations imposed by ▇▇▇▇▇▇▇, as may be modified by ▇▇▇▇▇▇▇ from time to time. (d) If Customer enables Dependencies or Compatibilities with the Offering, ▇▇▇▇▇▇▇ may access and exchange Customer Data with the Dependencies or Compatibilities on Customer’s behalf. Trimble will have no liability or obligations under the Agreement with respect to how any Dependencies or Compatibilities uses or processes Customer Data. If Trimble hosts any Dependency or Compatibilities at Customer’s request, Customer represents and warrants to Trimble that Customer has all rights necessary. Trimble may charge additional fees for such hosting services.
Dependencies and Compatibilities. If Customer enables Dependencies or Compatibilities with an Offering, ▇▇▇▇▇▇▇ may access and exchange Customer Data with the Dependencies or Compatibilities on Customer’s behalf. Trimble will have no liability or obligations under the Agreement with respect to how any Dependencies or Compatibilities uses or processes Customer Data. If Trimble hosts any Dependency or Compatibilities at Customer’s request, Customer represents and warrants to Trimble that Customer has all rights necessary. Trimble may charge additional fees for such hosting services.

Related to Dependencies and Compatibilities

  • Capabilities A. The Parties agree that the DRE must possess the legal, technical, and financial capacity to: (1) Accept and expend non-federal funds consistent with Section 4.2.4; (2) Accept transfer of the FERC license and title for the Facilities from PacifiCorp; (3) Seek and obtain necessary permits and other authorizations to implement Facilities Removal; (4) Enter into appropriate contracts and grant agreements for effectuating Facilities Removal; (5) Perform, directly or by oversight, Facilities Removal; (6) Prevent, mitigate, and respond to damages the DRE or any of its contractors, subcontractors, or assigns cause during the course of Facilities Removal, and, consistent with Applicable Law, respond to and defend associated liability claims against the DRE or any of its contractors, subcontractors, or assigns, including costs thereof and any judgments or awards resulting therefrom; (7) Carry the required insurance and bonding set forth in Appendix L to respond to liability and damages claims associated with Facilities Removal against the DRE or any of its contractors, subcontractors, or assigns; (8) Meet the deadlines set forth in Exhibit 4; and (9) Perform such other tasks as are reasonable and necessary for Facilities Removal. B. Before the DRE and PacifiCorp file the joint application to transfer the license for the Facilities, the DRE will Timely demonstrate to the reasonable satisfaction of the States and PacifiCorp that it possesses the legal, technical, and financial capacity to accomplish the tasks in Sections 7.1.2.A(1) through (5), (8), and (9). PacifiCorp and the States will consult if the DRE fails to make the demonstration required in this subsection. C. Within six months of the DRE’s execution of the Settlement, the DRE will include in an informational filing in the FERC license transfer proceeding proof that it possesses the legal, technical, and financial capacity to accomplish the tasks in Sections 7.1.2.A(6) and (7). This filing will include documentation that the DRE meets the requirements of Parts II, III, and IV of Appendix L and is capable of fulfilling its obligations under Section 7.1.3. The DRE will not provide the filing if either of the States or PacifiCorp objects to the filing after a reasonable opportunity to review before submission to FERC. The six-month deadline may be changed by agreement of the DRE, the States, and PacifiCorp. The Parties will Meet and Confer if the DRE fails to provide the informational filing to FERC.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.