Use a 3D model file to start an online quote, then add the purpose, use environment, and acceptance check. Protolabs' official quoting guide asks users to upload 3D CAD files and then choose materials, secondary operations, and finishing options. It also says that additive material and resolution changes affect 3D-printing prices.
Why the process name is not enough
Additive manufacturing builds a part layer by layer from a digital design. NIST notes that the process can use metals, plastics, or ceramics, while feedstock may take forms such as powder or wire. In other words, the phrase 3D printing does not identify one material or one process path.
For your handoff, record why the part exists, where it will be used, and how you plan to check it. The following is an editorial example you can adapt.
A compact handoff record
A developer or manufacturing coordinator can keep the request in four human-readable fields. This is an editorial example; the names are not required schema fields.
part_job: Hold a sensor in the same position during assembly
use_context: Indoor assembly bench; fluid contact still unknown
critical_interface: Sensor contact face and mounting-hole relationship
acceptance_method: Fit the mating part and agree on how to measure key dimensions
The first field describes the job rather than the noun. “Bracket” is ambiguous; “holds a sensor during assembly” tells the recipient which function should guide follow-up questions. The second field records the actual environment and preserves unknowns instead of inventing values. The third points to the interface that matters. The fourth turns “must fit” into a conversation about an observable check.
Keep unknowns visible
A request does not become more complete when someone guesses a temperature, load, or tolerance. Use a visible state such as known, to_confirm, or supplier_input_needed in an internal handoff. For example, material choice can remain supplier_input_needed while the use context and important interface are already known. These labels are suggestions for team communication, not a standard defined by NIST or Protolabs.
Compare responses against the same input
If two suppliers receive different quantities, finishing requests, or inspection scopes, their quote totals are not directly comparable. Send the same model, quantity, use description, environment notes, finishing request, and acceptance scope. Then review which material and process each supplier assumed, what post-print work is included, what will be inspected, and which unknowns still need answers.
Consider two replies to the same request. One may include a material recommendation and a plan to check the mating interface. Another may quote only the printed geometry and list inspection as an option. That difference is useful information even without fictional prices. It tells the team what each response includes and what must be clarified before choosing.
A small example
An office cable guide and a shop-floor positioning aid can share the same geometry. The first may prioritize appearance and handling. The second may raise questions about fluids, repeated force, and mating surfaces. This example does not prove that one material or process is better. It shows why geometry alone cannot carry the whole use case.
A practical first message can be short: what the part does, where it works, which interface matters, and how you plan to inspect it. Mark unknowns as questions for the manufacturer. The CAD file opens the quote. The brief gives engineers, buyers, and software teams a shared basis for comparing what comes back.
Sources:
- https://www.protolabs.com/help-center/prodesk/
- https://www.nist.gov/additive-manufacturing/what-additive-manufacturing
Read the full EyeContact analysis in the original article.
Top comments (0)