Can someone provide me with some use case for reference features, aka intent objects?
I'm preparing an upgrade from WF3 to WF5, and rediscover the reference features,or do you have to say 'intent objects'. I once had a use case for it, but we never implemented it.
Thanks Doug and Kevin. I got one extra direct reply, stating more or less the same. I found some video's on the net,some of them using reference features (intent objects) to facilitate the placement of UDF's.
My conclusion until nowis that ProE knowsintent objects by default (e.g. intent edges of a protrusion). "Reference features" add the option to define your own intentions, explicitly as a feature.
If this is correct, than I'm still wondering about the practical value of reference features. Or my round is going into resolve mode, or my reference feature is. So, what's the difference? There is a conceptual reason to use them, but is this enough to bother about them?
Two extra considerations:
- I saw a video where a reference feature was defined based on a query. At least, that's what I think I saw, because the resolution wasn't to good. But I don't succeed to reproduce this.
- Reference features get a feature name AND an intent name!! I'm scrolling through the help files, but I can't find a decent reason to explain to my designers when to use this.
Anyway, thanks for reading until here, and hopefully I will understand ProE sooner or later, Hugo.
<< ProE WF3 M250 - PDMLink 9.1 M060>>
I'd like to try to clear up the confusion around Intent Objects. At a high level, there are two kinds of Intent Objects: the ones that the system creates for you, and the ones that the user defines manually.
The ones that are created by the system are what Doug described in the thread above. They are automatically created at the intersections of merged solid features, all side edges, start or end section edges, all side surfaces, start or end surfaces, etc. It's a great idea to teach your users to use these references when they can, because, as you learned in the thread above, they are very robust because they don't require a specific reference. To get to the Intent References, you need to either query select or Pick From List (RMB on a reference). A simple example of this would be to extrude a cylinder, then apply a round to the Intent reference that corresponds to the circular section at one or the the other end. Now go back and redefine the extruded cylinder. Delete the circle and draw a rectangle instead. The round will still be created on the edges at the end of the now rectangular protrusion.
Next we have the Intent Objects that the user defines manually. These are the Intent Reference Features, such as Intent Chain, Intent Surface, Intent Csys, etc. There are basically two uses for these. The first is to provide a single reference that collects a set of several references. The second is to provide automatic placement of a UDF.
If you have a scenario where you have several children that all refer to the same set of surfaces or edges, you can create an Intent Reference Chain or Intent Reference Surface that collects all of those references. If you need to change the set, you only change it once in the definition of the Intent Reference, and it updates for all children. By the same token, if it fails, you only need to fix it in one place.
Automatic placement of a UDF can also be achieved with Intent References. Basically, you can create named Intent Refernce Features on your model, and then design your UDF so that the placement references are Intent Reference Features that query for the names of the references to which they should correspond. The simplest case would be to place an Intent Datum Csys in your model with a name, then build a UDF around an Intent Datum Csys that searches for that name. When you insert the UDF, it will place itself.
I did a presentation on Intent References at Planet PTC Live 2012 in Orlando a couple weeks ago. It talks about the advantages of using Intent References over both simply selected references and rule based references. It also covers the use case of auto placing a UDF. I think I've seen the low res Youtube videos that Hugo mentioned. I think you'll be able to follow along with those videos combined with my attached presentation to learn the UDF auto-placement workflow.
Let me know what you think, I hope you find the presentation helpful.