Systems and methods for adjusting elevator load settings

Abstract

To provide elevator control systems that dynamically adjust load capacity settings of elevators.SOLUTION: A method of adjusting a load setting of an elevator car includes receiving one or more load measurements associated with the elevator car and determining a maximum load of the elevator car from the one or more load measurements. The method further includes generating a modified load setting for the elevator car based on the maximum load and replacing the load setting of the elevator car with the modified load setting.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] Aspects of the present disclosure relate generally to systems and methods for controlling elevator traffic, and more particularly to an example elevator control system that dynamically adjusts elevator load capacity settings based on a detected maximum load. [Background technology]

[0002] Elevator systems typically allow preset load capacity settings for elevator cars, which define the maximum load each elevator car can accept. The load capacity may be preset by the elevator system manufacturer or by the elevator system user. In such systems, elevator cars whose current load exceeds the set load capacity may be excluded from receiving calls from passengers seeking rides. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] U.S. Patent No. 5,407,030 [Patent Document 2] U.S. Patent No. 5,345,042 [Patent Document 3] U.S. Patent No. 4,939,679 [Patent Document 4] European Patent No. 1,478,591 Summary of the Invention [Problem to be solved by the invention]

[0004] However, even if the current load of an elevator car is below its load capacity, passengers may avoid entering that elevator car for various reasons. For example, passengers may prefer to enter an elevator car that has a certain number of occupants that is less than the elevator car's load capacity. As a result, passengers may not enter an elevator car that has a current load below its set load capacity even if it is dispatched to the passenger's location, resulting in reduced traffic flow and longer wait times as passengers request the dispatch of another elevator car. [Means for solving the problem]

[0005] By providing a system that can dynamically adjust load capacity settings, elevator cars can be dispatched that are more likely to accept passengers, thereby increasing traffic flow and reducing wait times for passengers seeking rides.

[0006] According to one example, a method for adjusting a load setting for an elevator car includes receiving one or more load measurements associated with the elevator car and determining a maximum load for the elevator car from the one or more load measurements, the method further including generating a modified load setting for the elevator car based on the maximum load, and replacing the load setting for the elevator car with the modified load setting.

[0007] According to another example, a method for operating a plurality of elevator cars includes obtaining load measurements for each of the plurality of elevator cars during a prescribed time period and determining a maximum load for each of the plurality of elevator cars from the load measurements. The method further includes generating a modified load setting for each of the plurality of elevator cars, the modified load setting being based on the maximum load for each of the plurality of elevator cars, respectively, and enabling the modified load setting for each of the plurality of elevator cars in place of an original load setting during the prescribed time period. The modified load setting defines an adjusted capacity for each of the plurality of elevator cars relative to the load setting.

[0008] According to a further example, a method of allocating an elevator car includes determining an occupancy at each of a plurality of locations and determining a number of people from the elevator upon arrival at each of the plurality of locations. determining a first load measurement of the elevator car upon departure from each of the plurality of locations, determining a second load measurement of the elevator car upon departure from each of the plurality of locations, and determining a difference between the first load measurement and the second load measurement. The method further includes, when the elevator car is in an inactive state, moving the elevator car to a first location having a total occupancy greater than a occupancy at each of the plurality of locations. [Brief explanation of the drawings]

[0009] [Figure 1] 1 illustrates a dispatch system including one or more devices communicating over a network. [Figure 2] 2 is a schematic diagram of a work environment including multiple elevator cars interacting with the dispatch system shown in FIG. 1; [Figure 3] FIG. 3 is a top view of the elevator car interior from the working environment shown in FIG. 2. [Figure 4] 2 is a schematic diagram of the hardware components of a computer device from the dispatch system shown in FIG. 1 . [Figure 5] 2 is a flow diagram of an exemplary method for adjusting load settings for an elevator car with the dispatch system shown in FIG. 1 . [Figure 6] 2 is a flow diagram of an exemplary method for distributing inactive elevator cars with the dispatch system shown in FIG. 1 . DETAILED DESCRIPTION OF THE INVENTION

[0010] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various exemplary embodiments and, together with the description, serve to explain the principles of the disclosure. Aspects of the present disclosure may be implemented in conjunction with the embodiments illustrated in the accompanying drawings. These drawings illustrate different aspects of the present disclosure, and where appropriate, reference numerals indicating similar structures, components, materials, and / or elements in different figures are similarly numbered. It is understood that various combinations of structures, components, and / or elements other than those specifically shown are contemplated and are within the scope of the present disclosure. There are many aspects and embodiments described herein. Those skilled in the art will readily recognize that features of a particular aspect or embodiment may be used in combination with any or all features of the other aspects or embodiments described in this disclosure.

[0011] The dispatch system of the present disclosure may be in the form of a variety of embodiments, some of which are illustrated in the figures and further described below. Both the foregoing general description and the following detailed description are exemplary and explanatory and are not limiting of the features as claimed. As used herein, the terms "comprises," "includes," and other variations thereof are not intended to be exclusive, such that a process, method, article, or apparatus including a list of elements is inclusive of only those elements, but may include other elements not expressly listed or inherent in such process, method, article, or apparatus. Additionally, the term "exemplary" is used herein to mean "example" rather than "ideal." Note that all numerical values ​​disclosed or claimed herein (including all disclosed values, limits, and ranges) may have a + / -10% variation from the disclosed numerical value (unless a different variation is specified). Furthermore, in the claims, values, limits, and / or ranges mean + / -10% of the value, limit, and / or range.

[0012] FIG. 1 illustrates an exemplary dispatch system 100, which may include a navigation controller 105, a paging device 110, an input device 120, a sensor device 125, and a dispatch controller 130. One or more devices of dispatch system 100 may communicate with each other in any configuration via network 115. For example, devices of dispatch system 100 may be communicatively connected to each other via wired or wireless connections, etc. In some embodiments, network 115 may be a wide area network (“WAN”), a local area network (“LAN”), a personal area network (“PAN”), etc. Network 115 may also include the Internet, and information and / or data provided between devices of dispatch system 100 may occur online (e.g., from a location remote from other devices or networks connected to the Internet). In other embodiments, network 115 may utilize Bluetooth technology and / or radio frequencies.

