Very, very, very good thread and great comments.
I learned a lot.
No-one mentioned CATIA ?
First 3D CAD I learned, about 35 years ago.
And CATIA is well rated, although the typical users are aerospace and automotive, and their particular myopia may have a big impact.
Food for thought..
some want 5ax parts that look extremely good and hold decent tolerances (0.01 mm, less, volumetric) on high-end machines.
Qty 20-ish.
some want a few very very high-tolerance features, on their parts, and traceability is a big deal.
some want the flexibility to make a large family of parts in various flavours and sizes, sometimes with extra whizbangs.
some want good easy integration into the IT part, for sales/docs/liability reasons.
some want high volumes of same or very similar parts with minor feature mods
some want good production via better toolpaths
All above use cases are possible "core requirements" easily worth 40k for a single seat of sw of whichever flavour, when/if the parts are the typical very high value contracts.
I suspect most of these high-end packages could do any of the 5-6 use cases, decent-to-well, sometimes very well.
In some cases it would be far too difficult, or laborious, to get that "best possible result" bar none -- but a nearly-optimum result is probably quite easy, and quite fast to do, by someone truly expert in it.
My opinion:
No slight.
Talking as an analyst and 3d cad expert of 40 years.
My "feel" is that almost no users of any package can truly optimise any of the 6 scenarios, on any other sw package mentioned, apart from the one they most work with.
And that probably the best result anyone gets is only perhaps 70-80%, often 60%, of the best result available if the sw was truly used as well as is possible.
Competition:
Best cad + cam, advanced:
I would very much suggest a common contest from all You guys.
Make 3-4 simplistic fantasy parts with your favourite good or bad or hard part feature in it.
Everyone gets to want or add features..
and everyone makes at least that one model part on their favourite system.
All should share the model universally, full-res native and iges.
How long did it take to model ?
What are the critical features ? .. and how did You do them ?
Critical, imo:
How accurate is the model, in 3D.
--Whats the resolution, vs accuracy ?
How large is the native file, and the IGES.
E.
Simplistic things like high-pressure 300 bar (1000 bar ??) couplings with a mate like a flat boss (o ring), could be an example.
5x5x10 cm.
Thread form, root-crest-taper, thread end, manufacturability, efficiency come to play.
Can the sw make the part in a 5ax mill turn via turning, rolling, whirling, grinding ?
What are the accuracy constraints of each process, if any ?
Can the sw gage the part, via go, nogo, probe, or something else ? and how easy and fast ?
How long does it take to setup for machining in sw package "x" ?
And to what level in terms of tooling and accuracy and production.
In whatever machine+tooling one has available.
--
It´s fantasy parts.
No-one is losing any work, and EVERYONE will get vastly more efficient if 4-5 top guys share actual data.
EVERYONE may get a big lever to get their sw VAR to give them extra features, training, and swag, because obviously their sw lags on aa, bb, cc ..
EVERYONE may get a realistic appreciation of how sw "xx" works vs what they are doing now.
It´s like one of my long-time challenges :CAD.
"Model a ballscrew, including ogive arch".
E 25 x 5 mm, 200 mm OAL, == 80 mm usable length.
??
How does the thread end,
is it manufacturable,
will a mill-turn make one in one go,
how big is the native/iges model,
whats the real accuracy and resolution,
is the ogive arch how good,
how long did it take to do,
whats the native and iges filesize.
A:
About 3-5 hours first time to do,
20 MB file,
1 micron real resolution,
manufacturable with tapered out thread,
using an invented ogive arch of 1 micron modelling accuracy.
In 10-20-30 hours I could make a family of parts, using programming and a labelled model and an excel sheet to feed screw data of length, rise, thickness, with thread taper being a big part of the work.
I did something similar, first time took 4-5 days, learning the programming language.