668 Scen Overview en US

8/8/2019 668 Scen Overview en US

http://slidepdf.com/reader/full/668-scen-overview-en-us 1/13

668: APQP - Efficient Project

Management with Control Plan

SAP Best Practices for IM&C (US)

SAP Best Practices



Scenario Overview – 1

Purpose The scenario shows the full project management cycle following the

APQP standard.

Benefits

Standardizes the development process by using templates

Increase customer satisfaction Deliver quality products on time with the lowest possible costs

Reduce nonconformity costs by recognizing necessary changes early

Improve communication and decision making processes with internal

and external partners by using Web-based access

Increase the transparency of projects by full integration between project,

documents and cFolders which enables direct access to all project-

related documents

Integration of control plan and PLM backend system help the supplier

raise the project management efficiency as well as quality management

in future production

Purpose and Benefits:



Scenario Overview – 3

Detailed Process Description:

APQP - Efficient Project Management with Control Plan

The OEM requests a new product development from the supplier

The supplier creates the project by copying the APQP template. Changes are

made to the project structure based on the OEM’s specific requirement.

Resources are later assigned to the project, and the project is scheduled

For the first phase - Concept Design, a Q-Gate is defined. After creating the

related template documents for the project, and changing the task status, the

project manager creates an approval

The Quality Manager grants the approval, then the engineers start to create the

control plan for the project

After the control plan is created, it is downloaded as a pdf file. The control plan

is also transferred to the SAP ERP system, and an inspection plan in the SAP

ERP system is generated automatically

The project manager transfers the related data during the project to cFolders,

and the project is completed



Process Flow Diagram

APQP - Efficient Project Management with Control Plan



Define type of

APQP

Review/

ApprovalReview/

Approval

Review

Pre-Production

Release

Review

SOP

Release

1) Concept

Phase

RFQ / Business

case

Development Plan

Regulations (Laws,

Standards,

Objectives)

Continuous

Improvement

2) Product

Design

Design FMEA

Preliminary

Bill of Materials

Specification

Design

collaboration

Control Plan

(Prototype)

3) Process

Design

Process FMEA

Routing creation

Process flow

diagram

Statistical process

Control (SPC)

Control plan

(Model)

4) Validation

Planning and

production under

real-life conditions

Control plan for

series production

and inspection plan

Process audit

Production part

approval process

5) Product

Launch

Quality Inspections

during Production

Requalification

tests

Processoptimization

Advanced Product Quality Planning Phase Approach

A guideline for APQP is included in QS9000, which contains the general requirements on how the supplier

should handle a new product development project to meet the customer requirements by planning the

product and process quality in advance.

In this scenario, the basic requirements from the APQP manual are included in a project template, for

preparing plans and checklists, to ensure that Advanced Product Quality Planning is actually carried out at

the supplier.



APQP (Advanced Product Quality Planning) is a mandatory new product development process for

suppliers in many Industries, in order to fulfill the requirements from QS9000.

To use APQP, OEM and Supplier have the following requirements:

Need a standard template for an APQP project

Different roles and authorization defined for the different parties involved

Detailed processing for the control plan

Transparency to the OEM

With the traditional SAP system, it is difficult to fulfill all the requirements and standards defined for APQP. But we can meet the requirements by using cProject as following:

A business scenario for APQP project management starts by creating a project following the APQPstandard. Roles and authorization should be defined for different parties. Interactive operations betweenthe QM, PM, and engineer at the supplier side are then processed.

A practical control plan should be created during the procedure, and be seamlessly linked to thequality execution system.

The OEM should also have the possibility to check the working procedures and relateddocumentation through a certain system.

Business Background



Supplier

Project Manager Quality Manager Engineer

OEM

New Product

Development

Request

Supplier - cProjects

APQP Project

Create Project based

On APQP template

Resources Planning

Create Project based

On APQP template

Project Scheduling

Q-Gate Setting

Resources Planning

Project Scheduling

Q-Gate Setting

APQP

templa

te

Upload Documents

Concept Design

Maintain Task Status

Upload Documents

Copy/Maintain Checklist

