APQP Jan ("Yon") Roovers President JAN ROOVERS ASSOCIATES, INC.

Slides:



Advertisements
Similar presentations
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Advertisements

How to Document A Business Management System
Where does Failure Mode and Effects Analysis (FMEA) come from?  Developed by the Aerospace industry in the1960s  Spread to the Automotive industry 
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Overview Lesson 10,11 - Software Quality Assurance
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Managing Projects. Contemplative Questions  What does project management entail?  Do I want to be a project manager? What is the nature of the work?
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Computer System Analysis
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Rev 6.1.  Lack of collaboration is a major risk  Late engagement is a risk  How much is new?  How much time?  How many resources?  Design Collaboration.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Team-Based Development ISYS321 Managing the Information Systems Project.
Faculty Economics & Business EBS 2033 Systems Development Lecture 1 The Systems Development Environment Lecturer: Puan Asleena Helmi.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
CJA 444 Week 3 Team Assignment Behaviors and Processes Paper To purchase this material click below link
Process engineering Quality controls.
Integrating QS9000 Requirements
Chapter 1 The Systems Development Environment
Managing the Information Systems Project
Chapter 1 The Systems Development Environment
Chapter 3 Managing the Information Systems Project
Chapter 1: Introduction to Systems Analysis and Design
Week 1: Introduction to Quality Total Quality Management (p.1)
Chapter 1 The Systems Development Environment
BUSINESS PROCESSES MAP
Chapter 1 The Systems Development Environment
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
DSQR Training Control Plans
Chapter 1 The Systems Development Environment
Chapter 3 Managing the Information Systems Project
MBI 630: Systems Analysis and Design
OHS Staff Introduction Training
Chapter 3 Managing the Information Systems Project
APQP Quality Planning in ISO 9000/ QS-9000 or ISO/ TS or .....
APQP PROCESS FLOW Prepare for APQP Plan and Define Program
Web Capstone: Reflection & Documentation
Project Management Process Groups
Chapter 3 Managing the Information Systems Project
RISK REDUCTION PROCESS
Teams What is a team? Maintaining Focus
Chapter 1: Introduction to Systems Analysis and Design
Product and Process Validation JAN ROOVERS ASSOCIATES, INC.
Known as the business team, the Sun Microsystems approach to concurrent or simultaneous engineering may be used during the introduction of new products.
Modern Systems Analysis and Design Third Edition
Failure Mode and Effect Analysis
Lesson 10: IT Project and Program Management
HOW TO AUDIT AND TAKE AN AUDIT
Sales & Service team Learning solution Proposal
Chapter 1 The Systems Development Environment
Chapter 3 Managing the Information Systems Project
Chapter 1: Introduction to Systems Analysis and Design
Chapter 3 Managing the Information Systems Project
Chapter 2 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Modern Systems Analysis and Design Third Edition
Presentation transcript:

APQP Jan ("Yon") Roovers President JAN ROOVERS ASSOCIATES, INC. An introduction to Advanced Product Quality Planning and Control Plans Presented by: Jan ("Yon") Roovers President JAN ROOVERS ASSOCIATES, INC. Charlotte, North Carolina • USA 1

Getting Ready for APQP • Organize the Team • Define the Scope • Establish Lines of Communication • Conduct Training • Involve Customers and Suppliers • Utilize Simultaneous Engineering • Use Formal Problem Solving Methods • Develop a Timing Plan • Focus on Defect Prevention 24

Getting Ready for APQP Organize the Team • Engineering • Manufacturing • Material Control • Purchasing • Quality • Sales • Field Service • Suppliers • Customers 25

Getting Ready for APQP Define the Scope • Select a Team Leader • Define Roles and Responsibilities • Identify Internal and External Customers • Define Customer Requirements • Identify Resources • Understand Customer Expectations • Assess Feasibility of Proposed Design • Identify Costs, Timing, and Constraints • Determine Customer Assistance Required • Identify Documentation Process 26

Getting Ready for APQP Establish Lines of Communication • Customer Teams • Internal Teams • Supplier Teams Team-to-Team contact depends on the number of issues requiring resolution. 27

Getting Ready for APQP Conduct Training • Interpersonal Skills • Effective Communication • Handling Conflict • Analytical Techniques (See Appendix B, Pages 81-85) • Guidelines of APQP and CSRs • Requirements of ISO/TS 16949:2002 • Failure Mode Effects Analysis • Statistical Techniques Tools and techniques selected depend on the type of product and complexity of the project. 28

Getting Ready for APQP Involve Customers and Suppliers • The customer may initiate the APQP with the organization • The organization has the obligation to establish the APQP Team and manage the process • The organization must expect the same performance from its suppliers 29

Getting Ready for APQP Utilize Simultaneous Engineering • Cross functional teams strive for a common goal • Replaces the traditional sequential series of project steps • Expedites the introduction of quality products sooner • APQP Team assures that other areas/teams complete activities that support the common goal 30

Getting Ready for APQP Use Formal Problem Solving Methods • Document design and/or processing concerns on a matrix with assigned responsibilities and timing • Utilize disciplined problem-solving methods (ISO/TS 16949:2002, Clause 8.5.2.1) • Use analytical techniques described in Appendix B (Pages 81-85) 31

Getting Ready for APQP Develop a Timing Plan • Consider: type of product, complexity, and customer expectations • Plan and chart timing elements • Agree with each event, action, and timing • List tasks, assignments, and events • Utilize a consistent planning format • Establish Start and Completion dates 32