Transfer of Legacy Reference Service Delivery Sample Clauses

Transfer of Legacy Reference Service Delivery. Points at commencement of 2010 Access Arrangement
AutoNDA by SimpleDocs

Related to Transfer of Legacy Reference Service Delivery

  • Notification of Acceptance of General Offer of Privacy Terms Upon execution of Exhibit “E”, General Offer of Privacy Terms, Subscribing LEA shall provide notice of such acceptance in writing and given by personal delivery, or e-mail transmission (if contact information is provided for the specific mode of delivery), or first-class mail, postage prepaid, to the designated representative below. The designated representative for notice of acceptance of the General Offer of Privacy Terms is: Name: Xxxxx Xxxxxxxx Title: Technology Director Contact Information: xxxxx.xxxxxxxx@xxxxxxxxx.x00.xx.xx (000)000-0000 xxx 000

  • Notification of Acceptance of General Offer of Terms Upon execution of Exhibit “E”, General Offer of Terms, Subscribing LEA shall provide notice of such acceptance in writing and given by personal delivery, or e-mail transmission (if contact information is provided for the specific mode of delivery), or first-class mail, postage prepaid, to the designated representative below. The designated representative for notice of acceptance of the General Office of Privacy Terms is: Name: Title: Contact Information:

  • Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.

  • Sale of Note; Change of Loan Servicer; Notice of Grievance The Note or a partial interest in the Note (together with this Security Instrument) can be sold one or more times without prior notice to Borrower. A sale might result in a change in the entity (known as the “Loan Servicer”) that collects Periodic Payments due under the Note and this Security Instrument and performs other mortgage loan servicing obligations under the Note, this Security Instrument, and Applicable Law. There also might be one or more changes of the Loan Servicer unrelated to a sale of the Note. If there is a change of the Loan Servicer, Borrower will be given written notice of the change which will state the name and address of the new Loan Servicer, the address to which payments should be made and any other information RESPA requires in connection with a notice of transfer of servicing. If the Note is sold and thereafter the Loan is serviced by a Loan Servicer other than the purchaser of the Note, the mortgage loan servicing obligations to Borrower will remain with the Loan Servicer or be transferred to a successor Loan Servicer and are not assumed by the Note purchaser unless otherwise provided by the Note purchaser. Neither Borrower nor Lender may commence, join, or be joined to any judicial action (as either an individual litigant or the member of a class) that arises from the other party’s actions pursuant to this Security Instrument or that alleges that the other party has breached any provision of, or any duty owed by reason of, this Security Instrument, until such Borrower or Lender has notified the other party (with such notice given in compliance with the requirements of Section 15) of such alleged breach and afforded the other party hereto a reasonable period after the giving of such notice to take corrective action. If Applicable Law provides a time period which must elapse before certain action can be taken, that time period will be deemed to be reasonable for purposes of this paragraph. The notice of acceleration and opportunity to cure given to Borrower pursuant to Section 22 and the notice of acceleration given to Borrower pursuant to Section 18 shall be deemed to satisfy the notice and opportunity to take corrective action provisions of this Section 20.

  • ECR Number Environmental Commitment Record Requirements Description of ADOT Responsibilities TMP-3 The following measures will be implemented for the Selected Alternative: • All equipment exhaust systems will be in good working order. Properly designed engine enclosures and intake silencers will be used. • Equipment will be maintained on a regular basis. New equipment will be subject to new product emission standards. • Stationary equipment will be located as far away from sensitive receivers as possible. • Construction-related noise generators will be shielded from noise receivers (e.g., use temporary enclosures to shield generators or crushers, take advantage of site conditions to provide topographic separation). • Construction alerts will be distributed to keep the public informed of construction activities, and a toll-free number for construction-related complaints will be provided. • During the design phase, hours of operation will be evaluated to minimize disruptions during construction. ADOT to oversee for compliance TMP-4 Congestion from construction-related traffic will create temporary impacts in the project vicinity. The magnitude of these impacts will vary depending on the location of the sources of the fill material and of the disposition sites for surplus material, the land uses along the routes, the duration of hauling operations, staging locations, and the construction phasing. To identify acceptable routes and times of operation, ADOT, or its representative, will prepare an agreement with local agencies regarding hauling of construction materials on public streets. ADOT to oversee for compliance TP Attachment 000-0 Xxxxx Xxxxxxxx Xxxxxxx Project Record of Decision (ROD) Developer’s Environmental Commitment Requirements The following table includes the Project-specific environmental commitments as written in the ROD, with minor modifications for clarification purposes. As it relates to these Technical Provisions, references to freeway, project, South Mountain Freeway, proposed action, proposed freeway, and Selected Alternative mean the Project, and references to contractor mean Developer. Developer shall comply with and perform all of the contractor and ADOT requirements, including the ADOT obligations, commitments, and responsibilities, identified in the following table, except to the extent of those requirements that are specifically identified in the third column, entitled “Description of ADOT Responsibilities,” which are not delegated to Developer.

  • Certification Regarding Termination of Contract for Non-Compliance (Tex Gov. Code 552.374)

  • Transfer or Deletion of Student Data The Provider shall review, on an annual basis, whether the Student Data it has received pursuant to the DPA continues to be needed for the purpose(s) of the Service Agreement and this DPA. If any of the Student Data is no longer needed for purposes of the Service Agreement and this DPA, the Provider will provide written notice to the LEA as to what Student Data is no longer needed. The Provider will delete or transfer Student Data in readable form to the LEA, as directed by the LEA (which may be effectuated through Exhibit D of the DPA), within 30 calendar days if the LEA requests deletion or transfer of the Student Data and shall provide written confirmation to the LEA of such deletion or transfer. Upon termination of the Service Agreement between the Provider and LEA, Provider shall conduct a final review of Student Data within 60 calendar days. If the LEA receives a request from a parent, as that term is defined in 105 ILCS 10/2(g), that Student Data being held by the Provider be deleted, the LEA shall determine whether the requested deletion would violate State and/or federal records laws. In the event such deletion would not violate State or federal records laws, the LEA shall forward the request for deletion to the Provider. The Provider shall comply with the request and delete the Student Data within a reasonable time period after receiving the request. Any provision of Student Data to the LEA from the Provider shall be transmitted in a format readable by the LEA.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

Time is Money Join Law Insider Premium to draft better contracts faster.