Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Notify the user for ECAD assemblies that assembly needs to be updated - no longer parametric!Delivered

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.4.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Reference: Article: CS366849 Case: C16336356 SPR: 13742708   In a typical parametric assembly, if a component is placed using a surface or datum, and then the component's surface or datum is changed, it will automatically update the placement. Apparently this is not true for some use-cases regarding import of EMN/EMP data (from the IDF standard of ECAD MCAD Collaboration). This makes the functionality not parametric in a parametric tool. And there is not even a notification to the user. Even an advanced user would not think that the component should have been adjusted or something is not right. The shocking response by R&D is:   An ECAD assembly is a special assembly that contains many parts and is more complex, especially with many hole features. Editing features such as ECAD holes affect the performance of the software, so in order to avoid the performance problems, the automatic update results in the ECAD assembly are intentionally shielded   Please have at LEAST some notification that the user needs to manually update the placement. 4. What is the use case for your organization?Our business makes hundreds of products a year with PCBs. We have strict mcad libraries and collaborate using the IDF (and sometimes IDX) standards. We would like to avoid these 'surprises', when one use case out of thousands behave differently and now there are issues because of inconsistencies in the tool. If there is a good reason to not have it update, the new notification center needs to notify the user.5. What business value would your suggestion represent for your organization?It would allow us to use the modules and capabilities (ECAD MCAD Collaboration) for us to efficiently and quickly design our products. Otherwise, issues could occur and be found in production, causing a down line, and a complete redesign. If an assembly is not fully regenerated or changes still need to be reviewed, it should not be released.   @Alex_Y 

EMN Export to use the Creo design ECAD_NAME and ECAD_ALT_NAME and the not the ECAD_HINT.MAP valuesDelivered

Please include detailed documentation such as screenshots, images or video.1. What version of the software are you running?8.0.8.0 2. What is the problem?Reference ticket: 16962068  The ecad_hint.map file is being used as the default information to map our components (mostly as assemblies) while EMN files are being read out and written into Creo. However, if the design data is using a slightly different variant of the ECAD_NAME, Creo will STILL export using the name in the ecad_hint.map file. This should not be! It should use the name in the design file itself. Whenever the ECAD tool opens our EMN file, it gets flooded with warnings saying that the package name has a mismatch. We can't remove the component from the map file because we need the map file to map to the correct assembly model. If we put a wildcard ECAD_NAME "*", the ECAD tool still generates a warning:  The PCB designers can't read through hundreds or thousands lines of their warning log, trying to find the one or two changes they actually care about. 3. Are you using a workaround? If yes, please describe it.No. 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.If an ECAD_NAME or ECAD_ALT_NAME exists in the design file - it will use those values during export. If it doesn't exist, it will use the values in the map file. On an EMN import, if the values do not match the design file, it will update from the EMN, with the understanding that the EMN is coming from the PCB team which is controlling that information.  This way, both teams have accurate ECAD_NAME and ECAD_ALT_NAME values and there will be proper collaboration without issues and warnings. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Our ECAD tool is getting errors about a mismatch to their cell names. It is causing confusion and spamming their warning log. The important information is now hard to see through these warning errors. Collaboration doesn't work well, causing an increase in unnecessary manual work (like creating separate PCB drawings) and human error.

Provide a function in Pro/TOOLKIT that is equal to the GUI-function "Swap Columns" in Family TablesAcknowledged

1. Describe the ProblemIn some cases (e.g. for the repeat-region) it's necessary to reorder the columns in the family table, e.g. after some columns have been deleted and new ones added.Several automation tools are used to help the users to work with Family Tables using Pro/TOOLKIT. But currently there is no function similar or equal to the "Swap Columns" function from the GUI in the Creo Parametric Family Table.A Pro/TOOLKIT function that works similar to the ProParameterReorder() would be also helpful (or even better), where the parameter that comes just after the indicated one and can be passed to the function.2. Are you using a workaround?To reorder the columns, specific columns need to be deleted completely (while the content has to be stored programmatically) and inserted again in the correct and needed sequence.3. What is the use case for your organization?When the user works with Family Tables and display it on the drawing, the columns need to be visible in the right sequence (the same sequence how the parameters/dimensions/... occur in the Family Table.4. What impact does this problem currently have on your organization?The missing Pro/TOOLKIT function has no direct impact to the business because it can be solved via the workaround described above. But: In IT there is an increased effort during implementation or during software changes/adaptions and could be avoided if the above described Pro/TOOLKIT function would be provided.

SAVE MIRROR ASSEMBLY CHILD ASYMETRIC PARTS GEOMETRY WITH FEATURESAcknowledged

1. Describe the ProblemGeometry with features option is not available in : Mirror Assembly User Interface when performing >File >Save Mirror Assembly from top assemblyGeometry with features option is intended to be available only when mirroring a part but we have assemblies with 100s of parts in them creo offers the ability to detect parts in the assembly that will need to be mirrored due to asymmetries but doesn't allow the ability to mirror those PARTS with features (even though creo already clearly has the ability to do this you have to do it on each individual part individually instead of doing it in bulk like this)  this could even be added to the advanced settings page (accessed through the save a mirror assembly dialog box) as a column in the tree where you could toggle mirroring each part with just geometry or geometry and features2. Are you using a workaround?instead of mirroring large assemblies all at once we are mirroring each little child component (with features) one at a time into a new assembly3. What is the use case for your organization?we could click just a few buttons to get all the mirror parts within a huge assembly mirrored with features. instead of mirroring each child part of the assembly separately with thousands of button clicks depending on the size of the assembly4. What impact does this problem currently have on your organization?over 1000 users effected easily wastes 10s if not 100s of thousands of hours per year when designing a machine, you need many, many, many assemblies mirrored and Creo currently does not have a good solution to support this need as far as I can tell

Allow adding BOM_REPORT_QUANTITY for bulk items to the family table to manage varying quantityAcknowledged

1. Describe the ProblemWhen using family tables to manage product variants of different geometric size, eg. height/width variants, the quantity needed for a bulk item, e.g. glue or paint will often depend on the actual size variant.So there is a need to control the value of BOM_REPORT_QUANTITY individually for each instance in the assembly family table.However, Creo does currently not support that is explained in  https://www.ptc.com/en/support/article/CS214511"BOM_REPORT_QUANTITY" can be driven from bulk template or bulk component only to avoid conflict of drivers for this parameters.Please consider resolving this constraint to allow the same variability for bulk items as for other types of components in family tables.2. Are you using a workaround?We are using an "overloading" methodology for family tables with few instances, where a bulk item for the same material is created or assembled into the generic assembly as many times as there are different quantities needed across all the instances. Then each bulk item is added to the familly table as a component column, and for any given instance, only the one relevant bulk item is marked as "Y" while the others are suppressed with "N". However for our larger family tables with +40 instances and maybe 3-4 different types of material going in as bulk item that is an ugly workaround which will cause the amount of columns in the family table to explode.3. What is the use case for your organization?The idea would allow a much more consistent approach of using of bulk items to represent the use of non-each quantity type materials, and drive related WTPart structures including those materials from the CAD structures, rather than having to maintain the consumption of those materials in different ways, including maintenance for all variants independently in the WTPart structures.4. What impact does this problem currently have on your organization?+200 users affected by non-consistent way of working with bulk items, depending on the actual use cases. Bigger family tables which are more difficult to handle and overview.

BOM balloons Symbols should be allowed to contain groups.Acknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Aerospace industry, I am a design engineer.2. What version of Creo Parametric are you currently running?I'm currently running Creo 7.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.I want to be able to use a custom BOM Balloon that also displays QTY.  I currently leverage a repeat region and have to have 3 separate symbols: One with the QTY on the left of the balloon, one with QTY on the right of the balloon, and one showing no QTY (for components that only have 1X qty).  It would be great if Groups could be leveraged in BOM Balloons, so that I could create one symbol where all QTYs exist, and then select in Groups which one I want shown in the symbol.  I'm not sure why Groups cannot be used with BOM Balloons specifically, but can use them in other custom symbols? In this context especially - it's all the same information, I'm just deciding where I want that information displayed relative to the leader, or not at all.4. What is the use case for your organization?This would be used throughout the org in drawings to automate the find number call outs5. What business value would your suggestion represent for your organization?Significant labor savings due to tedious balloon creation, and potential for human error if qty or find number is mistyped.