We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Incident Logging Sample Clauses

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
Sample 1Sample 2See All (4)
Incident Logging. An Incident can be logged by the client by one of the following methods:
Sample 1Sample 2
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.
Sample 1Sample 2
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.
Sample 1
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.
Sample 1
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.
Sample 1
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.
Sample 1
Incident Logging 
Sample 1Sample 2

Related to Incident Logging

  • Incident Management 3.1. We shall notify You without undue delay after We becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, stored or otherwise processed by Us or Our sub-processors of which We become aware (“Security Incident”). 3.2. We shall use best efforts to identify the cause of such Security Incident and take the measures We deem necessary and within Our control for remediating and securing Customer Data; We shall coordinate such efforts with You without undue delay.

  • Logging The ISP will require the maintenance of network and application logs as part of BNY Mellon’s security information and event management processes. Logs are retained in accordance with law applicable to BNY Mellon’s provision of the services as well as BNY Mellon’s applicable policies. BNY Mellon uses various tools in conjunction with such logs, which may include behavioral analytics, security monitoring case management, network traffic monitoring and analysis, IP address management and full packet capture.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Incident Notification Google will notify Customer promptly and without undue delay after becoming aware of a Data Incident, and promptly take reasonable steps to minimize harm and secure Customer Data.

  • Incidents Without prejudice to Article 11 of this attachment, and in accordance with attachment F of the Access Code for Transmission, in case of an incident compromising the safe and efficient operation of the transmission grid and/or the system integrity, urgent measures shall be taken by TSO which can consist inter alia of, without being limited to an interruption and/or reduction of the Transmission Services. The Network Users affected by the interruption and/or reduction and the XXXX shall be informed by the TSO of the event and the estimated duration, according to the reporting obligations described in attachment F of the Access Code for Transmission. The Plan for Incident Management is included in attachment F of the Access Code for Transmission.

  • Dewatering (a) Where the whole of a site is so affected by surface water following a period of rain that all productive work is suspended by agreement of the Parties, then dewatering shall proceed as above with Employees so engaged being paid at penalty rates as is the case for safety rectification work. This work is typically performed by Employees engaged within CW1, CW2 or CW3 classifications. When other Employees are undertaking productive work in an area or areas not so affected then dewatering will only attract single time rates. (b) Where a part of a site is affected by surface water following a period of rain, thus rendering some areas unsafe for productive work, consistent with the Employer’s obligations under the OH&S Act, appropriate Employees shall assist in the tidying up of their own work site or area if it is so affected. Where required, appropriate Employees will be provided with the appropriate PPE. Such work to be paid at single time rates. Productive work will continue in areas not so affected. (c) To avoid any confusion any ‘dewatering’ time which prevents an Employee from being engaged in their normal productive work is not included in any calculation for the purposes of determining whether an Employee is entitled to go home due to wet weather (refer clauses 32.4 and 32.5)

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Processing operations The personal data transferred will be subject to the following basic processing activities (please specify):

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

  • Incident Reports Any serious occurrence involving a beneficiary, outside the normal routine of the OTP (see TRICARE Operations Manual (XXX), Chapter 7, Section 4), shall be reported to the referring military providers and/or Military Treatment Facility (MTF)/Enhanced Multi-Service Market (eMSM) referral management office (on behalf of the military provider), and DHA, and/or a designee, as follows: (a) An incident of a life-threatening accident, patient death, patient disappearance, suicide attempt, incident of cruel or abusive treatment, or any equally dangerous situation involving a beneficiary, shall be reported by telephone on the next business day with a full written report within seven days. (b) The incident and the following report shall be documented in the patient’s clinical record. (c) Notification shall be provided, if appropriate, to the parents, legal guardian, or legal authorities.

Most Referenced Clauses

Most Referenced Definitions