Service Windows. The time frame during which the eHealth services are offered to the client applications, is defined in terms of days and hours. Standard working days are all days of the year, except during the biannual maintenance periods and Bank Holidays. The following table summarises the eHealth Service Windows. Monday Tuesday Wednesday Thursday Friday Saturday Sunday Day period 00:00 – 07:00 07:00 – 08:00 08:00 – 16:30 16:30 – 19:00 19:00 – 20:00 20:00 – 24:00 Legend Timeslots where the Service must be available according to the SLA and where corrective actions will be taken to resolve detected Incidents. Timeslots where the Service will be available provided there are no blocking Incidents. If these incidents do appear, no corrective action will be taken. Timeslots where unavailability can occur.
Service Windows. 4.2.1 Details of the Service Windows shall be provided in the notification of Contract Award and examples shall be available within the relevant tools and templates schedule.
Service Windows. 5.1. A description of service windows for SDN is available on xxx.xxxxxx.xx. Notification of service windows must made through service information to connected parties. If the service window is necessary to rectify an acute problem, the parties will be notified afterwards.
5.2. The agreement system makes it possible for the connected parties to announce service windows for services displayed via the SDN.
Service Windows. Maintenance window Upgrade window
Service Windows. The time frame during which the eHealth services are offered to the client applications, is defined in terms of days and hours. Standard working days are all days of the year, except during the biannual maintenance periods. The default service windows defined in the MSA (Chapter 5.1.1 Service, Support and Maintenance Window) is applicable for this SLA. The following table summarises the eHealth Service Windows. Monday Tuesday Wednesday Thursday Friday Saturday Sunday Day period 00:00 – 07:00 07:00 – 08:00 08:00 – 16:30 16:30 – 19:00 19:00 – 24:00 Legend Timeslots where the Service must be available according to the SLA and where corrective actions will be taken to resolve detected Incidents. Timeslots where the Service will be available provided there are no blocking Incidents. If these incidents do appear, no corrective action will be taken. Timeslots where unavailability can occur.
Service Windows. (*) ***** ** ********. *** ******* **** ***** ** ****** ** *** ********** ******** ******* **** (***) ****** ** *** ****** *** ****. *** ***** ****** **** ***** ** *** ****** ****** ** *******. *** *********** ******* **** ***** ** **:** ******* ****. ************ ***** ******* *** ** ******* *********** ******** *** **** *** ******** ******* ** ******** ************ *** ********** *******. *** ********* ******* ** **** ******* ****** ******** ***** ** **** ** ***** ****** (**) **** ** *******. ************ ***** ****** *** ** ***** ****** (**) **** ** ******* ** *** ***** ** ******* *** ** *** ******* ******* ****** *****. ************ *** *** ***** ******* ******* ** ****** *********** ******** *** *** ******** ******** **** *** **** **** ** *** ****. ************ *** *** ***** ** ******** **** ****** *********** ******** ** **** *** *** ** ********** ** *** ******* ** ***** **** *** ***. **** ****** ****** ******** **** ******* *** *********:
1. (**) ****** ****** ******* **** * ******* ******** ** *.* *****
2. (*) ******** ****** ******* **** * ******* ******** ** * ***** *** *** ************ ***** ******** ***** ** *** ** ****** **** ******** ** ********.
Service Windows. 1. The required flexibility availability and capacity for each Zone shall be communicated by the Company to Providers at least one month ahead. The Company will establish the availability of Providers, using the Availability Request Form (see section 7 on Communications).
2. Where availability requirements can be forecast for several months or a year ahead, the Company may choose to request a Provider’s availability to cover the entire period.
3. The Provider may decline an Availability Request or propose reduced capacity. After mutually agreeable capacity and Service Windows are agreed, the Company will re-issue the Availability Request Form for formal acceptance.
4. By accepting an Availability Request, the Provider is offering to and committing to be ready to provide the agreed power change throughout the Service Window, if instructed to do so by the Company.
Service Windows. 1.5.1. The required flexibility availability and capacity for each CMZ are communicated by the Company to Flexibility Providers at least one month ahead. The Company will establish the availability of Flexibility Providers, using the Availability Request Form (see Forms and Templates).
1.5.2. Where availability requirements can be forecast for several months or a year ahead, the Company may choose to request a Flexibility Provider’s availability to cover the entire period.
Service Windows. 8.1 The current and agreed service windows for SDN are publicly available at www.med- xxx.xx.
8.2 Notification of service windows is provided through operational notifications to the connected parties. If a service window is necessary to address an urgent issue (such as patching a zero-day exploit), the connected parties will be informed as soon as possible.
8.3 The Agreement System includes the option for connected parties to indicate their pre- ferred service windows for their exposed services through SDN.
Service Windows. The required flexibility availability and capacity for each CMZ are communicated by the Company to Providers at least one month ahead. The Company will establish the availability of Providers, using the Availability Request Form (see Communications).
