Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Creo Illustrate : improvement of display "alternate part name" at eBOM tree - same way like at sBOMAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Illustrate 9.1 (productive) - 10.0 Testing2. What is the problem?The EBOS <-> SBOM Transfer is in our company driven by parameters where we collect in SBOM Child parts the designated operation's.In the SBOM they alternat part names - like "LINE NUMBER" can be displayed - while tranferring the items around - the EBOM should have same appearance acc. to the displayed names.3. Are you using a workaround? If yes, please describe it.NOPE - just hard work to evaluate Line number objects4. 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.Managing Operations (like work areas of assembly line stations) basically need the easy consume of attributes which should be available in both views (SBOM & EBOM) 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Number of users - in our enterprise >150loosing efficiency along the creation of SBOM - would think appr 10 Minutes more  per user and work instruction. => dealing with 10 files a month -> 150 files a Month in total -> appr. 16500 minutes a year (275 h = 1,5 man years)

Connect Windchill Notes to Model AnnotationsAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 7.0.9.0Creo View 10.0.0.0Windchill 11.2.1.152. What is the problem?There is currently no means of displaying notes associated to a part in Windchill inside that model.− Any arbitrary symbol in Creo Parametric should be capable of being linked to Windchill noteobjects.− Such symbols should, when interrogated, open a popup displaying that note’s text, without havingto open a separate notes/PL report from Windchill outside the model.− Note text should be snapshot and exported with those symbols when published as a PVZ, allowing those notes to be read in the standalone published PVZ on any device without a live link to the Windchill server.− General notes should also be viewable within linked models through some kind of method.3. Are you using a workaround? If yes, please describe it. The only workaround currently is to publish a separate notes list or access the Notes pages in Windchill, and open it alongside the MBD model.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.Why this is important:− Current practice requires manually referencing note numbers across different systems (Creo Parametric and Windchill). This leads to errors, increases authoring time, and increases difficulty when reading and interpreting MBD datasets.Ways to implement:− Symbols should have a “Note” attribute that can be designated for that annotation.− When activated, the symbol should fetch a list of all notes currently linked to that part’s WT, autofill the symbol value corresponding to the note number (e.g. selecting note object 1234567-N001 should autofill that symbol’s designated note number field with “1”), and the text of that note should be imported as metadata within the symbol.Visual Example:− A simple textbox could appear beside the symbol, displaying the note text stored in that symbol’s metadata (see attached image).5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Current productivity is hindered by having to refer to multiple files and sources to read notes, instead of being directly accessible within the model. 

Show All Model Annotations in Upper Data PanelAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 10.0.0.02. What is the problem? MBD may have annotations from lower level components shown in a given combo state.The Upper Data Panel’s Model Annotations tab is a very useful way to display a list of the annotations, but is only capable of showing one model’s annotations at a time.− In the example shown, multiple dash configurations are included in a MBD combo state.− The Upper Data Panel only shows the top level annotations by default, which in this case is largely empty.− Manually clicking on the lower level 010, 020 assembly models reveals the annotations for that subassembly, but these go away if you deselect the model.3. Are you using a workaround? If yes, please describe it. The user must know to select the different configuration assemblies individually.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. An improved and more intuitive method would be for the Model Annotations tab to by default show all annotations that are currently displayed in the graphics window.− The improved Model Annotations tree in this case would show the 010 and 020 as expandable trees listed sequentially, and would change only when the models in the Primary Panel are selected (see mock-up image).A recipe option should exist that publishes only activated/shown annotations to the PVZ.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Increases the chances of missing annotations.

Make Shrinkwrap quality more scalable to data size/complexityAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Automotive OEM with 500+ CAD seats. I´m responsible for CAD methodics. Stakeholders: Mechanical design, mockup, data exchange with other departments / supplyers using 3rd party CAD systems as well.2. What version of Creo Parametric are you currently running?7 & 83. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.This product idea is a response to PTC case C16442478https://www.ptc.com/appserver/cs/view/case.jsp?n=16442478 We use shrinkwraps (SW) for simplifying engine and transmission assemblies. Additionally it is a way to go for know-how- protection, too.We found out, that there is a dependency of surface quality of the resulting shrinkwrap and the amount and complexity and even bounding box of the regarded assembly.Even SW- quality can be influenced by some user actions, from a certain complexity of data sets, SW get a very poor quality. Please refer to case for some examples of surfaces before and after Shrinkwrap creation. SW quality gets a lot worse, if.......original assembly has more components,....original assembly has more complex components,....original assembly has a bigger bounding box, Test data shown below was provided by PTC.   Result with same settings but bigger bounding box: From a certain data size and complexity, for us, the result cannot be used für mockups in whole vehicles, as large surface sets are removed during SW creation. This leads to untrue distance measurements or even indicate free space where originally periferical parts are located but not shown.4. What is the use case for your organization?It would be great to have a new control option to influence SW creation method. Perhaps the amount of total / kept surfaces could be controlled by user, while classic options (e.g. "Level") keep same values, Last step is importatnt to us, as we must apply same SW level throughout all of our data sets. 5. What business value would your suggestion represent for your organization?....Better SW quality would deliver higher resoulution of result and showing the true shape of  assemblies....More "closed" surface regions in result.... Another key to control data size and resultion of SW... We could keep our deafault SW settings and apply them to all of our data sets

Automatically calculate optimal Minimum Element Size in Generative Topology OptimizationAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 8.0.5.02. What is the problem?The problem:  The minimum element size is critical to getting a good result in GTO, and, from discussions I've had with PTC, it needs to be the minimum thickness of the model divided by 1.5, or smaller.  You can get the minimum thickness from a thickness analysis.  There is no automation built in to the GTO tool, no documentation, information, or warnings.  Unfortunately all you get currently is strangely bad results. The solution:  A button to calculate the optimal (max), Minimum Element Size.  It would run this thickness analysis and do the math, and return the maximum usable value.  If your entered value is out of range, it should accept it, but also flag it with a warning and more information.3. Are you using a workaround? If yes, please describe it.Running the analysis and doing the math manually, with an internal wiki page describing the solution.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.Running a long optimization only to get unrealistic results, such as objects floating and disconnected while said to support a load is just wasted time when there is no warning in the software that the minimum element size is outside of the known good range, and how to find that good range is also not published.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)It has negatively impacted adoption of, and trust in, GTO, because results are often bad and unusable.  Fortunately this has kept lost hours low, but only because people aren't using it.

File Open dialog: keep search results after changing the File Type settingAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 7.0.x.0 untill Creo 10.0.x.0, and Creo+2. What is the problem?If you enter something in the Search-box in the File Open dialog and then change the selected File Type (eg. Creo Files to STEP) , the displayed (filtered) result list is reset according to the chosen File Type but you have to re-enter the information for which you were looking for in the Search-box.A (simplified) demonstration of this issue can be seen in the video below: I am looking for parts that only have the word "part" in.If I enter the information in the File Name box and change the Type, the entered keyword is erased.When I search for 'part' using the Search-box and then change the Type, all files that belong to the selected File Type are shown but the list isn't filtered anymore based on the information entered in the Search-box - even though the entered keyword is still shown in the Search-box afterwards(view in My Videos)3. Are you using a workaround? If yes, please describe it.N/A4. 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.Most companies use long filenames, so if an engineer is looking for a specific assembly/part by entering a keyword in the search box then he/she could change the file type to narrow down the results which will make retrieving a specific item much faster, 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Increased productivity