Dynamic Assignment Switching in the Dispatching of Elevator Cars

The invention relates in general to dispatching strategies for elevator systems of the hydraulic or traction type, and more specifically to a method for efficiently switching assignments of hall calls to a group of elevator cars.

Hall calls have been assigned to a group of elevator cars by a large number of different strategies. A common strategy estimates the time of arrival (ETA) of each elevator car for a specific hall call to be assigned. A count is computed for each car which represents the time estimated for the car in question to reach the call floor with the proper service direction to serve the hall call. The hall call assignment is given to the car having the lowest ETA count. The call assignments are continuously reevaluated. When a previously assigned hall call is being reconsidered, reassignment to another car having a lower ETA than the presently assigned car is only made when the lower ETA is lower by T seconds. The constant T is preselected at the time the elevator system is installed. Indiscriminate switching of hall call assignments can result in so called "no-call stops", with the value for T being selected to minimize such stops, as they are non-productive, time consuming, and energy wasting.

The present invention recognizes that it is difficult to select an optimum value for T. There are as many different optimum values as there are different buildings and traffic patterns, and a change in building usage can require a new value for T for efficient elevator service. Some values of T in certain buildings and traffic patterns can significantly adversely affect "average waiting time" (AWT), the industry standard for measuring the efficiency of an elevator system.

While it is not known when an elevator system is installed in a building what the optimum value for T will be, the desired AWT is known. The number of elevator cars, their acceleration rates, rated speed, door times, and operating strategies are all selected to provide a desired AWT for the contemplated building population and traffic patterns. When this desired AWT is achieved, it is known that the elevator system is operating efficiently.

The present invention dynamically changes the value of T until the desired AWT is achieved. When an elevator system is installed, an initial value for T is provided in computer memory, and the desired AWT is also provided in computer memory. The actual AWT is then calculated by accumulating call waiting time over a predetermined period of time accumulated during normal business days and business hours, and dividing the accumulated time by the number of calls which generated the waiting time. If the actual AWT is not equal to the desired waiting time, the initial value of T is incremented and the new value of T used in the call reassignment process. The actual AWT is again calculated the the selected time period and if it is still not equal to the desired AWT, but closer than the prior actual AWT, then T is incremented again. This testing and dynamic adjustment of T continues over the operating life of the elevator system, incrementing and decrementing T, as required to maintain the actual AWT as close as possible to the desired AWT. Thus, changes in building population and/or traffic patterns is automatically accommodated.

The invention will become more apparent by reading the following detailed description in conjunction with the drawings, which are shown by way of example only, wherein:

FIG. 1 is a diagrammatic representation of an elevator system which may utilize the dispatching methods of the invention;

FIG. 2 is a RAM map listing per-car status information;

FIG. 3 is a RAM map listing per-car floor enable information;

FIG. 4 is a RAM map of a hall call table;

FIG. 5 is a RAM map of a car table;

FIG. 6 is a RAM map of an assignment register;

FIG. 7 is a RAM map of a trip list;

FIG. 8 is a ROM map listing various time periods to be used by a hall call assignment program;

FIG. 9 is a flowchart of a program which assigns hall calls to a plurality of elevator cars;

FIG. 10 is a subroutine ASSIGN called by the program shown in FIG. 9 to make specific assignments of hall calls to the elevator cars;

FIG. 11 is a flow chart of a subroutine ETA-A which establishes a first travel path for an elevator car to service a hall call to be assigned;

FIG. 12 is a flow chart of a subroutine ETA-B which establishes a second travel path for an elevator car to service a hall call to be assigned;

FIG. 13 is a flow chart of a subroutine ETA-C which establishes a third travel path for an elevator car to service a hall call to be assigned;

FIG. 14 is a flow chart of a subroutine COMPUTE which may be used by subroutines ETA-A, ETA-B and ETA-C in computing the ETA travel time for a car to service a trip list prepared for the selected travel path;

