On further thought, another solution could be to implement a singular, digital wall panel where users can indicate to which specific floor they are intending to go, much like the ones found in many newer high-rise office buildings and hotels:
Original image by Access Matters on Flickr, used under CC BY-NC-SA 2.0.
Once the floor is selected, the main ...
In an office building where I worked, they solved a similar problem by making panel A a bit less obvious than panel B. Panel B was right out in the open, on the wall between two of the elevators, facing the lobby.
Panel A was located in the kind of door jamb space of elevator 1, perpendicular and right next to the elevator doors.
If this is not clear - this is bad solution.
Of course this is just a mockup.
Add accessibility icon at Panel A as most people respect this mark and will not use marked buttons.
Add notice to Panel B for rooftop and garage to make clear what to do - explicit allowance to use Panel A appropriate buttons.
Panel A button pairs Up and ...
This is a people problem.
This can be fixed by using some scotch tape and a piece of paper which reads:
Please use this panel only if you need roof or basement access, or need extra space for a wheelchair or other large belongings.
Thank you for your consideration.
The heart of the problem is that people going to every floor except the roof & basement will on average get better service by pressing both buttons. Any modification needs to remove that incentive, or remove the ability of inappropriate users to "double call".
For the floors other than lobby, I would make the selectors mutually exclusive: ...
I think this is especially tough because the combination of these issues:
E1 is the only way to access the roof and garage
E1 is the main intended elevator for for wheelchairs/strollers/accessibility
E1 is associated with panel A AND panel B
I'm going to assume that most users already have some way of knowing (existing labeling?) that E1 is the appropriate ...
Many of the proposed solutions involve combining the panels or relabeling Elevator 1's controls. The problem with this is accessibility: anyone who needs the larger car (especially if they are not tenants -- visitors or delivery people mostly) may not understand they have to use that panel to get Elevator 1 if their destination isn't one of the specially-...
I think the functionality of the elevators and two panels are fine. The issue is with user behavior.
You have two sets of users:
Users who are in a wheelchair or want to go to roof or basement.
Users not in set 1. ie. non-wheelchair users who want to go to general floors.
For each set of users, we want to encourage and discourage a certain behavior.
No hardware modification required. Just add two software rules:
full priority to the destination floor selected inside the elevator 1 when at the garage level or at the roof level
full priority to the elevator call buttons at the garage level and the roof level
This way the elevator 1 will not be affected by people pressing both buttons on all ...
Elevator1 Elevator2 Elevator3 Elevator4
~4 min ~1 min ~3 min ~3 min
The problem seems to be people believing they get a benefit out of pressing both buttons, when in fact they will not. I think this can be addressed by communicating the state of things more clearly. By displaying an estimated waiting time for ...
Panel "A" - Calls elevator 1
Panel "B" - Calls elevators 1-4
Panel "A+B" - May end up calling two elevators
Below are 2 proposed fixes, intended to be used at the same time.
If a user pushes any button on any panel, the corresponding light will turn on.
If a user pushes a direction on panel "A"...
Make panel B light up the buttons on both panels, summon any elevator, and have both go out when any elevator answers.
Make panel A light up only panel A, and summon only elevator 1.
Make elevator 1 responding to a panel A summons or use NOT respond to panel B summons. This mode would probably end when either the elevator is closed and not ...
I'd put a timer / a usage sensor in the circuits for Elevator 1 during peak periods, so once its been called it will always go directly to the set destination ( the roof or the basement )
Anything to do with trying to get users to modify their pattern of behaviour is going to be too complex.
EDIT: this doesn't address the disabled usage issue which I couldn'...