Priority Incident Tracker Sample Clauses

Priority Incident Tracker. The following information shall be continuously monitored, recorded and tracked by Supplier using the Incident Management System. • Priority Level 1 and Priority Level 2 Incident types • Ticket start timeBusiness impact time • Business impact scope • Timeline for Supplier’s delivery of Root Cause Analysis • Resulting impacted SLR based on the Root Cause Analysis • Accumulative Outage time by Availability SLR broken down by Incident and day of the month The Parties will review the priority Incident tracker information during each weekly Operations Review TeamSteady State meeting or any other meeting as agreed to by the Parties so as to align the Parties’ awareness and agreement.
AutoNDA by SimpleDocs

Related to Priority Incident Tracker

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

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

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

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

  • First Lien Status Mortgagor shall preserve and protect the first lien and security interest status of this Mortgage and the other Loan Documents. If any lien or security interest other than the Permitted Encumbrances is asserted against the Mortgaged Property, Mortgagor shall promptly, and at its expense, (a) give Mortgagee a detailed written notice of such lien or security interest (including origin, amount and other terms), and (b) pay the underlying claim in full or take such other action so as to cause it to be released or contest the same in compliance with the requirements of the Credit Agreement (including the requirement of providing a bond or other security satisfactory to Mortgagee).

  • Secured Party Control Bank, Secured Party, Servicer and Company each agree that Bank will comply with instructions given to Bank by Secured Party directing disposition of funds in the Collateral Accounts (“Disposition Instructions”) without further consent by Company or Servicer. Except as otherwise required by law, Bank will not agree with any third party to comply with instructions for disposition of funds in the Collateral Accounts originated by such third party.

  • Priority Hiring If the Contract Amount is over $200,000 and this Agreement is for services (other than Consulting Services), this section is applicable. Contractor shall give priority consideration in filling vacancies in positions funded by this Agreement to qualified recipients of aid under Welfare and Institutions Code section 11200 in accordance with PCC 10353.

  • Priority in Incidental Registrations If (i) a registration pursuant to this Section 3.2 involves an underwritten offering of the securities so being registered, whether or not for sale for the account of the Company, to be distributed (on a firm commitment basis) by or through one or more underwriters of recognized standing under underwriting terms appropriate for such a transaction and (ii) the managing underwriter of such underwritten offering shall inform the Company and holders of the Registrable Securities requesting such registration by letter of its belief that the distribution of all or a specified number of such Registrable Securities concurrently with the securities being distributed by such underwriters would interfere with the successful marketing of the securities being distributed by such underwriters (such writing to state the basis of such belief and the approximate number of such Registrable Securities which may be distributed without such effect), then the Company may, upon written notice to all holders of such Registrable Securities and to holders of such other securities so requested to be included, exclude from such underwritten offering (if and to the extent stated by such managing underwriter to be necessary to eliminate such effect) (i) first, the number of such Registrable Securities so requested to be included in the registration pro rata among such holders on the basis of the number of such securities requested to be included by such holders and (ii) second, shares of such other securities so requested to be included by the holders of such other securities, so that the resultant aggregate number of such Registrable Securities and of such other shares of securities so requested to be included which are included in such underwritten offering shall be equal to the approximate number of shares stated in such managing underwriter’s letter.

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