Implementation mechanisms Clause Samples

Implementation mechanisms. 22.1 To ensure full and proper implementation of the letter and spirit of this Agreement, the Parties hereby constitute a Joint Monitoring and Implementation Committee ("JOMIC") to be composed of four senior members from ZANU-PF and four senior members from each of the two MDC Formations. Gender consideration must be taken into account in relation to the composition of JOMIC. 22.2 The committee shall be co-chaired by persons from the Parties. 22.3 The committee shall have the following functions:- (a) to ensure the implementation in letter and spirit of this Agreement; (b) to assess the implementation of this Agreement from time to time and consider steps which might need to be taken to ensure the speedy and full implementation of this Agreement in its entirety; (c) to receive reports and complaints in respect of any issue related to the implementation, enforcement and execution of this Agreement; (d) to serve as catalyst in creating and promoting an atmosphere of mutual trust and understanding between the parties; and (e) to promote continuing dialogue between the Parties. 22.4 JOMIC shall be the principal body dealing with the issues of compliance and monitoring of this Agreement and to that end, the Parties hereby undertake to channel all complaints, grievances, concerns and issues relating to compliance with this Agreement through JOMIC and to refrain from any conduct which might undermine the spirit of co-operation necessary for the fulfillment of this Agreement. 22.5 The new Government shall ensure that steps are taken to make the security forces conversant with the Constitution of Zimbabwe and other laws of Zimbabwe including laws relating to public order and security. 22.6 The implementation of this agreement shall be guaranteed and underwritten by the Facilitator, SADC and the AU. 22.7 The Parties and the new Government shall seek the support and assistance of SADC and the AU in mobilizing the international community to support the new Government's economic recovery plans and programmes together with the lifting of sanctions taken against Zimbabwe and some of its leaders. 22.8 The Parties agree that they shall cause Parliament to amend any legislation to the extent necessary to bring this agreement into full force.
View SourceView Similar (6)
Implementation mechanisms. The program Administrator may issue one or more competitive procurements for program implementation services, in order to meet program design considerations that may include, but are not limited to, comprehensive audits, design ▇▇▇▇▇▇▇▇ services, project support/technical assistance, local workforce development, project qualification and review, incentive processing, and reporting. The MOU Parties may also use other implementation mechanisms with respect to this program
View SourceView Similar (3)
Implementation mechanisms. The two centres operations shall be limited to support and coordination. An annex shall be prepared which indicate the locations ofwork for both centres in Tripoli and in Malta, and the points of contact. The annex will be considered as an integral part of this Memorandum.
View Source
Implementation mechanisms. The program Administrator may provide direct workforce development grants. The program Administrator may issue one or more competitive procurements for program implementation services that may include, but are not limited to, program management, contractor qualification and oversight, innovative outreach strategies, project qualification and review, quality assurance, reporting, incentive/payment processing, assistance with program access, project support/technical assistance, and local workforce development and training. The MOU Parties may also use other implementation mechanisms with respect to this program.
View Source
Implementation mechanisms. (1) The program Administrator may issue one or more competitive procurements for projects. (2) The Collaborator will provide additional technical support beyond the duties outlined in Section II.B above during drafting of the procurement documents, contract, and project oversight including review of geothermal design documents prior to construction. (3) The MOU Parties may also jointly seek technical assistance or oversight for program selection, management, and/or measurement and verification of the program results.
View Source
Implementation mechanisms. The MOU Parties will request the City of ▇▇▇▇▇▇▇▇, the Town of Andover, and the Town of North Andover to identify one or more proposed clean energy or energy efficiency projects that meet one or more of the program goals. The MOU Parties will work with the City of ▇▇▇▇▇▇▇▇, the Town of Andover, and the Town of North Andover to develop program details, grant awards, and project implementation schedule. The MOU Parties shall agree on any grant or award and the program Administrator will be responsible for executing contracts with respect to such grants or awards.
View Source
Implementation mechanisms. (1) The MOU Parties shall work with the DHCD to identify energy efficiency and clean energy projects. (2) The program Administrator is responsible for drafting and executing an Inter-agency Service Agreement (“ISA”) and any other appropriate agreements, with the DHCD, to fund approved projects. (3) Any procurements or bids issued for project design or implementation conducted by DHCD or a public housing authority shall follow applicable rules and procedures.
View Source
Implementation mechanisms. 1. The APEI Professional Accountants and Auditors Committee (hereinafter referred to as the APAAC) is hereby established. 2. Membership of the APAAC shall comprise of three members from each jurisdiction; being two representatives from the Competent Authorities and a representative from the policy Ministry. 3. The APAAC shall be led by a Chairperson, who shall be appointed by the Chairperson of the APEI Committee. 4. The APAAC shall determine its own procedure including that of appointing sub-committees, convening its meetings and the conduct of business. 5. The APAAC shall have power to co-opt from time to time any person as a member of the committee as it may deem necessary. 6. The function of the APAAC shall be to oversee the implementation of this Agreement including through: i. monitoring the implementation of this Agreement; ii. reviewing the implementation of this Agreement and recommending action where necessary; iii. cooperation on training, practice standards and ethics; and iv. coordinating the mutual exchange of information relating to the accountancy profession and the adoption of best practices.
View Source
Implementation mechanisms. 22.1 To ensure full and proper implementation of the letter and spirit of this Agreement, the Parties hereby constitute a Joint Monitoring and Implementation Committee (“JOMIC”) to be composed of four senior members from ZANU-PF and four senior members from each of the two MDC Formations. Gender consideration must be taken into account in relation to the composition of JOMIC. 22.2 The committee shall be co-chaired by persons from the Parties. 22.3 The committee shall have the following functions:- (a) to ensure the implementation in letter and spirit of this Agreement; (b) to assess the implementation of this Agreement from time to time and consider steps which might need to be taken to ensure the speedy and full implementation of this Agreement in its entirety; (c) to receive reports and complaints in respect of any issue related to the implementation, enforcement and execution of this Agreement; (d) to serve as catalyst in creating and promoting an atmosphere of mutual trust and understanding between the parties; and (e) to promote continuing dialogue between the Parties.
View Source

Related to Implementation mechanisms

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

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

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • 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 ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/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 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 ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/resources/registries/pddrp and ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/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 ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/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.