SBS - The Best Value in QMS software

Inclusion of 7.3 design and development (previously excluded)

I

isaiah.w

#1
Is it necessary to include the clause (have been excluded for the past 5-6 years) if our internal IT dept somehow decide to do software development? But usage/deployment is limited to internal customer. The applications developed are requested by other departments to simplify/automate processes. Will not sell the software. I foresee complications if we decided to include the 7.3 clause without actually selling the "product", i.e. determining and reviewing customer requirements, customer satisfaction, etc. Please advise on how to document 7.3 product design and development without actually selling the product.
 
Elsmar Forum Sponsor

somashekar

Staff member
Super Moderator
#2
Is it necessary to include the clause (have been excluded for the past 5-6 years) if our internal IT dept somehow decide to do software development? But usage/deployment is limited to internal customer. The applications developed are requested by other departments to simplify/automate processes. Will not sell the software. I foresee complications if we decided to include the 7.3 clause without actually selling the "product", i.e. determining and reviewing customer requirements, customer satisfaction, etc. Please advise on how to document 7.3 product design and development without actually selling the product.
Internal customer is a fad. There is nothing like internal customer. These are processes which interact and as a part of the interaction towards planning for product realization, which is a part of the clause 7.1., your IT dept is providing necessary support.
Hence you are not involved in the 7.3 activity and therefore no scope for inclusion.
 

John Broomfield

Staff member
Super Moderator
#3
Is it necessary to include the clause (have been excluded for the past 5-6 years) if our internal IT dept somehow decide to do software development? But usage/deployment is limited to internal customer. The applications developed are requested by other departments to simplify/automate processes. Will not sell the software. I foresee complications if we decided to include the 7.3 clause without actually selling the "product", i.e. determining and reviewing customer requirements, customer satisfaction, etc. Please advise on how to document 7.3 product design and development without actually selling the product.
isaiah,

If you want to improve IT's performance when it comes to software design then include clause 7.3 as criteria for their management system. After all, someone said software is 98% design and 2% production!

But do not expect your registrar to audit this because the software is not sold and it will not appear in the scope of your certificate.

It is common for the scope of the management system to be wider than the scope stated on the certificate.

John
 

somashekar

Staff member
Super Moderator
#4
If you want to improve IT's performance when it comes to software design then include clause 7.3 as criteria for their management system.
John.
There is nothing in the OP's post which suggests that the IT dept is not doing the software planning and design to meet the other departments automation and simplification. The steps what the IT dept can take in providing solutions is more apt in the 7.1 c) of the ISO9001.
Inclusion of the 7.3, how is it justified for a product / service realization process.
 

John Broomfield

Staff member
Super Moderator
#5
John.
There is nothing in the OP's post which suggests that the IT dept is not doing the software planning and design to meet the other departments automation and simplification. The steps what the IT dept can take in providing solutions is more apt in the 7.1 c) of the ISO9001.
Inclusion of the 7.3, how is it justified for a product / service realization process.
somashekar,

Yes, they will be planning the realization of their software as well.

But planning is no substitute for design of the software.

John
 

qusys

Trusted Information Resource
#6
Is it necessary to include the clause (have been excluded for the past 5-6 years) if our internal IT dept somehow decide to do software development? But usage/deployment is limited to internal customer. The applications developed are requested by other departments to simplify/automate processes. Will not sell the software. I foresee complications if we decided to include the 7.3 clause without actually selling the "product", i.e. determining and reviewing customer requirements, customer satisfaction, etc. Please advise on how to document 7.3 product design and development without actually selling the product.
What do you sell? What is your "product" or "service" you provide to the customer to make business?
 
Thread starter Similar threads Forum Replies Date
L Clause 0.4 of ISO 9001 and EHS - Where should I stop the inclusion of EHS in my QMS ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 8
S ISO/IEC Guide 51: 1999, Safety Aspects - Guidelines for their inclusion in standards Food Safety - ISO 22000, HACCP (21 CFR 120) 4
V Coverage of Process Failures in dFMEA (Scope/Boundaries for Inclusion) & vice versa Pharmaceuticals (21 CFR Part 210, 21 CFR Part 211 and related Regulations) 1
F Quality Manual Inclusion and Exclusion Justifications ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 1
Z Supplier Scorecard Inclusion of Corrective Actions Supplier Quality Assurance and other Supplier Issues 3
D Sales targets (KPI's) and their inclusion in the QMS ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 14
Q Inclusion of company safety manual and procedures in QMS Document Control Systems, Procedures, Forms and Templates 8
Q MDD inclusion in Quality Policy - MDD Annex 5, 3.2 was referenced ISO 13485:2016 - Medical Device Quality Management Systems 3
S The essential criteria for inclusion in a test method Inspection, Prints (Drawings), Testing, Sampling and Related Topics 5
D PPAP for Electronics - Inclusion of Dimensional Data and Material Specifications APQP and PPAP 2
M Design Control - Management of Electronic CAD files Design and Development of Products and Processes 11
S Examples of FDA acceptable Software Design Specification (SDS) Medical Device and FDA Regulations and Standards News 6
A Design Change/ECO Related Question 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
R Using R package to implement Bayesian phase I/II dose-finding design for three outcomes ISO 13485:2016 - Medical Device Quality Management Systems 6
C ISO 9001:2015 8.3.2. h) Design and Development Planning - What is required? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
Z Software for design control ISO 13485:2016 - Medical Device Quality Management Systems 3
E Design and Development file Procedure ISO 13485:2016 - Medical Device Quality Management Systems 0
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
D Design controls - Inputs, outputs, V&V, DHF, DMR ISO 13485:2016 - Medical Device Quality Management Systems 10
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 6
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
C Documentation for items used for Design Verification 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
P Design verification driven by new equipment. How is this different than process validation? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1

Similar threads

Top Bottom