Can a single PQR test coupon qualify a WPS under both AWS D1.1 and ASME IX?

A shared test coupon that satisfies both codes' mechanical test requirements simultaneously is technically possible. However, the essential variable lists differ, so separate WPS documents must be generated for each code. Most shops maintain separate PQR records formatted to each code's requirements, even when a single welded coupon produced the test data.

Does AWS D1.1 recognize ASME IX welder performance qualifications?

No. AWS D1.1 does not automatically accept ASME IX welder qualifications. Each code has its own essential variables for WPQ, and the test positions, coupon geometries, and qualification ranges differ. A welder must hold separate qualifications under each code unless the contract or AHJ explicitly accepts cross-code portability, which is uncommon.

What cross-code error do auditors catch most often in multi-code fab shops?

Using a WPS qualified under one code on a job governed by another. This happens most during production rushes when welders grab the nearest available procedure. A WPS numbering scheme that encodes the governing code—such as D1-SMAW-001 vs IX-SMAW-001—eliminates most confusion at the point of use.

Can API 1104 procedures be used on structural steel governed by AWS D1.1?

No. API 1104 governs pipeline girth and seam welds in carbon and low-alloy steel pipe. It is not a recognized alternative to AWS D1.1 qualification for structural connections, even when the base metal and filler are identical. Always apply the code the governing contract, AHJ, or design specification requires.

Multi-Code WPS Management: D1.1, ASME IX, and API 1104

How fab shops running AWS D1.1, ASME IX, and API 1104 simultaneously can organize their WPS libraries, avoid cross-code qualification gaps, and stay audit-ready.

Fabrication shops that serve multiple markets—structural steel buildings, pressure equipment, and pipeline tie-ins—routinely work under three distinct welding codes on the same shop floor. AWS D1.1, ASME Section IX, and API 1104 each define their own procedure qualification requirements, essential variables, and acceptable qualification ranges. None recognizes either of the others as an automatic substitute.

The documentation challenge grows with every new project scope. A shop maintaining 40 WPS documents under one code easily reaches 120 when all three codes are active. The complexity is manageable, but only with deliberate library structure and clear welder assignment practices.

What Each Code Covers

AWS D1.1 governs fusion welding of structural steel in buildings, bridges, and related structures. It is the default code for AISC-certified fabricators and is referenced by IBC for special inspections. Essential variables are listed in Table 6.6 for the primary arc welding processes, and prequalified WPS are available under Clause 5.

ASME Section IX governs welding of pressure-containing equipment—pressure vessels, boilers, and piping systems covered by ASME B31.1, B31.3, and similar standards. Its P-number base metal grouping and F-number filler classification are unique to ASME IX and do not correspond directly to AWS D1.1 base metal and filler designations.

API 1104 governs pipeline girth and branch connection welds for oil and gas transmission systems. It is independent of both AWS D1.1 and ASME IX, with its own coupon requirements, destructive test acceptance criteria, and production inspection protocols.

A WPS qualified under one code is valid only for work governed by that code. This applies equally to the procedure itself and to the welder qualification records supporting it.

Essential Variable Differences That Create Gaps

The three codes define essential variables differently, which means the same production change can simultaneously be:

An essential variable under AWS D1.1 requiring immediate requalification
A supplementary essential variable under ASME IX triggered only when CVN toughness is contractually required
Not an essential variable under API 1104 at all

Common examples of this divergence include preheat minimums, heat input ranges, and base metal group changes. AWS D1.1 Table 6.6 and Table 6.8 (CVN supplementary essential variables) define these for structural welding; ASME IX QW-250 series covers the same variables with different tolerance bands; API 1104 uses its own heat input qualification range calculated from the test coupon itself.

For a direct technical comparison of the two most commonly confused codes, see AWS D1.1 vs ASME Section IX: Key Differences and API 1104 vs AWS D1.1 WPS Differences.

Building a Multi-Code WPS Library

Organizing a WPS library that spans codes requires clarity at two levels: document identification and procedure content.

Document identification. Every WPS must state its governing code on the face of the document. A numbering scheme that encodes the code prefix prevents job-site confusion:

D1-SMAW-0001 — AWS D1.1, SMAW
IX-GMAW-0001 — ASME Section IX, GMAW
API-FCAW-0001 — API 1104, FCAW

