eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release
Apache License 2.0
8 stars 10 forks source link

[R24.12] Traceability KIT Adaptation: Notifications Extension: Block-notification #782

Open RicardoSchlatter opened 3 months ago

RicardoSchlatter commented 3 months ago

Description

Introduction

The blocking process is a process in the automotive industry to segregate or quarantine nonconforming parts in the supply chain to prevent using them in the production process. Therefore, the supplier must send all relevant information to the customer, so that he is able to identify the affected parts at the assembly line or in logistics.

Target

Data on the particular parts is collected within the supply chain, but not systematically forwarded to the OEM. The aim is to improve and standardize an automated data exchange and consistency for blocking information.

Now there are two types of quality notifications. (quality alerts and quality investigations). The goal is to implement a third type for the blocking process (blocking-notification) and herby extend the Q-Notifications.

Key Benefits

The key benefits are that the blocking process will be much faster and more accurate as you can trace the defective parts whole down to the bottom of the supply chain and send standardized report of the defective parts to the customer. So, there will be a striking decrease of effort and costs in the blocking process and the end customer acceptance will increase noticeably when there are more precise recalls and a higher quality of products.

Proposed Solution

A solution to solve the problem is to extend the existing q-notification with a new standardized data model to exchange data for blocking parts from the supplier to the customer.

These are some attributes which should be considered during the development of the aspect model of the blocking information.

Part Number | -- | -- Change index | Control Unit ID | Supplier number | Counting address | Production date | Size of production lot | Delivery bill number | Package number | (Handling unit) | Delivery place | Delivery date | Number of parts per delivery bill | Number of parts per package | Order number | Serial/component number |

Implementation Plan

The new aspect model will be discussed and worked out in the Traceability expert group in the feature team for the “Enhancement of quality notifications” in a sub team for “Blocking Process”. The discussion on this topic has already started with a kick-off meeting. Next step will be to define a working model and working session to develop the aspect model.

Cost and Resources

No external cost estimated. Input and review are expected from the expert group.

Contact Information

Feature Team: Blocking Process

BMW

Steffen Düring

Impact

Additional information

Committers are: @maximilianong, @danielmiehle

stephanbcbauer commented 3 months ago

Presented in the DRAFT Feature Freeze -> Committer needed

stephanbcbauer commented 3 months ago

Maybe dependency to quality expert group

SteDue commented 3 months ago

@RicardoSchlatter: As I do not have editing rights - could you please update our description text within the feature at all relevant places? Thank you

Introduction  

The blocking process is a process in the automotive industry to segregate or quarantine nonconforming parts in the supply chain to prevent using them in the production process. Therefore, the supplier must send all relevant information to the customer, so that he is able to identify the affected parts at the assembly line or in logistics. 

Target 

Data on the particular parts is collected within the supply chain, but not systematically forwarded to the OEM. The aim is to improve and standardize an automated data exchange and consistency for blocking information 

Now there are two types of quality notifications. (quality alerts and quality investigations). The goal is to implement a third type for the blocking process (blocking-notification) and herby extend the Q-Notifications. 

Key Benefits 

The key benefits are that the blocking process will be much faster and more accurate as you can trace the defective parts whole down to the bottom of the supply chain and send standardized report of the defective parts to the customer. 
So, there will be a striking decrease of effort and costs in the blocking process and the end customer acceptance will increase noticeably when there are more precise recalls and a higher quality of products.   

Proposed Solution 

A solution to solve the problem is to extend the existing q-notification with a new standardized data model to exchange data for blocking parts from the supplier to the customer.   

These are some attributes which should be considered during the development of the aspect model of the blocking information. 

Part Number |   -- | -- Change index |   Control Unit ID |   Supplier number |   Counting address |   Production date |   Size of production lot |   Delivery bill number |   Package number |   (Handling unit) |   Delivery place |   Delivery date |   Number of parts per delivery bill |   Number of parts per package |   Order number |   Serial/component number |  

 

 

Implementation Plan 

The new aspect model will be discussed and worked out in the Traceability expert group in the feature team for the “Enhancement of quality notifications” in a sub team for “Blocking Process”. The discussion on this topic has already started with a kick-off meeting. Next step will be to define a working model and working session to develop the aspect model. 

Cost and Resources 

No external cost estimated. 
Input and review are expected from the expert group. 

Contact Information 

Feature Team: Enhancement of Q-Notifications:  

BOSCH 

Corina Stolz 

Sub Feature: Blocking Process 

BMW  

Steffen Düring 

RicardoSchlatter commented 3 months ago

@RicardoSchlatter: As I do not have editing rights - could you please update our description text within the feature at all relevant places? Thank you

@SteDue Done!

stephanbcbauer commented 3 months ago

Release Planning Day: Implementation/adaptation of the reference implementation will be done in the next release -> Please create an Issue for this to not forget it