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

Tool / fixture wtPart assoication to the eBOM

Highlighted
Aquamarine

Tool / fixture wtPart assoication to the eBOM

Greetings,

We only use an eBOM. Our company is new to the idea of wtParts.

Historically, the tools and fixtures that are needed to make a component are called out as children to the component they are used to make. This was displayed in our ERP system.

In Windchill, we did not include these tools/fixtures in the BOM.

 

We created a tool/fixture part for all the tools and fixtures we use.

 

Our plan is to have these tools and fixture Parts be parents of any components that requires a tool or fixture to make it.

 

The plus side is the eBOM will not include these tools / fixtures.

The downside is that when a tool/fixture Part is released, it could be published via ESI to our ERP system.

 

The tools and fixtures are called out in text within the manufacturing document that is used to make the assembly.

Our manufacturing documents are created in Arbortext (subtype EPMdocument) and would require a described by relationship. To get around this, we use a Published Content document that is Referenced to the assembly Part.

 

What have others done to structure tools and fixtures?

Thanks.

Tags (2)
2 REPLIES 2
Highlighted

Re: Tool / fixture wtPart assoication to the eBOM

Hi

 

we are a multi brand company.  And depending of Brand need, we implement 2 different solution:

- High End solution: Use of full MPMLink model , Create ProcessPlans and Operations.  And reference Toolings and fixtures (which are special Wtpart types "ressources" in MPMLink) in consuming Operations .

- Simple Solution: Use of Configurable Master link to create a "Manufacturing Folder" to the WTpart, where we reference Wtpart toolings

Highlighted

Re: Tool / fixture wtPart assoication to the eBOM

Do you use the OOB wtPart View of Design or Manufacturing?

Announcements