Consultation mechanisms Sample Clauses

Consultation mechanisms. 1. The Parties shall engage in dialogue through ongoing contacts, exchanges and consultations, which include the following: (a) summits at leaders level on an annual basis or as mutually agreed, held alternately in the Union and in Canada; (b) meetings at foreign-minister level; (c) consultations at ministerial level on policy issues of mutual interest; (d) consultations of officials at the senior and working level on issues of mutual interest or briefings and cooperation on major domestic or international developments; (e) promotion of exchanges of delegations from the European Parliament and the Parliament of Canada.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
Consultation mechanisms. 1. For the purpose of the proper implementation of this Agreement, the Contracting Parties shall, whenever necessary, exchange information and, at the request of either Contracting Party, hold consultations. 2. The Contracting Parties agree that the implementation of this Agreement shall be supervised and administered by a Joint Committee consisting of representatives of the Contracting Parties. For this purpose, the following shall apply: (a) The exchange of information and the consultations referred to in paragraph 1, and especially the consultations and decisions referred to in Article 23, shall, when appropriate, take place in the Joint Committee. (b) The Joint Committee may take decisions in cases provided for in this Agreement. On other matters the Joint Committee may make recommendations. (c) For the purpose of the proper implementation of this Agreement the Joint Committee shall meet whenever necessary. Each Party to this Agreement may request that a meeting be held. (d) The Joint Committee shall act by common agreement. (e) The Joint Committee shall lay down its own rules of procedure. (f) The Joint Committee may decide to set up such sub-committees and working parties as it considers necessary to assist it in accomplishing its tasks. (g) The Joint Committee may decide to amend the Annexes.
Sample 1Sample 2
Consultation mechanisms. TransGrid is committed to consultation and will maintain a two tiered consultative committee structure comprising of relevant TransGrid management and nominated employee representatives to enable ongoing discussion and information sharing on relevant matters at the workplace. To ensure appropriate consideration of all relevant matters the committees should be reflective of all workgroups at the relevant location. The committees are: • Level 1 Committee which meets on a quarterly basis, or as required, and will consider matters of a strategic organisational nature that are likely to impact on employees. The committee will consist of executive and senior management representatives, union officials and a representative from each Level 2 committee. • Level 2 Committees at each major location/workplace to consider location/workplace matters relevant to employees in that local area. These Committees meet at least every quarter and provide updates to the Level 1 Committee and will be a forum for cascading consultation. The committee will consist of local management and employee elected representatives covering all relevant workgroups at the site.
Sample 1
Consultation mechanisms. 1. For the purpose of the proper implementation of this Agreement, the Contracting Parties shall, whenever necessary, exchange information and, at the request of either Contracting Party, hold consultations. 2. The Contracting Parties agree that the implementation of this Agreement shall be supervised and administered by a Joint Committee consisting of representatives of the Contracting Parties. For this purpose, the following shall apply: (a) The exchange of information and the consultations referred to in paragraph 1, and especially the consultations and decisions referred to in Article 23, shall, when appropriate, take place in the Joint Committee. other matters the Joint Committee may make recommendations.
Sample 1
Consultation mechanisms. 46.1 Employees, the Company and the Union may identify matters (other than those covered by Clause 47 of this Agreement where separate consultation procedures are established) that need to be the subject of enterprise or workplace consultation. 46.2 A workplace Consultative Committee will operate for this purpose. 46.3 All employees, whether members of the Union or not will be entitled to vote in the establishment of the Consultative Committee and in any future votes regarding its constitution and/or role. 46.4 The Committee will establish consultative procedures appropriate to the needs of the workplace and consistent with Clause 7 of this Agreement. From time to time the Committee will review these procedures. 46.5 The Consultative Committee will consist of 4 employee representatives, 1 of which will be the Union representative, and 4 representatives of the Company. The safety representative who represents employees on OH&S matters will also attend Consultative Committee meetings while OH&S matters are being discussed and decisions taken. 46.6 Minutes will be taken at each meeting of the Consultative Committee and will be provided to all members of the Committee as soon as practicable after the conclusion of each meeting. 46.7 Each agreement reached, as a result of work done by the Consultative Committee, will be set down in writing and will be implemented according to its terms. 46.8 The Company shall make facilities available in a prominent position in the workplace upon which union representatives be allowed to post union notices.
Sample 1
Consultation mechanisms. TransGrid is committed to consultation and will maintain a two tiered consultative committee structure comprising of relevant TransGrid management and nominated employee representatives to enable ongoing discussion and inf ormation sharing on relevant matters at the workplace. To ensure appropriate consideration of all relevant matters the committees should be ref lective of all workgroups at the relevant location. The committees are:  Level 1 Committee which meets on a 2 monthly quarterly basis, or as required, and will consider matters of a strategic organisational nature that are likely to impact on employees. The committee will consist of executive and senior management representatives, union of f icials and a representative f rom each Level 2 committee.  Level 2 Committees at each major location/workplace to consider location/workplace matters relevant to employees in that local area. These Committees meet at least every quarter and provide updates to the Level 1 Committee and will be x x xxxx f or cascading consultation. The committee will consist of local management and employee elected representatives covering all relevant workgroups at the site.
Sample 1
Consultation mechanisms. (1) A Consultative Committee shall be established at each hospital. (2) Each Consultative Committee shall be made up of representatives of the employer respondents and the union party to this Agreement. (3) The Consultative Committees are for the purpose of progressing the issues raised in this Agreement and shall be established in accordance with the guidelines of this Agreement. The process shall begin by either party at a workplace notifying the others of the intention to start a Consultative Committee. (4) The parties shall then meet to decide the structure and the process of the Consultative Committee including elections and timetables. (5) Each union representative who has not previously received consultative training shall be released to attend union Consultative Committee training course before the first consultative committee meeting. (6) The Consultative Committees at each hospital shall progress issues relating to this Agreement. In particular the following issues may be considered: (a) Waste Management (b) Benchmarking (c) Skills Training (d) Service Quality (e) Staff Morale (f) The introduction of PCAs (g) Work Processes (h) Rostering (i) Absenteeism: Not to be approached in a negative/disciplinary manner (j) Local workplace issues (k) Occupational Safety & Health (l) Employee Mobility (7) The employer shall provide reasonable resourcing to ensure effective and informed employee participation, access to all relevant information and reasonable period of time release to facilitate the consultative process. (8) The employer shall be responsible for the keeping of proper records of the Consultative Committee. At the conclusion of each meeting minutes of the Consultative Committee shall be forwarded by the employer to the union. (9) An officer of the union is entitled to attend a meeting of the Consultative Committee and address the Committee on any issue but shall not vote on any motion.
Sample 1
AutoNDA by SimpleDocs
Consultation mechanisms. In implementing the agreed outcomes of this Agreement, a consultative mechanism will be established to ensure the continued effective and/or efficient operation of this Agreement.
Sample 1

