Technical Support State Street will provide technical support to assist the Fund in using the System and the Data Access Services. The total amount of technical support provided by State Street shall not exceed 10 resource days per year. State Street shall provide such additional technical support as is expressly set forth in the fee schedule in effect from time to time between the parties (the “Fee Schedule”). Technical support, including during installation and testing, is subject to the fees and other terms set forth in the Fee Schedule.
Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").
Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.
Customer Support and Training System Agency will provide support for the CMBHS, including problem tracking and problem resolution. System Agency will provide telephone numbers for Grantees to obtain access to expert assistance for CMBHS-related problem resolution. System Agency will provide initial CMBHS training. Grantee shall provide subsequent ongoing end-user training.
Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.
Support and Services ISD and HC agree to the following conditions:
A. HC agrees to the following for both the mathematics and English language arts courses:
i. To share data and provide feedback regarding student success on entry‐level college mathematics and English language arts courses;
ii. To train advisors to recognize and honor course(s) on school district transcripts;
iii. To ensure that eligible students are counseled directly into college level mathematics, English language arts, and all other courses that require mathematics and English language arts college readiness;
B. HC agrees to the following for the college preparatory mathematics courses:
i. To provide the Student Learning Outcomes;
ii. To provide the syllabi for the courses being offered.
iii. To provide regular meetings between the HC faculty and ISD faculty teaching the course.
C. HC agrees to the following for the college preparatory English language arts course:
i. To provide the Student Learning Outcomes for Integrated Reading/Writing (INRW 0303) course;
ii. To provide the syllabi, including types of essays required (i.e., expository, persuasive, and critical analysis).
iii. To provide regular meetings between the HC faculty and ISD faculty teaching the course.
D. ISD agrees to the following for both the mathematics and English language arts courses:
i. To provide highly qualified instructors for the courses being taught;
ii. To identify students who are not college ready as stated in HB 5;
iii. To provide professional development and resources required to teach the mathematics and English language arts courses;
iv. To identify successful completion of the course(s) on the student transcripts as determined by the State of Texas PEIMS number;
v. To provide curriculum for the course that is consistent with HC Student Learning Outcomes;
vi. To provide assistance with admission, enrollment, and financial aid applications;
E. ISD agrees to the following for the college preparatory mathematics course:
i. To teach a math course designed to focus on college mathematics (algebraic or non‐algebraic) concepts;
ii. Require students to meet college readiness scores on the TSI Assessment;
iii. To meet regularly with HC faculty.
F. ISD agrees to the following for the college preparatory English language arts course:
i. To teach an integrated Reading and Writing course that focuses on critical reading and college‐level writing;
ii. Require students to meet college readiness scores on the TSI Assessment;
iii. To meet regularly with HC faculty.
Research Support (a) Having regard to the resources reasonably available for such purposes, the Operator will cooperate with AHS to provide such participation by its Staff as may be reasonable in relation to the carrying out of research within the Province.
(b) The Operator agrees to promptly notify AHS in the event that it undertakes or agrees to participate in any form of clinical trial, research project, instrument use, or similar activity which in any way relates to the Services provided under this Agreement. The Operator shall, upon request, provide AHS with written evidence of Client disclosure and consent to research.
Clinical Supply In connection with the Technology Transfer, Lexicon shall transfer to Sanofi any usable inventory of Licensed Compound or Licensed Product, subject to Lexicon’s retention of reasonable requirements of such Licensed Compound or Licensed Product for its T1DM Development activities no later than [**] (or such other date as is agreed by the Parties), and Lexicon’s Manufacturing Cost paid to Lexicon CMOs for such transferred quantities of inventory shall be treated as Development Costs and borne by the Parties in accordance with Section 7.6. Prior to the completion of the Technology Transfer in accordance with Section 6.2, Lexicon shall, to the extent requested by Sanofi and as mutually agreed by the Parties, supply clinical quantities of the Licensed Products and placebo for use by Sanofi in the Development of Licensed Products for T2DM in accordance with the Development Plan, and Lexicon’s Manufacturing Cost incurred in connection therewith shall be treated as Development Costs. After the Technology Transfer, Sanofi shall supply clinical quantities of the Licensed Products and placebo reasonably required by Lexicon for Lexicon’s use in the Development of Licensed Products for T1DM in accordance with the Development Plan and for its own use in the Development of Licensed Products. Lexicon shall Manufacture (or have Manufactured) all such Licensed Product in accordance with Applicable Law and the applicable specifications therefor, including, to the extent required by Applicable Law, cGMP; provided that Lexicon’s liability arising from a breach by the CMO of its agreement with Lexicon shall be limited to such recoveries as are obtained by Lexicon using Commercially Reasonable Efforts to obtain such recoveries and such other remedies as may be available to Lexicon for such breach under its agreement with such CMO. Otherwise, Sanofi’s sole and exclusive remedy and Lexicon’s sole and exclusive liability to Sanofi for any nonconformity shall be for Lexicon to replace such nonconforming Licensed Compound or Licensed Product with conforming Licensed Compound or Licensed Product within reasonable timelines to be mutually agreed by the Parties in writing, but nothing in this Section 6.1.1 shall limit Lexicon’s liability for Third Party Claims under ARTICLE 11. At either Party’s option, Lexicon and Sanofi shall enter into a clinical supply agreement and a reasonable and customary Quality Agreement that shall set forth the terms and conditions upon which Lexicon and any of its Affiliates will conduct their quality activities in connection with such supply, including (i) a right of Sanofi to audit Lexicon and the Lexicon CMOs, (ii) coordination regarding inspections by Regulatory Authorities and (iii) the exchange of information between the Parties regarding the foregoing and quality issues in general. Such agreements shall be negotiated and agreed by the Parties in good faith.
Operations Support Systems (OSS)
47.1. Embarq will offer unbundled access to Embarq’s operations support systems to the extent technically feasible in a non-discriminatory manner at Parity. OSS consists of pre- ordering, ordering, provisioning, maintenance and repair, and billing functions supported by Embarq’s databases and information. The OSS element includes access to all loop qualification information contained in Embarq’s databases or other records, including information on whether a particular loop is capable of providing advanced services.
Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.
