NCRA MANAGEMENT Sample Clauses

Open Split View

Download

Share

Cite

NCRA MANAGEMENT. The parties agree as follows with respect to management of NCRA’s business and operations:

Sample 1Sample 2

Save

Copy

Related to NCRA MANAGEMENT

• Network Management 60.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. 60.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. 60.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. 60.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. 60.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. 60.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. 60.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. CenturyLink agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers which may result from such discontinuance of service.

• Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

• Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

• Data Management Contractor will not use State data, including production data, for testing or development purposes unless authorized in writing by the State Chief Information Security Officer or delegate. Contractor will implement and maintain procedures to physically and logically segregate State data, unless otherwise explicitly authorized by the State Chief Information Security Officer or delegate.

• Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

• Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.

• Asset Management Supplier will: i) maintain an asset inventory of all media and equipment where Accenture Data is stored. Access to such media and equipment will be restricted to authorized Personnel; ii) classify Accenture Data so that it is properly identified and access to it is appropriately restricted; iii) maintain an acceptable use policy with restrictions on printing Accenture Data and procedures for appropriately disposing of printed materials that contain Accenture Data when such data is no longer needed under the Agreement; iv) maintain an appropriate approval process whereby Supplier’s approval is required prior to its Personnel storing Accenture Data on portable devices, remotely accessing Accenture Data, or processing such data outside of Supplier facilities. If remote access is approved, Personnel will use multi-factor authentication, which may include the use of smart cards with certificates, One Time Password (OTP) tokens, and biometrics.

• SITE MANAGEMENT We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.

• Exit Management 58.1. The Service Provider shall perform its relevant Exit Management obligations as part of the Contract whether applicable on either the expiry or early termination of this Contract. 58.2. The Service Provider agrees that if it breaches (or attempts or threatens to breach) its obligation to provide Exit Management, the Purchaser and their respective customers and stakeholders shall be irreparably harmed. In such circumstance, the Service Provider agrees that the Purchaser may proceed directly to court notwithstanding anything to the contrary in the dispute resolution procedure outlined in Clause 53 (Dispute Resolution). If a court of competent jurisdiction finds that the Service Provider has breached (or attempted or threatened to breach) any such obligation, the Service Provider agrees that without any additional findings of irreparable injury, or other conditions to interdict, the Service Provider shall not oppose the entry of an appropriate order compelling performance by the Service Provider and restraining the Service Provider from any further breaches or attempted or threatened breaches of its obligations in relation to Exit Management. 58.3. A draft of the Exit Plan shall be produced by the Service Provider and supplied to the Purchaser within [three (3) months] after the Commencement Date and shall include or address the matters specified in Clause 59.3. The Purchaser shall provide to the Service Provider the Purchaser’s comments on the plan within one (1) month of the Purchaser’s receipt of the plan. The Service Provider shall take into account the comments and suggestions of the Purchaser and shall issue the final version of the Exit Plan to the Purchaser within ten (10) Working Days of receipt of the Authority’s comments. 58.4. The Service Provider shall throughout the period of the Contract review, maintain and continuously update the Exit Plan which shall include: 58.4.1. the activities required to enable the Purchaser to re-tender the Purchaser Requirements and/or the provision of the Services; 58.4.2. the activities necessary to support any Replacement Service Provider or the Purchaser in carrying out any necessary due diligence relating to all or part of the Services; 58.4.3. details of the Exit Management to be provided by the Service Provider prior to the Exit Management Date; 58.4.4. support for the Replacement Service Provider or the Purchaser during their preparation of any relevant plan for the transition of the System to the Replacement Service Provider or Purchaser, including prior to and during such transition period; 58.4.5. the maintenance of a ‘business as usual’ environment for the Purchaser during the period when Exit Management obligations are applicable; and 58.4.6. all other necessary activities to support the preparation for, and execution of, a smooth and orderly Exit Management and transfer of all or part of the Services to either a Replacement Service Provider or the Purchaser. 58.5. No amendment of the Exit Plan shall be made without prior written consent of the Purchaser.

• Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;