Test packages & sign-off
A test package groups a set of ISOs and their welds so they can be released and tracked together for pressure testing. This page explains how MaxTrax classifies packages, how to read the Test Packages screen, and how sign-off works — the completeness rule that decides when a package can be signed, what signing does, and why a sign attempt is sometimes refused.
Before you start
Section titled “Before you start”- Select a project first. The Test Packages screen is scoped to the active project; with no project selected it prompts you to pick one.
- Signing needs edit access on the project. Reading a package needs only read access.
- Completing welds is the prerequisite for sign-off. Sign-off checks weld completeness, so make sure the welds are complete before you expect a package to be signable — see Complete a weld & test-package sign-off.
What a test package is
Section titled “What a test package is”A test package is a named collection of welds, grouped by the ISOs they belong to and released together for pressure testing. An ISO belongs to a package when the ISO’s test-package code matches the package’s own code — so MaxTrax works out a package’s member ISOs from the ISO data rather than from a separate list. Every weld on those member ISOs is part of the package.
Package types
Section titled “Package types”Each test package carries a type that records which commissioning tier it belongs to:
| Type | Meaning |
|---|---|
| IWP | Installation Work Package — the installation tier. |
| TWP | Test Work Package — the test tier. |
| RFPC | Ready-for-Pre-Commissioning package. |
A package with no type set is treated as a Test Work Package (TWP) — that is the default tier, so projects that don’t distinguish tiers still see every package as a test package. The type comes from your data import, which classifies each package from its source tier column; it isn’t a field you edit on the package itself.
System and subsystem
Section titled “System and subsystem”A package can also carry an optional system and subsystem. MaxTrax combines them into a rollup grouping so packages can be reported and grouped by subsystem; a package with neither set is grouped as Ungrouped. Like the type, system and subsystem come from your imported data.
The Test Packages screen
Section titled “The Test Packages screen”Open a package to see its detail screen. At the top, a header shows the package’s identity and progress:
- The package code and label.
- Its completion figures — the number of active welds in the package, and how many of those are still incomplete. A weld counts toward the incomplete figure while it is missing a weld date or a welder, or still has an inspection awaiting review. When that figure reaches zero, the package is ready to sign.
- Its sign-off status — a Not signed badge while it is open, or a Signed badge with the date once it has been signed.
Below the header, the package’s welds are shown in the weld matrix, grouped by their member ISOs — the same grid used elsewhere in MaxTrax, scoped here to just this package. Use it to see the status of every weld the sign-off depends on. See The weld matrix for how to read and work in that grid.
Turnover / databook readiness
Section titled “Turnover / databook readiness”Below the header, the Turnover / databook readiness panel shows an overall readiness percentage and four facets, each as its own progress bar with a count:
- Welds complete — the same active/incomplete weld figures as the header, restated as a facet.
- NDE reviewed — of the welds that have inspections, how many have no inspection still awaiting review (a weld with no inspections yet is not counted either way).
- Signed — whether the package has been signed.
- MTR docs attached — whether at least one document has been attached to the package. Attach MTRs and other release evidence from the package’s own document panel below the readiness panel — see Documents for how attaching, downloading, and removing works.
The panel reads Ready for turnover once every facet is complete; otherwise it reads Not yet ready.
Underneath it, the What blocks this package panel lists every weld with an inspection still awaiting review — the review items that hold sign-off — one row per weld, showing how many of its inspections are still unreviewed. Selecting View in matrix on a row scrolls to the weld matrix below and searches it for that weld’s number, so you can jump straight to it. Two things to know about that search: if another weld’s number contains the same characters it appears in the results too, and it clears any filter you had set on the matrix (status, lens, spool) so the weld you picked is always visible.
Record a pressure test
Section titled “Record a pressure test”Select Record pressure test in the package’s header to open a form for the required and performed test pressure, the hold duration (hours and minutes), and the date the test was performed. Save to record the values; they’re reflected on the package immediately.
Release blockers
Section titled “Release blockers”Below the Turnover / databook readiness panel described above, the Release readiness panel lists every outstanding release blocker for the package — a single, shared list of what still stands between the package and turnover, covering welds, NDE, the punch list, and documents.
Punch list
Section titled “Punch list”Below the release blockers, the Punch list panel tracks outstanding walkdown items against the package — the small fixes and follow-ups found while working the package that don’t need to hold up signing.
- Raise an item by entering a description (and an optional category) and selecting Add punch
item. It starts
Open. - Edit an item’s description or category at any time, including after the package is signed — the punch list is a running work-off log, not part of the certified record.
- Close an open item once its follow-up is done, or Reopen a closed one if it turns out the follow-up wasn’t complete after all.
Sign a package
Section titled “Sign a package”Signing locks a package as finished. It is a single authorized action — not a separate signature capture — available from the package’s header once the package is eligible.
A package can be signed only when all of the following are true:
- It has at least one active weld.
- Every active weld is complete — it has a weld date and at least one assigned welder.
- None of those welds still has an inspection awaiting review.
When you sign, MaxTrax stamps who signed and when, and locks the package: welds on its member ISOs can no longer be created, classified, or repaired. Once a package is signed, the Sign package button is replaced by the Signed badge — signing happens once.
When a sign attempt is refused
Section titled “When a sign attempt is refused”If a package isn’t ready, the Sign package button stays disabled and shows why — for example, how many welds are still incomplete. If a sign is attempted but can’t go through, MaxTrax refuses it with a specific reason rather than signing a package that isn’t finished:
- The package is empty — it has no active welds to sign.
- A weld is still awaiting review — one or more welds has an active inspection that hasn’t reached a result yet.
- A weld isn’t complete — one or more welds is missing a weld date or an assigned welder.
Resolve the named condition — complete the outstanding welds, or record the pending inspection results — and the package becomes signable.
Related
Section titled “Related”- Complete a weld & test-package sign-off — completing the welds a package depends on.
- The weld matrix — the grid used on the package screen.
- Record an inspection result
- Documents — attaching MTRs and other release evidence to a package.
- Getting started — test package and ISO vocabulary.