Network Management. 56.1 CLEC and CenturyLink will exchange appropriate information (e.g., network information, maintenance contact numbers, escalation procedures, and information required to comply with requirements of law enforcement and national security agencies) for network management purposes. In addition, the Parties will apply sound network management principles to alleviate or to prevent traffic congestion and to minimize fraud associated with third number billed calls, calling card calls, and other services related to this Agreement.
56.2 The Parties will employ characteristics and methods of operation that will not interfere with or impair the Parties’ networks, or the network of any third parties or Affiliated companies, connected with or involved directly in the network or facilities of CenturyLink.
56.3 CLEC shall not interfere with or impair service over any circuits, facilities or equipment of CenturyLink, its Affiliated companies, or its connecting and concurring carriers.
56.4 If CLEC causes any impairment or interference, CenturyLink shall promptly notify CLEC of the nature and location of the problem and that, unless promptly rectified, a temporary discontinuance of the use of any circuit, facility or equipment may be required. The Parties agree to work together to attempt to promptly resolve the impairment or interference. If CLEC is unable to promptly remedy, then CenturyLink may, at its option, temporarily discontinue the use of the affected circuit, facility or equipment until the impairment is remedied.
56.5 Any violation of Applicable Law or regulation regarding the invasion of privacy of any communications carried over CenturyLink’s facilities, or that creates hazards to the employees of CenturyLink or to the public, is also considered an impairment of service.
56.6 CenturyLink shall give advanced notice to CLEC of all non-scheduled maintenance or other planned network activities to be performed by CenturyLink on any Network Element, including any hardware, equipment, software, or system, providing service functionality of which CLEC has advised CenturyLink may potentially impact CLEC End Users.
56.7 The Parties shall provide notice of network changes and upgrades in accordance with 47 C.F.R. §§51.325 through 51.335. CenturyLink may discontinue any Interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. Centu...
Network Management. 34.1 Any Party may use or request protective network traffic management controls such as 7-digit and 10-digit code gaps on traffic to or from each other’s network, when required to protect the public switched network from congestion due to Facility failures, switch congestion, or failure or focused overload. The Parties will immediately notify each other of any protective control action planned or executed.
34.2 Where the capability exists, originating or terminating traffic reroutes may be implemented by any Party to temporarily relieve network congestion due to Facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal Trunk servicing. Expansive controls will only be used when the Parties mutually agree.
34.3 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, in order to prevent or mitigate the impact of these events on the public switched network.
34.4 Both Parties shall work cooperatively to prevent use of anything provided under this Agreement in any manner that interferes with third parties in the use of their service, prevents third parties from using their service, impairs the quality of service to other Telecommunications Carriers or to either Party’s End Users, causes electrical hazards to either Party’s personnel, damage to either Party’s equipment, or malfunction of either Party’s billing equipment. At the earliest practicable time, each Party will provide the other verbal notice of any such network harm that could effect the other Party, its network, or its End Users.
34.5 The Parties shall cooperate to establish separate, dedicated Trunks for the completion of calls to high volume End Users.
34.6 Carrier and Telco will work cooperatively to install and maintain a reliable network. Carrier and Telco 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 and such other information as the Parties shall mutually agree) to achieve this desired reliability.
34.7 Carrier shall acknowledge calls in accordance with the following protocols.
34.7.1 Carrier will provide a voice intercept announcement or distinctive tone signals to the calling party when a call is directed to a number that is not assigned by Carrier.
34.7.2 Carrier will provide a voice announcement o...
Network Management. 3.6.1 CLEC and CBT shall work cooperatively to install and maintain a reliable network. CLEC and CBT shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, and such other information as the Parties shall mutually agree) to achieve this desired reliability.
3.6.2 CLEC and CBT shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion.
3.6.3 CBT shall, upon the request of CLEC, provide the following network information, subject to any necessary privacy or proprietary safeguards:
(a) Points of Interconnection available on the CBT network;
(b) List of all local exchanges, and for each local exchange, the NXXs that are defined as within CBT's “local calling areas”;
(c) Switch locations (including Tandems and End Offices);
Network Management. The Council is responsible for the maintenance of the Hedera Network, including the Hedera Network software. Any proposed modifications to the Hedera Network software require the approval by TechCom in accordance with TechCom’s duly approved charter and, if approved, shall be implemented by the Members in accordance with procedures and protocols established by TechCom in order to ensure decentralized control and the integrity of the Hedera Network. Notwithstanding the foregoing, the total supply of Hbars may not be increased above fifty billion (50,000,000,000) Hbars without the unanimous consent of the Members.
Network Management. 3.7.1 Requesting Carrier and Ameritech shall work cooperatively to install and maintain a reliable network. Requesting Carrier and Ameritech shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agree) to achieve this desired reliability.
Network Management. The LFC will pass through to the Service Provider signalling and network management information delivered to its ports, so that the Service Provider has transparency of information between the UNI port and the Interconnection Point to the extent reasonably required to enable the Service Provider to manage its services. The LFC may, with the Service Provider’s consent, delegate management control of the relevant UNI ports to the Service Provider (while retaining overall management control).
Network Management. The MCO must:
1. use the results of its Provider profiling activities to identify areas of improvement for individual PCPs and Providers, and/or groups of Providers;
2. establish Provider-specific quality improvement goals for priority areas in which a Provider or Providers do not meet established MCO standards or improvement goals;
3. develop and implement incentives, which may include financial and non-financial incentives, to motivate Providers to improve performance on profiled measures; and
4. at least annually, measure and report to HHSC on the Provider Network and individual Providers’ progress, or lack of progress, towards such improvement goals. If the MCO implements a physician incentive plan, the plan must comply with the requirements of 42 C.F.R. §438.6(h), §422.208 and §422.210. The MCO cannot make payments under a physician incentive plan if the payments are designed to induce providers to reduce or limit Medically Necessary Covered Services to Members. If the physician incentive plan places a physician or physician group at a substantial financial risk for services not provided by the physician or physician group, the MCO must ensure adequate stop-loss protection and conduct and submit annual Member surveys no later than five (5) Business Days after the MCO finalizes the survey results (refer to 42 C.F.R. §422.208 for information concerning “substantial financial risk” and “stop-loss protection”). The MCO must make information regarding physician incentive plans available to Members upon request, in accordance with the Uniform Managed Care Manual’s requirements. The MCO must provide the following information to the Member:
1. whether the Member’s PCP or other Providers are participating in the MCO’s physician incentive plan;
2. whether the MCO uses a physician incentive plan that affects the use of referral services;
3. the type of incentive arrangement; and
4. whether stop-loss protection is provided. No later than five (5) Business Days prior to implementing or modifying a physician incentive plan, the MCO must provide the following information to HHSC:
1. Whether the physician incentive plan covers services that are not furnished by a physician or physician group. The MCO is only required to report on items 2-4 below if the physician incentive plan covers services that are not furnished by a physician or physician group.
2. The type of incentive arrangement (e.g., withhold, bonus, capitation);
3. The percent of withhold or bonus (if appli...
Network Management. The HMO must:
Network Management. Network Management shall consist of automated monitoring and addressing or making recommendations about (in Marco’s sole discretion) issues Marco identifies in Network Equipment uptime reports, event logs, drive space, antivirus reports, errors/alerts, switch and firewall configuration status and hardware failure/warning lights. Client agrees that Marco may install software and/or equipment to assist in performing the Network Management. Marco will provide Network Management maintenance for items determined by Marco.
Network Management. (4 pages, plus 1 additional page per additional MCO Program bid if the Respondent’s response differs by MCO Program) Describe how the Respondent will actively work with Network Providers to ensure accountability and improvement in the quality of care provided by both Acute and Long-Term Services and Supports Providers. The description should include:
