Logical Model Sample Clauses

Logical Model. Critical Assumptions P4EG’s success in achieving the intended results assumes that private and public sector counterparts and representatives are willing and committed to engaging in P4EG activities. To that end, Activity indicators and targets have been selected based on the following assumptions about the national environment: • Government of North Macedonia macroeconomic and microeconomic policies and priorities remain stable and in line with the USG interest, particularly the goals of the Activity; • Activity participants and partners are willing to collaborate and comply with USAID data and information requirements for reporting; • Absence of socio-political instabilities, including national and regional scenarios; • Absence of extreme natural and economic shocks. 2 COLLABORATING, LEARNING, AND ADAPTING The Collaborating, Learning and Adapting (CLA)1 approach for P4EG reflects the strategy of USAID North Macedonia to xxxxxx collaboration between USAID and its Macedonian partners to enable adaptive approaches to achieve its objectives, informed by ongoing systems and contextual analysis. The Activity will continually assess the effectiveness of activities and interventions to evaluate whether those interventions are succeeding, apply lessons learned and adapt the work plan, methodologies, and approaches appropriately. Through a proactive CLA approach, P4EG actively supports collaborating with both internal and external stakeholders to understand and provide data for their information needs. The XXX Manager will work with the principal stakeholders of the Project to identify the core principles that will guide the data collection and dissemination: 1) participation of the internal and external partners in articulating the information needs to inform Project implementation; 2) sharing the information collected on a regular basis through workshops and meetings, as well as special CLA events; and 3) active discussions of changes based on the data about the way in which activities could be improved. P4EG staff will share the information quarterly with USAID and invite USAID staff to participate in the dialogue with partners, while at the same time participate in USAID Partner meetings and other info and lessons learned sessions. P4EG will also take part in USAID Partner meetings as well as other information and lesson-learned sessions.
Sample 1
AutoNDA by SimpleDocs

Related to Logical Model

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

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

  • Purchase Order Pricing/Product Deviation If a deviation of pricing/product on a Purchase Order or contract modification occurs between the Vendor and the TIPS Member, TIPS must be notified within five (5) business days of receipt of change order. TIPS reserves the right to terminate this agreement for cause or no cause for convenience with a thirty (30) days prior written notice. Termination for convenience is conditionally required under Federal Regulations 2 CFR part 200 if the customer is using federal funds for the procurement. All purchase orders presented to the Vendor, but not fulfilled by the Vendor, by a TIPS Member prior to the actual termination of this agreement shall be honored at the option of the TIPS Member. The awarded Vendor may terminate the agreement with ninety (90) days prior written notice to TIPS 0000 XX Xxx Xxxxx, Xxxxxxxxx, Xxxxx 00000. The vendor will be paid for goods and services delivered prior to the termination provided that the goods and services were delivered in accordance with the terms and conditions of the terminated agreement. This termination clause does not affect the sales agreements executed by the Vendor and the TIPS Member customer pursuant to this agreement. TIPS Members may negotiate a termination for convenience clause that meets the needs of the transaction based on applicable factors, such as funding sources or other needs. Usually, purchase orders or their equal are issued by participating TIPS Member to the awarded vendor and should indicate on the order that the purchase is per the applicable TIPS Agreement Number. Orders are typically emailed to TIPS at xxxxxx@xxxx-xxx.xxx. • Awarded Vendor delivers goods/services directly to the participating member. • Awarded Vendor invoices the participating TIPS Member directly. • Awarded Vendor receives payment directly from the participating member. • Fees are due to TIPS upon payment by the Member to the Vendor. Vendor agrees to pay the participation fee to TIPS for all Agreement sales upon receipt of payment including partial payment, from the Member Entity or as otherwise agreed by TIPS in writing and signed by an authorized signatory of TIPS.

  • Development Program RWJPRI shall be [**] and have [**] in consultation with the JDAC, to select LICENSED COMPOUNDS which shall then be designated PRODUCTS for further DEVELOPMENT by RWJPRI and marketing by ORTHO and its AFFILIATES. RWJPRI shall provide KOSAN with written notice of its decision to select a LICENSED COMPOUND for DEVELOPMENT. Once a PRODUCT has been selected for further DEVELOPMENT, RWJPRI, with the advice of the JDAC, shall have the [**] right to develop the PRODUCT through STAGES O, I, II and III and shall have the [**] right to prepare and file, and shall be the owner of, all applications for MARKETING AUTHORIZATION throughout the world. During such DEVELOPMENT efforts, KOSAN will assist RWJPRI as may be mutually agreed, at RWJPRI's expense, in chemical development, formulation development, production of labeled material and production of sufficient quantities of material for STAGE O and initial STAGE I studies. RWJPRI shall exercise diligent efforts, commensurate with the efforts it would normally exercise for products with similar potential sales volume and consistent with its overall business strategy, in developing such PRODUCT in accordance with the DEVELOPMENT PLAN established by RWJPRI. In the course of such efforts RWJPRI shall, either directly or through an AFFILIATE or SUBLICENSEE to which the license shall have been extended, take appropriate steps including the following: (i) in consultation with the JDAC, select certain LICENSED COMPOUNDS for STAGE O DEVELOPMENT; and (ii) establish and maintain a program reasonably designed, funded and resourced to obtain information adequate to enable the preparation and filing with an appropriate and properly empowered national regulatory authority all necessary documentation, data and [**] CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. other evidence required for IND non-rejection to commence and conduct human clinical trials of such PRODUCT. (iii) proceed following IND non-rejection to commence PHASE I, II, and III clinical trials, associated studies and such other work which RWJPRI reasonably deems to be required for subsequent inclusion in filings for MARKETING AUTHORIZATION; (iv) after such submissions are filed prosecute such submissions and file all reasonably necessary, reports and respond to all reasonable requests from the pertinent regulatory, authorities for information, data, samples, tests and the like.

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