By Uwe Janssen · Rauch Safety & Engineering · Las Vegas, Nevada
Every permanent access system installed on a building or structure will, if the asset lives long enough, present its owner with the same decision: the system has aged past the point where routine service sustains it, and something structural must now be done. Permanent access systems can remain in service for decades. Building maintenance units, davit systems, and anchor installations may therefore remain in service under conditions materially different from those surrounding them when they were installed. The decision that follows — refurbish, retrofit, or replace — is a capital event, and it is a decision with a structural feature that distinguishes it from almost every other capital decision the owner faces: much of the readily available advice about it is published by parties who sell one of the answers.
That is not an accusation. It is a description of the market. The technical literature on access-system retrofit is dominated by equipment manufacturers, installers, and service providers, and their material is often competent and informative. But a supplier’s analysis of whether to retrofit or replace is also a proposal, and a service provider’s condition report on a system is also a statement about the future of its own contract. The owner entering a retrofit decision should understand from the outset that the information environment is structured this way, because the structure of the information environment is the first thing the decision has to survive.
The first installation was run by builders; the second is run by the owner
When the system now being retired was first installed, it arrived inside a construction project. There was a design team, a general contractor, a commissioning process of some kind, and — at least nominally — an architecture of professional responsibility surrounding the work. The owner, in many cases, never made a single technical decision about the system; it came with the building.
The retrofit inverts this completely. There is no project team unless the owner assembles one. The building is occupied and operating, which constrains every method, sequence, and crane pick. The original supplier may have been acquired, exited the market, or ceased to exist; the original installer’s records may be unreachable; the institutional memory of how the system was specified and accepted may have left the organization. The documentation the owner inherited may be incomplete, may no longer correspond to the installed condition, or may not establish what happened after original acceptance. The retrofit decision is therefore made under exactly the conditions an engineering decision should not be made under: uncertain records, an operating asset, and advisors whose commercial interest runs through the outcome.
This is why the sequencing principle matters more in retrofit than anywhere else in the lifecycle: the engineering case precedes the engineering engagement. A defensible specification, refurbishment decision, or retrofit-versus-replacement comparison requires first establishing what the system actually is and what it actually needs — as a matter of documented engineering fact, not as a matter of what the most recent service report asserts. An owner who solicits retrofit bids before establishing that foundation is not procuring a solution; the owner is asking bidders to define the problem they will then be paid to solve.
What actually drives the decision
Stripped of sales framing, the refurbish-retrofit-replace decision turns on a small number of engineering questions. The first is the condition of what cannot economically be replaced: the structural frame, the track and its fixings, the building interfaces. Where the structural spine of the system remains sound, industry practice regularly retains it — track reuse under a new machine is an established approach — and the retrofit replaces the elements that age fastest: drives, hoists, electrical systems, controls, safety devices, and the cradle. Where the structure itself is compromised, or where the original system was never adequate to the façade it serves, refurbishment spends capital preserving a defect, and replacement is the honest answer.
The second driver is obsolescence, which is not the same as wear. A drive that functions today but whose manufacturer no longer exists, whose spare parts are no longer produced, and whose control logic no one currently in business can service, is a system whose next failure has no repair path. Parts unavailability converts minor failures into extended outages, and extended outages on access equipment cascade into deferred façade maintenance, deferred inspections, and the quiet workarounds that follow. Obsolescence risk is invisible in a functional test and fully visible in an engineering review — which is one reason the two should never be confused.
The third driver is regulatory drift. One example illustrates how obligations can change during the life of an installed system: OSHA’s general-industry requirements for rope descent systems include specific building-owner obligations concerning the identification, inspection, testing, certification, maintenance, and written confirmation of anchorages before they are used for rope descent. Those requirements apply to a defined use and should not be generalized to every access or fall-protection anchorage. The broader retrofit point is simpler: the framework applicable when a system was installed cannot be assumed to be the complete framework governing the work contemplated today. Suspended-access equipment standards, fall-protection codes, and the machinery frameworks under which equipment is placed on the market have all been revised over the service life of the systems now reaching retrofit age, and the applicable requirements must be established for the particular system, scope, jurisdiction, and use before the retrofit basis is set.
The fourth driver is the one owners most often discover late: what has been done to the system since installation. Components replaced over the years, controls modified, anchor points added during reroofing, capacity placards that may no longer match the installed configuration. An undocumented modification is not necessarily a defect — the work may have been perfectly engineered and the records simply lost. What an undocumented modification creates is a question about correspondence with the system’s established engineering basis, and that question stands open until the correspondence can be demonstrated. Unknown is not the same as wrong; it is the condition that must be resolved before the retrofit inherits it. The survey of the system as it exists — not as it was drawn — is the foundation document of the entire retrofit.
There is a fifth driver, easy to miss because it produces no failure at all: systems that have quietly fallen out of use. A permanent system can be physically present, nominally maintained, and simply no longer part of how work at height is actually performed on the asset — because the reach was never right, because a component stopped being trusted, because work practices changed, because contractors bring their own means of access, or because something was tagged out years ago and the institutional memory of why has left the organization. I have walked assets where the permanent system sat parked and maintained while the day’s work at height was done from equipment brought in through the loading dock. Non-use is information. It does not establish deficiency; it establishes a question worth answering before capital is committed: why did the operating practice move away from the system the asset possesses? A retrofit scoped without answering that question risks rebuilding, at considerable cost, a system the work will continue to route around.
The conflict structure, and the contract structure that answers it
The retrofit market’s structural condition — that advice, supply, installation, and subsequent service frequently flow through the same commercial channel — is not resolved by anyone’s good intentions. It is resolved, where it is resolved, by contract structure. One way to address the conflict structurally is to separate the engineering authority from the supply chain: the party that writes the specification, qualifies the bidders, oversees manufacture and installation, and conducts acceptance testing holds no commercial position in which equipment is selected or who installs it. The asset owner contracts directly with the equipment supplier, and directly with a qualified installer, under separate contracts — which also produces a clean warranty architecture, with equipment warranty running supplier-to-owner, workmanship warranty running installer-to-owner, and engineering responsibility standing apart from both.
The practical consequence of this structure is that the engineering recommendation can be trusted for a structural reason rather than a reputational one: the party making it has nothing to sell except the judgment itself. An owner does not need to adopt any particular firm’s model to apply the principle. The test is simple and worth applying to any retrofit engagement: does the party defining what should be bought stand to benefit from what is bought? Where the answer is yes, the owner should distinguish independent engineering judgment from technically sophisticated sales advice — the two can look alike on paper, and they are not the same thing.
What the retrofit must not inherit
The systems now being retired can carry, in their documentation gaps and acceptance histories, the consequences of conditions established during the first installation: specifications effectively written by the winning bidder; factory and site acceptance testing compressed under schedule pressure or skipped; equipment placed into beneficial use before acceptance completed, with no condition baseline and no record of which open items belonged to whom; turnover packages that never fully arrived. I have been asked, years into a system’s service life, for records that the file makes clear were never created. The retrofit is the owner’s one opportunity in a generation to refuse that inheritance.
Acceptance deserves particular attention, because it is where the owner’s exposure peaks. The point of acceptance is where a system passes from supplied to owned. Schedule pressure to use equipment before acceptance is complete is normal and often legitimate; what it obscures, unless someone deliberately maintains it, is the boundary — which conditions were accepted, which remain open, and which party carries each. A documented acceptance record protects every party whose work was sound, because work correctly performed cannot later be attributed elsewhere; its absence exposes everyone, and the owner most of all. The retrofit should therefore be scoped from the outset to end in a record: specifications, submittal reviews, factory and site acceptance test reports, commissioning documentation, and as-builts — the baseline file that may be incomplete or absent from the first installation, held this time by the owner as the asset’s engineering record. An owner who finishes a retrofit holding that file has purchased something beyond a machine: the owner has purchased the ability to answer, for decades to come, the questions this series has shown owners struggling to answer about the installation before it.
The decision framework, in order
Assembled, the sequence is short and its order is the point. First, the engineering case: an independent condition and configuration review of the system as it exists, against its documentation and against the current regulatory framework — completed before any procurement conversation begins. Second, the decision, made against that case: refurbish, retrofit, or replace, with the structural spine, obsolescence, regulatory drift, modification history, and patterns of actual use each answered rather than assumed. Third, the specification, written from the engineering case by a party outside the supply chain. Fourth, owner-direct procurement, with suppliers and installers qualified against engineering criteria and contracted directly to the owner. Fifth, oversight that runs through manufacture, installation, and acceptance to closeout — ending in the owner’s record.
None of this is exotic. It is simply the discipline of procuring an engineered system as engineering rather than as equipment. Whether a given retrofit is procured that way is a choice the owner makes at the outset — before the first bid is solicited — and it is the choice from which everything else in this article follows.
Rauch Safety & Engineering provides the engineering instruments the retrofit decision runs on — the independent engineering case ahead of procurement, specifications and supplier qualification under the owner-direct model, oversight through manufacture and installation, factory and site acceptance testing, and the closeout engineering record delivered to the owner. For systems in service, the engineering case is established through the Installed Systems Engineering Review™. RSE does not sell equipment, perform installation or service work, or compete with the parties who do. This article is a general discussion of engineering practice; the allocation of costs and obligations among parties is a contractual and legal matter on which it offers no opinion.