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.
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.
Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:
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.
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.
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:
Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet. (a) The Employer shall notify affected employees and the Union as soon as a formal decision to integrate is taken. (b) The Employer and the Union shall begin discussions concerning the specifics of the integration forthwith after a decision to integrate is taken. (c) As soon as possible in the course of developing a plan for the implementation of the integration the Employer shall notify affected employees and the Union of the projected staffing needs, and their location.
meminta nasihat daripada Pihak Xxxxxx dalam semua perkara berkenaan dengan jualan lelongan, termasuk Syarat-syarat Jualan (iii) membuat carian Hakmilik Xxxxx xxxxxx rasmi di Pejabat Tanah xxx/atau xxxx-xxxx Pihak-pihak Berkuasa yang berkenaan xxx (iv) membuat pertanyaan dengan Pihak Berkuasa yang berkenaan samada jualan ini terbuka kepada semua bangsa atau kaum Bumiputra Warganegara Malaysia sahaja atau melayu sahaja xxx juga mengenai persetujuan untuk jualan ini sebelum jualan lelong.Penawar yang berjaya ("Pembeli") dikehendaki dengan segera memohon xxx mendapatkan kebenaran pindahmilik (jika ada) daripada Pihak Pemaju xxx/atau Pihak Tuanpunya xxx/atau Pihak Berkuasa Negeri atau badan-badan berkenaan (v) memeriksa xxx memastikan samada jualan ini dikenakan cukai. HAKMILIK : Hakmilik strata bagi hartanah ini masih belum dikeluarkan HAKMILIK INDUK / NO. LOT : Pajakan Negeri 35263, Lot No.29096 MUKIM/DAERAH/NEGERI : Setapak / Kuala Lumpur / Wilayah Persekutuan Kuala Lumpur PEGANGAN : Pajakan selama 82-tahun berakhir pada 08/08/2085 KELUASAN LANTAI : 81.104 meter persegi ( 873 kaki persegi ) PEMAJU/PENJUAL : Mega Planner Jaya Sdn Bhd (326287-W)(Dalam Likuidasi) TUANPUNYA : Datuk Bandar Kuala Lumpur PEMBELI : Xxxxxxxx Bin Xxxxx @ Xxxx BEBANAN : Diserahhak kepada RHB Bank Berhad [196501000373 (6171-M)] Hartanah tersebut terletak di tingkat 9 pada bangunan apartment 14-tingkat terletak di Melati Impian Apartment, Setapak Fasa 1, Kuala Lumpur. Hartanah tersebut adalah sebuah unit apartment 3 xxxxx dikenali sebaga Xxxxx Pemaju No. 9, Tingkat No.9, Pembangunan dikenali sebagai Melati Impian Apartment Setapak Fasa 1, Kuala Lumpur xxx mempunyai alamat surat-xxxxxxxx xx Xxxx Xx. 0-0, Xxxxxx Impian Apartment, Xxxxx 0/00X, Xxxxx Xxxxxx, 00000 Xxxxx Xxxxxx, Xxxxxxx Xxxxxxxxxxx Xxxxx Xxxxxx. Harta ini dijual “keadaan seperti mana sediada” dengan harga rizab sebanyak RM 300,000.00 (RINGGIT MALAYSIA: TIGA RATUS RIBU SAHAJA) xxx tertakluk kepada syarat-syarat Jualan xxx melalui penyerahan hakkan dari Pemegang Serahak, tertakluk kepada kelulusan di perolehi oleh pihak Pembeli daripada pihak berkuasa, jika ada, termasuk semua terma, syarat xxx perjanjian yang dikenakan xxx mungkin dikenakan oleh Pihak Berkuasa yang berkenaan. Pembeli bertanggungjawab sepenuhnya untuk memperolehi xxx mematuhi syarat-syarat berkenaan daripada Pihak Berkuasa yang berkenaan, jika ada xxx semua xxx xxx perbelanjaan ditanggung xxx dibayar oleh Xxxxx Xxxxxxx.Pembeli atas talian (online) juga tertakluk kepada terma-terma xxx syarat-syarat terkandung dalam xxx.xxxxxxxxxxxxxxxx.xxx Pembeli yang berminat adalah dikehendaki mendeposit kepada Pelelong 10% daripada harga rizab dalam bentuk Bank Draf atau Cashier’s Order di atas nama RHB Bank Berhad sebelum lelongan awam xxx xxxx xxxx xxxxxx hendaklah dibayar dalam tempoh sembilan puluh (90) hari dari tarikh lelongan kepada RHB Bank Berhad melalui Bank Draf / XXXXXX. Butir-butir pembayaran melalui XXXXXX, xxxx berhubung dengan Tetuan Zahrin Emrad & Sujaihah. Untuk maklumat lanjut, xxxx berhubung dengan TETUAN ZAHRIN EMRAD & SUJIAHAH, yang beralamat di Suite 10.3, 10th Floor, Xxx Xxxx Building, Xx.00, Xxxxx Xxxx Xxxxxx, 00000 Xxxxx Xxxxxx. Tel: 00-0000 0000 / Fax: 00-0000 0000. [ Ruj: ZES/ZHR/RHB-FC/16250-17/0614-pae ], peguamcara bagi pihak pemegang xxxxx xxx atau pelelong yang tersebut dibawah.
Skidding and Yarding Methods of skid- ding or yarding specified for particular areas, if any, are indicated on Sale Area Map. Outside Clearcutting Units and construction clearings, insofar as ground conditions permit, products shall not be skidded against reserve trees or groups of reproduction and tractors shall be equipped with a winch to facilitate skidding. B6.421 Rigging. Insofar as practicable, needed rigging shall be slung on stumps or trees desig- nated for cutting.
STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.
