25_1330b_Kohlhoff-Vo_

Andreas Voß, Pierburg GmbHiViP Symposium, 25. April 2007, Wolfsburg

Global Engineering Change Management usingSAP Records Management

2© Pierburg GmbH 2005 – Schutzvermerk ISO 16016 beachten.

Agenda

Table of Content

1. Pierburg GmbH – The Company

2. Initial Situation and Requirements

3. Solution in Detail

4. Next Steps





Rheinmetall Group

Rheinmetall Defense

Revenue: € 2.000 Mill.Employees: 11.700

Revenue: € 1.400 Mill.Employees: 6.800

Leading European Defense Companyfor Military Technology

Leading Supplier for EngineComponents and Systems

Rheinmetall AGRevenue 2005: € 3.400 Mill., Employees: 18.500



Structure of Kolbenschmidt-Pierburg Group

Revenue :638 Mill.€Employees :5.779

KS Piston

Revenue :171 Mill €Employees :1.015

KS SlideBearing

Revenue :210 Mill.€Employees :1.007

KS AluminumTechnology

Revenue :160 Mill.€Employees :375

Engine Service

Revenue:903 Mill.€Employees:3.483

Pierburg

Kolbenschmidt Pierburg AGRevenue 2005: 2.0 Bill. € , Employess: 11.700



Worldwide Locations

Spain:Abadiano

France:Thionville

Germany:Nettetal

Germany:Berlin

Germany:Hartha

China:Shanghai

Italy:Lanciano

Brasil:Nova Odessa

USA:Fountain Inn, SC

Italy:Livorno

Czech:Ústí nad Labem

GermanyNeuss



Development Locations Europe

Thionville

Neuss,Central Engineering Center

Berlin

Hartha

Livorno



Pierburg – Information Technology

SAP R/3 4.6 C Automotive(CO, FI, MM, WM, PP, QM, PM, SD, PS, DMS)

SAP ERP 5.0 Human Resources (HR)(PM, PY, PT, OM)

SAP Advanced Planer & Optimizer (APO)(DS, DP)

SAP Records Management (RM)

ERP

Central, global SAP-SystemCATIAUNIGRAPHICSPro/EIdeas

SMARTEAMSAP

CAD

PLM

IT-OutsourcingIBM Mittelstand Systeme GmbH

Mail + PortalLotus Notes/DominoSAP Enterprise Portal






Initial Situation – IT Tools

Lotus Notes based tool for change managementNo integration with master data in SAP R/3

Material master

Bill of material

Document Info Record

Change master, etc.

No integration to transaction data(Stock, etc.)

No Integration with various functions(e.g. Where-used-list)

Inflexible Workflows



Forwarding of Information (Costing,Change Notification, ...) asExcel Attachment

KE DURCHGEFÜHRT

JA NEIN

EMPB Freigabemuster v. Lieferant

JA NEIN JA NEIN

A N

Dokum ent-Nr. T/B S ZI FO DA SY 3D CAD-KD-Umgebung A/D W N V

2.04434.06.0 - E S -

D-2 04434 000 01 - 06 A0 PZD C X Pierburg -

3.04434.06.0 - E S -


- - - -


7.01062.05.0 11 S S -

- - - - PZD S - SAP -

NR Produkt-Nr. NR

1 7.01062.05.0 5

2 63 7

4 8 AGS

Blatt 1 von 1

2.04434.05.0

3.04434.05.0

-

-

Kunde: DAEWOO P-PBQ 1/2/12

12Typ: EDR-Di P-PBA 11/12

P-PBL 11/12 Änderungs numm er

Produkt: DKS P-PBF 11/2/3526344

P-ZC1/P-EZL2 genehm igt: Gläßer

P-EZL21

S-ZP / P-ZL2 PSP-Element-Nr.: A-000065-01-S2-02Änderung der Fase am Gehäuse D-3 04434 000von 0,8 x 45 grad in 0,4 x 45 grad und Kantenbruch 0,15 mm hinzu

EINSATZTERMIN :13.05.05

Bearbeiter: Witta

P-ZB / P-ZS2 Datum: 06.04.2005

Produkt-Nr. Verteiler Änderungsgrund / Bem erkung Konstr.Gr.:

8

7

6

5

siehe Anlage4

P-PB - STÜCKLISTE

siehe Zeichnung3

P-PB - REGELKLAPPE

siehe Zeichnung +Stückliste2

P-PB siehe Rohteil GEHAEUSE

siehe Zeichnung +Stückliste1

P-PB ENAC-AlSi12Cu1(Fe)df DINEN1706 GEHAEUSE

BenennungÄnderungs-

beschreibung

Verw endungAlte Mat.-Nr.

Pierburg Kunde

Zeile

Material-Nr. TI Status PW L Werkstoff

Änderungsanweisung (AEA)Techn. Freigabe: EMPB Freigabemuster / Ergänzungsmusterung an Kunde

L = Lieferanten geb. DA = Dokumentenart AGS = ÄnderungsgrundschlüsselT/B = Teil / Blatt FO = Format A / D = Archiv. / Dokumentationspf licht V = VerschrottenPW = Produktionsw erk ZI = Zeichenindex 3D = 3-D Modell N = NacharbeitenTI = Teileindex S = Seite SY = Erstellungssystem W = in w eiteren Verw endungen

