Incident Logging. The Customer shall ensure the Company is informed by notification to the Company’s nominated service control (as notified to the Customer in writing from time to time) in a reasonable period of time, of any Equipment failure or potential failure, and shall as applicable permit or arrange with the End User for the Company to have the necessary access to the Equipment and use of necessary tools, machines and devices in the Customer’s or End User’s possession. The Customer shall maintain or take reasonable efforts to ensure the End User maintains accurate and current logs and records concerning the operation of the Equipment
Incident Logging. An Incident can be logged by the client by one of the following methods:
Incident Logging. The Customer’s primary IT contact must contact the Correct Solutions technical services team either by telephone, email, web portal or any other form of communication as offered by Correct Solutions from time to time. Any such contact will be a RFS.
Incident Logging. Any agreed alerts and alarms which are generated from the Clients SIEM solution will be investigated by the Suppliers security team. The Suppliers security team will assess the alarm or alert and decide if it should be logged as an incident for further investigation based on criteria agreed with the Client. Incidents will be logged in the Suppliers CRM system and the Client will be notified of agreed incidents that have been logged via an email generated by the Suppliers CRM system. During the onboarding project the Supplier and Client will agree on if/how incidents will be logged in the Clients CRM system, including how systems may integrate if required. All incidents logged are subject to the response times detailed in the Managed Security Services Schedule.
Incident Logging. Customer’s Authorised Support Users may submit Incidents to the Help Desk during normal working hours (09:00 – 17:30 GMT). Incidents are submitted via email to xxxxxxx@xxxxxxxx.xxx. Each Incident will be given a unique Incident log number which will be passed to the Customer. Workvivo undertakes to aid the resolution of Incidents as rapidly as the circumstances allow and based on the terms of this Support Policy. Resolutions may take the form of a repair, bypass or other reasonable solution agreed between Workvivo and the Customer.
Incident Logging. The Company shall ensure the Subcontractor is informed by notification to the Subcontractor’s nominated service control (as notified to the Company in writing from time to time), in a reasonable period of time, of Equipment failure or potential failure, and shall as applicable permit or arrange with the End User for the Subcontractor to have necessary access to the Equipment and use of necessary tools, machines and devices in the Company’s or End User’s possession. The Company shall maintain or take reasonable efforts to ensure the End User maintains accurate and current logs and records concerning the operation of the Equipment.
Incident Logging. The Customer’s Service Desk will contact MEDILOGIK to log an Incident. Contact is made by ringing the dedicated MEDILOGIK EMS support line +00 0000 000000 or by emailing xxxxxxx@xxxxxxxxx.xx.xx which will automatically create a support ticket on our Zendesk system. MEDILOGIK will assess and prioritise the Incident in line with the agreed Incident Severity Matrix. MEDILOGIK may amend the severity level after initial investigation and will notify the Customer of any changes in priority. The Customer will provide the Supplier’s Helpdesk with full details of the Incident, including any investigative or remedial actions taken locally prior to referral.
Incident Logging
