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.
Sample 1Sample 2Sample 3See All (6)
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.
Sample 1Sample 2Sample 3See All (5)
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.
Sample 1Sample 2
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 Services – Long 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.
Sample 1

Related to Further Specifications for Operating Procedures

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Standard Operating Procedures Over approximately the past eight years, the Parties have been supplying select Products to one another for use in the operation of their respective businesses within the United States of America, Canada and Mexico. The Parties developed and been following certain standard operating procedures in connecting with, among other topics, forecasting, production planning, ordering, delivering and resolving claims on the Products supplied to one another (the “Current SOPs”). The Parties will be updating their respective business systems over the next six months, and the updates to these business systems will require the Parties to modify the Current SOPs. Once the Parties have completed the updates to the business systems and agreed on the necessary modifications to the Current SOPs, the Parties will sign a written amendment to this Agreement appending the updated standard operating procedures (the “Updated SOPs”). Until the Parties have signed a written amendment appending the Updated SOPs, the parties will continue to follow the Current SOPs. The Parties will comply with the applicable SOPs in connection with the purchase and sale of products identified in a Purchase Schedule. The Parties may add terms and conditions to, and amend the terms and conditions of, the SOP in a Purchase Schedule, but any additional and amended terms and conditions in a Purchase Schedule supplementing and modifying the SOP will only apply the specific products identified in that Purchase Schedule for its duration.

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

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

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

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