Specifications as requirements?

OccamMan

Starting to get Involved
#1
My company is building a major subsystem for another company's large medical device - even though we're not directly on the hook to the FDA (our customer is), we want to produce documentation that our customer can successfully use with the FDA. Our subsystem will be sold to this customer and others as an off-the-shelf product once complete.

We're looking to nail down the interfaces between our subsystem and other subsystems, and a question has come up around specifications vs. requirements. An example might illustrate this best:

Let's suppose that our subsystem needs compressed air from the system, specified at 98-102 PSI, delivered through a specific fitting. It seems to me that we should be testing our subsystem to ensure that it functions properly to this specification. And once we lock this down (advertise it to customers), it begins to feel like a requirement rather than just a specification, i.e., since we're publishing a specification that says we work at 98-102 PSI delivered through a specific fitting, it now becomes a requirement that we actually do so, and we should trace through to testing to make sure the requirements have been met.

So... should this specification turn into a requirement? Or should it stay as a specification, presumably with some traceability to testing?

Advice appreciated!
 
Elsmar Forum Sponsor
S

SmallBizDave

#2
The word 'requirement' seems somewhat generic - specifications can be requirements. But there is a difference (however slight) in how we treat 'customer requirements' versus internally generated requirements, all of which can end up as specifications.

In general, one has more flexibility in testing internally generated requirements. In this example it may be the difference between testing only at a worst case pressure (for an internally generated requirement) or testing at low, high and median pressures (for a customer requirement). Interesting question. Other viewpoints welcome.
 
A

adamsjm

#3
Here is a quick 4 page presentation showing the cascade of requirements and the feedback loop of specification based upon QFD and the V-model. This may give you some ideas on how to work with your customers.
 

Attachments

Ronen E

Problem Solver
Staff member
Moderator
#4
My company is building a major subsystem for another company's large medical device - even though we're not directly on the hook to the FDA (our customer is), we want to produce documentation that our customer can successfully use with the FDA. Our subsystem will be sold to this customer and others as an off-the-shelf product once complete.

We're looking to nail down the interfaces between our subsystem and other subsystems, and a question has come up around specifications vs. requirements. An example might illustrate this best:

Let's suppose that our subsystem needs compressed air from the system, specified at 98-102 PSI, delivered through a specific fitting. It seems to me that we should be testing our subsystem to ensure that it functions properly to this specification. And once we lock this down (advertise it to customers), it begins to feel like a requirement rather than just a specification, i.e., since we're publishing a specification that says we work at 98-102 PSI delivered through a specific fitting, it now becomes a requirement that we actually do so, and we should trace through to testing to make sure the requirements have been met.

So... should this specification turn into a requirement? Or should it stay as a specification, presumably with some traceability to testing?

Advice appreciated!
From this description, I couldn't understand what would you be doing differently if you termed it "a requirement" vs. "a specification". I also couldn't quite figure what the FDA has got to do with it.

Sorry,
Ronen.
 

Ajit Basrur

Staff member
Admin
#5
Interesting discussion here ...

There is a Guidance Document "General Principles of Software Validation" that has defined the difference between "Specification" and "Requirement" - http:// www. fda. gov/ downloads/RegulatoryInformation/Guidances/ucm126955.pdf - DEAD LINK - SEE ATTACHED FILE


A requirement can be any need or expectation for a system

A specification is defined as ?a document that states requirements.? (See 21 CFR ?820.3(y).) It may refer to or include drawings, patterns, or other relevant documents and usually indicates the means and the criteria whereby conformity with the requirement can be checked.

.
 

Attachments

Last edited by a moderator:

OccamMan

Starting to get Involved
#6
That's really interesting Ajit, thanks, just what I'm looking for.

So, in the example that I gave above, where our subsystem requires 98-102 PSI compressed air through a specific fitting to function properly, do you think that this now becomes a requirement for the subsystem which is tracked and traced to tests like any external requirement imposed by a customer?
 

OccamMan

Starting to get Involved
#7
Ronen -

That's what I'm trying to figure out - if we have a specification that comes from an engineering need (e.g., requires 100 W at 120VAC), should that then be treated the same as a requirement imposed by a customer need (e.g., the device shall target the tumor with an accuracy of X).

The medical bit was added as there may be some regulatory implication to how this is handles, and there does seem to be such an implication based on Ajit's response.
 
M

MIREGMGR

#8
My view:

Requirements are real, and technically determined and defined.

Specifications are what somebody says they are. Assuming the somebody is competent and honest, the specification doesn't go outside the bounds of the corresponding requirement. There are various reasons, though, why a specification might differ from the corresponding requirement in the opposite direction, i.e. "inwardly" from the bounds of the corresponding requirement.
 

Ronen E

Problem Solver
Staff member
Moderator
#9
Ronen -

That's what I'm trying to figure out - if we have a specification that comes from an engineering need (e.g., requires 100 W at 120VAC), should that then be treated the same as a requirement imposed by a customer need (e.g., the device shall target the tumor with an accuracy of X).

The medical bit was added as there may be some regulatory implication to how this is handles, and there does seem to be such an implication based on Ajit's response.
So, according to this post, what you're actually asking is how to treat requirements from different sources. IMO, as far as compliance with the requirements is concerned, it doesn't matter what the source is, once the requirement has been accepted / recognized by your org as binding (be it customer, regulatory, technical or other). Criticality and nature of the requirement matter more, especially in the context of verifying / validating compliance.

