Skip to main content
T
TobyGillis1-Visitor
1-Visitor
January 16, 2015
Question

MBE

  • January 16, 2015
  • 4 replies
  • 2880 views

Is anyone able to add tables to an MBE environment yet? Specifically BOM tables with associative balloons?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

4 replies

S
shumphrey1-Visitor
1-Visitor
March 31, 2016

Have you gotten any additional information on this?

StephenW
StephenW23-Emerald III
23-Emerald III
March 31, 2016

What is an MBE environment?

M
mender12-Amethyst
12-Amethyst
March 31, 2016

I believe 'an MBE environment' means that you have a solid model, and document it according to standards like ASME Y14.41, with the goal of not needing a drawing to provide the necessary documentation.

As of now, model-based detailing standards do not include tables, or various other aspects of 2D detailing.  If you want to have a BOM table with ballooning, you'll need an auxiliary drawing.

D
dschenken1-Visitor
1-Visitor
March 31, 2016

I looked at trying to create genuine Component parameters, but it doesn't work as the vocabulary would suggest. There should be a way of associating parameters with each piece part within an assembly as well as each base model. That way I could indicate that every use of a part had a high level item number and that each individual assembly had a unique, changeable index.

So, all 1/4-20 x .75 screws of a certain type would get a a parameter that would be reflected in querying any of them as a base model in the assembly, as well as being able to say that the first 3 were identified as 1A, 1B, 1C, for example.

Then, when writing the process the writer could refer to the base model item number in the BOM and individually in process steps as they are installed.

Even if they were only handled on a part-by-part basis, the way the feature_id is done, I could bounce the list of all parts and see if the same part was assigned different item numbers.

All of this would happen at the assembly level as the same component could end up in multiple assemblies.

I suppose something could be worked using flexible components, but I've had flexible components flake in Repeat Regions because Creo sees them as entirely different parts.

It would be ideal if the identification flowed up to Windchill/was driven back by Windchill, so that an accurate BOM, with find numbers, could be viewed there. As it is, I can create multiple repeat regions and assign any item number to any part in any of them.

AFAIK Creo doesn't offer this level of downstream support in its MBE approach.

D
dschenken1-Visitor
1-Visitor
April 1, 2016

OK - I tried this today and each component can have it's associated in-assembly parameter, but that parameter does not seem to be visible from the model tree. It also applies at the individual level so I could create two params - one for the Item number and another for the per-component reference.

However, it requires picking each component one at a time to add this and, because it's not visible in the model tree, it isn't apparent which components have these parameters and which don't, which is likely the reason I discarded this as a useful option.

C
ctauber1-Visitor
1-Visitor
April 1, 2016

As of Creo Parametric 3, there is no functionality to create tables in a 3D environment, only a 2D environment. Similarly, there is no such functionality in the 3D environment as Pro/Report in the 2D environment. Pro/Report functionality is what drives parametric tables in the 2D environment and allows the automatic creation of BOM balloons in the 2D environment. No such functionality exists for the 3D environment.

You can create/place symbols in the 3D environment that look like BOM balloons, but without the Pro/Report functionality to drive them, they are "dumb" symbols and find (item) numbers must be assigned manually and the symbols placed/attached manually. A long way from viable functionality.

Terms & ConditionsAccessibility statement