Fault & Breach Management Sample Clauses

Fault & Breach Management. The Fault & Breach Management (FBM) component aims to enable the design and deployment of procedures and strategies with regard to fault and breach management and remediation by unifying, correlating and automating event handling across the end-to-end physical and virtual infrastructure. The FBM utilizes inputs from the RR and the AE in a management and orchestration ‘platform’ for semi-automated design and deployment of notification, management and remediation policies. These policies are personalized by network/service operators and are modelled to their specific requirements like specific mechanisms to be triggered after a security issue is detected. The goal of this component is to personalize the triage, reduce triage and mean-time-to-repair as well as to minimize exposure, while improving communication and collaboration. To this end, the FBM interacts with the TI, the SCO and the Portal Dashboard using Xxxxx protocol and topics.
Sample 1
AutoNDA by SimpleDocs
Fault & Breach Management. D2.1 specifies the generic requirements for most PALANTIR components and then specific requirements for each component. This section describes how the FBM meets those requirements in Table 2.
Sample 1
Fault & Breach Management. The initial FBM infrastructure is hosted on the Proxmox Virtual Environment (VE) [9], where each component is deployed as a Virtual Machine (VM). As depicted Figure 16, there are 3 VMs (components) building the architecture of the FBM. Figure 16 outlines the experimental and development infrastructure established for the PALANTIR project. After the technologies are developed, the component is pushed to the common PALANTIR testbed. The Spring Boot application include and runs the Apache Camel 3.9.0 [10], Swagger (webjars)
Sample 1

Related to Fault & Breach Management

  • Independence from Material Breach Determination Except as set forth in Section X.D.1.c, these provisions for payment of Stipulated Penalties shall not affect or otherwise set a standard for OIG’s decision that CHSI has materially breached this CIA, which decision shall be made at OIG’s discretion and shall be governed by the provisions in Section X.D, below.

  • Event of Breach Remedies 14.1. Event of Breach by Contractor. Any one or more of the following Contractor acts or omissions constitute an event of material breach under this Contract:

  • Default by Developer If Developer causes either an Event of Monetary Default or an Event of Non-Monetary Default, then the City may commence proceedings to modify or terminate this Agreement pursuant to this Section 11.4.

  • Breach of Conditions Where a loss occurs and there has been a breach of condition relating to a matter before the happening of the loss, which bre ach would otherwise disentitle the Insured from recovery under this Form, the breach shall not disentitle the Insured from recovery if the Insured establishes that the loss was not caused or contributed to by the breach of condition or if the breach of condition occurred in any portion of the project over which the Insured has no control.

  • Event of Breach by Contractor Any one or more of the following Contractor acts or omissions constitute an event of material breach under this contract:  products or services furnished fail to conform to any requirement;  failure to submit any report required by this contract;  failure to perform any of the other terms and conditions of this contract, including but not limited to beginning work under this contract without prior Department approval; or  voluntary or involuntary bankruptcy or receivership.

  • Breach; STATE’s Remedies If PURCHASER fails to remedy a violation within the time allowed and as instructed by STATE, or if PURCHASER fails to complete work as required within any interim contract completion date or by the contract expiration date, PURCHASER is in breach, and STATE may pursue any and all remedies available to STATE. Such remedies include, but are not limited to: (1) making a claim on each bond provided by PURCHASER; (2) suing PURCHASER for all damages STATE incurs as a result of PURCHASER's breach; (3) suing PURCHASER for specific performance of the contract; (4) terminating the contract and reselling the breached contract; and (5) declaring PURCHASER in default, in accordance with the provisions of OAR 629- 032-0000 through 0070 (as adopted at the time of contracting and as may be amended later by the agency having jurisdiction or authority over such activities). The provisions of OAR 629-032-0000 through 0070, and any future amendments, are incorporated into this contract and made a permanent part hereof by reference as though fully set forth herein. THE PROVISIONS OF OAR 629-032-0000 THROUGH 0070 ARE IN ADDITION TO, AND NOT IN LIEU OF, ANY OTHER REMEDIES STATE MAY HAVE FOR THE PURCHASER'S BREACH OF CONTRACT. NOTICES, PLANS, AND INSPECTIONS Section 35. Work Responsibility and Acceptance. Prior to the completion and final acceptance of operations, PURCHASER shall be held responsible for, and shall correct any injury or damage to, the operations or any part of the operations, from any cause whatsoever, unless adjustment is made pursuant to Section 28. STATE shall make final inspection of operations done by PURCHASER within 10 calendar days after written notification is received by STATE from PURCHASER stating that the operation is complete. Following inspection, STATE shall notify PURCHASER of acceptance in writing. If the operation is not acceptable to STATE, STATE shall advise PURCHASER in writing of the particular defects to be remedied before final acceptance by STATE can be made.

  • Developer Default Each of the following shall be an Event of Default by Developer:

  • Customer Default The occurrence at any time of any of the following events shall constitute a “Customer Default”:

  • Breach of Covenant The Borrower breaches any material covenant or other term or condition of the Subscription Agreement or this Note in any material respect and such breach, if subject to cure, continues for a period of ten (10) business days after written notice to the Borrower from the Holder.

  • Breach and Default 7.6.1 No Breach of this Agreement shall exist where such failure to discharge an obligation (other than the payment of money) is the result of a Force Majeure Event or the result of an act or omission of the other Parties. Upon a Breach, the non-breaching Party shall give written notice of such Breach to the Breaching Party. Except as provided in article 7.6.2, the Breaching Party shall have 60 calendar days from receipt of the Breach notice within which to cure such Breach; provided however, if such Breach is not capable of cure within 60 calendar days, the Breaching Party shall commence such cure within 20 calendar days after notice and continuously and diligently complete such cure within six months from receipt of the Breach notice; and, if cured within such time, the Breach specified in such notice shall cease to exist.

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