Contractor to mitigate delay impacts. Contractor shall make all reasonable efforts to prevent and mitigate the effects of any delay, whether occasioned by an act of Force Majeure or otherwise.
Contractor to mitigate delay impacts Sample Clauses
Related to Contractor to mitigate delay impacts
Contractor Approach The Contractor shall develop, document, and implement BIDM Data Exchanges to obtain BIDM Imports from and to send BIDM Exports to CDPHE's CEDRS. 17.47.2.1. This exchange shall occur on a period as determined by the Department
Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.
Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.
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.
System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.
Contractor Key Personnel The Contractor shall assign a Corporate OASIS SB Program Manager (COPM) and Corporate OASIS SB Contract Manager (COCM) as Contractor Key Personnel to represent the Contractor as primary points-of-contact to resolve issues, perform administrative duties, and other functions that may arise relating to OASIS SB and task orders solicited and awarded under OASIS SB. Additional Key Personnel requirements may be designated by the OCO at the task order level. There is no minimum qualification requirements established for Contractor Key Personnel. Additionally, Contractor Key Personnel do not have to be full-time positions; however, the Contractor Key Personnel are expected to be fully proficient in the performance of their duties. The Contractor shall ensure that the OASIS SB CO has current point-of-contact information for both the COPM and COCM. In the event of a change to Contractor Key Personnel, the Contractor shall notify the OASIS SB CO and provide all Point of Contact information for the new Key Personnel within 5 calendar days of the change. All costs associated with Contractor Key Personnel duties shall be handled in accordance with the Contractor’s standard accounting practices; however, no costs for Contractor Key Personnel may be billed to the OASIS Program Office. Failure of Contractor Key Personnel to effectively and efficiently perform their duties will be construed as conduct detrimental to contract performance and may result in activation of Dormant Status and/or Off-Ramping (See Sections H.16. and H.17.).
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.
Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.
Duty to report Force Majeure Event 21.5.1 Upon occurrence of a Force Majeure Event, the Affected Party shall by notice report such occurrence to the other Party forthwith. Any notice pursuant hereto shall include full particulars of: (a) the nature and extent of each Force Majeure Event which is the subject of any claim for relief under this Article 21 with evidence in support thereof; (b) the estimated duration and the effect or probable effect which such Force Majeure Event is having or will have on the Affected Party’s performance of its obligations under this Agreement; (c) the measures which the Affected Party is taking or proposes to take for alleviating the impact of such Force Majeure Event; and (d) any other information relevant to the Affected Party’s claim. 21.5.2 The Affected Party shall not be entitled to any relief for or in respect of a Force Majeure Event unless it shall have notified the other Party of the occurrence of the Force Majeure Event as soon as reasonably practicable, and in any event no later than 10 (ten) days after the Affected Party knew, or ought reasonably to have known, of its occurrence, and shall have given particulars of the probable material effect that the Force Majeure Event is likely to have on the performance of its obligations under this Agreement. 21.5.3 For so long as the Affected Party continues to claim to be materially affected by such Force Majeure Event, it shall provide the other Party with regular (and not less than weekly) reports containing information as required by Clause 21.5.1, and such other information as the other Party may reasonably request the Affected Party to provide.
