cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X

Creating BOM out of Creo with other quantity unit than "each"

Creating BOM out of Creo with other quantity unit than "each"

Components of Creo Parametric assemblies are represented in Windchill by CAD usage links which have attribute quantity.unit set to each. In some cases it is useful to have another quanitiy.unit, for example meter (for bars, rails, ...). It would be nice if we could to set designated parameters in Creo components, which are mapped in Windchill to quantity.amount and quantity.unit of CAD usage link. At the moment, such a mapping is not recognized by Windchill. It would also be helpful if these attributes are then mapped to the corresponding attributes of the part usage link through the build of WTParts.

Otherwise, the BOM of the WTPart must be corrected manually by deleting and reinserting such a component. Then, this BOM component is no longer associative to the CAD model, and always needs to be updated manually. No one wants to have this behavior.

The attached document explains the desired technique with some screen shots.

A similar behavor is already implemented for find number and line number as IBAs of CAD usage link, which are then mapped to attributes of the corresponding part usage link via preferences build.find.number.attribute and build.line.number.attribute. [Zemsky, Jeff: PTC Live Global: BOM and Configuration Management Best Practices, 2014-11-19]

10 Comments
slapha
15-Moonstone

Related idea with a similar problem, use of As Required/As Needed for bulk items. We also have some things like clamps with quantities "as required".

Bulk Item vs Regular Parts and integration with PDMLink

and similar: Better Unit of Measure and Quantity support between Creo and Windchill

ThomasBittner
4-Participant

We also have this requriement and it would be helpful to manage such units in Creo-BOM's

jschramm
8-Gravel

It would be great to havre this functionality also for any kind of attribute like wearing flags, etc...

Not only for quantity.unit.

PTCModerator
Emeritus
Status changed to: Acknowledged
 
DavidCobb
12-Amethyst

We have recently implemented Windchill 11.0 M030 using the out-of-the-box CAD to Part structure synchronization and when this issue surfaced I was surprised to find that it still requires a manual workaround from reading this idea and the other similar ones referenced in the comments. I have voted yes for this and the similar ideas and definitely agree with the earlier comments, the manual workarounds are clunky and highly undesirable.

jvonzastrow1
14-Alexandrite

This feature is also needed by many customers using 3rd party CAD (Solidworks, Inventor...)

lkennebrew2
7-Bedrock

I concur with the previous comments.  Per @jvonzastrow1 , this is also needed for CATIA V5.

tm-4
9-Granite

I request PTC to prioritize this in their roadmap. This is a very general issue across many industries. Currently we have implemented a workaround for which we have customized many functionalities.

SteveShaw
15-Moonstone
Status changed to: No Plans to Implement

Thank you for the idea, the comments and votes. Your idea is interesting and is aligned with our roadmap. However, given the team’s current strategic priorities, we are unlikely to prioritize the implementation in the next development cycles. Should this change, we will bring this idea back and provide appropriate updates. 

N.Barnes
11-Garnet

Please update the help files to make it clear bulk items can only do "Each".  The help file makes is sound like what people are requesting is already a capability.    If the helpfile is accurate, please help us understand how to make it work.  Thanks. 

 

https://support.ptc.com/help/windchill/plus/r12.0.2.0/en/index.html#page/Windchill_Help_Center%2FCADxInfoPgRprtsBulkItemAbout.html%23

 

"For example, a parameter defined in Creo Parametric, BOM_REPORT_QUANTITY, contains quantity and unit parameters, used to describe the quantity and unit of quantity for a bulk item (if no unit is explicitly assigned and the quantity is an integer value, the system assumes the unit to be "each". If the quantity is a real value, the unit is “As Needed.”). This information is passed toWindchill upon upload (either on the EPMDocument Master or on the EPMMemberLink) and can be displayed in tables showing the WindchillQuantity column."

 

Its not clear why this should be hard to implement. The bulk items have parameters, Windchill knows how to read parameters. Windchill understands units.  Windchill can already read the quantity parameter from a bulk item.   We just need Windchill to read a Unit parameter and then update the units in the HWPart structure to match.  All the fundamentals are in both tools.  Its ok if Windchill only does integers, we can use smaller units if needed.