Contract Discrepancy Report (Attachment I of this Exhibit A Sample Clauses

Contract Discrepancy Report (Attachment I of this Exhibit A. Verbal notification of a Contract discrepancy will be made to the Contract Representative as soon as possible whenever a Contract discrepancy is identified. The problem shall be resolved within a time period mutually agreed upon by the Department and the Contractor. The Contract Administrator will determine whether a formal Contract Discrepancy Report (CDR) shall be issued. Upon receipt of this document, the Contractor is required to respond in writing to the Contract Administrator within three workdays, acknowledging the reported discrepancies or presenting contrary evidence. A plan for correction of all deficiencies identified in the Contract Discrepancy Report shall be submitted to the Contract Administrator within five workdays.
Sample 1
AutoNDA by SimpleDocs

Related to Contract Discrepancy Report (Attachment I of this Exhibit A

  • Contract Exhibit J Quarterly Sales Report If a conflict exists among any of the Contract documents, the documents shall have priority in the order listed below:

  • ATTACHMENT C STANDARD STATE PROVISIONS FOR CONTRACTS AND GRANTS

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Contract Description The Description and Location of the Contract and related project(s) are as follows.

  • ATTACHMENT B Applicable California Vehicle Code and Civil Code Provisions Note: Many California laws, which govern a tow Operator’s business and vehicle operations, are included in this attachment. The is list of California statutes included herein is intended as a general guide only and is not meant to be considered all-inclusive. It is the tow Operator’s responsibility to know and comply with all federal and state statutes and all local ordinances relating to his/her business operations, including those that are referred to in this document and those that are not; any new statutes or ordinances that are subsequently adopted; and any amendments, repeals, or modifications of existing statutes and ordinances, including but not limited to those described in this attachment.

  • 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.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • 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.

  • Grievance Description 80. The Union and the City agree that the following guidelines will be used in the submission of grievances.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

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