General Incident/Issue Sample Clauses

General Incident/Issue. A general incident is typically a situation where functionality for a town supported equipment or software application does not work as expected. This could be an individual incident or one that affects multiple users (staff or customers). Acknowledgement: 4 hours during business hours Timeline: Troubleshooting work to start within 1 day since acknowledgement. Regular status update to be provided to OPL.
AutoNDA by SimpleDocs

Related to General Incident/Issue

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Data Incidents Merchant must report all instances of a Data Incident (as defined in the American Express Merchant Operating Guide) immediately to ISO after discovery of the incident. Merchant must ensure data quality and that Transaction Data and customer information is processed promptly, accurately, and completely, and complies with the American Express Technical Specifications. THE FOLLOWING SERVICES ARE PROVIDED BY ISO ONLY. Bank shall not have any obligation or liability of any nature in connection with such services. PART THREE

  • Accident and Incident Investigations An accident, injury, critical injury, or hazardous situation will be investigated in accordance with the CJHSC’s investigation protocol.

  • Description of Services (a) Services Provided on an Ongoing Basis, If Applicable.

  • Description of Service 2.14.1.1 BellSouth shall make available to <<customer_name>> loop makeup (LMU) data for BellSouth's network facilities. This section addresses LMU as a preordering transaction, distinct from <<customer_name>> ordering any other service(s). Loop Makeup Service Inquiries (LMUSI) for preordering loop makeup are likewise unique from other preordering functions with associated service inquiries (SI) as described in this Agreement.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Security Incident Notification The Transfer Agent shall promptly notify the Trust but in no event later than 72 hours following discovery of any Security Incident(s). Such notification shall include the extent and nature of such intrusion, disclosure, or unauthorized access, the identity of the compromised Customer Confidential Information (to the extent it can be ascertained), how the Transfer Agent was affected by the Security Incident, and its response to such Security Incident. The Transfer Agent shall use continuous and diligent efforts to remedy the cause and the effects of such Security Incident in an expeditious manner and deliver to the Trust a root cause analysis and future incident Mitigation plan with regard to any such incident. The Transfer Agent shall reasonably cooperate with the Trust’s investigation and response to each Security Incident. If the Trust determines in its sole discretion that it may need or be required to notify any individual(s) as a result of a Security Incident, the Trust shall have the right to control all such notifications and the Transfer Agent shall bear all direct costs associated with the notification, to the extent the notification and corresponding actions are required by U.S. law, and subject to the limitation of liability set forth in the Agreement. Without limiting the foregoing, unless otherwise required by U.S. law, no such notifications shall be made by the Transfer Agent without the Trust’s prior written consent and the Trust shall, together with the Transfer Agent, determine the content and delivery of all such notifications. For the avoidance of doubt, the Transfer Agent shall be solely responsible for all costs and expenses, subject to the limitations of liability under the Agreement that the Trust and/or the Transfer Agent may incur to the extent that they are attributable to or arise from the Transfer Agent’s breach of its confidentiality obligations under the Agreement.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • PROCEDURE FOR DEALING WITH SAFETY ISSUES OR INCIDENTS 11.1 The Employer, the Employees and the Union agree that for the purposes of s. 81 of the WHS Act matters about work health and safety arising at the workplace shall be resolved in accordance with this procedure.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.