Design Inputs not Quantitative - ISO 9001 Clause 7.3.2 requirement

Helmut Jilling

Auditor / Consultant
#11
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?
Wait a minute, if you read my post #8, I did not say any form is OK, and no NC's could be issued! I said the ones mentioned sound like they are not effective, and were just thrown together. It is an audit trail, and would likely lead to an NC or at least an OFI. But, I would have to audit further before I could decide that.

"say what they do, and do what they say" was overrated and simplistic 10 years ago, and is completely outdated today. Systems must be effective, not just compliant with some procedure. Many of the NCs I write are because a process was not effective, not just basic compliance.
 
Elsmar Forum Sponsor

Caster

An Early Cover
Trusted Information Resource
#13
qualitative and not quantitative,
I think this is red herring.

Try some Dr. Phil on it "How's that working out for ya?"

If they are making tons of money, gaining market share, customers are happy, designs launch on time, with few errors, and have few warranty problems...then "Just walk away Renee"

<Classic song by The Left Banke 1966 - I was 7 building tree houses - where were you?>

But if there are problems, Dr. Phil says "you might want to try something different!"

As was suggested, this response would definitely cause me to dig. It just doesn't sit right.
 

Stijloor

Staff member
Super Moderator
#14
If they are making tons of money, gaining market share, customers are happy, designs launch on time, with few errors, and have few warranty problems...then "Just walk away Renee"

<Classic song by The Left Banke 1966 - I was 7 building tree houses - where were you?>
.
:topic:

Caster,

Sorry, I could not resist.....

The Four Tops did it too, but I like this version better.



Stijloor.
 

Helmut Jilling

Auditor / Consultant
#15
Hello Helmut,

What do you mean by "willing to accept beneficial qualitative inputs", thanks
I would accept a client defining whatever design inputs they wish, qualitative, or quantitative. I think either could be acceptable if they are meaningful. The ones cited by the OP as examples however, sounded silly, not meaningful.
 

Big Jim

Super Moderator
#16
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,
There is not enough presented here to make a good evaluation, but it sounds like you are trying to bend the standard to your concepts. There is no requirement for "quantitative" anywhere is 7.3.

Design activities can vary widely from one company or industry to another. Some design activity will by nature be quantitative and others will not.

As in many things in the standard, the true test is effectiveness. In design, effectiveness is evaluated during review, verification, and validation.

There can be a difference between what an auditor would like to see or even expect to see, and what the standard requires. Auditors should always apply the test of "what does the standard say" while auditing and running across something that doesn't seem right.
 
J

juliov

#17
All in all what still doesn't sit right with my opinion is the fact that
7.3.2 a: says "functional and performance requirements"
what do we understand then by functional and performance reqs? about a couple of examples. There seems to be a wide interpretation and very subjective interpretation of the req among us in quality. Any examples out there? thanks,
 

Coury Ferguson

Moderator here to help
Staff member
Super Moderator
#18
All in all what still doesn't sit right with my opinion is the fact that
7.3.2 a: says "functional and performance requirements"
what do we understand then by functional and performance reqs? about a couple of examples. There seems to be a wide interpretation and very subjective interpretation of the req among us in quality. Any examples out there? thanks,
The bottom line is that the standard allows the company to define what the requirements are.

If the company chooses to define it "quantitative or qualitative" for design input then where would they be wrong?

I really don't think, in my opinion, that there would be any NC's issued, unless the procedures lack the requirements. I would probably identify it as an OFI.
 

charanjit singh

Involved In Discussions
#19
I am not quite aware of what the product was when the auditor asked for quantitative design input. If it is some manufactured product there would most likely be some quantitative aspect to the specification that form the customer requirement (design input) e.g. dimensions, weight, volume, speed, intensity of light, sound/noise, finish etc. The point is to see whether the reply or the evidence provided appears credible irrespective of whether the standards specifically mention quantitative or qualitative inputs. We need to look at the intent of the standard.

I know of cases, both as a consultant and as an auditor, where the companies do not want to give the details of design input (also about design verification/validation) in the belief that they would be giving away some design secrets. In this case it is a question of allaying their apprehensions that is needed, yet one can even indirectly confirm that the company does take into account the important design input requirements.

I feel what is required is a proper judgment on the part of the auditor to ask questions that may uncover what design inputs would be involved for a given requirement.

Good luck!
 

Stijloor

Staff member
Super Moderator
#20
All in all what still doesn't sit right with my opinion is the fact that
7.3.2 a: says "functional and performance requirements"
what do we understand then by functional and performance reqs? about a couple of examples. There seems to be a wide interpretation and very subjective interpretation of the req among us in quality. Any examples out there? thanks,
Hello Juliov,

Simple example:

Functional: A detailed description of what the product is supposed to do. Its intended functions.
Performance: A detailed description of how long it is supposed to last. Its duration/longevity.

Stijloor.
 
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