Loop Interference and Maintenance Sample Clauses

Loop Interference and Maintenance. If US Dial Tone’s deployment of service enhancing technology interferes with existing or planned service enhancing technologies deployed by GTE or other CLECs in the same cable sheath, GTE will so notify US Dial Tone and US Dial Tone will immediately remove such interfering technology and shall reimburse GTE for all costs and expenses incurred related to this interference. When US Dial Tone provides its own loop and connects directly to GTE’s NID, GTE does not have the capability to perform routine maintenance. US Dial Tone can perform routine maintenance via its loop and inform GTE once the trouble has been isolated to the GTE NID and GTE will repair (or replace) the NID, or, at US Dial Tone’s option, effect a NID-to-NID cross connection, using the GTE NID only to gain access to the inside wire at the Customer location.
AutoNDA by SimpleDocs
Loop Interference and Maintenance. If Gulf Coast’s deployment of service enhancing technology interferes with existing or planned service enhancing technologies deployed by GTE or other CLECs in the same cable sheath, GTE will so notify Gulf Coast and Gulf Coast will immediately remove such interfering technology and shall reimburse GTE for all costs and expenses incurred related to this interference. When Gulf Coast provides its own loop and connects directly to GTE’s NID, GTE does not have the capability to perform routine maintenance. Gulf Coast can perform routine maintenance via its loop and inform GTE once the trouble has been isolated to the GTE NID and GTE will repair (or replace) the NID, or, at Gulf Coast’s option, effect a NID-to-NID cross connection, using the GTE NID only to gain access to the inside wire at the Customer location.
Loop Interference and Maintenance. If Empire’s deployment of service enhancing technology interferes with existing service enhancing technologies deployed by Verizon or other CLECs in the same cable sheath, Verizon will so notify Empire and Empire will immediately remove such interfering technology and shall reimburse Verizon for all costs and expenses incurred related to this interference. Verizon may request that Empire service enhancing technology be removed if it interferes with Verizon’s carrier of last resort obligations. When Empire provides its own loop and connects directly to Verizon’s NID, Verizon does not have the capability to perform routine maintenance. Empire can perform routine maintenance via its loop and inform Verizon once the trouble has been isolated to the Verizon NID and Verizon will repair (or replace) the NID, or, at Empire’s option, effect a NID-to-NID cross connection, using the Verizon NID only to gain access to the inside wire at the Customer location.

Related to Loop Interference and Maintenance

  • Support and Maintenance Where Licensee purchases support and/or maintenance services, Licensee’s initial support and/or maintenance term will begin upon delivery to Licensee of the Licensed Software and continue for one (1) year thereafter (or the length of the term if less than a year for any subscription/term license) unless otherwise specified in the applicable annual support and/or maintenance agreement, Product Order, or other written agreement executed between Licensor and Licensee. Where Licensee purchases support and/or maintenance for any Licensed Software, Licensee hereby agrees that it shall purchase such support and/or maintenance services for all of Licensee’s licensed units of such Licensed Software product. Support and/or maintenance services provided by Licensor will be subject to Licensor’s then current applicable standard annual support and/or maintenance agreement unless otherwise agreed by the parties in writing.

  • Operation and Maintenance 17.1 O&M obligations of the Concessionaire

  • Planned Maintenance (a) Sellers may designate up to twenty (20) Days of Planned Maintenance on Sellers’ Facilities during each Contract Year. Sellers shall be entitled to reduce (including down to zero (0)) its Gas scheduling under Clause 8 and Exhibit 3 for each Day of Planned Maintenance.

  • 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!