Real problems. Working software.

An assembly leaves the crib, gets preset, runs on a machine, comes back blunt and goes out for regrinding. Somewhere in that loop most shops lose track of it, and the answer to "where is that holder" becomes a walk around the building.

Sonar closes the loop. Every holder and assembly carries a tag; a scan at a station is the only thing anyone has to do. From there the system knows what exists, where it is, how long it has been sitting there and who moved it last — and the shop stops buying duplicates of tools it already owns.

• Tag scan at every station
• Live wall dashboard for the floor
• Approval flow for regrind and scrap
• Holder and tool catalogue
• Shop map with routed traffic heatmap
• REST API and signed webhooks for your ERP

Getting correct starting values out of a tooling catalogue means holding four pages open at once: the tool, the insert selection chart, the coating matrix, the V_c band for the material class — then the h_m table for the feed, and the chip-thinning arithmetic by hand. Most programmers do it once, write the numbers on a sticky note, and reuse them on the wrong material.

This does the whole lookup in a browser, from the catalogue's own tables. Where the catalogue has no value for a combination, it says so instead of printing a number — and a family that is not rated for slotting is refused, not answered.

• 136 milling tools · WSP catalogue 03/25
• 1,464 sawing items · Sägen catalogue 09/25
• 500+ materials by SS, DIN, EN, AISI, UNS or JIS
• Insert and coating picked from the selection chart
• Vc · n · fz · Vf · Q with exact chip thinning
• One file, works offline