MyTechDailyNews Software Update: Additive Industries Next-Generation Build Processor Brings Faster MetalFab Build Preparation

Reported by Sarah Chen, Tech Daily Software desk · Editorial contact: hello@techdaily.com

The gap between a planned build and a machine-ready build file is where a lot of metal additive workflows lose their rhythm. Additive Industries and Materialise have made the Additive Industries Next-Generation Build Processor available for MetalFab systems, and for software-focused readers this release is best understood as a workflow correction rather than a catalogue item: it keeps the functions of the existing Additive Industries Build Processor and stacks additional capabilities for build preparation, process control, and production management on top of them, with a published benchmark that puts preprocessing runtime at the centre of the story.

Release at a glance

• Product: Additive Industries Next-Generation Build Processor, developed with Materialise and made available for MetalFab systems.
• Lineage: it brings together the functions of the existing Additive Industries Build Processor with extra capabilities for build preparation, process control, and production management.
• Intended use: industrial metal additive manufacturing applications that need consistent process execution and repeatable results.
• Primary output: production-ready build files.
• Availability: the software is available to MetalFab customers.

What actually changes in day-to-day build processing

Less waiting before the job can start

The first claim attached to the Next-Generation Build Processor is time: the software shortens preprocessing time. For teams that queue several build files a day, that is the practical difference between processing sitting inside the operator's shift and processing becoming a scheduled bottleneck.

Headroom for larger and more complex builds

The release is also positioned around scale. The processor is described as handling large and complex builds, which reframes preprocessing capacity as a selection criterion: the question is no longer only whether a build file is correct, but whether the toolchain can chew through a dense, parameter-heavy build without turning that into unplanned downtime.

More control over scan strategies

Users get additional control over scan strategies. Read alongside the exposure-strategy options below, this is the part of the change that process engineers feel first, because scan strategy is where a preparation tool stops being a file converter and starts being a process definition.

Process control and production management together

Beyond preparation, the software adds further process-control and build-preparation functions and folds production management into the same environment, rather than treating it as a downstream reporting task.

Machine capabilities the release exposes

Support is included for the capabilities introduced with the MetalFab 420K. In the published description these are:

• laser load balancing;
• variable beam diameter control by vector type;
• thermal management using ghost vectors;
• additional exposure strategy controls.

For readers evaluating the software today, the useful framing is that these are the items to verify in your own profile set: if your process relies on any of them, the Next-Generation Build Processor is the tool that puts them under explicit control.

Benchmark data and a side-by-side comparison

Benchmark testing reported with the release showed that processing time dropped from 46 minutes with the Classic Build Processor 2.6 to 6 minutes with the Next-Generation Build Processor. The stated drivers are multiprocessing and algorithm updates, which matters for anyone tempted to attribute the result to faster workstations: this is a software-side improvement.

Aspect	Classic Build Processor 2.6	Next-Generation Build Processor
Reported benchmark processing time	46 minutes	6 minutes
Stated performance drivers	Baseline toolset	Multiprocessing and algorithm updates
Function coverage	Functions of the Additive Industries Build Processor	Same functions plus additional build preparation, process control and production management capabilities
Large and complex builds	Not the focus of the release	Explicitly handled
Scan-strategy control	Existing control set	Additional control over scan strategies
Support for MetalFab 420K capabilities	Not specified in the release	Included: laser load balancing, variable beam diameter control by vector type, thermal management using ghost vectors, additional exposure strategy controls
Existing profiles	Source of the profile set	Users can import profiles from the Classic Build Processor
Availability	Prior generation	Available to MetalFab customers, for MetalFab systems

How Materialise Magics fits into the chain

The software integrates with Materialise Magics for build preparation, configuration, and job submission. Two implications are worth noting for anyone planning the switchover:

• Magics remains the workspace where preparation and configuration work happens, and where the job is submitted, so the change is additive to an existing pipeline rather than a replacement of it.
• The processor is the layer that decides how that prepared build is executed and controlled, which is where the new scan-strategy, exposure and production-management functions live.

