COLLABORATIVE ACTIONS WE AGREE Sample Clauses

COLLABORATIVE ACTIONS WE AGREE. TO TAKE We agree to the following collaborative actions to work towards the above- noted process outcomes for this point where our work intersects:  CA#1: The service plan will include a jointly developed (CAS, VAW and the woman) and agreed to risk reduction strategy, including a safety plan for mother and child(ren) such as providing advocacy for and facilitating access to any other services deemed appropriate.  CA#2: The woman should be provided with pro-active support and advocacy regarding applications for housing, social assistance, and other community supports, e.g. Supportive letters or advocacy strategies. This is especially important if the woman does not choose to access a community women’s resource that could provide this advocacy.  CA#3: Where appropriate, VAW agencies and CAS will support the woman through any actions involving institutions and agencies such as the police, Crown Attorneys, Family Court, Criminal Court, and Justices of the Peace.  CA#4: Options for laying of criminal charges, obtaining restraining orders and sole possession of home, etc. should be explored with the woman, in particular if she does not wish to access the resource of woman abuse services. At the same time, however, it is critical that the woman be assured that she also has the right not to proceed with legal options.  CA#5: No referrals should be made to services such as couple counselling, mediation or alternative dispute mechanisms where the woman is required to engage with the abuser.  CA#6: The CAS worker, where contact with the abusive partner is possible, will facilitate the use of and coordinate the initial referral to use of Partner Assault Response.  CA#7: The CAS will include consideration of the safety/lethality assessments from all VAW agencies involved before developing the plan of service. INTERSECTION POINT# 4: VAW WORKER IS TRYING TO DETERMINE WHETHER A SITUATION CONSTITUTES REASONABLE GROUNDS TO SUSPECT THAT A CHILD MAY BE IN NEED OF PROTECTION. A) NO REPORT TO CAS IS REQUIRED B) A REPORT TO CAS IS REQUIRED 4.1 OUTCOMES TO BE ACHIEVED  Where needed, the VAW worker informally seeks information from a CAS worker to assist in making the decision as to whether a situation constitutes reasonable grounds that a child may be in need of protection.  (In communities where they exist) the mother receives information about non-protective CAS services regardless of whether a report is made.  If a report is made to the CAS, the VAW agency provides a...
Sample 1
AutoNDA by SimpleDocs

Related to COLLABORATIVE ACTIONS WE AGREE

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date. 31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must: 31.2.1 work proactively and in good faith with each of the Buyer’s contractors 31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services

  • Research Collaboration 3.7.1 Aarvik shall carry out the activities of each Work Item and deliver the required Data Package and/or deliverables in accordance with the applicable SOW. Without limiting the generality of the foregoing, Aarvik shall, in accordance with the applicable SOWs and the timeline approved by JRC, apply the Aarvik IP to (i) design and synthesize Collaboration Compounds, and (ii) by itself or through subcontractor(s), [***]. During the Research Term, if any Party identifies any Third Party Patent or Know-How that is necessary or reasonably useful for any activity under the SOWs but has not been included in the Aarvik IP, then such Party shall immediately inform the other Party and the Parties shall discuss in good faith the need of obtaining a license from such Third Party. 3.7.2 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver the Data Packages and all other deliverables required under the [***], as well as the results of the Patentability and FTO Analysis as described in Section 3.2.3, to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1. 3.7.3 If, upon completion of the [***] for the Collaboration Program, AxxxXxxx decides not to advance the Collaboration Program to [***], ArriVent may terminate the Collaboration Program. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1. 3.7.4 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing. 3.7.5 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent. 3.7.6 Within [***] ([***]) days after completion of the [***], Aarvik shall deliver to ArriVent a full report on all key results and findings of the Collaboration Program, and such other data, results and information as ArriVent may deem necessary for it to determine whether or not to exercise the Option (the “Full Report”).

  • Research Matters By entering into this Agreement, the Placement Agent does not provide any promise, either explicitly or implicitly, of favorable or continued research coverage of the Company and the Company hereby acknowledges and agrees that the Placement Agent’s selection as a placement agent for the Offering was in no way conditioned, explicitly or implicitly, on the Placement Agent providing favorable or any research coverage of the Company. In accordance with FINRA Rule 2711(e), the parties acknowledge and agree that the Placement Agent has not directly or indirectly offered favorable research, a specific rating or a specific price target, or threatened to change research, a rating or a price target, to the Company or inducement for the receipt of business or compensation.

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.

  • Research Independence The Company acknowledges that each Underwriter’s research analysts and research departments, if any, are required to be independent from their respective investment banking divisions and are subject to certain regulations and internal policies, and that such Underwriter’s research analysts may hold and make statements or investment recommendations and/or publish research reports with respect to the Company and/or the offering that differ from the views of its investment bankers. The Company hereby waives and releases, to the fullest extent permitted by law, any claims that the Company may have against such Underwriter with respect to any conflict of interest that may arise from the fact that the views expressed by their independent research analysts and research departments may be different from or inconsistent with the views or advice communicated to the Company by such Underwriter’s investment banking divisions. The Company acknowledges that the Representative is a full service securities firm and as such from time to time, subject to applicable securities laws, may effect transactions for its own account or the account of its customers and hold long or short position in debt or equity securities of the Company.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Clinical Trials The studies, tests and preclinical and clinical trials conducted by or on behalf of, or sponsored by, the Company, or in which the Company has participated, that are described in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus, or the results of which are referred to in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus, were and, if still pending, are being conducted in all material respects in accordance with protocols, procedures and controls pursuant to, where applicable, accepted professional and scientific standards for products or product candidates comparable to those being developed by the Company and all applicable statutes, rules and regulations of the FDA, the EMEA, Health Canada and other comparable drug and medical device (including diagnostic product) regulatory agencies outside of the United States to which they are subject; the descriptions of the results of such studies, tests and trials contained in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus do not contain any misstatement of a material fact or omit a material fact necessary to make such statements not misleading; the Company has no knowledge of any studies, tests or trials not described in the Disclosure Package and the Prospectus the results of which reasonably call into question in any material respect the results of the studies, tests and trials described in the Registration Statement, the Time of Sale Disclosure Package or Prospectus; and the Company has not received any notices or other correspondence from the FDA, EMEA, Health Canada or any other foreign, state or local governmental body exercising comparable authority or any Institutional Review Board or comparable authority requiring or threatening the termination, suspension or material modification of any studies, tests or preclinical or clinical trials conducted by or on behalf of, or sponsored by, the Company or in which the Company has participated, and, to the Company’s knowledge, there are no reasonable grounds for the same. Except as disclosed in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus, there has not been any violation of law or regulation by the Company in its respective product development efforts, submissions or reports to any regulatory authority that could reasonably be expected to require investigation, corrective action or enforcement action.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

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