Scope of the Project Under this Agreement, the scope of the Project (the “Scope of the Project”) shall mean and include:
(a) construction of the Project Highway on the Site set forth in Schedule- A and as specified in Schedule-B together with provision of Project Facilities as specified in Schedule-C, and in conformity with the Specifications and Standards set forth in Schedule-D;
(b) maintenance of the Project Highway in accordance with the provisions of this Agreement and in conformity with the requirements set forth in Schedule-E; and
(c) performance and fulfilment of all other obligations of the Contractor in accordance with the provisions of this Agreement and matters incidental thereto or necessary for the performance of any or all of the obligations of the Contractor under this Agreement.
Details of the Processing The subject-matter of Processing of Personal Data by Data Processor is the performance of the Services pursuant to the Agreement. The duration of the Processing, the nature and purpose of the Processing, as well as the types of Personal Data Processed and categories of Data Subjects under this DPA are further specified in Schedule 1 (Details of the Processing) to this DPA.
RISK OF THE PROPERTY As from the time of the sale, the Property shall be at the sole risk of the Purchaser as regards to loss or damage of whatsoever nature or howsoever occurring including by fire or other accidents, state of cultivation, non-occupation or otherwise.
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.
CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.
Development of the Property Except as modified by this Agreement, the Development and the Property will be developed in accordance with all applicable local, state, and federal regulations, including but not limited to the City’s ordinances and the zoning regulations applicable to the Property, and such amendments to City ordinances and regulations that that may be applied to the Development and the Property under Chapter 245, Texas Local Government Code, and good engineering practices (the “Applicable Regulations”). If there is a conflict between the Applicable Regulations and the Development Standards, the Development Standards shall control.
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>.
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.
Previously Reviewed Receivable; Duplicative Tests If any Review Receivable was included in a prior Review, the Asset Representations Reviewer will not conduct additional Tests on such Review Receivable, but will include the previously reported Test results in the Review Report for the current Review. If the same Test is required for more than one representation and warranty, the Asset Representations Reviewer will only perform the Test once for each Review Receivable, but will report the results of the Test for each applicable representation and warranty on the Review Report.
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.
