This is a question that many engineers have faced when evaluating various types of "add on" functionality to their existing MCAD system. Whether it be CAM, FEA, CFD or PDM, there are many options out there.
Depending on the level of sophistication, the answer to the question is not so easy. Let's take PDM, for example. It makes sense to me that users should be able to check things in and out of the vault, have full revision control etc all within the CAD environment.
How about CAM? The question gets a little more complicated. How much will users be using the CAM software? How complicated are the parts? Will the users be driving the CAM software daily? If you have to think twice about any of these, then it makes sense to consider whether or not the "CAD-embedded" solution has all of the bells and whistles you'll need.
Now, how about FEA? Let's take Pro/Mechanica for example. It was one of the original fully embedded FEA programs out there. PTC acquired RASNA and tightened the integration. Mechanica always stuck to its roots. P-method, liner static analysis with steady state thermal capbilities. Nothing more, nothing less (for the most part). So, in this case, if it fits your needs and you are a Pro/e user, makes sense to go the CAD-embedded route.
Let's look at COSMOS/Works. They have done quite well for themselves by embedding inside SolidWorks. But there was always this option to "upgrade" to the full suite, COSMOS/M. Now that SolidWorks owns the former SRAC, it is probably not as much of an issue as they are focused on the full product within SW. But suppose SW didn't purchase SRAC. Users risk that there will be a disconnect between the two different development teams. Now in this case, there was a happy ending.
But now, suppose the SRAC folks had an agreement with SolidWorks, Autodesk and UG? Can we count on the fact that they have a close knit relationship with all equally? Do all of their graphics work the same? Is their UI framework flexible enough to be embedded in all of those systems equally? SRAC made a smart decision. They picked one, focused and delivered. In this case, they made a smart pick. Good for them!
There are many companies out there that claim that their solution embeds in all of the CAD tools. Some even claim to have an upward path to their "flagship" offering if your needs grow beyond their embedded capabilities. Yikes! How focused are the vendors on their CAD embedded solution? Is it just a marketing campaign to claim "me too"? These are the questions I would be asking.
Point is, is CAD-embedded all that is cracked up to be? It can appear to have its advantages. But I wouldn't let it sway my decision. I would put it in the nice to have column.
Consider these points when making the decision whether to go with CAD-embedded.
Is the CAD embedded tool developed and owned by the CAD vendor? If the codes are not developed by the same people, there is bound to be a disconnect.
If you want to run a CFD analysis, for example, does it occupy your CAD license?
How many products does the vendor develop? How much of their focus/$$ comes from the product you are evaluating? Is it their bread and butter?
Don't be fooled by the carrot of CAD-embedded with promises of an "upgrade" path.
Check out this cooling fan model I have been working on, cool stuff.
No comments:
Post a Comment