Maintenance Agreement The parties will abide by the terms of the Maintenance Agreement including the capacity to dispute the classification in accordance with the Maintenance Agreement (Information Appendix C).
Yield Maintenance Agreement The Trustee is hereby authorized and directed to, and agrees that it shall, enter into the Yield Maintenance Agreement on behalf of the Trust Fund.
Routine Maintenance (i) CRC shall be responsible for Routine Maintenance when necessary or desirable to maintain the Shared Assets in a safe operating condition, and to permit and facilitate (A) the performance by CRC of its obligations pursuant to this Agreement, and (B) the use of Shared Assets by the Operators in accordance with this Agreement. (ii) CSXT or NSR, directly or through their respective affiliates, may perform the work which CRC performed prior to the date of this Agreement when (A) CRC does not possess the skills needed for such work, (B) CRC lacks the necessary employees to do such work in a timely fashion, or (C) CRC does not possess the equipment needed to do such work. CRC and the party performing the work shall agree to a reasonable fee for such work prior to performance. CRC, CSXT and NSR may agree to have additional work performed either by CSXT, NSR or their affiliates.
Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.
Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.
Aircraft Maintenance Operator shall, at its own expense, cause the Aircraft to be inspected, maintained, serviced, repaired, overhauled, and tested in accordance with FAR Part 91 so that the Aircraft will remain in good operating condition and in a condition consistent with its airworthiness certification and shall take such requirements into account in scheduling the Aircraft hereunder, including but not limited compliance with applicable airworthiness directives and service bulletins. Performance of maintenance, preventive maintenance or inspection shall not be delayed or postponed for the purpose of scheduling the Aircraft unless such maintenance or inspection can safely be conducted at a later time in compliance with applicable laws, regulations and requirements, and such delay or postponement is consistent with the sound discretion of the pilot-in-command. In the event that any non-standard maintenance is required during the term and will interfere with User’s requested or scheduled flights, Operator, or Operator’s pilot-in-command, shall notify User of the maintenance required, the effect on the ability to comply with User’s requested or scheduled flights and the manner in which the parties will proceed with the performance of such maintenance and conduct of such flight(s). In no event shall Operator be liable to User or any other person for loss, injury or damage occasioned by the delay or failure to furnish the Aircraft under this Agreement, whether or not maintenance-related.
Software Maintenance Subrecipient shall apply security patches and upgrades in a timely manner and keep virus software up-to-date on all systems on which State data may be stored or accessed.
Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.
Master Services Agreement This Agreement is a master agreement governing the relationship between the Parties solely with regard to State Street’s provision of Services to each BTC Recipient under the applicable Service Modules.
Document Retention and Record Maintenance The HSP will (a) retain all records (as that term is defined in FIPPA) related to the HSP’s performance of its obligations under this Agreement for 7 years after the termination or expiration of the term of this Agreement; (b) keep all financial records, invoices and other finance-related documents relating to the Funding or otherwise to the Services in a manner consistent with either generally accepted accounting principles or international financial reporting standards as advised by the HSP’s auditor; and (c) keep all non-financial documents and records relating to the Funding or otherwise to the Services in a manner consistent with all Applicable Law.
