Process for Recovery of Funding If the Funder, acting reasonably, determines that a recovery of Funding under section 5.1 is appropriate, then the Funder will give 30 Days’ Notice to the HSP. The Notice will describe: the amount of the proposed recovery; the term of the recovery, if not permanent; the proposed timing of the recovery; the reasons for the recovery; and the amendments, if any, that the Funder proposes be made to the HSP’s obligations under this Agreement. Where the HSP disputes any matter set out in the Notice, the parties will discuss the circumstances that resulted in the Notice and the HSP may make representations to the Funder about the matters set out in the Notice within 14 Days of receiving the Notice. The Funder will consider the representations made by the HSP and will advise the HSP of its decision. Funding recoveries, if any, will occur in accordance with the timing set out in the Funder’s decision. No recovery of Funding will be implemented earlier than 30 Days after the delivery of the Notice.
Instructions for Operators This agreement is intended to be provided to an Operator from a LEA. The Operator should fully read the agreement and is requested to complete the below areas of the agreement. Once the Operator accepts the terms of the agreement, the Operator should wet sign the agreement and return it to the LEA. Once the LEA signs the agreement, the LEA should provide a signed copy of the agreement to the Operator. Cover Page Box # 3 Official Name of Operator Cover Page Box # 4 Date Signed by Operator Recitals Box #5 Contract Title for Service Agreement Recitals Box #6 Date of Service Agreement Article 7 Boxes #7-10 Operator’s designated representative Signature Page Boxes #15-19 Authorized Operator’s representative signature Exhibit A Box #25 Description of services provided Exhibit B All Applicable Boxes Operator notates if data is collected to provide the described services. Defines the schedule of data required for the Operator to provide the services outlined in Exhibit A Exhibit D All Applicable Boxes (Optional Exhibit): Defines deletion or return of data expectations by LEA Exhibit E All Applicable Boxes (Optional Exhibit): Operator may, by signing the Form of General Offer of Privacy Terms (General Offer, attached as Exhibit E), be bound by the terms of this DPA to any other Subscribing LEA who signs the acceptance in said Exhibit. Exhibit F Boxes # 25-29 A list of all Subprocessors used by the Operator to perform functions pursuant to the Service Agreement, list security programs and measures, list Operator’s security measures
Solicitations for Subcontracts Including Procurements of Materials and Equipment. In all solicitations either by competitive bidding or negotiation made by the Engineer for work to be performed under a subcontract, including procurements of materials or leases of equipment, each potential subcontractor/subconsultant or supplier shall be notified by the Engineer of the Engineer's obligations under this Contract and the Regulations relative to nondiscrimination on the grounds of race, color, or national origin.
Mechanisms for Cooperation Pursuant to Article 149 (Objectives), the Parties hereby establish a Committee on Cooperation comprising representatives of each Party.
Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
GRIEVANCE REPORT FORM Grievance # School District Distribution of Form 1. Superintendent
Supplemental Provisions for Resecuritization This Agreement may be supplemented by means of the addition of a separate Article hereto (a "Supplemental Article") for the purpose of resecuritizing any of the Certificates issued hereunder, under the following circumstances. With respect to any Class or Classes of Certificates issued hereunder, or any portion of any such Class, as to which the Company or any of its Affiliates (or any designee thereof) is the registered Holder (the "Resecuritized Certificates"), the Company may deposit such Resecuritized Certificates into a new REMIC, grantor trust, FASIT or custodial arrangement (a "Restructuring Vehicle") to be held by the Trustee pursuant to a Supplemental Article. The instrument adopting such Supplemental Article shall be executed by the Company, the Master Servicer and the Trustee; provided, that neither the Master Servicer nor the Trustee shall withhold their consent thereto if their respective interests would not be materially adversely affected thereby. To the extent that the terms of the Supplemental Article do not in any way affect any provisions of this Agreement as to any of the Certificates initially issued hereunder, the adoption of the Supplemental Article shall not constitute an "amendment" of this Agreement. Each Supplemental Article shall set forth all necessary provisions relating to the holding of the Resecuritized Certificates by the Trustee, the establishment of the Restructuring Vehicle, the issuing of various classes of new certificates by the Restructuring Vehicle and the distributions to be made thereon, and any other provisions necessary for the purposes thereof. In connection with each Supplemental Article, the Company shall deliver to the Trustee an Opinion of Counsel to the effect that (i) the Restructuring Vehicle will qualify as a REMIC, grantor trust, FASIT or other entity not subject to taxation for federal income tax purposes and (ii) the adoption of the Supplemental Article will not endanger the status of the Trust Fund as a REMIC or (subject to Section 10.01(f)) result in the imposition of a tax upon the Trust Fund (including but not limited to the tax on prohibited transactions as defined in Section 860F(a)(2) of the Code and the tax on contributions to a REMIC as set forth in Section 860G(d) of the Code).
Applications for Payment 9.3.1 At least ten days before the date for each progress payment established in the State- Contractor Agreement, the Contractor shall submit to the Architect an itemized Application for Payment, notarized if required, supported by such data substantiating the Contractor's right to payment as the State or the Architect may require. The application for payment must, at a minimum, reflect retainage and the required waivers of lien and any other support documentation enumerated elsewhere in the Contract Documents.
9.3.2 Unless otherwise provided in the Contract Documents, payments will be made on account of materials or equipment not incorporated in the Work but delivered and suitably stored at the site and, if approved in advance by the State, payments may similarly be made for materials or equipment suitably stored at some other location agreed upon in writing. Payments for materials or equipment stored on or off the site shall be conditioned upon submission by the Contractor of bills of sale or such other procedures satisfactory to the State to establish the State's title to such materials or equipment or otherwise protect the State's interest, including applicable insurance and transportation to the site for those materials and equipment stored off the site.
9.3.3 The Contractor warrants that title to all Work, materials and equipment covered by an Application for Payment will pass to the State either by incorporation in the construction or upon the receipt of payment by the Contractor, whichever occurs first, free and clear of all liens, claims, security interests or encumbrances, hereinafter referred to in this Article 9 as "liens"; and that no Work, materials or equipment covered by an Application for Payment will have been acquired by the Contractor, or by any other person performing Work at the site or furnishing materials and equipment for the Project, subject to an agreement under which an interest therein or an encumbrance thereon is retained by the seller or otherwise imposed by the Contractor or such other person.
Solicitations for Subcontracts, Including Procurements of Materials and Equipment In all solicitations either by competitive bidding or negotiation made by the Engineer for work to be performed under a subcontract, including procurements of materials or leases of equipment, each potential subcontractor or supplier shall be notified by the Engineer of the Engineer's obligations under this contract and the Regulations relative to nondiscrimination on the grounds of race, color, or national origin.
REQUESTS FOR FLEXIBLE WORKING ARRANGEMENTS 49.1 Employee may request change in working arrangements s.65 of the Act. Note 1: Section 65 of the Act provides for certain Employees to request a change in their working arrangements because of their circumstances, as set out in s.65(1A).
