Overview of Information Requirements Sample Clauses

Overview of Information Requirements. This Appendix B governs the information that must be received by the ISO from Market Parties for Generator Deactivation Solutions, including Initiating Generators, Generator Deactivation Solutions proposed pursuant to Section 38.4 of Attachment FF, and Generators that have submitted a statement of intent or are otherwise required by the ISO to submit this information pursuant to 38.5 of this Attachment FF. The term “information” as used in this Appendix B and in Attachment FF includes all sources and types of information and data. The information required by this Appendix shall be separately stated from and is in addition to the information requirements for Generators in certain outages set forth in Section 5.18 of the ISO Services Tariff, the information required by the ISO pursuant to Section 23.4.5.6 of the ISO Services Tariff, and the Generator Deactivation Process project information requirements set forth in Section 38.4 of this Attachment FF. If the information required by this Appendix does not exist on the date due to the ISO, the Market Party shall promptly provide it to the ISO if and when it does exist in whole or in part.
AutoNDA by SimpleDocs

Related to Overview of Information Requirements

  • Information Requirements (a) The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder of Registrable Securities and take such further reasonable action as any Holder of Registrable Securities may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder of Registrable Securities, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company's most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Information Requirement The successful bidder's shall be required to advise the Office of Management and Budget, Government Support Services of the gross amount of purchases made as a result of the contract.

  • Publication Requirements Those seeking to include renderings of more than 10 images from the UND Biometrics Database in reports, papers, and other documents to be published or released must first obtain approval in writing from the UND Principal Investigator. In no case should the face images be used in a way that could cause the original subject embarrassment or mental anguish.

  • Special Formalities and Information Requirements 1. Nothing in Article 10.3 shall be construed to prevent a Party from adopting or maintaining a measure that prescribes special formalities in connection with covered investments, such as a requirement that investors be residents of the Party or that covered investments be legally constituted under the laws or regulations of the Party, provided that such formalities do not materially impair the protections afforded by a Party to investors of the other Party and covered investments pursuant to this Chapter.

  • Documentation Requirements (a) An employee must apply for personal leave in writing in the form required by the CEO as soon as it is reasonably practicable for the employee to make the application.

  • Information Required Such records must contain the name; Social Security number; last known address, telephone number, and email address of each such worker; each worker's correct classification(s) of work actually performed; hourly rates of wages paid (including rates of contributions or costs anticipated for bona fide fringe benefits or cash equivalents thereof of the types described in 40 U.S.C. 3141(2)(B) of the Xxxxx-Xxxxx Act); daily and weekly number of hours actually worked in total and on each covered contract; deductions made; and actual wages paid.

  • Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave.

  • Freedom of Information 23.1 The Supplier acknowledges that the Authority is subject to the requirements of the FOIA and the Environmental Information Regulations and shall assist and co-operate with the Authority to enable the Authority to comply with its Information disclosure obligations.

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

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