3MF Package Acceptance: Resolve the Unit Interpretation

A supplier sends a 3MF package and a screenshot showing that the assembly opens in a receiving application. Before accepting the digital handover, the buyer should ask how the application's displayed dimensions relate to the unit convention in the file. A 3MF package acceptance can establish that relationship without pretending that a preview proves a physical manufacturing result. The following discussion concerns an imaginary file delivery; no model has been imported or printed for this article.

Locate the convention inside the delivered model

The 3MF Core Specification and Reference Guide, identified as version 1.4.0 in the source, defines a model unit attribute with millimeter as its default. This is a rule for interpreting model information in that format. It does not tell the buyer what a particular supplier intended or whether a receiving application's display follows the intended interpretation.

Ask the supplier to identify the convention that applies to the delivered model and explain whether it is explicit or relies on the documented default. Keep that answer with the exact submitted package. A separate screenshot caption may be useful, but it should not silently replace what the file declares. If the caption and the declared convention appear inconsistent, record the inconsistency as a question for the contributor.

For the fictional delivery, the buyer sees a familiar-looking assembly but lacks an explanation of the display settings. The appropriate response is to request the missing association. Do not estimate the intended dimensions from a recognizable shape, or change the imported model until it looks plausible. Either action could conceal the very interpretation issue the acceptance review is meant to expose.

Ask what the receiving application actually reported

Request the name and version of the tool used for the demonstration, the supplied file identifier and the displayed quantity the supplier wants the buyer to inspect. The explanation should distinguish reading the file's convention from changing a display preference or applying a transformation. These are proposed evidence questions, not a claim that any particular application has made an error.

The 3MF Consortium's lib3mf project documents reading, writing, conversion and validation capabilities for the format. That provides one example of software support available to developers. The existence of such a library is not evidence that the supplier used it, that a particular check ran or that the delivered model passed a validation exercise.

If the supplier supplies a validation report, ask what input and scope it covers. A report about one package should remain associated with that package. Do not extend it to a later export merely because the filename is similar. Likewise, validation of format-related information should not be relabeled as an independent confirmation of the buyer's intended part dimensions.

Keep the original package while a question is resolved

Agree how the supplier will provide a correction or clarification. The response might explain the existing file or supply a replacement package. Keep those possibilities separate in the handover record. A clarification changes the buyer's understanding of material already received; a replacement introduces material that needs its own identified review. Neither should make the original question disappear from the record without an explanation.

Do not overwrite the submitted package merely to simplify the directory. Keep a readable association between the original item, the question and the response. If the supplier's demonstration includes an adjusted display setting, ask whether the receiving team is expected to retain that setting or whether the file itself now carries a different declaration. The answer belongs to the delivered workflow and should be stated explicitly.

Agree on one observable import finding

An authorized software-only demonstration can be planned around a defined observation: the reviewer can identify the unit interpretation associated with a named delivered model. Before it begins, state which materials and tool configuration are in scope. Afterwards, record what was actually shown and which explanations came from the supplier separately. This article provides no import commands or machine-operating instructions.

A limited acceptance note can confirm that the file convention and receiving display have been related in the supplied evidence. It should leave physical dimensions, manufacturing suitability and printed-part inspection to the reviews that actually address them. If the relationship remains unexplained, report that specific gap instead of replacing it with a general statement that the package failed.

The illustrations are original conceptual maps of a file-review task, with no fabricated mesh, scale values or printer output. Related digital-delivery discussions appear in the 3D manufacturing reading section, while the article directory provides further topics. A usable import finding tells the next reviewer how the supplied convention was understood and which evidence supports that account.