Post 1
Welcome to BOM Hell - Is As Built = M(RP)-BOM and As Designed = EBOM? Let's resolve the discourse 🤔
Do you know this? When the consultants whirl the names for the BOMs around your head and you wonder what is what and how you can relate them to each other? 🧐
Well, the following categorizations are particularly popular:
Categorization: As Planned BOM, As Designed BOM, As Built BOM, As Delivered BOM
Categorization: CAD-BOM, E-BOM, M-BOM, TOS, M(RP)-BOM...
Well, what does that mean? First of all, don't bother mapping both categorizations. That may work at first, but it breaks down in the deeper discussion. I think, as is so often the case, these are categorizations of the same thing from different perspectives and with different degrees of sharpness.
Categorization 1:
The As ... BOMs are focused on a defined point in time in the product development process. The categorization merely determines that these BOMs have different contents at different points in time. And that's it. What the BOMs are used for, who creates them, what their semantics are, which business objects they carry (document, part or material), is not clear.
Categorization 2:
The xBOMs are named BOMs, whereby an attempt is made to designate the area in which the BOMs are used by the first letter (e.g. E and M). This categorization is also too vague. As it comes from the PLM world, specific BOMs from ERP are missing.
To be precise, I'll try an example. We start from STO, mapped in Teamcenter and SAP.
With STO (Select to Order), we have a product development process. An M(RP) BOM must be available in the ERP for the SOP (Start of Production). This is created via a CAD BOM in Teamcenter, goes via an E-BOM-like Part BOM in Teamcenter and is then transferred to SAP as a document structure (better this way!) or group BOM (no plant entered in the BOM in SAP). A plant-specific M(RP) BOM is created from this. Production orders are now instantiated via the MRP run. These have a component list (also a BOM). This controls the stock withdrawal. Parts may still be exchanged there. In this scenario, the group BOM would be something like the as-designed, the M(RP) BOM could be described as intended as-built. The sum of the component lists from the production orders of a product would be an As Built after the parts have been scheduled. These would also be the As Delivered at the same time, as nothing changes in the STO afterwards.
Well, you see it is unfortunately so complicated. Therefore, it is better to simply keep the two categories separate and remember that category 1 the As (...) BOMs are essentially suitable for strict ETO cases.
Any questions or comments? I look forward to hearing your views.
📝 #PLM #ERP #Teamcenter #SAP #ProductLifecycle
Post 2
BOM Hell - the xBOM's - I'm sure they say he's crazy when I explain that.
Do you remember the one-structure concept that was preached for years?
One BOM, why do we need more, the customers always asked. When we at RIM explained the multi-structure concept in workshops, we often had the feeling that the participants thought we were a bit crazy.
Well, that has changed today. A little 😊. It's still funny.
Especially when we show our RIM 360° Structure Model. Now usually we don't explain it completely, but only parts of it.
But today I want to show you our RIM 360° Structure Model. It is our reference for which structures and business objects are relevant in companies.
Attention, it is not complete. In particular, business objects from Finance and Controlling are still missing completely (the slide was too small).
I thought I'd explain the key aspects of this in a series of posts here on LinkedIn.
But first a few general explanations about the picture.
The main business objects required by a business model and their relationships are shown. These business objects are organized into two basic structure types.
On the one hand, these are structures that function according to the "part of" principle. In other words, the classic BOMs that combine parts of a whole. These are shown in the black rectangles with an implied structure (round nodes).
On the other hand, there are the classifying structures. These work according to the "is a" principle. These are shown without rectangles.
Now to the abbreviations:
GPS: Generic Product Structure
PRES: Product Requirement Element Structure
FSES: Functional System Element Structure
PSES: Product System Element Structure
EBOM: Engineering Bill of Materials, sometimes also Enterprise Bill of Materials
TOS: Technical Order Structure
M(RP)-BOM: Manufacturing Resources Planning Bill of Material (it's MRP II 🙂
SBOM: Service BOM - I may change the Name here in the future
DTasD: Digital Twin as Delivered
DTasM: Digital Twin as Maintained
WBS: Work Breakdown Structure if using Project System
PM Tasks: Project Management Tasks if using Project System
The whole thing really is a bit crazy.
So now, what do you think? Which structures are missing? How do you name the structures?
For which structures would a more in-depth discussion be important to you?
Well, and if you need a multi-structure concept tailored to your company, then get in touch with the STZ-RIM.
By loading the video, you accept YouTube's privacy policy.
Learn more