FIG. 15 is a chart which illustrates the operation of the programs in selecting travel paths for a car in which its farthest committed stop is for a car call;

FIG. 16 is a chart which illustrates the operation of the program in selecting travel paths for a car in which its farthest committed stop is for a hall call;

FIG. 17 is a flowchart of a program which is called periodically on the basis of elapsed time, or on the basis of the number of hall calls, for adjusting the difference in seconds (T) required to initiate reassignment of a hall call to a car having a lower ETA than the presently assigned car;

FIG. 17A is a modification of the program set forth in FIG. 17 which may be used; and

FIG. 18 is RAM map illustrating program variables used and stored by the program of FIG. 17 to adjust the value of T to facilitate dynamic hall call assignment reevaluation.

The invention will be described relative to a specific, exemplary ETA dispatching system. It is to be understood, however, that the invention may be used to enhance any ETA type dispatching system.

Referring now to the drawings, and to FIG. 1 in particular there is shown an elevator system 20 which may benefit from the teachings of the invention. Elevator system 20 includes a plurality of elevator cars #0 through #N mounted for guided movement in hatchways 22 of a building 24 to serve the floors therein numbered 1 through N. Elevator cars #0 through #N, which cars may be of the hydraulic type, or of the traction type, as desired, each have a car controller, such as car controller 26 associated with car #0. The plurality of elevator cars #0 through #N are placed under group control by a system processor 28. A car controller which may be used for car controller 26 is shown in U.S. Pat. No. 3,750,850, with modifications thereof for group control by a system processor, including data links, being shown in U.S. Pat. No. 3,804,209. U.S. Pats. Nos. 3,750,850 and 3,804,209, which are assigned to the same assignee as the present application, are hereby incorporated into the specification of the present application by reference.

Car calls are registered in the elevator cars #0 through #N via suitable pushbutton arrays, such as pushbutton array 30 in car #0.

