Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Need Block List capability for the Creo Embedded Browser in Creo ParametricDelivered

Please include detailed documentation such as screenshots, images or video. Along the lines of article CS378421 regarding an Allow List, we need a Block List capability.1. What product and version are you running?Creo Parametric 7.0.8.0, soon to be 9.0.5.02. What is the problem?We need to prevent users from accessing certain Windchill URLs from the embedded browser.  It is not practical to maintain an Allow List.3. Are you using a workaround? If yes, please describe it.User education, which is not holding up well.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 have Multiple Windchill Clusters on a Load Balancing Router with Common Base URL.  After many years with this setup, it is impractical for us to correct this from the Windchill implementation standpoint.  If a Creo Parametric user Registers and Connects to the wrong Windchill URL, it corrupts their cache.  We could finally make this situation impossible if we could block access to incorrect URLs when using certain configurations by managing a Block List.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)This would plug a major hole in our Creo implementation of 3000+ users.  Lots of data has been lost over the years due to Windchill cache corruption situations due to the above Windchill setup at our company.

Propose to create in Creo Manufacturing functionality of Turning by millingAcknowledged

Turning by milling We propose to create Creo Manufacturing functionality that will make it possible to process using the “Turning by milling” method.There is a need, especially in turning and milling, to organize processing using the “Turning by milling” method.This method is very important for our customers. To obtain scallops of optimal height, it is necessary to shift the center of the cutter tool relative to the axis of the workpiece.In other words, we need to ensure a offset of the cutter axis relative to the workpiece axis (Ew). We tried to do this using the 4X_LEAD_ANGLE angle, but we realized that the Ew offset and the 4X_LEAD_ANGLE angle are different and independent values. That is, it is impossible to obtain a certain offset Ew simply by changing the angle 4X_LEAD_ANGLE, and vice versa.Moreover, the contact point of the “END MILL” tool with values ​​of 4X_LEAD_ANGLE is more than 1 deg. from the center of the tool face, when 4X_LEAD_ANGLE is close to zero, immediately moves to a point at a distance of the tool radius. It is not yet possible (CREO 10) to obtain an offset at a distance less than the tool radius:  How, for example, can you machine an elliptical section of a shaft with the “END MILL” tool offset? Turning by milling has long been implemented in many CAM systems. We are waiting for such a solution in CREO Manufacturing!

start value for hole label naming in hole tableAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?We use Creo parameteric 8.0.9 in conjunction with Windchill 12.0.2.2. What is the problem?We often use the hole tables in the drawings for hole specifications. In most cases, several tables are created in order to achieve a clear assignment to the different views.We use alphanumeric identification to assign names. Unfortunately, the first hole in each of these tables is labeled "A1". Unique identification is therefore not possible when using multiple tables.Specifying a starting value for the naming would be very helpful here, as it would allow you to create unique designations.3. Are you using a workaround? If yes, please describe it.It is only possible to try to create the assignment of the hole table to the display view as accurately as possible. However, this is hardly possible for large drawings with a large number of holes and hole tables.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.Incorrect allocation results in faulty parts that usually cannot be reworked and therefore have to be scrapped.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)I cannot currently quantify any specific damage. The actually sensible use of the hole tables requires a lot more time during the drawing check and work preparation, because the error-free assignment has to be checked several times.

Creo to better handle imported ECAD PCB silk screen layersDelivered

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders. PCB design, computer and electronic device designWe are Design Automation Team.Our customers are our MCAD Mechanical designers, ECAD designers, product designers.2. What version of Creo Parametric are you currently running? Creo 9.0, and Creo 7.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Creo 9 supports to import ECAD IPC-2581 files,  When Import ECAD silk screen data entitles as quilts, the 2D silk screen layer is under the 3D copper layers and cannot be seen properly. The Silk screen should on the top surface of the 3D copper layers and sold mask layers. Otherwise, it is hard to clearly see and validate the ECAD design. It defeats the propose to import ECAD files into Creo.  To make this feature more useful and better, I think either the silk screen layer should be allowed to be imported as quilts, or at least the silk screen entities should be allowed to place on top of copper layers and sold mask layers. Converting ECAD Entities as 3D quilt surfaces with multiple layers with thickness allows users to accurate validate design. The thickness is also important for certain product designs. 4. What is the use case for your organization? Import IPC-2581 ECAD design in Creo with MCAD components to validate the complete design. 5. What business value would your suggestion represent for your organization?It will add significate values to our current design workflow. Make it more reliable, faster and easier for designers.     

Save as Assembly and Parts with drawings, with instances and their drawings renamedAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Our Industry is the manufacturer of machinery for complete bottling solutions like water bottle blowing machine, filling machine, labelling machine and shrink wrapping machine. 2. What version of Creo Parametric are you currently running?Creo Parametric 9.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.While saving a large assembly to another directory for designing a new variant of that machine, the assemblies and parts will be saved with the rename that we give. But the instances of the parts and their drawings are not created and  saved. This takes lots of time wasting to create the instances again with rename and to do drafting again.  The common solution given currently is to backup it and rename it. How is it possible for thousands of components in a machine? Another one solution is to save as individual parts. This is also time consuming and assembly fails, references fails and to reconstruct it. The final solution given is to rename and copy it. We have to open thousands of drawings in one session opening every single drawing one by one. There is also a limit to open number of drawings in a session. Even though there is no limit, it is very time consuming. 4. What is the solution or idea suggested?We are asking to combine two solutions into one.1) Save as Option will work fine for assembly and parts by renaming them with drawings and saving them. 2) If we save as only one number of part the instances and drawing file is saved. What we are suggesting is to combine these to and while saving the assembly and parts, let they be saved 1) with rename, 2) with drawings and 3) with instances in the family table and also with their associated drawing files. This will save lot of time for many industries while they are planning to design a new machine variant in the same category and  want the name to different and the component is same shape except their size and simple modifications in some part as it is absolute necessary.

