Monitoring of the Service. JRNI and bookinglab will regularly monitor the status of the Booking Service (including routine checks on the hardware, processes and wait queues) on behalf of bookinglab using both automated and manual tools and testing procedures. Upon request by Customer, but no more than once every 6 months, bookinglab will provide a report listing all Customer-affecting service and outage faults during the prior 6 months, including: • Date and time of fault • Impact of fault on service provision • Service outage duration • Description of Error and resolution identifying steps taken to prevent future occurrences • Scheduled releases
Monitoring of the Service. TAAP and bookinglab will regularly monitor the status of the TAAP Visitor Book Service (including routine checks on the hardware, processes and wait queues) on behalf of bookinglab using both automated and manual tools and testing procedures. Upon request by Customer, but no more than once every 6 months, bookinglab will provide a report listing all Customer-affecting service and outage faults during the prior 6 months, including: Date and time of fault Impact of fault on service provision Service outage duration Description of Error and resolution identifying steps taken to prevent future occurrences Scheduled releases
Monitoring of the Service. JRNI and Field Dynamics will regularly monitor the status of the Booking Service (including routine checks on the hardware, processes and wait queues) on behalf of Field Dynamics using both automated and manual tools and testing procedures. Upon request by Customer, but no more than once every 6 months, Field Dynamics will provide a report listing all Customer-affecting service and outage faults during the prior 6 months, including: Date and time of fault Impact of fault on service provision Service outage duration Description of Error and resolution identifying steps taken to prevent future occurrences Scheduled releases
Monitoring of the Service. 13.1 The Service will be monitored in accordance with the procedures and service standards referred to in Appendix 1 (Description of Services – Performance Indicators), Appendix 2 (Charging Arrangements), Appendix 3 (Governance Arrangements) and Appendix 4 (Operational Arrangements).
Monitoring of the Service. 2.1 The Service is monitored in two ways: • Active monitoring: Parkeon's automatic procedures, which periodically test the availability of the main system and its functionalities. These active monitoring processes include the alert and escalation mechanisms needed for Parkeon’s technical support department to be informed as quickly as possible. • Passive monitoring: Customer is able to notify, 24 hours a day, an incident associated with the use of the Service. Outside the Help Desk’s working hour time slots, this notification shall be made by e-mail to the address xxxx@xxxxxxxxxxx.xxx
Monitoring of the Service. LRC has no obligation to monitor the Service, but may do so and may disclose information regarding the use of the Service for any reason if LRC, in its sole discretion, believes that it is reasonable to do so. This includes but is not limited to: satisfying laws, regulations, government or legal requests, maintenance and operation of the Service, or to protect itself, its members or its customers.
Monitoring of the Service bookinglab will regularly monitor the status of the TuGO Service (including routine checks on the hardware, processes and wait queues) on behalf of bookinglab using both automated and manual tools and testing procedures. Upon request by Customer, but no more than once every 6 months, bookinglab will provide a report listing all Customer-affecting service and outage faults during the prior 6 months, including: Date and time of fault Impact of fault on service provision Service outage duration Description of Error and resolution identifying steps taken to prevent future occurrences Scheduled releases
