Feature-to-operation matching · explainable verdicts · setups & machines · cost-linked
PlanDFM matches each recognized feature — a hole, a pocket, a thread, a tight bore — against a versioned library of manufacturing strategies, gated by material, tolerance, quantity, and accessibility, and returns a selected/rejected/deprioritized/uncertain verdict per strategy with the specific requirement it passed or failed. The winning strategy's parameters, plus the setups and machine it needs, feed straight into the same cost engine behind every quote in the suite.
Free to start · no credit card · your files stay yours.
The problem
Drill straight through or centre-drill first, tap or thread-mill, rough conventionally or clear adaptively — the right call for THIS feature, at THIS tolerance and quantity, usually lives in one programmer's head.
A tight-tolerance bore or a feature with poor tool access should change the operation, not just the cycle time — but without a documented rule, it often gets planned like every other hole until it fails on the machine.
The programmer's actual operation choice and the spreadsheet's cycle-time guess are two different numbers, built by two different people, that happen to end up on the same quote.
What you get
Recognized features are matched individually against a versioned strategy library — drill-from-solid, ream-to-tolerance, form-tap, adaptive-clearing, and more — not one blanket approach applied to the whole part.
A strategy only wins when it clears the part's real requirements — the same requirement Partimation names when a strategy is rejected or flagged uncertain, not a silent pass.
When accessibility, tolerance, or another requirement isn't known for a feature, the verdict says so — "uncertain" — instead of quietly picking a strategy anyway.
Setups and machine assignment ride the same engine that already prices the rest of the suite, so the plan's operation and the quote's price stop being two different guesses.
How it works
Features already recognized on the part — holes, pockets, slots, threads, bosses — feed the matcher directly.
Each feature gets selected/rejected/deprioritized/uncertain verdicts against the strategy library, with the requirement named.
The winning strategy's setups and machine assignment come off the same engine that prices the rest of the suite.
The plan's operations price straight through — one number, traceable back to the strategy that produced it.
Pricing
Priced for a one-person job shop and a production programmer alike. Feature matching is unmetered — plan as many parts as you like.
EUR prices exclude VAT, added at checkout where it applies. Early adopters keep their price as the suite grows.
Run it your way
Sign in and plan a part from any browser. We run the compute, ship the updates, and keep your data yours.
Defense, aerospace, and anyone under NDA can run the whole thing on their own hardware. Custom strategy packs are the single largest concentration of a shop's own manufacturing knowledge — licenses and updates are signed files, so an air-gapped install stays air-gapped.
Where this fits
ProcessDFM answers which process family should even be in the running. PlanDFM plans the operations inside that family, feature by feature. RouteDFM plans the handoff when a part needs more than one family to finish. All three sit on top of the same DFM screening and should-cost engine as the rest of the suite.
One part, three questions, in order:
Priced by CostDFM — see the rest of the suite at partimation.com/#modules.
Get started
Plan a real part free in your browser, or book a walkthrough set up for your shop's strategies and machines.
Book a demo
We reply within one business day.