Job Classification Specifications Sample Clauses

Job Classification Specifications. Class specifications, as prepared by Minnesota Management and Budget, shall be made available to an employee upon request. If a current position description for an employee exists, it too shall be made available to the employee. When new classifications/class options are established in State service and in the bargaining unit, employees within the new classification and within the bargaining unit shall be provided with a position description by the Appointing Authority within fifteen (15) calendar days after appointment to the classification. If new classifications and/or class options are created during the life of this Agreement, the Association shall be advised in advance of the final establishment of the classification and/or class option, and upon request, may discuss the new classification and/or class option with Minnesota Management and Budget. Matters relating to classification of individual positions are covered in Article 16, Section 5.
Sample 1Sample 2Sample 3See All (11)
AutoNDA by SimpleDocs
Job Classification Specifications. Class specifications, as prepared by Minnesota Management & Budget, shall be made available to an employee upon request. If a current position description for an employee exists, it too shall be made available to the employee. When new classifications/class options are established in State service and in the bargaining unit, employees within the new classification and within the bargaining unit shall be provided with a position description by the Appointing Authority within fifteen (15) calendar days after appointment to the classification.
Sample 1Sample 2Sample 3See All (7)
Job Classification Specifications. The Human Resources Office will maintain a master set of all approved job specifications used by the Agency, which will be available on the Agency’s intranet website.
Sample 1Sample 2
Job Classification Specifications. Class specifications, as prepared by the Department of Employee Relations, shall be made available to an employee upon request. If a current position description for an employee exists, it too shall be made available to the employee. When new classifications/class options are established in State service and in the bargaining unit, employees within the new classification and within the bargaining unit shall be provided with a position description by the Appointing Authority within fifteen (15) calendar days after appointment to the classification.
Sample 1
Job Classification Specifications. If new classifications and/or class options are created during the life of this Agreement, the Association shall be advised in advance of the final establishment of the classification and/or class option, and upon request, may discuss the new classification and/or class option with Minnesota Management and Budget….
Sample 1
Job Classification Specifications. Section 1. The DHS agrees to continue to utilize the current job classification specifications in effect on the date of the signing of this Contract. The DHS reserves the right to make changes in job classification specifications, however, said changes shall not be made for arbitrary or capricious reasons. Section 2. The DHS shall meet with the Union at least ten (10) working days prior to making changes in job classification specifications for the purpose of discussing such changes. Section 3. If substantial changes in the method of operation of bargaining unit job occur, or if a new bargaining unit job is established which has not been previously classified, the DHS shall meet with the Union for the purpose of establishing a classification and rate of pay or placing the job in an existing classification. In the event the parties are not able to agree on the rate of pay for the new job, the Union shall have the right to submit the issue to arbitration as provided in Step 4 of the Grievance Procedure set forth herein.
Sample 1
Job Classification Specifications. SECTION 1. The County agrees to continue to utilize the current job classification specifications in effect on the date of the signing of this Contract. The County reserves the right to make changes in job classification specifications, however, said changes shall not be made for arbitrary or capricious reasons. SECTION 2. The County shall meet with the Union at least ten (10) working days prior to making changes in job classification specifications for the purpose of discussing such changes. SECTION 3. If substantial changes in the method of operation of bargaining unit job occur, or if a new bargaining unit job is established which has not been previously classified, the County shall meet with the Union for the purpose of establishing a classification and rate of pay or placing the job in an existing classification. In the event the parties are not able to agree on the rate of pay for the new job, the Union shall have the right to submit the issue to arbitration as provided in Step 3 of the Grievance Procedure set forth herein.
Sample 1
AutoNDA by SimpleDocs
Job Classification Specifications. The Agency shall maintain a master set of all approved job specifications applicable to the bargaining unit. Each job specification shall constitute the official job specification in the Job Classification Plan. The copies of each job specification shall indicate the date of adoption or the latest revision. The Agency shall post a copy of the job specifications for each bargaining unit class on the Agency’s intranet website.
Sample 1

Related to Job Classification 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.

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

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

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

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

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

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

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

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

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

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