Skip to main content
Feb 16, 2023 12:45 AM UTC
Acknowledged

Enable more parameters in manufacturing for use in relations

Related products:Creo Parametric

I am a user of Creo 8.0.7.0 Manufacturing

I have been using PTC Manufacturing software for 20 years and have hit this limitation of the software many times, recently the topic has come up via the PTC community proving I am not the only one having the same pain.

Within manufacturing there are many parameters but not all can be used/referenced for relations, enabling access to more of the parameters (that we know exist) would allow for a higher level of automation and improved consistency. POCKET_NUMBER is an interesting example, it is very valuable to manufacturing, it represents the tool # for the CL data generated but it is a little mysterious in the way it exists and that is OK, we would like more of these. If it is not possible to enable all parameters (model tree, process manager, PPRINT, XML templates, Pro/Report) to be used in the relation editor perhaps as a group of users we can build a list, here are a few to start:

•STEP_NUM – the NC sequence number, Step # in process manager

•FEATURE_ID – this can be output for PPRINT but not accessible in any other way

•NC_SEQUENCE_NAME – another that can be output via PPRINT but not accessible via relations editor

•TYPE – this can be added a column in process manager and lists the NC Sequence type but cannot be referenced

•OBJECT_ID – this is a column that can be added to the process manager

•AXES – 2,3,4,5 this can be added to the process manager

•NC_SEQUENCE_CSYS – the pro/report symbol is &mfg.oper.ncseq.csys and MFG_NC_REF_STEP_CSYS is the parameter in an exported XML template or ORIENTATION column from process manager

•NC_SEQUENCE_RETRACT – this is also a column option in process manager

•COMMENTS – this column can be added to the process manager but it would be nice if we could populate with a relation

4 replies

Feb 17, 2023 8:03 AM UTC
Status changed to: Clarification Needed

Hi @BryantMorgan!

Thank you for publishing your idea. However, we need more information as specified in the form you saw in the submission process. (questions below). You may simply add a comment to your idea. The more details and context you give to document your idea, the better. Think about ways to educate and convince other Community members to support your idea and present your case to the product management team for consideration.

Please let us know within the next two weeks.

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
2. What product & version are you currently running?
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
4. What is the use case for your organization?
5. What business value would your suggestion represent for your organization?

Additionally, I invite you to check out this topic where PTC executives explain product managers' approach to customer ideas and input for product roadmaps.

Feb 17, 2023 6:20 PM UTC
  1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
    1. Industry = Aerospace and defense
    2. Role = NC Programmer
    3. Stakeholders = Tax payers, Management, Engineering customers, Machinists
  2. What product & version are you currently running?
    1. Creo Parametric 8.0.7.0 – NC Complete
  3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
    1. Relations are very powerful and can be used for many different things but are limited by what parameters can be referenced/accessed.
    2. The current auto generated names for NC sequences is not very informative and the naming convention contains spaces which cannot be reproduced
    3. Many NC sequences share parameters of the same name but acceptable values are different = SITE file can’t be used to set
    4. Would like a consistent\unique\meaningful name generation for CL files output
    5. Would like to work away from pro\process generated tables and work towards annotation elements and 3d PDF’s for reporting
    6. Process manager columns and model tree columns are not completely in sync
  4. What is the use case for your organization?
    1. Too much time spent on administrivia – typing in information to name each NC Sequence in a meaningful way, add comments, etc. I estimate this could be as much as 10% of the time taken to program a part, with the proper access to existing parameters relations could be used to automatically populate this data in a way that is unique (because defining a unique value can often be a pain point) and consistent.
      1.     I often name an NC sequence based upon the “Orientation+NC Sequence+Number of Axes” Type and if a unique value was accessible like STEP_NUM or FEAURE_ID it seems that this could be automated = NC_SEQ_NAME = Orientation+NC Sequence+Number of Axes+FID
      2.     Some details that are not accessible via relations/parameters can be output via PPRINT statements but the formatting is limited, if COMMENTS could be driven with relations and parameters were accessible the comments could be better formatted and similar data could be passed as with PPRINT
    2. Some NC Sequence level parameters are used for multiple/all NC sequences but the acceptable values vary by NC sequence type – RETRACT_OPTION for instance – has different values based upon NC Sequence type = this means you cannot set a relation or default value via a SITE file. A global relation with some logic might be an option IF a parameter was accessible that defined “NC Sequence type” and “Number of axes”.
      1.     My current work around to address this issue is to have predefined NC sequences in my startpart for each type of toolpath so I can copy/paste each with parameters set and relations defined. IF more parameters were accessible I think I could create relations to make smarter NC sequences and reduce the size of my startpart and data sets.
    3. This conversation began on the PTC Community discussing a way to automate the naming of NCL files that are output based upon NC Sequence number or STEP_NUM – this is a unique value (per mfg file) it is a dynamic value that can change as the NC sequence is re-ordered in the model tree, it is a quick/easy value for a machinist to reference when communicating about an issue, it can also represent the order in which to run programs – unfortunately it is not an accessible parameter that can be referenced for relations.
    4. There are parameters that are only reportable on a drawing via pro/report symbols – how do we access these if we want to use annotation elements and eliminate the drawing? These parameters need to be accessible at the assembly level
    5. Of course access to additional parameters could benefit family tables too, allowing for parameters to be generated/modified using table (excel like) format
    6. Any feature level parameter can be added to model tree or process table as a column, this could increase consistency between the two
  5. What business value would your suggestion represent for your organization?
    1. This suggestion is beneficial to all users of the software (more than just mfg), the benefits are not limited to my organization. My organization would benefit from a time savings = reduced NC programming costs, increased productivity via automation, performance gains as a result of smaller data sets and greater consistency which will improve communications.

BryantMorgan_0-1676658012191.png

 

Feb 20, 2023 8:43 AM UTC
Status changed to: Acknowledged

Hi @BryantMorgan!

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.

Thank you!

Feb 21, 2023 4:33 AM UTC

I have known Bryant for the entire 20+ years that he has been using the NC module of this software. Since he was new to the software he has tenaciously sought improvements and has been a loyal PTC customer. He has always been willing to suggest improvements, no matter how frustrating the process may be (i.e. enhancement requests, technical committee participant, PTC/User presenter, etc.). I support any improvement that Bryant suggests and that would no doubt be an improvement to the software at any level of usage whether the user is new to Creo or a longtime user such as Bryant. I sincerely hope that his suggestion is taken seriously by development.

Terry Smith