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.
ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.
Contract Revisions Notwithstanding Contract Exhibit C, Special Contract Conditions section 6.9, the following types of revisions can be made to the Contract without a formal Contract amendment, upon written notice: Revisions by the Contractor:
1) Contractor’s Information and Contacts
2) Contractor’s Contract Manager Revisions by the Department:
1) Department’s Contract Manager
2) Department’s Quarterly Sales Report (Contract Exhibit J)
3) Contractor Performance Survey (Contract Exhibit I) Contract Exhibit C, Special Contract Conditions section 6.9, applies to all other modifications to the Contract.
Program Location A. Unless otherwise agreed upon in writing, the parties acknowledge and agree that the Work of this Agreement will be performed at the following Property address: Ktr Address1 Address2
Terminal Receipt You can get a receipt at the time you make any transaction (except inquiries) involving your account using an ATM and/or point-of-sale (POS) terminal.
Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.
Escrow Format Specification 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.
ESTIMATED / SPECIFIC QUANTITY CONTRACTS Estimated quantity contracts, also referred to as indefinite delivery / indefinite quantity contracts, are expressly agreed and understood to be made for only the quantities, if any, actually ordered during the Contract term. No guarantee of any quantity is implied or given. With respect to any specific quantity stated in the contract, the Commissioner reserves the right after award to order up to 20% more or less (rounded to the next highest whole number) than the specific quantities called for in the Contract. Notwithstanding the foregoing, the Commissioner may purchase greater or lesser percentages of Contract quantities should the Commissioner and Contractor so agree. Such agreement may include an equitable price adjustment.
