Related Requirements If the coverages have an expiration or renewal date occurring during the time for performance of this Agreement, Subrecipient must furnish renewal certificates to the email address and/or website location specified by the City. The receipt of any certificate does not constitute agreement by the City that the insurance requirements in this Agreement have been fully met or that the insurance policies indicated on the certificate are in compliance with all requirements of this Agreement. The failure of the City to obtain certificates or other insurance evidence from Subrecipient is not a waiver by the City of any requirements for Subrecipient to obtain and maintain the specified coverages. Subrecipient must advise all insurers of the Agreement provisions regarding insurance. Non-conforming insurance does not relieve Subrecipient of your obligation to provide insurance as specified here. Nonfulfillment of the insurance conditions may constitute a violation of this Agreement, and the City retains the right to stop work or Services or terminate this Agreement until proper evidence of insurance is provided. Subrecipient must provide for 30 days prior written notice to be given to the City in the event coverage is substantially changed, canceled or non-renewed. All deductibles or self- insured retentions on referenced insurance coverages must be borne by Subrecipient. Subrecipient hereby waives and agrees to require their insurers to waive their rights of subrogation against the City of Chicago, its employees, elected officials, agents or representatives. The coverages and limits furnished by Subrecipient in no way limit Subrecipient's liabilities and responsibilities specified within this Agreement or by law. Any insurance or self- insurance programs maintained by the City of Chicago do not contribute with insurance provided by Subrecipient under this Agreement. The required insurance to be carried is not limited by any limitations expressed in the indemnification language in this Agreement or any limitation placed on the indemnity in this Agreement given as a matter of law. If Subrecipient maintains higher limits than the minimums shown above, the City requires and shall be entitled to coverage for the higher limits maintained by Subrecipient. Any available insurance proceeds in excess of the specified minimum limits of insurance and coverage shall be available to the City. If Subrecipient is a joint venture or limited liability company, the insurance policies must name the joint venture or limited liability company as a named insured. Subrecipient must require all subcontractors to provide the insurance required in this Agreement, or Subrecipient may provide the coverages for subcontractors. All subcontractors are subject to the same insurance requirements of Subrecipient unless otherwise specified in this Agreement. Subrecipient must ensure that the City is an additional insured on the insurance required from Subcontractors. If Subrecipient or Subcontractors desire additional coverages, the party desiring additional coverages is responsible for the acquisition and cost of such additional protection. Notwithstanding any provisions in this Agreement to the contrary, the City of Chicago’s Risk Management Department maintains the right to modify, delete, alter or change these requirements.
Minimum Vendor Legal Requirements Vendor shall remain aware of and comply with this Agreement and all local, state, and federal laws governing the sale of products/services offered by Vendor under this contract. Such applicable laws, ordinances, and policies must be complied with even if not specified herein.
Course Approval Approval for dual credit shall be by the LEA and POSTSECONDARY INSTITUTION representatives on a course-by-course basis each semester based on the student’s prior coursework, career pathway, and/or academic readiness. There is no state limit to the number of credits a student may earn through dual credit in an academic term; however, the student must meet eligibility requirements.
ORDERING REQUIREMENTS Eligible Purchasers shall order Goods and/or Services from this Master Contract, consistent with the terms hereof and by using any ordering mechanism agreeable both to Contractor and Purchaser but including, at a minimum, a purchase order. When practicable, Contractor and Purchaser also shall use telephone orders, email orders, web-based orders, and similar procurement methods (collectively “Purchaser Order”). All Purchase Orders must reference the Master Contract number. The terms of this Master Contract shall apply to any Purchase Order and, in the event of any conflict, the terms of this Master Contract shall prevail. Notwithstanding any provision to the contrary, in no event shall any ‘click-agreement,’ software or web-based application terms and conditions, or any other agreement modify the terms and conditions of this Master Contract.
Metering Requirements Seller shall comply with all applicable rules in installing a meter appropriate for deliveries pursuant to the Full Buy/Sell or Excess Sale arrangement selected in paragraph 2.2, above, which can be electronically read daily by:
Proposal Requirements Proposals will be submitted in a Portable Document Format (“PDF”) file. Proposals will include the items below. Responses to items a. and b. are awarded 0 or 2 points.
Ongoing Trunk Forecast Requirements Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.
Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
HIPAA Requirements The Parties agree that the provisions under HIPAA Rules that are required by law to be incorporated into this Amendment are hereby incorporated into this Agreement.
Testing Requirements 12.1. Workplaces -