[0013] The traffic controller 105 may be operably connected to the transport unit and may be configured to detect and transmit operational data of the transport unit to one or more devices of the dispatch system 100, such as the dispatch controller 130. For example, the traffic controller 105 may measure and record one or more parameters (e.g., operational data) of the transport unit, including, but not limited to, current location, direction of travel, speed of travel, door position, status (e.g., active, inactive, moving, parked, idle, etc.), etc. The traffic controller 105 may include a computing device having one or more hardware components (e.g., a processor, memory, sensors, communication modules, etc.) for generating, storing, and transmitting the operational data. As described in further detail herein, the traffic controller 105 may be operably connected to elevator cars located within a building, and the dispatch system 100 may include at least one traffic controller 105 for each elevator car.

[0014] Continuing with reference to FIG. 1 , the call device 110 may be located outside the transportation unit and may be configured to receive user input from one or more riders seeking access to the transportation unit. For example, the user input may indicate a call requesting transportation from the transportation unit. The call device 110 may be configured to transmit the call request to one or more devices of the dispatch system 100, such as, for example, the dispatch controller 130. The call device 110 may include a keypad, a touchscreen display, a microphone, buttons, switches, etc. The call device 110 may further be configured to receive user input from multiple locations indicating a current location (e.g., a first location) and / or a destination location (e.g., a second location) of the call request.

[0015] As described in further detail herein, call devices 110 may be located within a building, and dispatch system 100 may have at least one call device 100 for each floor of the building. Call devices 100 may be configured to transmit messages from one or more devices of dispatch system 100 (e.g., dispatch controller 130) that identify an elevator car designated to arrive at a floor of the building to respond to a call request. Messages may be communicated by call devices 100 via a variety of suitable manners, including, for example, text, voice, graphics, etc.

[0016] Input device 120 may be located inside a transport unit and configured to receive user input from one or more occupants of the transport unit. For example, the user input may indicate a command requesting redirection of the transport unit. Input device 120 may be configured to transmit commands to one or more devices of dispatch system 100, such as dispatch controller 130. Input device 120 may include a keypad, a touchscreen display, a microphone, buttons, switches, etc. As described in more detail herein, input device 120 may be located in an elevator car, and dispatch system 100 may include at least one input device 100 for each elevator car in a building. In other embodiments, input device 120 may be omitted entirely from dispatch system 100.

[0017] 1 , the sensor devices 125 may be located inside or outside the transport unit and may be configured to detect and transmit sensor data related to the transport unit to one or more associated devices of the dispatch system 100, such as the dispatch controller 130. For example, the sensor devices 125 may measure and record the current load of the transport unit, including, but not limited to, weight measurements and voltage and current. The sensor devices 125 may include, for example, a crosshead deflection device, a rope installation device, a platform movement device, and a load weighing device such as a load sensor or cell (e.g., a force transducer). As described in further detail herein, the sensor devices 125 may be connected to elevator cars located within a building, and the dispatch system 100 may include at least one sensor device 125 for each elevator car in the building.

[0018] The dispatch controller 130 may be located outside the transport unit and may be configured to receive data (e.g., operational data, call requests, redirect commands, sensor data, etc.) from one or more devices of the dispatch system 100. The dispatch controller 130 may be further configured to determine whether to dispatch at least one of the plurality of transport units to a location of a call request received from a ride seeker seeking a ride. The dispatch controller 130 may be further configured to determine a current load of the transport unit based on data received from one or more devices of the dispatch system 100. The dispatch controller 130 may include a computing device (see FIG. 4) operable to perform one or more processes (see FIG. 5) for dynamically adjusting a load setting of the transport unit and preventing the transport unit from receiving a call request when the current load exceeds the load setting. The dispatch controller 130 may also be operable to perform one or more processes (see FIG. 6) for moving an inactive transport unit to a location where the total occupancy is higher than the occupancy of other locations. As described in further detail herein, dispatch controller 130 may be operably connected to multiple elevator cars located within a building, and dispatch system 100 may include at least one dispatch controller 130 for each building.

[0019] Referring now to FIG. 2 , dispatch system 100 may be utilized in work environment 200, such as a building (e.g., a facility, a factory, a store, a school, a home, an office, and various other structures). In this example, the transportation unit may include one or more elevator cars within the building. It should be understood that work environment 200 is merely exemplary, and dispatch system 100 may be utilized in a variety of other suitable environments other than those shown and described herein without departing from the scope of this disclosure. For example, work environment 200 may include a mass transit system, where the transportation unit may include a bus, a train, a subway car, a metro car, a vehicle, etc. In this example, work environment 200 may include multiple floors, e.g., first floor 204A, second floor 204B, third floor 204C, and fourth floor 204D, defining multiple locations within a building. It should be understood that in other embodiments, the construction of work environment 200 may include additional and / or fewer floors.

[0020] Work environment 200 may further include one or more elevator shafts with at least one elevator car disposed within each elevator shaft. In this example, work environment 200 includes a first elevator shaft 202 with a first elevator car 210 and a second elevator shaft 212 with a second elevator car 220. Although not shown, work environment 200 may include additional (e.g., multiple) elevator shafts and / or elevator cars. Each elevator car 210, 220 may be connected to a pulley system 208 configured to move elevator car 210, 220 within elevator shafts 202, 212 relative to floors 204A-204D. It should be understood that pulley system 208 may include various mechanical and / or electrical mechanisms for moving elevator cars 210, 220 within elevator shafts 202, 212, including, but not limited to, motors, cables, counterweights, pulleys, etc.

