Incident Response Timescales Sample Clauses
The 'Incident Response Timescales' clause defines the required timeframes within which parties must respond to and address security incidents or breaches. Typically, this clause specifies deadlines for acknowledging receipt of an incident report, initiating an investigation, and providing updates or resolutions, such as requiring notification within 24 hours of discovery. Its core practical function is to ensure prompt action and communication during security incidents, thereby minimizing potential damage and ensuring accountability between parties.
Incident Response Timescales. 7.2.1. OUTSOURCE TELECOM shall use best endeavours to assign an Incident to an appropriate engineer within 30 minutes of the generation or receipt of a fault for no less than 95% of Incidents properly submitted to OUTSOURCE TELECOM by the Client in accordance with Clause 7.1.
7.2.2. OUTSOURCE TELECOM shall use best endeavours to make an update on an Incident available to the Client via email within the response times specified in Clause 7.4.1.
Incident Response Timescales. FCC shall use best endeavours to assign an Incident to an appropriate FCC engineer within 30 minutes of the generation or receipt of an Incident Report for no less than 95% of Incidents properly submitted to FCC by the Customer in accordance with paragraph 4.1 of this Schedule. FCC shall use best endeavours to make an update on an Incident available to the Customer via the Trouble Ticket System within the response times specified in paragraph 8 of this Schedule.
Incident Response Timescales. 1CommsFM shall use best endeavours to update the Customer on an Incident within the response times specified in Schedule 2.
Incident Response Timescales. 7.2.1. ES SYSTEMS LTD shall use best endeavours to assign an Incident to an appropriate ES SYSTEMS LTD engineer within 30 minutes of the generation or receipt of a fault for no less than 95% of Incidents properly submitted to ES SYSTEMS LTD by the Client in accordance with Clause 7.1.
7.2.2. ES SYSTEMS LTD shall use best endeavours to make an update on an Incident available to the Client via email within the response times specified in Clause 7.4.1.
Incident Response Timescales. 8.2.1 ANGLIAN INTERNET LTD shall use best endeavours to assign an Incident to an appropriate ANGLIAN INTERNET LTD engineer within 30 minutes of the generation or receipt of a fault for no less than 95% of Incidents properly submitted to ANGLIAN INTERNET LTD by the Client in accordance with Clause 8.1.
8.2.2 ANGLIAN INTERNET LTD shall use best endeavours to make an update on an Incident available to the Client via email within the response times specified in Clause 8.4.1.
Incident Response Timescales. 8.3.1 GIACOM shall use best endeavours to assign an Incident to an appropriate GIACOM engineer within 1 Business Hour of receipt of the Incident Report for no less than 98% of Incidents properly submitted to GIACOM by the Reseller in accordance with clause 8.1.1.
8.3.2 GIACOM shall use best endeavours to make an update on an Incident available to the Reseller via the Trouble Ticket System within the response times specified in clause 8.5.1.
Incident Response Timescales. 8.3.1 Immervox shall use best endeavours to assign an Incident to an appropriate Immervox engineer within 2 hours of the generation or receipt of the an Incident Report for no less than 95% of Incidents properly submitted to Immervox by the Client in accordance with Clause 8.1.
8.3.2 Immervox shall use best endeavours to make an update on an Incident available to the Client via the Trouble Ticket System within the response times specified in Clause 8.5.1.
Incident Response Timescales. 8.3.1 TALKTECH shall use best endeavours to assign an Incident to an appropriate TALKTECH engineer within 30 minutes of the generation or receipt of the an Incident Report for no less than 95% of Incidents properly submitted to TALKTECH by the Client in accordance with Clause 8.1.
8.3.2 TALKTECH shall use best endeavours to make an update on an Incident available to the Client via the Trouble Ticket System within the response times specified in Clause 8.5.1.
Incident Response Timescales. 8.3.1 RCUK and/or its suppliers shall use best endeavours to assign an Incident to an appropriate engineer within 30 minutes of the generation or receipt of an Incident Report for no less than 95% of Incidents properly submitted to RCUK and/or its suppliers by the Client in accordance with Clause 8.1.
8.3.2 RCUK and/or its suppliers shall use best endeavours to make an update on an Incident available to the Client within the response times specified in Clause 8.5.1.
Incident Response Timescales. 8.2.1. Micro Minder Ltd shall use best endeavours to assign an Incident to an appropriate Micro Minder Ltd engineer within 30 minutes of the generation or receipt of a fault for no less than 95% of Incidents properly submitted to Micro Minder Ltd by the Client in accordance with Clause 8.1.
8.2.2. Micro Minder Ltd shall use best endeavours to make an update on an Incident available to the Client via email within the response times specified in Clause 8.4.1.