Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Creo Drawing Table ImprovementsAcknowledged

 Very confusing interface.Needs lot of learning and practice to use.Improvement needed is : It should be as simple as Excel or equivalent.1. What product and version are you running?I use Creo 9 and Creo 10 both. Have used all ProE and Creo versions starting from ProE WF-32. What is the problem?Creating and editing BOM Table takes lot of time. Being an old Pro user, we can manage it.But new Users does not like the old school method of adding and editing tables in Creo. New Users are more familiar with the new intuitive UI based and dropdown based editing rather than selecting options through Menu manager. They always compare it with Solidworks BOM table.Even Autocad now has improved the table creation. In Creo it is still the same older method and no improvement after this many years. BOM is something where engineers spend most of their time and it should be easy and fast, mostly for new beginners. Because Pro-users are not  immortal 😁. They will be replaced with new users and they will require GenZ approach of managing all things. So improve and enhance what is important. 3. Are you using a workaround? If yes, please describe it.We are managing and training new people to accept it and forcing them to become use to. Because, i don't think PTC product development team is interested to improve it.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. As i said in my problem statement, this improvement is required since long and no action is taken till now. I am also surprised that no idea is still submitted in community.This will be really helpful for new users to accept the product.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.) Being a PTC Partner, we are getting lot of support calls on this from our customers.They are always complaining about the product improvements.This affects mostly to the new Creo Users, as they have the reference of other tools where it is done easily.Many small customers are creating BOM from standard table formats available in CREO and using it to just export BOM to CSV and then editing BOM in Excel file. They are not able to use it extensively with all functions because of tedious workflow. With all such small improvements, which are not addressed, PTC Creo is loosing its edge against competition.

configurations that can control shared models differentAcknowledged

1. Describe the ProblemShared models are the same models. So it is impossible to display them in different configurations. Also if 2 shared assemblies are contained in a main assembly, it is impossible to display them in different configurations. Like displayed below: The main assembly "Layout" contains 2 shared assemblies: "Bgr_1" and "Bgr_1.1". Both shared models have 2 configurations.Konfig_1_mitte:Konfig_2_oben_rechts:The main assembly cannot display "Bgr_1" and "Bgr_1.1" with different configurations. By merging or activating configurations both sub assemblies "Bgr_1" and "Bgr_1.1" can be displayed either in configuration "Konfig_1_mitte" or "Konfig_2_oben_rechts". The product idea is the possibiliy to merge different configurations of shared assemblies. So you are able to display the main assembly "Layout" like: 2. Are you using a workaround?There is no workaround.3. What is the use case for your organization?We develop configurable machines with automations. Machines can be assembled different to the automation, but being the same machine. Therefore we use the configuration to display the different mounting positions a customer can choose from. If a customer wants 2 machines but mounted in 2 different ways to the automation system, the visualization can be controlled via the configuration option.4. What impact does this problem currently have on your organization?A lot of time needs to spent to place every part with the selective indepent feature. Otherwise we are not able to plan whole smart factories with mutlipe machines in different customer variations.

Toolkit API for surface finish value and other propertiesAcknowledged

1. Description of the ProblemFor surface finish annotations, we are currently using the ProSurffinishValueGet() function to retrieve the associated property.However, we have observed that depending on the symbol type (e.g., ASME or ISO), the function does not return the expected values. Specifically, the roughness_height field is not available in some cases, and other fields such as surface_texture_requirement may contain only text values.Would it be possible to obtain the roughness height value (as a double) directly from surface finish annotations, such as those shown in the attached image?Additionally, we would prefer an API that is specifically designed to access this data, rather than extracting it from general symbol instance properties.Below is an example of a surface finish symbol where the function fails to return the expected value. 2. Are you using a workaround?No, we are not using any workaround at the moment.3. What is the use case for your organization?We need to validate surface finish information within our software.Specifically, we need to extract detailed data such as the surface roughness value, material, orientation, etc., for downstream processing and quality control.4. What impact does this problem currently have on your organization?We are currently unable to store sufficient information in our formatted files due to the missing data.At the moment, we are only able to retrieve the correct double value when using generic/standard.sym symbols.

