Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Error rendering macro 'excerpt-include' : No link could be created for 'Documentation - Arrival Revamp'.

This feature is supported for: Resorts that use RTP|One and Aspenware Identity and have a license agreement for Aspenware Arrival.

This feature is NOT supported for: Resorts that use Siriusware.

Key Terms

Resort/Organization

This is the highest level of the Arrival application. This level will have impacts across the entire application. Theming and technical tasks are completed at this level. Resorts can have many Locations.

Location

This is the second level in the Arrival architecture. Locations are composed of Activities. There can be several Locations and each Location can have multiple Activities.

Activity

This is the third level in the Arrival architecture. Activities are composed of Tasks. There can be many Activities under one Location and each Activity can have multiple Tasks.

Task

This is the fourth level in the Arrival architecture. Each task indicates a discreet action that is needed to be taken by the guest. Activities can have multiple tasks.

Description

Airline passengers have been programmed to check-in 24 hours prior to their flights for years now. This allows the airline to capture information on the guest, saves time at the airport, and gives travelers peace of mind that their experience at the airport will be smooth. Aspenware Arrival provides this experience for guests coming to ski and ride at the resort.

Arrival uses Locations, Activities, and Tasks to determine what functions guests will be completing.

  • Locations - A Resort can have several Locations. Each Location will have its own unique URL to which guests can navigate. Each Location requires a default activity. Examples of locations include:

    1. “POS Transactions” - A “POS Transactions” Location might prompt users to complete tasks personalized to them based off of orders placed in your POS system. Whether through an eCommerce store such as Aspenware Commerce or placed directly into the POS through a phone call or resort visit.

    2. “Rental Shop” A “Rental Shop” Location is most likely a configuration used for purchases made by guests who are physically at a rental location on-premise.

  • Activities - An Activity is comprised of one or more tasks. These task may be related to a specific purchase. Examples include:

    1. “Purchases” - This might be an Activity underneath the “POS Transactions” Location. This particular Activity will link to specific tasks that are required to be completed by the guest for the particular product purchases they have where they are missing required information. The guest would only be prompted to fill out specific tasks that they are personally missing based on their orders.

    2. “Ski/Snowboard Rentals” - This might be an Activity underneath the “Rental Shop” Location. Again, this particular Activity will link to specific tasks that are required to be completed by the guest for this particular product purchase.

  • Task - A Task is the specific function that guests will be completing. Tasks supported in Arrival include:

    1. Waiver Signing 

    2. Child Registration Capture

    3. Rental Profile Capture

    4. Photo Capture

Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.

  • No labels