Dev:SARA.ProcessAutomationEngine

Available Triggers

The SARA Engine is triggered each time, when a special assistance request reaches one of the SAR checkpoints.

• On SAR-Request Claim
• On Journey Entry/Change
• On Segment-Service add/remove
• On Full MEDA Approval
• Full Fit-To-Fly status reached
• Full Confirmend status reached (all Segments HK [holding confirmed] or KK [manually confirmed] )
• On SAR-request Cancel
• Time (in h) before journey start
• Time (in h) before journey end
• Time (in h) before trip start - embarcation event
• Time (in h) before trip end - disembarcation event      
• Time (in h) before segment start
• Time (in h) before segment end
• Time (in h) before port Arrival (or Departure time of first trip segment)
• Time (in h) before port Departure (or Arrival at the last trip Segment)
• On all Segments flown
• On Service capacity limit reached

Supported matching criteria

Once being triggered for a case, the SARA Engine will match the case against matching criteria. If the matching criteria are not fulfilled, no action will be taken.

• Full Request matching - all Segments and ports are included in matching
  • Touches specific regulatory areas
  • Any Segment includes Service Type (like MEDA, PWD, INFO)
  • Any Segment includes SAR Service(s)
  • Any Port includes Technical Services
  • No journey provided
  • Journey starts in x Hours
  • Journey Ends in y hours
• Trip matching - all segments and ports are included in matching
  • Any segment includes a specific SAR Service  
  • Any segment touches specific regulatory areas  
  • Trip embarcs at port
  • Trip disembarcs at port
  • Trip transfers at port
  • Trip contains Segment
  • Trip contains ground Service
  • Trip starts in x Hours
  • Trip Ends in y hours
• Ground Service matching
  • Matched ground or technical services (WCHR, Mounting/Dismantling,...) 
  • Planned at Port
  • Port additional criteria
    • Port of Delivery is Embarcation Port
    • Port of delivery is Transfer port
      • with Prior Segment Arrival rime is (<> xx:yy)
      • with Prior Segment Arrival from (Multiple Source Port Selection)
      • with Next Segment Departure to (Multiple Target Port Selection)
      • with Next Segment Departure time is (<> xx:yy)
    • Port of delivery is Disembarcation Port

• Segment Service matching
  • Matching requested OnSegment Services
  • Segment Departure Port (wildcard allowed)
  • Segment Destination Port (wildcard allowed)
  • Flight Numbers (*, all except)
  • Segment Rotation starts in x hours
  • Segment Rotation ends in x hours
  • Segment arrival time (><*)
  • Segment departure time (><*)

Actions

Each matching rule may define one or multiple actions to be automatically performed

Information Actions

For each of the information actions you have to decide, which information of the case can be included

• Personal information
  • Name-Properties
  • Birthdate
  • Communication-Properties (Phone, Fax, Email)
  • Body/Medical-Information (Weight, Height)
• Booking information
• Classified MEDA information
• Filled placeholders. See placeholderlist.

When it comes to communication generation, there are often also service specific restrictions about what information may be handed out to external parties.

Data Privacy Note: The generated contents for communication or tasks, will then only contain the information which may be included. Even if the template can support more information, it will not be filled.

Generally these information actions are supported:

• Create internal task - Requires a selected task template and needs to define the list of task receivers. Task receivers can be:
  • predefined receipients roles (Passengers, Travel Agent, MOC Team, Doctors Team, Controlling Team)
  • secure receipients (Business participant groups or individual business participants) or
• Create communication - Requires a selected communication template and receipients. Communication receipients can be
  • predefined receipients roles (Passengers, Travel Agent, MOC Team, Doctors Team, Controlling Team)
  • secure receipients (Business participant groups or individual business participants) or
  • insecure receipients (by adding TELEX or EMAIL addresses)
• Perform HandlingAdvice - See this article for details.
• Perform RoutineCheck - This will create a communication for a specific service in a predefined communication template to receipients, which are calculated by a specific logic for the routine check. It typically contains:
  • to all involved service delivery partners (secure/insecure)
  • to eventually involved extra routine check receipients (secure/insecure)

Manipulate SARA Process Flow

• Mark Service as impossible on this segment
• Fit-To-Fly is forbidden for this segment
• Confirmation (HK/KK) is forbidden for this segment
• Comment to show above service section
• Comment to show above service - select service
• Make PAX birthdate mandatory
• Make Ambulance car data is mandatory (driver, plate, ...)
• Add special Email/Telex receipient(s) to Standard Handling Advice for this trip
• Add additional email/Telex receipient(s) to Standard Routine Telex for this trip
• Disable MEDA process flow (if not manually locked)
• Enable MEDA process flow (if not manually locked)