[0021] 2, each elevator car 210, 220 may include at least one operation controller 105 operably connected to sheave system 208, for example, via a wireless and / or wired connection 209. The operation controller 105 is configured to measure operation data (e.g., status) from elevator car 210, 220 by detecting relative motion of sheave system 208. Each elevator car 210, 220 may further include at least one input device 120 disposed within the cabin of elevator car 210, 220 for accepting user input from one or more occupants 10 located within the cabin.

[0022] Each floor 204A-204D may include one or more call devices 110 and access doors 206 that provide access to the elevator cars 210, 220 when the elevator doors 207 of the elevator cars 210, 220 are located at the respective floors 204A-204D. The call devices 110 may be configured to receive user input from one or more ride seekers 20 located at one of the floors 204A-204D. For example, the call devices 110 may be configured to receive user input indicating a call requesting transportation via at least one of the elevator cars 210, 220. The call devices 110 may be configured to transmit a call request to the dispatch controller 130, which may include data indicating a current location within the work environment 200 from which the call request is originating. The call request may further include data indicating a destination location within the work environment 200 to which the ride seeker is seeking transportation.

[0023] 2 , each elevator car 210, 220 may further include at least one sensor device 125 disposed within the cabin. The sensor device 125 may be connected to the elevator car 210, 220 and configured to detect the load (e.g., weight) of the elevator car 210. In elevator cars 210, 220 that include one or more occupants 10 within the cabin of the elevator car 210, 220, the sensor device 125 may be operable to correlate the detected load measurement with the number of occupants 10 within the elevator car 210, 220. In some embodiments, the sensor device 125 may be disposed within the elevator car 210, 220 (e.g., within the cabin). In other embodiments, the sensor device 125 may be disposed external to the elevator car 210, 220 and connected to the sheave system 208. For example, the sensor device 125 may include one or more connections 211 connected to one or more components of the pulley system 208 (eg, a crosshead, a beam, a hitch, a rope, a platform, etc.).

[0024] 3, the sensor device 125 may be configured to measure the total load of the elevator car 210, 220, which includes anything in the cabin that occupies the volume of the elevator car 210, 220 (e.g., passengers 10, incidental objects 12, etc.). In some embodiments, the sensor device 125 may be configured to detect the total load of the elevator car 210, 220, which includes the weight of the elevator car 210, 220 and one or more components of the elevator car 210, 220 (e.g., rails 14, input devices 120, doors 207, etc.). In other embodiments, the sensor device 125 may detect the current load of the elevator car 210, 220, excluding anything in the cabin that does not occupy the volume of the elevator car 210, 220 (e.g., rails 14, input devices 120, doors 207, etc.). The sensor device 125 may detect one or more load measurements of the elevator cars 210, 220 and record such measurements as sensor data. As described further herein, the sensor device 125 may be configured to transmit the sensor data for each elevator car 210, 220 to the dispatch controller 130 over the network 115 to determine whether the elevator car 210, 220 is available to receive passengers 20 from one or more floors 204A-204D.

[0025] Referring now to FIG. 4 , dispatch controller 130 may include a computing device incorporating multiple hardware components that enable dispatch controller 130 to receive data (e.g., operational data, call requests, commands, sensor data, etc.), process information (e.g., current load measurements, load placement, etc.), and / or perform one or more processes (see FIG. 5 ). An exemplary hardware configuration of dispatch controller 130 may include at least one processor 132, at least one communication module 134, a user interface 136, and at least one memory 138. In some embodiments, dispatch controller 130 may include a computer, a mobile user device, a remote station, a server, cloud storage, etc. Although in the illustrated embodiment, dispatch controller 130 is shown and described herein as a device separate from other devices of dispatch system 100, in other embodiments, one or more aspects of dispatch controller 130 may be integrated with one or more other devices of dispatch system 100. In other words, the exemplary hardware configuration of the dispatch controller 130 shown and described herein may be integrated with one or more of the operation controller 105, the calling device 110, the input device 120, and / or the sensor device 125.

[0026] The processor 132 may include any computing device capable of executing machine-readable instructions, which may be stored on a non-transitory computer-readable medium, such as the memory 138. By way of example, the processor 132 may include a controller, an integrated circuit, a microchip, a computer, and / or any other computing unit operable to perform the calculations and logical operations necessary to execute a program. As described in detail herein, the processor 132 is configured to perform one or more operations according to instructions stored in the memory 138, such as the dispatch logic 140 and the zone logic 142. The communications module 134 may facilitate communication between the dispatch controller 130 and one or more other devices in the dispatch system 100, such as over the network 115. The user interface 136 may include one or more input and output devices, including one or more input ports and one or more output ports. The user interface 136 may include, for example, a keyboard, a mouse, a touchscreen, etc. as input ports. The user interface 136 may further include, for example, a monitor, a display, a printer, etc. as output ports. The user interface 136 may be configured to receive user input indicating various commands, including, but not limited to, commands to perform one or more operations (FIGS. 5-6), commands to define a prescribed time period, commands to apply automatic adjustments to load settings, etc. 4 , memory 138 may include various programmed algorithms and data that support the operation of dispatch system 100. Memory 138 may include any type of computer-readable medium suitable for storing data and algorithms, such as, for example, random access memory (RAM), read-only memory (ROM), flash memory, a hard drive, and / or any device capable of storing machine-readable instructions. Memory 138 may include one or more data sets, including, but not limited to, operations data received from operations controller 105, load settings 144 for each of the plurality of elevator cars 210, 220, sensor data 146 acquired by each sensor device 125, modified load settings 148 for each of the plurality of elevator cars 210, 220, zone load data 150, etc.

