Our Obligations Some obligations placed on us under this contract may be carried out by another person. If an obligation is placed on us to do something under this contract, then: (a) we are taken to have complied with the obligation if another person does it on our behalf; and (b) if the obligation is not complied with, we are still liable to you for the failure to comply with this contract.
USER OBLIGATIONS As a user of the Website or Services, You may be asked to register with Us. When You do so, You will choose a user identifier, which may be Your email address or another term, as well as a password. You may also provide personal information, including, but not limited to, Your name. You are responsible for ensuring the accuracy of this information. This identifying information will enable You to use the Website and Services. You must not share such identifying information with any third party, and if You discover that Your identifying information has been compromised, You agree to notify Us immediately in writing. Email notification will suffice. You are responsible for maintaining the safety and security of Your identifying information as well as keeping Us apprised of any changes to Your identifying information. Providing false or inaccurate information, or using the Website or Services to further fraud or unlawful activity is grounds for immediate termination of this Agreement.
▇▇▇▇▇ OBLIGATIONS A ▇▇▇▇▇▇▇'s acceptance of funds directly under the Grant or indirectly through a subaward acts as acceptance of the authority of the State, under the direction of the legislative audit committee, to conduct an audit or investigation in connection with those funds. In accordance with the legislative audit committee, DFPS can request any documentation, at any time, to be sent to DFPS to a location DFPS chooses. Examples of documentation that DFPS may request include, but are not limited to: 1. Participant files in their entirety. This includes, but is not limited to: a. Progress notes. b. Action plans. c. Registration forms. d. Surveys. e. Sign-in sheets. f. Monthly tracking forms.
Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.
Buyer Obligations During the Delivery Term, Buyer shall arrange and be responsible for transmission service, including risk of transmission outage or curtailment, from the Delivery Point and bear all risks and costs associated with such transmission service, including, but not limited to, any transmission outages or curtailment. During the Delivery Term, Buyer shall Schedule or arrange for Scheduling Coordinator services with its Transmission Providers to receive the Product at the Delivery Point. During the Delivery Term, Buyer shall be responsible for all CAISO costs and charges, electric transmission losses and congestion from the Delivery Point.