Maintenance Windows & Planned Interventions Sample Clauses

Maintenance Windows & Planned Interventions eHealth will strive for limiting as much as possible the impact and duration of the planned interventions. Today, eHealth is committed to make efforts so planned unavailability’s do not exceed one to a few hours per year. In case of maintenance requiring support from users, or impacting them, eHealth will notify them at least one week ahead.
AutoNDA by SimpleDocs
Maintenance Windows & Planned Interventions. The eHealth platform will strive for limiting as much as possible the impact and duration of the planned interventions. Today, the eHealth platform is committed to make efforts so planned unavailability’s do not exceed one to a few hours per year. • Portal, Network interventions and application release: 2 times a year.
Maintenance Windows & Planned Interventions. During the Major Releases, a downtime of maximum 30 minutes is authorised. This downtime will not be taken into account when calculating the Availability of the different Services. Other periods can be agreed between the Constituent and the Service Provider. Interventions authorized on the Active environment are Corrective actions intended to enhance the availability or stability of the Service. Unavailability caused by these interventions will be recorded as downtime In exceptional circumstances, unplanned interventions may be needed in order to restore the service. 3.1. eHealth Service
Maintenance Windows & Planned Interventions. The eHealth platform will strive for limiting as much as possible the impact and duration of the planned interventions. Today, eHealth is committed to make efforts so planned unavailabilities do not exceed one to a few hours per year. In case of maintenance requiring support from users, or impacting them, eHealth will notify them at least one week ahead.  Portal Interventions: 2 times a year  Network Interventions: 2 times a year  Application Releases: max. twice a year: interventions needed for installing new versions of Consult RN software, other eHealth components or other eHealth Services involved in the provision of the Consult RN Base Service.

Related to Maintenance Windows & Planned Interventions

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Installation and Maintenance Except for the bi‐directional and production metering equipment owned by the City, all equipment on Customer’s side of the delivery point, including the required disconnect device, shall be provided and maintained in satisfactory operating condition by Customer and shall remain the property and responsibility of the Customer. The City will bear no responsibility for the installation or maintenance of Customer’s equipment or for any damage to property as a result of any failure or malfunction thereof. The City shall not be liable, directly or indirectly for permitting or continuing to allow the interconnection of the Facility or for the acts or omissions of Customer or the failure or malfunction of any equipment of Customer that causes loss or injury, including death, to any party.

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

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC 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 CSTC 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 CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC 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 CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Software Maintenance Subrecipient shall apply security patches and upgrades in a timely manner and keep virus software up-to-date on all systems on which State data may be stored or accessed.

  • Installation, Maintenance, Testing and Repair Unless otherwise agreed in writing by the Parties, to the extent required by Applicable Law, Interconnection provided by a Party shall be equal in quality to that provided by such Party to itself, any subsidiary, affiliates or third party. If either Party is unable to fulfill its obligations under this Section 14.2, it shall notify the other Party of its inability to do so and will negotiate alternative intervals in good faith. The Parties agree that to the extent required by Applicable Law, the standards to be used by a Party for isolating and clearing any disconnections and/or other outages or troubles shall be at parity with standards used by such Party with respect to itself, any subsidiary, affiliate or third party.

  • Maintenance Program LESSEE's Maintenance Program

  • Routine Maintenance (i) CRC shall be responsible for Routine Maintenance when necessary or desirable to maintain the Shared Assets in a safe operating condition, and to permit and facilitate (A) the performance by CRC of its obligations pursuant to this Agreement, and (B) the use of Shared Assets by the Operators in accordance with this Agreement. (ii) CSXT or NSR, directly or through their respective affiliates, may perform the work which CRC performed prior to the date of this Agreement when (A) CRC does not possess the skills needed for such work, (B) CRC lacks the necessary employees to do such work in a timely fashion, or (C) CRC does not possess the equipment needed to do such work. CRC and the party performing the work shall agree to a reasonable fee for such work prior to performance. CRC, CSXT and NSR may agree to have additional work performed either by CSXT, NSR or their affiliates.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

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