Pipeline welding teams operate in environments where consistency, traceability, and compliance are critical to both safety and project success. API 1104 provides the framework that supports this—giving teams a clear, standardized way to qualify procedures, document work, and validate weld quality across projects.
API 1104, Welding of Pipelines and Related Facilities, is the primary standard used for pipeline welding in the oil and gas industry. It’s specifically designed for the realities of pipeline work—long-distance infrastructure, changing environmental conditions, and high operating pressures.
What sets API 1104 apart is its practical nature. It reflects how welding is actually performed in the field and gives teams clear guidance on how to qualify procedures, execute welds, and verify quality. Because of that, it’s widely used by operators, contractors, engineering teams, and inspectors—and is often required by project specifications and regulators.
At a high level, API 1104 outlines the full lifecycle of pipeline welding, from qualification through inspection. It defines the variables that impact weld quality—materials, processes, joint design, and heat input—and clarifies which changes require requalification.
It also establishes expectations for inspection and testing, including visual inspection and nondestructive examination methods like radiography and ultrasonic testing. These requirements help ensure that welds meet both mechanical performance standards and defect acceptance criteria.
While the standard itself is well understood, the difficulty often comes from managing the documentation and maintaining consistency across projects.
Teams are typically working across multiple jobs, materials, and conditions, which makes it difficult to:
When this is handled manually, it introduces risk—whether that’s missing variables, outdated procedures in the field, or gaps during audits.
API 1104 is built around a structured relationship between qualification, procedure, and performance. Each component plays a distinct role, but they are tightly connected:
This relationship is foundational. If the links between these documents aren’t clear or well-managed, it becomes difficult to ensure compliance or defend decisions during inspection.
ProWrite S9 is expanding to support API 1104 workflows in a phased approach, starting with the foundation: procedure qualification.
The initial release focuses on:
This phase is designed to help teams capture required variables more consistently and build code-aligned documentation from the start. By improving how PQRs are created and managed, it sets a stronger foundation for everything that follows.
Future releases will expand into:
Rather than treating each document as a standalone file, this approach focuses on maintaining the relationships between them. That structure helps teams improve consistency across projects, reduce rework, and keep documentation organized and accessible.
For organizations managing multiple crews or projects at once, this becomes especially important. It reduces the effort required to maintain compliance and makes it easier to ensure that teams in the field are working from the correct information.
Successfully applying API 1104 isn’t just about understanding the code—it’s about building processes that support it. That includes standardizing how procedures are created, ensuring access to current documentation, and maintaining clear, traceable records over time.
Tools like ProWrite S9 are designed to support those processes by embedding code assistance directly into the workflow, helping teams stay aligned with API 1104 requirements without adding unnecessary complexity.
API 1104 sets a clear standard for pipeline welding, but the real challenge is managing the documentation and workflows that support it.
ProWrite S9’s API 1104 expansion is focused on making that process more consistent, more traceable, and easier to manage—starting with PQRs and building toward full lifecycle support.