Xxxxxxxxx Redress Mechanism Sample Clauses

Xxxxxxxxx Redress Mechanism. 1. Sala (Conflict resolution through penalty)
AutoNDA by SimpleDocs
Xxxxxxxxx Redress Mechanism. The Recipient shall maintain, throughout Project implementation, and publicize the availability of a grievance mechanism, in form and substance satisfactory to the Association, to hear and determine fairly and in good faith all complaints raised in relation to the Project, and take all measures necessary to implement the determinations made by such mechanism in a manner satisfactory to the Association.

Related to Xxxxxxxxx Redress Mechanism

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

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

  • Purchase Mechanism If the Focus Investor exercises its rights provided in this Section 4.5, the closing of the purchase of the New Securities with respect to which such right has been exercised shall take place within 30 calendar days after the giving of notice of such exercise, which period of time shall be extended for a maximum of 180 days in order to comply with applicable laws and regulations (including receipt of any applicable regulatory or corporate approvals). The Company and the Focus Investor agree to use commercially reasonable efforts to secure any regulatory or corporate approvals or other consents, and to comply with any law or regulation necessary in connection with the offer, sale and purchase of, such New Securities.

  • Adjustment Mechanism If an adjustment of the Exercise Price is required pursuant to this Section 6 (other than pursuant to Section 6.4), the Holder shall be entitled to purchase such number of shares of Common Stock as will cause (i) (x) the total number of shares of Common Stock Holder is entitled to purchase pursuant to this Warrant following such adjustment, multiplied by (y) the adjusted Exercise Price per share, to equal the result of (ii) (x) the dollar amount of the total number of shares of Common Stock Holder is entitled to purchase before adjustment, multiplied by (y) the total Exercise Price before adjustment.

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

  • Alternative Dispute Resolution Limitations This is a requirement of the TIPS Contract and is non-negotiable. No Waiver of TIPS Immunity This is a requirement of the TIPS Contract and is non-negotiable. 5 5 Payment Terms and Funding Out Clause This is a requirement of the TIPS Contract and is non-negotiable. 6

  • DISPUTE SETTLEMENT PROCEDURE A major objective of this Agreement is to eliminate lost time and/or production arising out of disputes or grievances. Disputes over any work related or industrial matter should be dealt with as close to its source as possible. Disputes over matters arising from this agreement shall be dealt with according to the following procedure. An employee or the union delegate or site xxxxxxx or Enterprise should initially submit any work related grievance and/or industrial matter to the site foreperson, supervisor or other appropriate site representative of the company or appropriate site union representative as relevant. If the matter remains unresolved the union delegate or site xxxxxxx may then submit the matter to the appropriate senior management person. Where relevant the Enterprise may submit the matter to a union official. If still not resolved the delegate or site xxxxxxx shall refer the matter to an appropriate official of the union, who shall discuss the matter with the nominated representative of the Enterprise. If still not resolved there may be discussions between the state secretary and senior management representative. Whilst the above procedures are being followed work should continue as normal. This procedure is to be followed in good faith and without unreasonable delay by any party. Should the matter remain unresolved and where the issue is within the jurisdiction of the Victorian Building Industry Disputes Board (“the Board”), either of the parties shall refer the dispute at first instance to the Board (which shall deal with the dispute in accordance with VBIA procedures and, where required, determine issues of jurisdiction). The Board’s decision will be accepted by all parties subject to the right of either party to refer the dispute to the Australian Industrial Relations Commission for conciliation and if required arbitration. The Commission’s decision will be accepted by all parties subject to legal rights of appeal. This dispute settlement procedure does not apply to health and safety issues or issues of industry, state or national significance.

  • Alternative Dispute Resolution Prior to filing of litigation, the parties may select non-binding mediation as a method of conflict resolution for issues arising out of or relating to this procurement process or any contract resulting from or any contemplated transaction. The parties agree that if non-binding mediation is chosen as a resolution process, the parties must agree to the chosen mediator(s) and that all mediation venue shall be at a location in Xxx Xxxxx County, Texas or agreed by the parties. The parties agree to share equally the cost of the mediation process and venue cost.

  • Negotiation; Alternative Dispute Resolution The Parties will attempt in good faith to resolve any dispute or controversy arising out of or relating to the performance of services under this Agreement. If the Parties are unable to resolve the dispute, then, pursuant to San Francisco Administrative Code Section 21.36, Contractor may submit to the Contracting Officer a written request for administrative review and documentation of the Contractor's claim(s). Upon such request, the Contracting Officer shall promptly issue an administrative decision in writing, stating the reasons for the action taken and informing the Contractor of its right to judicial review. If agreed by both Parties in writing, disputes may be resolved by a mutually agreed-upon alternative dispute resolution process. If the parties do not mutually agree to an alternative dispute resolution process or such efforts do not resolve the dispute, then either Party may pursue any remedy available under California law. The status of any dispute or controversy notwithstanding, Contractor shall proceed diligently with the performance of its obligations under this Agreement in accordance with the Agreement and the written directions of the City. Neither Party will be entitled to legal fees or costs for matters resolved under this section.

  • Move-Out Procedure Prior to either (i) the expiry of the Term, or (ii) the date on which the Resident is to vacate the Residence (detailed in Table 1 & 3), the Manager, or designate, can be requested in advance by the Resident to complete a visual inspection of the Suite to view the state of cleanliness and repair. If no request to inspect the suite is made by the Resident, the inspection will take place once the Resident has vacated the suite. In the event the Resident chooses to have the inspection completed prior to vacating the suite, the Manager, or designate, will inspect the suite and inform the Resident of potential damage and/or cleaning charges and outline what steps the student may take to mitigate charges. On vacating, all garbage and belongings of the Resident must be removed, and the suite must be cleaned to the point of restoring the suite to its original condition. Once the Resident has vacated, the Manager, or designate, will complete a documented visual inspection of the Suite. In the event deficiencies are found, the cost of cleaning the suite and restoring it to its original state may be deducted from the Resident’s original Deposit. There is a minimum cleaning charge of

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