ILEARN Proficiency Sample Clauses

ILEARN Proficiency. (Benchmarks 1-2) 1. For ELA, the School Corporation shall see an increase in the percentage of students in grades 3-8 on the 2022-23 ILEARN state assessment as documented on the “Corporation Report Card” who are approaching proficiency, at proficiency, or above proficiency by the tiers outlined below as compared to the 2021-22 Corporation Report Card. The attainment date for this benchmark shall be the end of Year 1 of the Contract Term. Within ninety (90) days of publication of the Corporation Report Card by the Indiana Department of Education (“IDOE”), the Manager shall submit a letter to DUAB that documents the testing results and includes the Corporation Report Card. DUAB, in conjunction with IDOE, shall evaluate the Corporation Report Card for the School Corporation published by IDOE to determine if the benchmark has been achieved. Upon DUAB’s review of the Corporation Report Card and successful achievement of the benchmark, the Manager shall receive Benchmark Compensation in accordance with the applicable Achievement Tier as follows: Content/Category Tier Benchmark Compensation ILEARN Proficiency (ELA) 1 Increase by 2 Percentage Points $37,500 2 Increase by 4 Percentage Points $63,750 3 Increase by 7 Percentage Points $75,000 Benchmark Compensation for this benchmark shall not exceed $75,000.
AutoNDA by SimpleDocs