Couple of suggestions related Creo message logAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 10. 2. What is the problem?Message log tells me clues instead giving me a more complete information about the issue at hand. Capturing information from it is tedious.   3 examples: a) If there is a model in an assembly and its layer state was altered, then upon saving the assembly, a message will show up (in black): Problem is that often, I have no good idea as to which model it was that was saved (with its layer status not saved).  I am suggesting that the name of the relevant model is added in brackets at the end.   b)  If a dimension is driven by a relation, then attempt to modify it by double-clicking on it will result in a warning message: Problem is that I don't know where this relation is - because it can be a part level relation, or it could be a feature relation... it could even be a feature relation in a completely different feature!.. So, please add the pertinent information to the above warning message.   c) Often I want to use the information from the message log and "cut-and paste" it. Sometimes it is easy to grab the relevant bit just by double-clicking. Other times though, double-clicking gets you extra characters such as the trailing period or that leading bullet.  Those are annoying as they need to be deleted upon pasting.    3. Are you using a workaround? If yes, please describe it.No4. 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.Less frustration.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Minimal.

Allow part and (sub)assembly parameters in a 3D Note as are allowed for bulk itemsAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 9.0.4.02. What is the problem?Part or (sub)assembly parameters cannot be referenced in a 3D note at the assembly level.  This behavior appears inconsistent because bulk item parameters can be referenced in 3D notes at the assembly level.  The parameters for a bulk item can be reference at the assembly level 3D note using <parameter>:FID_# where # is the feature ID of the bulk item.   However, if a lower level "component" is a part or subassembly the above method does not work.  Nor does using <parameter>:SID# where SID# is the session ID allow the lower level parameter value to appear in the note.  3. Are you using a workaround? If yes, please describe it.There is a work around in that in Relations one can create a parameter <parameter_test> and declare it equal to the lower level parameter using <parameter>:SID# and then call the assembly parameter in the 3D note by using the "&"  (i.e. &parameter_test).  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 use case is with model based definition there is a need to call lower level parameters such as description, part number or general model information at a higher level to define the product.  This is indeed possible with bulk items and a workflow for calling parameters from those items is possible.  Having consistent behavior with parts and assemblies would allow for a standard workflow for assembly level 3D MBD notes.  The solution could uses the session ID instead of the feature ID like a bulk item.  The ask here is that it be possible to directly (and easily) reference the lower level part numbers without have to create a new relation for them.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)The workaround is obviously more work and can make for the need of a lot of "unnecessary" relations in the assembly.  With model based definition, referring to lower level product information is becoming more common in a 3D note.  Hence each user will have to spend several more minutes creating relations where a consistent behavior would eliminate those minutes.  It doesn't sound like a lot, but over many assemblies the time adds up.

Hole Export Control for ECAD IDF (EMN) and IDX Standards to account for holes that are in 'parts'Acknowledged

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?We are aggressively attempting to use the ECAD MCAD Collaboration Standards (IDF and IDX) but are running into some stumbling blocks, especially with holes. There are many holes in the board, like a standoff hole, that is already included in our decal/cell of the standoff within the ECAD tool (PADS, Xpedition). So when the standoff is in their layout tool, it automatically places the hole. Which means, they don't want the EMN file we send them to include another hole. The PCB team would need to search through the import and manually delete the holes each time! It gets even weirder. The PCB team uses parts for regular mounting holes as well! Even if there is no actual part, they create one with a simple hole. This helps for routing within the schematic and other reporting metrics as well. I believe there is a convoluted way to make this work by assigning a feature level parameter (ECAD_ASSOCIATED_PART) to each hole that matches the reference designator of the part and then the ecad tool might ignore it... This is something that won't end up happening and might not even work in all situations (Sketched Holes). It also introduces a big risk where the wrong reference designator is entered or updated. The point of the collaboration process is to save time and issues. By adding this large amount of work, goes against the whole idea and the team will just end up sending out the collaboration files with the holes that don't have this parameter. If there was some way to either exclude holes from the export altogether, or figure out another simpler, smarter solution to this problem, that would be great!3. Are you using a workaround? If yes, please describe it.No. We are struggling to get thru these roadblocks.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.Our organization is built of producing products that have PCBs. Most of our engineering effort revolves around PCB development. Therefore creating processes that optimize this is critical. Ideally, the collaboration file that the PCB team imports from the Mechanical Team won't have holes listed for any parts that are using that hole (standoffs, connectors or even mounting hole parts).5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)This impacts about 100 users. It would easily reduce the collaboration time and errors between the two teams as this is one of the big pain points from having us continue with the collaboration effort.