Additive MES: Connecting Orders, Builds and Finished Parts

An additive manufacturing execution system connects the work a customer ordered with the work moving through production. For a service bureau, that means answering a practical question: where are the units needed to finish this order, even when they share a print build with parts from other customers?

A useful evaluation starts with those relationships. A dashboard showing that a printer has finished is helpful, but it does not establish whether every customer part has passed finishing, inspection and shipment preparation.

Model orders, production runs and builds separately

An order describes a customer commitment. A production run describes a quantity of a particular part following a particular sequence of operations. A build groups units for an operation. Those groups can change after printing: some parts need dyeing, others need inserts, and others can move directly to inspection.

Consider an illustrative order for ten identical parts. Six units may join one build and four another. After printing, one unit is scrapped. The order still needs ten acceptable units, and the team needs to know where the replacement enters production. A single “printing complete” checkbox cannot represent that situation accurately.

During a software demonstration, ask the vendor to run this example. Check whether the operator can see the part, quantity and production run at each step, and whether sales can distinguish production progress from customer-order completion.

Evaluate the whole production route

List the operations that actually determine delivery: preparation, printing, cooling or part removal, finishing, inspection and dispatch preparation. Give each step a clear completion condition. “Printed” and “ready to ship” should have different meanings.

Keep material compatibility and finishing requirements visible when forming batches. Grouping everything by customer order may waste build capacity; grouping everything by material may hide a finish-specific deadline. The system should let the team coordinate both views without losing the connection to the original order.

For repeat parts, a reusable route can preserve an established method. For unfamiliar work, the team needs a controlled way to choose different operations. Phasio's production routing model gives each work order its own routing snapshot. A later template change does not silently rewrite an existing run.

Know where each system takes responsibility

Build preparation, business administration and shop-floor coordination are different jobs. Your slicer or nesting tool prepares the print job. The printer and its controls execute it. Accounting software maintains financial records. MES or workflow software coordinates the production record between these activities.

Ask which connections are native, which require an integration, and which rely on operators entering updates. “Real time” is only meaningful when the source and timing of each update are understood. An API being available does not mean every machine is connected automatically.

Phasio documents a powder-bed workflow in which nesting happens offline and a 3MF upload helps connect the prepared build to production. This is a concrete integration boundary to evaluate with your own files.

Test exceptions before scaling

A pilot should include a split build, an optional finishing step, a repeat order, a scrap event and a second run for the same part. Ask an operator to perform the updates, then ask someone outside production to explain the resulting status.

Phasio's scrap and trace guide describes replacement quantities being added to the beginning of the existing work order. It also states that the scrap record is not individually linked to those replacement units. If your traceability requirements need that relationship, assess it explicitly.

Start with one production route and compare time spent finding work, unresolved quantity discrepancies and late handoffs before and after the pilot. Expand when the team trusts the records and understands how to handle exceptions.

Explore Phasio production management with a representative order, including the difficult handoffs that currently require a spreadsheet or a conversation.