Change Start Part Template for Existing Parts for easier MBD ImplementationAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?CREO 8.02. What is the problem?Our company is in the early phases of implementing MBD. One of the issues we are finding is that we can not change the "start part" template for already existing parts and assemblies, which means we have to create all the combination states (following MIL-STD-31000) for each existing part. For new parts, it should not be an issue if we change the company "start part" template to match the MBD "start part" template, but for older parts it is a pain to have to recreate all the combination states, unattached notes, title block, etc.... Can we please create a way to either:1. Copy a part (Save as) and give the option to change the start part. OR2. Be able to import combination states with all the notes, title blocks, etc.Both options seem better that recreating all the combination states from scratch for existing parts.3. Are you using a workaround? If yes, please describe it.Only work around I know of is either re-creating all the combination states from:1. Doing it manually. Very tedious.2. Creating a complex macro to create all the combination states with all the notes, title blocks, etc.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.Please see question 2. I pretty much answered that question there.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Ton of hours lost in productivity due to creating all these combination states for existing parts (parts designed using the old start part template - non MBD) and the higher ups in the company are starting to look on the process of MBD as a huge burden instead of seeing how it can help us retain design intent and in the future require less work.

Add a search function (Ctrl+F) to the menu for playing the toolpath (Manufacturing)Acknowledged

1. What version of the software are you running?Creo11   2. What is the problem? An offer to the CREO developers to add a search function to the menu of playing the toolpath by NCL-file (Manufacturing). This function is very useful for postprocessor developers and search for specific strings of NCL-file in the play menu. The problem is in the analysis of the postprocessing result.After postprocessing the ncl file and subsequent analysis of the *.lst file, it is sometimes extremely difficult to find the problematic CL record found in the *.lst file in the toolpath playback interface (graphical representation of the trajectory). For example: It is necessary to examine the CL-record in the *.lst-file after postprocessing2321>GOTO /-24.61144,20,-75.18996,0,1,0which is presented by the postprocessor as a sequence of blocks:2321 2322 2301 CC X12.632 Y108.216$2321 2322 2302 C X-24.611 Y75.19 DR-$ It is necessary to find this CL-record2321>GOTO /-24.61144,20,-75.18996,0,1,0when playing back the CNC program and track the position of the tool graphically relative to the workpiece. If the toolpath player had a CL-record search, then in the CTRL+F window you could enter the phrase: GOTO /-24.61144,20,-75.18996,0,1,0   + Ctrl+F   I don't think this is that hard to do, and for large NCL files it would be very useful! 3. Are you using a workaround? If yes, please describe it.Yes, we do. We save the CL file, and then manually find a similar entry in the trajectory player window for a very long time.   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.See p N2. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)This problem increases the time it takes to find postprocessor errors by 300…500%. The number of users depends on the number of workstations at the customer’s enterprise: from 4 to 100 workstations.  

update the standard in Windchill;withAttributes, without deleting this standard from WindchillAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo illustrate 11.1 Abillity to Save your illustrate company standard to Windchill as a *.pvsf file 2. What is the problem?When adding Windchill Attribute information to e.g. Callotuts, this information is not in your ADMINtool. So you will have to use Import. The problem is that you must delete the current standard, from WIndchill (!!), import the updated standard from the latest c3di file and save it back to Windchill. This will start a comple te new Version (A.1) instead of promoting to a new itteration or Version! 3. Are you using a workaround? If yes, please describe it.Workaround is to use revision Management in the file naming, Wouw.... just as not using PLM! Or just not use the Windchill system but stay with the current method for ci 1 - 10.1  Shared_Prefs in EV4. 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.What i would expect is that you can- check out the standard- import the new standard / import the changes items in the standard with containing attribute information- check in the standard. This way you have an PLM revisioned , updated standard for creo illustrate with adittional attribute information. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Useless updates feature for all users over the world

Creo Relations Add ELSEIF for IF statementsAcknowledged

1. Describe the Problem Creo Relations IF statements are missing ELSEIF or ELSE IF ability: https://support.ptc.com/help/creo/creo_pma/r11.0/usascii/index.html#page/fundamentals/fundamentals/Conditional_Statements_in_Relations.html   Most languages have ELSE IF (ex: C# https://www.w3schools.com/cs/cs_conditions_elseif.php or C++ https://www.w3schools.com/cpp/cpp_conditions_elseif.asp)   ELSEIF provides: Less verbose relations that are easier to read and write (see example below). Clear intent that only one of these IF, ELSEIF, or ELSE statements should be evaluated. Potentially faster evaluation of the relations. If one of the IF or ELSEIF statements are met, none of the remaining ELSEIF or ELSE statements need to be evaluated. Presumably Creo would use ELSEIF (without a space) to match the lack of space in the current ENDIF.   Current workaround 1 (lots of separate IF statements): Not always clear if only 1 of the IF statements should be evaluated (this simple example is clear). IF d1 > d2 length = 14.5 ENDIF IF d1 < d2 length = 9.0 ENDIF IF d1 == d2 length = 7.0 ENDIF Current workaround 2 (IF statements nested in ELSE statements). This can get VERY hard to read on more complicated examples. IF d1 > d2 length = 14.5 ELSE IF d1 < d2 length = 9.0 ELSE IF d1 == d2 length = 7.0 ENDIF ENDIF ENDIF Future Relations using ELSEIF: IF d1 > d2 length = 14.5 ELSEIF d1 < d2 length = 9.0 ELSEIF d1 == d2 length = 7.0 ENDIF The ELSEIF example above is easy to read/write and is clear that only 1 of the LENGTH= statements should be evaluated. 2. Are you using a workaround?See above examples of workarounds lead to some very complex relations that are hard to read or write.3. What is the use case for your organization?Easier to read and write clear ELSEIF statements. The current workarounds above can get VERY hard to read.4. What impact does this problem currently have on your organization?Extra time reading / writing relations. Lack of clear design intent when reading or writing relations with current workarounds.

