Notes for people who program machines.
What we learn building Metallovy with machinists: coordinates, Heidenhain code, drawings, data and the plant.

Every number has a source
Geometry computes the coordinates, AI reads and explains, a person confirms. Why every value in a Metallovy program can be traced back to where it came from.
Read more
The hidden cost of hand-typed coordinates
Hunting dimensions, recalculating from your zero, bolt circles, typing the same points three times: where transfer errors come from, and a checklist that works without software.

Heidenhain code in your shop's style
Machinists edit every program anyway, so generated code has to look like their own: one LBL per hole group, the shop's cycles and tool numbers, a STOP after every tool.

Paper, PDF, DXF, STEP: what arrives with an order
Each format gives you something and hides something else. What you can rely on in each, how Metallovy handles it today, and what to ask the customer for.

Customer drawings are not ours
Geometry stays on a PC at the plant, cloud AI only with permission, a log of who did what. How Metallovy treats drawings, and how to answer customers' data questions.

The whole plant without walking the floor
From one machine to the plant: progress weighted by time, one tap at the STOP after each tool, a plan per machine with load and 'what if'. A first version, on demo data.

Bring one drawing. Leave with a program.
Send us one real order and the program your shop wrote for it. We return the coordinates, a program in your style and a line-by-line comparison — then your machinist tries it on the next job.