Logic of the Intervention
Logic of the Intervention Sample Clauses
Related to Logic of the Intervention
Intervention If the Commission finds deficiencies in the School's performance or legal compliance, the Commission and the School shall follow the Intervention Protocol attached as Exhibit D. Intervention may be initiated when the Commission finds that the School has failed to: (a) Comply with applicable laws, rules, policies, or procedures; (b) Comply with the terms and conditions of this Contract; or (c) Meet performance expectations as set forth in the Performance Frameworks. Failure to invoke the Intervention Protocol shall not be (i) construed as a waiver or relinquishment of any requirement under applicable laws, rules, policies, procedures, contractual terms and conditions, or performance expectations; or (ii) deemed a necessary precedent to non-renewal or revocation.
Interventions 1. Door to balloon time 2. Door to needle time 3. No interventions b. Discharge status 1. Home
Regulatory Intervention In the event that there is any change to any applicable statutes, enactments, acts of legislatures or parliament, laws, ordinances, orders, rules, by-laws or regulations of any government or statutory authority in India including but not limited to the Ministry of Information and Broadcasting and The Telecom Regulatory Authority or any final un-appealable order of any competent court or tribunal, etc, which would have a material adverse effect on either of the Parties, then the affected Party may request that the Parties consult as soon as reasonably practicable with a view to negotiating in good faith an amendment to this Agreement including but not limited to the Subscription Fee payable hereunder. Such amendment shall take effect from the date of such change. In the event the Parties are unable to agree on an amendment within thirty (30) days of the date of the request by the affected Party, then either Party may approach TDSAT for appropriate resolution of the dispute.
Name Collision Occurrence Management 6.1. No-‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
Performance Monitoring A. Performance Monitoring of Subrecipient by County, State of California and/or HUD shall consist of requested and/or required written reporting, as well as onsite monitoring by County, State of California or HUD representatives. B. County shall periodically evaluate Subrecipient’s progress in complying with the terms of this Contract. Subrecipient shall cooperate fully during such monitoring. County shall report the findings of each monitoring to Subrecipient. C. County shall monitor the performance of Subrecipient against the goals, outcomes, milestones and performance standards required herein. Substandard performance, as determined by County, will constitute non-compliance with this Contract for which County may immediately terminate the Contract. If action to correct such substandard performance is not taken by Subrecipient within the time period specified by County, payment(s) will be denied in accordance with the provisions contained in this Paragraph 47 of this Contract. D. HUD in accordance with 24 CFR Part 570 Subpart O, 570.902, will annually review the performance of County to determine whether County has carried out its Community Development Block Grant (CDBG) assisted activities in a timely manner and has significantly disbursed CDBG funds and met the mandated “1.5 ratio” threshold. Subrecipient is responsible to ensure timely drawdown of funds.
Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;
Performance of the Work The Contractor shall perform all of the Work required for the complete and prompt execution of everything described or shown in, or reasonably implied from the Contract Documents for the above referenced Project.
Outcomes Secondary: Career pathway students will: have career goals designated on SEOP, earn concurrent college credit while in high school, achieve a state competency certificate and while completing high school graduation requirements.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.
