Scope an elevator modernization from a single-speed or older AC/DC drive to a VVVF (variable-voltage, variable-frequency) drive, including when machine-room-less (MRL) retrofit is feasible
domain: Elevator Modernization Scoping — Drive Upgrade & MRL Feasibility · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the existing equipment's drive type, hoistway dimensions, pit depth, and overhead clearance from as-built drawings or a field survey before assuming any modernization path
For a VVVF drive upgrade, confirm the new controller/drive is compatible with the existing motor, governor, and safety-device wiring, or whether those must be replaced as part of the same scope
For a machine-room-less retrofit, confirm the existing hoistway footprint, pit, and overhead can accommodate a gearless MRL drive unit within the shaft per the manufacturer's engineering data, since MRL units are designed to fit within standard shaft dimensions but still have minimum clearance requirements
Identify whether any dimension falls short of current code minimums (pit depth, overhead, refuge space) and, if so, confirm whether the AHJ has a variance/alternative-compliance process rather than assuming the modernization is a straightforward like-for-like swap
Confirm which retroactive code requirements (e.g., door lock monitoring, firefighters' service upgrades) will be triggered by the modernization filing itself, since a modernization permit can obligate compliance with current retroactive rules beyond just the drive change
Known gotchas
MRL feasibility is manufacturer- and model-specific — 'MRL fits in the existing shaft' is a general industry claim, not a guarantee for a specific building without an engineering survey
A modernization permit filing can trigger compliance with current retroactive code items (door lock monitoring, fire service, etc.) that a pure like-for-like drive swap might otherwise avoid — confirm this with the AHJ before scoping cost
If any existing dimension (pit, overhead) doesn't meet current code minimums, the project needs a documented AHJ variance/interpretation, not just a design workaround, before permitting
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?