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
AutoNDA by SimpleDocs
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. An Incident can be logged by the client by one of the following methods:
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. 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. 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. 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.
AutoNDA by SimpleDocs
Incident Logging 

Related to Incident Logging

  • 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.

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

  • Post-Accident Testing All Employees‌ Post-accident drug and alcohol testing may be conducted by the Employer for any employee when a work-related incident has occurred involving death, serious bodily injury or significant property/environmental damage, or the potential for death, serious bodily injury, or significant property/environmental damage, and when the employee’s action(s) or inaction(s) either contributed to the incident or cannot be completely discounted as a contributing factor. Referral for post-accident testing will be made in accordance with Subsection 22.5 C, above.

  • Sub-processing 11.1 The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub- processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement. 11.2 The prior written contract between the data importer and the sub-processor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the sub-processor shall be limited to its own processing operations under the Clauses. 11.3 The provisions relating to data protection aspects for sub-processing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established, namely ........................................ 11.4 The data exporter shall keep a list of sub-processing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5(j), which shall be updated at least once a year. The list shall be available to the data exporter’s data protection supervisory authority.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Catering Cafeteria style of serving meals will be acceptable, providing dishes are carried back by the Culinary Staff. The food shall be of good quality and have the approval of the Camp Committee of the Building and Construction Trades Council of Ontario. There shall be sufficient housekeeping staff supplied by the Culinary Workers to keep the bunkhouses clean, and beds shall be made up each day by such staff. Kitchen facilities, equipment and food supplies shall be subject to inspection by the duly authorized Camp Committee at any and all times and further all grievances shall be dealt with by said Committee.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!