Introduction
In the elevator industry, when selecting a traction machine, the starting point is often the product: a specific technology, a familiar configuration, a solution that “has always worked.” This is an understandable approach, especially in contexts where time constraints and complexity push toward decision shortcuts.
However, starting from the product is also one of the most common mistakes.
Today’s projects are increasingly complex: mixed-use buildings, limited spaces, variable traffic flows, strict regulations, and high expectations in terms of comfort, reliability, and efficiency. In this scenario, a correct technical choice cannot rely on a standard solution but must originate from a structured analysis of the application context.
This is where Application Driven Design comes into play: an approach that reverses the perspective and places the problem, not the product, at the center of the decision-making process.
The choice does not start from the product
Why there is no universal solution
In the world of traction machines, there is no single solution suitable for every project. Each installation operates within a unique scenario defined by technical, functional, and operational variables that change from case to case.
Assuming that one technology can fit every context means oversimplifying a reality that, in practice, is far more complex. A solution that works effectively in one building may prove inefficient, oversized, or unsuitable in another.
The risks of a “one-size-fits-all” approach
A standardized approach involves several risks:
- performance not aligned with actual usage;
- long-term inefficiencies;
- higher operating and maintenance costs;
- design compromises that only emerge after installation.
Starting from the product often means adapting the project to the solution rather than the other way around.
Context as the starting point
A correct technical choice originates from the analysis of the application context. This means asking the right questions before even evaluating technologies or configurations.
Building type
Residential, commercial, industrial, public, healthcare: each building type has specific requirements in terms of usage, service continuity, and user expectations.
Actual system usage
What matters is not only the intended use on paper, but how the system will actually be used: peak hours, average loads, frequency of operation, and daily operating conditions.
Traffic and frequency
Traffic is one of the most critical variables. Intense and concentrated flows require different solutions compared to more evenly distributed usage over time. Properly assessing these aspects means designing a system consistent with its function.
Space and design constraints
Shaft dimensions, available headroom, building layout, architectural and regulatory constraints: space is not a detail but a determining factor that guides technical choices from the very beginning.
Application Driven Design: a change in method
Not a technology, but an approach
Application Driven Design is neither a technical solution nor a specific technology. It is a working method that connects needs, constraints, and objectives before defining the most suitable solution. The focus shifts from “what to install” to “why to install it.”
How dialogue changes among designers, installers, and manufacturers
Adopting this approach also means changing how project stakeholders interact. The discussion becomes more structured, based on data, context, and actual system usage.
Designers, installers, and manufacturers collaborate to build a coherent solution, avoiding decisions driven solely by habit or by the immediate availability of a product.
Informed decisions = long-term value
A choice guided by context delivers benefits not only during design and installation but also over the long term.
Efficiency
A system designed according to its real application uses resources more efficiently, avoiding oversizing or unnecessary configurations.
Reliability
Consistency between expected use and the technical solution increases system reliability and reduces the risk of operational issues over time.
Alignment between needs and solution
When the choice originates from context, the final solution is more balanced: it responds to the real needs of the project and supports system performance throughout its lifecycle.
Conclusion
Context drives the choice.
And every project deserves a dedicated evaluation.
Application Driven Design is not an abstract concept but a practical method for addressing the complexity of modern projects. An approach that supports more informed, technically sound decisions focused on long-term value.