Operational Run-In Sample Clauses

Operational Run-In. The Run-In period will extend for a minimum of 30 days from the start of substantial operations with cutover of substantial input and output lines. This period of time shall be discussed and agreed to by all parties during the SSTP development process, and reconfirmed at the completion of the ISAT. Substantial Operations shall normally be defined as when the CBIS is processing 80% or greater of its normal (not peak) operational daily load of “checked bags or luggage”. This period shall also be dependent on resolution of deficiencies found during testing and Run-In. Once a week during the Run- In period, the AIRPORT SPONSOR or their authorized representatives shall forward electronic versions of all CBIS Reports required by PGDS to the TSA RMD and Acceptance Test Contractor. After receipt, review and analysis of at least 21 days of performance data, TSA and their Acceptance Test Contractor will deploy to the site to physically verify closure of open deficiencies, and observe system operation against the data reported. During this time, measurements of belt speeds for security tracking zone conveyors will be performed. These Run-In period measurements will be recorded and reported together with similar measurements made during mobilization for ISAT testing. Based on the data analysis and physical observations, a recommendation will be made to TSA via a Test Summary Report (TSR) to end the Run-In period, extend the Run-In period, and/or change the operational status of the CBIS.
Sample 1
AutoNDA by SimpleDocs

Related to Operational Run-In

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Project Implementation The Borrower shall:

  • Operating Plan To Agent and Lenders, as soon as available, but not later than thirty (30) days after the end of each Fiscal Year, an annual combined operating plan (the "Operating Plan") for Parent and its Subsidiaries, approved by the Board of Directors of Parent, for the following Fiscal Year, which (i) includes a statement of all of the material assumptions on which such plan is based, (ii) includes projected monthly income statement, balance sheets and source and use of funds for the following year and (iii) Borrowing Availability projections, all prepared on the same basis and in similar detail as that on which operating results are reported (and in the case of cash flow projections, representing management's good faith estimates of future financial performance based on historical performance), and including plans for personnel, Capital Expenditures and facilities.

  • Timescale It is recognised that discussions around actual salary increases have a dependency on top level Company decisions. However, it is agreed that more general discussions can start before this point, these will include: The Company providing the latest pay and benefit guidelines/comparators (if updated) By end of January Identify and attempt to agree deviations from information detailed in appendix 4. By 16th March The Company providing information as detailed in Appendix 4 (snapshot as of 1st April) (incorporating any agreed deviations from the standard list) By 10th April Joint team produce cost-model ready for negotiations By end of April Unite Submit and present to the Company negotiating team their annual pay claim By end of April Line Managers completing Appraisals (including Company checking of employees who don’t have a PAC) January – March where possible By end of April in all cases Company provides remainder of appraisal PAC information By 7th May Negotiate non-budget related matters By end May Once the Company decisions referred to above have been made, the pay negotiations can further progress. Steps will be taken earlier where practicable. Stage 1 negotiations Offer voted on by 14th June If required stage 2 negotiations Offer voted on by 30th June If required stage 3 negotiations Offer voted on by 14 th July Guidelines issued to line managers (following discussions between Unite & the Company) By 22nd July Pay planning complete By end July Pay review effective 1st August Company provides UNITE with information, snapshot at 1st August By 10th August Notification of pay review to individuals by managers Before August pay date At the start of the process, UNITE and the company will jointly review the timetable and agree any variations that are required.

  • OFFICE OF MANAGEMENT AND BUDGET (OMB) AUDIT REQUIREMENTS The parties shall comply with the requirements of the Single Audit Act of 1984, P.L. 98-502, ensuring that the single audit report includes the coverage stipulated in 2 CFR 200.

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

  • General Compliance This Agreement is intended to comply with Section 409A or an exemption thereunder and shall be construed and administered in accordance with Section 409A. Notwithstanding any other provision of this Agreement, payments provided under this Agreement may only be made upon an event and in a manner that complies with Section 409A or an applicable exemption. Any payments under this Agreement that may be excluded from Section 409A either as separation pay due to an involuntary separation from service or as a short-term deferral shall be excluded from Section 409A to the maximum extent possible. For purposes of Section 409A, each installment payment provided under this Agreement shall be treated as a separate payment. Any payments to be made under this Agreement upon a termination of employment shall only be made upon a “separation from service” under Section 409A. Notwithstanding the foregoing, the Company makes no representations that the payments and benefits provided under this Agreement comply with Section 409A, and in no event shall the Company be liable for all or any portion of any taxes, penalties, interest, or other expenses that may be incurred by the Executive on account of non-compliance with Section 409A.

  • Commissioning Commissioning tests of the Interconnection Customer’s installed equipment shall be performed pursuant to applicable codes and standards. The ISO and Connecting Transmission Owner must be given at least five Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.

  • Disaster Recovery and Business Continuity The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!