Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
If they decide to go for ISO 9001 certification only clauses from section 8 can be candidates for classification as non-applicable. ISO 9001:2015 is a generic standard applicable to all kinds of organizations. The company:
Inside 8.5 typical candidates for non-applicability are:
It seems that all clauses are applicable.
While considering the use of ISO 9001 for software development activities, consider this support ISO/IEC/IEEE 90003:2018 - Software engineering — Guidelines for the application of ISO 9001:2015 to computer software - https://www.iso.org/standard/74348.html
For more information about exclusion, the right ISO wording is applicability, consider the following:
Our course will cover these documents, and these documents are part of our toolkit. Our courses and documentation toolkit are designed to cover all the requirements of the standard. But for any other questions, we are at your disposal.
Please note that the supplier information security requirements are based on the results of risk assessment and applicable legal requirements, which are exclusive for each organization because they are related to their context and risk appetite.
For example, two organizations may have the same cloud provider, but because they have different risk appetites, a requirement for the less risk+tolerant organization may not be used by the more risk +olerant one.
Included in your toolkit there is a list of commonly adopted security clauses for suppliers and partners that can help you define your supplier information security requirements. This template is on folder 08 Annex A Security Controls >> A.15 Supplier Relationships
This article will provide you a further explanation about security clauses for suppliers:
Requirement 6.1.3 “c” refers to a comparison between controls to be applied with those in Annex A, to ensure that no necessary controls have been omitted.
Requirement 6.1.3 “d” refers to the development of the Statement of Applicability (SoA), informing the necessary controls and justification for inclusions, whether they are implemented or not, and the justification for exclusions of controls from Annex A.
The full text of these requirements can be found in the ISO 27001 standard (https://www.iso.org/standard/54534.html).
Due to Intellectual Property rights, the standard is not included in the toolkit, but you can find some explanation about the requirements in this paper:
You can use it because ISO 13485 standard covers all necessary elements regarding the production; it guides you on how to best organize production, how to ensure that you know at all times what stage your product is at, how to ensure traceability (both raw-repro material and finished product) and the required purity. Regardless of the fact that ISO 13485 covers medical devices, this approach is acceptable for the production of any product.
However, please be aware that ISO 13485:2016 is standard for preparing quality management systems explicitly for manufacturers of medical devices. In section 3. Terms and definitions, in point 3.11 is described what a medical device is. A product may be a medical device if it has one or more of the following roles: diagnosis, prevention, monitoring, treatment, or alleviation of disease. Therefore, if your materials meet this definition (and the rest of what is written in point 3.11) then the materials for ISO 13485 are applicable.
If you need more information what is ISO 13485:2016, please see following articles:
Besides the requirements you mentioned, the document control process also needs to consider appropriate:
This article will provide you a further explanation about document control:
This material will also help you regarding document control:
“I want to understand the frame / process that is followed in creating an ISO management documentation - are you able to provide a structure.”
In this article, you see the most common frame used to describe a quality management system (QMS) documentation - How to structure quality management system documentation - https://advisera.com/9001academy/knowledgebase/how-to-structure-quality-management-system-documentation/
It starts with the quality policy, the most high-level document in a QMS, continues with a quality manual, no longer mandatory with ISO 9001:2015, but still considered useful by most organizations to present a general description of the management system. For example, I recommend designing the quality manual based on the process mapping exercise of clause 4.4.1 b). Then come the procedures where we can describe what is done in the QMS, by whom, and when. When it is needed a more detailed description about how to do something in the QMS we use work instructions. At the base, we have forms that, once filled in, become records. We have also other records not generated by filling a form. For example, an e-mail sent by a customer with a complaint becomes a record.
Procedures and work instructions are not mandatory. Please check clause 4.4.2. Each organization can consider a list of topics when thinking about what procedures are needed or not. Consider that procedure may be useful or needed because of:
“Also, I liked that a SWOT analysis is carried out. Is a SWOT always carried out?"
Carrying out a SWOT analysis is not mandatory. So, organizations may not use it. In this free webinar-on-demand, I show how the SWOT analysis can be used - ISO 9001:2015 clause 4 - Context of the organization, interested parties, and scope - https://advisera.com/9001academy/webinar/iso-90012015-clause-4-context-of-the-organization-interested-parties-and-scope-free-webinar/
You can find more information about context, documents, and records below:
Please note that the mentioned threats (Earthquake / Fire / Flood / Storm) can cause injuries on employees (making them unable to work), or preventing them from reaching the workplace, and if there is no replacement person to perform activities the business will be negatively impacted.
This article will provide you a further explanation about matching assets, threats, and vulnerabilities:
This material will also help you regarding matching assets, threats, and vulnerabilities:
Sometimes to ensure product or service conformity organizations must control and prevent situations that lead to deterioration, loss, theft, end of validity, tampering, and so on.
For example, raw materials while at a warehouse may be deteriorated due to high or low temperatures, or the level of humidity may be lost due to animal contamination or mixing with other substances. During manufacturing, dust or other types of contamination may generate product nonconformities. The finished product may be lost because temperature and humidity are not controlled, or handling is not well suited (remember the warning phrase “Fragile” in packaging). Finished products may also be lost due to bad practices at the warehouse, new batches are shipped before old batches until validity time is run-up.
For example, at a restaurant consider temperature and contamination control to avoid food deterioration. An IT service provider considers measures to preserve the server’s performance. A university considers what should be done to ensure that exams are not disclosed.
So, in your organization’s case look for situations like these and think about what should be done to prevent them.
You can find more information below:
ISO 27001 does not require an explicit identification/link between external/internal issues, interested parties, risks, and opportunities, so this issue is not a certification requirement.
The standard only requires that external/internal issues, interested parties are determined.
These articles will provide you a further explanation about internal/external issues and interested parties: