Skip to main content
Apr 30, 2024 4:03 AM UTC
Acknowledged

Surface Selection Group

Related products:Creo Parametric

1. What product and version are you running?

Creo Parametric 9.0.7.0


2. What is the problem?
It can be tedious and repetitive to select surfaces to add to an annotation's semantic references to support Model Based design.      It would be helpful if there were tools to create an manage "Surface Selection Sets" which could exist as a Custom Group to be able to be selected while defining an annotation or applying model color, etc...

There is a related selection tool improvement request which will help, but a "Surface Selection Set" capability would also be a good complimentary capability.
3. Are you using a workaround? If yes, please describe it.

No, just many many clicks.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
For a relatively small design I needed to select 267 surfaces to include a surface treatment note.  Then I will have to click that again to apply a special profile tolerance.   Then potentially again for surface finish annotations.   So we are over 750 clicks to properly semantic reference 3 (yes three!) annotations.   After chamfers and rounds are added, and having to click on both parts of the cylinder for each hole the clicks really add up.    
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Many, Many, Many clicks.   Repetitive and tedious clicks.   Taking much longer to complete a simple task than is necessary. 

5 replies

Apr 30, 2024 8:16 AM UTC
Status changed to: Acknowledged

Hi @N.Barnes 

Thank you for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

Apr 30, 2024 2:15 PM UTC

I never used intent chains or intent surfaces, but I guess that little known feature in Creo more or less might do what you are asking for.

To define the intent surface, a feature is created with the one time selection. Any further place that needs to reference the same selection, it only needs to click or search the feature with the intent selection.

N.BarnesAuthor
Apr 30, 2024 2:42 PM UTC

@S_Edgenear the intent surfaces is a good suggestion.   That will help.   

 

One issue I've seen from a few minutes of testing is that when the Intent Surface feature is deleted, the annotation the references the feature fails.  The annotations aren't included in the feature removal warnings.  Thanks again for the suggestion, its a step in the right direction.

 

May 5, 2024 12:17 PM UTC

Hi @N.Barnes 

In the referenced thread, I have shown one example where the DRF (datum reference feature) may be used for collecting rule based surfaces (collect all holes of radius=X) and then reuse them for annotation's semantic references.

 

In addition to that example, you can create the DRF as a "surface selection group" (as you called it) and then use this same collection as an input to any annotation's references or for coloring them. this collection may be rule based or user defined collection. its up to you. the DRF can also collect intent surfaces.

 

BTW in Creo 11 you no longer have to pick both cylinder halves as semantic references. picking one of them will automatically collect the other half for you 🙂

 

Given those comments I would like to know what might be still missing for you with the already offered tools.

 

Thanks,

Michael Fridman 

Creo Product Manager

 

N.BarnesAuthor
May 6, 2024 1:52 PM UTC

The initial Datum Reference dialogue box suffers from the common problem of not scaling.  If I make the box bigger, the list boxes don't scale.  (maybe this is addressed in newer versions of Creo?!)

 

The GUI for the surface sets isn't intuitive.  When initially opened the user has a box with included and excluded surfaces and an "Add" button.  The Add button adds a rule bases surface set, but they are shown in the same box with no obvious difference.    I think almost a "Query Builder" interface would be more intuitive.  Then I could use the surface selection rules to "Include this cut, but NOT these rounds in the cut".   Also a query builder approach doesn't need a "Individual Surfaces" and "Excluded Surfaces" category.   Just a groups of surfaces which have "AND" or "NOT" statements associated with them.

There should also be a way to explode the DRF, so that all the selections just become a list of individual surfaces. 

 

Regarding the available rules...

  • "Seed and bounding surfaces" I haven't gotten to work.  I pick the top of a boss and the bottom, the tool selects the entire part. 
  • "Surfaces of all bodies" works fine.   Probably being able to select the surfaces of a specific body would be nice.
  • "Tangent Surfaces" is ok for the part I tested, but I could see it getting out of control if a few extra fillets were added.   The "Neighboring surfaces only" option might help mitigate those problems. 
  • "Geometry rule surfaces"  are ok, but can over select.
  • "Shape Surfaces" tends to over select, sometimes is neat. Its not consistently good.

A zone select option would be nice.  Create a volume and be able to include or exclude everything within the volume.   Also the option to select crossing or inside the zone would be good. 

 

Include and Exclude surfaces need to have box select functionality.

 

The combination of Zone Select, Box Select, and Query methodologies would help manage issues of over collection.  Maybe I have a part with 2 patterns of 25 vent holes each.   Currently if I select all the holes with the same radius, I'll get both patterns.  But maybe I only want one of the patterns.  Being able to pick all the holes of the same radius which aren't in a specific zone would solve that.   

 

The problem that you'll always face with trying to make "automatic" rules is that all us customers want different things.  You can make a set of rules that works in a customer demo, but will then often struggle in the real world.   Maybe someday there is a future where we can train an AI on the fly to "pick everything that looks like this hole with rounds".  But, that will also take a while to be reliable.

 

One last item, the DRF needs to be error checking before the DRF is deleted or an edit is completed which will warn the user which Annotations are about to be broken.