曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
Problems with the KUTD system
People do not have the
training or knowledge to
flow all that is required
Customers are not
reviewing all the orders
(especially on repeats)
Purchase Order review by the
customer to ensure the correct
notes are applied to the contract is
not robust
Supplier C & S
2.0 Requirements and Flowdown
Team Leader: Barb O’Dell
2.1 How to clearly identify and communicate requirements
throughout the supply chain
Team Leader: Barb O’Dell
Team Members: Gordon Rosner, Arne Logan, George Udris, Jarie Hermie, Wes
Wilkey
2.2 How to generate a shared understanding of the
requirements
Team Leader: Gayle Roland
Team Member: Jay Park, Michelle Pierce, Dave Trucksis
2.3 How to manage revisions to requirements after initial
contract/purchase order release
Team Leader: John Skokos
Team Members: Dale Gordon
7.4.2j Sub tiers are getting the suppliers
interpretation of what the customer's
requirements are, not the accurate flowdown.
All the necessary
requirements aren't
flowed.
People do not have the
training or knowledge to
flow all that is required
7.2.2 People who
own the task of PO
review, how do they
know how to do it?
7.2.2 Supplier
misunderstands
requirements
Complex and
complicated
specs
7.4.2a,e &f Access to
specs by subtiers. . The
first tier is responsible to
identify and send the
required data.
7.4.2a Specification
Pull system is a
problem .. suppliers
overloaded
Special process houses
don't have access to our
specs!
7.2.2 9100 oversight by
some CRBs is sometimes
insufficient to detect the
lack of compliance
Poor communication with sub-tier
suppliers ... not getting specs
7.2.2 Supplier agreed to meet
requirements they couldn't meet
Ambiguous terms and
acronyms, ….leads to
assumptions
Customer gives the wrong revision level of
a drawing or spec to a supplier or doesn't
ensure the supplier is aware of changes to
drawings or specs
Process changes occur in the middle of
the product realization process.
Do a better job of
discussing
requirements on
some major
projects
Customers are not
reviewing all the orders
(especially on repeats)
Purchase Order review by the
customer to ensure the correct
notes are applied to the contract is
not robust
We aren't connecting
the quality customer
with the quality supplier
Contract review
process is not robust
enough, not 2 way
communication
Process spec changes
without supplier input and
confirmation of their ability
to meet the change
Suppliers don't want
to question
customers and risk
losing the work.
7.2.2 Suppliers
accept work they
cannot meet
requirements
Requirements change, with no required a
change incorporation request or date.
Supplier wasn't even notified of the change.
Supplier submits errors in the drawing/
specs, but we don't correct it promptly
Problems with the KUTD system
Supplier Customer &Supplier Customer
6.2.2 Resources
7.2.1 Requirements Definition
7.2.2 PO Review 7.4.2 Flow Down
7.2.2 Contract Review 7.4.2 Change Management
7.2.2 Contract Review
Customer Customer &Supplier Supplier
Custome
r
Supplie
r
C & S
Reqts
Def
Contr.
Rev
Change Mgt
Chapter 2: Requirements & Flowdown
Chapter 2.0 Requirements and Flowdown
2.0 Requirements and Flowdown
2.1 How to clearly identify and communicate
requirements throughout the supply chain
2.2 How to generate a shared understanding of the
requirements
2.3 How to manage revisions to requirements after initial
contract/purchase order release
Chapter 2 - Requirements and Flowdown
• Deliverables by Seville:
– Connect to others doing similar work (Missile Defense Agency,
Space Quality Improvement Council) to see if we can combine
efforts
– Communicate our work to others (AIA, ASQ)
– Collect best practices and white papers from aerospace and other
industries
• Actions to be completed later
– Benchmark Medical Device Industry and SEA on Requirements &
Flowdown
– Publish guidelines/best practices by June 07
Chapter 3 – New Product Introduction
• Background:
The Aerospace Industry developed a successful product
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：航空资料20(64)