[0027] The load settings 144 may include data indicating a preset maximum load for each of the plurality of elevator cars 210, 220. That is, the load settings 144 may define the maximum weight that each elevator car 210, 220 can accept during use. It should be understood that the load settings 144 for each of the plurality of elevator cars 210, 220 may be the same or different from one another. The load settings 144 may be predefined, for example, by a user of the dispatch system 100 (e.g., via the user interface 136). In some embodiments, the load settings 144 may be changed by the user. The sensor data 146 may include real-time load measurements for each elevator car 210, 220 indicating the number of occupants 10 (and / or incidental objects 12) located within the cabin of the elevator car 210, 220. In some embodiments, the sensor data 146 stored in the memory 138 may include a maximum load measurement for each elevator car 210, 220 detected by the sensor device 125. As described in detail herein, the modified load settings 148 may include updated load settings (e.g., maximum load capacities) for each of the plurality of elevator cars 210, 220 based on data received from one or more devices (e.g., sensor devices 125) of the dispatch system 100. The dispatch controller 130 may be configured to dynamically generate the modified load settings 148 based on one or more load measurements received from the sensor devices 125 of the elevator cars 210, 220.

[0028] 4 , the modified load setting 148 may further include a predetermined period of time during which the modified load setting 148 may be applied by the dispatch controller 130. The dispatch controller 130 may be configured to replace the load setting 144 with the modified load setting 148 for the predetermined period of time. In some embodiments, the dispatch controller 130 may be configured to autonomously determine the predetermined period of time, while in other embodiments, a user of the dispatch system 100 may manually select the predetermined period of time (e.g., via the user interface 136).

[0029] The zone load data 150 may include load distribution measurements at each of a plurality of locations within the work environment 200 and may indicate the number of occupants 10 located on each of a plurality of floors 204A-204D. The dispatch controller 130 may be configured to calculate the zone load data 150, which may correspond to the load of items (e.g., occupants 10, incidental items 12, etc.) being transported between each of a plurality of floors 204A-204D by at least one of the plurality of elevator cars 210, 220. The dispatch controller 130 may further be configured to store the zone load data 150 in memory 138 and associate the load with the number of occupants (guests) located at a particular location (e.g., floor 204A-204D) within the work environment 200. For example, the dispatch controller 130 may receive the operation data received from the operations controller 105 and correlate it with the sensor data 146 received from the sensor device 125 to determine the zone load data 150.

[0030] In some embodiments, the dispatch controller 130 may be configured to periodically (e.g., hourly, daily, weekly, monthly, yearly, etc.) update the modified load settings 148 for each of the plurality of elevator cars 210, 220 based on receiving additional load measurements (e.g., sensor data 146) from the sensor devices 125. In further embodiments, the dispatch controller 130 may be further configured to periodically update the zone load data 150 upon determining that one or more elevator cars 210, 220 have moved to transport at least one occupant 10 between floors 204A-204D. That is, the dispatch controller 130 may continually modify the zone load data 150 to include current load distribution measurements at each floor 204A-204D based on determining the number of occupants 10 departing or arriving between each floor 204A-204D (e.g., as detected by the sensor devices 125).

[0031] Continuing to refer to FIG. 4 , memory 138 may include non-transitory computer-readable media storing machine-readable instructions, such as dispatch logic 140 and zone logic 142. In one example, dispatch logic 140 may include executable instructions that enable dispatch system 100 to determine the passenger capacity of each elevator car 210, 220 based on current load measurements (e.g., sensor data 146) for each elevator car 210, 220. As described in detail herein, dispatch system 100 may be configured to determine whether the current load (indicating the number of passengers present in the cabin) of each elevator car 210, 220 exceeds the maximum load (e.g., load setting 144, modified load setting 148) for each elevator car 210, 220. If the maximum load of at least one elevator car 210, 220 is exceeded, dispatch system 100 may disable that particular elevator car from responding to additional call requests from ride seekers 20 seeking transportation. That is, dispatch system 100 removes an elevator car from consideration when determining which of multiple elevator cars 210, 220 to dispatch a new call request to until the current load of the elevator car does not exceed the maximum load.

[0032] In another example, zone logic 142 may include executable instructions that enable dispatch system 100 to determine when one or more of elevator cars 210, 220 is inactive and at what location (e.g., a first location) to park the elevator car when inactive. The executable instructions of zone logic 142 may further enable dispatch system 100 to determine an amount of load to be transported by elevator cars 210, 220 to multiple locations (e.g., floors 204A-204D) and identify a first location that has a greater load distribution than the remaining multiple locations.

[0033] 5, an exemplary method 300 is shown for dynamically adjusting elevator car load settings using dispatch system 100 to prevent an elevator car from accepting calls when the current load exceeds the load setting. It should be understood that the steps shown and described herein, and the order in which they are presented, are merely exemplary, and that additional steps and / or fewer steps may be added and included in various configurations without departing from the scope of the present disclosure.

[0034] In step 302, dispatch system 100 may receive a call at a first location of multiple locations within work environment 200. The call may be initiated, for example, in response to ride seeker 20 activating call device 110 at a location (e.g., the first location). Call device 100 may transmit the call to dispatch controller 130 over network 115, and the call may include data indicating the first location from which the call originated (e.g., fourth floor 204D). The call may further include data indicating a destination within work environment 200 to which ride seeker 20 is traveling (e.g., second floor 204B), such as first floor 204A.

[0035] Dispatch controller 130 may retrieve operational data for each elevator car 210, 220 from the corresponding operations controller 105 in accordance with dispatch logic 140 to determine operational parameters for elevator cars 210, 220. For example, dispatch controller 130 may receive data including the current location, direction of travel, speed of travel, etc. of each elevator car 210, 220. Dispatch controller 130 may also retrieve load measurements (e.g., sensor data 146) for each elevator car 210, 220 from the corresponding sensor device 125 in step 304. Dispatch controller 130 may be configured to determine the current load of each elevator car 210, 220 based on the sensor data 146.

[0036] 5, in step 306, the dispatch controller 130 may compare the current load measurement of each elevator car 210, 220 with its respective load setting 144 to determine whether the current load of each elevator car 210, 220 exceeds its maximum load capacity (e.g., load setting 144). The load setting 144 may include a variety of suitable capacities, including, but not limited to, a range from approximately 1,000 pounds (approximately 454 kg) to approximately 3,000 pounds (approximately 1,361 kg). In this example, the load setting 144 of the first elevator car 210 may be approximately 1,500 pounds (approximately 680 kg), and the load setting 144 of the second elevator car 220 may be approximately 1,400 pounds (approximately 635 kg). Dispatch controller 130 may be configured to analyze operational and sensor data 146 of multiple elevator cars 210, 220 to determine which elevator car 210, 220 to dispatch to the first location in step 308.

