Design Inputs not Quantitative - ISO 9001 Clause 7.3.2 requirement

J

juliov

#1
Attention quality pros, review and comment on the following question/concern:

I was auditing "Design and development" and while reviewing ISO 9k2k, requirement 7.3.2 (Design and development inputs) at the engineering function, I observed that the inputs were qualitative and not quantitative, in other words the requirements in the document stated inputs such as: market need, build a collator, build a pneumatic application tool, design, etc. I did not see any quantitative specs such as numbers and tolerances, specifications addressing with a number a certaing customer need to be met.

What can you comment about the above. Can companies doing design enter qualitative inputs, or is it up to the customer, " that's how we do things here" about compliance? my idea is that systems must improve, yet, I don't want to over react and p---off the engineering manager because of the lack of quantitative inputs.
Thanks,
 
Elsmar Forum Sponsor

Sidney Vianna

Post Responsibly
Staff member
Admin
#2
Irrespective of what ISO 9001 states and how one interprets the design input requirement, you know your engineering process is dysfunctional.

Reminds me of the famous cartoon:
 
Last edited:
J

juliov

#3
can you expand a bit further on your comment please, it is of interest to me to get objective opinions based on fact and experience about my question.

But, 7.3.2 a, states: functional and performance requirements, (the req does not state that quantitative specs are to be defined) comment?
 
M

Mark R.

#6
I double-checked for my own sanity, but the word "quantitative" isn't in the standard.

Mark
 

Stijloor

Staff member
Super Moderator
#7
Attention quality pros, review and comment on the following question/concern:

I was auditing "Design and development" and while reviewing ISO 9k2k, requirement 7.3.2 (Design and development inputs) at the engineering function, I observed that the inputs were qualitative and not quantitative, in other words the requirements in the document stated inputs such as: market need, build a collator, build a pneumatic application tool, design, etc. I did not see any quantitative specs such as numbers and tolerances, specifications addressing with a number a certaing customer need to be met.

What can you comment about the above. Can companies doing design enter qualitative inputs, or is it up to the customer, " that's how we do things here" about compliance? my idea is that systems must improve, yet, I don't want to over react and p---off the engineering manager because of the lack of quantitative inputs.
Thanks,
Juliov,

Some organizations use the Quality Function Deployment (QFD) process to convert the Voice of the Customer (VOC) which in many cases consist of qualitative data into clearly defined design goals (quantitative data).

When conducting an audit, you should look for this. The purpose of design review is to verify that the design output meets the design input requirements. Even though the ISO 9001:2000 standard does not use this (qualitative-quantitative) terminology, design and development activities are much easier to monitor and track (audit) if the data is available in a more quantitative format.

But whatever type of data is available is what we should use. Auditing is many times not what we like to see, but what the company decides to use. And if it meets the intent and purpose of the D&D process...what can we say?

Stijloor.
 

Helmut Jilling

Auditor / Consultant
#8
Attention quality pros, review and comment on the following question/concern:

I was auditing "Design and development" and while reviewing ISO 9k2k, requirement 7.3.2 (Design and development inputs) at the engineering function, I observed that the inputs were qualitative and not quantitative, in other words the requirements in the document stated inputs such as: market need, build a collator, build a pneumatic application tool, design, etc. I did not see any quantitative specs such as numbers and tolerances, specifications addressing with a number a certaing customer need to be met.

What can you comment about the above. Can companies doing design enter qualitative inputs, or is it up to the customer, " that's how we do things here" about compliance? my idea is that systems must improve, yet, I don't want to over react and p---off the engineering manager because of the lack of quantitative inputs.
Thanks,
I'm with Sidney. While the standard does not require the inputs to specifically be quantitative, and I would be willing to accept beneficial qualitative inputs, the examples you cite are silly...The sound like something they tossed together for ISO audits. Not meaningful, useful and effective inputs.

It could be an NC, at minimum would be an audit trail leading to an OFI or NC. Does not seem like they get it. I would explore their understanding and intention.
 
J

juliov

#9
Randy, I was referring that the inputs to 7.3.2 a, this company use are qualitative. I know that there is no requirement asking for "Quantitative" inputs, however, inputs in a quantitative form could be best for a design that meets customer needs.

Helmut and Stijloor comments above address this topic and it appears that while auditing 7.3.2 any form that best suits the organization should be fine and no NCs could be issued, as long as the company "says what they do, and do what they say"

It appears that some companies also don't know much about D&D, other than design by experience the correct methods are not used. Add hoc?
 
