FORM D: Deviations/Exceptions To Form Of Contract Sample Clauses

FORM D: Deviations/Exceptions To Form Of Contract. Complete and submit FORM D: Deviations/Exceptions To Master Agreement any Deviations/Exceptions proposed to the Master Agreement attached hereto as Exhibit 1 Master Agreement and include an explanation for the requested change(s) with your response. By execution of its Proposal, Respondent agrees to the Master Agreement attached as Exhibit 1. FORM D must be submitted with your Proposal, either confirming that you propose No Exceptions to the Master Agreement or requesting changes to the Master Agreement. NOTE: FAILURE TO PROVIDE COMMENTS OR REQUESTED CHANGES WILL INDICATE YOUR ACCEPTANCE OF THE REQUIRED CONTRACT PROVISIONS AND NO FURTHER NEGOTIATION OF THE PROVISIONS WILL BE PERMITTED. The final contract shall be subject to review and approval of legal counsel.
AutoNDA by SimpleDocs

Related to FORM D: Deviations/Exceptions To Form Of Contract

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement. No response

  • Form of Contract The form of contract for this solicitation shall be the Request for Proposal, the awarded proposal(s) and best and final offer(s), and properly issued and reviewed purchase orders referencing the requirements of the Request for Proposals. If a vendor submitting an offer requires TIPS and/or TIPS Member to sign an additional agreement, a copy of the proposed agreement must be included with the proposal. Vendor contract documents: TIPS will review proposed vendor contract documents. Vendor’s contract document shall not become part of TIPS’s contract with vendor unless and until an authorized representative of TIPS reviews and approves it.

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

  • Solicitation Exceptions/Deviations Explanation If the bidder intends to deviate from the General Conditions Standard Terms and Conditions or Item Specifications listed in this proposal invitation, all such deviations must be listed on this attribute, with complete and detailed conditions and information included or attached. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any bid based upon any deviations indicated below or in any attachments or inclusions. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Standard Terms and Conditions, Item Specifications, and all other information contained in this Solicitation.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • DESCRIPTION OF CONTRACT MODIFICATION This contract modification is made in accordance with Exhibit E-Revised-1, Contractual Terms and Conditions, Section 22. CHANGES, to be made part hereof for all pertinent purposes. The changes are as follows:

  • CLOUD SPECIFIC TERMS AND CONDITIONS To the extent that Contractor has received an award for Lot 3, Cloud, the following terms and conditions apply to Lot 3, Cloud. For the duration of an Authorized User Agreement, the Cloud Solution shall conform to the Cloud Solution Manufacturer’s specifications, Documentation, performance standards (including applicable license duration, warranties, guarantees, Service Level Agreements, service commitments, and credits). PROTECTION OF DATA, INFRASTRUCTURE AND SOFTWARE Contractor is responsible for providing physical and logical security for all Data, infrastructure (e.g. hardware, networking components, physical devices), and software related to the services the Contractor is providing under the Authorized User Agreement. All Data security provisions agreed to by the Authorized User and Contractor within the Authorized User Agreement may not be diminished for the duration of the Authorized User Agreement without prior written agreement by the parties amending the Authorized User Agreement.

  • Modifications/Add-ons 6.3.1 Licensee shall comply with SAP’s registration procedure prior to making Modifications or Add-ons. All Modifications and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. All Add-ons developed by SAP (either independently or jointly with Licensee) and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. Licensee agrees to execute those documents reasonably necessary to secure SAP’s rights in the foregoing Modifications and Add-ons. All Add-ons developed by or on behalf of Licensee without SAP’s participation (“Licensee Add-on”), and all rights associated therewith, shall be the exclusive property of Licensee subject to SAP’s rights in and to the Software and SAP Materials; provided, Licensee shall not commercialize, market, distribute, license, sublicense, transfer, assign or otherwise alienate any such Licensee Add-ons. SAP retains the right to independently develop its own Modifications or Add-ons to the Software, and Licensee agrees not to take any action that would limit SAP’s sale, assignment, licensing or use of its own Software or Modifications or Add-ons thereto.

  • WILEY OPEN ACCESS TERMS AND CONDITIONS Wiley Publishes Open Access Articles in fully Open Access Journals and in Subscription journals offering Online Open. Although most of the fully Open Access journals publish open access articles under the terms of the Creative Commons Attribution (CC BY) License only, the subscription journals and a few of the Open Access Journals offer a choice of Creative Commons Licenses. The license type is clearly identified on the article.

Time is Money Join Law Insider Premium to draft better contracts faster.