Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation
Information and Services Required of the Owner The Owner shall provide information with reasonable promptness, regarding requirements for and limitations on the Project, including a written program which shall set forth the Owner’s objectives, constraints, and criteria, including schedule, space requirements and relationships, flexibility and expandability, special equipment, systems, sustainability and site requirements.
Certification Regarding Prohibition of Boycotting Israel (Tex Gov. Code 2271)
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK
Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.
Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years.
b. Renewal registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms not exceeding a total of ten years.
c. Upon change of sponsorship of the registration of a Registered Name from one registrar to another, according to Part A of the ICANN Policy on Transfer of Registrations between Registrars, the term of registration of the Registered Name shall be extended by one year, provided that the maximum term of the registration as of the effective date of the sponsorship change shall not exceed ten years.
d. The change of sponsorship of registration of Registered Names from one registrar to another, according to Part B of the ICANN Policy on Transfer of Registrations between Registrars shall not result in the extension of the term of the registration and Registry Operator may assist in such change of sponsorship.
Procurement of the Site (i) The Authority Representative, the Contractor and Authority’s Engineer shall, within 10 (ten) days of the date of this Agreement, inspect the Site and prepare a detailed memorandum containing an inventory of the Site including the vacant and unencumbered land, buildings, structures, road works, trees and any other immovable property on or attached to the Site (hereinafter referred to as the “Handover Memorandum”). Subject to the provisions of Clause 8.2 (iii), the Handover Memorandum shall have appended thereto an appendix (the “Appendix”) specifying in reasonable detail those parts of the Site to which vacant access and Right of Way has not been given to the Contractor along with details of hindrances in the Construction Zone. For sake of clarity the Handover Memorandum shall clearly specify the parts of Site where work can be executed. Signing of the Handover Memorandum, in three counterparts (each of which shall constitute an original), by the authorized representatives of the Authority, Contractor and Authority’s Engineer shall be deemed to constitute a valid evidence of giving the Right of Way to the Contractor for discharging its obligations under and in accordance with the provisions of this Agreement and for no other purpose whatsoever.
(ii) Whenever the Authority is ready to hand over any part or parts of the Site included in the Appendix, it shall inform the Contractor, by notice, of the proposed date and time such of hand over. The Authority Representative and the Contractor shall, on the date so notified, inspect the specified parts of the Site, and prepare a memorandum containing an inventory of the vacant and unencumbered land, buildings, structures, road works, trees and any other immovable property on or attached to the Site so handed over. The signing of the memorandum, in three (3) counterparts (each of which shall constitute an original), by the authorised representatives of the Parties shall be deemed to constitute a valid evidence of giving the relevant Right of Way to the Contractor. If the contractor fails to join for site inspection or disputes the parts of the site available for work, the Authority’s Engineer shall decide the parts of the site where work can be executed and notify to both the parties within 3 days of the proposed date of inspection. The parties agree that such notification of the Authority’s Engineer as mentioned hereinabove shall be final and binding on the parties.
(iii) The Authority shall provide the Right of Way to the Contractor in respect of all land included in the Appendix by the date specified in Schedule-A for those parts of the Site referred to therein, and in the event of delay for any reason other than Force Majeure or breach of this Agreement by the Contractor, it shall pay to the Contractor, Damages in a sum calculated in accordance with Clause 8.3. The Contractor agrees that it shall not be entitled to claim any other damages on account of any such delay by the Authority.
(iv) Notwithstanding anything to the contrary contained in this Clause 8.2, the Authority shall specify the parts of the Site, if any, for which Right of Way shall be provided to the Contractor on the dates specified in Schedule-A. Such parts shall also be included in the Appendix prepared in pursuance of Clause 8.2 (i).
(v) The Authority further acknowledges and agrees that prior to the Appointed Date, it shall have procured issuance of the statutory notification under Applicable Laws for vesting of all the land comprising the Project in the Authority and has taken possession of area for Construction Zone for at least 90% (ninety per cent) of the total length of the Project Highway. The Parties also acknowledge and agree that the conditions specified in this Clause 8.2 (iii) shall not be modified or waived by either Party.
(vi) For the avoidance of doubt, the Parties expressly agree that the Appendix shall in no event contain sections of the Project Highway the cumulative length of which exceeds 10% (ten percent) of the total length of the Project Highway.
(vii) Pursuant to signing of Handover Memorandum under clause 8.2 (i), Contractor shall submit to the Authority’s Engineer, a monthly land possession report till expiry of 180 (one hundred and eighty) days from Appointed Date, in respect of those parts of the site to which vacant access and right of way was not given to the contractor and included in Appendix to the memorandum signed under clause 8.2 (i), duly specifying the part of the site, if any, for which the right of way is yet to be handed over.
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.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers.
9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA.
9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
