By Uwe Janssen · Rauch Safety & Engineering · Las Vegas, Nevada
When a building maintenance unit is purchased from an overseas manufacturer, the owner takes on a set of questions that a domestic purchase poses more gently: distance, which changes what the owner can see and when; a delivery chain, which may place intermediaries between the owner and the works; regime correspondence, where the machine is built to one standard and the asset is governed by another; documentation, which arrives speaking the originating regime’s language; and time, because the machine’s most correctable period is spent an ocean away from the project. The purchase contract assigns the obligations. What strengthens the owner’s position in practice is the procurement structure built around those obligations: verification staged at the works before shipment, documentation specified as a deliverable rather than received as a parcel, and payment milestones aligned to verified acceptance stages so that the owner’s commercial position and the machine’s technical status move together. This article describes that structure.
Distance, and what it does to position
The acceptance article in this series develops the concept that matters here: what verification buys an owner is position — discovery at the works, before shipment, while the machine and the resources needed to investigate and correct a finding remain together. Distance sharpens that concept into procurement architecture. While the machine stands at the manufacturer’s works, examination occurs at the works, correction can be undertaken there, and — where the commercial structure preserves it — remaining payment may still provide leverage. Once the machine ships, the geography of every remaining question changes: examination competes with a construction site, correction involves mobilization across borders, and the parties who built the machine are no longer in the room with it. Nothing about that shift is improper — it is what shipping a machine means. The procurement consequence is simply that the pre-shipment period is particularly valuable, and a procurement structure that spends it — with specified factory acceptance testing, owner representation at the works, and verification of corrections before the machine leaves — is using technical and commercial leverage while both remain comparatively strong. I have represented owners at manufacturers’ works overseas; the structure this article describes is the structure of that work.
The delivery chain
An imported machine may reach the project through a chain: a delivery partner or integrator who purchased the machine from its manufacturer, a contractor who purchased it from the delivery partner, and an owner whose contract may stand at one or two removes from the party who actually built the equipment. Each party in such a chain carries its own obligations. The engineering consequence sits alongside the commercial one: the party contractually answerable to the owner may be neither the designer nor the builder of the machine, and the technical questions an owner needs answered — design basis, test results, component provenance, correction status — originate at the works regardless of where the contract sits. A procurement structure that anticipates this specifies the owner’s technical access directly: the right to attend factory testing, the right to receive manufacturer-level documentation, and the identification of who answers engineering questions at each tier. The first article in this series describes what an owner holds when its information arrives only as representations produced within a chain; the strongest time to establish that line of sight is before the order is placed, while technical access can still be incorporated into the procurement structure.
Two regimes, one purchase
Where the machine is built to EN 1808, a principal European standard for suspended access equipment, and the asset is governed by the US framework, the correspondence between the two is part of what the procurement must deliver — a subject the acceptance article in this series treats in full: the specification approach that cites both regimes and requires application of the more stringent requirement where they differ, the engineering reconciliation that approach requires someone to actually perform, and the value of requiring the stringency determination itself as a documented deliverable. For procurement purposes, one addition belongs here: the stage at which a correspondence question is resolved changes the available response. During design it may be addressed through drawings and specifications; at the works it may require modification or additional verification; after installation the technical and contractual consequences can be substantially more complex. The earlier the correspondence question is assigned, examined, and documented, the more options remain available for resolving it within the procurement process.
Documentation as a deliverable
The documentation that accompanies an imported machine — test certificates, material and component records, load charts, manuals, conformity declarations — may have been produced for the originating regime’s purposes and conventions, sometimes in another language and in other units. The acceptance article describes the acceptance file as the asset’s baseline record; for an imported machine, the procurement structure helps determine whether that baseline arrives usable. A procurement structure that treats documentation as a specified deliverable — named documents, project language and units, content requirements tied to the governing specification, delivery staged with the machine rather than after it — produces a file the owner’s service life can actually run on. One that treats documentation as whatever accompanies the crate produces the condition the first article in this series describes: an owner holding, decades later, whatever survived — except that here the surviving documents may also require translation before they can be read.
Payment milestones as verification gates
Payment structure is a commercial matter, set by the parties and their counsel. From an engineering standpoint, however, payment milestones can create verification gates — explicit moments at which unresolved engineering questions have to be answered before the transaction advances — when they are aligned to defined technical stages. Where milestones are aligned to verified stages — factory acceptance passed, corrections verified, shipment released, site acceptance completed, final acceptance — the owner’s position and the machine’s status move together, and the structure itself creates the occasions on which verification happens: a payment gate is an appointment to examine the machine. Where milestones track dates, the two can diverge, and payment can advance materially ahead of technical closure. And where a technical condition remains unresolved late in the process, the remaining payment structure may materially affect the parties’ commercial position while correction is addressed — which is a further reason the structure deserves design rather than default. How any of this is drafted is for the commercial and legal side of the project; what engineering contributes is the stage definitions themselves — what ‘verified’ means at each gate, examined by whom, against what scope — so that the milestones are tied to events that mean something.
The practical posture for an owner or project manager
The posture assembles what the series has already built, pointed at the purchase. Specify factory and site acceptance testing in the purchase documents, with scope, load cases, safety-device demonstrations, and documentation deliverables named — and owner representation at both. Where the specification requires application of the more stringent of several regimes, require the stringency determination as a documented deliverable. Specify the documentation file — contents, language, units, timing. Establish the owner’s technical access across the delivery chain before the order is placed. Align payment milestones to verified acceptance stages, with engineering defining what each stage verifies. Verify corrections at the works before shipment. And receive the completed file as the asset’s baseline record — a foundation, as this series has described from its first article, for future inspection, service decisions, and engineering questions across the asset’s life. Conditions surfacing in early service, and what the available evidence can establish about their technical origin, are subjects of their own, addressed separately in this series.
Rauch Safety & Engineering provides independent engineering presence through international BMU procurement — specification review, factory and site acceptance testing at manufacturers’ works and on the project, verification of corrections before shipment, and the stage definitions that give payment milestones their engineering content — conducted independently of the equipment supply chain and the contract delivery chain, with the findings and records belonging to the owner. RSE does not sell equipment, perform service work, or compete with the parties who do. This article is a general discussion of procurement-stage engineering practice; the drafting of contracts, payment terms, and warranty provisions is a legal and commercial matter on which it offers no opinion.