Hall calls are registered from suitable pushbuttons located at the various floors of building 24, such as an up hall call pushbutton 32 located at the lowest floor (floor #1), a down hall call pushbutton 34 located at the highest floor (floor #N), and up and down hall call buttons 36 located at each of the intermediate floors. The up and down hall calls may be serialized and transmitted to an input interface 38 of system processor 28 as signals 1Z and 2Z. The car calls registered in each of the cars may be serialized and transmitted to input interface 38 along with other per-car related information as signal 3Z. The per-car information includes car status signals, such as a signal INSV which is true when the associated car is in service; a signal UPTR which is a logic one when the associated car is set for up travel and a logic zero when it is set for down travel; a signal AVAS when an in-service elevator car is stationary, not busy and available for assignment, i.e., the car has no car calls and no assigned hall calls; a signal AVP which gives the advanced position of the associated elevator car in binary; a signal ACC which indicates the car is to accelerate away from a floor; a signal DEC which indicates the car should start decelerating to land at a target floor; a signal DCL which indicates that the car doors are closed; and a signal ACCX which is a start command. The per-car information also includes floor enable signals FEN which indicate which floors of the building 24 the associated car is enabled to serve. The floor enable signals may be set in memory tracks in the car controllers, or at a traffic director's station (not shown), as desired.

System processor 28, in addition to input interface 38, includes a central processing unit (CPU) 40, a read-only memory 42 (ROM), a random-access memory 44 (RAM), and an output port 46.

As shown in the RAM maps of FIGS. 2 and 3, system processor 28 stores the per-car information in suitable tables in RAM 44, including a car status table 48 (FIG. 2) and a floor-enable table 50 (FIG. 3).

System processor 28 additionally prepares a hall call table 52 shown in FIG. 4, a car table 54 shown in FIG. 5, an assignment register 56 shown in FIG. 6, and a trip list table 58 shown in FIG. 7. The hall call table 52 may be integrated into the assignment register 56 if desired, by adding a "call" bit next to the assignment bit in both the up and down call portions of the register.

FIG. 8 is a ROM map 60 which includes a list of constants stored in ROM which pertain to the specific elevator system 20. The constants include an initial time T in seconds by which the lowest ETA for a hall call must be lower than the ETA of a different car which was previously assigned to serve the hall call being considered, before the assignment will be switched to the different car. As will be hereinafter explained, this initial value of T is used according to the teachings of the invention to start a dynamic process of determining the optimum value for T for the specific building 24 and traffic patterns therein that the elevator system 20 is associated with. The constants also include a listing of times in seconds for the specific elevator cars in system 20 to perform the various functions required to serve the floors, including the time ACCT to accelerate from a floor to full speed; the time DECT to decelerate from full speed and land at a target floor; the time HS to travel from one floor level to another at full speed; the time OFTT for a car to make a one-floor run; the time ADT to land at a target floor when the car being considered is already in the process of decelerating; the time DOT for the elevator car door and associated hatchway door to fully open; the time DCT for the elevator car and hatch doors to travel from a fully open position to a fully closed position; the non-interference time NIT for which the car and hatchway doors are normally maintained open to answer a call; and the door cycle time DYCT which is the sum of DOT, NIT and DCT. The constants also include the desired average waiting time (AWT) that elevator system 20 was designed to produce for the associated building 24, and a constant X used by the program in FIG. 14.

FIG. 9 is a detailed flowchart of a hall call assignment program 62 stored in ROM 42. Program 62 is entered at 64 and step 66 initializes the system, such as by setting table pointers to initial positions. For example, step 66 places pointer 68 at the lowest up scan slot position so the program starts by looking for an up hall call at the lowest floor. When this pointer is incremented, it will go upwardly through the up hall call table. When it is incremented from the up scan slot for floor N-1 it will jump to the highest scan slot in the down hall call portion of the table. When the pointer is incremented downwardly through the down hall call table, it will jump back to the lowest scan slot in the up hall call portion of the table when it is advanced from the scan slot associated with the next to the lowest floor. Thus, the up scan slots are numbered 0 through N-1, and the down scan slots are numbered from N through 1. In like manner, pointer 70 is initialized at up scan slot 0 in the assignment register 56 shown in FIG. 6. Additional pointers to be initialized by step 66 include pointer 72 to the floor enable table 50 shown in FIG. 3, and pointer 74 to the car table 54 shown in FIG. 5.

After the initialization step 66, step 76 checks pointer 68 of the hall call table 52 for a registered up hall call. If no hall call is found, step 78 increments pointers 68, 70 and 72 of tables 52, 56 and 50, respectively, and the program returns to step 76. The program 62 thus loops through the up and down hall call tables continuously until step 76 finds a registered up or down hall call.

When step 76 finds a registered hall call, step 80 checks pointer 74 of the car table to determine which car is presently being considered for the hall call, it obtains the car status information associated with this car from the RAM map 48 shown FIG. 2, and it obtains the floor enable data FEN for this car from the floor enable table 50 shown in FIG. 3.

Step 82 checks the logic level of signal INSV to determine if the car being considered is in service. It this car is not in service, step 84 sets the ETA time for this car to the maximum value OFFH, and the program will not consider a car having the maximum ETA for assignment. Step 86 increments the car pointer 74 in the car table 54 of FIG. 5, and step 88 determines if the whole car table has been considered relative to the call in question. If one or more cars remain to be considered, step 88 returns to step 80 to obtain information relative to the newly selected car. If step 88 finds that all of the cars have been considered relative to the hall call in question, the program calls subroutine ASSIGN in step 90. Subroutine ASSIGN is shown in FIG. 10 which is a flowchart of an assignment program 92 which will be hereinafter be described in detail.

Returning to step 82, if step 82 finds that the car being considered is in service, step 94 checks the floor enable bit FEN to see if this car is enabled for the floor of the hall call. If this car is inhibited from serving hall calls at this floor, step 94 returns to step 84 and proceeds through steps 86, 88 and 90, which were previously described.

If step 94 finds that the car being considered is enabled for the floor of the hall call being considered, step 96 checks signal AVA to determine if the car is busy serving a call, or if it is idle and available for assignment. If the car is idle, step 96 proceeds to step 98 which calls a subroutine ETA-A for computing the ETA time for the car to serve the hall call. FIG. 11 is a flowchart of a program 100 which implements the ETA-A subroutine, and it will be hereinafter described in detail.

Step 98 returns to program step 86 after running subroutine ETA-A, to determine if all of the cars have been considered relative to the call to be assigned or reassigned.

If step 96 finds that the car being considered is not an idle car available for assignment, step 102 checks to see if the car has a car call 3Z or an assigned up or down hall call 1Z or 2Z, respectively. If the car has no car call and no hall call assignment, it may be considered to be the same as an available car and the program calls subroutine ETA-A in step 98.

If step 102 finds that the car is busy, ie., it has at least one car call or at least one assigned hall call, step 104 determines the floor of the farthest committed stop (FC floor) in the travel path of the car in serving its present workload. For example, if the car is traveling upwardly and its highest car call is for floor N-2, and it has no assigned hall calls which require further travel of the car, the FC floor would be N-2. If in addition to the car call at N-2, the car has been assigned a down hall call at floor N-4, then the FC floor would be N-4.

After the FC floor is determined, step 106 checks to see if the FC floor is related to a car call or an assigned hall call. If the FC floor is related to a car call, step 108 determines if the car travel direction is the same as the scanning direction through the hall call table 52 shown in FIG. 4. If the car is set for up travel and the scanning direction is upwardly through the up hall call table, or if the car is set for down travel and the scanning direction is downwardly through the down hall call table, step 108 proceeds to step 110. Step 110 determines if the scan slot floor (the floor of the hall call being considered) is closer to the AVP floor of the car than the previously determined FC floor. If the car will arrive at the scan slot floor before the FC floor, step 110 proceeds to step 98 to call subroutine ETA-A. If the car will arrive at the FC floor before reaching the scan slot floor, then step 110 proceeds to step 112. Step 112 calls a subroutine ETA-B to compute the ETA time for the car to arrive at the hall call floor. FIG. 12 is a flowchart of a program 114 which implements the ETA-B subroutine, and it will be hereinafter described in detail. Step 112 returns to step 86 to check for another car after subroutine ETA-B runs.

If step 108 found that the car travel direction was opposite to the scanning direction through the hall call table 52, then step 108 proceeds to step 112 to call subroutine ETA-B.

If step 106 found that the FC floor was not associated with a car call, then the FC floor is associated with a hall call assignment and the program branches to step 116. Step 116 is similar to step 108, determining if the car travel direction is the same or opposite to the scanning direction through hall call table 52. If the travel direction is the same as the scan direction step 118 checks to see if the car travel direction UPTR is the same as the service direction of the hall call at the FC floor. If the car travel direction is the same as the service direction of the hall call it had been previously assigned to serve, which call is located at the FC floor, step 118 returns to step 110 previously described. If the car travel direction is opposite to the direction of the hall call at the FC floor, then step 118 proceeds to step 98 to call subroutine ETA-A.

If step 116 finds the car travel direction UPTR is opposite to the scanning direction through the hall call table 52, step 116 proceeds to step 120. Step 120 determines if the car travel direction UPTR is the same as the direction of the hall call at the FC floor. If the directions are the same, step 120 proceeds to step 122 to call a subroutine ETA-C for computing the ETA time for the car to arrive at the scan floor. FIG. 13 is a flowchart of a program 124 which implements the ETA-C subroutine, and it will be hereinafter described in detail. Step 122 returns to step 86 after running subroutine ETA-C.

If step 120 finds that the car travel direction UPTR is opposite to the direction of the hall call at the FC floor, step 120 proceeds to step 126 to determine if the scan floor of the hall call being considered is farther from the AVP floor of the car than the previously determined FC floor. If the scan slot floor is farther from the AVP floor than the FC floor, step 126 proceeds to step 98 to call subroutine ETA-A. If the scan slot floor is not farther from the AVP floor than the FC floor, step 126 proceeds to step 112 to call subroutine ETA-B.

Subroutines ETA-A, ETA-B and ETA-C establish three different potential travel travel paths for determining ETA time. Subroutine ETA-A is entered at 128 and step 130 prepares a trip list for the car being considered from the advanced floor position AVP of the car to the scan slot floor. FIG. 7 illustrates the trip list 58, and it would be made out for the car in question, listing all stops between the AVP floor and the scan slot floor. If the car's AVP is the second floor and the scan slot floor is N-1, for example, all of the stops which the car is presently committed to make between these two floors would be listed. Step 132 computes the time for the car to complete its trip list and arrive at the scan slot floor. Step 132 calls a subroutine COMPUTE shown in FIG. 14, with FIG. 14 being a flowchart of a program 134 for computing ETA which will be hereinafter described. Subroutine ETA-A returns to the main program at 136 after computing and storing the ETA for the car in question for comparison with the ETA's of the remaining cars.

Subroutine ETA-B is entered at 138 and step 140 prepares a trip list for the car being considered from the AVP floor of the car to the FC floor, and from the FC floor to the scan floor. Thus, unlike ETA-A, which prepared a trip list from the car directly to the scan floor, ETA-B prepares a trip list from the car to the floor of the farthest committed call, i.e., the FC floor, and then from the FC floor to the floor of the hall call being considered for assignment, ie., the scan floor. Step 142 calls the subroutine COMPUTE shown in FIG. 14 to compute the time for the car to complete its trip list, and the subroutine returns to the main program at 144.

Subroutine ETA-C is a subroutine used only when the FC floor is related to a hall call. Subroutine ETA-C is entered at 146 and step 148 prepares a trip list for the car being considered from the AVP floor of the car to the FC floor, from the FC floor to the terminal floor which is in the direction of the service direction of the hall call at the FC floor, and from this terminal floor to the hall call scan floor. Thus, unlike ETA-A, which prepares a trip list from the car directly to the scan floor, and unlike ETA-B which prepares a trip list from the car to the floor of the farthest committed call, ie., the FC floor, and then from the FC floor to the floor of the hall call being considered for assignment, i.e., the scan floor, ETA-C prepares a trip list from the car to the FC floor, from the FC floor to a terminal floor, and then from the terminal floor to the scan floor. Step 150 calls the subroutine COMPUTE shown in FIG. 14 to compute the time for the car to complete its trip list, and the subroutine returns to the main program at 152.

The program 134 for the subroutine COMPUTE shown in FIG. 14 is entered at 154 and the purpose of the subroutine is to compute the ETA for the specific trip list prepared for the car. Step 156 checks to see if the car is moving. If either signal ACC or signal DEC is true, the car is moving. If the car is not moving, step 158 checks signal DCL to see if the car doors are closed. If the car doors are closed, step 160 checks start command signal ACCX to determine if the car has just arrived or is preparing to leave the floor. If the car is not leaving it has just arrived, or is parked at the floor with its doors closed. Step 162 determines if the floor at which the car is located is the scan floor, i.e., the floor of the hall call to be assigned. In this instance it is not the scan floor, as the hall call would have been cancelled when the car started decelerating to stop at the floor, and step 162 proceeds to step 164 to see if the car is a busy car or an available car by checking signal AVAS. If the car is not available, then it just stopped at the floor and step 166 adds the door cycle time DCYT to any previous ETA time computed for this car. If the car is available, then no door time is required as the car can start on its trip list without opening its doors. Step 166 and the "yes" branch from step 164 proceed to step 168 which checks to see if the next stop on the trip list is one floor from the present car position, i.e., a one-floor run. If the next stop is a one-floor run, step 170 adds the one-floor run time OFTT to any prior computed value of ETA, and stores the new ETA at a temporary location in RAM. Step 162 checks to see if this next stop, i.e., the one floor run, will bring the car to the scan floor. If not, step 166 adds the door cycle time DCYT to the car's ETA and returns to step 168. If the next stop on the trip list is not a one-floor run, step 172 adds the acceleration time ACCT to the car's ETA and proceeds to step 174. Step 174 determines how many floors will be passed at rated speed before reaching the next stop on the trip list, and multiplies this number by the time HST required for the car to travel between two floors at rated speed. This time, plus the deceleration time DECT to stop at the next stop are added to the car's ETA. Step 174 proceeds to step 162 to determine if the car has completed its trip list. When step 162 finds that the stop being considered is the scan slot floor, step 176 adds the time DOT to open the door at the scan slot floor to the car's ETA.

If step 158 finds the doors open, step 159 adds the door non-interference time NIT and the door close time DCT to the car's ETA. Step 159 proceeds to step 168.

If step 156 finds that the car is moving at the time its trip list is initiated, the car is accelerating, or it is at full speed, or it is already decelerating. Step 186 determines if the car is accelerating, and if it is, step 172 adds the accelerating time ACCT to the car's ETA, and advances to step 174, which was previously described. If the car is not accelerating, step 188 determines if the car is traveling at full speed. If it is traveling at full speed, step 188 advances to step 174. If the car is not accelerating and is not traveling at full speed, it is already decelerating and step 188 advances to step 190 which adds the "already decelerating" time ADT to the car's ETA. Step 190 advances to step 162. Thus, when all of the floor stops on the trip list have been considererd, the car's ETA has been completed, and the subroutine returns to the main program 62 shown in FIG. 62.

When program 62 finds that the ETA times for all of the cars have been computed for the hall call in question, step 88 branches to step 90 which calls subroutine ASSIGN. Subroutine ASSIGN is a program 92 shown in FIG. 10 which is entered at 192. Step 194 compares the ETA values for all of the cars and determines which car # has the lowest ETA value. Step 196 determines if this hall call is a new call, or one which had been previously assigned to a car, by checking the assignment bit in assignment register 56 shown in FIG. 6. If the call is a new hall call, step 198 assigns the call to the car having the lowest ETA and the subroutine exits at 200 to return to the main program to consider the next hall call in the hall call table 52.

If the call had been previously assigned, step 196 advances to step 202 which determines the car # to which the call was assigned. Step 204 checks to see if the car # with the lowest ETA is the same car # to which the call had been previously assigned. If it is the same car, step 198 returns to the main program at 200.

If step 204 finds that the car having the lowest ETA is not the same as the car with the prior assignment, step 206 determines the difference between the ETA's of the two cars and step 208 determines if the new car's ETA time is lower than the ETA time of the prior assigned car by a predetermined number T. If the new car's ETA is not lower by T seconds, the assignment to the prior car is retained and step 208 returns to the main program. If the new car's ETA is lower than the prior car's ETA by more than T seconds, step 210 assigns the call to the new car and removes the assignment from the assignment register of the prior car. Step 210 returns to the main program 200.

The chart of FIG. 15 lists examples of the travel paths for different relative positions of the AVP floor, the scan slot floor and the FC floor when the FC floor is related to a car call. The car call floor has no service direction, which simplifies the travel paths to those of subroutines ETA-A and ETA-B.

If the scan slot floor is between the AVP floor and the FC floor, the travel path and thus the trip list will be between the AVP floor and the scan slot floor, as indicated by dotted line 212. This is implemented by subroutine ETA-A. In the remaining examples, the travel path and trip list extends from the AVP floor to the FC floor, and from the FC floor to the scan floor, which is implemented by subroutine ETA-B.

More specifically, when the FC floor is between the AVP floor and the scan slot floor, the travel path if from the car to the FC floor and from the FC floor to the scan floor regardless of the car travel direction or scan direction. This is indicated by travel paths 214 and 216 for like travel and scan directions, and by travel paths 218 and 220 for unlike travel and scan directions.

When the scan floor is between the AVP floor and the FC floor, and the scanning direction is opposite to the car travel direction, the travel path extends from the AVP floor to the FC floor, indicated by travel path 222, which by-passes the scan floor, and then the travel path reverses, indicated by travel path 224, to extend from the FC floor to the scan floor.

When the FC floor is on one side of the AVP floor and the scan floor on the other side, with unlike travel and scan directions, travel path 226 is followed from the AVP floor to the FC floor, and the travel path then reverses, following path 228 from the FC floor to the scan floor.

The chart of FIG. 16 lists examples of the travel paths for different relative positions of the AVP floor, the scan slot floor and the FC floor when the FC floor is related to a hall call. The hall call floor has a service direction, which requires the travel path provided by subroutine ETA-C in addition to the travel paths provided by subroutines ETA-A and ETA-B.

More specifically, if the FC floor is between the AVP floor and the scan floor, and the hall call at the FC floor has the same service direction as the car travel direction, subroutine ETA-B is selected which provides a travel path 230 from the AVP floor to the FC floor, and a travel path 232 from the FC floor to the scan floor.

When the FC floor is between the AVP floor and the scan floor, and the hall call at the FC floor has a service direction which is opposite to the car travel direction, subroutine ETA-A is selected, establishing a travel path 234 from the AVP floor to the scan floor. The assigned hall call at the FC floor is ignored during this determination, and if it should result that the car is assigned the hall call at the scan floor, the down hall call previously assigned to this car will probably be reassigned to another car.

In like manner, if the scan floor is closer to the AVP floor than the FC floor, the car travel direction is the same as the scan direction and opposite to the service direction of the hall call at the FC floor, travel path 236 will be followed from the AVP floor to the scan floor, with the assigned down hall call at the FC floor being ignored. This result will be provided by calling subroutine ETA-A.

When the FC floor is closer to the AVP floor than the scan floor, the car travel direction is the same as the service direction of the assigned hall call at the FC floor, and the scan direction is opposite to the car travel direction, the travel path includes a leg 238 from the AVP floor to the FC floor to service the up hall call. Since is is not known at this point how far the up hall call passenger will wish to travel in the up direction, it is assumed that the prospective passenger will place a car call for the longest trip, i.e., to the upper terminal floor N, providing a travel path 240 from the FC floor to the terminal floor N, and a travel path 242 from the terminal floor N to the scan floor. This result is provided by calling subroutine ETA-C.

When the scan floor is closer to the car than the FC floor and the car travel direction is opposite to both the scan direction and the service direction of the hall call at the FC floor, a travel path having a leg 244 extends from the AVP floor to the FC floor, and leg 246 extends from the FC floor to the scan floor. This requires subroutine ETA-B.

When the scan floor is closer to the AVP floor than the FC floor, and the car travel direction is opposite to both the scan direction and the service direction of the hall call at the FC floor, subroutine ETA-A is called which establishes travel path 248 from the AVP floor to the scan floor.

When the car's AVP floor is between the scan floor and the FC floor, and the car travel direction is opposite to both the scan direction and the service direction of the hall call at the FC floor, the travel path includes a leg 250 from the AVP floor to the FC floor, and a leg 252 from the FC floor to the scan floor.

FIG. 17 is a flowchart of a program 258 which implements the teachings of the invention. Program 258 is called periodically, such as by a timer interrupt, to update the value of T used by step 208 of the assignment program 92 shown in FIG. 10. FIG. 18 is a RAM map 260 showing information utilized by program 258, as well as program variables used and stored by program 258. For example, when the elevator system is initialized, RAM map 260 includes the initial value of T obtained from the ROM map 60 shown in FIG. 8. This value will be continuously updated, and will thereafter always show the updated value. RAM map 260 also tabulates the total number of hall calls entered into the elevator system 20 since the last calculation of AWT, it keeps track of the total waiting time from hall call timers (not shown) which are active while the tabulated hall calls are active, it stores the last AWT calculated by program 258, and it includes a flag termed DEC FLAG which is set when the last change in T was due to a decrementation thereof.

Program 258 is entered at 262 and step 264 goes to the RAM map 260 of FIG. 260 and retrieves the value of T, the total number of hall calls entered over defined periods of building usage time since the last calculation of T, the total waiting time associated with the tabulated hall calls, and the last calculation of AWT. Step 264 also obtains the desired AWT from ROM map 60 shown in FIG. 8.

Step 266 determines if the information call information is sufficient to basis a new update on. This may be triggered on an elapsed time basis, when the number of calls tabulated reaches a predetermined number, when the accumulated waiting time reaches a predetermined value, and the like. For purposes of example, step 266 checks the number of tabulated calls, using 1000 calls as the trigger point. If step 266 finds that the number of calls does not exceed 1000, the program exits at 268.

When step 266 finds more than 1000 calls, step 270 calculates the AWT for the last value of T used. Step 272 compares this calculation with the desired AWT for the building. If the actual AWT is within a predetermined tolerance of the desired AWT, step 272 advances to step 280 which clears the number of hall calls and total waiting time, to start the next calculation period, and it stores the last calculation of AWT in the RAM map 260 for use during the next calculation. Step 280 then returns to the main program at 268.

If step 272 finds that the actual AW is not within the predetermined tolerance of the desired AWT, step 272 proceeds to step 274 to determine if the newly calculated AWT is closer to the desired AWT than the last calculated value just retrieved from RAM. If it is closer, the last change in T was in the proper direction and step 276 checks DEC FLAG to see if the last change incremented or decremented T. If the DEC FLAG is not set it indicates that the last change was an increment, and step 278 increments T and stores the new value in RAM. Step 278 then proceeds to step 280 and exits the program at 268. This process will continue as long as each calculation of actual AWT is closer to the desired AWT than the prior calculation. When step 274 finds that the new calculation of AWT is not as close to the desired AWT as the prior calculation, step 274 proceeds to step 282 which checks DEC FLAG. If DEC FLAG is not set, the last change incremented T and the program goes to step 284 which decrements T. Step 286 sets DEC FLAG and proceeds to step 280 which stores the new T, as well as clearing the calls and accumulated waiting time.

If decrementing T now causes step 274 to find that the newly calculated AWT is closer to the desired AWT than the prior calculation, step 276 will now find DEC FLAG set and advance to step 288 which decrements T. This process will continue until step 274 finds that the prior calculation of AWT was closer to the desired value than the new calculation, and step 274 will advance to step 282. Step 282 will now find DEC FLAG set and advance to step 290 which increments T. Step 292 resets DEC FLAG.

FIG. 17A sets forth a modification of the invention set forth in program 258 shown in FIG. 17 which may be used between steps 272 and 280. In this modification, the program looks to see if the actual AWT is less than, or greater than, the desired AW. If the actual calculated AWT is less than the desired AWT, tested in step 294, step 294 proceeds to step 296 which decrements T and stores the new value for T in RAM. If the actual calculated AWT is not less than the desired AWT, i.e., it is greater, than step 294 proceeds to step 298 which increments T.

Thus, there has been disclosed a modification to ETA dispatching strategy which allows building population and/or traffic patterns may change with losing elevator efficiency, as program 258 will continuously provide the optimum value of T required to maintain the elevator system 20 at peak dispatching efficiency.