Structural Steel

Procedure qualification for robotic structural-steel welding

How to connect the governing specification, WPS, qualification evidence, robot program and operator responsibilities before production welding.

Procedure qualification for robotic structural-steel welding — engineering review illustration
TitanWeld editorial reference. Schematics explain review relationships and do not prescribe welding parameters.

At a glance

Keep the WPS, qualification evidence and robot program as distinct controlled records. Check their applicable material, joint and process ranges, then agree the evidence and change controls required for production release.

The robot changes delivery, not the need for a defined procedure

A robot can execute a reviewed welding path consistently, but the path does not define all the conditions needed for an acceptable structural weld. Material, joint preparation, consumables, welding position, process variables and inspection requirements still need a controlled basis. The practical task is to connect the robot's operation to that basis without assuming that a successful demonstration qualifies every later job.

Begin with the governing project requirements. AWS's D1 committee currently lists AWS D1.1/D1.1M:2025-AMD1 for structural welding of commonly used carbon and low-alloy constructional steels. That published scope is a reference, not a decision that the latest listed edition governs an existing contract. [1] Confirm the code, edition, amendments and project supplements with the responsible parties.

This article is an engineering planning guide. It does not select a qualification route, prescribe a test coupon or provide welding parameters. Those decisions require the applicable controlled requirements and competent review. Its purpose is to make the evidence chain understandable before equipment selection, trials and production release become entangled.

Keep four documents and decisions distinct

The WPS describes the process conditions authorized for the relevant work. A procedure qualification record documents the evidence supporting a qualification route and its applicable range. The robot program defines motion and task logic, including the relationship to selected process settings. Operator or setter qualification concerns the personnel role defined by the applicable requirements.

ISO 15609-1:2019 addresses WPS content for arc welding, while ISO 15614-1:2017 addresses procedure testing for specified steel and nickel applications. [2] [3] These documents serve different purposes. Neither is simply a file name for a robot job, and a record of a completed weld path is not automatically a qualification record.

Use identifiers that connect these items without merging them. A production job should reference the applicable WPS revision, and the WPS should have a documented basis. Record the relevant robot and power-source configuration separately. This permits a reviewer to ask what changed without treating every software edit as a new welding procedure or overlooking a process change because the path file name stayed the same.

Project specification leads to qualification route, evidence, released WPS and production job
The required relationships depend on the governing code and project specification. Original TitanWeld diagram; explanatory, not an approved procedure.

Select the route before preparing the demonstration

Qualification and approval routes depend on the applicable code and application. Some circumstances permit defined prequalified or other accepted routes; others require procedure testing. Do not assume a route from the welding process name or from the fact that the equipment has been used elsewhere. Ask the welding engineer to identify the basis and the conditions that must be satisfied.

ISO 15614-1:2017 describes two levels of procedure testing with different testing extent and qualification ranges. [3] If that standard applies, the selected level and any contractual requirements need to be resolved before planning the test. The standard's public scope page does not replace the full text, amendments or application-specific requirements.

TWI explains the relationship between a preliminary procedure, supporting test evidence and a released procedure. [4] In project planning, this means defining the intended production scope first, then arranging appropriate evidence. A test chosen only because it is convenient to weld may leave important production conditions outside the resulting scope. Make those conditions visible before spending effort on a demonstration.

Build a production-scope matrix

List the intended base materials, thicknesses, joint configurations, welding positions, process variants, consumables and other variables relevant to the governing requirements. Link each product family to the proposed WPS. Have the responsible welding engineer compare the production scope with the qualification evidence and identify uncovered conditions.

The matrix should distinguish actual production needs from optional future work. If a planned cell may later weld another material or joint family, record it as a separate requirement awaiting review. Do not extend a current qualification claim through an open-ended phrase such as all structural steel. The useful output is a defined range with an explicit boundary.

Use a representative connection to test the matrix. Ask which WPS covers it, which record supports that WPS, which thickness and position entries apply, and what inspection is required. If the answers rely on verbal assumptions, close those gaps before transferring the task into an automated program. This exercise also helps purchasing teams understand why seemingly similar parts may require different development or qualification work.

Connect the WPS to controller settings and motion

Map the approved procedure variables to the actual equipment controls. Identify which values are entered directly, which are selected through a power-source program and which depend on motion or tool geometry. Confirm the interpretation with the equipment documentation. A displayed setting is useful only when the team understands what it represents in the configured process.

Keep the program revision and procedure revision visible together. Review travel direction, position, starts, stops and any planned multipass sequence in relation to the WPS. Do not assume that matching one nominal current value reproduces the whole qualified condition. Equally, do not invent a universal rule about which program edits always require requalification; the governing requirements determine that.

Document authority to change process settings. Operators, setters, programmers and welding engineers may have different roles. The agreed controls should make the current authorized state identifiable and preserve a record of changes. This is practical quality management for an automated task: the process definition remains readable even when several machines, shifts or similar product variants share the same cell.