[0037] For example, in response to determining that the current load does not exceed the load setting 144, dispatch controller 130 may be configured to allow elevator car 210, 220 to receive the call. That is, dispatch controller 130 may determine that elevator car 210, 220 is available for consideration when determining which of multiple elevator cars 210, 220 to dispatch a call request to. In response to determining that the current load exceeds the load setting 144, dispatch controller 130 may be configured to prevent elevator car 210, 220 from receiving the call. In this case, dispatch controller 130 may determine that elevator car 210, 220 is unavailable such that elevator car 210, 220 is removed from consideration when determining which of multiple elevator cars 210, 220 to dispatch a call to.

[0038] In this example, first elevator car 210 may include a current load of approximately 200 pounds (approximately 91 kg), and second elevator car 212 may include a current load of approximately 0 pounds (0 kg). Furthermore, first elevator car 210 may be located farther from the first location (e.g., fourth floor 204D) than second elevator car 220 when the call is received in step 302. Therefore, second elevator car 220 may be determined to be the best elevator car of the multiple elevator cars 210, 220 to dispatch to fourth floor 204D. In some embodiments, dispatch controller 130 may be configured to communicate with call device 110 to send a message to ride seeker 20 at the first location. For example, dispatch controller 130 may communicate the identity of second elevator car 220 assigned to answer the call. In other embodiments, dispatch controller 130 may identify second elevator shaft 212 in which second elevator car 220 is to arrive. The message may be transmitted via paging device 110 in a variety of suitable formats, including, for example, via a display (e.g., in text format, image format, etc.), a speaker (e.g., in audio format), etc.

[0039] The dispatch controller 130 may be configured to store the sensor data 146 for each of the plurality of elevator cars 210, 220 in the memory 138. It should be understood that the dispatch controller 130 may continuously store the sensor data 146 for the elevator cars 210, 220 in response to repeatedly using the dispatch system 100 when receiving a call (step 302) and acquiring the sensor data 146 (step 304) to determine which of the plurality of elevator cars 210, 220 to dispatch to the call (step 308). Thus, the memory 138 may provide a database of load measurements for each of the plurality of elevator cars 210, 220. Furthermore, the dispatch controller 130 may determine when each load measurement is received by the dispatch controller 130 such that the sensor data 146 stored in the memory 138 is associated with a corresponding time interval. It should be understood that the sensor data 146 may be accessible via the user interface 136 for review by a user of the dispatch system 100.

[0040] In step 310, the dispatch controller 130 may be configured to determine a maximum load for each elevator car 210, 220 from one or more load measurements received from the sensor devices 125 during one or more defined time periods. The defined time periods may include various time intervals during which sensor data 146 is received from the elevator cars 210, 220. For example, but not limited to, the defined time period may be one or more hours per day, one or more days per week, one or more weeks per month, one or more months per year, etc. Thus, the dispatch controller 130 may determine a maximum load measurement for each elevator car 210, 220 during a particular defined time period. It should be understood that the memory 138 may include corresponding load measurements (e.g., sensor data 146) for multiple defined time periods.

[0041] In this example, the prescribed time period may include a two-hour period (e.g., 12:00 PM to 2:00 PM) during weekdays (e.g., Monday, Tuesday, Wednesday, Thursday, and Friday). In this case, the maximum load measurement for each elevator car 210, 220 may be determined from one or more load measurements received from elevator cars 210, 220 during the two-hour period on each weekday. In step 314, dispatch controller 130 may be configured to generate a modified load setting 148 for each elevator car 210, 220 based on the maximum load received by each elevator car 210, 220 during the prescribed time period. That is, modified load setting 148 may be equal to the largest load measurement received by each elevator car 210, 220 during the prescribed time period.

[0042] In some embodiments, the dispatch controller 130, in step 312, can receive user input (e.g., via the user interface 136) along with a command to determine a corrective load setting 148 for one or more of the plurality of elevator cars 210, 220. It should be understood that each corrective load setting 148 can be associated with a particular elevator car 210, 220 and a particular defined period during which the maximum load measurement from which the corrective load setting 148 is derived was received. It should be understood that the corrective load setting 148 can be applied for a defined period.

[0043] In this example, the maximum load measurement received by the first elevator car 210 during the specified period may be equal to approximately 1,100 pounds (approximately 499 kg), and the maximum load measurement received by the second elevator car 220 during the specified period may be equal to approximately 1,300 pounds (approximately 590 kg). Accordingly, the dispatch controller 130 may adjust the original load setting 144 of the first elevator car 210 from 1,500 pounds (approximately 680 kg) to 1,100 pounds (approximately 499 kg) (e.g., the modified load setting 148) during the two-hour weekday period. The dispatch controller 130 may also adjust the load setting 144 of the second elevator car 220 from 1,400 pounds (approximately 635 kg) to 1,300 pounds (approximately 590 kg) (e.g., the modified load setting 148) during the two-hour weekday period.

[0044] In other embodiments, dispatch controller 130 may be configured to automatically generate a modified load setting 148 for one or more of the plurality of elevator cars 210, 220. For example, dispatch controller 130 may automatically generate a modified load setting 148 based on determining that the maximum load measurement is less than the load setting 144 by a specified threshold value. The specified threshold value may be determined by dispatch controller 130 or may be predefined by a user of dispatch system 100. In some examples, the specified threshold value may range from approximately 5% to approximately 95%.

