Alloy, Temper and Batch: What Actually Identifies Aluminium?

The aluminium identity stack

The same piece of aluminium can be described correctly at several levels at once. The mistake is asking one level to prove another.

These layers can be joined. They should not be collapsed.

Alloy designation is a specification key, not a batch certificate

The Aluminum Association's registration and standards route provides defining references for wrought and cast alloy designations and chemistry limits. That makes an alloy code a powerful specification key. It can answer questions such as which nominal chemistry family a designation belongs to.

It cannot tell you the actual measured chemistry of the aluminium delivered to you. A batch can conform to an alloy specification while having measured element values somewhere within the permitted range. The designation constrains the truth. It does not measure the batch.

This is why an exact-looking number copied from a nominal chemistry table is still the wrong evidence object for a field that asks for delivered chemistry.

Temper only makes sense with form and governing specification

Temper adds another layer, but it is not a standalone material identity. The same alloy designation can exist in different tempers, and the properties associated with a temper can depend on product form, dimensions, process and the governing standard or producer specification.

The producer evidence makes that boundary visible. Alcoa's EverCast C862F technical data publishes named alloy chemistry limits and typical mechanical and physical properties for C862F-T6, while explicitly noting that mechanical properties depend strongly on the casting process. Rio Tinto's A356.2 foundry-alloy data likewise publishes composition limits, casting application and typical property information.

Both are useful specification-level evidence. Neither source, by itself, establishes the chemistry, test results, exact producing facility or transaction identity of a particular delivered casting or ingot.

A safe data model therefore stores the alloy designation, temper, form and governing specification as separate assertions, then attaches measured results only when an evidence object supports the delivered scope.

Product form is part of the meaning

“6061-T6 aluminium” sounds precise, but it is not a complete delivered-material identity. A sheet, extrusion, forging and other form can sit under different product standards, dimensional ranges and property conditions. Thickness or section can matter too.

The form/specification layer answers: what requirements should this material meet in this condition?

The delivered-batch layer answers a different question: what evidence says this supplied material actually belongs to that batch and what results were recorded for it?

Those questions need a join, not a substitution.

Specification truth and delivered-material truth must stay separate

A technical sheet, alloy registration record or governing standard can legitimately establish:

• alloy designation
• nominal chemistry limits
• temper or specification context
• declared or typical properties at the stated scope

It does not automatically establish:

• actual delivered-batch chemistry
• actual batch test results
• the actual production batch or cast
• the physical production facility for the delivery
• an item-specific result

This is not a criticism of technical sheets. They are doing the job they were written to do. The error happens downstream when a system changes the scope of the assertion while copying the value.

An exact coil identity can close some joins, not all of them

Speira's public speira.ID record provides a useful real example. The light public view for exact coil 9013514010 binds that coil to the VERO ORBIS product, EN/AW3104 H19 and named casthouse and rolling-mill information.

That is materially stronger than finding a generic EN/AW3104 datasheet because the digital record identifies one exact coil. But the same public view keeps several coil-specific fields, including chemical composition and batch number, behind direct-customer or subscriber access.

The lesson is not that a digital record solves everything. It is that identity and evidence availability are separate. An exact coil identifier can make a correct join possible while individual assertions remain unavailable to the public or still require a customer evidence object.

Cast, batch, lot and coil are join keys, not interchangeable words

Producer terminology can vary. One business may use cast, another batch or lot, and a processor may create a new coil or work-order identity downstream.

Treat those labels as keys with defined scope rather than assuming they all mean the same manufacturing unit. When a certificate or test object arrives, the important check is whether its identifier can be bound to the delivered object and whether the evidence scope matches the assertion you want to publish.

If you need to decide whether the operational object should be a lot, serialised unit or individual item, that belongs with the generic guide to lot, serial and item identity. Aluminium does not create a universal exception to that decision.

Commercial product identity is another layer again

A manufacturer product name, catalogue code or SKU can help find the right technical evidence. It still does not replace material identity.

A commercial product may be sold in several forms, dimensions, tempers or production batches. Conversely, one aluminium alloy can appear across many commercial products. Keep the catalogue identity as a useful join, but do not let it silently become the batch key.

The separate model, variant and SKU facts guide owns that commercial-granularity problem.

Identifier design comes after the evidence model

A system can use producer identifiers, internal ERP keys, standardised identifiers or a combination of them. The first design question is not which identifier format looks most universal. It is which object needs to remain distinguishable and which evidence must be bound to it.

Once that is clear, the generic product identifiers and identifier design guidance covers the broader identifier architecture. This page only needs the aluminium-specific rule: do not use an alloy designation as if it were the unique identity of a delivered batch.

A check before publishing a delivered-material fact

Use this check whenever a value has been found in a standard, technical sheet, certificate or digital product record:

1. Name the assertion. Is it alloy, temper, form, nominal chemistry, measured chemistry, mechanical property, facility or another fact?
2. Name the evidence object. Is the source a standard, registration record, technical sheet, batch certificate, exact coil record or item test?
3. Read the source scope. Does it describe an alloy family, product family, facility, batch, coil or exact item?
4. Find the binding key. Can the evidence object be joined to the material that was actually supplied?
5. Reject scope promotion. A family or specification value does not become a batch result because the designation matches.
6. Keep residue visible. If the batch ID, chemistry, test result or facility cannot be established, leave that assertion UNKNOWN or requiring evidence rather than filling it from a broader source.

That approach lets you reuse strong specification data without overstating what it proves.

What would change this page

The identity guidance would need review if a future aluminium delegated act prescribed a mandatory granularity or identity stack that materially changed these joins, or if a cross-industry standard or public API established a materially different universal batch-identity model.

A new technical sheet or producer portal would not change the core distinction on its own. It would simply create another evidence route whose scope and binding still need to be checked.

Sources

• The Aluminum Association, Bookstore and Registration Records
• Speira speira.ID example coil 9013514010
• Alcoa EverCast C862F Technical Data
• Rio Tinto, Primary aluminium foundry alloys, A356.2