The May release of PLM 360 bought two new ways of importing Bills of Materials (BOMs) into PLM 360. From the Wiki:
There are two new methods for importing BOMs: Level Import and Hierarchy Import. Use Level Import for BOMs that identify each row with a level number. Use Hierarchy Import for BOMs that identify each line item with a sequence of numbers indicating both the parent and its sequence within the parent BOM.
In a previous blog post, You Dropped a BOM on me, PLM 360, I walked through how to use the BOM import functionality (we also did PLM Talk on BOM Import if you’d like to view that recording or check out this tutorial on Importing BOM Data into a Workspace).
Today I want to walk through how to use these 2 new methods (there’s another example on the Wiki as well – I just thought it would be fun to revisit our old flashlight example and do a step-by-step. Besides, it was a good excuse to use the ‘kitty with a flashlight’ photo).
Let’s start with the Hierarchy BOM. In this method, each line in the import file is marked with a sequence of numbers that identifies both its parent and its sequence within the parent BOM[parent number].[sequence]. For example, the item marked 184.108.40.206 is a child of the item market 1.3.2 who, in turn, is a child of 1.3, etc. I like to think of this as the nested view.
Here’s what my Excel file looks like:
When I set up my import project, I make sure I select ‘Hierarchy BOM’ for the Import Type.
You get some guidance with the set up – you’ll be prompted to select the column as hierarchy and from there you’ll select the ‘Match as BOM Hierarchy key’ to indicate that this column will be used to determine the BOM structure when it’s imported:
Next up is doing the column mappings, filling out the relevant options for the import settings, then running the import. As usual, you’ll get some feedback as to what will be created when you import (I like that validation before hitting ‘proceed’!)":
And voilà! Import complete and the BOM looks good:
Setting up for the level import is similar, though here you identify each row in the import file with a level (indentation) number. The parent of each item is the item with the lower level number above it in the file.
Here’s my Excel file for the level import:
Set up is similar, just choosing level rather than hierarchy:
And after the import is run – the results I anticipated:
So there you have it – BOM importing made even easier!
Photo: Adrian Nier