Thread starter Similar threads Forum Replies Date
D Design controls - Inputs, outputs, V&V, DHF, DMR ISO 13485:2016 - Medical Device Quality Management Systems 10
J Design file for pre-existing products - Inputs and Outputs ISO 13485:2016 - Medical Device Quality Management Systems 5
C Design Control - Ways of capturing inputs from manufacturing Other Medical Device Related Standards 5
V Sequence of performing risk assessment: User_FMEA (User Errors) vs Design Inputs FMEA and Control Plans 1
D Are detailed engineering requirements Design Inputs or Design Outputs 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 14
M IATF 16949 - Cl. 8.3.3 - Product design inputs, manufacturing process design inputs IATF 16949 - Automotive Quality Systems Standard 4
L Identification of Inputs vs. Outputs in Design and Development (Section 7.3) ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
M Design Inputs - Final Medical Device Specifications 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
J Design Inputs and Verification Activities CE Marking (Conformité Européene) / CB Scheme 5
S Cost Targets as Design Inputs in your DHF (Design History File) US Food and Drug Administration (FDA) 7
K Interpreting and Applying 7.3.2 Design and Development Inputs ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
Q Design Inputs Document Content Design and Development of Products and Processes 20
Chennaiite DFMEA (Design FMEA) at Vehicle Level - Some inputs needed. FMEA and Control Plans 4
S Design Trace Matrix Ensuring that Design Outputs meet Design Inputs wanted 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
D 7.3.2 Design and Development (trade licenses) Inputs Record - Example wanted Design and Development of Products and Processes 2
N Design and development inputs, how many records are maintained? Design and Development of Products and Processes 2
B Design and Development Audit checklist - What are design inputs and design outputs? Design and Development of Products and Processes 1
M Manufacturing Process Design Documentation - Inputs and Outputs Design and Development of Products and Processes 2
R 7.3.2 Design and Development Inputs clause - What is the record needed? Design and Development of Products and Processes 17
S Manufacturing process design inputs - Productivity, process capability, cost targets Design and Development of Products and Processes 2
DuncanGibbons Section 8.3 relevant for design organisations AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 2
P DFMEA - Machinery Design Best Practices FMEA and Control Plans 0
R Is a FAIR required on parts that we design? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
U API Spec Q1 - 5.6.1.2 C (3) - Design software Oil and Gas Industry Standards and Regulations 3
N Example for design and development planning,input,output,review,verification,validation and transfer Misc. Quality Assurance and Business Systems Related Topics 4
A 8.6 Release of products and services, 8.3 Design and development - evidence required ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 9
C Stress / Challenge Conditions for Design Verification Testing to Reduce Sample Size 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 11
J Significant change related to design and intended use EU Medical Device Regulations 3
S Traceability of requirements to design and risk Design and Development of Products and Processes 3
U NOC - What is considered a "design change" EU Medical Device Regulations 5
Q PPT used as Design Review ISO 13485:2016 - Medical Device Quality Management Systems 3
D Design Verification Sample Size vs Repeats Statistical Analysis Tools, Techniques and SPC 9
A Design and development procedure for API Spec Q2 Oil and Gas Industry Standards and Regulations 6
LostLouie Manufacturer divorced from Design process, is he justified in design process deficiencies? ISO 13485:2016 - Medical Device Quality Management Systems 9
R DFA & DFM - Examples for Design for assembly and design for manufacturability Lean in Manufacturing and Service Industries 2
D Using Laboratory Notebooks in R&D and Design and Development ISO 13485:2016 - Medical Device Quality Management Systems 3
D ISO 13485 - 7.3.6 Design and development verification - Do most folks create a separate SOP? ISO 13485:2016 - Medical Device Quality Management Systems 5
K Joint approval between OEM and Manufacturer on Design Documents ISO 13485:2016 - Medical Device Quality Management Systems 4
M API 4F/7K/8C Design Package Validation Oil and Gas Industry Standards and Regulations 2
A Design History File - Not ready to share the design drawings or Bill of Material US Food and Drug Administration (FDA) 2
W Need for current design or process control FMEA and Control Plans 2
A What is the difference between Design Process, Process Design and Design Control? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
D Test summary report example for design validation wanted - ISO 13485 ISO 13485:2016 - Medical Device Quality Management Systems 1
B Why the Greek god Hephaestus should have done a design FMEA (DFMEA) on his giant robot APQP and PPAP 1
S Documenting Design Verification Test Results (ISO 9001) Design and Development of Products and Processes 1
DuncanGibbons Understanding the applicability of Design of Experiments to the IQ OQ PQ qualification approach Qualification and Validation (including 21 CFR Part 11) 5
S Requirement to Conduct New Shelf-life Testing? (re-do testing for design change) EU Medical Device Regulations 3
A Sample Agreement available for Outsourcing Medical Device Design activity? ISO 13485:2016 - Medical Device Quality Management Systems 1
DuncanGibbons How is the arrangement between Design and Production organisation envisaged? EASA and JAA Aviation Standards and Requirements 4
L Design & Development of a SERVICE Service Industry Specific Topics 13

Similar threads

Top Bottom