X X

X

X

Kunde

Einlauf WerkzeugMaterial-Nr. ------------------

Dokument-Nr. Inves tition KST ± TE/% ± €/%

2.04434.06.0

D-2 04434 000

3.04434.06.0

D-3 04434 000

NR Erzeugnis-Nr NR Erzeugnis-Nr NR Abteilung Nam e Datum

1 7.01062.05.0 5 9

2 6 10

3 7 11

4 8 12

Ja Vertrieb /Controlling

Unterschrift:

GEHAEUSE

GEHAEUSE

06

06

Anreger:Pierburg

Kostenübernahme:Kostenermittlung (KE)

in € Pierburg Lieferant

Zeile ZI Benennung

Men

ge SKD Bem erkung /geplanter ÄnderungseinsatzMaterial-Nr. Neu

Dokument-Nr. Alt

AuslaufZI

MEK €/%Fertigung

12.04434.05.0 EFD-2 04434 00 EF

1 05Gehaeuse als Gussteil undBearbeitung istEigenfertigung.

23.04343.05.0 EF

D-3 04434 000 EF1 05

3

4

5

6

7

8

P-EZL 21

Art der Änderung / Bemerkung BEARB.: Exner

Erzeugnis-Nr K.GR:

PSP-Element-Nr.: A-000065-01-S2-02Änderung der Fase am Gehäuse D-3 04434 000von 0,8 x 45 grad in 0,4 x 45 grad und Kantenbruch 0,15 mm hinzu

GEPR.: Gläßer

DATUM: 04.04.05

KE-NR.: 526344

1 von 1

Erzeugnis: DKS ERS.F.KE-NR.

Typ: EDR-DiBl.

Kunde: DAEWOO

ÄnderungsanweisungGenehmigung Nein Datum:

Blatt

X



Requirement for a New Solution

System based management of „Change Forms“ change request,change order, etc.

Integration of master and transaction Data

Flexible workflow control

Management of related documents

Extensive reporting

Mail integration with Lotus Notes

Support of international locations

SAP based solution, since SAP is strategic platform for Pierburg






Phases of Engineering Change Process

ECR (EngineeringChange Request)

ECI (EngineeringChange

Implementation)

MCI (ManufacturingChange

Implementation)ECN (Engineering

Change Notification)

M1Change Request

issued

M2ECN

release

M3ECR

released

M5Change

completed

M4ECI

completed

Responsibility: BU Responsibility: Plant





Implementation)







M1Change Request

issued

M2ECN

release

M3ECR

released

M5Change

completed

M4ECI

completed


Basic Data

Pierburg specificdata fields



Basic Data

Integration of „Original“ SAPdata fields-> Input help-> Data validation



Collect Affected Parts –ATO-Cockpit (AusTauschObjekt)

-> Input material numbers to be exchanged-> Input help, data validation



Plants

1. Read plant specific records of materials

2. Display in ATOC 3. Automat. read of „virtual attributes“



Integrated “Where-Used-List“

1. Call “Where-Used-List“ from ATOC

2. Store “Where-Used-List” in VN Cockpit

Original Direct Predecessor Usage



3. Evaluate Usage w.r.t. change relevance




4. Transfer of affected materials into ATOC (change scope)




Detailed Information (Customer, Stock, ...)



Documents for Material (e.g. Drawing)



Team Definition / Distribution List



Release Change Request



Process Route

Initiate follow-on tasks



Information im Mailsystem

Drill-down to change case





Implementation)





M1Change Request

issued

M2ECN

release

M3ECR

released

M5Change

completed

M4ECI

completed




Complete Process Route

Extension of the process route by authorized user-> sequential-> parallel-> template or single step-> directly to user or roles from the project team



Compile Information from Departments(eval. documents, costs, ...)

Status dependent Layout: here: Costing



Create Attachments



Change/Display Attachments





Implementation)







M1Change Request

issued

M2ECN

release

M3ECR

released

M5Change

completed

M4ECI

completed


Creation of Change Master Record



Definition of Change Package



Maintenance of Material Master




Maintenance of Material Master




Implementation)





M1Change Request

issued

M2ECN

release

M3ECR

released

M5Change

completed

M4ECI

completed




Same Technical Procedure as inPrevious Phases

Extension of Process Routes (via single items or templates)

Input of Data in ATOC

Drill-Down to Maintenance Transactions

Documentation of Change Status by Advancement of StatusControl Net



4. Next Steps

4. Next Steps


Goal 2007 ff.: Implementation of SAPRM as an Integration Platform for ....

Market

Strategy

Technology

Pre-DSelectionProcess

Pre-DAdvance

Development

PDPProduct

Development

ECMEng. ChangeManagement

LiPLicense

Management

PTPProduction

Transfer???

4. Next Steps


Solution Scenarios

4. Next Steps

The presented solution is a Pierburg specific projectsolution

ILC PROSTEP offers components as a productFurther information is with ILC PROSTEP


Questions ?

End

Contact:

Andreas Voß

Mail: [email protected]

mailto:[email protected]

25_1330b_Kohlhoff-Vo_

Documents

requirements10 pierburg

requirements11 pierburg

company4 pierburg gmbh

company5 pierburg gmbh

company6 pierburg gmbh

company7 pierburg gmbh

company8 pierburg gmbh

company9 pierburg gmbh