Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Kinematic information exchange via STEP AP242 XML-formatAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We are an OEM car manufacturer; 500+ CAD-users; I´m responsible for CAD methodology.Stakeholders for this topic are e.g. our poduction process planning department and corresponding suppliers (tool and machinery makers) and design departments.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.In various applications, the presentation and execution of kinematics are essentual components in order to be able to make the right decisions (e.g. mockup visualization). Often, different software with their own proprietary data formats are used. So far, this often leads to the manual and subsequent implementation of the kinematics for each application.  To avoid huge additional effort and data inconsistencies along the process, it would be a great benefit to use the neutral data format STEP AP242 XML in creo to transfer  kinematic information between different software products.4. What is the use case for your organization?Uniformed data kinematic exchange between different software applications and parties5. What business value would your suggestion represent for your organization?Kinematic information available throughout whole process chainLess manual effort for reworking data at system-switches (different software)No data inconsistencies as using unique data format even in case of system-switches

New ModelCheck IdeasDuplicate

Below are a list of some of the items on our company checklist that are not covered by modelcheck. We would like to see some of these implemented. I know some have their own product idea, but I'm throwing everything in here:   No Weak Dimensions All Orphaned Dependencies Broken Features set to Read Only Any un-embedded datums or sketches should be named No 0 dimensions for scenarios where they could be constrained to coincident (in sketches, holes, datum planes, etc) Only Locked Dimensions, where applicable All dimensions should be named when used for relations or family tables All features should be named for family tables Sheetmetal flatpattern won't fail No nested family tables Patterns should be set to Identical, where possible, instead of General Remove unnecessary relation comments Any sheetmetal features not using the default sheetmetal parameters for bend radius, etc... First Assembly component that is externally referenced First Assembly component that is not using default or coincident with default datum planes Checking subcomponents in assembly for proper naming convention Checking subcomponents in assembly for proper parameters (windChill location, based on naming convention and release state) No Assembly Cuts Assembly not to be in Exploded View Assembly not to be in X-Section View Drawing/Annotation Notes to only be used from a certain list, where the notes contain more than one line Drawing General Views to not reference Geometry Model Name should be the same as File Name and Number (3 columns in WindChill) . I had to create a separate idea for this...   In addition: Better Support for use-case scenarios where some instances of family tables are released and others still being worked on or tweaked from the generic's family table. How can we run modelcheck without flagging all instances as modified. Allow an option for ModelUpdate or Custom Checks to go to the ALL tab by default Allow mapkeys to work within browser pages and change the ModelCheck tab/buttons Allow condition file to incorporate more than 2 statements and include multiple AND/OR with parenthesis Allowing the condition file to see information about the drawing's model (parameters, model type, etc) Update HTML look to be similar to WindChill 10, like the current looks like WindChill 9 Have the condition file be able to not add parameters or add parameters based on certain situations (will help the family table scenario above - for generics) ModelUpdate run on other modes besides Interactive Check for Material Names that should NOT be using ModelCheck be run from within WindChill (like the View addon can create dxfs...) ASM_CREATE_VIEW ability to create ISO views - more complex views EXTRA_LAYERS - Allow for a list of layers to be in the layer tree, without forcing its creation, such that everything else can be deleted PRT_PARAM_MAP won't actually map if PRT_PARAMETER is also available for the same parameter STD_DRW_DTL_FILE based on model units OVERLAP_INFO - Support Geometry lines, not view border UNUSED_SHEETS to support formats MCREGEN_VERIFY_FT_INSTS for parts as well (see above about released instances) DIR_REPORT to be a separate location than the actual HTML files for the ModelCheck browser. Any non-local path will fail give an error when running modelcheck Move out as many config.init options to another location that can be modified while running Creo AND can be set with a condition.init MATERIAL_NAME support for subfolders in the material library. 9/5/17 - Allow ModelCheck reports to be added as an attachment to the CAD Document in WindChill automatically. 10/18/17 - Have the Circular reference error actually spell out what is wrong and what the loop is. At LEAST using the same words as the .crc file. We would appreciate better wording than the .crc. Currently it just lists the model, which is very confusing and doesn't help much. The Creo 4 notification window doesn't help much in this area as well. We need to move away from the .crc file to debug circular references. Modelcheck AND the noficiation window should be better used for this.   From Comments Below: mlockwood-2‌ - ModelUpdate option on a per-check basis (buried features to not be deleted) especially since buried feature check is more wrong than right... (And Erased Views)   I'm sure there is more that I'll think of later. But this should be a good starting list

Sheetmetal pattern/reference functionality doesn't work like the regular moduleAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo user community.  2. What version of Creo Parametric are you currently running?8.0.5.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.Reference: Case: 16087371 SPR: 13261009       In our PCB Board start-part, we have ecad areas for the annular rings around PCB mounting holes. These ecad keep outs are on the top and bottom of the PCB. We create an ecad area on one side, referencing the hole. Then we create the ecad area on the second side and reference the first ecad area. We group the 2 areas and reference pattern it to the PCB holes. This works great in the regular part mode. However, in the ECAD module (which is using the sheetmetal code), it doesn't work! According to PTC and R&D, ECAD areas that use projected curves cannot be reference patterned. This seems like a full-on bug to me. If it works fine in one module, yet it doesn't in the other, that can cause frustration and confusion with the user-base. Can we get this fixed? See attached for sample files.  4. What is the use case for your organization?Our organization designs hundreds of products a year, all with PCBs. We are trying to extend our usage to the ECAD module, but we keep on hitting bugs, like this one, that prevents us from using it the way we need.5. What business value would your suggestion represent for your organization?This would get us closer to use the ECAD module, which would bring benefit to our organization, whether through the IDX collaboration standard, or it's ECAD capabilities.   Thank you   @Alex_Y 

Keep Creo Simulate results window openAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Space industry, senior CAD and systems engineer, Our company and customers2. What version of Creo Parametric are you currently running?6.0.6.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.In when performing an analysis on a component using Creo Simulate, through Creo Parametric, one can view the Results window. However, one is forced to close this window to go back into both the Simulate environment and to the CAD environment to make alterations. It would in many cases be good to have the results window open when going back to make changes, such that one can look back at the results window to see where these changes should be made.As a second step, one could envision a "Refresh" button in the results window that reruns the associated analysis and updates the results accordingly. A dialogue box can inform the user of the time it took for the previous analysis, as that is available in the analysis results in order to make an informed decision on continuing with the refresh or not at that time.4. What is the use case for your organization?Every new component and assembly that is designed5. What business value would your suggestion represent for your organization?It could shorten the time needed to develop a product.