Equipment Capability, WPS/WPQR and Production Acceptance: Keep the Evidence Distinct

Three questions need three kinds of evidence

A robotic welding project can show that equipment performs a defined task, that a welding procedure has supporting qualification evidence, and that a particular production weld satisfies its acceptance requirements. These are related questions, but they are not interchangeable. A shipyard should establish which evidence answers each question before treating a demonstration, certificate or process database as authorization for production.

The distinction is especially important in custom automation. TitanWeld's marine brief describes double-sided, double-arc fillets, two arms per basic unit and a current ceiling of four units and eight arms. It is a highly non-standard project with no off-the-shelf single machine. The brief does not itself establish equipment certification, WPS approval, WPQR coverage or acceptance of a vessel's production welds.

This article proposes a document and trial structure for project discussions. The applicable classification requirements, contract, drawings and inspection plan must determine the actual approval route. External references explain the categories and current publication context; they are not evidence that a named authority has reviewed, approved or certified the TitanWeld concept.

Read the CCS guide within its published scope

CCS published its 2025 guide for welding inspection in ship intelligent manufacturing with an effective date of 1 January 2026. Its announcement describes intelligent-level classification, equipment capability certification tests and welding-process database approval. [1] Those stated subjects make the guide relevant to an intelligent-welding equipment discussion, while also showing why a buyer must ask what a specific approval actually covers.

Obtain the applicable guide and project requirements through the responsible classification and quality channels. Identify the equipment configuration, function, test conditions and limitations described in any evidence offered. A guide's existence is not a certificate, and a supplier's use of similar terminology is not proof that its system has completed the relevant assessment.

For procurement, create an evidence register with a separate row for each proposed approval or capability claim. Record the issuing body, document identity, scope, configuration and current status where evidence exists. Where it does not exist, use a clear proposed or pending status. This gives the buyer a concrete question to resolve without overstating either a supplier's capability or the meaning of a general published guide.

Keep WPS instructions and WPQR evidence distinct

A WPS supplies controlled welding instructions. The supporting procedure qualification record documents the relevant qualification evidence and its scope under the selected requirements. TWI explains the relationship between the WPS and the records of welding and testing that support procedure approval. [2] A robot recipe can implement selected instructions, but its program name does not replace that document relationship.

Map each proposed weld family to the WPS and supporting qualification evidence that the project intends to use. Include the material, joint, process and other applicable scope variables through the controlled documents. Do not invent a universal transfer rule from a successful trial on another component. The responsible welding function must determine whether the actual production task is covered and what additional evidence is required.

Treat process-library entries carefully. A database may contain useful parameter sets, development trials or approved procedures, but those categories have different meanings. Ask how an entry's status is identified and how its permitted use is controlled. A convenient software selection should not cause an unqualified development recipe to appear equivalent to a production instruction approved for the specific project.

Check the applicable IACS revision and implementation context

The IACS W28 publication listing identifies Revision 2 as the current version and states that Revision 3 comes into force on 1 January 2027. This article was prepared on 20 September 2026. [3] The listing concerns welding procedure qualification tests for steels used in hull construction and marine structures; it is not a generic robot-equipment approval document.

A project extending across the implementation date should establish the applicable requirements with its classification and contracting parties. Record the adopted revision and any project-specific direction in the compliance register. Do not silently use the newest available document merely because it appears online, and do not assume that an older quotation establishes the rules for every later production stage.

Keep revision control visible in supplier submissions. A test plan, WPS register and acceptance report should identify their governing requirements consistently. If the applicable basis changes, assess the documents and tests affected by that change. The necessary action may differ between equipment functions, procedure qualification and production inspection; grouping them under one undefined certification milestone conceals that work.

Define equipment capability tests around stated functions

An equipment test should identify the function being examined, its input condition, the expected response and the evidence that demonstrates it. Examples for review include seam identification, registration, path execution, paired operation, interruption handling and record retention. These are proposed subjects for a project test plan, not a claim that a particular guide mandates this exact list.

State the tested configuration: robot and external axes, torch package, sensor arrangement, software revision, fixture and selected welding equipment. A result from one configuration should not be transferred automatically to another. If a later design change affects the demonstrated function, document the engineering review and any retest required under the project's agreed process.

