Further Specifications for Operating Procedures Sample Clauses

Further Specifications for Operating Procedures. Detailed specifications of operating procedures and budgets required by this Contract, including but not limited to, monitoring, evaluating, auditing, billing, or regulatory changes, may be clarified in a written letter signed by Contractor and the department head, or designee, of the county department on whose behalf this Contract is made. No written clarification prepared pursuant to this Section will operate as an amendment to, or be considered to be a part of, this Contract.
AutoNDA by SimpleDocs
Further Specifications for Operating Procedures. Detailed specifications of operating procedures and budgets required by this Agreement including, but not limited to, monitoring, auditing, billing or regulatory changes, may be developed and set forth in written "Informal Agreement" entered between the Contractor and the Agency. Such "Informal Agreements" when entered shall not be modifications to this Agreement except to the extent that they further detail or clarify that which is already required hereunder. Further, any "Informal Agreement" entered may not enlarge in any manner the scope of this Agreement, including any sums of money to be paid the Contractor as provided herein. "Informal Agreements" may be approved for, and executed on behalf of the Agency by the Agency Executive Director or his Designee.
Further Specifications for Operating Procedures. Detailed specifications of operating procedures and budgets required by this Contract, including but not limited to, monitoring, evaluating, auditing, billing, or regulatory changes, may be developed and set forth in a written Informal Agreement between Contractor and County. Informal Agreements shall be designated as such and shall not be amendments to this Contract except to the extent that they further detail or clarify that which is already required hereunder. Informal Agreements may not enlarge in any manner the scope of this Contract, including any sums of money to be paid Contractor as provided herein. Informal Agreements may be approved and signed by the head of the county department for which this Contract is made or its designee.
Further Specifications for Operating Procedures. Detailed specifications of operating procedures and budgets required by this Contract, including but not limited to, monitoring, auditing, billing, or regulatory changes, may be developed and set forth in written Information Agreements between the CONTRACTOR and the AUTHORITY. Such Information Agreements shall be designated as such and shall not be amendments to this Contract except to the extent that they further detail or clarify that which is already required hereunder. Such Information Agreements may not enlarge in any manner the scope of this Contract, including any sums of money to be paid the CONTRACTOR as provided herein.
Further Specifications for Operating Procedures. Detailed specifications of operating procedures and budgets required by this Contract, including but not limited to, monitoring, evaluating, auditing, billing, or regulatory changes, may be developed and set forth in a written Informal Agreement between Contractor and HACCC GENERAL CONDITIONS Form C-4400 G (Purchase of ServicesLong Form) Revised 7/31/09 HACCC. Informal Agreements shall be designated as such and shall not be amendments to this Contract except to the extent that they further detail or clarify that which is already required hereunder. Informal Agreements may not enlarge in any manner the scope of this Contract, including any sums of money to be paid Contractor as provided herein. Informal Agreements may be approved and signed by the Executive Director of the HACCC for which this Contract is made or his designee.

Related to Further Specifications for Operating Procedures

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

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

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

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