Benchmark Class Specifications Sample Clauses

Benchmark Class Specifications. 4.1 The benchmark class specifications, hereafter referred to as benchmarks, in existence at the date of this agreement and agreed to by the parties and listed in Schedule A (Grid & Benchmark Titles) shall constitute the sole criteria for classifying work covered by the collective agreement. Except as provided for in Article 9.7(d) (Classification Dispute Resolution Process) of the maintenance agreement, no new benchmark shall be introduced and no existing benchmark shall be changed except by mutual agreement between the HEABC and the Association. Neither party shall withhold mutual agreement unreasonably. 4.2 Each benchmark shall be assigned to an appropriate Classification Grid, which shall be deemed to comprise part of the benchmark.
Sample 1Sample 2Sample 3See All (30)
AutoNDA by SimpleDocs
Benchmark Class Specifications. The benchmark class specifications in existence at the date of this agreement and agreed to by the parties in the attached Wage Schedules - Benchmarks shall constitute the sole criteria for classifying work in the health care industry covered by the Collective Agreement. Except as provided for in Section 9, no new benchmark class specification shall be introduced and no existing benchmark class specification shall be changed except by mutual agreement between the HEABC and the Union. Neither party shall withhold mutual agreement unreasonably.
Sample 1Sample 2Sample 3See All (12)
Benchmark Class Specifications. (1) The benchmark class specifications in existence at the date of this agreement and agreed to by the parties in the attached Wage Schedules - Benchmarks shall constitute the sole criteria for classifying work in the health care industry covered by the Collective Agreement. Except as provided for in Section 9, no new benchmark class specification shall be introduced and no existing benchmark class specification shall be changed except by mutual agreement between the HEABC and the Union. Neither party shall withhold mutual agreement unreasonably. (2) The grid levels which are set out in the attached Wage Schedules – Grids to this agreement shall be assigned a value derived from the wage schedule of the Collective Agreement. Each benchmark class specification shall be assigned to an appropriate rate level which shall be deemed to comprise part of the specification.
Sample 1Sample 2Sample 3See All (5)
Benchmark Class Specifications. (1) The benchmark class specifications in existence at the date of this agreement and agreed to by the parties and attached as Schedule A shall constitute the sole criteria for classifying work in the health care industry covered by the Collective Agreement. Except as provided for in Section 9, no new benchmark class specification shall be introduced and no existing benchmark class specification shall be changed except by mutual agreement between the HEABC and the Union. Neither party shall withhold mutual agree- ment unreasonably. (2) The rate levels which are set out in Schedule B to this agreement shall be assigned a value derived from the wage schedule of the Collective Agreement. Each benchmark class specification shall be assigned to an appropriate rate level which shall be deemed to comprise part of the speci- fication.
Sample 1

Related to Benchmark Class Specifications

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

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

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

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

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

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

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Specifications That part of the Contract Documents consisting of written requirements for materials, equipment, systems, standards, and workmanship as applied to the Work, and certain administrative requirements and procedural matters applicable thereto. The term "Specifications" shall also include all written matter in the Project Manual or on the drawings and any Addenda or Change Orders thereto.

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