.png)
Physical weld
Canonical identity across every project-native reference.
Physical identity and examination
One physical weld. Every event. No erased history.
KanGate resolves the same physical weld across drawings, weld logs, welder identity, WPS, NDE reports, repair records, materials, package scope, and final acceptance. Contractor teams see the exact action required to close the weld; enterprise clients see whether acceptance and downstream release are genuinely supportable.
Control question: Can the project prove this weld's complete current history?
Weld lineage treeISO-2201 / W-14
Governed stateFabricationW-14 created / WPS-07 appliedIdentity established
Original examinationRT-00456 / rejectDiscontinuity recorded
Repair eventREP-0021-R1 / authorizedPrior reject preserved
Repair examinationRT-00471 / acceptedPackage recalculated
Representative deterministic example - not customer proof.
Discipline-specific evidence model
A weld has a current state only when its history is complete.
The page follows one physical weld through procedure, welder eligibility, original rejection, repair authorization, repair examination, and the packages that depend on its acceptance.
Procedure
WPS, revision, applicability, process, range, project control.
Welder eligibility
Qualification, continuity, process, position, date, authorization.
Examination
Required method, extent, report, indication, result, acceptance.
Repair history
Reject, disposition, excavation, repair, re-examination.
Package effect
Current consequence for release, turnover, and authority review.
Demonstrated operating logic
Select a weld event and see what changes.
Contractor teams see the closeout action. Enterprise reviewers see whether the acceptance basis and downstream package consequence can be trusted.
Identity
One canonical weld identity sits behind inconsistent labels.
Drawing mark, weld log number, NDE reference, repair reference, spool, line, and package all resolve to the same physical weld without overwriting source identifiers.
Condition7 aliases
Governed stateRESOLVED
State transition
The original rejection stays visible after the repair is accepted.
That is the point. KanGate does not flatten the weld into passed or failed. It keeps the chronology intact so a reviewer can understand what happened, who accepted it, and which packages changed.
Weld created
Welder checked
Reject recorded
Repair authorized
Repair NDE accepted
Packages reviewed
Controlled outputs
The output is a weld story a reviewer can inspect.
Each register or report carries the source record, current state, open condition, accountable authority, and package consequence behind the conclusion.
Weld lineage register
A current, source-linked history for each physical weld.
NDE and repair chronology
Required examination, actual results, repairs, and final acceptance.
Package consequence report
Every package, output, or release state affected by the weld event.
90-day governed proof engagement
Use one difficult welding package to prove identity, examination, repair, and consequence control.
Begin with one active project, one primary workflow or release gate, an agreed evidence set, defined authorities, bounded acceptance criteria, and a Deploy / Refine / Stop conclusion. Pricing is established after pilot-fit review and scope confirmation.