JOB REGISTRY SYSTEM Sample Clauses

JOB REGISTRY SYSTEM. 20.15.1 The parties agree that an OPS-wide job registry system shall be developed by the Employer and shared with the CERC, to track all funded vacancies in the Regular Service as approved to be filled by the Employer. Such vacancies shall be reported by ministries to the Employer for inclusion in the registry. Names of surplus employees shall be reported by ministries to the Employer and the Union once an employee is given written notice of lay-off. Monitoring of the job registry and targeted direct assignment results will be reported to Management Board of Cabinet and CERC by the Employer on a quarterly basis.
Sample 1Sample 2Sample 3See All (26)
AutoNDA by SimpleDocs
JOB REGISTRY SYSTEM. 14.14.1 The parties agree that an OPS-wide job registry system shall be developed by the Employer and shared with the PCERC to track all funded regular vacancies as approved to be filled by the Employer. Such vacancies shall be reported by Ministries to the Employer for inclusion in the registry. Names of surplus employees shall be reported by Ministries to the Employer and the Association once an employee is given written notice of lay-off. Monitoring of the job registry and redeployment results will be reported to Management Board of Cabinet and to the PCERC by the Employer on a quarterly basis.
Sample 1Sample 2Sample 3See All (8)
JOB REGISTRY SYSTEM. The parties agree that an job registry system shall be developed by the Employer and shared with the Central Management Committee to track all funded classified vacancies as approved to be filled by the Employer. Such vacancies shall be reported by Ministries to the Employer for inclusion in the registry. Names of surplus employees shall be reported by Ministries to the Employer and the Association once an employee is given written notice of lay-off. Monitoring of the job registry and redeployment results will be reported to Management Board of Cabinet and Central Management Committee by the Employer on a quarterly basis.
Sample 1

Related to JOB REGISTRY SYSTEM

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.

  • TLD Nameservers ICANN will use commercially reasonable efforts to ensure that any changes to the TLD nameserver designations submitted to ICANN by Registry Operator (in a format and with required technical elements specified by ICANN at xxxx://xxx.xxxx.xxx/domains/root/ will be implemented by ICANN within seven (7) calendar days or as promptly as feasible following technical verifications.

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

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