Skip to main content
Dec 5, 2024 2:39 PM UTC
Acknowledged

Repeat Region Feature for MBD Tables

Related products:Creo Parametric

1. Describe the Problem

With the introduction of Tables in 3D mode, PTC has made an important step towards MBD with Creo 11.

 

What we are missing here, is the opportunity to re-use data from the 3D file properties, such as Name, Number, Weight, etc. so basically the repeat region feature which is available for tables in 2D mode.

This is currently explicitly excluded in the PTC Documentation:

https://support.ptc.com/help/creo/creo_pma/r11.0/usascii/index.html#page/whats_new_pma/mbd_create_tables.html

Limitations: Currently, Creo does not support tables with repeat regions. When you place a table with repeat regions, a message appears in MBD, and the table is placed as a simple table.

Feature Request would be to enhance the tables make them re-use attributes already available instead of manually typing all the information into it.

Documentation for Repeat Regions: https://support.ptc.com/help/creo/creo_pma/r11.0/usascii/index.html#page/detail/Understanding_Repeat_Regions.html


2. Are you using a workaround?
No workaround available

3. What is the use case for your organization?
Using Tables in a most efficient way and avoid copy pasting information

4. What impact does this problem currently have on your organization?
Manual table maintenance instead of using available attributes

7 replies

Community Manager
Dec 5, 2024 3:11 PM UTC
Status changed to: Acknowledged

Thank you @CHENAMA for your idea. 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.

Jan 23, 2025 3:17 PM UTC

Great idea ! 👌

Feb 26, 2025 11:25 AM UTC

Hi @CHENAMA and @RaphMORIN 

Can you please elaborate more on the ways that repeat region tables will be consumed for MBE workflows at your company?

I assume that one of the obvious use-cases is visualization and that those tables will be mostly consumed by humans (human readable use cases).

Can you please elaborate more on those use cases, as well as if you have any other use cases where you envision that tables will be used for automating processes downstream (machine readable)?

 

Any input will be highly appreciated

 

Thanks in advance,

Michael Fridman

Creo Product Manager for MBD

CHENAMAAuthor
Feb 26, 2025 11:48 AM UTC

Hi @Mfridman 

 

This idea focusses more on the hours spent by Engineers, but of course together with my other idea https://community.ptc.com/t5/Creo-Parametric-Ideas/Designate-amp-Control-Characteristics-Cells-for-MBD-Tables/idc-p/987339#M21459 this would also support the connectability towards Windchill and then re-use certain information in automation (MPM-Link, Process Plans, Operations, refer to it in Creo Illustrate and prepare work instructions, information sent then to a MES System which either controls tools or guides workers).

 

In this idea here, I thought of replacing the tables we use in Drawings. We for example use a table where we refer to the CAD Name and define for a screw for example with which torque this has to be installed. If you could use repeat regions, you don't rely on manual input by an Engineer but you actually refer to the real CAD. Especially for changes, let's say we change 3 screws from M6x12 to M6x16 while 5 others stay as they are, with manual tables you have to do the work twice (replace the screw in 3D and then update the table) while with repeat regions you could have that second step automated and data quality is ensured.

Feb 26, 2025 12:53 PM UTC

Hi @CHENAMA ,

Thank you for the additional feedback, I agree that the automatic update that repeat region offers, makes them much more robust and requires less maintenance from the user.

 

Can you please provide specific example on the type of tables/cell data that you would want to make available in WC/MPMLink and reuse them ?

Maybe it makes sense that you will provide those comments to the other product idea that you created, where you asked for the table cell designation.

 

Thanks,

Michael

CHENAMAAuthor
Feb 28, 2025 10:13 AM UTC

Hi @Mfridman ,

 

We are trying to get rid of drawings and put everything into 3D (MBD).

One specific use case would be:

We often order pre-assembled sheet metals with some insert studs, insert nuts, some rivets installed etc.

On our drawing today we add a table with all the single items, their order codes (for standard parts) and the sheet thickness and bending radii of sheet metals and their material.

Background why we add this information, the supplier first hands in an offer, for this he can't spend the time in checking the detailed CAD file, so he needs a rough overview of the materials used and how complex the geometry is.

I would see this absolutely possible with a 3D file and a table next to it, but again, you don't want users manually maintaining such attributes in tables, when the information is available in 3D and actually we were able to call it out in 2D.

 

I hope the use case is more clear now.

Mar 2, 2025 8:21 AM UTC

Thank you @CHENAMA , your use case is clear now to me

 

Best Regards,

Michael