Recovery Service. In the event a Booked Flight scheduled to be performed during the non- Peak Travel Days within the continental U.S. Canada, Mexico, and the Caribbean is cancelled due to a Force Majeure event related to a SIG Program Aircraft, XO shall arrange alternative service for SIG Member on a SIG Program Aircraft at no additional cost to SIG Member (“Recovery Service”). XO reserves the right to provide the Recovery Service on a SIG Program Aircraft that is lower in class than the SIG Program Aircraft originally assigned to perform the Booked Flight. Recovery Service may depart from any airport within a 100-mile radius of the origin airport of each Flight Segment of the Booked Flight. XO does not guarantee the time frame in which the Recovery Service will be provided. In the event SIG Member does not approve a Trip Itinerary for the Recovery Service within twenty four hours of its receipt, both Parties will be released from their obligations related to the cancelled Booked Flight, including without limitation provision of the Recovery Service.
Recovery Service. Recovery services will be provided by the service provider that we choose from time to time. The current provider of Recovery Services is Europ Assistance. We will notify you of any changes to the service provider. Recovery service benefits of 1-year are included for free.
Recovery Service. 15. In the event of theft or hijacking Mix shall use its reasonable endeavours to trach and recover the asset.
Recovery Service. Unless otherwise specified in the Program Agreement, if a Booked Flight is cancelled, interrupted or delayed for any reason other than Program Member delays, XO will use commercially reasonable efforts to arrange alternative service for Program Member in similar cabin class (such service, herein referred to as “Recovery Service”) on an XOJET Aviation Aircraft (at no additional cost than as set forth in the original Flight Itinerary for the Booked Flight), or if an XOJET Aviation Aircraft is not available, an Other Air Carrier Aircraft (which may require the payment of additional fees). In the event Recovery Service is to be provided on an Other Air Carrier Aircraft, XOJET shall issue a new Flight Itinerary, Flight Invoice and Charter Terms (collectively “Recovery Service Documentation”) for such Recovery Service and Program Member shall have the right to approve such Recovery Service (in the same manner as provided in these Charter Terms). If the Program Member agrees to a Recovery Service on an Other Air Carrier Aircraft, Program Member is responsible for the cost of the Recovery Service set forth in the Recovery Service Documentation (inclusive of the Flight Cost and Flight Expenses for the Recovery Service) for such Recovery Service. Payment for the Recovery Service shall be made pursuant to Section 3.1. In the event a Booked Flight involves multiple Flight Segments, some of which were cancelled, interrupted, or delayed by XO or Air Carrier for any reason other than Program Member delays, Passenger will be charged only for the Flight Segments performed and the applicable Recovery Service will be only for the Flight Segments that were cancelled, interrupted or delayed.
Recovery Service. As was defined in D2.1, the Recovery Service assures the SCHI's resiliency by organizing the recovery activities needed when a platform or capability is deemed untrustworthy or when a defect or breach is discovered. The recovery options are many and varied in nature: a platform may be rebooted or isolated by rerouting network traffic around it, a Security Capability can be re-configured or implemented with a new solution, and so on. Such a wide range of recovery activities necessitates a flexible method of picking the best recovery approach for each case, such as changeable playbooks. The RS implementation also uses the FSMs similarly to the Data Breach implementation. The structure of the RS component consists of the same building blocks: Spring Boot application, Spring Statemachine, Xxxxx and Camel with Swagger UI. Figure 20 depicts the diagram and flow of the RS component. The following example was presented on the PALANTIR December 2021 GA meeting. A Xxxxx producer (e.g. the AE) is sending to the topic “palantir_demo_1” while on the Spring Boot application Xxxxx consumer is subscribed to the same topic and retrieves the incoming JSON based message. Here JSON contained the “ddos” threat name. Based on received threat name FSM RS1 started its execution. Because threat was categorized as a “ddos” FSM chooses its right branch and first state “SOFTWARE” and state “SERVICE RECONFIGURE”. From there, the next state was called as a Java Bean. This Java Bean is a Xxxxx client (i.e. a Xxxxx producer and consumer in the same time) listening on different topics. First, the Xxxxx producer sends a message to topic “palantir_demo_2” and another external Xxxxx consumer waits for a message on that topic. Once the message is received, it is up to operator to conclude the FSM by sending a confirmation message. However, this confirmation message is sent to a different topic “palantir_demo_3”, which the Xxxxx consumer inside the FSM is waiting to reach the final “END” state. Figure 20: RS Component Structure proposition with FSM model.
