Queries about Element no 5.5.1 and 7.5.2 - Designation of "Authority"

A

arin_23

#1
I am working as the Manger business Excellence for an organization which is dealing with the E commerce business and having various cross functional activities like E sourcing, Forward and reverse action, Customer Care and other related activities.

My query is regarding element no. 5.5.1 of ISO 9001:2000 Quality Management System. The standards mentions in very brief "Top management shall ensure that responsibilities and authorities are defined and communicated within
the organization"

My question is whether the "Authority" has to be designated to all the functional people as per organization chart of the organization or Responsibility and Authorities can be mentioned against each activity designated in a process line, which shows the involvement of respective departments.

Whether addressing of clause no 7.5.2 is required for the software design and development process or it is taken care of by clause no 7.3.6????
 
Elsmar Forum Sponsor
A

arin_23

#2
Re: Queries about Element no 5.5.1 and 7.5.2

Hi buddies!!!

waiting for your valued response in this regard.

Cheers:cool:

Arindam
 

Helmut Jilling

Auditor / Consultant
#3
Re: Queries about Element no 5.5.1 and 7.5.2

I am working as the Manger business Excellence for an organization which is dealing with the E commerce business and having various cross functional activities like E sourcing, Forward and reverse action, Customer Care and other related activities.

My query is regarding element no. 5.5.1 of ISO 9001:2000 Quality Management System. The standards mentions in very brief "Top management shall ensure that responsibilities and authorities are defined and communicated within
the organization"

My question is whether the "Authority" has to be designated to all the functional people as per organization chart of the organization or Responsibility and Authorities can be mentioned against each activity designated in a process line, which shows the involvement of respective departments.

Whether addressing of clause no 7.5.2 is required for the software design and development process or it is taken care of by clause no 7.3.6????
In my opinion, responsibilities and authority should be defined throughout your system, where appropriate. The organization chart plays a part, but does not describe much detail. So, usually this is discussed in procedures. If you address things in 7.3.6 or 7.5.2 is up to you. In the process approach, it is not linked to a particular clause.

For your industry, it would seem likely that the design people would be the operational people. If they are the same people, you can address it under either clause.
 

Randy

Super Moderator
#4
Responsibilities are basically those tasks that one is required to perform and will be held accountable for.....and authorities are the actions and decisions one is allowed to take to fulfill responsibilities.
 

atitheya

Quite Involved in Discussions
#5
My question is whether the "Authority" has to be designated to all the functional people as per organization chart of the organization or Responsibility and Authorities can be mentioned against each activity designated in a process line, which shows the involvement of respective departments.
I advise to define responsibilities for every (responsible:lol:) person and then accordingly define authority (by determining as necessary) of these persons to carry out the responsibilities alloted to them.

Whether addressing of clause no 7.5.2 is required for the software design and development process or it is taken care of by clause no 7.3.6????
The entire clause 7.3 (7.3.1 to 7.3.7) will be applicable to the process and then you do not need to address 7.5.2 for the activities addressed in 7.3
 
A

arin_23

#6
Re: Queries about Element no 5.5.1 and 7.5.2

In my opinion, responsibilities and authority should be defined throughout your system, where appropriate. The organization chart plays a part, but does not describe much detail. So, usually this is discussed in procedures. If you address things in 7.3.6 or 7.5.2 is up to you. In the process approach, it is not linked to a particular clause.

For your industry, it would seem likely that the design people would be the operational people. If they are the same people, you can address it under either clause.
Hi buddy hjilling!!!!

I also thought in the same line.....actually, my design people are not involved in operation, they just develop the software application based on the requirements of the other business units.

I fully agree with you that the validation can be addressed in either clause, but there is only one ambiguity....if I want to include validation in 7.3.6 then straightway exclusion for 7.5.2 can be taken; but on the other hand if I want to address it in clause 7.5.2, can I claim exclusion for 7.3.6????? By doing this ami I not breaking the continuity of the design and development life cycle????

Cheers

Arindam
 
A

arin_23

#7
I advise to define responsibilities for every (responsible:lol:) person and then accordingly define authority (by determining as necessary) of these persons to carry out the responsibilities alloted to them.



