Welcome to BOM Hell

Im Beitrag werden Bezeichnungen und Kategorisierungen von Stücklisten (BOMs) sowie das RIM-360°-Multi-Structure-Model vorgestellt.
Post 1

Welcome to BOM Hell – Is As Built = M(RP)-BOM and As Designed = EBOM? Let’s resolve the discourse 🤔

Now, particularly popular are the following categorizations:
👉 Categorization 1: As Planned BOM, As Designed BOM, As Built BOM, As Delivered BOM
👉 Categorization 2: CAD-BOM, E-BOM, M-BOM, TOS, M(RP)-BOM…

Now, what does this mean? First of all: Don’t bother mapping both categorizations. It works in theory but breaks down in deeper discussion. I think these are often categorizations of the same thing from different perspectives and at different levels of detail.

👉 Categorization 1:
The As … BOMs focus on a defined point in time in the process. This categorization simply states that these BOMs have different contents at different times. That’s all. What the BOMs are used for, who creates them, their semantics, and what business objects they carry (document, part, material or equipment) is not clear.

👉 Categorization 2:
The xBOMs are named BOMs, where the first letter (e.g., E and M) tries to denote the area in which the BOMs are used or created. This categorization is also vague. Since it comes from the PLM world, specific BOMs from the ERP are missing.

To be more precise, let me try with an example. We start from STO  (Select to Order) , represented in #Teamcenter and #SAP.

In STO, we have a Product Development Process. By SOP (Start of Production), an M(RP)-BOM must exist in the ERP. This is created via a CAD-BOM in Teamcenter, goes through an E-BOM-like Part BOM in Teamcenter, and is then transferred as a document structure (better to do it this way!) or a corporate BOM (no plant in the BOM in SAP) into SAP. From this, a plant-specific M(RP)-BOM is created. Through the MRP run, manufacturing orders are now instantiated. These have a component list (also a BOM). This list controls the stock withdrawal. Material may be exchanged there. In this scenario, the corporate BOM would be something like the As-Designed BOM, the M(RP)-BOM could be described as the intended As-Built BOM. The sum of the component lists from the manufacturing orders of a product would be an As Built BOM after the disposition of the parts (if you need the instances then equipments). These would also be the As Delivered BOM, since nothing changes in STO after that.

Now, you see, it is complicated. Therefore, it is better to 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 your opinions.

📝 #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 Single-Structure Concept that was preached for years?

A BOM, why do we need more, customers always asked. Often, when we from STZ-RIM Reshape Information Management explained the Multi-Structure Concept in workshops, we felt that the participants believed we were a bit crazy.

Well, that has changed today. A little bit. It’s still feels weird 😊.
Especially when we show our RIM 360° Structure Model. That is why we usually, don’t explain it completely but just parts of it.

Anyhow – today, I want to show you exclusively our RIM 360° Multi Structure Model. It’s our reference for which structures and business objects are relevant in companies.
Attention, it’s not complete. Particularly, business objects from Finance and Controlling are still completely missing (the slide was too small).
I thought I’d explain the essential aspects of it in a series of posts here on LinkedIn.

First, however, some general explanations about the picture.
What you see are the essential business objects a company model needs and their relationships. These business objects are organized into two principal types of structures.

Firstly, there are structures that work on the principle of „Part of“. These are the classic BOMs that summarize parts of a whole. These are shown in the black rectangles with implied structure (round nodes).

Secondly, there are the classifying structures. These work on the principle of „is a“. These are shown without black rectangles and have these rectangular nodes.

Now for 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

Really a bit crazy, the whole thing.

So, what do you think?
Which structures are missing?
How do you name the structures?
Which IT system should the structures live in?
Which structures would you like to have a deeper discussion on?

Well, and if you need a Multi-Structure Concept tailored to your company, then contact us today at STZ-RIM.

#Innovation #BusinessModel #Engineering #DigitalTransformation 🚀💡🔧

YouTube

Mit dem Laden des Videos akzeptieren Sie die Datenschutzerklärung von YouTube.
Mehr erfahren

Video laden

YouTube Video

As…Bom’s vs. x-Bom’s – Jörg was machst du?

Das YouTube-Video von unserem STZ-RIM-Kanal verdeutlicht die Thematik nochmals in Bild und Ton auf Deutsch.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert

Weitere Artikel

Im Beitrag werden Bezeichnungen und Kategorisierungen von Stücklisten (BOMs) sowie das RIM-360°-Multi-Structure-Model vorgestellt....