S
Engineering R&R 10.7
S
General update Engineering R&R 10.7
Specifications -
PCC & manufacturing at DIFFERENT location vs. at SAME location
> General collaboration PE/ME
> Simultaneous Trial/pre RFC review
> One voice communication
Open discussion, experience sharing, Questions
S
技术 R&R 更新概览 10.7
Specifications 说明 -
PCC & 生产在不同的地点 VS. 在相同的地点
> PE/ME 合作概览
> 模拟试做 /RFC 前回顾
> 同一个声音沟通
公开讨论，经验分享，问题
PE – PR, Additional time for VC
S
FROM
TO
PE – PR/PRO/KAPMO,
S
Activity adjustment & additional time
FROM
TO
PE – ST/PRE RFC Review, Stage adjustment
S
FROM
TO
ME – PRO, Additional TD code responsibility and time
S
FROM
TO
ME – ST/PRE RFC Review, Stage adjustment
S
FROM
TO
ME – EST/FSR, Activity adjustment
S
FROM
TO
ME – FSR, Additional activity and time
S
FROM
TO
ME – FDPA, Removed TD code F level responsibility
S
FROM
TO
Location Specifications
S
SAME location
PCC PCC
Manufacturing Manufacturing
DIFFERENT location
Collaboration PE/ME - @ KAPM
S
PE
ME
Collaboration PE/ME - @ KAPM
S
PE
ME
Collaboration PE/ME - @ ST/PRE RFC Review
S
PE
ME
Collaboration PE/ME - @ ST/PRE RFC Review
S
PE
ME
Collaboration PE/ME - @ ST/PRE RFC Review
S
PE
ME
One Voice Communication – PR through RFC & RFC to Manufacturing S
Purpose Process
To simplify the complex The overall process is Prior to RFC – ITP to RFC confirmation
communication being divided into two The communication during this period should be led by the PCC for direct
communication to Beaverton category development team and cc’d to Off -shore
channels to ensure all sections teams. It is important to ensure that all suggestions from manufacturing should
stakeholders are on the “Prior to RFC – RFC” be discussed, get consensus before communicating all stake holders . If no
consensus arrived, manufacturing suggestions should not be filtered, included
same page throughout
and in project file by the PCC team and transparency is maximized by all
the process stakeholders.
“Post RFC – FSR”
Post RFC – MST through to FSR confirmation
The communication during this period should be led by the manufacturing
team Off-shore for direct communication to Beaverton with results and
recommendations for any possible changes to the product through
commercialization and cc’d to the original development team
S
BVTN. DEV. PCC GTM/KAPM STAGE BVTN. DEV.
BVTN. Receives PRO PCC: receives BVTN. BVTN. Receives KAPM
ITP/PR THROUGH TO RFC CONFIRMATION – LEAD BY PCC/NLO (PRIOR TO RFC)
combined project file feedback & expectations combined project file
from PCC/Off- shore on revisions. from PCC/Off- shore
sources plus look see PCC executes new sources plus look see
samples. Evaluates & samples for GTM/KAPM samples. Evaluates &
gives possible revisions & & prepares tech package gives possible revisions &
sends back to PCC & Off- for BVTN. & Off-shore. VC MEETING sends back to PCC & Off-
shore for GTM/KAPM PCC prepares shore for Pre-RFC & ST
stage GTM/KAPM project file Teams review findings stage
If Bvtn. gives feedback it with combined from the tech package, If Bvtn. gives feedback it
is important to ensure comments and sends to agree on which are the is important to ensure
all stakeholders are
copied
BVTN. & copies Off-
shore. (Techpackage
issues that need be
addressed from
all stakeholders are
copied
PRE-RFC/ST
send within 48 hours of development &
dispatch of sample to manufacturing for the
WHQ) GTM/KAPM stage.
MANUFACTURING Agreement on what
needs to be sent to
Receives GTM/KAPM BVTN. By both teams
revisions/suggestions in VC to be held within 3
preparation for new tech working days of feedback
package being developed being supplied
by PCC the for PCC to supply feedback
GTM/KAPM stage to BVTN, within 2
working days of VC
agreement
MANUFACRUTING INTERNAL REVIEW
Receives GTM/KAPM PCC: Should give
tech package & reviews feedback on Off-shore
their trial, feedback suggestions that were
should contain not accepted, reasoning
suggestions on possible for not using them.
KAPM
solutions to This can be used as a
manufacturing issues learning tool.
(Feedback to PCC &
Beaverton category
within 7 working days)
PCC RFC STAGE MFG (EXT) BVTN. DEV.
S
MST THROUGH TO FSR CONFIRMATION – LEAD BY OFF-SHORE (POST RFC)
PCC executes RFC trial on Off –shore receives the BVTN. team receives
confirmation and RFC tech package and results from the extreme
agreement of a proceeds with the trial plus the required
successful ST trial. Extreme trial grading & shoes and tech packages
executes a trial. when necessary (as per
PCC prepares full RFC
tech package for the Off- Trail report is written up
category requirement) FSR Stockfit/FSR
shore to begin their and results are Communicates directing
commercialization communicated to both to Off-shore & cc’s
process. the Beaverton team & PCC /PMO teams
cc’d to the PCC/PMO
PCC confirms RFC, teams
executes trial report and
sends data to BVTN. & Trial samples sent to
both locations
copies Off-shore
VC MEETING
Results are reviewed
between off-shore and
PCC teams on results
plus possible
recommendations back
to Beaverton
VC meeting is required
for key models and any
trial issues
PCC/PMO
PCC receives results if
the Extreme trial with
possible
recommendations for
EST
changes based on Off-
shore findings
S
NO Shortcuts
Trials
Engineering R&R
Communication
If so, utilize the benefit of PCC and Manufacturing
are at same location.
For example, instead of VC conduct a meeting,
instead of ST conduct
Pre RFC review trial.
RELATED BOX FOLDERS
S
Engineering R&R
[Link]
One Voice Communication
[Link]
ST Procedure
[Link]
RFC Procedure
[Link]
Global Trial Definitions
[Link]
Tech Package Requirements
[Link]
Project File Requirement
[Link]
S
Experiences?
Questions?
OPEN DISCUSSION
S
T HAN K
Y O U!