Written by machinists. Enforced in code.
Every decision has a rule, every rule has an author — and when MEKLYRA does not know, it says so.
The experience is the engine.
MEKLYRA was not trained to sound like a machinist — it was written by machinists. Decades of process engineering at the machine, distilled into 275 written rules the engine must obey. The math proposes the numbers; the experience holds veto power. Three of those rules, the way they were learned:
Spot first — unless it's proven
A drill goes in only after a spot, unless that exact drill is on record as self-centering. "Probably fine" is how a hole walks off position — a spotting cycle costs seconds, a walked hole costs the part. Not on record means spot, and the plan says why.
Face, then the contour — always
The first cuts clean the stock to size: face, then the outside contour, before anything else. Now the material is seen true, and every hole that follows is measured against a datum that actually exists — not against raw stock that was never straight.
Zero belongs to the process
The coordinate system is the programmer's decision, made for the setup — the STEP file doesn't get a vote. Z along the spindle, origin on a drawing datum when there is one. A system that copies the CAD axes is a system that never stood at a machine.
Every one of the 275 rules is written down, reviewed, and enforced in code — and your own shop's rules can join them. Machining knowledge stops leaving with the people who carry it: it becomes a repeatable engineering system the whole shop runs on. That is the difference between a model that imitates experience and a system that carries it.
Every decision has a rule. Every rule has an author.
Most systems guess and look confident. MEKLYRA is built the other way around: it plans like a good programmer, and when it doesn't know — it says so.
The Playbook runs the show
275 written rules, each with a source — setup order, workholding, hole-making, milling strategy, coordinate systems, time. The engine may only do what the playbook allows, and every choice on screen cites the rule that made it.
Honest by construction
Missing data stays missing: no invented feeds, no guessed tool lengths, no silent defaults. A gap in the plan is painted on the part in warning amber — material no operation removes is something you see, not something that disappears.
The drawing decides
The model is compared against the drawing — threads, datums, tolerances. Where they disagree, the plan stops and says exactly what's wrong instead of quietly machining to either number. A part that isn't ready to program is never presented as one that is.
See it machined first
Per-setup fixturing and work offsets (ISO 841), tools drawn to their real type and dimensions, metal coming off the stock as it would on the machine, and cutting time separated from setup, tool-change and rapid time.
It works with what you already run.
MEKLYRA sits between your CAD, your CAM and your ERP — it reads what you already have and hands the floor a plan. Every file is read in your browser; your models, drawings and programs never leave the shop.
Your CAD — the model and the drawing
A STEP model, with the drawing as PDF or DXF. The engine reads true B-Rep geometry, and the drawing's title block and callouts — material, tolerances, threads — are read cell by cell, not typed twice.
Your CAM — the part you already programmed
Already cut it in SolidCAM? Drop SolidCAM's setup document and the job package is built on your own plan — your setups, tools, speeds and feeds taken as written. MEKLYRA plans the process; it never replaces the CAM you own.
Your ERP — your crib and warehouse
Your tool crib comes from your ERP's own export — KITARON today, read by column name so a reordered export still loads — and every tool is matched to your shelf by its company part number. Built to add another ERP the same way.
Don't see yours? A pilot on one of your parts is the fastest way to find out — send it and we'll tell you honestly what reads today and what we'd add.