Use of Modified Days Sample Clauses

Use of Modified Days. Elementary School Modified Days A minimum of two (2) modified Wednesdays each month shall be designated as Preschool- age Special Education -5th Grade Teacher planning days. The first and third Wednesdays of each month shall be designated as District inservice/planning days. The second and fourth Wednesdays of each month shall be designated as Teacher planning days. These days may be changed by mutual agreement by the site administrator and OVTA site representative. Middle School Modified Days Ten (10) Modified Thursdays, one early release day each month, will be designated at the Middle Schools for staff meetings, professional learning communities, collaboration time, professional development, and planning time (See Appendix T for 2021-22 Dates). The Association School Site Representative(s) and the school site Principal shall collaboratively determine the Teachers’ needs for professional development and professional growth.
AutoNDA by SimpleDocs
Use of Modified Days. Elementary School Modified Days A minimum of two (2) modified Wednesdays each month shall be designated as Preschool- age Special Education -5th Grade Teacher planning days. The first and third Wednesdays of each month shall be designated as District inservice/planning days. The second and fourth Wednesdays of each month shall be designated as Teacher planning days. These days may be changed by mutual agreement by the site administrator and OVTA site representative. Middle School Modified Days (See MOU for 2019-2020)

Related to Use of Modified Days

  • Severability and Modification To the extent permitted by applicable law, the parties agree that any term or provision of this Agreement (or part thereof) that renders such term or provision (or part thereof) or any other term or provision (or part thereof) of this Agreement invalid or unenforceable in any respect shall be severable and shall be modified or severed to the extent necessary to avoid rendering such term or provision (or part thereof) invalid or unenforceable, and such severance or modification shall be accomplished in the manner that most nearly preserves the benefit of the parties’ bargain hereunder.

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e). (b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.

  • Terms of Modified/Restructured Loan 16 1st Trial Payment Due Date 20090119 17 Modification Effective Date 20090419 Net Unpaid Principal Balance (net of forbearance & 18 principal reduction) 467188 19 Principal forbearance 0 20 Principal reduction 0 21 Product (fixed or step) step 22 Remaining amortization term 480 23 Maturity date 20490119 24 Interest rate 0.02159 25 Next Payment due date 20090601 26 Monthly payment - P&I 1454 27 Monthly payment - T&I 1000 Total monthly payment 2454 28 Next reset date 20140501 29 Interest rate change per adjustment 0.01000 30 Lifetime interest rate cap 0.05530 31 Back end DTI 0.45000 same as Unpaid Principal Balance before 4 above restructuring/modification 450000 34 Accrued interest, limited to 90 days 7313 35 Attorney's fees 0 Foreclosure costs, including title search, filing fees, 36 advertising, etc. 500 37 Property protection costs, maint. and repairs 0 38 Tax and insurance advances 2500 Other Advances 39 Appraisal/Broker's Price Opinion fees 100 40 Inspections 0 41 Other 0 Total loan balance due before restructuring 460413 42 MI contribution 0 43 Other credits 0 44 T & I escrow account balances, if positive Total Cash Recovery 0 45 Discount rate for projected cash flows 0.05530 46 Loan prepayment in full 120 47 NPV of projected cash flows (see amort schd1) 386927 48 Gain/Loss Amount 73485 Line item definitions can be found in SFR Data Submission Handbook.

  • Severability and Modification of Covenants Employee acknowledges and agrees that each of the Restrictive Covenants is reasonable and valid in time and scope and in all other respects. The parties agree that it is their intention that the Restrictive Covenants be enforced in accordance with their terms to the maximum extent permitted by law. Each of the Restrictive Covenants shall be considered and construed as a separate and independent covenant. Should any part or provision of any of the Restrictive Covenants be held invalid, void, or unenforceable, such invalidity, voidness, or unenforceability shall not render invalid, void, or unenforceable any other part or provision of this Agreement or such Restrictive Covenant. If any of the provisions of the Restrictive Covenants should ever be held by a court of competent jurisdiction to exceed the scope permitted by the applicable law, such provision or provisions shall be automatically modified to such lesser scope as such court may deem just and proper for the reasonable protection of the Company’s legitimate business interests and may be enforced by the Company to that extent in the manner described above and all other provisions of this Agreement shall be valid and enforceable.

  • ACCEPTANCE OF CONTRACT/TERMS AND CONDITIONS (a) This Contract integrates, merges, and supersedes any prior offers, negotiations, and agreements concerning the subject matter hereof and constitutes the entire agreement between the parties. (b) SELLER's acknowledgment, acceptance of payment, or commencement of performance, shall constitute SELLER's unqualified acceptance of this Contract. (c) Unless expressly accepted in writing by LOCKHEED XXXXXX, additional or differing terms or conditions proposed by SELLER or included in SELLER's acknowledgment are objected to by LOCKHEED XXXXXX and have no effect. (d) The headings used in this Contract are inserted for the convenience of the parties and shall not define, limit, or describe the scope or the intent of the provisions of this Contract.

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by XXX to return or destroy Student Data. Except for Subprocessors, Xxxxxxxx agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.

  • DESCRIPTION OF CONTRACT MODIFICATION This contract modification is made in accordance with Exhibit E-Revised-1, Contractual Terms and Conditions, Section 22. CHANGES, to be made part hereof for all pertinent purposes. The changes are as follows:

  • Description of Goods or Services and Additional Terms and Conditions The Contractor shall perform as set forth in Exhibit A. For purposes of this Contract, to perform and the performance in Exhibit A is referred to as “Perform” and the “Performance.”

  • Severability; Modification All provisions of this Agreement are severable from one another, and the unenforceability or invalidity of any provision of this Agreement shall not affect the validity or enforceability of the remaining provisions of this Agreement, but such remaining provisions shall be interpreted and construed in such a manner as to carry out fully the intention of the parties. Should any judicial body interpreting this Agreement deem any provision of this Agreement to be unreasonably broad in time, territory, scope or otherwise, it is the intent and desire of the parties that such judicial body, to the greatest extent possible, reduce the breadth of such provision to the maximum legally allowable parameters rather than deeming such provision totally unenforceable or invalid.

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