The entire clause 7.3 (7.3.1 to 7.3.7) will be applicable to the process and then you do not need to address 7.5.2 for the activities addressed in 7.3
Hi buddy Parag!!!!

Thanx.......Can you throw some light on the authorities of the programmers who simply write the codes for any application????? His / Her responsibility is to do the coding of a particular module within a given time period.....He/she does not even have the final decision on the codes he/she is writing. The final authority lies with the team leader, as he is accountable for the debelopment of the project as a whole.

Cheers

Arindam
 
A

arin_23

#8
Responsibilities are basically those tasks that one is required to perform and will be held accountable for.....and authorities are the actions and decisions one is allowed to take to fulfill responsibilities.
Hi buddy Randy!!!!

That is quite obvious that "Responsibility" without "Authority" does not have any significance......my hitch is that whether authorities of all the responsibilities mentioned in an organization chart should be documented or not!!!! If yes then whether will it be done designationwise or process wise.

To my understanding, if I try to map the authorities process wise, then it is always better...because you need not bug your head for each and every authority along with the designated responsibilities for that particualr process, but the authority of the process owner can always be mentioned.

Cheers

Arindam
 

Jim Wynne

Staff member
Admin
#9
That is quite obvious that "Responsibility" without "Authority" does not have any significance......
Obvious to you, perhaps, but there are many instance where responsibilities are assigned without the necessary authority also being explicitly assigned.

my hitch is that whether authorities of all the responsibilities mentioned in an organization chart should be documented or not!!!! If yes then whether will it be done designationwise or process wise.
You can avoid all of the trouble by just stating in your documentation that "authority" is to be assumed when "responsibility" is mentioned.
 

Helmut Jilling

Auditor / Consultant
#10
Re: Queries about Element no 5.5.1 and 7.5.2

Hi buddy hjilling!!!!

I also thought in the same line.....actually, my design people are not involved in operation, they just develop the software application based on the requirements of the other business units.

I fully agree with you that the validation can be addressed in either clause, but there is only one ambiguity....if I want to include validation in 7.3.6 then straightway exclusion for 7.5.2 can be taken; but on the other hand if I want to address it in clause 7.5.2, can I claim exclusion for 7.3.6????? By doing this ami I not breaking the continuity of the design and development life cycle????

Cheers

Arindam

OK. There are specific requirements that personnel designing things must have the particular skills needed. In your case, I assume that is writing program code, and designing the structure and flow of the software. These design skills must be defined and verified. The better fit for this is 7.3.6.

There is also a manufacturing skill requirement, where the product quality cannot be verified by inspection, then more specific controls must be defined. In your case, it seems the hard part is already done in software design, in 7.3.6. Any further details in 7.5 can cross reference to this. 7.3.6 is the better fit for you.
 
