Performing Agency Responsibility for System Agency’s Termination Costs If the System Agency terminates the Contract for cause, the Performing Agency shall be responsible to the System Agency for all costs incurred by the System Agency and the State of Texas to replace the Performing Agency. These costs include, but are not limited to, the costs of procuring a substitute vendor and the cost of any claim or litigation attributable to Performing Agency’s failure to perform any Work in accordance with the terms of the Contract.
Responsibilities of Customer 5.1 To the extent that the Supplier requires access to the Customer Site to perform the Services, the Customer shall provide such access during Normal Business Hours and to provide a suitable work environment to enable the Supplier to perform such Services subject to the Supplier complying with such internal policies and procedures of the Customer (including those relating to security and health and safety) as may be notified to the Supplier in writing from time to time.
5.2 The Customer shall co-operate with the Supplier in all matters relating to the Services and shall appoint a Representative (“Customer Representative”), who shall have authority to commit the Customer on all matters relating to the relevant Service.
5.3 The Customer agrees and acknowledges the terms of the applicable Licence Agreements, Customer Agreement and that such terms shall form part of this Agreement. For the avoidance of doubt, in the event the applicable Licence Agreements and/or Customer Agreement is not applicable to the Services being received or delivered by the Supplier to the Customer under this Agreement, such agreements shall not apply.
5.4 Customer shall;
(a) adhere to the Acceptable Use Policy;
(b) be a bona fide licenced user of all Third-Party Software used in the provision of the Services;
(c) co-operate with the Supplier in all matters relating to the Services as reasonably requested by the Supplier;
(d) adhere to the dates scheduled for provision of Services by the Supplier to the Customer as stated in the applicable Statement of Work or otherwise agreed between the Parties in writing. In the event the Customer wishes to reschedule or cancel the dates for the provision of Services, liquidated damages (“Liquidated Damages”) will become payable from the Customer to Supplier on the following basis:
(i) If dates are changed or cancelled at the Customer’s request more than 14 days before the scheduled start date no Liquidated Damages are payable.
(ii) If dates are changed or cancelled between 7 days and 14 days before the scheduled start date Liquidated Damages equivalent to 50% of the Fees for the Services to be provided at that time will be payable.
(iii) If dates are changed or cancelled less than 7 days before the scheduled start date Liquidated Damages equivalent to 100% of the Fees for the Services to be provided at that time will be payable.
(e) inform the Supplier of all health and safety rules and regulations and any other reasonable security requirements that apply at any of the Customer’s premises;
(f) in respect of any Microsoft funded services, sign and deliver the Microsoft Proof of Execution (XXX) within 7 days of the date of issue by Microsoft. In the event that the Customer does not return the XXX within the 7 days’ notice period, the Supplier may be entitled to charge the Customer the amounts directly and the Customer shall follow the payment terms in this Agreement.;
(g) maintain continuous global admin access to the Customer’s relevant Microsoft
(h) Where a Microsoft Cloud service is deployed / utilised within the project the Customer shall assign the Supplier to be the Digital Partner of Record for a minimum of twelve (12) months from project completion date;
(i) provide appropriate hardware interface, software and access authorisation to enable remote diagnosis, should such capability be required;
(j) provide all information and make available all resources as reasonably requested by Supplier in the execution of its obligations under this Agreement;
(k) use all reasonable efforts to follow the reasonable instructions of Supplier support personnel with respect to the resolution of defects;
(l) gather all relevant information prior to requesting assistance in respect of any defects including detailed defect description, and procedures required to replicate a problem if possible. Any additional information which may help in the diagnosis of a defect should be included such as network configuration details;
(m) agree that if, in the course of performing the Services, it is reasonably necessary for the Supplier’s performance of its obligations under a Statement of Work for Supplier to access or use any equipment, software or data of the Customer (or which is in the possession of the Customer) then it shall where it is able to do so grant to Supplier a non-exclusive, royalty free, terminable licence to use the same solely for the purpose of delivering the Services only for as long as is strictly necessary to deliver such Services; and
(n) provide network and user access between Customer’s and Supplier’s data centres.
5.5 To the extent that the Supplier requires access to the Customer’s Operating Environment to perform the Dedicated Support, the Customer shall use reasonable endeavours to provide such access during Normal Business Hours and to provide a suitable work environment to enable the Supplier to perform such Dedicated Support subject to the Supplier complying with such internal policies and procedures of the Customer (including those relating to security and health and safety) as may be notified to the Supplier in writing from time to time.
5.6 The Customer shall (unless otherwise specified in the Statement of Work or as otherwise set out in this Agreement):
(a) use the Services only for lawful purposes and in accordance with this Agreement;
(b) keep secure from third parties any passwords issued to the Customer by the Supplier;
(c) install or, permit the Supplier to install, the current version of software required to provide the Dedicated Support from time to time when upgrades or fixes occur and to provide a reasonable level of assistance in implementation and testing;
(d) provide notice of intention to change applicable Customer-side Equipment or Customer Operating Environment or data-feeds that will directly impact the Dedicated Support;
(e) comply with all applicable laws and regulations with respect to its activities under this Agreement, including those set out in Clause 20;
(f) carry out all other Customer responsibilities set out in this Agreement and the Statement of Work in a timely and efficient manner. In the event of any delays in the Customer's provision of such assistance as agreed by the Parties, the Supplier may adjust any timetable or delivery schedule set out in this Agreement as reasonably necessary;
(g) use the Third-Party Software and/or Software correctly in accordance with its operating instructions;
(h) notify Supplier promptly of any problems with the Third-Party Software and/or Software; and
(i) use only versions of the Third-Party Software and/or Software covered by Microsoft in mainstream or extended support unless otherwise agreed in writing.
5.7 In the event that the Customer is in breach of its obligations under the Agreement (excluding payment obligations) then the Supplier shall provide written notice of such breach, specifying in detail the nature of the breach and providing thirty (30) Business Days’ notice to remedy such breach if capable of remedy. If the Customer fails to remedy such breach the Supplier shall be entitled to terminate or suspend the Services without prejudice to any pre-existing rights and obligations of either Party. The Supplier shall have no liability or responsibility should the Services fail to comply with the Statement of Work and/or Service Level Agreements as a direct result of the Customer (including without limitation any of its employees, subcontractors or any of its staff) being in breach of the Agreement.
5.8 In the event that the Customer is in breach of its payment obligations under the Agreement then the Supplier shall provide written notice of such breach, specifying in detail the nature of the breach and providing thirty (30) days notice to remedy such breach if capable of remedy. If the Customer fails to remedy such breach the Supplier shall be entitled to terminate or suspend the Services without prejudice to any pre- existing rights and obligations of either Party. The Supplier shall have no liability or responsibility should the Services fail to comply with the Statement of Work and/or Service Level Agreements as a direct result of the Customer (including without limitation any of its employees, subcontractors or any of its staff) being in breach of the Agreement.
Patent Filing Responsibilities and Costs 1. The invention and patent rights herein apply to any patent application or patents covering an invention made under this Agreement. Each Party is responsible for its own costs of obtaining and maintaining patents covering sole inventions of its employees. The Parties may agree otherwise, upon the reporting of any invention (sole or joint) or in any license granted.
2. Partner shall include the following in patent applications for an invention made jointly between NASA employees, its Related Entity employees and Partner employees: The invention described herein may be manufactured and used by or for the U.S. Government for U.S. Government purposes without the payment of royalties thereon or therefore.
Responsibilities of the City The City’s Contract Manager will be responsible for exercising general oversight of the Contractor’s activities in completing the Scope of Work. Specifically, the Contract Manager will represent the City’s interests in resolving day-to-day issues that may arise during the term of this Contract, shall participate regularly in conference calls or meetings for status reporting, shall promptly review any written reports submitted by the Contractor, and shall approve all invoices for payment, as appropriate. The City’s Contract Manager shall give the Contractor timely feedback on the acceptability of progress and task reports.
Contractor Responsibility for System Agency’s Termination Costs If the System Agency terminates the Contract for cause, the Contractor shall be responsible to the System Agency for all costs incurred by the System Agency and the State of Texas to replace the Contractor. These costs include, but are not limited to, the costs of procuring a substitute vendor and the cost of any claim or litigation attributable to Contractor’s failure to perform any Work in accordance with the terms of the Contract.
RESPONSIBILITIES OF CITY City or its representative shall issue all communications to Contractor. City has the authority to request changes in the work in accordance with the terms of this Agreement and with the terms in Exhibit A – Scope of Work. City has the authority to stop work or to suspend any work.
Responsibilities of Contractor A. The Contractor shall perform all work on the described project as required by the Contract documents. The work to be performed includes the labor and services necessary to produce such replacement, and all materials, supplies, tools, transportation, equipment, and machinery required for replacement.
B. This project bid includes all materials, labor and equipment to complete the reconstruction and resurfacing of streets as outlined in the Project Manual for WWREYN - XXXXXXXX SANITARY SEWER - PHASE 1 dated March 25th, 2021 as outlined in Attachment A.
Responsibilities of Client a. Client shall exclusively retain the services of Consultant to perform the Scope of Work, in accordance with, and subject to, the other provisions of this Agreement.
b. Client shall provide access for Consultant and its subcontractors to the Site, and shall enter into access agreements with other third party property owners, as necessary for Consultant to complete the performance of the Scope of Work.
c. Client shall, as necessary to complete the Scope of Work: (i) cooperate and assist Consultant with the preparation and submittal, to PADEP, PAUSTIF, local governing authorities and others, of all information and documents including, without limitation, correspondence, notices, reports, data submittals, restrictive covenants, engineering and institutional controls, and the like; and (ii) implement and maintain any engineering or institutional controls.
d. Client shall transmit to Consultant copies of all documentation, correspondence, reports, and the like, sent or received by Client, regarding the Scope of Work at the Site.
e. Client shall make a good faith effort to minimize any and all interference with the progress of the Scope of Work if the Site is remodeled or otherwise modified. Client shall also make a good faith effort to place this condition on third parties that are not a party to this Agreement including, but not limited to, current owners, future owners, current operators, future operators, current lessees and future lessees.
Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES
Responsibilities of the District 12.1. The District shall examine the documents submitted by the Architect and shall render decisions so as to avoid unreasonable delay in the process of the Architect’s Services.
12.2. The District shall verbally or in writing advise Architect if the District becomes aware of any fault or defect in the Project, including any errors, omissions or inconsistencies in the Architect’s documents. Failure to provide such notice shall not relieve Architect of its responsibility therefore, if any.
12.3. Unless the District and Architect agree that a hazardous materials consultant shall be a Consultant of the Architect, the District shall furnish the services of a hazardous material consultant or other consultants when such services are requested in writing by Architect and deemed necessary by the District or are requested by the District. These services shall include: asbestos and lead paint survey; abatement documentation; and specifications related to said matters, which are to be incorporated into bid documents prepared by Architect. If the hazardous materials consultant is furnished by the District and is not a Consultant of the Architect, the specifications shall include a note to the effect that the hazardous materials consultant’s specifications are included in the Architect’s bid documents for the District’s convenience and have not been prepared or reviewed by the Architect. The note shall also direct questions about the hazardous materials consultant’s specifications related to asbestos and lead paint survey and/or abatement documentation to the preparer of the hazardous materials consultant’s specifications.
