Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.
Application Submission Submissions of a rental application does not guarantee approval or acceptance. It does not bind us to accept the application or to sign a Lease contact.
Updated Information Submission by Developer The updated information submission by the Developer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. Developer shall submit a completed copy of the Large Generating Facility data requirements contained in Appendix 1 to the Large Facility Interconnection Procedures. It shall also include any additional information provided to Connecting Transmission Owner for the Interconnection Feasibility Study and Interconnection Facilities Study. Information in this submission shall be the most current Large Generating Facility design or expected performance data. Information submitted for stability models shall be compatible with NYISO standard models. If there is no compatible model, the Developer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Developer’s data is different from what was originally provided to Connecting Transmission Owner and NYISO pursuant to an Interconnection Study Agreement among Connecting Transmission Owner, NYISO and Developer and this difference may be reasonably expected to affect the other Parties’ facilities or the New York State Transmission System, but does not require the submission of a new Interconnection Request, then NYISO will conduct appropriate studies to determine the impact on the New York State Transmission System based on the actual data submitted pursuant to this Article 24.3. Such studies will provide an estimate of any additional modifications to the New York State Transmission System, Connecting Transmission Owner’s Attachment Facilities, or System Upgrade Facilities or System Deliverability Upgrades based on the actual data and a good faith estimate of the costs thereof. The Developer shall not begin Trial Operation until such studies are completed. The Developer shall be responsible for the cost of any modifications required by the actual data, including the cost of any required studies.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users.
2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status.
2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Information Submission by Connecting Transmission Owner The initial information submission by Connecting Transmission Owner shall occur no later than one hundred eighty (180) Calendar Days prior to Trial Operation and shall include New York State Transmission System information necessary to allow the Developer to select equipment and meet any system protection and stability requirements, unless otherwise mutually agreed to by the Developer and Connecting Transmission Owner. On a monthly basis Connecting Transmission Owner shall provide Developer and NYISO a status report on the construction and installation of Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades, including, but not limited to, the following information: (1) progress to date; (2) a description of the activities since the last report; (3) a description of the action items for the next period; and (4) the delivery status of equipment ordered.
DOES THE SPR NEED TO BE UPDATED IF INFORMATION CHANGES Yes. It remains a continuing obligation of the principal or his/her authorized agent to update the SPR whenever any of the information provided on the initial form changes. The SPR needs to be filed with the County Department or County Division processing the application or matter. If and when an additional expenditure is incurred subsequent to the initial filing of the SPR, an amended SPR needs to be filed with the County Department or County Division where the original application, including the initial SPR, was filed. In most cases, the initial SPR needs to be filed with the other application forms. The SPR and any update must be filed with the appropriate County Department or County Division not less than seven (7) days prior to the BCC hearing date so that they may be incorporated into the BCC agenda packet. (See Section 2-354(b), Orange County Code.) When the matter is a discussion agenda item or is the subject of a public hearing, and any additional expenditure occurs less than 7 days prior to BCC meeting date or updated information is not included in the BCC agenda packet, the principal or his/her authorized agent is obligated to verbally present the updated information to the BCC when the agenda item is heard or the public hearing is held. When the matter is a consent agenda item and an update has not been made at least 7 days prior to the BCC meeting or the update is not included in the BCC agenda packet, the item will be pulled from the consent agenda to be considered at a future meeting.
The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.
ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
AUDIT OF LICENSED PRODUCT USAGE Contractor shall have the right to periodically audit, no more than annually, at Contractor’s expense, use of licensed Product at any site where a copy of the Product resides provided that: (i) Contractor gives Licensee(s) at least thirty (30) days advance written notice, (ii) such audit is conducted during such party’s normal business hours, (iii) the audit is conducted by an independent auditor chosen on mutual agreement of the parties. Contractor shall recommend a minimum of three (3) auditing/accounting firms from which the Licensee will select one (1). In no case shall the Business Software Alliance (BSA), Software Publishers Association (SPA), Software and Industry Information Association (SIIA) or Federation Against Software Theft (FAST) be used directly or indirectly to conduct audits, or be recommended by Contractor; (iv) Contractor and Licensee are each entitled to designate a representative who shall be entitled to participate, and who shall mutually agree on audit format, and simultaneously review all information obtained by the audit. Such representatives also shall be entitled to copies of all reports, data or information obtained from the audit; and (v) if the audit shows that such party is not in compliance, Licensee shall be required to purchase additional licenses or capacities necessary to bring it into compliance and shall pay for the unlicensed capacity at the NYS Net Price in effect at time of audit, or if none, then at the Contractor’s U.S. Commercial list price. Once such additional licenses or capacities are purchased, Licensee shall be deemed to have been in compliance retroactively, and Licensee shall have no further liability of any kind for the unauthorized use of the software.