Thread starter Similar threads Forum Replies Date
H Queries: RFD & Pre-RFD Program Medical Device and FDA Regulations and Standards News 0
M Multiple Standard Interpretation Queries Occupational Health & Safety Management Standards 4
S Queries of new version ISO 9001 2015 ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 11
B Six ISO 13485 Queries Other ISO and International Standards and European Regulations 6
P General queries on TS 16949 Registration - Software Services IATF 16949 - Automotive Quality Systems Standard 9
H Attribute Data Gage R&R - Queries of data from a system Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 19
L "Document Controlling" Queries run to obtain information reported to customer Document Control Systems, Procedures, Forms and Templates 7
A Where can I get information to answer queries realted to OHSAS 18001? Occupational Health & Safety Management Standards 1
N QUERIES On ISO 17025 AUDIT - Measurement Uncertainty Budget, etc. ISO 17025 related Discussions 1
N UNcertainty Queries !!!PLease reply ! Measurement Uncertainty (MU) 5
N Infant radiant warmer - Heater Quartz Element type Other Medical Device Related Standards 0
S Cost of Poor Quality (CoPQ) - Scrap element of calculation includes lost margin? Misc. Quality Assurance and Business Systems Related Topics 7
A IEC 60601-1 cl.15.4.2.1 - Tubular Heating Element (Protection against Overheating) IEC 60601 - Medical Electrical Equipment Safety Standards Series 5
S How does each element of OHSAS contribute to management of work place safety & health Occupational Health & Safety Management Standards 7
S Should there be a SME (Subject Matter Expert) for each element? Training - Internal, External, Online and Distance Learning 3
F ISO/TS 16949 - Definition Clause, sub clause, section, element IATF 16949 - Automotive Quality Systems Standard 8
somashekar Design as a Purchased Element in QMS ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 21
I Component Evaluation - Relevant Element of the Standard? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 1
Q How to Audit ISO 14001 Element 4.5.2: Evaluation of Compliances ISO 14001:2015 Specific Discussions 4
I IEC 62304:2006 Definitions - Software System, a Software Element and Software Unit IEC 62304 - Medical Device Software Life Cycle Processes 13
D Found Watch - Watch is "Element" and says "New York" Coffee Break and Water Cooler Discussions 16
A What is the difference between an ISO Section vs. ISO Element? ISO 13485:2016 - Medical Device Quality Management Systems 10
I Does a QMS defined by the element-by-element approach meet the intent of 4.1a? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 15
P Corporate Social Responsibility as an essential element to sustain a business Other ISO and International Standards and European Regulations 19
G "Prevent Pollution" element of Policy Statement Miscellaneous Environmental Standards and EMS Related Discussions 6
J Print asking for Straightness of 0.013 and it has a note "Any Radial Element" Inspection, Prints (Drawings), Testing, Sampling and Related Topics 8
A "Element of" in ISO 14001:2004 (3.6 - environmental aspect)? ISO 14001:2015 Specific Discussions 4
W Internal Auditing - Processs Audit vs. Element Audit - ISO 9001 Process Audits and Layered Process Audits 6
K How do I audit the Design Element of ISO 9001 including Verification and Validation? General Auditing Discussions 3
C Laboratory Testing as a "Special Process" - element 7.5.2 ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
J Reference Element for a Coordinate Measuring Machine General Measurement Device and Calibration Topics 3
B Audit by Element vs. Audit by Process Process Audits and Layered Process Audits 12
B Purchasing Element Audit Checklist to audit against ISO 9001 Document Control Systems, Procedures, Forms and Templates 6
Jen Kirley New Element Found! Governmentium (Gv) Funny Stuff - Jokes and Humour 1
D Newest element discovered: "Governmentium" Funny Stuff - Jokes and Humour 4
L Link to an example of a full 19 element PPAP example - Seeking APQP and PPAP 5
D ISO/TS Element Responsibility Matrix IATF 16949 - Automotive Quality Systems Standard 4
J Finite Element Analysis (FEA) - Preventive Action? Preventive Action and Continuous Improvement 18
C How to exclusion element 6.2.2.1, 7.5.1.8 of TS2 requirements? IATF 16949 - Automotive Quality Systems Standard 7
R Process Audit vs. Element Audit - The auditor focused on 13 different processes. Process Audits and Layered Process Audits 5
J Servicing element - Servicing of the automobile or the production of service parts QS-9000 - American Automotive Manufacturers Standard 3
J Do I have to write a procedure for every element in QS-9000? QS-9000 - American Automotive Manufacturers Standard 13
T Element 4.5 - Hand written correction to a controlled component drawing? QS-9000 - American Automotive Manufacturers Standard 1
Q What element from QS that is no longer in TS? IATF 16949 - Automotive Quality Systems Standard 1
J QS-9000 Element 4.10.5 QS-9000 - American Automotive Manufacturers Standard 3
J QS 9000 Element 4.15 ( 4.15.6.4 Shipment Notification System) QS-9000 - American Automotive Manufacturers Standard 2
J TL 9000 - Element 4.9 Significant Change TL 9000 Telecommunications Standard and QuEST 6
M Element 7.5.5 - Preservation of Product - We ship the product FOB Point of Origin ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
C Element 4.9.1 Process Monitoring QS-9000 - American Automotive Manufacturers Standard 3
D Element 4.7 Customer supplied product QS-9000 - American Automotive Manufacturers Standard 3

Similar threads

Top Bottom