It reasons about the code. It does not just print it.

The difference in one example

A procedure is qualified on a test piece 12 mm thick. A job arrives with a 22 mm joint. Is the procedure valid?

A document generator has produced a PDF that says 12 mm. Answering the question means somebody opens the code, finds the thickness range rule for that process, and works it out — correctly, under time pressure, every time, for every assignment.

An engine has already computed the qualified range from the essential variables at the moment the qualification record was created. The assignment either falls inside it or it does not, and the system says which. The rule is applied once, by a machine, instead of many times, by people who are busy.

WPS-017 · qualified PQR-021

Qualified ranges, computed from the test record

Thickness3 – 20 mm

Diameter≥ 60 mm

Positionall (1G–6G)

Material group1.1 – 1.4

M. Rossi covers joint W-0143Qualified ✓

What it holds

• Codes, at the edition level — ASME IX, ISO 15614-1, ISO 9606-1, AWS D1.1 and the rest
• Essential, supplementary essential and nonessential variables, per process, per code
• Material groupings — P-numbers, ISO/TR 15608 groups — and how a qualification extends across them
• Filler metal and weld metal groupings
• Position coverage, diameter and thickness rules, heat input limits, PWHT conditions

Why the edition matters so much

Codes are revised. A qualification made under one edition does not silently become a qualification under the next, and a contract may name an edition that is no longer current. Binding every record to the edition it was made under is not pedantry — it is the only way the record still means something in five years, which is exactly when somebody will ask.

It also makes revisions legible. When an edition changes, what changed for you is a question with an answer, rather than a review of everything.

Where you can see it working

In the ordinary moments: assigning a welder to a joint, drafting a procedure, being told the NDT extent for a class of weld. None of it looks like a feature. That is the intended effect — the code stops being something you consult and becomes something the system already knows.