Cover of The Elevator: Rope, Brake, Sky, a book by Ketineni RamaraoFrom the book The Elevator: Rope, Brake, Sky
Chapters 18-18A, 20A and 33. Read the full book free as a PDF.

The queue is a system problem

A passenger sees doors and wonders why the car takes so long. The simple answer seems to be speed: make the lift faster. But a building's transport service includes waiting, boarding, stopping and leaving as well as motion through the shaft. A faster trip between floors cannot remove every other part of that journey.

KONE's destination-control explanation focuses on assigning passengers to suitable cars using their requested floors. ASME likewise describes batching stop requests as an energy-conscious control strategy. The shared mechanism is grouping trips. It changes how the available cars are used rather than merely making each cabin travel faster.

A conventional call gives limited information

With an ordinary up-or-down landing request, the system knows a passenger wants to travel in a direction but may not yet know the destination. Passengers then choose floors inside the arriving car. Several people can enter one cabin while needing many different stops. The loading pattern matters to the service that follows.

KONE contrasts this with entering a destination before boarding. Its description is a supplier's account, not an independent performance guarantee. The useful factual point is what information the controller receives and when it receives it. Knowing destinations sooner creates different options for grouping passengers.

Destination entry changes the assignment

In destination control, the passenger chooses the required floor at the departure landing and receives guidance to a particular elevator. The system can group people going to the same or nearby floors. KONE says this can reduce intermediate stops, with results depending on building layout, configuration and traffic conditions.

Passenger: chooses destination; System: groups nearby floors; Display: assigns a car; Boarding: follow assignment; Result: fewer avoidable stops
Original IOI explanatory diagram, based on the linked sources; not to scale.

The passenger must follow the assignment rather than automatically entering the first opening car. The interface is therefore part of the transport design. A technically useful assignment is only useful in practice if people can understand which cabin to board. Signage and clear feedback matter alongside the dispatch logic.

The building supplies different traffic patterns

An office arrival peak, movement between floors and a hotel's visitor traffic do not ask the same question of a lift group. KONE describes destination-control applications across offices, residential buildings, hotels and mixed-use developments. Benefits are not necessarily identical in each setting.

This is why no universal waiting-time reduction is offered here. A supplier can explain how grouping works without establishing what one particular building will achieve. Assessment must consider its destinations, traffic and equipment. A single product label does not substitute for understanding who is trying to travel where.

Access and accessibility add requirements

KONE describes integration with access-control systems and options that provide additional time or different passenger allocations for accessibility needs. The dispatch task can therefore involve more than choosing a physically nearby car. The building may need to consider permitted floors and users needing different boarding conditions.

Such features depend on the actual configuration. A destination panel should not be assumed to include every option simply because the technology can support it. In the book's material perspective, the interface, controls and building rules meet at the same doorway. Treating software alone as the solution misses that junction.

Throughput and experience both count

The Elevator's treatment of traffic asks how a fixed set of shafts serves a changing population. Speed is one variable, but grouping can change stops and the distribution of passengers between cars. ASME's overview places control strategies beside hardware because energy use and service patterns depend on how equipment is operated.

The practical lesson is to identify the bottleneck before buying a faster machine. Is the issue travel time, too many stops, uneven loading or an interface people cannot use easily? Destination control addresses the information and assignment part of that question. It does not make every queue vanish, but it shows why a lift is a traffic system rather than a motor with buttons.

Quick answers

Where do users choose the floor?

In destination control, generally at the departure landing before entering the assigned car.

Will it always reduce waiting?

No universal result is claimed. Performance depends on the building, configuration and traffic.

Sources

Technical claims checked against the sources below; no current market-size or price claim is made.

More from this book

Mechanism · From the book The Elevator: Rope, Brake, Sky

How a traction elevator moves its car

A traction elevator does not wind a passenger car onto a drum.

Safety systems · From the book The Elevator: Rope, Brake, Sky

Why an elevator has more than one brake

The machine brake, overspeed governor, car safeties and buffers are different parts.

Lifecycle · From the book The Elevator: Rope, Brake, Sky

Maintenance or modernisation: what an old lift needs

Keeping equipment working and changing its underlying system are different decisions.

History · From the book The Elevator: Rope, Brake, Sky

What Elisha Otis actually changed

Elisha Otis did not invent lifting.