Audience: CEO/Owner, General Manager
Read Time: 15 Minutes

This article provides a general overview of the Carey CSI Integration including common application setup requirements and integration expectations. 

Note: You can find details on recent changes to the Carey integration here.

Setup Overview

FASTTRAK now supports integration with Carey allowing for automated creation of reservations into the FASTTRAK environment. The support includes one-way integration for new reservations, updated reservations and cancellations. Once enabled, reservations will be created in FASTTRAK based on the configuration settings chosen below.

Note: Real-time GPS and Status updates also flow back to Carey automatically. Status updates are driven automatically by status changes across all FASTTRAK Applications. GPS data is generated in real-time via the FASTTRAK DriverApp as service passengers on Carey connected trips.

The general process for setting up the Carey Integration is as follows:

1. Customer contacts Carey to request the FASTTRAK integration to be enabled
   • apisupport@carey.com
2. Customer configures FASTTRAK using the steps provided below
   • Contact support@fasttrakcloud.com for questions in FASTTRAK configuration
   • Fasttrak API Token is generated in Fasttrak Ultimate or InVision and provided to Carey
3. Carey enables integration
4. Customer/Carey tests and confirms integration
   • Update vehicle type mapping in FASTTRAK
   • Send reservation from Carey Web UI to Fasttrak via integration
   • Update reservation
   • Cancel Reservation
   • Customer/Carey contacts support@fasttrakcloud.com if issues present

Integration Overview

Once the integration is enabled, all new reservations will be created within a single customer profile. Generally guidelines include:

• This should be your Carey International account that is used currently.  
• This customer profile must be created prior to enabling the Carey integration. 
• The profile name does not need to be specific. 
• Reservations created within the Carey environment will automatically flow to the selected customer profile. 
• The current integration is one-way from Carey to Fasttrak and supports new, updated and cancelled reservations

Important Note: You must be subscribed to Fasttrak Web Services to be eligible to receive Carey Reservations. If you do not see the Web Service User & GPS Setup tab under System Settings, Web Service integration is not enabled for your account. Please contact support@fasttrakcloud.com .

Vehicle Type Mapping Requirements

Carey vehicle types and FASTTRAK vehicle types are not identical. For this reason, FASTTRAK Vehicle types need to be "mapped" to the expected Carey vehicle type in FASTTRAK settings. These settings are shared by all web service integrations and may already be configured in your database.

Vehicle Mappings are completed in the FASTTRAK software:

• FASTTRAK Ultimate: Menu > System, Company & User Setup > System Global Settings > Web Services & eAffiliates
• FASTTRAK InVision: System Setup > Integrated Affiliates & APIs > Integrated Affiliates > Carey

Keep in mind, a “FASTTRAK Web Service Vehicle Type” mapping sits between the Carey vehicle type and your custom FASTTRAK vehicle type. You are not mapping directly to a Carey vehicle type. Instead, you are mapping your custom vehicle types to a FASTTRAK Web Service Vehicle Type, and the Web Service Vehicle Type is mapped to a Carey vehicle type.

For example, to support the “Sedan” vehicle type from Carey, you must map the standard FASTTRAK Web Service Vehicle Type “Sedan (standard)” to one of your custom Vehicle types in FASTTRAK. In the example below, the operator (i.e. you the operator) has created a custom vehicle type named “Sedan XYZ”.

The table below shows the mapping requirement for each vehicle type supported via the Carey integration.  

Known Integration Limitations and Concerns

Carey aggregates data across multiple sources to support direct/single integrations with operators. For this reason, the data that Carey provides via the FASTTRAK connection is not always consistent. Although Carey and FASTTRAK have made significant strides to ensure the integrity of the data, it is important to note minor concerns and inconsistencies. These concerns will be described below.

Carey is the PPRIMARY data manager

FASTTRAK maps data into a variety of fields where pertinent to ensure the operator can efficiently service the trip. Although much of this data has been mapped, it is not always consistent or complete. If the operator modifies data that came from Carey and Carey proceeds to update the data via the integration (source system updates trip, etc.) the operator changes may be overridden.

It is imperative that you the operator review the changes for Carey trips to ensure your operational data has not been modified. Although FASTTRAK has added a great deal of mapping logic, it is not perfect. The only way to ensure the operational integrity of a trip is to review the changes via the options below.

1. New/Update email sent for every successful Carey trip delivery
   • Subject contains summary of trip and summary of any concerns; mapping, changes, pricing, day of dispatch, etc.
   • Body contains details for each concern (noted above)
2. Special Handling flag is set in the following circumstances:
   • Greeter has been requested
   • Mapping issue was found (view email or Affiliate Notes for details)
   • Validation issue found (view email or Affiliate Notes for details) 
3. Trip available/notified for review in Internet Reservations form
4. For updates, the reservation Change Log will describe updated/changed values 

Estimated Hours and End Time

Carey does NOT currently provide this information. The Drop off time within the Carey ecosystem does NOT REQUIRE this field. For this reason, the value is almost never available. Changes to resolve this issue are two fold:

1. FASTTRAK leverage the operators pricing to determine the duration of the trip (IN PLACE CURRENTLY, 4/2022).
   • The default plan for the configured Carey Customer profile will be used to determine pricing plan.
   • If a flat rate zone is matched, the estimated value in that match would be used to calculate estimated hours and estimated end time.
   • If no zone match is found, hourly pricing would be used instead. In this case, the minimum hours will be used to calculate estimated hours and estimated end time.
2. Carey is targeting additional fields to aid in calculating this value. (TENTATIVELY June/July 2022)
   • Carey will provide a garage to garage time estimate with each trip update
   • FASTTRAK will use this value to set estimated hours and calculate estimated end time from scheduled pick-up
   • The default plan for the configured Carey Customer profile will continue to be used to determine pricing plan. 

Airport Mappings Rules and FBOs

FASTTRAK deploys Carey-specific matching logic for Airports. This allows the operator multiple options to handle airport pickup and departures across both commercial and FBO locations. 

The matching logic options are as follows:

• Multiple Airports for specific FBO locations
• Airlines used to represent FBO locations
• Single Airport and do not use Airlines for FBO locations

Depending on the option you choose, matching logic is run to determine the appropriate airport and/or airline to select when a Carey reservation is created/updated.

Multiple Airports for specific FBO locations

If you have created multiple airports for a single Airport code (ex: PHX – Cutter, PHX – Signature and PHX – Sky Harbor Intl, etc.), the Carey matching logic will first find all matching airports by code, then second look within matches for airports that contain the airport name from Carey. If no match is found, the airport is left blank and detail is added to affiliate notes describing the information from Carey so that the operator can make the appropriate changes prior to pick-up.

Airlines used to represent FBO locations

If you have a single primary airport record and leverage multiple airline records to represent FBO locations, the same matching logic will apply; however, it will look at the Airline name and not the Airport name. When creating FBOs as airlines, the designator code” is not important.

Single Airport and do not use Airlines for FBO locations

If you choose to leverage a single airport and do not wish to manage FBOs individually, you do not need to make any changes. The Carey logic will map on Airport code and display additional information in the Pick-up/Drop-Off location field.

Note: Regardless of the option chosen, FBO information will always be written to the Pick-Up/Drop-Off location on the FASTTRAK reservation form.

You can find the list of Carey airports and corresponding names by clicking here. You can use these names to update Airport and/or Airline records in the FASTTRAK software.

If you have any questions, please contact Carey or FASTTRAK Support.

Carey Support: apisupport@carey.com
Fasttrak Support: support@fasttrakcloud.com