and confirm Status

Maintain Task Status Project EvaluationQ-Gate:

Phase Approval

Create/Download/Print

Control Plan

Export Inspection Plan

To R/3Create Collaboration

Complete Project

Copy/Maintain Checklist

and confirm Status

Project EvaluationQ-Gate:

Phase Approval

Create/Download/Print

Control Plan

cFolders

APQP Project

Folders

Export Inspection Plan

To R/3

Product Design

Concept Design

Design FMEA

BOM

Control Plan

Monitor

Product Design

Process Design

Validation

Product Launch

Design FMEA, BOM,

Control Plan, Process

Flow, Diagram,

Process FMEA,

PPAP Design

Process Design

Validation

Product Launch

Create Collaboration

Complete Project

Information Synchronization Solution for OEM and

Supplier in SAP BP



cProjects is used to control the project, especially the pre-BOM phase

The template is pre-defined in SAP Best Practices for IM&C

Project Template in c-Project



Control Plan created in cProjects can be downloaded as a pdf file

Control Plan created in cProjects can be transferred to the SAP ERP system

An Inspection Plan in the SAP ERP system can be automatically generated

based on the Control Plan

Control Plan in pdf Format



cFolders is linked with cProjects

Related information during the project can be published to the cFolders

The OEM has the possibility to monitor the project remotely

cFolders Linked to the cProjects



Legend

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable Clerk

or Sales Representative. This band can also identify anorganization unit or group, rather than a specific role.

The other process flow symbols in this table go into theserows. You have as many rows as required to cover all of theroles in the scenario.

Role band contains

tasks common to thatrole.

External Events: Contains events that start or end thescenario, or influence the course of events in the scenario.

Flow line (solid): Line indicates the normal sequence of stepsand direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or

conditional tasks in a scenario. Line can also lead todocuments involved in the process flow.

Connects two tasks ina scenario process or a non-step event

Business Activity / Event: Identifies an action that either leadsinto or out of the scenario, or an outside Process that happensduring the scenario

Does not correspondto a task step in thedocument

Unit Process: Identifies a task that is covered in a step-by-stepmanner in the scenario

Corresponds to a taskstep in the document

Process Reference: If the scenario references another scenario in total, put the scenario number and name here.


Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the stepnumbers from that scenario here


Process Decision: Identifies a decision / branching point,signifying a choice to be made by the end user. Linesrepresent different choices emerging from different parts of the diamond.

Does not usuallycorrespond to a taskstep in the document;Reflects a choice tobe made after stepexecution

Symbol Description Usage Comments

To next / From last Diagram: Leads to thenext / previous page of the Diagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies a p rinteddocument, report, or form

Does not correspond to a task step in adocument; instead, it is used to reflect adocument generated by a task step; thisshape does not have any outgoing flowlines

Financial Actuals: Indicates a financialposting document


Budget Planning: Indicates a budgetplanning document


Manual Process: Covers a task that ismanually done

Does not generally correspond to a taskstep in a document; instead, it is used toreflect a task that is manually performed,such as unloading a truck in thewarehouse, which affects the processflow.

Existing Version / Data: This block cove rsdata that feeds in from an e xternalprocess

Does not generally correspond to a taskstep in a document; instead, this shapereflects data coming from an externalsource; this step does not have anyincoming flow lines

System Pass / Fail Decision: This blockcovers an automatic decision made bythe software

Does not generally correspond to a taskstep in the document; instead it is used toreflect an automatic decision by thesystem that is made after a step has beenexecuted.

<Function>

External

toSAP

BusinessActivity / Event

Unit Process

ProcessReference

Sub-Process

Reference

ProcessDecisio

n

DiagramConnection

Hardcopy /Document

Financial Actuals

Budget Planning

ManualProcess

ExistingVersion /

Data

SystemPass/Fa

ilDecisio

n



Copyright 2009 SAP AG

All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein

may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,

eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,

POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,

MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective

logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products

and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other

countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be

construed as constituting an additional warrant.

668 Scen Overview en US

Documents

Transcript of 668 Scen Overview en US