[0045] In this example, the default threshold may be set to approximately 20%. If the maximum load measurement of the first elevator car 210 (e.g., 1,100 pounds (approximately 499 kg)) is approximately 27% less than the load setting 144 of the first elevator car 210 (e.g., 1,500 pounds (approximately 680 kg)), the dispatch controller 130 may automatically generate a corrective load setting 148 for the first elevator car 210. Furthermore, if the maximum load measurement of the second elevator car 220 (e.g., 1,300 pounds (approximately 590 kg)) is approximately 7% less than the load setting 144 of the second elevator car 220 (e.g., 1,400 pounds (approximately 635 kg)), the dispatch controller 130 may forgo generating a corrective load setting 148 for the second elevator car 220. It should be appreciated that the dispatch controller 130 may be operable to account for small losses in load measurements due to a variety of causes, including sensor devices 146, hoistway problems, and the like.

[0046] 5, in step 314, dispatch controller 130 may be configured to apply a modified load setting 148 in place of load setting 144. It should be understood that modified load setting 148 may be an adjustment to load setting 144 and may be applied in place of original load setting 144 during a specified period of time. In this case, upon receiving a new call request (step 302) during a specified period of time (e.g., between 12:00 PM and 2:00 PM on a weekday), dispatch controller 130 may compare (step 306) the detected load measurements of elevator cars 210, 220 (step 304) with modified load setting 148 when determining whether elevator cars 210, 220 contain sufficient capacity to receive the call.

[0047] 6, an exemplary method 400 is shown for using dispatch system 100 to determine occupancy levels at multiple locations and allocate inactive elevator cars to locations with higher occupancy levels. It should be understood that the steps shown and described herein, and the order in which they are presented, are merely exemplary, and that additional steps and / or fewer steps may be added and included in various configurations without departing from the scope of the present disclosure. Furthermore, it should be understood that dispatch system 100 may perform exemplary method 400 in combination with one or more other processes, such as method 300 described above.

[0048] In step 402, dispatch system 100 may receive a call request at a location among multiple locations within work environment 200. The call may be initiated in response to a ride seeker 20 activating a call device 110 at that location (e.g., floors 204A-204D). Call device 100 may transmit the call to dispatch controller 130 over network 115. In this example, dispatch controller 130 may receive the call from a first location (e.g., second floor 204B) for transportation to a second location (e.g., first floor 204A). Dispatch controller 130 may receive operational data from the corresponding operation controller 105 of each elevator car 210, 220 in accordance with zone logic 142 to determine current operational parameters of the multiple elevator cars 210, 220.

[0049] Dispatch controller 130 may also receive sensor data 146 from the corresponding sensor device 125 of each elevator car 210, 220 to determine the current load of the elevator car 210, 220. Operations controller 105 and sensor device 125 may each transmit signals (via network 115) to dispatch controller 130 indicative of the operational and sensor data 146 of the corresponding elevator car 210, 220. In step 404, dispatch controller 130 may dispatch at least one elevator car of the plurality of elevator cars 210, 220 whose current load does not exceed the load setting 144 (and / or modified load setting 148), such as by following the steps of method 300 described above. In this example, the first elevator car 210 may be dispatched to the first location of the call (e.g., second floor 204B) to pick up ride seeker 20.

[0050] 6 , in steps 406-410, the dispatch controller 130 may be configured to determine the number of occupants at a plurality of locations. For example, in step 406, the dispatch controller 130 may be configured to determine a first load measurement (e.g., a load start value) of the first elevator car 210 upon arrival at the first location. In this case, the sensor device 125 may transmit a signal of the first load measurement to the dispatch controller 130 (e.g., sensor data 146) when the operational parameters received from the operations controller 105 indicate that the first elevator car 210 has arrived at the first location. In this example, the first load measurement may include a load indicative of a single occupant 10 located within the cabin of the first elevator car 210 upon arrival at the second floor 204B.

[0051] In step 408, the dispatch controller 130 may be configured to determine a second load measurement (e.g., a load end value) of the first elevator car 210 upon departing from the first location. In this case, the sensor device 125 may transmit a signal of the second load measurement (e.g., sensor data 146) to the dispatch controller 130 when the operational parameters received from the operations controller 105 indicate that the first elevator car 210 has departed the first location. In this example, the second load measurement may include a load indicative of two occupants 10 located within the cabin of the first elevator car 210 upon departing from the second floor 204B. In step 410, the dispatch controller 130 may be configured to determine a difference between the first load measurement (step 406) and the second load measurement (step 408) to calculate a resulting occupancy number at the first location. Thus, to determine the corresponding number of ride seekers 10 received (and / or transported) from the first location, the dispatch controller 130 may compare a first load measurement of the first elevator car 210 upon arrival at the second floor 204B with a second load measurement after departure from the second floor 204B.

[0052] In this example, the first elevator 210 may include a first load measurement of approximately 150 pounds (approximately 68 kg) to approximately 200 pounds (approximately 91 kg) when arriving at the first location and may include a first load measurement of approximately 300 pounds (approximately 136 kg) to approximately 400 pounds (approximately 181 kg) when departing from the first location to a destination location (e.g., the first floor 204A). Accordingly, the dispatch controller 130 may be configured to determine that approximately one ride seeker 20 entered the first elevator car 210 from the second floor 204B. It should be understood that the dispatch controller 130 may store a nominal passenger load in the memory 138. In this case, the dispatch controller 130 may correlate one or more load measurements with the number of passengers 10 via a conversion to a nominal passenger load. For example, the nominal passenger load may be in the range of approximately 100 pounds (approximately 45 kg) to approximately 300 pounds (approximately 136 kg), such as 150 pounds (approximately 68 kg). In other embodiments, one or more load measurements may be in a variety of other metric formats, including, for example, Volts Direct Current (VDC). In this case, dispatch controller 130 may correlate 1 volt to a defined load variable, such as, for example, weight ranging from about 100 pounds (about 45 kg) to about 300 pounds (about 136 kg). It should be understood that a variety of other suitable metrics for load measurements may be implemented by dispatch system 100 without departing from the scope of this disclosure.

