Contract Administrator and Project Change Request Sample Clauses

Contract Administrator and Project Change Request. Each party will designate a contract administrator as set forth in the applicable SOW, which may be changed from time to time by either party by providing written notice to the other party. In the event CLIENT requests minor changes to the Services and/or Hardware described in an SOW, CLIENT may submit a project change request form (“Project Change Request”) to AU for AU’s review or initiate a request through a support ticket provided by AU in accordance with AU’s processes and procedures. In the event AU accepts the Project Change Request or otherwise agrees to the changes requested via the support ticket, AU shall notify in its response to the support ticket and/or it in its response to the Project Change Request. Any mutually agreed upon such changes following the foregoing process shall be memorialized by the parties in writing and considered incorporated into the applicable SOW. In the event of a conflict between the terms and conditions of an SOW and a Project Change Request and/or agreed upon change via a support ticket, the change agreed upon by the parties via the support ticket or the Project Change Request (as the case may be) shall govern as it relates to the particular SOW.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Contract Administrator and Project Change Request

  • Change Request Either Landlord or Tenant may request Changes after Landlord approves the Approved Plans by notifying the other party thereof in writing in substantially the same form as the AIA standard change order form (a “Change Request”), which Change Request shall detail the nature and extent of any requested Changes, including (a) the Change, (b) the party required to perform the Change and (c) any modification of the Approved Plans and the Schedule, as applicable, necessitated by the Change. If the nature of a Change requires revisions to the Approved Plans, then the requesting party shall be solely responsible for the cost and expense of such revisions and any increases in the cost of the Tenant Improvements as a result of such Change. Change Requests shall be signed by the requesting party’s Authorized Representative.

  • No Cost Change Request The Authorized User reserves the right to reasonably amend a Fixed-Price Deliverable, provided the amendment does not materially change the Scope of the Deliverable, without a cost increase. Although the Authorized User has endeavored to identify many tasks associated with a Fixed-Price Deliverable (Tasks), additional Tasks which can reasonably be anticipated to carry out the Deliverable shall be within the scope of the Deliverable, and shall not result in a cost increase. An Authorized User shall use Appendix F, Attachment 4, No Cost Change Request Template to reflect such modifications. Written approval of the No-Cost Change Request is required from both the Authorized User and the Contractor.

  • CHANGE REQUEST PROCEDURE (a) Any Change Request of Customer or SAP must be in writing and in the format as provided by SAP.

  • 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

  • Change Request Procedures 4.1. Either party can request changes to the Service in accordance with the change request form attached to the Order Form or provided by SAP from time to time (“Change Request”).

  • Change Requests 4.1.1. Either party can request changes to the Service.

  • Contract Task Order A-E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The COUNTY Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with COUNTY Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by COUNTY Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, COUNTY Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned COUNTY Project Manager within the timeframe indicated in the CTO or as directed by COUNTY Project Management staff.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Housing.

  • Independent Status of Contractor In the performance of this Contract, the parties shall be acting in their individual, corporate or governmental capacities and not as agents, employees, partners, joint ventures, or associates of one another. The parties intend that an independent contractor relationship shall be created by this Contract. The Contractor shall be responsible for all federal and/or state tax, industrial insurance, wages, benefits, or other compensation by or on behalf of the Contractor and its employees. The Contractor shall not make any claim of right, privilege or benefit which would accrue to an employee under chapter 41.06 RCW or Title 51 RCW.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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