Latency recommender
Through the waiting time recommendation system, the waiting time is compared using historical data and context information, the problem of inaccurate prediction of scenic spots is solved, and the information selection of guests and the operational efficiency of theme parks is improved.
Patent Information
- Application Number
- CN202411268001.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2018-10-02
- Filing Date
- 2019-10-01
- Publication Date
- 2024-12-06
AI Technical Summary
The prior art is difficult to accurately predict and notify the waiting time of attractions, making it difficult for guests to make informed decisions, affecting the distribution of passenger flow and customer satisfaction in theme parks and other places.
Through the waiting time recommendation system, using the waiting time historical data and context information, the existing waiting time is compared with the expected waiting time, determine whether it is shorter or longer than expected, and send notifications to the guest's mobile device to recommend the waiting time of the attraction.
It improves the customer experience and customer satisfaction in the theme park, helps guests make more informative choices, optimizes the passenger flow distribution of attractions, and improves the operational efficiency of the theme park.
Smart Images

Figure CN119090088A_ABST
Abstract
Description
Background Art
[0001] The present disclosure generally relates to wait times for attractions. More specifically, embodiments of the present disclosure relate to determining wait times for attractions that are shorter or longer than expected and notifying guests of these shorter or longer wait times.
[0002] This section is intended to introduce the reader to various aspects of the art that may be relevant to the various aspects of the present technology described and / or claimed below. It is believed that this discussion helps to provide the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Therefore, it should be understood that these statements will be read in this context and not as an admission of the prior art.
[0003] Many places or service providers such as theme parks, restaurants, ticket sellers, government agencies, etc. may include teams or queues for customers to obtain services. For example, a theme park may include multiple attractions, each of which has at least one team. Therefore, each team at each attraction may include a corresponding waiting time. Guests at the theme park may decide which attraction to attend based on multiple factors, including preferences for attractions, distance to the attractions, time of day, weather, and the waiting time (or length) of the corresponding team. In some cases, the corresponding waiting time may be provided via a software application on the guest's mobile device, although any suitable device may be used to display or transmit the corresponding waiting time, such as a signage inside the theme park, a signage at each attraction, a notice on a website associated with the theme park, or a notice via a chatbot on a notice platform.
[0004] However, if more information is available (such as whether the wait time for the corresponding line is shorter or longer than the typical or expected wait time), the guest can make a better informed decision about which attraction to attend. Summary of the invention
[0005] Certain embodiments commensurate in scope with the originally claimed subject matter are summarized below. These embodiments are not intended to limit the scope of the present disclosure, but rather these embodiments are intended only to provide a brief summary of certain disclosed embodiments. In fact, the present disclosure may encompass a variety of forms that may be similar to or different from the embodiments set forth below.
[0006] The present disclosure provides systems and methods for determining whether the waiting time of an attraction is shorter or longer than expected and notifying guests of these shorter or longer waiting times. In particular, a theme park may include multiple attractions, each of which has at least one team. Therefore, each team of each attraction may include or be associated with a corresponding waiting time at a given time. The corresponding waiting time may be communicated to the guest via a software application on the guest's mobile device, which may display information and tools related to the theme park, such as operating hours, the status of the attraction, and the waiting time of the attraction, although any suitable device may be used to display or transmit this information, such as signs inside the theme park, signs at each attraction, notices on a website associated with the theme park, or notices made via a chatbot on a notification platform.
[0007] The waiting time recommendation system can use waiting time history data, which includes waiting times for attractions in the park, and is used to determine historical waiting times, expected waiting times, or typical waiting times for various attractions. These waiting times can be provided for each attraction and / or as a percentage of the total collected waiting time for all attractions. In one embodiment, the expected waiting time can be expressed as an expected ratio or percentage of the total waiting time of the park represented by a separate attraction (for example, 5-7% of the expected total waiting time of the park can be represented by a single attraction). The waiting time recommendation logic of the waiting time recommendation system can determine the current waiting time value or the existing waiting time value.
[0008] In one embodiment, the waiting time value of the attraction is based on the relationship between the existing waiting time of the individual attraction and the total existing waiting time of all attractions in the theme park. The existing waiting time of the attraction or the calculated waiting time value representing the relationship between the existing waiting time of the attraction and the total existing waiting time of all attractions can be compared with the historical data to determine whether any individual attraction is outside the expected limit, for example, having a longer or shorter waiting time than expected. For example, if the individual attraction typically represents at least 5% of the typical total park waiting time, then the existing waiting time that represents less than 5% of the current total park waiting time can be considered to be shorter than the expected waiting time. In another embodiment, the existing waiting time can be directly compared with the historical waiting time with a given context to evaluate whether the existing waiting time is shorter or longer than expected. That is, instead of comparing the existing waiting time with the overall average historical waiting time, the historical waiting time used in the comparison can be selected from the same day or the same park population (e.g., using the total park guests on the day) subset of the data point.
[0009] If the wait time recommendation logic determines that the wait time value is less than the short wait time threshold (e.g., ratio or percentage), the wait time recommendation logic can send a notification to the software application on the guest's mobile device that the wait time is shorter than expected. If the wait time recommendation logic determines that the wait time value is greater than the long wait time threshold (e.g., ratio or percentage), the wait time recommendation logic can send a notification to the software application on the guest's mobile device that the wait time is longer than expected. The short wait time threshold and the long wait time threshold can be based on the expected wait time ratio of the attraction. The expected wait time value can be based on historical wait time data for attractions and theme parks, date or time information (such as time of day, day of the week, week of the year or quarter), weather, characteristics of the attraction (such as whether the attraction is outdoor or indoor), whether the attraction is open or closed (e.g., for a time range), or holiday or event date (e.g., public holidays such as Thanksgiving or Christmas, school holidays such as spring break, or religious holidays such as Easter). Then, guests can use the notification that the wait time is shorter or longer than expected as a factor when deciding whether to wait in the queue of the attraction.
[0010] In one embodiment, a waiting time recommendation system includes a processor, a memory, and a communication circuit. The memory stores instructions that, when executed by the processor, cause the processor to receive existing waiting times for attractions in a theme park and determine a waiting time value based on a relationship between the existing waiting time of the individual attractions and the existing total waiting time of the attractions in the theme park. The instructions also cause the processor to generate a waiting time recommendation for the individual attractions based on a comparison of the waiting time threshold of the individual attractions with the waiting time value. The communication circuit can then send an indication of the waiting time recommendation to a waiting time recommendation software application of a mobile device.
[0011] In another embodiment, a tangible, non-transitory computer-readable medium includes instructions for generating a wait time recommendation for an attraction at a theme park. The instructions, when executed by a processor, cause the processor to receive a total wait time for an attraction at the theme park, receive a wait time for the attraction, and compare the wait time or wait time value for the attraction to a threshold value associated with the attraction. The wait time value is based on the total wait time and the wait time for the attraction. The instructions also cause the processor to send a notification based on the comparison.
[0012] In yet another embodiment, a method for generating wait time recommendations includes receiving wait times for attractions at a theme park, and determining a wait time value for each individual attraction based on the wait times. The method also includes comparing the wait time value for each individual attraction to a wait time threshold for each individual attraction, and identifying a subset of attractions based on the comparison, the subset of attractions having wait time values that indicate shorter than expected wait times. The method also includes sending a notification including an indication of the subset. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] These and other features, aspects and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings, in which like characters refer to like parts throughout the drawings, and in which: Figure 1 is a block diagram of a waiting time recommendation system according to an embodiment of the present disclosure; Figure 2 is a flowchart of a process for generating wait time recommendations for attractions in a theme park based on total wait times for multiple attractions in a theme park according to an embodiment of the present disclosure; Figure 3 is a flow chart of a process for generating wait time recommendations for attractions in a theme park based on park attendance according to an embodiment of the present disclosure; Figure 4 is an example screenshot of a theme park software application for providing theme park information to theme park guests according to an embodiment of the present disclosure; Figure 5 A graphical notification having a shorter than usual waiting time according to an embodiment of the present disclosure Figure 4 Example screenshots of all the wait time pages for the theme park software app; Figure 6 A text-based instruction with shorter than usual waiting time according to an embodiment of the present disclosure Figure 4 Another example screenshot of the all wait times page for the theme park software application; Figure 7 According to an embodiment of the present disclosure, when the waiting time of the line at the scenic spot changes to be shorter than the usual waiting time, Figure 4 Another example screenshot of the all wait times page for the theme park software application; Figure 8 is an example screenshot of a chat user interface that may provide wait time recommendations according to an embodiment of the present disclosure; and Fig. 9 is an example screenshot of an employee dashboard that may provide wait times and wait time recommendations according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0014] The present disclosure provides systems and methods for determining shorter or longer waiting times for attractions than expected and notifying guests of these shorter or longer waiting times. In particular, a theme park may include multiple attractions, each of which has at least one team. Therefore, each team at each attraction may include a corresponding waiting time. The corresponding waiting time may be provided to the guest, for example, via a software application on the guest's mobile device or a display board within the theme park. In some cases, the theme park may provide a software application to the guest, which may display information and tools related to the theme park, such as operating hours, the status of the attractions, and the waiting time for the attractions.
[0015] The waiting time recommendation system can provide a notification when it is determined that the waiting time of an attraction is shorter or longer than expected (by, for example, comparing the waiting time of the attraction with the waiting time history data of the attraction). The waiting time history data can take into account date or time information (such as time of day, day of the week, week of the year or quarter), weather, characteristics of the attraction (such as whether the attraction is outdoor or indoor), whether the attraction is open or closed (for example, for a time range), holiday or event date (for example, public holidays such as Thanksgiving or Christmas, school holidays such as spring break, or religious holidays such as Easter), weather information (for example, related to temperature, humidity, probability or amount of rainfall, probability of natural disasters, etc.), parades, performances, or other performances occurring nearby, or any other suitable information that may affect the waiting time or delay the waiting time. Then, guests can use the notification that the waiting time is shorter or longer than expected as a factor when deciding whether to wait in the queue of the attraction. In this way, guests can make more informed decisions about which attraction to wait for and maximize their time in the theme park. In addition, theme park operations can be more efficient because guests can be more evenly distributed between attractions. That is, if one or more attractions are underserved, the disclosed technology can alert guests, thereby encouraging redistribution of guests to one or more underserved attractions. It should be noted that although the present disclosure describes embodiments for theme parks and attractions, the presently disclosed systems and methods can be applied to any suitable venue for line wait time analysis, such as restaurants, ticket sellers, government agencies, etc.
[0016] The disclosed technology provides guests with improved context for wait time estimates. For example, if the wait time for a particular ride is 35 minutes, that 35 minutes may be longer than expected for that ride if the park is relatively empty or on a rainy day, but may be shorter than expected on a crowded day / clear day. Furthermore, ranking rides by estimated wait time does not provide guests with information about which rides tend to be more crowded or more popular. By providing a quality assessment of wait time on a per-ride basis (e.g., shorter than expected, longer than expected), guests can determine which rides are good value and enjoy the feeling of getting a bargain on wait time (even for rides with long absolute wait times relative to other rides in the park), thereby improving guest experience and customer satisfaction.
[0017] Figure 1 1 is a block diagram of a waiting time recommendation system 10 according to an embodiment of the present disclosure. The waiting time recommendation system 10 includes a controller 12, which includes one or more processors 14 and one or more memory devices 16. The processor 14 can execute software programs and / or instructions to determine waiting time recommendations. In addition, the processor 14 may include multiple microprocessors, one or more "general-purpose" microprocessors, one or more special-purpose microprocessors, and / or one or more application-specific integrated circuits (ASICs), and / or one or more reduced instruction set (RISC) processors. The memory device 16 may include one or more storage devices, and may store machine-readable and / or processor-executable instructions (e.g., firmware or software) for the processor 14 to execute, such as instructions related to determining waiting time recommendations. Therefore, the memory device 16 may store, for example, control software, lookup tables, configuration data, etc., to facilitate determining waiting time recommendations. In some embodiments, the processor 14 and the memory device 16 may be external to the controller 12. The memory device 16 may include tangible, non-transitory machine-readable media such as volatile memory (e.g., random access memory (RAM)) and / or non-volatile memory (e.g., read-only memory (ROM), flash memory, a hard drive, and / or any other suitable optical, magnetic, or solid-state storage media).
[0018] The controller 12 may employ a wait time recommendation logic that determines a wait time recommendation for an attraction 34 of a theme park. In particular, the wait time recommendation may include an indication that the wait time is shorter than expected, longer than expected, or as expected. The wait time recommendation may also include an expected (e.g., typical or usual) wait time, an indication of how much shorter or longer the wait time is than expected (e.g., presented as a total time such as saved minutes or additional minutes of waiting, or presented as a percentage (e.g., 10% shorter or longer than normal)). It should be understood that the term "logic" as used in the present disclosure may include hardware (such as circuits), software (such as instructions stored in the memory 16 for execution by the processor 14), or a combination of both. The wait time recommendation logic may use the wait time history data 22 as an input. The wait time history data 22 may be stored in the memory 16 and / or provided in a database. For example, the wait time recommendation system 10 may include a database that stores the wait time history data 22 and returns the requested wait time history data 22 in response to receiving a query from the wait time recommendation logic.
[0019] In one embodiment, the waiting time recommendation logic can determine the waiting time recommendation by determining the waiting time value of the scenic spot. The waiting time value can represent the ratio of the existing waiting time of an scenic spot to the total waiting time of all scenic spots in the theme park. Therefore, the waiting time recommendation logic can determine the waiting time value by dividing the existing waiting time of the scenic spot by the total existing waiting time of all scenic spots (e.g., at the current time or in a rolling time window). The waiting time value can be compared with one or more historical waiting time values calculated in the same manner, but using the waiting time history data 22. The historical total waiting time can be the average value of the total waiting time of all scenic spots in any suitable time period, or a subset of the historical waiting time data points can be used based on the context information (e.g., a day, a week, a quarter, or a year) provided herein. In some embodiments, the historical total waiting time can be the average value of the total waiting time for the time period corresponding to the current time or day for which the waiting time recommendation is requested. For example, the historical total wait time can be an average of the total wait times corresponding to the same date (for multiple years), the same time (for multiple dates), similar weather (for multiple dates), similar characteristics (e.g., weekend wait times, holiday wait times, or parades, performances, or other performances occurring nearby), similar attraction status (e.g., the attraction is closed), or any other similar suitable information that may affect the wait time. In addition, factors that may lag the historical total wait time can be taken into account, such as by adjusting the lagged historical total wait time to compensate for the lag factor.
[0020] Then, the waiting time recommendation logic can compare the waiting time value with the expected or historical waiting time value. The expected (e.g., typical or usual) waiting time value can be a ratio based on the following: historical waiting time data for attractions and theme parks, date or time information (such as time of day, day of the week, week of the year or quarter), weather and / or characteristics of the attractions (such as whether the attractions are outdoor or indoor). For example, the expected or historical waiting time value can be the expected waiting time of the attractions divided by the total waiting time of all attractions (related to the expected waiting time). The expected waiting time of the attractions can be provided by the waiting time history data 22. In one embodiment, if the waiting time value is less than the expected waiting time value, the waiting time recommendation logic can notify the guest's mobile device 24 that the waiting time of the attractions is shorter than expected. On the other hand, the waiting time value is greater than the expected waiting time value, and the waiting time recommendation logic can notify the guest's mobile device 24 that the waiting time is longer than expected. If the waiting time value is not less than or greater than the expected waiting time value, the waiting time recommendation logic can determine that the waiting time is as expected.
[0021] In some embodiments, the waiting time recommendation logic can use a threshold value (e.g., a ratio, percentage, or time period) to compare the waiting time value with the expected waiting time value. As an example, in the context of a total historical waiting time of 600 minutes for all attractions, the expected or historical waiting time for the attraction can be 60 minutes. Therefore, the expected or historical waiting time value can be 60 / 600 or 10%. If a 5% deviation is used to set the short waiting time threshold, the short waiting time threshold can be defined as 5% (i.e., 10%-5%). Therefore, if the waiting time value is less than 5%, the waiting time recommendation logic can send a notification to the guest's mobile device 24 that the waiting time is shorter than expected. The long waiting time threshold can be similarly defined and applied. The deviation for the short waiting time threshold and the long waiting time threshold can be any suitable deviation within the range of 1-50%. In addition, in some embodiments, the threshold can be customizable (e.g., by the developer, theme park, or guest). In some embodiments, the waiting time recommendation logic can compare the waiting time value with the expected waiting time value without using a threshold. For example, the waiting time recommendation logic can determine all deviations of all waiting times from the expected waiting time of all attractions. The wait time recommendation logic may then display all wait times or a subset of wait times (eg, the top ten, top five, top three, or any suitable top number) that have the largest deviations from their corresponding expected wait times.
[0022] It should be understood that although the present disclosure uses values to determine waiting time recommendations, any suitable numerical representation of waiting time may be used, including the waiting time itself. For example, in some cases, the waiting time history data 22 may receive the existing waiting time for each attraction, and the existing waiting time for the attraction may be compared with the expected or historical waiting time (or a subset of the historical waiting time based on the context, e.g., only the historical weekend waiting time, only the historical Tuesday waiting time) to determine the waiting time recommendation. For the purposes of this example, if the expected waiting time for the attraction is 60 minutes and the short waiting time threshold is set using a threshold deviation of 10 minutes, the short waiting time threshold is 50 minutes (i.e., 60 minutes-10 minutes). Therefore, if the waiting time is less than 50 minutes, the waiting time recommendation logic may send a notification to the guest's mobile device 24 that the waiting time is shorter than expected. The long waiting time threshold may be similarly defined and applied.
[0023] The expected waiting time value can be determined and / or adjusted based on the historical waiting time data of the scenic spot and theme park and any suitable context information. In particular, the waiting time recommendation logic can obtain or receive context information based on, for example, the date or time corresponding to the time of the request waiting time recommendation. The context information may include date or time information (e.g., time of day, day of week, week of year or quarter), holiday or event date (e.g., public holidays such as Thanksgiving or Christmas, school holidays such as spring break, or religious holidays such as Easter), weather information (e.g., related to temperature, humidity, probability or amount of rainfall, probability of natural disasters, etc.), characteristics of the scenic spot (e.g., whether the scenic spot is outdoor or indoor), parades, performances, or other performances occurring nearby, the geographic location of the mobile device 24 or the proximity between the scenic spot and the mobile device 24, and / or any other suitable information that may affect the waiting time or delay the waiting time. In some embodiments, the controller 12 may be programmed to obtain suitable or requested context information. In alternative or additional embodiments, the context information may be received from a variety of sources, such as calendar software applications, weather software applications, and / or location determination software applications.
[0024] As an example of a waiting time recommendation logic using contextual information, the waiting time recommendation logic can determine the expected waiting time value for a date by averaging the historical expected waiting time values associated with a date in previous years. As another example, the waiting time recommendation logic can determine the expected waiting time value for a time by averaging the historical expected waiting time values for a time in the previous 30 days. As yet another example, the waiting time recommendation logic can determine the expected waiting time value for a time by averaging the historical expected waiting time values, which are obtained when weather conditions substantially match weather conditions at a time (e.g., when the temperature is approximately the same (such as within one to five degrees Fahrenheit), when the humidity is approximately the same, when the amount of rainfall is approximately the same, etc.). Therefore, the waiting time recommendation logic can consider or adjust the expected waiting time value based on the date, time, weather, scenic spot characteristics, or any other suitable factors that may lag the expected waiting time value. For example, if the wait time history data 22 corresponds to one or more attractions in a theme park being closed, the wait time history data 22 may be delayed (because the remaining attractions will have elevated wait time values since there will be no wait times associated with the closed attractions). In this case, the wait time recommendation logic may estimate the wait times for the closed attractions (e.g., based on the wait time history data 22) to compensate for the closed attractions. Alternatively, the wait time recommendation logic may not use the wait time history data 22 corresponding to the closed attractions (or existing attractions that are no longer in operation). Although the present disclosure discusses that the wait time recommendation logic can determine the expected wait time, it should be understood that any suitable logic (e.g., external to the wait time recommendation logic) can determine the expected wait time.
[0025] Once the wait time recommendation logic determines that the wait time is shorter than expected, longer than expected, or as expected, the wait time recommendation logic may send a corresponding indication or notification to the guest's mobile device 24 via the communication network 28. The communication network 28 may be wired and / or wireless and enables the wait time recommendation logic to communicate with and / or send indications or notifications to the guest's mobile device 24 via any suitable communication protocol. For example, the communication network 28 may include a wireless network such as a mobile network, WiFi, LAN, WAN, the Internet, and / or the like.
[0026] The mobile device 24 may store and execute a wait time recommendation software application 30 that enables the mobile device 24 to display wait times and wait time recommendations for attractions in the theme park. It should be understood that certain features of the system 10 may be shared or exchanged with each other in the case of duplication. For example, the wait time recommendation software application 30 may be stored in a memory (e.g., sharing certain features of the memory 16) and executed by a processor (e.g., sharing certain features of the processor 14) of the mobile device 24. The mobile device 24 may use a communication circuit 33 (e.g., sharing certain features of the communication circuit 17) to communicate with the controller 12 via the communication network 28.
[0027] In addition, the waiting time recommendation system 10 includes a plurality of attractions 34 under the control of the attraction information system 35 and communicating with the controller 12 via the communication network 28 using the communication circuit 36. The waiting time history data 22 can be updated using the waiting time data from each individual attraction 34, and is stored as the waiting time history data 22 and the input used by the controller 12 to obtain the existing waiting time of each attraction 34, and the input is then used to determine the collected or total existing waiting time of all attractions (e.g., by summing all the existing waiting times of the attractions 34). In some embodiments, the waiting time data can be manually determined. For example, an employee of a theme park can monitor the waiting time of the attractions of the theme park and input or send the waiting time to the attraction information system 35 and / or the controller 12.
[0028] The attraction information system 35 may include a memory (e.g., sharing certain features of the memory 16) and may be under the control of a processor (e.g., sharing certain features of the processor 14). The attraction may also include one or more sensors 38 that generate data for determining the existing waiting time of the individual attractions 34. In one embodiment, the sensor 38 may include a guest tracking sensor (e.g., a barcode or optical reader, an NFC reader) that reads identification information from the mobile device 24 at the entrance to the attraction line and when each guest enters the attraction itself and leaves the line. In one embodiment, the existing waiting time for each attraction 34 may be the average waiting time of the last N guests (e.g., the last 10 guests, the last 50 guests). In another embodiment, the sensor 38 may include a camera or image sensor that estimates the length of the line using image data of the line, and then estimates the existing waiting time based on the estimated line length.
[0029] The waiting time recommendation application 30 can receive waiting time recommendation information (such as an indication or notification of waiting time recommendation) from the waiting time recommendation logic, and display the waiting time recommendation based on the waiting time recommendation information. In some embodiments, the waiting time recommendation application 30 can be part of a larger software application, such as a software application for providing theme park information to theme park guests. The mobile device 24 can be any suitable electronic device that receives waiting time recommendations, including smart phones, wearable devices, laptops, tablets, etc. In some embodiments, the mobile device 24 can alternatively be any other suitable device that can display or transmit the corresponding waiting time, such as a sign inside the theme park, a sign at each attraction, a notice on a website associated with the theme park, or a notice on a notice platform via a chatbot.
[0030] In some embodiments, the waiting time recommendation application 30 can provide and / or display waiting time recommendations based on user context information provided via the user interface or user input device 32 of the mobile device 24. The user context information 32 may include any suitable information that can facilitate the provision of a more relevant display of waiting time recommendations. In particular, the user context information 32 may include user preferences of the guest or their group (e.g., related to which attractions the guest or the guest's group expects or does not expect to attend, or related to attractions that the guest or the guest's group is eligible or ineligible to attend based on the age or height of the members of the guest or the guest's group), location information of the mobile device 24 (e.g., as provided by location determination logic (such as global positioning system (GPS) hardware and / or software), etc. For example, the waiting time recommendation application 30 may evaluate waiting times or display / push waiting times only for those attractions that meet the user preferences and / or are within a threshold distance from the location of the mobile device 24. In one embodiment, the guest can set or configure what user context information 32 is provided and / or used to determine how to determine and / or display waiting time recommendations. Then, the guest can use notifications of waiting times that are shorter or longer than expected as a factor when deciding whether to wait in the queue of the attraction.
[0031] Figure 24 is a flow chart of a process 40 for generating wait time recommendations for attractions in a theme park based on the total wait time of multiple attractions in the theme park according to an embodiment of the present disclosure. In particular, the waiting time recommendation system 10 can implement the process 40 to generate waiting time recommendations. The process 40 can be in the form of one or more software applications that include instructions executed by at least one suitable processor such as the processor 14 of the waiting time recommendation system 10 via waiting time recommendation logic. According to the present disclosure, the illustrated process 40 is provided only as an example, and in other embodiments, certain illustrated steps of the process 40 may be performed in other orders, skipped, repeated, or not in the order in which they are performed. Figure 3 Shown in.
[0032] As shown, in process frame 42, processor 14 receives the total waiting time of multiple attractions of theme park.Multiple attractions of theme park can include all attractions of theme park or all attractions of theme park in operation.Total waiting time can be the average value of the total waiting time of all attractions in any suitable time period (e.g., one day, one week, one quarter or one year).In particular, total waiting time can be provided by waiting time history data 22.In some embodiments, total waiting time can be the average value of the total waiting time of the time period corresponding to the current time or day of request waiting time recommendation.For example, total waiting time can be the average value of the total waiting time corresponding to the same date (for many years), the same time (for multiple dates), similar weather (for multiple dates) and / or other similar characteristics.
[0033] In some embodiments, the processor 14 may consider or adjust the total waiting time based on the date, time, weather, characteristics of the attraction, or any other suitable factor that may lag the expected waiting time value. For example, if the waiting time history data 22 corresponds to one or more attractions in the theme park being closed, the waiting time history data 22 may be delayed (because the remaining attractions will have elevated waiting time values because there will be no waiting times associated with the closed attractions). In this case, the waiting time recommendation logic may (e.g., based on the waiting time history data 22) estimate the waiting time for the closed attractions to compensate for the closed attractions. Alternatively, the waiting time recommendation logic may not use the waiting time history data 22 corresponding to the closed attractions (or existing attractions that are no longer in operation).
[0034] In process block 44, processor 14 receives a wait time for the attraction. For example, the wait time may be provided by a timer or counter of attraction 34, or may be manually entered.
[0035] In process block 46, processor 14 determines a waiting time value for an attraction based on the total waiting time for all attractions in the theme park and the waiting time for the attraction. The waiting time value may represent a ratio of the waiting time for the attraction to the total waiting time for all attractions in the theme park. In particular, the waiting time recommendation logic may determine the waiting time value by dividing the waiting time for the attraction by the total waiting time for all attractions. The waiting time value may be expressed as a fraction, a decimal, or a percentage.
[0036] In decision block 48, processor 14 determines whether the waiting time value is less than a short waiting time threshold. The short waiting time threshold may be based on the expected waiting time value of the attraction. The expected (e.g., typical or usual) waiting time value may be a ratio based on the following: historical waiting time data for attractions and theme parks, date or time information (such as time of day, day of the week, week of the year or quarter), weather, and / or characteristics of the attraction (such as whether the attraction is outdoor or indoor). For example, the expected waiting time value may be the expected waiting time of the attraction divided by the total waiting time of all attractions (related to the expected waiting time). The expected waiting time of the attraction may be provided by the waiting time history data 22. Then, the short waiting time threshold may be determined by subtracting the threshold time period from the expected waiting time. The threshold time period may be any suitable time period (e.g., from thirty seconds to thirty minutes, one minute, five minutes, or ten minutes) or may be a threshold percentage (e.g., a range of 0.1 to 10%, or 1 to 5%).
[0037] In process box 50, if processor 14 determines that the waiting time value is less than the short waiting time threshold, processor 14 sends a notification that the waiting time of the attraction is short. In particular, processor 14 can send a notification that the waiting time is shorter than expected to the waiting time recommendation software application 30 on the guest's mobile device 24. In one embodiment, processor 14 ranks all attraction waiting times based on a comparison with the expected waiting time. For example, the ranking can identify a subset of attractions that are the best values relative to their expected or historical waiting time values. The waiting time recommendation system 10 can push a subset of the best value attractions to the guest mobile device 24 via a notification. The ranking can be based on the total minutes saved in one embodiment. For example, if the attraction is typically 45 minutes waiting on weekends, but the existing waiting time is 35 minutes, the attraction can be ranked higher than an attraction with a lower absolute waiting time (e.g., 15 minutes) that is 5 minutes lower than normal.
[0038] In decision block 52, if the processor 14 determines that the wait time value is not less than the short wait time value threshold, the processor 14 determines whether the wait time value is greater than the long wait time value threshold. The long wait time threshold may be determined by adding a threshold time period to the expected wait time. It should be noted that the threshold time period subtracted from the expected wait time to determine the short wait time threshold may or may not be equal to the threshold time period added to the expected wait time to determine the long wait time threshold.
[0039] In process block 54, if the processor 14 determines that the wait time value is greater than the long wait time threshold, the processor 14 sends a notification that the wait time for the attraction is long. In particular, the processor 14 may send a notification to the wait time recommendation software application 30 on the guest's mobile device 24 that the wait time is longer than expected. In some embodiments, if the processor 14 determines that the wait time value is not less than the short wait time threshold (from decision block 48) and not greater than the long wait time value threshold, the processor 14 may send a notification to the wait time recommendation software application 30 on the guest's mobile device 24 that the wait time is as expected. The processor 14 may provide multiple recommendations corresponding to multiple attractions. In one embodiment, the processor 14 may list the multiple recommendations in a ranked order so as to prioritize the queues with the shortest wait time or the greatest wait time savings when compared to the expected wait time. If the wait time value is neither less than the short wait time threshold nor greater than the long wait time threshold, the processor 14 may not provide any recommendations (thereby indicating that the guests of the theme park are evenly distributed between the attractions).
[0040] In some embodiments, the processor 14 may compare the wait time value to the expected wait time value without using a threshold value. For example, the processor 14 may determine all deviations of all wait times from the expected wait times of all attractions. The wait time recommendation logic may then display all wait times or a subset of wait times (e.g., the first ten, the first five, the first three, or any suitable number of the first few) that have the largest deviations from their corresponding expected wait times. In this manner, the processor 14 may implement the process 40 to generate wait time recommendations for attractions in a theme park based on the total wait times for multiple attractions in the theme park.
[0041] In some embodiments, in addition to or as an alternative to the total wait time for multiple attractions at a theme park, wait time recommendations can be generated based on other factors. For example, Figure 3is a flow chart of a process 60 for generating wait time recommendations for attractions in a theme park based on park attendance according to an embodiment of the present disclosure. In particular, the wait time recommendation system 10 may implement the process 60 to generate wait time recommendations. The process 60 may be in the form of one or more software applications that include instructions executed by at least one suitable processor, such as the processor 14 of the wait time recommendation system 10, via wait time recommendation logic. According to the present disclosure, the illustrated process 40 is provided only as an example, and in other embodiments, certain illustrated steps of the process 40 may be performed in other orders, skipped, repeated, or not in the process 40. Figure 3 Shown in.
[0042] As illustrated, in process block 61, processor 14 receives current park attendance for a theme park. In process block 62, processor 14 receives one or more historical wait times for an attraction for a time when the corresponding historical park attendance was approximately the current park attendance. The one or more historical wait times may be provided by wait time history data 22. In some embodiments, processor 14 may include or exclude historical wait times associated with delayed historical park attendance (e.g., due to attraction closures, weather, holiday or event dates, parades, shows, or other performances occurring nearby, or any other suitable information that may affect wait times or cause wait times to lag). In one embodiment, processor 14 may adjust historical wait times associated with delayed historical park attendance. If the historical park attendance is within a threshold attendance of the current park attendance, processor 14 may determine that the historical park attendance is approximately the current park attendance. The threshold number of people can be any suitable number of people (e.g., a range of 1 to 10,000 people, 1 to 1,000 people, or 1 to 100 people) or any suitable percentage of current park attendance (e.g., a range of 0.1 to 10% or 1 to 5%).
[0043] In process block 63, processor 14 determines an average historical waiting time for the attraction based on one or more historical waiting times. That is, processor 14 may average one or more historical waiting times for the attraction to determine the average historical waiting time. In additional or alternative embodiments, another representative value may be used, such as a median, a modulus, a minimum, or a maximum.
[0044] In process block 64, processor 14 determines a short wait time threshold and a long wait time threshold based on the average historical wait time. The short wait time threshold may be determined by subtracting a threshold time period from the average historical wait time, while the long wait time threshold may be determined by adding the threshold time period to the average historical wait time. The threshold time period may be any suitable time period (e.g., from thirty seconds to thirty minutes, one minute, five minutes, or ten minutes) or may be a threshold percentage (e.g., a range of 0.1 to 10%, or 1 to 5%).
[0045] In process block 65, processor 14 receives a wait time for the attraction. For example, the wait time may be provided by a timer or counter of attraction 34, or may be manually entered.
[0046] In decision block 66, processor 14 determines whether the waiting time is less than the short waiting time threshold. If so, processor 14 sends a notification that the waiting time for the attraction is short in process block 67. In particular, processor 14 may send a notification to the waiting time recommendation software application 30 on the guest's mobile device 24 that the waiting time is shorter than expected.
[0047] If the processor 14 determines that the wait time is not less than the short wait time threshold, then in decision block 68, the processor 14 determines whether the wait time is greater than the long wait time threshold. If so, then in process block 69, the processor 14 sends a notification that the wait time for the attraction is long. In particular, the processor 14 can send a notification to the wait time recommendation software application 30 on the guest's mobile device 24 that the wait time is longer than expected.
[0048] In some embodiments, if the processor 14 determines that the wait time value is not less than the short wait time threshold (from decision block 66) and is not greater than the long wait time value threshold, the processor 14 may send a notification that the wait time is as expected to the wait time recommendation software application 30 on the customer's mobile device 24. In this manner, the processor 14 may implement the process 60 to generate wait time recommendations for attractions at a theme park based on park attendance.
[0049] Considering the foregoing, Figure 4is an example screenshot of a theme park software application 70 for providing theme park information to theme park guests according to an embodiment of the present disclosure. In particular, the theme park software application 70 can be stored and executed on the guest's mobile device 24. As illustrated, when, for example, the guest selects a menu button 74, the theme park software application 70 can display a menu 72. The menu 72 can display a variety of options, including: a display all wait times page 76 (entitled "All Wait Times"), which displays all wait times for all attractions in the theme park; and a display recommended wait times 78 (entitled "Recommended Wait Times"), which displays recommended wait times for attractions in the theme park.
[0050] Although all wait times page 76 may display all wait times for all attractions in a theme park, in some embodiments, page 76 may also display recommended wait times. For example, Figure 5 A graphical notification having a shorter waiting time than usual according to an embodiment of the present disclosure Figure 4 76 of the theme park software application 70. In some embodiments, the wait time recommendation software application 30 may provide information displayed on the all wait time page 76. For example, the wait time recommendation software application 30 may be part of the theme park software application 70. The all wait time page 76 displays the wait times for the lines of attractions at the theme park. As illustrated, line A 90 has a wait time 92 of 15 minutes, line B 94 has a wait time 96 of 50 minutes, and line C 98 has a wait time 100 of 25 minutes. In addition, the all wait time page 76 may provide a graphical indication 102 to notify guests that the lines have a shorter or longer wait time than the usual wait time. For example, the all wait time page 76 displays a graphical indication 102 for both line A 90 and line C 98 to indicate that these lines have a shorter wait time than usual. In some embodiments, the all wait time page 76 may also include an indication to notify guests that the lines have a longer wait time than usual. It should be noted that the graphical notification may be provided in any suitable format, such as clip art, emoticons, icons, etc.
[0051] In some embodiments, all waiting time pages 76 may include an option to display preferred waiting times, or the theme park software application 70 may include a preferred waiting time page that displays waiting times for attractions in the theme park based on the preferences of the guest. For example, the theme park software application 70 may receive the preferences of the guest for certain attractions (e.g., as part of the user context information 32). The theme park software application 70 may then instruct the waiting time recommendation system 10 to evaluate only the waiting times for rides indicated by the guest as preferred, or to display only the waiting times for rides indicated by the guest as preferred. As another example, the theme park software application 70 may receive the location and / or distance of the mobile device 24 from the attraction (e.g., as part of the user context information 32), and then instruct the waiting time recommendation system 10 to evaluate only the waiting times for rides within a threshold distance from the mobile device 24, or to display only the waiting times for rides within a threshold distance from the mobile device 24. In some embodiments, the theme park software application 70 can instruct the waiting time recommendation system 10 to weight multiple factors, including waiting time, the difference between the waiting time in the queue and the expected waiting time of the queue, the guest's preferences and / or the location of the mobile device 24, to determine which waiting times are to be displayed as preferred waiting times. Similarly, the all waiting time page 76 can include any suitable options to sort or filter the waiting times, such as by waiting time, by the difference between the waiting time in the queue and the expected waiting time of the queue, by the ratio of the difference between the waiting time in the queue and the expected waiting time of the queue to the expected waiting time, etc.
[0052] like Figure 5 As shown in FIG. 1 , the graphical indication 102 has the form of an icon or a graphical image. In alternative or additional embodiments, the indication may have the form of text. For example, Figure 6 A text-based indication or marking with shorter than usual waiting time according to an embodiment of the present disclosure Figure 4 Another example screenshot of the all wait times page 76 of the theme park software application 70 of FIG. In particular, Figure 6 A text-based indication or label 110 is illustrated (eg, "Recommended!"). Figure 5 and 6 The indication is displayed in the form of an icon and text, respectively, but it should be understood that it is contemplated that the indication 102 can be displayed in any suitable format. For example, the text-based mark 110 can have a different font style (e.g., bold, italic, or uppercase) than other text on all waiting time pages 76 and / or be displayed differently (e.g., differently colored or using a flashing effect) than other text on all waiting time pages 76 to draw attention to the mark 110.
[0053] Additionally, as the wait time for a line or attraction changes status (e.g., from an expected wait to a shorter wait time than expected), the theme park software application 70 and / or the wait time recommendation software application 30 may provide a larger or more noticeable notification (e.g., a push notification) to draw the guest's attention to the change in status. For example, Figure 7 According to an embodiment of the present disclosure, when the waiting time of the queue changes to a shorter waiting time than usual, Figure 4 . As illustrated, line A 90 transitions from an expected wait time to a shorter wait time than usual. Therefore, a notification prompt 120 is displayed to communicate this transition to the guest. In particular, the notification prompt 120 may be “pushed” or initiated by the wait time recommendation system 10 to be displayed on the mobile device 24. The notification prompt 120 also enables the guest to indicate via a “Go” button 122 that they will be in line A 90, or via a “Cancel” button 124 that they will not be in line A 90. In this manner, the theme park software application 70 and / or the wait time recommendation software application 30 may provide wait time recommendations to guests.
[0054] In some embodiments, wait time recommendations may be provided via a chat or notification interface (e.g., stored and executed on mobile device 24). Figure 8 is an example screenshot of a chat interface 130 that may provide wait time recommendations according to an embodiment of the present disclosure. The chat interface 130 may be provided by any suitable chat or notification platform executed on the mobile device 24, such as a short message service, a notification software application, an instant notification software application, a component of the wait time recommendation software application 30, or a component of the theme park software application 70. The chat interface 130 may be communicatively connected to a robot (e.g., a chatbot) or other suitable software application or artificial intelligence that engages in a conversation with the guest via text (or auditory) communications operated by, for example, the processor 14 and provided by the wait time recommendation logic.
[0055] The chat interface 130 may provide wait time recommendations via the wait time recommendation system 10 in response to a request made by the guest. For example, the guest may send a message 132 requesting the "best" team (e.g., "Which team is the best right now?"). The chatbot may query the wait time recommendation system 10 for the team with the shortest wait time, the team with the largest difference between the (current) wait time in the team and the expected wait time of the team, or the team with the largest ratio of the wait time in the team to the expected wait time of the team, and display a response 134 indicating the result.
[0056] In some embodiments, the chatbot may incorporate the guest's preferences for certain attractions (e.g., as part of the user context information 32) into its response 134. For example, the chatbot may instruct the waiting time recommendation system 10 to evaluate only the waiting times of rides indicated by the guest as preferred, or to respond only to the waiting times of rides indicated by the guest as preferred. As another example, the chatbot may incorporate the location of the mobile device 24 and / or the distance from the attraction (e.g., as part of the user context information 32) into its response 134. In particular, the chatbot may instruct the waiting time recommendation system 10 to evaluate only the waiting times of rides within a threshold distance from the mobile device 24, or to respond only to the waiting times of rides within a threshold distance from the mobile device 24. In some embodiments, the chatbot may instruct the waiting time recommendation system 10 to weight multiple factors, including the waiting time, the difference between the waiting time in the queue and the expected waiting time of the queue, the guest's preferences, and / or the location of the mobile device 24, to determine the "best" queue. As illustrated, the chatbot's response 134 indicates which line is "best," as well as the difference between the wait time in the line and the expected wait time for the line (e.g., "Currently, Line A at 25 minutes is best, 20 minutes shorter than usual.").
[0057] As another example, a guest may send a message 136 requesting the wait times for all teams (e.g., "What are the wait times for all teams?"). The chatbot may query the waiting time recommendation system 10 for the wait times for all teams at the theme park and an indication of whether any wait time is less than expected, and display a response 138 indicating the result. As illustrated, the chatbot's response 138 displays the wait times for all teams and the wait times for teams that are less than expected or "low wait" (e.g., "Team A: 25 minutes - low wait!"; Team B: 40 minutes; Team C: 30 minutes; Team D: 15 minutes - low wait!").
[0058] The guest may also send a message 140 requesting a wait time for a particular line (e.g., "What was the wait time for line E?"). The chatbot may query the wait time recommendation system 10 for the wait time for that line and an indication of whether the wait time was less than expected, greater than expected, or as expected, and display a response 142 indicating the result. As illustrated, the chatbot's response 142 displays the wait time for the requested line, as well as an indication that the wait time was greater than expected (e.g., "The wait time for line E is 55 minutes. That wait is 20 minutes longer than usual!"). Although Figure 8The illustration is in the form of a chat or notification interface, but it should be understood that the disclosed technology can be applied to any other suitable communication format associated with artificial intelligence or robots (e.g., chatbots), such as virtual assistants or smart speakers.
[0059] Guest service employees (e.g., at a theme park) may also use a software application or interface that enables guest service employees to view wait times and wait time recommendations. For example, Fig. 9 is an example screenshot of an employee dashboard 150 that may provide wait times and wait time recommendations according to an embodiment of the present disclosure. The employee dashboard 150 may be provided by any suitable platform, such as the wait time recommendation software application 30, the theme park software application 70, or a stand-alone employee dashboard software application, executing on any suitable electronic device, such as a computing device (e.g., a desktop computer, laptop, tablet, smartphone, or wearable device) of a theme park or guest services employee.
[0060] As illustrated, the employee dashboard 150 may display the wait times for lines at an attraction in an “all wait times” window 152. The employee dashboard 150 may also display wait time recommendations in a “recommended wait times” window 154. In this manner, the employee dashboard 150 may enable guest service employees to quickly and conveniently retrieve information related to wait times and / or the most efficient, convenient, and / or time-saving attractions to wait in line for. In fact, the employee dashboard 150 may enable guest service employees to contact guests, such as via a service desk or via a roaming employee, to recommend wait times for attractions, thereby providing guests with a personal touch and useful information. As further illustrated, the employee dashboard 150 may also display other convenient information that may be requested by a guest or facilitate service to a guest, such as weather updates 156, theme park ticket plan pricing details 158, emergency contact numbers 160, and news and other information 162.
[0061] While the disclosed embodiments illustrate recommendations for the same type of queue (e.g., regular ticket holder or standby queue), the present disclosure contemplates applying the disclosed technology to different and multiple types of queues, such as fast queues, season ticket holder queues, VIP queues, and / or disability access queues. In particular, wait time recommendations may be provided for these other types of queues and / or factors in the additional wait times based on these other types of queues.
[0062] The technology presented and claimed herein is cited and applied to material objects and specific examples of a practical nature that demonstrably improve the art and, therefore, are not abstract, intangible, or purely theoretical. In addition, if any claim appended to the end of this specification contains one or more elements designated as "means for [performing] ... [function]" or "steps for [performing] ... [function]," it is intended that such elements be interpreted in accordance with 35 U.S.C. 112(f). However, for any claim containing elements designated in any other manner, it is intended that such elements not be interpreted in accordance with 35 U.S.C. 112(f).
Claims
1. A method for generating a wait time recommendation, the method comprising: receiving, via a processor, park attendance for a theme park; receiving, via the processor, a plurality of historical wait times for a plurality of attractions within the theme park; receiving, via the processor, wait times for attractions among the plurality of attractions; determining, via the processor, a waiting time threshold for the attraction based on the plurality of historical waiting times: generating, via the processor, a wait time recommendation for the attraction based on the wait time and the wait time threshold; and A notification of the wait time recommendation is sent via the processor. 2 . The method of claim 1 , comprising determining, via the processor, an average historical wait time based on the plurality of historical wait times, and determining the wait time threshold based on the average historical wait time. 3 . The method of claim 1 , comprising determining, via the processor, a second latency threshold based on the plurality of historical latency times.
4. The method according to claim 3, comprising: Based on the wait time for the attraction being greater than the second wait time threshold, sending, via the processor, a second notification that the wait time for the attraction is longer than expected.
5. The method according to claim 1, comprising: Receiving, via the processor, a total waiting time for the plurality of attractions: determining, via the processor, a wait time ratio for the attraction based on the wait time for the attraction and the total wait time for the plurality of attractions; and determining, via the processor, a total historical waiting time for the plurality of attractions based on the plurality of historical waiting times, wherein: the waiting time threshold comprises a ratio based on the historical waiting time for the attraction and the total historical waiting time for the plurality of attractions; and The wait time recommendation for the attraction is generated based on the wait time ratio and the wait time threshold.
6. The method according to claim 1, comprising: receiving, via the processor and from a sensor, a location of an electronic device within the theme park: and A set of points of interest from among the plurality of points of interest within a threshold distance of the electronic device is determined, via the processor.
7. The method according to claim 6, comprising: receiving, via the processor, additional wait times corresponding to additional attractions in the set of attractions; determining, via the processor, an additional wait time ratio between the additional wait time for the additional attraction and an existing total wait time for the plurality of attractions: and A wait time recommendation is generated, via the processor, for the additional attraction based on comparing the wait time threshold and the additional wait time.
8. The method according to claim 7, comprising: Based on the wait time for the additional attraction being greater than a second wait time threshold, sending, via the processor, an additional notification that the wait time is longer than expected.
9. The method according to claim 7, wherein: Determining, via the processor, the additional wait time ratio includes dividing the additional wait time for the additional attraction by the plurality of historical wait times for the plurality of attractions.
10. A waiting time recommendation system, comprising: a sensor configured to detect a location of an electronic device within a theme park, the theme park including a plurality of attractions; processor; a memory storing instructions that, when executed by the processor, cause the processor to: determining a set of points of interest from among the plurality of points of interest within a threshold distance of the location of the electronic device; receiving a wait time corresponding to an attraction in the set of attractions; generating a waiting time recommendation for the attraction based on the waiting time and the total waiting time of the plurality of attractions; and A notification of the wait time recommendation is sent.
11. The waiting time recommendation system according to claim 10, wherein: The processor is configured to determine a wait time ratio between the wait times and the total wait time for the plurality of attractions, wherein the wait time recommendation is generated based on comparing the wait time ratio to a wait time threshold.
12. The waiting time recommendation system according to claim 11, wherein: The waiting time threshold is determined based on a relationship between the historical total waiting time of the plurality of attractions and the historical waiting time of the attraction.
13. The waiting time recommendation system according to claim 11, wherein: The wait time threshold is a short wait time threshold, and wherein, based on the wait time ratio being less than the short wait time threshold, the wait time recommendation is that the wait time is shorter than expected.
14. The waiting time recommendation system according to claim 11, wherein: The wait time threshold is a long wait time threshold, and wherein, based on the wait time ratio being greater than the long wait time threshold, the wait time recommendation is that the wait time is longer than expected.
15. The waiting time recommendation system according to claim 10, wherein: The processor is configured to remove a second wait time corresponding to a closed attraction from the total wait time for the plurality of attractions.
16. A tangible, non-transitory computer-readable medium comprising instructions for generating wait time recommendations for an attraction in a plurality of attractions of a theme park, the instructions, when executed by a processor, causing the processor to: Receiving a location of an electronic device within the theme park from a sensor: determining a group of points of interest from among the plurality of points of interest within a threshold distance of the location of the electronic device; receiving total waiting times for the plurality of attractions in the theme park; receiving a waiting time corresponding to the attraction among the plurality of attractions: and Based on the waiting time for the attraction being greater than a waiting time threshold, a notification is sent that the waiting time for the attraction is longer than expected.
17. The tangible, non-transitory computer-readable medium of claim 16, wherein the instructions, when executed by the processor, cause the processor to: determining a waiting time ratio of the attraction among the plurality of attractions, wherein the waiting time ratio is based on a total waiting time of the plurality of attractions and the waiting time of the attraction: and A wait time recommendation is generated based on the wait time ratio and the wait time threshold.
18. The tangible, non-transitory computer-readable medium of claim 16, wherein the instructions, when executed by the processor, cause the processor to: After a period of time, receiving an updated wait time corresponding to the attraction in the plurality of attractions; and based on the wait time for the attraction being less than the wait time threshold, sending an additional notification that the wait time for the attraction is shorter than expected.
19. The tangible, non-transitory computer-readable medium of claim 16, wherein: The waiting time threshold is determined based on date, time or weather.
20. The tangible, non-transitory computer readable medium of claim 16, wherein the wait time threshold is determined based on a total historical wait time for the plurality of attractions when historical park attendance is correlated with park attendance for the theme park.