A change is identified, checked against scope, reviewed and released before use
Change review separates motion edits, process changes and qualification consequences. Original TitanWeld diagram; explanatory, not an approved procedure.

Treat personnel competence as its own requirement

Automation changes the personnel tasks but does not remove them. Staff may prepare models, verify fit-up, select jobs, set welding conditions, assess abnormal behavior or carry out recovery. Identify those roles and the competence required for each. A person trained to load a part is not automatically authorized to revise a welding procedure.

ISO 14732:2025 concerns qualification testing of welding operators and weld setters for mechanized and automatic welding of metallic materials. [5] Where invoked, review its applicability to the actual roles and the project. Do not substitute a general machine-training certificate for a qualification requirement, or assume that a manual welder's credential automatically covers every automated-welding responsibility.

Prepare a role matrix as part of commissioning. State who verifies the job, who may alter a process setting, who reviews an exception and who releases a repaired weld. Pair training with the actual equipment and controlled procedures. The outcome should be a usable division of responsibility, so the team knows how to act when production differs from the approved trial.

Plan trials with traceable inputs and meaningful inspection

For each required trial, identify the material, preparation, consumables, equipment configuration and applicable procedure. Record the actual conditions and retain the test and inspection evidence required by the governing route. Agree witness and examiner responsibilities before the work begins where they are required by the project.

Keep process development separate from the qualification record. Development may involve unsuccessful settings and exploratory samples. That work can be valuable, but the final supporting record must identify the conditions and evidence that form the accepted basis. Avoid combining photographs from one trial, parameter logs from another and inspection results from a third without clear traceability.

For a robot application, preserve the associated path and setup revisions as contextual evidence. They help explain the demonstration and support later reproduction. Their presence does not change the qualification rules, but their absence can make a technically successful trial difficult to repeat. Record the fixture and physical presentation because they influence how the production task is actually carried out.

Review changes before transferring the job to another condition

Changes can arise through material substitution, revised joint details, consumable changes, a new position or altered process controls. Identify the change, compare it with the applicable procedure and qualification range, and have the responsible party decide the necessary action. Some changes may be covered; others may require additional review, tests or qualification. The exact consequence is code- and project-dependent.

Do the same when transferring work to another cell. Similar equipment names do not by themselves prove identical process delivery. Check the actual configuration, settings, motion, tool and production conditions. Preserve the record of the transfer review and its required verification. Do not describe a transferred program as qualified solely because it ran successfully on another machine.

Where the drawing changes, connect the revised joint to the procedure matrix before updating the robot route. This keeps design, welding and automation decisions aligned. It also prevents a local programming adjustment from becoming an undocumented response to a substantive manufacturing change.

Audit one job before release

Select a real production joint and follow its references without informal explanations. Start at the drawing, find the WPS, locate its supporting basis and compare the relevant production condition with the documented scope. Then inspect the robot job and equipment configuration that will deliver the weld. Record any broken link as an open item.

Different teams may use different identifiers for the same joint. The modeller may use an assembly mark, the programmer a task number and the inspector a drawing location. Provide a mapping so all three can identify the same physical weld. This is an information-control measure, not an additional qualification rule.

Complete the audit with the people who will operate and inspect the task. They should be able to find current instructions and recognize a condition requiring review. The exercise makes procedure control practical on the shop floor and helps a sound qualification package remain connected to actual production. Repeat the relevant parts of the audit after an approved change, and preserve the record of what was checked. The resulting release should identify an authorized combination of documents and configuration rather than relying on a statement that the job was previously approved.

Specify a release package that production can use

Before production release, assemble the applicable project requirements, WPS revisions, supporting qualification evidence, job and equipment references, personnel responsibilities and inspection plan. Identify the limits of the approved scope and the actions required when a part falls outside it. The package should be controlled, accessible and understandable to the people who use it.

Ask the supplier and fabrication team to walk through one representative joint from drawing to released job. They should be able to locate its procedure, identify the supporting basis, show the approved settings relationship and explain the inspection outcome required. This is a practical acceptance exercise that exposes missing links without relying on broad statements about robot weld quality.

A qualified procedure is valuable because it defines an evidenced process within an applicable scope. The robotic system then needs to execute the authorized task under controlled conditions, while inspection determines the required product acceptance. Keeping these responsibilities connected and distinct gives structural-steel automation a sounder foundation than treating a successful machine cycle as the entire welding-quality argument.

Project review checklist

  • Identify the governing contract and welding qualification requirements.
  • Keep the WPS, qualification record and robot program as distinct records.
  • Confirm the applicable material, joint and process range with responsible personnel.
  • Control program and process changes against the approved procedure.
  • Agree the evidence required before releasing production work.

Project discussion

Start with your workpiece.

Share the drawings, weld details and workshop conditions to define the engineering review.

Talk with an engineer

Privacy settings

Choose whether Google Maps and YouTube players may load.

Necessary website operation

Required to deliver pages, remember this choice and keep forms usable.