[0053] Continuing with reference to FIG. 6 , in step 412, the dispatch controller 130 may determine whether the elevator car 210, 220 is in an inactive state. For example, the dispatch controller 130 may be configured to determine the operational status of the first elevator car 210, such as whether the first elevator car 210 is actively completing a call and / or whether it is assigned to answer additional calls. In this example, upon receiving a call from the second floor 204B (e.g., the first location), the first elevator car 210 is dispatched to the ride seeker 20's destination (e.g., the second location) to complete the call request. Thus, the dispatch controller 130 may determine in step 412 that the first elevator car 210 remains in an active state and return to step 404 to dispatch the first elevator car 210 to the second location. The dispatch controller 130 may be configured to repeat steps 406-410 to determine the occupancy level at the second location (e.g., the first floor 204A). Thus, dispatch controller 130 may measure a first load measurement of first elevator car 210 upon arrival at the second location (step 406) and a second load measurement upon departure from the second location (step 408). Dispatch controller 130 may determine the difference between the first and second load measurements (i.e., the load rate of change) (step 410) and calculate the resulting dwell time at the second location.

[0054] It should be appreciated that the dispatch controller 130 may calculate a load change rate for each of the plurality of locations when at least one of the plurality of elevator cars 210, 220 moves to the aforementioned locations to answer a call (e.g., pick up a ride seeker 20) and / or complete a call (e.g., drop off a passenger 10). The dispatch controller 130 may generate zone load data 150 for the first location and the second location, respectively, based on the occupancy count calculated in step 410. The zone load data 150 may include a measurement of the load carried by the first elevator car 210 between the first location (e.g., the second floor 204B) and the second location (e.g., the first floor 204A). The zone load data 150 may indicate the number of passengers 10 present at the aforementioned location after the first elevator car 210 departs from or arrives at the aforementioned location.

[0055] It should be appreciated that zone load data 150 may include a comprehensive measurement describing the cumulative load transported to and from the location by multiple elevator cars 210, 220. Accordingly, dispatch controller 130 may maintain a current occupancy determination for each of multiple locations. Dispatch controller 130 may be configured to store zone load data 150 in memory 138 and to continually update zone load data 150 for each of multiple floors 204A-204D during ongoing use of dispatch system 100.

[0056] 6 , in step 412, dispatch controller 130 may determine whether elevator cars 210, 220 are in an inactive state. Dispatch controller 130 may determine that first elevator car 210 is in an inactive state when no more calls are assigned to first elevator car 210 and / or when first elevator car 210 does not contain any additional destinations from existing calls. In response to determining that first elevator car 210 is in an inactive state in step 412, dispatch controller 130 may be configured to determine at least one location among the multiple locations that has the largest occupancy, in step 414. That is, dispatch controller 130 may be configured to compare zone load data 150 of the multiple locations to each other to evaluate the current occupancy at each location.

[0057] The dispatch controller 130 may determine that the fourth floor 204D has a greater occupancy than the remaining locations. In this example, as seen in FIG. 2, the first floor 204A may include two occupants 20 (e.g., just transported there by the first elevator car 210), the second floor 204B may include one remaining occupant 20, the third floor 204C may include two occupants, and the fourth floor 204D may include three occupants 20. Thus, the dispatch controller 130 may determine that the fourth floor 204D has a greater current occupancy than the remaining floors 204A-204C.

[0058] In step 416, dispatch controller 130 may be configured to move first elevator car 210 to fourth floor 204D. First elevator car 210 may be located at fourth floor 204D while first elevator car 210 remains in an inactive state. In other words, first elevator car 210 may be parked at fourth floor 204D until a call request from one of the plurality of floors 204A-204D is assigned to first elevator car 210 by dispatch controller 130 (e.g., via call device 110). It should be appreciated that if first elevator car 210 is maintained at fourth floor 204D and fourth floor 204D has a larger occupancy than the remaining plurality of floors 204A-204C, the minimum travel distance for first elevator car 210 to respond to future call requests may be minimized.

[0059] It should be appreciated that the dispatch controller 130 may be configured to periodically re-evaluate the current occupancy (e.g., zone load data 150) for each of the plurality of floors 204A-204D. Accordingly, the dispatch controller 130 may move one or more inactive elevator cars 210, 220 to a corrective position based on the updated zone load data 150. For example, in response to a first location (identified in step 414) no longer having a greater occupancy than the other plurality of locations, the dispatch controller 130 may be configured to relocate the inactive elevator car 210, 220 to a second location having the greatest occupancy.

[0060] In some embodiments, method 300 may include a further step of directing one or more inactive elevator cars 210, 220 to additional locations if the number of inactive elevator cars 210, 220 at the first location (e.g., fourth floor 204D) exceeds a specified threshold. In other embodiments, a user of dispatch system 100 may determine the number of locations at which multiple elevator cars 210, 220 are parked when in an inactive state. For example, dispatch controller 130 may receive user input (e.g., via user interface 136) indicating three locations at which to park inactive elevator cars 210, 220. In this case, dispatch controller 130 may determine which three of the multiple locations have the highest dwelling population compared to the remaining multiple locations and direct any inactive elevator cars 210, 220 to at least one of the three locations. In some embodiments, the dispatch controller 130 may be operable to generate a report (e.g., via the user interface 136) that includes information related to one or more of the load settings 144, the sensor data 146, the modified load settings 148, the in-zone load data 150, etc.

[0061] It should be understood that one or more processes of dispatch system 100 shown and described herein, such as exemplary methods 300 and 400, may be implemented in a variety of other operating environments. In one example, dispatch system 100 may be configured to apply one or more of exemplary methods 300 and 400 in a transportation system, such as a bus service, a train service, a subway service, a metro service, a car-sharing service, etc. With respect to exemplary method 300, dispatch system 100 may prevent a transportation unit (e.g., a bus, a train, a subway, a metro, a car, etc.) from accepting additional calls and / or passengers when its maximum load capacity is exceeded. In this case, the transportation unit may bypass the location (e.g., a stop) and / or prohibit the transportation unit from accepting additional loads (e.g., by not opening its doors). In some embodiments, dispatch system 100 may be configured to communicate with one or more remote stations to transmit information indicative of the current load.