WRT the FDA -- given that you're acting as a component supplier, only few regulatory requirements apply directly to you (though many more may be transposed to you via contractual obligations towards your customer(s)). Before applying any FDA guidance, it's important to understand the scope of its application.

Cheers,
Ronen.
 
Thread starter Similar threads Forum Replies Date
C Taking exception to customer requirements or specifications & AS9100D AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 6
D Raw Material chemical/Tensile Requirements Specifications (QQ-A-250/4, etc) AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 3
alonFAI SMT machine specifications and performance meet the requirements for our production Manufacturing and Related Processes 2
O Functional Specifications - Tracability to requirements? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
A Are Software Requirements Specifications part of Design Input? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
K How do ISO 9001 Requirements apply to 2 sets of specifications to 2 separate vendors? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 3
S TS 16949 Requirements for Timely Review of Engineering Specifications IATF 16949 - Automotive Quality Systems Standard 6
A Tool Capability vs. Customers Requirements and Specifications (Ethics) Quality Assurance and Compliance Software Tools and Solutions 6
T Product Realization Confusion - Manufacturer Specifications Aspects and Requirements ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 1
Q Quality Standard, Requirements & Specifications Various Other Specifications, Standards, and related Requirements 2
D Traceability Matrix format for tracing user needs - Requirements, specifications, etc Food Safety - ISO 22000, HACCP (21 CFR 120) 11
F Control Of Documents Questions - Customer Specifications / Requirements IATF 16949 - Automotive Quality Systems Standard 1
S Marketing Requirements vs Product Specifications ISO 13485:2016 - Medical Device Quality Management Systems 14
M How to handle changed Customer Specifications or Requirements IATF 16949 - Automotive Quality Systems Standard 4
R EU-MDR Article 9-common specifications Other ISO and International Standards and European Regulations 2
A Oven Controller Specifications - BAC5621 and AMS2750F AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 2
V Customer Print Specifications on PFMEA FMEA and Control Plans 13
R BS EN 12060:1998 - Zinc and zinc alloys Method of sampling Specifications Manufacturing and Related Processes 4
M MDR "Common Specifications" (CS) - If not standards, then what? EU Medical Device Regulations 5
G Engineering Specifications - APQP APQP and PPAP 5
M Measuring Capability of Process with Multiple Specifications Capability, Accuracy and Stability - Processes, Machines, etc. 6
DuncanGibbons OEM specifications such as AIPS spec from Airbus AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 3
E Packaging Specifications Mercedes-Benz U.S. International IATF 16949 - Automotive Quality Systems Standard 4
P Software requirement and design specifications - Medical device contains both hardware and software IEC 62304 - Medical Device Software Life Cycle Processes 2
M Informational EU – Draft Functional specifications for the European Database on Medical Devices (Eudamed) – First release (High(1)) to be audited Medical Device and FDA Regulations and Standards News 0
M Specifications Aerospace - Who is responsible for providing the correct specification(s) AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 14
2 ASTM or ISO Specifications on Prints Other US Medical Device Regulations 2
R Control of COTS (Commercial Off The Shelf) Specifications ISO 13485:2016 - Medical Device Quality Management Systems 2
I Procedures from recognized standards or specifications ISO 17025 related Discussions 3
S Test Specifications based on Vehicle Type Various Other Specifications, Standards, and related Requirements 0
P Help with 8.5.1 regarding Welding Procedure Specifications (WPS's) ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 10
A Technical Documentation - Manufacturing Specifications EU Medical Device Regulations 4
Z How to Contractually Agree on Specifications for Raw Material Purchases Supplier Quality Assurance and other Supplier Issues 15
J Change in Lot Release Specifications - Definition of "Substantial Change" EU Medical Device Regulations 14
T ISO 13485 Label Specifications and Artwork Control ISO 13485:2016 - Medical Device Quality Management Systems 3
N Subscription Service to Raw Material Specifications AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 6
W Japanese Steel Specifications - A material called HNCM220M Manufacturing and Related Processes 1
A Procedure for Labeling Review and Approval and Specifications Matrix US Food and Drug Administration (FDA) 2
M Design Inputs - Final Medical Device Specifications 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
Q How to handle customer request for changing specifications 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
H Resistance Temperature Detectors (RTD) Manufacturer's Specifications General Measurement Device and Calibration Topics 3
K Thermocouples Hot Junction and Number of Uses Specifications AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
K What is included in Raw Material and Component Specifications for Medical Devices? Other Medical Device Related Standards 3
T How to keep Customer Engineering Specifications & CSRs Up to Date IATF 16949 - Automotive Quality Systems Standard 6
N Control of Documents Scope - Product Specifications ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 3
W Who in your company writes your policies, procedures, specifications etc. Document Control Systems, Procedures, Forms and Templates 10
M Thread Ring Gauge Specifications General Measurement Device and Calibration Topics 3
U Looking for Bolt Thread Specifications for Delrin & Aluminum Inspection, Prints (Drawings), Testing, Sampling and Related Topics 3
Q Standards or Specifications required for Garbage Truck Compressors Various Other Specifications, Standards, and related Requirements 1
V Where to get MS501 Chrysler Specifications APQP and PPAP 3

Similar threads

Top Bottom