Continuing Organization Sample Clauses

Continuing Organization. Notwithstanding the Participant’s authority to withdraw, this Agreement and MN-TF1 shall continue in force until all remaining Participants mutually agree to terminate this Agreement.
AutoNDA by SimpleDocs

Related to Continuing Organization

  • Professional Organizations During the Term, Executive shall be reimbursed by the Company for the annual dues payable for membership in professional societies associated with subject matter related to the Company's interests. New memberships for which reimbursement will be sought shall be approved by the Company in advance.

  • International Organization Any international organization or wholly owned agency or instrumentality thereof. This category includes any intergovernmental organization (including a supranational organization) (1) that is comprised primarily of non-U.S. governments; (2) that has in effect a headquarters agreement with Singapore; and (3) the income of which does not inure to the benefit of private persons.

  • Project Organization A summary organization chart showing the interrelationships between Owner, Construction Contractor and Design Professional, and other supporting organizations and permitting review agencies. Detailed charts, one each for Construction Contractor and Design Professional, showing organizational elements participating in the Project shall be included.

  • NONPROFIT ORGANIZATION(S) A university or other institution of higher education or an organization of the type described in section 501(c)(3) of the Internal Revenue Code of 1954 (26 U.S.C. 501(c)) and exempt from taxation under section 501(a) of the Internal Revenue Code (26 U.S.C. 501(a)) or any nonprofit scientific or educational organization qualified under a state nonprofit organization statute. As used herein, the term also includes government agencies.

  • Project Organization Chart As part of the Mini-Bid, the Authorized User may require the Contractor to develop and submit a proposed project organization chart. The project organization chart should identify all the proposed key personnel of each team component and how the team will be managed. If required, the project organization chart must include both Contractor and State staff roles as identified in the Mini-Bid.

  • DIRECTORS, OFFICERS AND ORGANIZATION LIABILITY Required (If Grantee is a Non‐Profit or if a first tier contractor or subgrantee is a Non‐Profit) Directors, Officers and Organization insurance covering the Grantee’s Organization, Directors, Officers, and Trustees actual or alleged errors, omissions, negligent, or wrongful acts, including improper governance, employment practices and financial oversight - including improper oversight and/or use of use of grant funds and donor contributions - with a combined single limit of no less than $1,000,000.00 per claim.

  • Table C - Receiving Organisation Enterprise The Receiving Organisation/Enterprise will provide financial support to the trainee for the traineeship: Yes ☐ No ☐ If yes, amount (EUR/month): ……….. The Receiving Organisation/Enterprise will provide a contribution in kind to the trainee for the traineeship: Yes ☐ No ☐ If yes, please specify: …. The Receiving Organisation/Enterprise will provide an accident insurance to the trainee (if not provided by the Sending Institution): Yes ☐ No ☐ The accident insurance covers: - accidents during travels made for work purposes: Yes ☐ No ☐ - accidents on the way to work and back from work: Yes ☐ No ☐ The Receiving Organisation/Enterprise will provide a liability insurance to the trainee (if not provided by the Sending Institution): Yes ☐ No ☐ The Receiving Organisation/Enterprise will provide appropriate support and equipment to the trainee. Upon completion of the traineeship, the Organisation/Enterprise undertakes to issue a Traineeship Certificate within 5 weeks after the end of the traineeship. By signing this document, the trainee, the Sending Institution and the Receiving Organisation/Enterprise confirm that they approve the Learning Agreement and that they will comply with all the arrangements agreed by all parties. The trainee and Receiving Organisation/Enterprise will communicate to the Sending Institution any problem or changes regarding the traineeship period. The Sending Institution and the trainee should also commit to what is set out in the Erasmus+ grant agreement. The institution undertakes to respect all the principles of the Erasmus Charter for Higher Education relating to traineeships. Commitment Name Email Position Date Signature Trainee Trainee Responsible person12 at the Sending Institution Supervisor13 at the Receiving Organisation During the Mobility Table A2 - Exceptional Changes to the Traineeship Programme at the Receiving Organisation/Enterprise (to be approved by e-mail or signature by the student, the responsible person in the Sending Institution and the responsible person in the Receiving Organisation/Enterprise) Planned period of the mobility: from [month/year] ……………. till [month/year] ……………. Traineeship title: … Number of working hours per week: … Detailed programme of the traineeship period: Knowledge, skills and competences to be acquired by the end of the traineeship (expected Learning Outcomes): Monitoring plan: Evaluation plan: After the Mobility Table D - Traineeship Certificate by the Receiving Organisation/Enterprise Name of the trainee: Name of the Receiving Organisation/Enterprise: Sector of the Receiving Organisation/Enterprise: Address of the Receiving Organisation/Enterprise [street, city, country, phone, e-mail address], website: Start date and end date of traineeship: from [day/month/year] …………………. to [day/month/year] ……………….. Traineeship title: Detailed programme of the traineeship period including tasks carried out by the trainee: Knowledge, skills (intellectual and practical) and competences acquired (achieved Learning Outcomes): Evaluation of the trainee: Date: Name and signature of the Supervisor at the Receiving Organisation/Enterprise:

  • Name and Organizational Changes (a) PSP must provide TFC with written notification of all name changes and organizational changes relating to PSP including, but not limited to, merger, acquisition, corporate reorganization, or sale no later than sixty (60) days prior to such change. PSP, in its notice, shall describe the circumstances of the name or organizational change, state its new name, provide the new Tax Identification Number, if available, and describe how the change will impact its ability to perform under the Agreement. All written notifications of organizational change must include a detailed statement specifying the change and supporting documentation evidencing continued right of Agreement or successor entity, as applicable, to maintain its status as a party to this Agreement. If the change entails personnel changes for personnel performing the responsibilities of the Agreement for PSP, PSP shall identify the new personnel and provide resumes to TFC, if resumes were originally required by the solicitation. TFC may require other information or documents related to the change and its impact on the PSP and Agreement shall supply the requested information within five (5) working days of receipt of the request.

  • Intergovernmental Organizations As instructed from time to time by ICANN, Registry Operator will implement the protections mechanism determined by the ICANN Board of Directors relating to the protection of identifiers for Intergovernmental Organizations. A list of reserved names for this Section 6 is available at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved. Additional names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Any such protected identifiers for Intergovernmental Organizations may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such protected identifiers shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. SPECIFICATION 6 REGISTRY INTEROPERABILITY AND CONTINUITY SPECIFICATIONS

  • Continuing Business Nothing in this Agreement will preclude or limit Red Hat from providing software, materials, or services for itself or other clients, irrespective of the possible similarity of such software, materials or services to those that might be delivered to Client. The terms of confidentiality in Section 9 will not prohibit or restrict either party's right to develop, use or market products or services similar to or competitive with the other party; provided, however, that neither party is relieved of its obligations under this Agreement.

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