Managing and controlling EBOMs and MBOMs (bill of materials)

  • 9 December 2020
  • 6 replies
  • 2239 views

Userlevel 4
Badge +11
  • Hero (Partner)
  • 69 replies

Looking to start a conversation with users that have similar requirements/processes and maybe even a solution that you wouldn’t mind sharing.

 

All parts get setup in our PDM system and and are configured in the form of an Engineering Bill of Materials (EBOM). These EBOMs are generally built from the bottom up and contain every part needed to cost the final product.

 

These BOMS may feature Technical, Design and Electrical parts.

 

We need to bring these parts into IFS in the form of a product structure that is configured for manufacturing (MBOM).

These MBOMs differ from EBOMS as the component parts may be combined in different ways in order to best facilitate the manufacturing process (effectively create sensible Shop Orders in IFS).

 

If this resonates with anyone on this forum please reply.

 

Many thanks,

Pete


This topic has been closed for comments

6 replies

Userlevel 7
Badge +28

The answer to this question is a book, not a forum post. 

We also use an external PDM system to create what you refer to as the EBOM (BOM for us).  Then we release the item from the PDM using an Engineering Change Order in that application that triggers an interface connection to IFS (this is a custom written interface by us).  This interface first brings the information into the Master Part, then according to many different settings in custom fields, determines which sites the parts need setup in as Inventory Parts.  The initial setting of the inventory part in each site is based on a TEMPLATE Part that exists in each site. This provides the initial setup of the part and based on the Part Type coming from the PDM system, makes an initial guess on whether the part is to be Purchased or Manufactured in that site.  If Manufactured, this will also automatically setup the IFS Structure.  All items are initially set as Planning Method A because there is no way to know otherwise how the item is to be managed from an inventory standpoint.  There are some additional rules and flags that we transfer over from the PDM system - for example, we use a Reference flag in the PDM system to flag items like drawings and hardware that is expensed - this in turn sets the Consumption Item flag on the Structure to Not Consumed.

From there, a Planner has to come along and go through the Structure top to bottom and determine the proper Planning Details settings for each item, set the Default Location and several other Inventory Part settings - all manual because there just isn’t any hard and fast rule to determine this stuff.  If the item is manufactured AND it won’t be Phantomed, it also requires Routings to be added.  After all of that setup is finished, then it is turned over to Purchasing to quote and update the Estimated Material Cost for all of the new items.  When Purchasing is done, then it is turned over to Cost Accounting for the Cost Calculation to be done part by part up through the structure.  Once the final cost is achieved, then the Sales Part setup process is done for the top level selling items.

Revisions are synchronized between the PDM system and IFS so only current released BOMs can be built as structures.  Custom Items and Configured Items have separate, parallel processes with some differences than Standard Items.  Lower level items that eventually become service spares also have different setup.  Here is how heavily the Master Part view is modified - everything in the box is a custom field that both holds a latest copy of the information from the PDM system and is also used to further setup the inventory parts.  

Item Sites and Structure Sites use a noun name translation to an IFS Site number to connect the sites correctly based on the listed physical manufacturing site.

 

Master Part Custom Fields

 

Inventory Part Templates

 

That is a 20 minute scratch the surface explanation of a couple of day course to explain to a new engineer or a new planner how it all works - and that would be the visible portion, not the technical portion.

 

 

 

Userlevel 4
Badge +11

Thank you for the in depth response @ShawnBerk  - I appreciate that this only scratches the surface of the solution you have in place at Instron.

If we had a few more questions relating to your experiences in this area and about this solution would you be open to a call in the new year?

Badge +1

The answer to this question is a book, not a forum post. 

We also use an external PDM system to create what you refer to as the EBOM (BOM for us).  Then we release the item from the PDM using an Engineering Change Order in that application that triggers an interface connection to IFS (this is a custom written interface by us).  This interface first brings the information into the Master Part, then according to many different settings in custom fields, determines which sites the parts need setup in as Inventory Parts.  The initial setting of the inventory part in each site is based on a TEMPLATE Part that exists in each site. This provides the initial setup of the part and based on the Part Type coming from the PDM system, makes an initial guess on whether the part is to be Purchased or Manufactured in that site.  If Manufactured, this will also automatically setup the IFS Structure.  All items are initially set as Planning Method A because there is no way to know otherwise how the item is to be managed from an inventory standpoint.  There are some additional rules and flags that we transfer over from the PDM system - for example, we use a Reference flag in the PDM system to flag items like drawings and hardware that is expensed - this in turn sets the Consumption Item flag on the Structure to Not Consumed.

From there, a Planner has to come along and go through the Structure top to bottom and determine the proper Planning Details settings for each item, set the Default Location and several other Inventory Part settings - all manual because there just isn’t any hard and fast rule to determine this stuff.  If the item is manufactured AND it won’t be Phantomed, it also requires Routings to be added.  After all of that setup is finished, then it is turned over to Purchasing to quote and update the Estimated Material Cost for all of the new items.  When Purchasing is done, then it is turned over to Cost Accounting for the Cost Calculation to be done part by part up through the structure.  Once the final cost is achieved, then the Sales Part setup process is done for the top level selling items.

Revisions are synchronized between the PDM system and IFS so only current released BOMs can be built as structures.  Custom Items and Configured Items have separate, parallel processes with some differences than Standard Items.  Lower level items that eventually become service spares also have different setup.  Here is how heavily the Master Part view is modified - everything in the box is a custom field that both holds a latest copy of the information from the PDM system and is also used to further setup the inventory parts.  

Item Sites and Structure Sites use a noun name translation to an IFS Site number to connect the sites correctly based on the listed physical manufacturing site.

 

Master Part Custom Fields

 

Inventory Part Templates

 

That is a 20 minute scratch the surface explanation of a couple of day course to explain to a new engineer or a new planner how it all works - and that would be the visible portion, not the technical portion.

 

 

 


Thanks for the response  @ShawnBerk , i work along with @pwlm We have done a similar set up to what you describe, but your is much more in-depth with your custom fields.  Our scenario around how to manage the BOM into a more manageable form, i.e. how would we create a consolidated BOM that can be pushed into IFS in the structure that suits manufacturing better, as we understand the EBOM make sense for how the product is to be designed. It sounds like you do the same as us right now and go from the BOM product structure in the PDM, directly into IFS and apply your customisations and processes as is.

Thanks

Brian

Userlevel 7
Badge +28

Engineers operate in the PDM system and don’t interact with IFS much, Planners operate in IFS and don’t really work in the PDM system.  So from the perspective of the BOM in the PDM system being not exactly the same as the Structure in IFS, it actually makes sense for us.  Thus no real need to do a conversion in the transfer.

Userlevel 2
Badge +6

There are many tools around that will synchronise PLM data with IFS Engineering (EBOMs) or Manufacturing (Product Structures). One such is provided by ELMO. It’s very flexible and has connectors for most common PLM systems such as Windchill and TeamCentre. It shouldn't be a manual process to sync PLM data with IFS.

Userlevel 3
Badge +7

Hi,

Not sure if this is on the right line of thought, but I create EPR Structures using the logical hierarchy of raw materials, sub-assemblies and finished goods that reflects the engineering design. Then, in conjunction with Manufacturing, we decide what EPR’s are not required as make to stock and set the EPR Provide Code to Phantom. Then when I transfer the EPR we end up with the appropriate Manufacturing Structure based on how Production want to build the product.

So I guess this process requires the upload to the EPR plus a transfer, rather than a direct upload to the Manufacturing Structure.

Cheers,

Wade