Classification Specifications The Employer agrees to supply the President of the Union or his/her designate with the classification specifications for those classifications in the Bargaining Unit.
CHANGE IN CLASSIFICATION SPECIFICATIONS Section 1. The Employer shall notify the Union of intended classification studies.
Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.
Job Evaluation Plan (a) The Employer agrees that no job evaluation plan pertaining to positions covered by this Agreement will be introduced without the mutual agreement of the Parties.
Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.
Classification Plan (a) The Employer and the Union recognize the need to maintain the principles of Pay Equity to evaluate jobs in the Public Service bargaining unit. The parties also agree to apply the Public Service Job Evaluation Plan in accordance with those principles to all bargaining unit positions using the gender neutral plan factors and degrees in the Public Service Job Evaluation Plan. The Public Service Job Evaluation Plan will be used to evaluate positions in the Main Agreement and to determine their appropriate factor ratings.
Classification Plan Revisions A. The Employer will provide to the Union, in writing, any proposed changes to the classification plan including descriptions for newly created classifications. Upon request of the Union, the Employer will bargain, in accordance with Article 37, Mandatory Subjects, the effect(s) of a change to an existing class or newly proposed classification.
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.
Classification Changes When the University determines that a revision of a class specification for positions covered by this agreement is needed, and such revision affects the collective bargaining unit designation, the University shall notify AFSCME in writing of the proposed change. AFSCME shall notify the University, in writing, within fifteen (15) days of receipt of the proposed changes, of any comments it has concerning the proposed changes or of its desire to discuss the proposed changes.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
