Network Maintenance and Management for Direct Interconnection Clause Samples

The Network Maintenance and Management for Direct Interconnection clause defines the responsibilities and procedures for maintaining and managing network connections directly linking the parties. It typically outlines requirements for scheduled maintenance windows, notification protocols for outages or upgrades, and standards for troubleshooting and repair. This clause ensures that both parties coordinate effectively to minimize service disruptions and maintain reliable interconnection, thereby reducing the risk of unexpected downtime and clarifying each party’s obligations in managing the shared network infrastructure.
Network Maintenance and Management for Direct Interconnection. The Parties will work cooperatively to install and maintain reliable network facilities. The Parties will exchange appropriate information to achieve this desired reliability, subject to the confidentiality provisions herein. 7.3.1 Party shall provide a 24-hour contact number for network Traffic management issues to the other’s surveillance management center. Telephone Company Contact Number: (xxx)-xxx-xxxx CMRS Provider Contact Number: ▇▇▇-▇▇▇-▇▇▇▇ 7.3.2 Neither Party will use any service provided under this Agreement in a manner that impairs the quality of service to other carriers or to either Party’s subscribers. Either Party will provide the other Party notice of said impairment at the earliest practicable time. 7.3.3 Use of the CMRS Providers’ facilities, or that of a third party in conjunction with any of the Telephone Company’s facilities, shall not materially interfere with or impair service over any facilities of either Party, its affiliated companies or its connecting and concurring carriers involved in its services, cause damage to their plant, impair the privacy of any communications carrier over their facilities or create hazards to the employees of any of them or the public. Upon reasonable written notice and opportunity to cure, the Party whose facilities are being used may discontinue or refuse service to the other Party if the Party using the facilities violates this provision; provided, that such termination of service will be limited to the facilities being used that is subject of the violation. 7.3.4 Maintenance of Service Charge - When one Party reports trouble to the other Party for clearance and no trouble is found in the second Party’s network, the reporting Party shall be responsible for payment of a Maintenance of Service Charge for the period of time when the second Party’s personnel are dispatched. In the event of an intermittent service problem that is eventually found to be in the second Party’s network, the reporting Party shall receive a credit for any Maintenance of Service Charges applied in conjunction with this service problem. If a Party reports trouble to the other Party for clearance and the other Party’s personnel are not allowed access to the reporting Party’s premises, the Maintenance of Service Charge will apply for the time that the non-reporting Party’s personnel are dispatched; provided that the Party’s have arranged a specific time for the service visit.
View SourceView Similar (6)
Network Maintenance and Management for Direct Interconnection. The Parties will work cooperatively to install and maintain reliable network facilities. The Parties will exchange appropriate information to achieve this desired reliability, subject to the confidentiality provisions herein. 7.3.1 Party shall provide a 24-hour contact number for network management issues to the other's surveillance management center. A contact person and number must also be provided to facilitate notifications for planned mass calling events. 7.3.2 Neither Party will use any service provided under this Agreement in a manner that impairs the quality of service to other carriers or to either Party's subscribers. Either Party will provide the other Party notice of said impairment at the earliest practicable time.
View Source
Network Maintenance and Management for Direct Interconnection. 8.3.1 The Parties will work cooperatively to install and maintain a reliable network. The Parties will exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, etc.) to achieve this desired reliability, subject to the confidentiality provisions herein. 8.3.2 The Parties shall provide a twenty-four (24)-hour contact number for network traffic management issues to the other’s surveillance management center. A fax number must also be provided to facilitate notifications for planned mass calling events.
View Source

Related to Network Maintenance and Management for Direct Interconnection

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

  • Workload Management 11.1 The parties to this Agreement acknowledge that Employees and management have a responsibility to maintain a balanced workload and recognise the adverse effects that excessive workloads may have on Employee/s and the quality of resident/client care. 11.2 To ensure that Employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, Employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected Employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the Employee/s may advance the matter through clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the Employer and the Employee representative, which may include the union/s.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.