The Build-as-Parent-Job Problem
A single plate may hold parts from five customers and several jobs. The machine hours, powder and gas belong to the build; the parts belong to different sales orders with different due dates and post-processing. Most ERPs expect one job to make one item.
Test how a candidate system handles allocating a shared operation cost to several jobs, and how it reports on partial plates. Some bureaus model the build as a work order with phantom or co-product outputs; others keep builds in MES software and post summarized costs to the ERP. Either approach works if the allocation is consistent and visible.
- One build record, many part jobs and customers
- Cost allocation rule for shared machine time
- Partial-plate and failed-build handling
- Link from part serial or lot back to the build file and machine log
Powder Lot Genealogy
Powder is blended, reused and sometimes returned to storage, so genealogy is more complex than a single raw material lot. The system should record virgin lot additions, reused powder blends, sieving, and chemistry or particle size test results, then link each build to the powder lots it consumed. Aerospace and medical customers expect a certificate of conformance with powder and process traceability.
If your ERP has lot tracking with parent-child lots, you can model a blend as a new lot that consumes the old ones. Check that it supports lot attributes for test results and that expired or quarantined powder can be blocked from issue.
Routings, Outside Processing and Quality
Post-processing is a multi-step routing: stress relief, plate removal, support removal, HIP, heat treat, machining, finishing, inspection. Look for outside processing with receiving inspection, minimum charge handling and travelers that show the current step. Quality needs nonconformance records, inspection plans with CT or CMM results, witness coupon tracking and, where certified, document control aligned with AS9100 or ISO 13485.
Systems with strong quality modules, such as Infor SyteLine, Epicor Kinetic or Plex, can model this. Small bureaus may be better served by a job shop ERP such as JobBOSS, E2 or ProShop plus a controlled build log, as long as the traveler captures the essentials.
Try it here, free
MES Implementation Cost Calculator
Estimate total MES implementation cost across licensing, shop-floor terminal hardware, configuration labor, and ERP integration complexity.
Quoting, Costing and Machine Integration
Ask how the ERP supports quoting from build time and post-processing templates, and whether quote assumptions are saved so you can compare them with actuals. Look for machine data capture: some printers export job logs with start, end, layer count and alarms that can be imported or read via an API or file drop. Importing these removes manual time entry and improves cost accuracy.
Without it, operators end up estimating hours on paper. Also verify that the ERP can store 3D files and build documents under access controls, since CAD files for defense parts can be controlled technical data.
When You May Not Need a Full ERP
A bureau with a couple of printers, mostly prototype work and no regulated customers can often run on accounting software, a quoting tool and a spreadsheet-based build log. The pain that pushes teams to an ERP is usually lot traceability, certificate generation, multiple machines and shifts, or margin surprises. Move when those appear, and pick the system by testing a real build with shared plate, powder genealogy and outside HIP before signing.
A demo with a simple make-to-stock item proves nothing about additive.
Frequently asked questions
Can standard job shop ERP handle 3D printing builds?
Yes with design care. Model the build as its own job or work order, assign shared machine cost to the part jobs by a consistent rule, and use lot tracking for powder. The weak points are shared-plate costing and powder blend genealogy, so test those with real scenarios before you commit.
What traceability do aerospace customers expect for AM parts?
Typically the machine and build identifier, powder lot and reuse history, process parameters or software version, heat treatment and HIP records, inspection and test results, and a certificate of conformance. Exact requirements come from the customer purchase order and applicable specifications, so capture them at contract review.
Do I need MES in addition to ERP for additive?
Not always. If your printers export usable job logs and your ERP can ingest them, ERP alone can work. With many machines, shift operations and real-time scheduling needs, an MES or scheduling tool linked to the ERP gives better visibility. Choose based on how many builds you schedule weekly.
Already running an ERP and struggling to see cost per build? Netray can add a private question-and-answer layer over your ERP and build logs without replacing your system.