Separate functional outcomes from weld-quality outcomes. The equipment may correctly detect a seam and execute a path while the selected procedure still needs development. Conversely, an acceptable trial weld may be produced with manual intervention that falls outside the proposed automatic operating method. Record both findings. The buyer needs evidence that the full required process works under the defined conditions, not a single pass label that hides unresolved tasks.

Build the procedure trial around representative production

The welding trial should reproduce the joint and operating conditions needed to establish the intended procedure scope. Select test pieces, examinations and witnesses according to the applicable requirements and responsible parties. An editorial example cannot determine the mandatory coupon geometry, test quantity or acceptance values for an unspecified vessel or material.

For custom paired welding, make the proposed simultaneous or staged sequence explicit in the trial documentation. Record any deviations, interruptions or manual operations. A result obtained after an undocumented parameter change may be useful for development but cannot serve as a clear basis for reproducing the process. Preserve the preliminary instructions, actual trial conditions and resulting examination records as distinct documents where the project method requires them.

Identify the transition from development to controlled production instructions. The project should know who can release a recipe, who can change it and how the corresponding WPS reference is maintained. A software database can assist this workflow, but the authority and scope of approval must come from the project's quality system and applicable requirements rather than from the existence of a database entry.

Release production welds through the inspection plan

Production acceptance concerns the actual work made for the project. Link each required weld or defined inspection lot to the applicable drawing, procedure and inspection route. Record the required pre-weld checks, in-process observations and post-weld examinations through the project's controlled documentation. Completion of a robot program should remain separate from release of the assembly.

TWI describes visual inspection as working alongside other inspection methods and assessed against applicable criteria. [4] A process trace or image can support investigation, but the quality plan determines what evidence accepts the production weld. Avoid presenting a stable current graph, a bead photograph or an equipment capability certificate as a universal substitute for the required examination.

Define the disposition of nonconforming work. Keep the original operation, examination finding, repair instruction, repair execution and subsequent acceptance connected to the same weld identity. A repair should add history rather than overwrite it. This is a practical traceability recommendation; the formal document content and approval authority must follow the project's actual quality requirements.

Negotiate acceptance milestones without merging responsibilities

A custom project may have design review, development trials, factory acceptance, installation checks and production release stages. Define what each stage proves and which unresolved items can legitimately remain afterward. A factory test using representative material may demonstrate useful functions while site-specific installation or production approval work remains outstanding.

Assign responsibility for workpieces, material records, consumables, procedures, examination, witnessing, utilities and data retention. Identify dependencies early. A supplier cannot complete a representative trial if the customer has not supplied the agreed assembly information, and a customer cannot assess a claimed result if the supplier omits the configuration or raw evidence needed to understand it.

Write pass criteria before the demonstration. Where a criterion is conditional, state the condition and the route for closing it. Avoid a broad acceptance certificate that conceals excluded weld details or pending inspection. The commercial record should make it possible to distinguish delivered equipment functions from the remaining steps needed to use those functions on a specific production job.

Create one traceable evidence chain

The final review package should let the project follow an identified production weld back to its design requirement, controlled procedure, supporting qualification scope and equipment configuration. It should also lead forward to the actual operation record, required examination and release decision. That chain is more useful than a collection of impressive but disconnected certificates.

Use plain status labels: proposed, under development, demonstrated in a named trial, approved within a stated scope, and accepted for an identified production item. Apply each label only where evidence supports it. In particular, the cited CCS and IACS publications describe external requirements and guidance; their inclusion in a supplier article does not confer approval on the supplier or its equipment.

For a highly non-standard marine welding project, disciplined separation of these evidence categories makes procurement easier. The buyer can identify the remaining obligation precisely, the supplier can demonstrate the function it is responsible for, and the welding and inspection teams can preserve control of their own approval decisions. Equipment capability, procedure qualification and production acceptance then reinforce each other without being mistaken for the same result.

Project review checklist

• Identify the contract, applicable rules and responsible approval parties.
• Separate equipment capability evidence from WPS and WPQR documentation.
• Confirm personnel requirements for the actual welding operation.
• Define representative trial pieces, examinations and acceptance criteria.
• Retain the approved configuration, revisions and outstanding conditions.