Thank you @asalunkhepatil for publishing your idea. However, we need more information as specified in the form you saw in the submission process. (questions below). The more details and context you give to document your idea, the better. Think about ways to educate and convince other Community members to support your idea and present your case to the product management team for consideration. As an example, here is a Creo well documented idea: Make Shrinkwrap quality more scalable to data size... - PTC CommunityPlease let us know within the next two weeks.1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.2. What product & version are you currently running?3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.4. What is the use case for your organization?5. What business value would your suggestion represent for your organization?Additionally, I invite you to check out this topic where PTC executives explain product managers' approach to customer ideas and input for product roadmaps.
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
We (Novus Nexus) is technical partner to PTC. We developed automation CAE product-CAENexus as an addin/Auxiliary application over Creo using Pro/toolkit API. Our product has been used by some of our common customers using Creo. This issue has been originally reported by John Deere. I am working as software developer and support engineer for CAENexus.
2. What product & version are you currently running?
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
The product idea is a response to case-C16059524 (https://www.ptc.com/appserver/cs/view/case.jsp?n=16059524). PTC raised SPR 13280600 for this case but finally we ended up that product idea needs to be raised for the same.
CAENexus creates simulation model (imprinted model) as ProToolkit's ProMechModel. The ProMechModel created using Pro/Toolkit API fails to give bonded surface (even though distance between them is 0) when face types are different in native Creo model (Cylindrical and Fillet). Please find attached presentation to know more about the model.
4. What is the use case for your organization?
In CAENexus, we create non-manifold model (built over ProMechanica model) to do the meshing and next processes such as exporting FEA solver deck. It would be great if ProMechanica model gives bonded surface even if native faces are different. If these faces come as bonded then we can merge them at our end and create valid non-manifold model with merged faces. As we mesh non-manifold model in our software, it fails to do the meshing if faces are not merged in our non-manifold model. (because they are not bounded faces in ProMechanica model).
5. What business value would your suggestion represent for your organization?
Currently if such faces are not merged then Deere CAD engineers needs to do trial and error with different features to get the face types same. Again there is no specific method or recipe to get the face types same. It all depends on trial and error trying different features to create the faces. Hence it will be good if ProMechanica model gives bonded surface even if face types are different and distance between them is 0.
Thank you for your follow up @amol_patil. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.