Unused Models in DrawingsAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Design systems / assemblies to address client challenges - from initial concept to delivering final product. 2. What version of Creo Parametric are you currently running?83. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Unused models in drawings can only be deleted one-at-a-time from within the drawing and are only accessible from an old antiquated DOS-like menu.  Unused models can accumulate from drawing revisions and if a drawing is copied and views are edited.  You may not even know you have unused models that are taking up memory.  And if you do know there are unused models in your drawing, it takes an inefficient use of effort and time to remove them.  Modelcheck can be used to strip unused models from a drawing, but that's another step that shouldn't be necessary.  Suggestion:  Modernize the drawing model selection menu and add the ability to select multiple unused models to delete and/or the ability to delete all the unused models at once.   4. What is the use case for your organization? Unnecessarily excessive file size uses additional file space and takes time during the drawing phase to manage.5. What business value would your suggestion represent for your organization?More efficient use of file storage space and less time necessary for a project.

Create or Redefine Simplified Representation WITHOUT Activating ItDelivered

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric (7.0.9.0, applies to all versions)2. What is the problem?I can open this model in an empty simp rep, open the simp rep manager, and create or edit a simp rep--all without loading any 3D CAD. But if I want to get past this screen, my only choices are to Open (saves the simp rep definition and opens it to the graphics window), Cancel (undos any changes I made), or Apply (opens it to the graphics window but does not save the edited simp rep definition). This feels like what was most likely an oversight in the original UI design and was just never properly addressed, I should be able to just press something like "OK" and return to the previous screen without being forced to load all those models.3. Are you using a workaround? If yes, please describe it.A full workaround is not possible. While you can modify simp reps from the model tree to avoid the dialog window mentioned above, you can only choose default (e.g. Master, Exclude, Automatic, etc.)--not user defined--simp reps this way.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.Every designer working with assemblies (which is to say, all users of Creo Parametric) would benefit from being able to modify simp reps without activating them in the graphics window. For large assemblies, this would present massive time savings.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)In our organization of several hundred Creo Parametric users, everyone spends countless cumulative hours dealing with this issue. I could not accurately put a number on it, but it easily surpasses 1,000 cumulative hours per year across the enterprise spent waiting for Creo to load our massive assemblies, when we don't necessarily need to open the model after making those simp rep definition changes.

Eliminate Creo View Login when already logged into Windchill browserAcknowledged

1. Describe the Problem User's must log in again when launching Creo View from an already signed in session of Windchill.  The second login was not required with Internet Explorer.  This is very frustrating for users to log in twice. 2. Are you using a workaround?There is no work around to making the user waste time log in to open Creo View from an already logged in session of Windchill. We have entered Case C17831347 with Tech Support for reference. 3. What is the use case for your organization?This applies to all organizations that launch Creo View from Windchill. In Internet Explorer version of Windchill and Creo View Interaction, User launches IE, goes to Windchill address and logs in. Finds a representation and uses open in Creo View and Creo View opens WITHOUT additional login. In Chromium Browser(Edge, Mozilla, Chrome), user launches browser, goes to Windchill address and logs in. Finds a representation and uses open in Creo View and is AGAIN presented with the same popup to login. Remove extra button clicks!4. What impact does this problem currently have on your organization?Extra steps cost money and time. There are some times when the popup gets hidden behind a window and a user has to search to find it. assume 40 users launch Creo View per day, 40 clicks/day or 10,400 clicks per year. 5 second impact each time. Using $87/50/hr rate -> $1,264 per year. Every PTC organization (~100). $126,389 impact. Also take into account the frustration of users having to log in twice. This should not be underestimated.