Step-by-step: moving from the Classic Build Processor

1. Confirm eligibility. The software is available to MetalFab customers, and it was made available for MetalFab systems, so the starting point is validating your installed base rather than your file formats.
2. Inventory the profiles you use today in the Classic Build Processor. The migration path stated with the release is to import profiles from the Classic Build Processor, so a clean, current profile set is what makes the switch predictable.
3. Run build preparation and configuration in Materialise Magics, the integration point for preparation, configuration and job submission.
4. Set the scan strategy and the additional exposure strategy controls on the Next-Generation Build Processor side, instead of accepting defaults carried over from the older profiles.
5. If your machine carries the capabilities introduced with the MetalFab 420K, verify laser load balancing, variable beam diameter control by vector type, and thermal management using ghost vectors inside the imported profile before you trust a production job.
6. Submit the job and treat the result as a production-ready build file, then keep the process-control and production-management records for repeatable-result comparison.

Numbers referenced in this report

• 46 minutes — benchmark processing time attributed to the Classic Build Processor 2.6.
• 6 minutes — benchmark processing time attributed to the Next-Generation Build Processor.
• 2.6 — the named Classic Build Processor release used as the comparison baseline.
• 420K — the MetalFab 420K model designation whose new capabilities the software supports.
• Multiprocessing plus algorithm updates — the two stated drivers of the runtime improvement.

Common misconceptions

“Old profiles are wasted.”

No. The stated path is that users moving to the new software can import profiles from the Classic Build Processor, so accumulated parameter work carries across.

“The speed-up means you need newer hardware.”

The published explanation credits multiprocessing and algorithm updates — software changes — not workstation upgrades.

“This replaces the preparation stage.”

It does not. The software integrates with Materialise Magics for build preparation, configuration, and job submission; the processor governs how the prepared build is exposed, controlled and managed.

“Only 420K owners should look at it.”

The release was made available for MetalFab systems and is offered to MetalFab customers; the 420K capability set is what the software additionally supports, not the boundary of who can use it.

FAQ

Who can get the software?

MetalFab customers. Additive Industries and Materialise made the Additive Industries Next-Generation Build Processor available for MetalFab systems.

What does it do that the previous tool did?

It brings the functions of the existing Additive Industries Build Processor together with additional capabilities for build preparation, process control, and production management.

How large is the reported time saving?

In benchmark testing, processing time dropped from 46 minutes with the Classic Build Processor 2.6 to 6 minutes with the Next-Generation Build Processor.

Which machine functions are newly covered?

The capabilities introduced with the MetalFab 420K: laser load balancing, variable beam diameter control by vector type, thermal management using ghost vectors, and additional exposure strategy controls.

Does this matter for repeatability?

Yes — that is the stated design intent: the software is intended for industrial metal additive manufacturing applications that need consistent process execution and repeatable results.

Action recommendations

• Time your own preprocessing job before you judge the headline figures; use your current runtime as the baseline against 46 minutes and 6 minutes rather than assuming your builds behave like the benchmark file.
• Re-validate imported profiles one capability at a time if you rely on the 420K feature set, starting with laser load balancing and thermal management using ghost vectors.
• Treat scan-strategy control as the reason to upgrade, not just speed: additional control only pays off when you actually change strategies and record the outcome.
• Log process-control settings per job from day one, so the repeatable-result claim becomes measurable inside your production management data instead of staying a vendor statement.
• Route eligibility and rollout questions through your MetalFab support channel; for editorial follow-up on this report, contact Tech Daily at hello@techdaily.com.

The practical takeaway for software-first readers is narrow but useful: the Additive Industries Next-Generation Build Processor is the preparation layer that removes a long-standing waiting step for MetalFab systems while adding control over exposure and scan behaviour. Evaluate it on your own build files, keep your existing profiles as the migration starting point, and let the production-management functions turn each repeat run into comparable data.