Related to ILEARN Proficiency

  • Limited English Proficiency The Grantee must comply with the Department of Justice Guidance pertaining to title VI of the Civil Rights Act of 1964, 42 U.S.C. § 2000d. Grantee must take reasonable steps to provide meaningful access to their program(s) and activities for persons with limited English proficiency (LEP). For information on the civil right responsibilities, see xxxx://xxx.xxx.xxx.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Cooperative Master Contract Sales Reporting. Contractor shall report total Cooperative Master Contract sales quarterly to Enterprise Services, as set forth below. Cooperative Master Contract Sales Reporting System. Contractor shall report quarterly Cooperative Master Contract sales in Enterprise Services’ Cooperative Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized Purchasers specified herein during the term of the Cooperative Master Contract. If there are no Cooperative Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Cooperative Master Contract Sales Reporting. Quarterly Cooperative Master Contract Sales Reports must be submitted electronically by the following deadlines for all Cooperative Master Contract sales invoiced during the applicable calendar quarter: Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.5 percent on the purchase price for all Cooperative Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Cooperative Master Contract sales invoiced (not including sales tax) x .015. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Cooperative Master Contract sales reported by Contractor. Contractor is not to remit payment until Contractor receives an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Cooperative Master Contract number, the year and quarter for which the VMF is being remitted, and Contractor’s name as set forth in this Cooperative Master Contract, if not already included on the face of the check. Contractor’s failure to report accurate total net Cooperative Master Contract sales, to submit a timely Cooperative Master Contract sales report, or to remit timely payment of the VMF to Enterprise Services, may be cause for Enterprise Services to suspend Contractor or terminate this Cooperative Master Contract or exercise remedies provided by law. Without limiting any other available remedies, the parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums, the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) calendar days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Cooperative Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Cooperative Master Contract Sales Report. Contractor shall provide to Enterprise Services a detailed annual Cooperative Master Contract sales report. Such report shall include, at a minimum: the Goods/Services sold (including, as applicable, item number or other identifier), per unit quantities sold, items and volumes purchased by Purchaser, shipment/delivery locations by Purchaser, and Cooperative Master Contract price. This report must be provided in an electronic format that can be read by Microsoft (MS) Excel. Such report is due within thirty (30) calendar days of the annual anniversary of the effective date of this Cooperative Master Contract.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopted for the employees of the Employer; 5.2 The Employee accepts that the purpose of the performance management system will be to provide a comprehensive system with specific performance standards to assist the employees and service providers to perform to the standards required; 5.3 The Employer must consult the Employee about the specific performance standards and targets that will be included in the performance management system applicable to the Employee; 5.4 The Employee undertakes to actively focus on the promotion and implementation of the key performance indicators (including special projects relevant to the employee’s responsibilities) within the local government framework; 5.5 The criteria upon which the performance of the Employee shall be assessed shall consist of two components, Operational Performance and Competencies both of which shall be contained in the Performance Agreement; 5.6 The Employee’s assessment will be based on his performance in terms of the outputs/outcomes (performance indicators) identified as per attached Performance Plan, which are linked to the KPAs, and will constitute 80% of the overall assessment result as per the weightings agreed to between the Employer and Employee; 5.7 The Competencies will make up the other 20% of the Employee’s assessment score. The Competencies are spilt into two groups, leading competencies (indicated in blue on the graph below) that drive strategic intent and direction and core competencies (indicated in green on the graph below), which drive the execution of the leading competencies. Strategic direc on and leadership People management Program and project management Financial management Change leadership Governance leadersip Moral competence Planning and organising Analysis and innova on Knowledge and informa on management Communica on Results and quality focus

  • Value Engineering The Supplier may prepare, at its own cost, a value engineering proposal at any time during the performance of the contract. The value engineering proposal shall, at a minimum, include the following; a) the proposed change(s), and a description of the difference to the existing contract requirements; b) a full cost/benefit analysis of the proposed change(s) including a description and estimate of costs (including life cycle costs) the Procuring Entity may incur in implementing the value engineering proposal; and c) a description of any effect(s) of the change on performance/functionality.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Services and Information for Persons with Limited English Proficiency A. Grantee shall take reasonable steps to provide services and information both orally and in writing, in appropriate languages other than English, to ensure that persons with limited English proficiency are effectively informed and can have meaningful access to programs, benefits and activities. Meaningful access may entail providing language assistance services, including oral interpretation and written translation, if necessary. More information can be found at xxxxx://xxx.xxx.xxx/. B. Grantee shall identify and document on the client records the primary language/dialect of a client who has limited English proficiency and the need for translation or interpretation services and shall not require a client to provide or pay for the services of a translator or interpreter. C. Grantee shall make every effort to avoid use of any persons under the age of 18 or any family member or friend of the client as an interpreter for essential communications with a client with limited English proficiency, unless the client has requested that person and using the person would not compromise the effectiveness of services or violate the client’s confidentiality and the client is advised that a free interpreter is available.

  • Performance Testing (a) All performance tests of the Project, including any Initial Performance Test required in Section 2 of Appendix VIII, will be performed in accordance with the test procedures set forth in Appendix VIII (“Performance Test”), including additional procedures and protocols related to Performance Testing as mutually agreed between Buyer and Seller (“Test Procedures”). Seller shall bear all costs and receive all revenues, if applicable, associated with all Performance Tests. (b) After the Initial Delivery Date and during the Delivery Term, Buyer will have the right to conduct a Performance Test (“Buyer Performance Test”) no more than once a calendar year to demonstrate whether the Project is capable of delivering the Distribution Services at the Contract Capacity. Within 30 calendar days following a Buyer Performance Test, Seller will have the right to retest the Project with a Performance Test (“Seller Retest”). For the avoidance of doubt, the results of any Seller Retest will supersede the results of the preceding Buyer Performance Test. (i) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at or above ninety-nine percent (99%) of the Initial Contract Capacity, the Contract Capacity will remain the Initial Contract Capacity; (ii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at more than or equal to eighty-five (85%) of the Initial Contract Capacity, but less than ninety-nine percent (99%) of the Initial Contract Capacity (“Testing Band”), the Contract Capacity will be automatically adjusted (upwards or downwards) to the capacity commensurate with the amount of Distribution Services the Project delivered during the Performance Test within the Testing Band. (iii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is not capable of delivering Distribution Services of at least eighty-five percent (85%) of the Initial Contract Capacity, an Event of Default shall occur in accordance with Section 7.1(a)(viii).

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Constructability Review Prepare detailed interdisciplinary constructability review within Fourteen (14) days of receipt of the plans from the District that: 10.1.2.1.6.1 Ensures construction documents are well coordinated and reviewed for errors; 10.1.2.1.6.2 Identifies to the extent known, construction deficiencies and areas of concern; 10.1.2.1.6.3 Back-checks design drawings for inclusion of modifications; and 10.1.2.1.6.4 Provides the District with written confirmation that: 10.1.2.1.6.4.1 Requirements noted in the design documents prepared for the Project are consistent with and conform to the District's Project requirements and design standards. 10.1.2.1.6.4.2 Various components have been coordinated and are consistent with each other so as to minimize conflicts within or between components of the design documents.

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