Can One Project Use Multiple Structural Steel Fabricators?

A project can use multiple structural steel fabricators, but only when the work can be divided without dividing accountability. Before awarding parallel packages, define which assemblies each company owns, who controls common detailing and connection rules, where one package physically meets another, and how revisions, inspections, markings and records cross that boundary. Then prove one representative interface before both shops reach full production. If the packages cannot be separated on drawings, in the model, during erection and in the manufacturing data record, a split award may create more schedule risk than capacity. The practical output is a Cross-Fabricator Boundary Schedule tied to one controlled project baseline.

Decide Whether the Project Is Actually Divisible

Do not start with the number of tonnes each shop can accept. Start with the structure and ask whether it contains packages that can be defined, detailed, fabricated, inspected, delivered and erected with a limited number of controlled interfaces.

A clean division usually follows a physical and contractual boundary: separate buildings, independent areas, erection zones, repeated modules, self-contained secondary-steel packages or assemblies connected through deliberately defined field joints. A poor division cuts through shared connections, transfers incomplete design between shops, duplicates member marks or requires one fabricator to infer another's tolerances and production state.

Use a split/no-split gate before tender clarification:

The decision is not simply “two suppliers are faster.” Parallel production can increase available capacity, but it also adds handoffs, duplicated approvals and interface exposure. Treat schedule benefit as a project hypothesis to test against package separability, approval workload, material availability, logistics and erection need dates. Do not turn it into a universal promise.

Choose the Sourcing Topology Before Naming Suppliers

“Multiple fabricators” can describe several different arrangements. Choose the topology first because each one creates a different boundary and control burden.

Do not call a second shop a backup if it has not received the relevant drawings, process requirements, qualification scope, material route, inspection plan and transfer records. A company name on a bidder list is not a usable recovery path.

Likewise, do not treat subcontracting as invisible single sourcing. If a contracted structural steel fabrication company sends welding, machining, galvanizing, trial assembly or another controlled activity elsewhere, the project still needs to know how that process is qualified, instructed, traced, inspected and released. The commercial contract may remain with one party, but the production and evidence boundary still exists.

Record the selected topology, the reason for it, the packages it covers and the conditions that would reopen the decision. Examples include a design change that moves a major interface, a facility losing an applicable qualification, a common material source becoming unavailable or the erection sequence changing.

Draw the Cross-Fabricator Boundary

Create a Cross-Fabricator Boundary Schedule before award. Its rows should be physical interfaces and shared controls, not vague work descriptions such as “Building A steel” or “miscellaneous items.”

Every row needs an owner, approving authority, required input, output, due state and change route. Add coordinates or model references where the boundary is geometric. A color on a federated model is useful for orientation, but it is not a contractual scope definition unless it is tied to controlled objects, drawings and registers.

The boundary schedule should reconcile both directions. Select any physical interface and trace its two mating sides to their owners and released documents. Then select any fabricator package and confirm that every supplied item reaches an approved assembly or interface. This catches both gaps and double allocation.

Freeze One Shared Information Baseline

Parallel shops must not develop parallel versions of the project. Establish one shared baseline containing the documents and data that both packages inherit: design drawings, specifications, adopted standards and editions, model coordinates, grid and level conventions, connection philosophy, material rules, tolerances, finishes, identification conventions, ITP principles, document numbering and the approved erection sequence.

ANSI/AISC 303-22 provides a current framework for common understanding in structural-steel contracting. It does not create a universal multi-fabricator procedure, but it reinforces why project documents must make responsibilities and information expectations explicit. The governing contract, design requirements and local rules still control the project.

Build the baseline as a versioned release, not a download folder. Each fabricator should acknowledge which revision it received and which package objects it is allowed to use. Derived outputs—shop drawings, material lists, NC/CNC files, weld maps and packing lists—must remain traceable to that basis.

ISO 19650-2:2018 addresses information-management processes and exchanges during asset delivery and remains current after ISO's 2024 confirmation, although a revision is under development. Use the applicable contract information-management plan to define exchange states, authorization and responsibility; the standard's scope does not make a model fabrication-ready or decide the steel split.

Name one coordination authority for the federated state. That party does not silently assume structural design responsibility; it checks whether issued package information is complete, compatible and at the required status. Define how conflicts are logged, who provides the technical decision and which derived files must be regenerated after approval.

Qualify Each Facility for Its Assigned Package

Qualify the company, facility and order scope separately. A group-level brochure or certificate does not prove that every location, line, process or subcontractor is covered for the proposed package.

AISC's current Certification Program descriptions state that its certification is address-specific and that each facility is certified separately. The current certification framework uses AISC 207-25. Where that scheme is contractually relevant, verify the facility and applicable program at the scheme source. For other countries or schemes, apply the equivalent project-defined verification route rather than substituting the AISC example automatically.

For each proposed fabricator, map the assigned package against:

• legal entity and production location;
• applicable certifications, endorsements and limits;
• material receipt, identification and traceability controls;
• cutting, forming, machining, welding and distortion-control processes needed by the package;
• WPS/PQR and personnel qualification coverage for the actual joints and materials;
• dimensional capacity, inspection capability and calibration route;
• surface-treatment and outsourced-process controls;
• nonconformance, repair, concession and change procedures;
• proposed production, inspection, packing and delivery sequence; and
• the records required for the common MDR.

