Useful elevator software needs to model passenger population and arrival patterns, multiple traffic mixes across a full day, dispatch and control logic, and physical car and shaft constraints, then report interval, handling capacity, and waiting time against each scenario. Software that only handles a single traffic pattern is answering a narrower question than most projects actually need answered.
It's easy to assume that any tool producing an interval-and-handling-capacity number is doing the same job. In practice, the range of what gets called elevator software spans a simple calculator built around one formula through to full discrete-event simulation, and the gap between those two ends of the range matters for how much a design team can actually trust the output.
Population and Demand, Not Just Floor Count
The first thing worth checking is whether the tool takes population and attendance assumptions as real inputs, or whether it infers demand purely from floor area and a fixed occupancy ratio. Buildings with unusual density, shift patterns, or a non-standard mix of uses need software that lets those assumptions be set explicitly and tested against alternatives, not baked in as defaults.
More Than One Traffic Pattern
A tool that only tests the morning up-peak is answering the easiest question in the brief. Useful software also runs lunchtime, interfloor, and down-peak scenarios, each with its own passenger mix, because a design that clears up-peak can still fail at other times of day. This is where calculation-only tools tend to fall short of what a mixed-use or heavily interfloor-trafficked building actually needs.
It's a reasonable question to ask a vendor directly: does the tool run more than one traffic mix in a single project, or does every additional scenario require setting the whole model up again from scratch? The answer says a lot about whether a piece of software was built for comparing design options or for producing a single compliance number and moving on.
Dispatch Logic and Physical Constraints
Destination-control dispatch groups passengers differently from conventional up-and-down call buttons, and that grouping changes round-trip time in ways a generic formula won't capture. Software worth trusting for this kind of building needs to model the specific control strategy being proposed, alongside real car capacity, door timing, and travel speed, rather than treating dispatch as a detail to be added later.
Interoperability With the Rest of the Design Team
Lift design doesn't happen in isolation from the rest of the building model. Where a project is running in buildingSMART's openBIM workflow, core dimensions and shaft geometry are increasingly held in an IFC model shared across disciplines, and elevator software that can work from, or at least stay consistent with, that shared geometry avoids the coordination errors that creep in when core dimensions are re-entered by hand in a separate tool.
None of this needs to be complicated to check. A short conversation with a vendor or consultant, covering population inputs, the number of traffic scenarios tested, dispatch modelling, and how results are reported, tends to separate a genuinely capable tool from one that only handles the easiest version of the question.
What Good Output Looks Like
The output that actually helps a design team is a side-by-side comparison of interval, handling capacity, and waiting time across every traffic scenario tested, for more than one candidate configuration, not a single pass-or-fail number. AdSimulo is built around producing exactly that kind of comparison, so a four-lift and a five-lift option can be weighed against each other on the same evidence rather than taken on faith.
The underlying test is simple even when the software isn't: would this tool's output survive being challenged by someone who genuinely knows the building? If the answer to a question like "what happens at lunchtime" or "how does this handle destination control" is that the tool doesn't model that, the output is narrower than it looks, whatever the report's cover page claims.
