Incident Response by Severity Sample Clauses

Incident Response by Severity. Incident severity levels (defined below) are utilized in establishing the incident impact to the Customer upon incident receipt and will be used to set mutual expectations between Customer and eXo. Severities are established by eXo in accordance with the Severity Levels definitions below and are subject to change during the progress of each specific case.
AutoNDA by SimpleDocs

Related to Incident Response by Severity

  • Incident Response Operator shall have a written incident response plan that reflects best practices and is consistent with industry standards and federal and state law for responding to a data breach, breach of security, privacy incident or unauthorized acquisition or use of any portion of Data, including PII, and agrees to provide LEA, upon request, an executive summary of the written incident response plan.

  • Incident Notice and Remediation If Contractor becomes aware of any Incident, it shall notify the State immediately and cooperate with the State regarding recovery, remediation, and the necessity to involve law enforcement, as determined by the State. Unless Contractor can establish that none of Contractor or any of its agents, employees, assigns or Subcontractors are the cause or source of the Incident, Contractor shall be responsible for the cost of notifying each person who may have been impacted by the Incident. After an Incident, Contractor shall take steps to reduce the risk of incurring a similar type of Incident in the future as directed by the State, which may include, but is not limited to, developing and implementing a remediation plan that is approved by the State at no additional cost to the State.

  • Downtime Due to the nature of server provision, downtime and lost transmissions may occur as part of routine maintenance. You are advised to maintain a copy of your account status and details of Content purchased.

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Client Responsibility For clarity, the parties agree that in reviewing the documents referred to in clause (b) above, Patheon’s role will be limited to verifying the accuracy of the description of the work undertaken or to be undertaken by Patheon. Subject to the foregoing, Patheon will not assume any responsibility for the accuracy of any application for receipt of an approval by a Regulatory Authority. The Client is solely responsible for the preparation and filing of the application for approval by the Regulatory Authority and any relevant costs will be borne by the Client.

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

  • Tenant Responsibility Good housekeeping is expected of everyone. Tenant agrees to keep quarters clean and in a sanitary condition. The Tenants agree not to permit any deterioration or destruction to occur while they are occupying the property.

  • Transmission Delivery Service Implications Network Resource Interconnection Service allows Interconnection Customer's Large Generating Facility to be designated by any Network Customer under the Tariff on Transmission Provider's Transmission System as a Network Resource, up to the Large Generating Facility's full output, on the same basis as existing Network Resources interconnected to Transmission Provider's Transmission System, and to be studied as a Network Resource on the assumption that such a designation will occur. Although Network Resource Interconnection Service does not convey a reservation of transmission service, any Network Customer under the Tariff can utilize its network service under the Tariff to obtain delivery of energy from the interconnected Interconnection Customer's Large Generating Facility in the same manner as it accesses Network Resources. A Large Generating Facility receiving Network Resource Interconnection Service may also be used to provide Ancillary Services after technical studies and/or periodic analyses are performed with respect to the Large Generating Facility's ability to provide any applicable Ancillary Services, provided that such studies and analyses have been or would be required in connection with the provision of such Ancillary Services by any existing Network Resource. However, if an Interconnection Customer's Large Generating Facility has not been designated as a Network Resource by any load, it cannot be required to provide Ancillary Services except to the extent such requirements extend to all generating facilities that are similarly situated. The provision of Network Integration Transmission Service or firm Point-to-Point Transmission Service may require additional studies and the construction of additional upgrades. Because such studies and upgrades would be associated with a request for delivery service under the Tariff, cost responsibility for the studies and upgrades would be in accordance with FERC's policy for pricing transmission delivery services. Network Resource Interconnection Service does not necessarily provide Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on Transmission Provider's Transmission System without incurring congestion costs. In the event of transmission constraints on Transmission Provider's Transmission System, Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in Transmission Provider's Transmission System in the same manner as Network Resources. There is no requirement either at the time of study or interconnection, or at any point in the future, that Interconnection Customer's Large Generating Facility be designated as a Network Resource by a Network Service Customer under the Tariff or that Interconnection Customer identify a specific buyer (or sink). To the extent a Network Customer does designate the Large Generating Facility as a Network Resource, it must do so pursuant to Transmission Provider's Tariff. Once an Interconnection Customer satisfies the requirements for obtaining Network Resource Interconnection Service, any future transmission service request for delivery from the Large Generating Facility within Transmission Provider's Transmission System of any amount of capacity and/or energy, up to the amount initially studied, will not require that any additional studies be performed or that any further upgrades associated with such Large Generating Facility be undertaken, regardless of whether or not such Large Generating Facility is ever designated by a Network Customer as a Network Resource and regardless of changes in ownership of the Large Generating Facility. However, the reduction or elimination of congestion or redispatch costs may require additional studies and the construction of additional upgrades. To the extent Interconnection Customer enters into an arrangement for long term transmission service for deliveries from the Large Generating Facility outside Transmission Provider's Transmission System, such request may require additional studies and upgrades in order for Transmission Provider to grant such request.

  • Payment Responsibility The payment obligations of each Participating Manufacturer pursuant to this Agreement shall be the several responsibility only of that Participating Manufacturer. The payment obligations of a Participating Manufacturer shall not be the obligation or responsibility of any Affiliate of such Participating Manufacturer. The payment obligations of a Participating Manufacturer shall not be the obligation or responsibility of any other Participating Manufacturer. Provided, however, that no provision of this Agreement shall waive or excuse liability under any state or federal fraudulent conveyance or fraudulent transfer law. Any Participating Manufacturer whose Market Share (or Relative Market Share) in any given year equals zero shall have no payment obligations under this Agreement in the succeeding year.

  • OUR RESPONSIBILITY FOR LOSS OR DAMAGE SUFFERED BY YOU 14.1 We are responsible to you for foreseeable loss and damage caused by us. If we fail to comply with this Agreement, we are responsible for loss or damage you suffer that is a foreseeable result of our breaking this Agreement or our failure to use reasonable care and skill, but we are not responsible for any loss or damage that is not foreseeable. Loss or damage is foreseeable if either it is obvious that it will happen, or if, at the time the Agreement is made, both we and you knew it might happen. We are not responsible for any loss or damage you suffer which is a result of you breaking this Agreement or you acting fraudulently.

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