The part of procurement everyone thinks is easy
I manage purchasing for a facilities company. Roughly 400 employees, three locations, eight vendors across different service categories. Elevator components and cable railing systems come through my desk every quarter — maintenance parts, retrofit orders, occasional new-build support.
When I took over purchasing in 2020, I assumed this category would be the simplest. Elevator components are hardware with specs. Cable railing is metal with specs. Get quotes, compare numbers, award to the lowest bidder. Right?
Not even close.
It took me about three years, two delayed projects, and one compliance issue that made me look bad to our VP of Operations before I understood something fundamental: the problem with elevator component sourcing and cable railing procurement isn't price. It's that the specifications you send to vendors rarely match the specifications your project actually needs. And nobody tells you that upfront.
The real problem: your specs aren't as clear as you think
Here's what I used to do. Project manager says we need cable railing for a stairwell. I pull the dimensions, note the material preference, maybe grab a reference photo, and send it to four vendors. They come back with quotes. I pick one. Done.
Except it wasn't done. Not even close.
The first time this blew up, we ordered a cable railing system that met the visual requirements perfectly. Looked great in the catalog. The vendor confirmed all the measurements. But when the installation crew showed up, the anchoring system didn't meet local building code for that application. We needed a different tensioning method and thicker cables. The vendor blamed us for not specifying it. We blamed the vendor for not asking. The project sat for three weeks while we sorted it out.
That's when I learned the hard truth about this industry: specifications aren't just dimensions and materials — they're compliance requirements, load ratings, testing standards, and installation constraints, all bundled together. And most purchasing people, including me, only know about the first two.
Three things I didn't know I didn't know
First: elevator component compliance isn't one standard. It depends on the elevator type, the building code in your jurisdiction, the year of installation, and whether you're doing a modernization or a repair. A component that's compliant in one state might not be in another. I once sourced what I thought was a universal door operator part. Turns out, our building was under a code cycle that required additional safety features. The part was well-made. It just didn't belong in our building.
Second: cable railing specifications involve structural assumptions you may never see. The vendor calculates tension, spacing, and anchoring based on what you tell them. If your input is wrong — or incomplete — the output looks fine on paper but fails in the field. This isn't a vendor problem. It's a communication problem. And it flows both ways.
Third: the sourcing process itself has gaps you can't fix with better spreadsheets. I tried building a more detailed RFP template. I added more fields, more checkboxes, more reference documents. It helped, but only marginally. Because the information that matters most — the specific compliance standard your project falls under, the exact load requirements, the installation environment — often lives with the architect or engineer, not with purchasing.
Why does this matter? Because when I was searching for answers early on, I kept running into the same problem: fragmented information. I'd search for "elevator components compliance requirements" and get results for a completely different industry — I remember one search where I ended up on a page about a king kone cone filler machine, which tells you how noisy the keyword landscape is. The signal-to-noise ratio on technical procurement topics is terrible.
What this actually costs
Let me be specific, because vague warnings don't help anyone.
On one retrofit project, we ordered elevator door components that met the spec sheet we sent, but didn't meet ASME A17.1 requirements for that specific building application. The parts arrived. The installer started work. Two days in, the local inspector flagged the installation. We had to pull everything, re-order, and eat the labor cost on the first installation attempt. Total delay: four weeks. Total extra cost: somewhere around $4,200 — I don't have the exact figure in front of me, but it was in that range.On the cable railing side, the cost is less dramatic but more insidious. We've had three projects where the railing system technically met the specs, passed inspection, and looked fine... but the client complained about "movement" within six months. Not a failure. Just enough flex to feel cheap. The problem was spacing between posts relative to the cable diameter, which nobody specified clearly. We ended up re-tensioning every run and adding two intermediate posts per section. Not covered by warranty. Not covered by the client contract. Just... absorbed.
But the real cost isn't dollars. It's this: after two of these incidents, our operations team stopped trusting the procurement process for anything technical. They started bypassing me and going directly to vendors they knew. That undermined my role, created invoice chaos, and made it nearly impossible to track compliance documentation across projects.
Looking back, I should have realized that the problem wasn't the vendors. It wasn't even the specs. It was that I was treating a compliance-heavy procurement category like a commodity purchase.
What actually helps (keep it simple)
The fix was less about adding process and more about shifting where the information comes from.
If you're sourcing elevator components or cable railing systems for B2B projects, here's what I'd suggest — nothing revolutionary, just the stuff that worked for us.
Start with compliance, not with price. Before you send a single RFQ, know which standard applies to your project. For elevator components in the US, that's typically ASME A17.1/CSA B44. For railings, it's IBC Section 1015 for loads and often ASTM E935 for testing. If you're sourcing internationally, EN 81-20 and EN 81-50 apply. This isn't optional background info — it's the foundation of every spec you send out. Confirm current requirements with your local authority having jurisdiction, because code cycles change.
Have one conversation with the technical side before you go to market. Whether it's your engineer, your architect, or the installation contractor — get them to document the compliance requirements, load assumptions, and installation constraints in writing. Then attach that to your RFQ. This single step eliminated about 80% of our back-and-forth on cable railing projects.
Work with vendors who can handle a technical conversation. The difference between a vendor who takes your spec at face value and one who asks "what code cycle is this building under?" is the difference between a smooth project and a four-week delay. When I started screening vendors for their ability to ask clarifying questions — not just their prices — the quality of our outcomes changed noticeably.
Switching to this approach cut our revision cycles from an average of three per project to fewer than one. And it eliminated the re-inspection failures that used to eat up entire weeks.
I won't pretend it's a perfect system. We still hit snags — especially on older buildings where nobody has complete documentation. But the difference between approaching this as a price-driven purchase and approaching it as a specification-driven one is the difference between reacting to problems and preventing them. That's not a small thing.