SCOPE (cont’d) Sample Clauses

SCOPE (cont’d). 1.02 Whenever any words are used in this Agreement in the masculine gender, they shall be construed as though they were also in the feminine gender in all situations where they would so apply.
AutoNDA by SimpleDocs
SCOPE (cont’d) b) The provisions of this Agreement will also apply to the aforesaid Part-time Employees who, by virtue of their classification, are required to work more than twenty-four (24) hours per week between the dates of June 15 to Labour Day in the Aquatics Section. All other part-time employees may work up to twenty-nine (29) hours per week to respond to vacation, short-term illness within the Bargaining Unit and Union leave. This provision is not intended to supersede any other current Memorandum of Agreement. Every effort will be made to cover the above noted absences within the twenty-four

Related to SCOPE (cont’d)

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

  • The Contractor must 16.1.1. treat all Authority Protected Information as confidential and safeguard it accordingly, implementing appropriate technical and organisational measures to protect Authority Protected Information against disclosure;

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

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Technical Objections to Grievances It is the intent of both parties to this agreement that no grievance shall be defeated merely because of a technical error other than time limitations in processing the grievance through the grievance procedure. To this end an arbitration board shall have the power to allow all necessary amendments to the grievance and the power to waive formal procedural irregularities in the processing of a grievance in order to determine the real matter in dispute and to render a decision according to equitable principles and the justice of the case.

  • State Specific Contract Form Observe the state of the Seller on the Contract, if the Seller lists an address in Alaska, Arkansas, Delaware, North Carolina, Virginia, Maryland, Montana, Connecticut, Vermont, Louisiana or Mississippi, confirm the form number on the Contract is on the List of Approved Contract Forms, for the corresponding state.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Objections to New Subprocessors (a) If Customer has a legitimate reason under Data Protection Law to object to the new Subprocessors’ processing of Personal Data, Customer may terminate the Agreement (limited to the Cloud Service for which the new Subprocessor is intended to be used) on written notice to SAP. Such termination shall take effect at the time determined by the Customer which shall be no later than thirty days from the date of SAP’s notice to Customer informing Customer of the new Subprocessor. If Customer does not terminate within this thirty day period, Customer is deemed to have accepted the new Subprocessor.

  • CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

Time is Money Join Law Insider Premium to draft better contracts faster.