Exit Mechanism Sample Clauses

Exit Mechanism. 9.1.1 The Company and the Founders shall provide an exit (the “Exit”) to the Investors within a period of 5 years from the Effective Date (“Exit Date”) by undertaking either (a) a Qualified Initial Public Offering in accordance with Clause 9.1.2 below; (b) an Exit Sale in accordance with Clause 9.1.3 below; 9.
AutoNDA by SimpleDocs
Exit Mechanism. 1After the Closing, if any Investor exits through the Company’s Subsequent Financing, mergers and acquisitions, Qualified IPO or other transactions conducted by the resolutions of shareholders or the Board of Directors (the “Company-led Exit Transaction”), the Repurchase Obligors shall ensure that the Investor sells his shares in the Company at a consideration of not less than the Qualified Exit Price. For the purposes of this Section 4, Subsequent Financing means any issuance of New Securities (as defined below) after the Closing.
Exit Mechanism. 5.1 The shareholders may legally transfer all or any part of their shares to each other or a third party. 5.2 Party A may legally transfer its equity interests in the Target Company to a third party at an equity exchange center through bidding, auction and listing. 5.3 Under equal conditions, the other shareholder shall have the right of first refusal.
Exit Mechanism. Any Party to this Agreement may withdraw from the Agreement to be effective no sooner than the end of any calendar year provided the withdrawing Party gives to all other Parties no less than three (3) months’ prior written notice of its intent to withdraw. 1. Withdrawal from this Agreement shall not relieve the Agency from responsibility for the Agency’s financial obligations through the remainder of the current fiscal year. 2. No compensation of any kind, including refunds of assessments or distributions that may be realized from the eventual liquidation of property and equipment acquired hereunder, will be returned to any Agency until final termination of this Agreement. Assets purchased by County IT or 9-1-1 in the initial contract with the third-party vendor will remain the respective property of County IT or 9-1-1.
Exit Mechanism. GoS/XXXXX agrees to consider any proposal of any other Shareholder made after completion of 2 (“Two”) Years from the Commercial Operation Date of the Project or earlier on mutual beneficial terms to divest some part of GoS/SPICL’s equity share capital in the Company either in favour of such person or public/IPO, to whom the said Shareholder is selling its equity shares in the Company.
Exit Mechanism. In the event a Founder desires to transfer, sell , or otherwise dispose of their equity interest in the Company, they shall first provide written notice to the other Founder(s) and offer them the right of first refusal to purchase such equity interest on the same terms and conditions as offered to a third party. If the other Founder(s) decline or do not respond within [number of days, e.g., 30 days], the selling Founder may proceed with the transfer to a third party, subject to the Company's governing documents and applicable law. The Founders acknowledge that the enforceability of certain provisions in this Agreement, including but not limited to non-compete restrictions, may be subject to the laws of the jurisdiction in which the Company is located. The Founders agree to comply with such laws and to seek appropriate legal advice as necessary to ensure the enforceability of this Agreement.
Exit Mechanism. Membership of the PSB is Senior / Executive Members of partner organisations. If a PSB Member is no longer able to fulfil their role on the PSB it is their responsibility to find a suitable replacement from their organisation to take their position on the group. The full membership of the PSB is as per the guidance form the Well-being of Future Generations (Wales) Xxx 0000.
AutoNDA by SimpleDocs
Exit Mechanism. Titan III will have the right at any time to put its interest in a Stabilized OPJV to the OP for OP Units (valued at their public market price) or cash, at the OP’s election. These OP Units will be entitled to the registration rights to be afforded to holders of OP Units generally. Further at any time that such right is exercised by Titan III as to a positive return OPJV, the OP shall have the right to also call Titan III’s interest in one or more negative return OPJV’s which are fully operational for more than one calendar year and the price for such interests shall be calculated on a blended basis taking into account shortfalls from negative return OPJV’s. After a property’s fifth full calendar year of operations, the OP will have the right to force an exchange of Titan III’s interest in the property’s OPJV for OP Units (valued at their public market price) or cash, at the OP’s election. These OP Units will be entitled to the registration rights to be afforded to holders of OP Units then outstanding. The Master Agreement will specify to extent possible the limitations on converting Units to cash, i.e., length of holding period and issuing price.
Exit Mechanism 

Related to Exit Mechanism

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

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

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

  • Payment Mechanics All payments of principal and interest hereunder are to be made in lawful money of the United States of America in the manner specified in Article III of the Purchase and Sale Agreement.

  • 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-­‐

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