Topic:
Expected location calculation behavior and configuration options when using travel connectors such as AMEX, ISOS, Anvil, et al. with Everbridge Suite.
Description:
Itineraries may contain multiple locations. When using a travel connector, upon ingestion, the traveler expected location is updated. This Knowledge Base Article explains how those locations are calculated based on how each option (event) is configured.
NOTE: h = hour/hours
Expected Locations:
Expected locations created from travel itineraries are set by default to start 24h before the traveler departs from a specific location and expire 24h after the traveler reaches a specific location.
For instance, if a traveler is leaving their home to take a flight, they will be considered at the airport 24h before the scheduled departure time for the flight. In the same way, a traveler reaching a destination will be considered at that location for 24h after the expected arrival date and time.
- For flight and train segments, two expected locations are created. (See the special case for Transit under Expected Location Calculation for Transit below.)
- For a car segment, two expected locations are created.
- For a hotel segment, a single expected location is created.
The default times are configurable under Settings > Map > Location Data Sources > Defaults.
The below table describes each event available, its default value, the configuration options for that event, and recommended (best practice) values for each event.
| Event | Default Value | Configuration options (can be enabled individually) | Recommended Best Practice |
|---|---|---|---|
| Hotel Check-In Note: One hotel segment has one expected location |
The original hotel check-in time | Point in time: The time configured as the check-in time. The time-zone is the hotel's local time zone OR Length of time prior to check-in |
4PM |
| Hotel Check-Out Note: One hotel segment has one expected location |
The original hotel check-out time | Point in time: The time configured as the check-out time. The time-zone is the hotel's local time zone OR Length of time prior to check-out |
10AM |
| Flight Departure | 24h prior to departure | 1h to 12h (by hour increment) prior to departure | 3h |
| Flight Arrival | 24h after arrival | 1h to 12h (by hour increment) after arrival | 2h |
| Train Departure | 24h prior to departure | 1h to 12h (by hour increment) prior to departure | 1h |
| Train Arrival | 24h after arrival | 1h to 12h (by hour increment) after arrival | 1h |
| Max Flight/Train Connection Time | 4h | 1h to 12h (by hour increment) | 4h |
| Car Rental Pick Up | 24h before pickup | 1h to 12h (by hour increment) before pickup | 1h |
| Car Rental Return | 24h after return | 1h to 12h (by hour increment) after return | 1h |
| Other | 24h | 1h to 12h (by hour increment) |
Changes will apply to all newly created or updated itineraries for the entire organization. (Expected locations for existing itineraries will not be re-calculated.)
Maintain Contact at Their Expected Location
Because of the expected location range, by default for a multi-segment itinerary, it is possible that an expected location may start some time after the expiration of the previous one. When that occurs,the traveler has no expected locations for the time period between when the last expected location expires and the new expected location starts and cannot be alerted if a risk event occurs.
In this case, you can configure the system to keep the traveler in its expected location until the start of the next one by turning on the toggle Maintain traveler at their expected location under Settings > Map > Location Data Sources > Defaults.
Enabling that specific toggle, will allow filling the gap between the expiration of an expected location and the start of the next expected location.
Example 1: Day trip from Boston to Chicago
Example 2: Overnight trip from Boston to Chicago
NOTE: This option does not work if expected locations are in different itineraries. All expected locations must be in the same itinerary.
Expected Location Calculation for Transit
By default, for Air and Train segments, an expected location is created for each side of the segment (arrival and departure), however a single expected location will be created in the case of transit.
Transit occurs when the traveler arrives and departs from the same airport/train station within (by default) 4h. The max transit time is also configurable and can be extended/reduced from 1h to 12h.
In the case of transit, the expected location range will ALWAYS take the earliest to the latest of the dates/times (calculated or actual arrival/departure). If the default configuration is used, the calculated expected location range for transit will be:
- Start: 24h before the departure date/time of the 2nd segment.
- End: 24h after the arrival date/time of the 1rst segment.
Example: Trip from BOS to LAX with three hour layover at ORD. Depart BOS at 9AM, Arrive ORD at 11AM, Depart ORD at 2PM Arrive LAX at 7PM
If the configuration was changed with X being the time PRIOR to departure and Y the time AFTER arrival, the expected location range for transit will be:
- Start: Xh before the departure date/time of the 2nd segment.
- End: Yh after the arrival date/time of the 1rst segment.
EXCEPT in the following conditions:
If X + Y is less than the actual transit time, then in this case the calculation takes the actual arrival and departure times.
If Y < Transit time AND X > Transit Time, then in this case the range will be
- Start: Xh before the departure date/time of the 2nd segment.
- End: Actual departure time of the 2nd segment.
If X < Transit Time AND Y > Transit time, then in this case the range will be
- Start: Actual Arrival time of the 1rst segment.
- End: Yh after the arrival date/time of the first segment.
Article Feedback
Please sign in to leave a comment.