LinkedIn post 1
The 7 keys to solve PLM & ERP - Did you know them all?
Recently Martin Eigner and I posted that we have solved PLM and ERP: The solution for PLM & ERP | STZ-RIM Here are a few initial insights for you from my perspective.
The seven keys to solve PLM & ERP.
If we bring classic PLM as we know it closer to ERP, there are a number of key issues that I like to subsume under the term ERP-related PLM.
So what are they and what do they mean? Here is a brief explanation. In a series of posts, I would then like to describe the individual keys one by one.
👉 Structure Supply Sequence is the centerpiece that connects PLM & ERP!
Product structures can be seen as a data highway. They supply each other with information. A structure supply sequence is formed for each process pattern, product architecture and production concept.
👉 Revison & Effectivity Based Lifecycle Threads
The transition from PLM to ERP is characterized by a change in the lifecycle threads. In PLM, the lifecycle threads are revision-based. In ERP, they are effectiveness-based. The transition and handling is characterized by the requirement for form fit function (F3) of the respective company
👉 Portfolio Hierarchization
In all process patterns (ETO, CTO,...) there is a hierarchy above the products that shape the portfolio. The portfolio of a company is characterized by a variability that often exists implicitly in ETO, but must be made explicit on the way to CTO. The necessary hierarchy, its variability and rules are subject to a lifecycle that has to be managed close to the ERP, and the variability in particular also contains production control options
👉 Generic Structure Instance Embedding
CTO+ requires a flexible modular system. In future, its structure must be built generically for each product line across the entire product structure down to the sheet level. Instantiation from this modular system will then take place horizontally and no longer vertically, as was previously the case.
👉 Object Type Cascade
In the future, we will have to differentiate engineering materials from production materials much more frequently due to extended supply chain requirements. An engineering material will then give birth to a series of production materials. This results in a new cascade of object types.
👉 Supply Chain Steering
Sustainability, regulation and the development of resilient supply chains will require much more precise supply chain management in the future. This is done from the M(RP)-BOM and the ad hoc attribution of material.
👉 Production Near Lifecycle Management
Late changes to the production order will be the new normal. This calls for lifecycle management that is close to production, consistent and traceable.
More on the respective topics in subsequent posts, which will be continuously added to here.
What do you think? Have I forgotten the key?
By loading the video, you accept YouTube's privacy policy.
Learn more
You can find the video on our YouTube channel: How do PLM & ERP work together? Here are the seven keys to success. (youtube.com)
LinkedIn post 2
7 keys to solve PLM & ERP
Key 1: Structure Supply Sequence 🔑
Today I would like to describe the first of the 7 keys to solve PLM & ERP.
Let's take a look at the past.
What was it like in the past when there was only PDM or CAD and the products were not yet smart? 🤔
👉 In the past, the necessary documents and drawings for a product were created in an engineer's head and then transferred to production. 🛠️ With the advent of "smart" parts in products, i.e. software and mechatronic components, and the introduction of modern CAD and PLM systems, this has changed fundamentally. 💡
👉 Today, a wide variety of product master data is created in a large number of engineering applications. The life cycle of this data, i.e. how it changes over time, is supported and managed by PLM. The master data required for ERP, e.g. in the form of parts lists, material master information and operations, is then derived from this product master data. 📊
When developing a product, the first step is to create structure types close to the development stage, such as CAD structure and EBOM (Engineering Bill of Material). These then supply downstream structures such as the MBOM (Manufacturing Bill of Material) and routings with information. 🔄
....and this results in the structural supply sequence.
Its task is to supply the product data to the places where it is used, e.g. in the M(RP) BOM or structure BOM in the ERP or in the service BOM. The structure supply sequence therefore routes the necessary information for the core tasks of the ERP to these locations. 🛤️
It is therefore the freeway from PLM to ERP. 🌐
On the surface, structural supply consequences often appear to be the same. However, when viewed in detail, they are individual to each company. Their design is influenced, among other things, by the process pattern, the individual product architecture, the modular kit strategy, the supply chain and the production strategy. 🏗️
What do you think?
What does your structural supply sequence look like and where do you want to develop it?
To be continued...
