Manufacturing

TL;DR for operators A CAD assistant that writes code once and hopes for the best is not an engineering workflow. It is a raffle with syntax highlighting. IterCAD is interesting because it treats CAD generation and editing as an iterative operating loop: read the drawing, generate CadQuery code, execute it in a sandbox, inspect compiler and geometric feedback, revise, and stop only when the model has evidence that the shape is right.1 The paper’s practical contribution is not “AI can design parts now.” That would be the usual confetti cannon, and mercifully not the correct lesson. The better lesson is that useful CAD automation needs closed-loop verification, localized visual grounding, and evaluation metrics that count failures instead of quietly hiding them in the basement. ...

Factories rarely fail because a machine cannot work. They fail because the machine, the operator, the part, the fixture, the pallet, and the next free square meter of floor space refuse to arrive in the same universe at the same time. That is why a scheduling paper about pallets is more interesting than it sounds. ...

Furnace loading is not the glamorous side of artificial intelligence. No one gives a keynote about choosing which pile of titanium scrap should enter an induction furnace. Which is precisely why it is useful. The paper Enterprise Resource Planning Using Multi-type Transformers in Ferro-Titanium Industry applies a Multi-Type Transformer, or MTT, to two classic combinatorial optimization problems: the Knapsack Problem (KP) and the Job-Shop Scheduling Problem (JSP). It then pushes the method into a real manufacturing allocation case: selecting raw materials for a ferro-titanium furnace batch.1 ...

Factory trouble usually begins in language. Not elegant language. Not the polished language of annual reports and transformation roadmaps. The useful trouble is buried in work orders, technician notes, supplier messages, inspection records, customer complaints, meeting minutes, and logs written by people who had better things to do than produce clean training data. ...

Factory sketches are usually where industrial simulation begins, not where it runs. An engineer draws the line, marks the queue, places a processor, adds a conveyor, then disappears into the less glamorous work: configuring objects, assigning arrival distributions, wiring routes, and writing platform-specific logic. The sketch is the easy part. The executable twin is the expensive part. ...

The compiler is the interesting part Blocks are easy to understand. That is why this paper is more interesting than it first looks. At the surface, Prompt-to-Parts: Generative AI for Physical Assembly and Scalable Instructions is a paper about using large language models to generate LEGO-style assemblies from natural language prompts.1 It shows a medieval castle, an International Space Station model, a modular multitool kit, and an image-to-parts helicopter conversion. Naturally, the tempting summary is: “LLMs can now design LEGO models.” ...