Related to Consultation mechanisms

  • CONSULTATIVE MECHANISMS 11.1 Effective consultation is essential for continuous workplace reform and such consultation can take place at any time during the life of a project. Consultative Committees may be set up on larger projects for this purpose. The Consultative Committee will operate for the purpose of continually assessing the efficiency of working arrangements, monitoring the outcomes of this Agreement, coordinating training activities and sharing pertinent information.

  • Consultative Mechanism The parties agree that a precondition for the effective operation of the Agreement is the establishment of consultative mechanisms with the Company. To this end, a Consultative Committee, comprising of Company appointed representatives and employee elected representatives should be established and maintained. Officers of the Union shall have a standing invitation to attend any such meeting. The purpose of the Consultative Committee shall be to consult, develop, recommend and assist to implement strategies and measures designed to achieve the objectives outlined under Clause 4 of this Agreement.

  • Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.

  • Consultation Procedure If a party hereto is unable to meet the provisions of the Service Level Agreement, or in the event that a dispute arises relating to performance goals set forth in the Service Level Agreement, either party to this Agreement shall address any concerns it may have by requiring a consultation with the other party.

  • Validation Mechanism To be eligible for articulation, the student must show evidence of their CompTIA A+ certification and it must have been issued within three (3) years prior to their enrollment in the program.

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • Rights Protection Mechanisms Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the registry-­‐registrar agreement entered into by ICANN-­‐accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-­‐requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-­‐

  • Dispute Resolution Mechanism a. Any dispute regarding the administration of the Institute at the Company or plant level shall be subject to expedited resolution by the Chairs of the Union and Company Negotiating Committees and the Executive Director of ICD who shall apply the policies, rules and regulations of the Governing Board and the provisions of this Section in ruling on any such dispute. Rulings of the Executive Director may be appealed to the Governing Board, but shall become and remain effective unless stayed or reversed by the Governing Board. b. Within sixty (60) days of the Effective Date, the parties will develop an expedited dispute resolution mechanism that resolves disputes within two (2) weeks.

  • Consultation 10.1 The Employer agrees to consult the Employee timeously where the exercising of its powers will have amongst others- 10.1.1 A direct effect on the performance of any of the Employee’s functions; 10.1.2 Commit the Employee to implement or to give effect to a decision made by the Employer; and 10.1.3 A substantial financial effect on the Employer. 10.2 The Employer agrees to inform the Employee of the outcome of any decisions taken pursuant to the exercise of powers contemplated in clause 12.1 as soon as is practicable to enable the Employee to take any necessary action with delay.

  • Rights Protection Mechanisms and Abuse Mitigation ­‐ Registry Operator commits to implementing and performing the following protections for the TLD: i. In order to help registrars and registrants identify inaccurate data in the Whois database, Registry Operator will audit Whois data for accuracy on a statistically significant basis (this commitment will be considered satisfied by virtue of and for so long as ICANN conducts such audits). ii. Work with registrars and registrants to remediate inaccurate Whois data to help ensure a more accurate Whois database. Registry Operator reserves the right to cancel a domain name registration on the basis of inaccurate data, if necessary. iii. Establish and maintain a Domains Protected Marks List (DPML), a trademark protection service that allows rights holders to reserve registration of exact match trademark terms and terms that contain their trademarks across all gTLDs administered by Registry Operator under certain terms and conditions. iv. At no cost to trademark holders, establish and maintain a Claims Plus service, which is a notice protection mechanism that begins at the end of ICANN’s mandated Trademark Claims period. v. Bind registrants to terms of use that define and prohibit illegal or abusive activity. vi. Limit the use of proxy and privacy registration services in cases of malfeasance. vii. Consistent with the terms of this Registry Agreement, reserve the right to exclude from distribution any registrars with a history of non-­‐compliance with the terms of the Registrar Accreditation Agreement. viii. Registry Operator will be properly resourced to perform these protections.

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