Listing and Maintenance Requirements The Common Stock is registered pursuant to Section 12(b) or 12(g) of the Exchange Act, and the Company has taken no action designed to, or which to its knowledge is likely to have the effect of, terminating the registration of the Common Stock under the Exchange Act nor has the Company received any notification that the Commission is contemplating terminating such registration. The Company has not, in the 12 months preceding the date hereof, received notice from any Trading Market on which the Common Stock is or has been listed or quoted to the effect that the Company is not in compliance with the listing or maintenance requirements of such Trading Market. The Company is, and has no reason to believe that it will not in the foreseeable future continue to be, in compliance with all such listing and maintenance requirements.
Project Maintenance The Local Government shall be responsible for maintenance of locally owned roads and locally owned facilities after completion of the work. The State shall be responsible for maintenance of the state highway system after completion of the work if the work was on the state highway system, unless otherwise provided for in existing maintenance agreements with the Local Government.
Installation and Maintenance Except for the bi‐directional and production metering equipment owned by the City, all equipment on Customer’s side of the delivery point, including the required disconnect device, shall be provided and maintained in satisfactory operating condition by Customer and shall remain the property and responsibility of the Customer. The City will bear no responsibility for the installation or maintenance of Customer’s equipment or for any damage to property as a result of any failure or malfunction thereof. The City shall not be liable, directly or indirectly for permitting or continuing to allow the interconnection of the Facility or for the acts or omissions of Customer or the failure or malfunction of any equipment of Customer that causes loss or injury, including death, to any party.
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.
Maintenance and Support Services If this Agreement is for IT goods or services, this section applies: Unless otherwise specified in this Agreement: The Contractor shall promptly provide the Court with all Upgrades, including without limitation: (i) all Upgrades generally made available by Contractor to its other customers; (ii) Upgrades as necessary so that the Work complies with the Specifications and Applicable Law (including changes in Applicable Law); (iii) Upgrades as necessary so that the Work operates under new versions or releases of the Court’s operating system or database platform; and (iv) all on-site services necessary for installation of Upgrades. Without limiting any other obligation of Contractor under this Agreement, Contractor represents and warrants that it will maintain services, equipment, software or any other part of the Work so that they operate in accordance with their Specifications and Documentation; and The Contractor shall respond to the Court within four (4) hours after the Court reports a Technical Support Incident (such hours all occurring during Standard M&S Hours) to Contractor. DELIVERY, ACCEPTANCE, AND PAYMENT Delivery. Contractor shall deliver to the Court the Deliverables in accordance with this Agreement, including the Statement of Work. Unless otherwise specified by this Agreement, Contractor will deliver all goods purchased by the Court “Free on Board Destination Freight Prepaid” to the Court at the address and location specified by the Court. Title to all goods purchased by the Court vests in the Court upon payment of the applicable purchase price. Contractor will bear the risk of loss for any Work being delivered until received by the Court at the proper location. All shipments by Contractor or its Subcontractors must include packing sheets identifying: this Agreement number, the Court’s purchase order number, item number, quantity and unit of measure, part number and description of the goods shipped, and appropriate evidence of inspection, if required. Goods for different Agreements shall be listed on separate packing sheets.
Record Maintenance and Retention A. Grantee shall keep and maintain under GAAP or GASB, as applicable, full, true, and complete records necessary to fully disclose to the System Agency, the Texas State Auditor’s Office, the United States Government, and their authorized representatives sufficient information to determine compliance with the terms and conditions of this Grant Agreement and all state and federal rules, regulations, and statutes.
B. Grantee shall maintain and retain legible copies of this Grant Agreement and all records relating to the performance of the Grant Agreement, including supporting fiscal documents adequate to ensure that claims for grant funds are in accordance with applicable State of Texas requirements. These records shall be maintained and retained by the Grantee for a minimum of seven (7) years after the Grant Agreement expiration date or seven (7) years after all audits, claims, litigation or disputes involving the Grant Agreement are resolved, whichever is later.
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.
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.
System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.
Maintenance and Support NCR Voyix is solely responsible for providing any maintenance and support services with respect to the Software as specified in the Agreement, or as required under applicable law. The parties acknowledge that Apple has no obligation whatsoever to furnish any maintenance and support services with respect to the Software.