[0062] For example, dispatch system 100 may send an alert to a remote station requesting assistance from additional transportation units at one or more locations when the current load of one or more current transportation units (e.g., buses, trains, subways, metro cars, etc.) exceeds the maximum load capacity. It should be appreciated that dispatch system 100 can facilitate traffic flow by determining the minimum number of transportation units needed at one or more locations or at one or more predetermined intervals to accommodate expected loads based on area load data for various locations. With respect to example method 400, dispatch system 100 may determine occupancy levels at multiple locations (e.g., bus stops, train stops, subway stops, metro cars, etc.) and allocate inactive transportation units (e.g., buses, trains, subways, metro cars, etc.) to locations with the highest occupancy levels.

[0063] All technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains, unless otherwise specified. As used herein, the singular includes the plural unless the context clearly dictates otherwise.

[0064] The above description is illustrative and not intended to be limiting. Those skilled in the art may make various modifications and / or variations without departing from the general scope of the present disclosure. For example, as noted above, the above-described embodiments (and / or aspects thereof) may be used in combination with each other. In addition, portions of the above-described embodiments may be omitted without departing from the scope of the present disclosure. Furthermore, modifications may be made to adapt a particular situation or material to the teachings of the various embodiments without departing from their scope. Many other embodiments will be apparent to those skilled in the art upon reviewing the above description.

Claims

1. 1. A method for adjusting a load setting of an elevator car, comprising: receiving one or more load measurements associated with the elevator car; determining a maximum load for the elevator car from the one or more load measurements; generating a revised load setting for the elevator car based on the maximum load; replacing the load setting of the elevator car with the modified load setting; A method comprising:

2. receiving a new load measurement associated with the elevator car; comparing the new load measurements to the revised load settings; The method of claim 1 further comprising:

3. Disabling the elevator car from receiving calls in response to the new load measurement exceeding the modified load setting; or enabling the elevator car to receive the call in response to the new load measurement not exceeding the modified load setting; The method of claim 2 further comprising:

4. the modified weight setting replaces the weight setting for a specified period of time; The method of claim 1.

5. and replacing the modified load setting with the load setting upon completion of the predetermined period. The method of claim 4.

6. receiving a new load measurement associated with the elevator car after completion of the predetermined period of time; comparing the new load measurement to the load setting; Disabling the elevator car from receiving calls in response to the new load measurement exceeding the load setting, or enabling the elevator car to receive the calls in response to the new load measurement not exceeding the load setting; The method of claim 5 further comprising:

7. the one or more load measurements are received during the specified time period such that the maximum load of the elevator car is associated with the specified time period. The method of claim 4.

8. receiving one or more load measurements during a plurality of defined time periods; determining a corresponding maximum load of the elevator car for each of the plurality of defined time periods; generating at least one modified load setting for each of the plurality of defined time periods based on the corresponding maximum load; The method of claim 7 further comprising:

9. The method includes, prior to generating the revised load settings for the elevator car: comparing the maximum load to the load setting; determining a difference between the maximum load and the load setting; determining that the difference exceeds a specified threshold, and generating the modified load setting in response to the difference exceeding the specified threshold; The method of claim 4, comprising:

10. the load setting defines a first maximum load capacity for the elevator car, and the modified load setting defines a second maximum load capacity for the elevator car that is less than the first maximum load capacity. The method of claim 1.

11. 1. A method of operating a plurality of elevator cars, comprising: obtaining load measurements for each of the plurality of elevator cars during a defined period of time; determining a maximum load for each of the plurality of elevator cars from the load measurements; generating a revised load setting for each of the plurality of elevator cars, each based on the maximum load for each of the plurality of elevator cars; enabling the modified load setting for each of the plurality of elevator cars in place of an original load setting during the specified period, the modified load setting defining an adjusted capacity of each of the plurality of elevator cars relative to the load setting; A method comprising:

12. receiving a call for at least one of the plurality of elevator cars during the defined period; measuring a new load on each of the plurality of elevator cars; comparing the new loads to the revised load settings for each of the plurality of elevator cars; The method of claim 11 further comprising:

13. determining that the load on a first elevator car of the plurality of elevator cars does not exceed the modified load setting; enabling the first elevator car to receive the call; dispatching the first elevator car for the call; The method of claim 12 further comprising:

14. determining that the load on a first elevator car of the plurality of elevator cars exceeds the modified load setting; Disabling the first elevator car from receiving the call; and preventing the first elevator car from dispatching for the call; and The method of claim 12 further comprising:

15. the load setting is replaced by the modified load setting for the specified period, the method comprising: and replacing the modified load setting with the load setting upon completion of the predetermined period. The method of claim 11.

16. determining an updated maximum load for each of the plurality of elevator cars in response to measuring one or more additional loads during the defined period; generating updated modified load settings for each of the plurality of elevator cars based on the respective updated maximum loads; The method of claim 11 further comprising:

17. 1. A method for positioning an elevator car, comprising: Determining a resident population at each of a plurality of locations; determining a first load measurement of the elevator car upon arrival at each of the plurality of locations; determining a second load measurement of the elevator car upon departure from each of the plurality of locations; determining a difference between the first load measurement and the second load measurement; When the elevator car is in an inactive state, moving the elevator car to a first location where a total number of people is greater than the number of people at each of the plurality of locations; A method comprising:

18. and parking the elevator car at the first position when the elevator car is in an inactive state.

18. The method of claim 17.

19. and updating the resident count at one or more of the plurality of locations in response to determining that the second elevator car has arrived at one or more of the plurality of locations, respectively.

18. The method of claim 17.

20. and further comprising, in response to determining that the total number of people at the second location is greater than the total number of people at each of the plurality of locations and the first location, moving the elevator car from the first location to the second location.

20. The method of claim 19.

Images