Pot vs Spherical Bearings: What Information Is Needed to Compare Them?

The comparison begins with the project condition

A pot-versus-spherical discussion is most useful when it starts with the conditions that the project needs the support to address. Both families are commonly considered where a bearing arrangement needs a defined combination of vertical support, rotation, translation or restraint. The correct family or configuration is not determined by a slogan such as “high load” or “large rotation.” It depends on the approved action envelope, the rotation and movement directions, the restraint strategy, the available support geometry, the interface and construction constraints, the service environment and the governing requirements.

The practical question is therefore not “which bearing is better?” It is “what information is needed to compare two technically complete proposals?” An inquiry should let each supplier work from the same bearing schedule, axes, actions and drawings. That makes it possible to identify different assumptions rather than treating different product mechanisms as automatically comparable. Final selection must still follow the project engineer’s approved design basis and the controlled documents for the proposed configuration.

Understand the two broad mechanisms without turning them into claims

At a conceptual level, a pot bearing is commonly described through rotation accommodated by a confined elastomeric element within a steel housing. Any project-specific translation or restraint is addressed through the selected sliding and guidance arrangement. A spherical bearing is commonly described through rotation at a curved interface, with translation and restraint addressed by the relevant project configuration. These descriptions help a buyer understand why the two families may raise different interface and documentation questions. They do not define an allowable capacity, movement, angle, material, durability outcome or code compliance.

In both cases, fixed, guided and free are configuration behaviours rather than complete product specifications. A guided condition must identify the permitted direction and restrained direction. A free condition still needs a declared movement envelope and interface context. A fixed condition needs a defined horizontal-action path. A comparison is only useful if each proposal explains how the requested movement and restraint intent is being interpreted. Do not assume a standard family label has the same implication across different drawings, suppliers or project stages.

For a related project route, review Pot Bearings or Spherical Bearings in the context of Highway Bridges.

State the action and movement envelope first

Start with vertical reactions and their basis, but keep the rest of the action envelope beside them. The relevant combination may include longitudinal and transverse horizontal actions, minimum reaction, uplift, seismic or wind conditions, braking, settlement or construction-stage actions. Where the project has distinct service and ultimate states, identify them clearly. The purpose is to ensure that two technical responses address the same governing conditions.

Then state translation and rotation by the project’s local axes. Describe the expected movement direction, total range, reversals and irreversible effects if they are known. Describe rotations about the relevant axes and whether rotation and translation may occur together. A comparison should also identify whether an effect belongs to the completed structure, a temporary construction state, a launching stage, a jacking operation or a replacement sequence. A product family can never replace this project information. It is the input that allows a mechanism to be developed into a real configuration.

Make the restraint strategy visible

A bridge uses a system of support functions. The location of a fixed point, the orientation of guides and the free-movement locations are all part of the force path. When comparing pot and spherical proposals, give each bidder the same bearing layout with identifiers, local axes and arrows. State whether the bearing is meant to be fixed, guided or free, and identify whether separate keys, pins, stops or structural details take some of the horizontal action.

This step is important because a guided bearing is not defined by a generic word alone. The guide direction must be aligned with the drawing, especially on curved or skewed structures. Likewise, a free sliding condition does not eliminate the need to discuss travel allowance, support clearance, protection and inspection access. A fixed location does not automatically identify how every horizontal action reaches the foundation. Keep the restraint strategy tied to the bridge drawing so the technical comparison is about equivalent intent rather than verbal interpretations.

Compare the support envelope and connection questions

The available footprint, total height, support levels, top and bottom connection concept, anchor layout, clearances, edge distances, adjacent reinforcement, access and tolerance requirements can materially affect a bearing proposal. A family that appears suitable from the action schedule may need a different interface once the real support geometry is considered. Include the current support details and state whether the drawings are preliminary, issued for coordination or approved for construction.

Replacement work requires another layer of information. Existing bearing identification, measured dimensions, condition images, jacking/temporary-works questions, removal route, traffic or rail constraints and available work windows should be visible in the comparison request. These topics do not create an instruction for field work. They make the interface and programme risks visible before a product proposal is treated as a complete solution. The purchaser can then distinguish product scope from site, temporary works and approval responsibilities.

Ask what is included in each proposal

Two comparable mechanisms can still lead to unlike commercial scope. Ask each supplier to state the bearing configuration, upper and lower interfaces, connection plates, anchors, guides or sliding components, protection, markings, drawings, material/inspection records, testing or witness scope, packaging, shipping basis and handover documents. The relevant answer will be project-specific, but the categories should be visible in every comparison.

Keep documents separated by role. A family overview aids orientation. A data sheet may support screening and design development. A component or interface drawing supports coordination. A specification or quality document defines required procurement evidence. A handling or installation document, where controlled and applicable, belongs to the exact assembly and project stage. Do not use a brochure image or a generic table as a substitute for a drawing or project-approved calculation. A clear document list makes it possible to compare scope, revision and responsibility without inventing a compliance claim.

Use a common comparison sheet

A good comparison sheet has one column for each proposal and one row for each project input. Include the action basis, movement and rotation axes, function, guide direction, support envelope, connection responsibility, environment, special conditions, inspection/documents, quantity, delivery sequence and exclusions. Then identify what is confirmed, assumed or still open. The outcome is not an automated recommendation. It is a controlled list of the questions that must be resolved before a project team can judge whether offers are equivalent.

If a proposal uses a different assumption, bring that difference back to the designer or responsible reviewer. For example, a different function, connection boundary, document scope or project-stage condition should be confirmed against the bearing schedule and support detail. This avoids a common procurement error: treating an apparent technical difference as a price difference when it is actually a change in scope or design basis.

When to ask for further technical review

Request a deeper review when the brief includes concurrent movement and rotation, a constrained support envelope, unusual horizontal or uplift conditions, significant temporary works questions, difficult access, a replacement interface, demanding exposure, unclear restraint responsibility or incomplete project data. The purpose of further review is to define the missing information and document route, not to publish a universal answer.

For an RFQ, send the bearing schedule, reaction and movement data, support drawings, local axes, available geometry, environment/specification requirements, quantity, programme and current unknowns. Ask the supplier to state the configuration assumptions and supply boundary. That process gives pot and spherical bearing proposals a fair technical basis for comparison while retaining project-specific engineering verification where it belongs.