Cost of the Work The sum of all allowable costs necessarily incurred and paid by Contractor in the proper performance of the Work.
Termination Due To Lack Of Funding Appropriation If, in the judgment of the Director of Accounts and Reports, Department of Administration, sufficient funds are not appropriated to continue the function performed in this agreement and for the payment of the charges hereunder, State may terminate this agreement at the end of its current fiscal year. State agrees to give written notice of termination to contractor at least 30 days prior to the end of its current fiscal year, and shall give such notice for a greater period prior to the end of such fiscal year as may be provided in this contract, except that such notice shall not be required prior to 90 days before the end of such fiscal year. Contractor shall have the right, at the end of such fiscal year, to take possession of any equipment provided State under the contract. State will pay to the contractor all regular contractual payments incurred through the end of such fiscal year, plus contractual charges incidental to the return of any such equipment. Upon termination of the agreement by State, title to any such equipment shall revert to contractor at the end of the State's current fiscal year. The termination of the contract pursuant to this paragraph shall not cause any penalty to be charged to the agency or the contractor.
Termination due to Force Majeure 13.5.1 If the Force Majeure Event or its effects continue to be present beyond the period as specified in Article 4.5.3, either Party shall have the right to cause termination of the Agreement. In such an event, this Agreement shall terminate on the date of such Termination Notice.
Material Occurrences Promptly notify Agent in writing upon the occurrence of (a) any Event of Default or Default; (b) any event, development or circumstance whereby any financial statements or other reports furnished to Agent fail in any material respect to present fairly, in accordance with GAAP consistently applied, the financial condition or operating results of any Borrower as of the date of such statements; (c) any accumulated retirement plan funding deficiency which, if such deficiency continued for two plan years and was not corrected as provided in Section 4971 of the Code, could subject any Borrower to a tax imposed by Section 4971 of the Code; (d) each and every default by any Borrower which might result in the acceleration of the maturity of any Indebtedness, including the names and addresses of the holders of such Indebtedness with respect to which there is a default existing or with respect to which the maturity has been or could be accelerated, and the amount of such Indebtedness; and (e) any other development in the business or affairs of any Borrower which could reasonably be expected to have a Material Adverse Effect; in each case describing the nature thereof and the action Borrowers propose to take with respect thereto.
Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.
Name Collision Occurrence Management 6.1. No-‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
Development of the Project 4.1 TSP's obligations in development of the Project:
a. for procuring and maintaining in full force and effect all Consents, Clearances and Permits, required in accordance with Law for development of the Project;
b. for financing, constructing, owning and commissioning each of the Element of the Project for the scope of work set out in Schedule 1 of this Agreement in accordance with:
i. the Electricity Act and the Rules made thereof;
ii. the Grid Code;
iii. the CEA Regulations applicable, and as amended from time to time, for Transmission Lines and sub-stations: • the Central Electricity Authority (Technical Standards for Connectivity to the Grid) Regulations, 2007; • Central Electricity Authority (Technical Standards for construction of Electrical Plants and Electric Lines) Regulation, 2010; • Central Electricity Authority (Grid Standard) Regulations, 2010; • Central Electricity Authority (Safety requirements for construction, operation and maintenance of Electrical Plants and Electrical Lines) Regulation, 2011; • Central Electricity Authority (Measures relating to Safety and Electricity Supply) Regulation, 2010; • Central Electricity Authority (Technical Standards for Communication System in Power System Operation) Regulations, 2020.
iv. Safety/ security Guidelines laid down by the Government;
v. Prudent Utility Practices, relevant Indian Standards and the Law; not later than the Scheduled COD as per Schedule 2 of this Agreement;
c. for entering into a Connection Agreement with the concerned parties in accordance with the Grid Code.
d. for owning the Project throughout the term of this Agreement free and clear of any encumbrances except those expressly permitted under Article 15 of this Agreement;
e. to co-ordinate and liaise with concerned agencies and provide on a timely basis relevant information with regard to the specifications of the Project that may be required for interconnecting the Project with the Interconnection Facilities;
f. for providing all assistance to the Arbitrators as they may require for the performance of their duties and responsibilities;
g. to provide to the Nodal Agency and CEA, on a monthly basis, progress reports with regard to the Project and its execution (in accordance with prescribed form) to enable the CEA to monitor and co-ordinate the development of the Project matching with the Interconnection Facilities;
h. to comply with Ministry of Power order no. 25-11/6/2018 – PG dated 02.07.2020 as well as other Guidelines issued by Govt. of India pertaining to this;
i. to procure the products associated with the Transmission System as per provisions of Public Procurement (Preference to Make in India) orders issued by Ministry of Power vide orders No. 11/5/2018 - Coord. dated 28.07.2020 for transmission sector, as amended from time to time read with Department for Promotion of Industry and Internal Trade (DPIIT) orders in this regard (Procuring Entity as defined in above orders shall deemed to have included Selected Bidder and/ or TSP). Also, to comply with Department of Expenditure, Ministry of Finance vide Order (Public Procurement No 1) bearing File No. 6/18/2019- PPD dated 23.07.2020, Order (Public Procurement No 2) bearing File No. 6/18/2019-PPD dated 23.07.2020 and Order (Public Procurement No. 3) bearing File No. 6/18/2019-PPD, dated 24.07.2020, as amended from time to time, regarding public procurement from a bidder of a country, which shares land border with India;
j. to submit to Nodal Agency information in the prescribed format [To be devised by Nodal Agency] for ensuring compliance to Article 4.1 i) above.
k. to comply with all its obligations undertaken in this Agreement.
4.2 Roles of the Nodal Agency in implementation of the Project:
4.2.1 Subject to the terms and conditions of this Agreement, the Nodal Agency shall be the holder and administrator of this Agreement and shall inter alia:
a. appoint an Independent Engineer within 90 days of the Effective Date
b. provide letters of recommendation to the concerned Indian Governmental Instrumentality, as may be requested by the TSP from time to time, for obtaining the Consents, Clearances and Permits required for the Project;
c. coordinate among TSP and upstream/downstream entities in respect of Interconnection Facilities; and
d. monitor the implementation of the Agreement and take appropriate action for breach thereof including revocation of guarantees, cancellation of Agreement, blacklisting etc
e. provide all assistance to the Arbitrators as required for the performance of their duties and responsibilities; and
f. perform any other responsibility (ies) as specified in this Agreement.
SCOPE OF THE WORK The Contractor shall furnish all the materials, perform all of the Work, and do all things required by the Contract Documents.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1.
6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>.
6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released.
6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Site Investigation Developer has made a careful investigation of the Site and is familiar with the requirements of the Contract Documents and has accepted the readily observable, existing conditions of the Site.