Purely numeric systems (WPS-001, WPS-002) require staff to read the governing standard field in the document body—a step routinely skipped under schedule pressure. The code prefix makes the right procedure self-evident at the point of use.

Separate PQR records. Even when a single test coupon produced data for both codes, maintain separate PQR documents formatted to each code's required content. An AWS D1.1 PQR and an ASME IX QW-483-formatted PQR serve different auditors and reference different acceptance criteria tables. Combining them into one record creates ambiguity that neither auditor will accept.

Procedure cross-reference log. Maintain a master log mapping every WPS number to its supporting PQR(s) and governing code. As the library grows, this log becomes the primary audit navigation tool.

For practical guidance on dual-qualification testing programs, see Dual Qualification PQR: AWS D1.1 and ASME IX.

Welder Qualification Across Codes

No code automatically accepts another code's welder performance qualifications (WPQ). This is the most operationally disruptive aspect of multi-code shops.

AWS D1.1 WPQ under Clause 6.5 is position- and process-specific. Qualification coverage for groove welds in non-tubular connections differs from coverage for tubular connections. A welder qualified for structural plate work is not automatically qualified for structural pipe or HSS connections under Clause 9 without separate consideration of the qualification position and essential variable coverage.

ASME IX WPQ under QW-300 series defines ranges differently—particularly for weld deposit thickness, base metal P-number coverage, and position coverage. An ASME IX 6G pipe test provides broad coverage within the ASME IX framework but does not carry over to AWS D1.1 structural qualification without a separate review of AWS D1.1's qualification position tables.

API 1104 WPQ is pipeline-specific. Qualification on pipe sizes and wall thicknesses does not map directly to plate thickness ranges used under AWS D1.1 or ASME IX.

The practical result: a shop running all three codes typically needs welders holding three sets of WPQ records. Continuity tracking is also code-specific. A welder maintaining active production under ASME IX may still lapse under AWS D1.1's Clause 6.4.1 six-month rule if no D1.1-governed work was performed in that period. See AWS D1.1 Welder Continuity: The 6-Month Rule for the specific continuity requirements.

Document Control Practices That Scale

As the WPS library grows, document control discipline determines whether the program survives an audit intact. Three practices matter most:

Supersession tracking. Every WPS revision must identify the previous revision it supersedes. In multi-code libraries, the risk that an outdated revision stays in service alongside an updated one is amplified because each code's procedures move independently.

Job packet assembly. For each project, assemble a packet containing only WPS documents valid under the governing code for that specific scope. A shared digital folder containing the complete library without job-specific filtering is a documented audit failure pattern—welders access convenient procedures, not necessarily the correct ones.

NDE acceptance criteria cross-check. NDE is one of the areas where code-specific acceptance criteria diverge most sharply. The visual acceptance criteria, UT rejection levels, and RT density requirements under AWS D1.1 are not the same as ASME VIII Appendix 4 or API 1104 Section 9. The NDE procedure governing each specific weld must reference the inspection code that governs that weld's qualification, not the most recently used standard.

For more on version control in a growing WPS library, see WPS Revision Control Best Practices and WPS Numbering Scheme Best Practices.

What Auditors Check in Multi-Code Shops

When an AISC auditor, National Board inspector, or pipeline owner representative audits a multi-code shop, they verify that the WPS presented for a specific weld is valid under the governing code for that weld—not simply that a WPS with a plausible description exists. Common findings include:

WPS references a PQR qualified under a different code's requirements
Welder's WPQ covers only one code but was used on production governed by another
Heat input range stated on the WPS was calculated using one code's formula and applied to work governed by a code with different range criteria
NDE acceptance criteria from one code's table applied to inspection governed by a different code

An EPC contractor managing welding across multiple codes and fabrication facilities faces compounded risk from these gaps. See EPC Contractor WPS Management Across Multiple Fab Shops for multi-site considerations.

Building the Program

Running a multi-code WPS program is achievable for any size shop, but it requires structure that does not emerge naturally from general welding management practice. The foundation is code-identified document numbering, code-segregated welder qualification records, separate PQR documentation per code even when coupon sharing occurs, and job-specific packet assembly.

Shops looking to centralize multi-code WPS management in a single system can view our pricing for AWS D1.1 procedure management with multi-code tracking.

Rule library based on AWS D1.1:2025; verify against your governing edition (the AHJ or contract may specify 2020 or earlier).