MIDCENTRAL SPECIFIC Sample Clauses

MIDCENTRAL SPECIFIC. Time in Lieu as an Alternative for Overtime Payment An employee who is eligible to be paid overtime shall as an alternative to such payment be entitled to choose time off equivalent to the extra time worked at the convenience of the employer. MidCentral District recognise that there may be a need for employees to work additional hours at times to meet service requirements. These additional hours may be credited as time in lieu and both parties should ensure that this time is taken off as is convenient for the person and the service.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to MIDCENTRAL SPECIFIC

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

  • Signaling Parameters All SS7 signaling parameters will be provided in conjunction with traffic exchange trunk groups, where and as available. These parameters include Automatic Number Identification (ANI), Calling Party Number (CPN), Privacy Indicator, calling party category information, originating line information, charge number, etc. Also included are all parameters relating to network signaling information, such as Carrier Information Parameter (CIP), wherever such information is needed for call routing or billing. GTE will provide SS7 via GR-394-SS7 and/or GR-317-SS7 format(s).

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

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