Status

Owner
StakeholdersThe persons consulted or otherwise involved in making this decision. Type @ to mention people by name

Issue

This KDD document identifies the main material inspection processes that will be in scope of the QM stream of ERP Rebuld project.

These are the processes currently running in Syensqo WP1 and PF1 systems, as identified in the AS-IS analysis:

  • Inspection at Purchasing Goods Receipt (01)
  • In Process Production Inspection (03)
  • Inspection at Production Goods Receipt (04)
  • Inspection at Other Goods Receipt (05)
  • Inspection at Customer Returns (06)
  • Inspection at Stock Transfer (08)
  • Recurring Inspection (09)
  • Outbound Inspection (10-11-12)
  • Manual non-stock-based inspection (89)

All these inspection types are used in combination with inspection plans.

We identify the opportunities to introduce:

  • Inspection for Asset maintenance and calibration (14)
  • Sample Inspection (15)
  • Usage of Material Specification instead of / in combination with Inspection Plans


Recommendation

Option A is the recommended one: introduce in scope of the project inspection types 14 and 15 and allow the usage of Material Specification.


Background & Context

The two systems PF1 and WP1 have a very similar QM model, based on custom inspection types which are copies of the original standard types. 

Material inspection is largely used in SAP ECC, in some cases in combination with Labware and WEBLIMS, in other cases with a full E2E process in SAP.

The QM Material Inspection is a crucial part of the traceability and Quality Assurance process in Syensqo and involves all steps of the process: Inbound, Production, Outbound, Stock Management.



Assumptions

  • the new ERP system will be S4 HANA version 2023 or higher
  • one single instance will exist, instead of the current WP1, PF1 and WPX
  • current Labware and WEBLIMS systems remain
  • the QMS project with EQT will go on only for Composite GBU, while Specialty Polymers and the other GBUs will investigate the corresponding SAP functionalities in the Detailed Design phase


Constraints

  • We must guarantee the ability of each GBU and each single plant to maintain their own inspection plans where required

Impacts

  • it is a basic requirement to introduce Inspection type 14 (calibration) to integrate properly SAP S/4HANA Asset Management for Resource Scheduling


Business Rules

A decision tree will be designed in Detail Design to identify the inspection types to be activated for each material.

A decision tree will be designed in Detail Design to define whether a material specifiation or an insection plan should be created to host the tests required for a new material.

Options considered

Option A: Add Inspection Types 14 and 15 to the scope and allow material specification

Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly


Option B: Keep only currently used Inspection Types and do not allow Material Specification

This option is a replica of the current AS-IS solution. It would not be possible to create Inspection Lots for Samples and for Tool Calibration. It would be mandatory to use Inspection Plan for each material/plant to inspect.


Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.



Option A

Option B
Criterion 1

(plus)Pro

(minus)Con

(plus)Pro

(plus)Pro

Criterion 2

(plus)Pro

(minus)Con

(minus)Con
Criterion 3(plus)Pro(minus)Con

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.


Change log

Workflow history