Skip to main content
Fabrication management

Fabrication management with one source of truth for the shop

Keep drawings, weld procedures, welder qualifications, material certs, NDE reports, and turnover packs linked to the same job for review.

  • Central drawing register with revision control and PDF upload
  • Weld procedures (WPS / PQR) and welder qualifications attached to each weld
  • Material certs (MTRs) linked to the heat numbers they cover
  • Turnover packs assembled from reviewed project records
  • Transmittals tracked end-to-end with audit history

One workspace for connected fabrication records

A pipe shop runs on many record types: drawings, transmittals, WPS, welder logs, NDE reports, material certs, hydrotest sign-offs, and punch lists. Piping.Tools can keep supported records in the same workspace and link them through the drawing the work belongs to.

Built around how the shop actually transmits and hands over

Transmittals send what was issued. Turnover packs assemble what was completed. Both are built from the same underlying records, so the package an inspector signs is the same package the engineer issued — only with the welds, NDE, and certs filled in along the way.

Where it lives in the product

The workspace tabs that deliver it

Each card jumps to the dedicated feature page for that workspace tab — same data you see in the product, explained in detail.

FAQs

What does Piping.Tools manage on the shop floor?
Supported workflows include drawings, transmittals, weld logs, weld procedures (WPS / PQR), welder qualifications, NDT reports, material certificates (MTRs), turnover packs, loads, and shipping. Configured relationships help reviewers navigate between a pack and its source records.
How is this different from a generic project-management tool?
Piping.Tools models welds, WPS records, MTRs, and turnover packs as domain records. Configured relationships can connect a weld to its procedure, welder, and material context, while qualified personnel remain responsible for checking project and code requirements.
Does it replace our QA or document-control system?
That depends on the required records, integrations, approval model, and customer deliverables. A paid pilot should test the intended workflow before any replacement or integration decision is made.
Can multiple shops or projects run side-by-side?
Yes. Projects are first-class, and team membership is scoped per project. A welder on one job and an inspector on another can share the same login while only seeing what they should.