Functional Requirements of Software Tools for Laser-Based Powder Bed Fusion Additive Manufacturing for Metals
Bibliographic record
Abstract
Abstract Additive manufacturing (AM) for metals is rapidly transitioning to an accepted production technology, which has led to increasing demands for data analysis and software tools. The performance of laser-based powder bed fusion of metals (PBF-LB/M), a common metal AM process, depends on the accuracy of data analysis. Advances in data acquisition and analysis are being propelled by an increase in new types of in situ sensors and ex situ measurement devices. Measurements taken with these sensors and devices rapidly increase the volume, variety, and value of PBF-LB/M data but decrease the veracity of that data simultaneously. The number of new, data-driven software tools capable of analyzing, modeling, simulating, integrating, and managing that data is also increasing; however, the capabilities and accessibility of these tools vary greatly. Issues associated with these software tools are impacting the ability to manage and control PBF-LB/M processes and qualify the resulting parts. This paper investigates and summarizes the available software tools and their capabilities. Findings are then used to help derive a set of functional requirements for tools that are mapped to PBF-LB/M lifecycle activities. The activities include product design, design analysis, process planning, process monitoring, process modeling, process simulation, and production management. PBF-LB/M users can benefit from tools implementing these functional requirements implemented by (1) shortening the lead time of developing these capabilities, (2) adopting emerging, state-of-the-art, PBF-LB/M data and data analytics methods, and (3) enhancing the previously mentioned AM product lifecycle activities.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.019 | 0.073 |
| Meta-epidemiology (narrow) | 0.003 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.006 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.006 | 0.006 |
| Open science | 0.005 | 0.004 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".