ISO 3834-2:2021 defines comprehensive quality requirements for fusion welding in workshops and at field installation sites. Its official page shows the edition as published and under systematic review in September 2026. Use the edition adopted by the contract and verify how each welding organization covers the relevant work; do not infer joint acceptance, project certification or capacity from the title alone.

Qualification can therefore produce different decisions for two companies. One may be approved for repetitive secondary members but not a fatigue-sensitive or unusually heavy assembly. Another may have suitable welding scope but lack the necessary coating or dimensional route. Bind every approval to the specific facility, processes, package, conditions and evidence reviewed.

Release One Representative Boundary Before Full Production

The most valuable early check is not two unrelated first articles. It is one representative cross-fabricator boundary that forces the shared rules to work together.

Choose an interface with enough consequence and repetition to expose the coordination method: a field splice, a shared grid line, a transfer assembly, a truss segment joint, a platform connection or a package-to-package erection handoff. The appointed project parties decide whether physical fit-up, survey evidence, digital verification, templates or another method is required.

Use a First-Boundary Release Gate:

1. Both sides reference the same approved design and interface revision.
2. Connection responsibility and design status are explicit.
3. Mating datums, dimensions, holes, tolerances and orientation are reconciled.
4. Materials, welding, fasteners and finish transitions match the controlled basis.
5. Member marks, package codes and erection location agree across drawings, models and lists.
6. Required inspection results and exception closures are available for both sides.
7. The erection and access assumptions are reviewed by the responsible parties.
8. The accepted evidence, limits and any corrective action are recorded before repeat release.

Digital checking can identify model clashes or inconsistent attributes, but it cannot prove every fabricated dimension, material identity, weld condition, coating state or field fit. A physical trial assembly can test selected geometry but may not represent every production lot or erection condition. State exactly what the chosen verification demonstrates and what remains controlled by later inspection.

If the first boundary fails, contain the affected pattern in both packages. The response may require new detail rules, revised drawings, expanded dimensional checks, altered sequence or a different split. Do not repair one pair of parts and continue producing the same error on both sides.

Keep Changes, Marking and Records Whole

A split award remains one project. Run RFIs, design changes, deviations and nonconformances through a common impact route so a decision made for one shop cannot leave the mating package on an obsolete basis.

For each change, record the originating issue, affected design objects, package owners, interface rows, material or work already completed, derived documents, inspection consequences, site and logistics effects, approving authority and effective revision. Require positive acknowledgement from every affected shop before the change is closed. Distribution is not proof of implementation.

Use one project-level identification grammar. A mark should distinguish project, area or erection sequence, fabricator package and unique item without allowing two shops to create the same identity. Keep the approved cross-reference in the model, drawings, bill of materials, material traceability records, inspection reports, packing list and erection documentation. Temporary local shop numbers can exist, but they must map back without ambiguity.

Plan the final evidence as one dossier from the beginning. The project MDR index should show common documents once, fabricator-specific records under each package, and interface records that reconcile both. Preserve superseded and exception history according to the contract; do not merge two PDFs in a way that hides which facility, lot, item or revision each result covers.

The release decision should answer four questions: are both packages complete for the required erection state, are their shared interfaces accepted, are open exceptions visible and authorized, and can the field team trace every delivered item to the current basis? If any answer depends on inference, the split is not yet under control.

Using multiple structural steel fabricators is a sourcing architecture, not a capacity shortcut. It works when the project follows separable packages, maintains one information baseline, qualifies every facility for its actual scope and verifies the first shared boundary early. Where those controls are disproportionate or the interfaces cannot be bounded, retain a single accountable fabrication route or redesign the package split before award.

Related Resources

• Structural Steel Fabricators: Match Evidence to Contract Scope owns the broad supplier-qualification decision.
• Structural Steel Shop Drawings: Release the First Submittal explains drawing information, connection responsibility and revision readiness.
• Vendor Document Requirement List: Freeze Scope Before Award defines deliverables, review purposes and milestone obligations.
• When Does Structural Steel Need Trial Assembly? helps select physical, partial or digital interface verification.
• Steel Structures remains the parent commercial route for structural supply enquiries.

References

• ANSI/AISC 303-22 — Code of Standard Practice for Steel Buildings and Bridges
• AISC — Program Descriptions for Certification
• ISO 3834-2:2021 — Comprehensive quality requirements for fusion welding
• ISO 19650-2:2018 — Information management during the asset delivery phase

Next Step: Issue the Boundary Schedule

Before requesting parallel fabrication proposals, mark the proposed package split on controlled drawings and complete the Cross-Fabricator Boundary Schedule. Include the common baseline, facility-specific qualification scope, representative first-boundary gate, change route, identification grammar and MDR index. Send that bounded package to info@baolaipipes.com through the Steel Structures route. East Baoyu can review the information and structural supply interfaces within an agreed enquiry; design responsibility, package strategy, supplier approval, inspection authority, erection planning and final acceptance remain with the appointed project parties.