Compliance Between Individual Contract and Master Agreement Any individual contract between the Board and an individual employee, heretofore or hereafter executed, shall be subject to and consistent with the terms and conditions of this Agreement. If an individual contract contains any language inconsistent with this Agreement, this Agreement, during its duration, shall be controlling.
Agreement Overview This SLA operates in conjunction with, and does not supersede or replace any part of, the Agreement. It outlines the information technology service levels that we will provide to you to ensure the availability of the application services that you have requested us to provide. All other support services are documented in the Support Call Process.
Quality Agreement If appropriate or if required by Applicable Law, the parties will also agree upon a Quality Agreement containing quality assurance provisions for the Manufacture of Product (“Quality Agreement”), which agreement will also be attached to the applicable Work Order and incorporated by reference in the Work Order.
CERTIFICATION REGARDING CERTAIN FOREIGN-OWNED COMPANIES IN CONNECTION WITH CRITICAL INFRASTRUCTURE (Texas law as of September 1, 2021) By submitting a proposal to this Solicitation, you certify that you agree to the following required by Texas law as of September 1, 2021: Proposing Company is prohibited from entering into a contract or other agreement relating to critical infrastructure that would grant to the company direct or remote access to or control of critical infrastructure in this state, excluding access specifically allowed by the Proposing Company for product warranty and support purposes. Company, certifies that neither it nor its parent company nor any affiliate of company or its parent company, is (1) owned by or the majority of stock or other ownership interest of the company is held or controlled by individuals who are citizens of China, Iran, North Korea, Russia, or a designated country; (2) a company or other entity, including governmental entity, that is owned or controlled by citizens of or is directly controlled by the government of China, Iran, North Korea, Russia, or a designated country; or (3) headquartered in China, Iran, North Korea, Russia, or a designated country. For purposes of this contract, “critical infrastructure” means “a communication infrastructure system, cybersecurity system, electric grid, hazardous waste treatment system, or water treatment facility.” See Tex. Gov’t Code § 2274.0101(2) of SB 1226 (87th leg.). The company verifies and certifies that company will not grant direct or remote access to or control of critical infrastructure, except for product warranty and support purposes, to prohibited individuals, companies, or entities, including governmental entities, owned, controlled, or headquartered in China, Iran, North Korea, Russia, or a designated country, as determined by the Governor.
Pharmacovigilance Agreement Within [***] after the Effective Date, BMS and the Company (under the guidance of their respective Pharmacovigilance Departments, or equivalent thereof) shall define and finalize the responsibilities the Parties shall employ to protect patients and promote their well-being in connection with the use of the Licensed Compound(s) until such time that all pharmacovigilance responsibilities have transferred from BMS to Company. These responsibilities shall include mutually acceptable guidelines and procedures for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of adverse event reports, pregnancy reports, and any other information concerning the safety of any Licensed Compound(s). Such guidelines and procedures shall be in accordance with, and enable the Parties and their Affiliates to fulfill, local and international regulatory reporting obligations to government authorities. Furthermore, such agreed procedures shall be consistent with relevant International Council for Harmonization (ICH) guidelines, except where said guidelines may conflict with existing local regulatory safety reporting requirements, in which case local reporting requirements shall prevail. Until such guidelines and procedures are set forth in a written agreement between the Parties (hereafter referred to as the “Pharmacovigilance Agreement”), the Party responsible for pharmacovigilance prior to execution of this Agreement shall have sole Pharmacovigilance responsibility for the Licensed Compound(s) subject to all applicable regulations and guidelines. In the event that this Agreement is terminated, the Parties agree to implement the necessary procedures and practices to ensure that any outstanding pharmacovigilance reporting obligations are fulfilled. Certain information marked as [***] has been excluded from this exhibit because it is both (i) not material and (ii) would be competitively harmful if publicly disclosed.
Performance and Compliance with Contracts and Credit and Collection Policy The Seller shall (and shall cause the Servicer to), at its expense, timely and fully perform and comply with all material provisions, covenants and other promises required to be observed by it under the Contracts related to the Receivables, and timely and fully comply in all material respects with the applicable Credit and Collection Policies with regard to each Receivable and the related Contract.
END USER AGREEMENTS (“EUA H-GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC
DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.
Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.
Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: