Skip to main content

Filter by idea status

Filter by product

6851 Ideas

The installation program should have the option not to change the file type associations.Acknowledged

Please include detailed documentation such as screenshots, images or video.When Installing multiple versions of Modeling / Drafting / ModelManager, there is usually a preferred version, where the file type associations should point to.On installing a version, all file types are registered for this version and have therefore to be registered for the preferred version again.On uninstalling a version, all file type associations are removed and have therefore to be registered for the preferred version again.1. What product and version are you running?20.3.4.0, 20.4.4.0, 20.5.3.02. What is the problem?File type associations have always to be registered for the preferred version again.3. Are you using a workaround? If yes, please describe it.Registering file type associations multiple times.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.We always install a new version on all PCs in the company and after a couple of weeks we uninstall the old version. We have to build custom uninstallers which register the file type associations after the uninstallation again.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)It affects us on all PCs (about 450PCs in the company) more than once a year.

Cable Harness service loops and dressing/management capabilityAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 82. What is the problem?Current cabling workflow does not have a straight forward way to add a service loop to a routed cable in a 3D model or allow the cable to be looped/routed back on itself, this requires manual addition of offset locations and is very time consuming3. Are you using a workaround? If yes, please describe it.Yes, we create a network going through the cable management features in the assembly, then route the cable through the network, then add in offset locations until the service loop appears as designed, in places where we need the cable to be dressed by manufacturing we again create a looped section in the network and then route the cable through this loop and create offset locations to give the appearance of a dressed extra length of cable.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.In our rack based system, we often have service loops between components to allow field service, we also have cases where items move, so the extra length is necessary. Some times we reuse COTS cables that are too long for the application and we will dress this extra length and manufacturing needs to know how we are prescribing that to develop their process.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)very few people are comfortable with cabling as it is right now, and even less doing manual routed features like this, so its usually bottlenecked at 1 or 2 people in the company, so quite the impact and lost productivity

Update TERMINATOR TABLE functionality in Creo's Cabling (TTB file) to match functions in SchematicsAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 8 2. What is the problem?When getting nwf's from other programs then Creo Schematics,  We  have to execute a terminator table using the logical refs menu in Creo's Cabling application.    I am asking PTC to update it to the better functions using wildcards to execute a terminator table TTB that could easily be the terminator table CSV we use in Creo schematics.   Although using Creo Schematics is preferred some companies service others that use outside programs like Capitol. I would like to actually see the exact same CSV file used in Creo schematics to be used as a TTB.   Also instead of Pro/Table as an editor allow Excel to edit it (like family tables do)3. Are you using a workaround? If yes, please describe it.Yes,   but because you cannot match a MODEL_NAME of DT06* you have to spell it out on each line4. 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.Using NWF's from Capitol and other programs to build cabling assemblies would be easier5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Low impact currently (1-2 users) , but more possible work on the way from outside cabling work.

Case SummarizerImplementation In Progress

1. Describe the specific problems or pain points that this tool aims to address. What challenges does it solve? Could be more than one.Getting a real-time, accurate summary on the situation of a long-standing case is complicated, and requires a lot of manual labour 2. Provide real-world scenarios or use cases where your tool would be beneficial. How do you see users incorporating it into their workflows?As a PTC employee who needs to get involved on a case (EM, TSAM, other TSE, TS Manager…), I want to have a summary of the whole history so that I can get up-to-speed very quickly3. Identify primary processes that will directly benefit from this tool.TSAM, Coporate Escalation, Point Escalation, EDOWN, Case Management4. Identify the primary users or target audience for this tool. Who will benefit the most from its features? TSAMs, Service Managers, CSMs, EMs, Support Managers 5. Estimate the potential business value and impact of implementing this tool. Quantify as much as possible. For example: "TSAMs would save 30 minutes each week", or "TTR for cases would decrease by 1 day."It is hard to quantify the cost of having inaccurate information (all the time wasted based on misunderstanding, etc.), but maybe we can assume that we could eventually save time maintaining closure details (and eventually, in an ideal world, retire it), for example 1 minute for every transaction on cases6. If you have any preferences or ideas regarding the tool's user interface, provide them here.The user enters the case number, then they are displayed the summarySummary could be text or a nice timeline, with colors7. Include any extra details, suggestions, or considerations you think are important for evaluating your idea.Can eventually be integrated in Salesforce and the eSupport Case Viewer

ECAD Components stops following flex board shape after redefinition - please fixAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 9.0.7.0 2. What is the problem? Reference: Ticket #: 17094880 SPR#: 14927971  Article: 404190   We imported a baseline PCB into an ECAD assembly. This was a flex PCB that needed to get bent, so we added bends to get the routing needed. We are able to successfully show the flattened state and all components regenerate fine. HOWEVER, if we redefine a component and press OK (without making any changes), the component can no longer update properly when toggling between the flat and bent states! All we did was press OK!3. Are you using a workaround? If yes, please describe it.We are using two assemblies, a flat state and a bent state. This can introduce discrepancies and issues between the two assemblies, and a lot of extra work when trying to collaborate between the ECAD and MCAD teams.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.The components would regenerate normally during the flat and bent states. It would behave as it should.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)It is another roadblock during out attempt to use the ECAD module. Our main business revolves around PCBs and getting the tools and processes optimized for our engineers is critical. We can't have workarounds and separate processes for each PCB. This impacts hundreds of engineers and hundreds of hours of work.

Topic solved summaryAcknowledged

1. Describe the specific problems or pain points that this tool aims to address. What challenges does it solve? Could be more than one. On the support forums, the conversions can be lengthy. When a topic is solved, the meandering dialog leading to the solution may be too long.     2. Provide real-world scenarios or use cases where your tool would be beneficial. How do you see users incorporating it into their workflows? When users are searching / visiting the existing solved topics, we want to present them with a summary of the question and the solution, clear of the adjacent details.     3. Identify primary processes that will directly benefit from this tool. Community engagement in general 4. Identify the primary users or target audience for this tool. Who will benefit the most from its features?All Community users.  5. Estimate the potential business value and impact of implementing this tool. Quantify as much as possible. For example: "TSAMs would save 30 minutes each week", or "TTR for cases would decrease by 1 day."A few minutes saved for users to evaluate the relevance of the forum solution for their problem.  6. If you have any preferences or ideas regarding the tool's user interface, provide them here.Below the initial question, offer a summary of the relevant parts of the entire topic with a different font color and / or background.   7. Include any extra details, suggestions, or considerations you think are important for evaluating your idea.

A tool for duplicated article checkUnder Consideration

1. Describe the specific problems or pain points that this tool aims to address. What challenges does it solve? Could be more than one. Duplicate articles are one of KHC's check items, but the current KB search tools for synonyms search or non-native English language reasons, it is difficult for TSE to avoid creating duplicate articles. And it also is difficult for DSE to check the duplicate articles. 2. Provide real-world scenarios or use cases where your tool would be beneficial. How do you see users incorporating it into their workflows? TSE can use this tool to check whether the article is duplicates before publishing it. DSE can use this tool to check duplicate articles. 3. Identify primary processes that will directly benefit from this tool. Reduce duplicate articles. 4. Identify the primary users or target audience for this tool. Who will benefit the most from its features?All TSEs and KCS management.  5. Estimate the potential business value and impact of implementing this tool. Quantify as much as possible. For example: "TSAMs would save 30 minutes each week", or "TTR for cases would decrease by 1 day."TSE/DSE could save time to check if the article is duplicates. 20mins for each new article. 6. If you have any preferences or ideas regarding the tool's user interface, provide them here.As part of the article editor and KHC review tool 7. Include any extra details, suggestions, or considerations you think are important for evaluating your idea.

Allow "Feat Name" to be used in 2D and 3D annotation.Acknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 7.0.8.0.2. What is the problem?Unable to use the "Feat Name" parameter in Creo Parametric for 2D or 3D annotation.3. Are you using a workaround? If yes, please describe it.No known work-around.  Interested in any options that are available.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."Feat Name" is an assembly-level parameter, so it is applied to different instances of the same component in an assembly.  Once checked-in, the "Feat Name" value from the CAD is applied to the "Component Name" attribute of the CAD Doc object (when looking at the assembly structure).  If a Design Part is linked to the CAD Doc, the same value will be propagated to the "Reference Designator" attribute on the Design Part. This is good for CAD and Windchill structure, but there is no capability to add the value the the CAD model as annotation. We would like to be able to create 3D annotation to our CAD models for the "Feat Name" parameter.  This would give allow us to attach Reference Designators to the instances in a CAD assembly.  Very handy.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)All users.  Small to medium impact because we see this capability as an enabler.  If it was supported, we'd be using it a lot.