Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
I'm assuming you are auditing considering ISO 27001.
Considering that, first you need to consult the Statement of Applicability, to identify which controls are related to license and patch management (e.g., A.11.2.7 Secure disposal or reuse of equipment, A.12.5.1 Installation of software on operational systems, and A.12.6.1 Management of technical vulnerabilities), and how these controls are implemented.
Based on that you can build a checklist with documents and records you need to look for.
This article will provide you a further explanation about developing an internal audit checklist:
These materials will also help you regarding internal audit:
ISO 9001:2015 is not about departments, but about processes. So, determine which processes cross each department. When auditing a department you will audit the requirements around the processes that cross that department.
For example, purchasing department may be about purchasing (clause 8.4), about quality control at reception and nonconformities (clauses 8.6 and 8.7), about identification and traceability (clause 8.5.2), about production planning (clause 8.5.1), about preservation (clause 8.5.4), about warehouse conditions (clause 7.1.4). If you check, I identified the clauses by following the process since identifying a need for purchasing until receiving and storing in the warehouse.
About the annual audit plan, you should consider auditing all processes and ISO 9001:2015 clauses in two or more internal audits along a year.
The following material will provide you information about internal auditors:
You can consider it an indirect environmental aspect that the organization can influence, but not control. Then, while evaluating that aspect you can decide if your organization should do anything about it, or if there are other priorities.
You can find more information below:
Determine the scope of the quality management system (QMS), your organization may decide to include only certain lines of business.
Setup a project sponsor, a project manager and a project team. Ensure top management support, get training about the standard. Designing and implementing a quality management system implies being knowledgeable about ISO 9001:2015.
As a first step perform a Gap analysis, to determine the amount of work to be done - comparing what your organization already has in place versus ISO 9001:2015 requirements. From that GAP Analysis you can develop your Project Plan, listing what needs to be done, by whom, until when.
Then, an important step is to design a model of how your organization work as a set of interrelated processes. For example:
Decide how to describe and monitor those processes.
From there it is implementation in order to close the gaps found. Then, perform an internal audit and the management review. There you can decide if your organization is ready for a certification audit.
This is a very short description of the journey but below you can find more detailed information:
You can find more information below:
Unfortunately, there is no straightforward way to review the company's QMS documentation according to IATF 16949: 2016 standard.
Important issues for major QMS documentation are given below.
The IATF 16949: 2016 standard does not expect 3rd party PPAP certification. In addition, there is no expectation of 3rd party PPAP certification. However, internal auditors and person who is preparing PPAP documentation may need PPAP training.Since the competence of the person giving the training is important.
The instructor of PPAP training can be a 3rd party IATF 16949: 2016 and/or VDA 6.3 auditor, etc. Or the instructor's CV should be competent and sufficient in the PPAP subject.
They are different. Environmental impacts are about the changes to the environment resulting from an organization’s environmental impacts:

Risks are about the effect of uncertainty. Most of time there is no uncertainty about impacts, they are happening and predictable.
The impact is about the consequences for the environment, while the risk is about processes, products or services.

Some risks become higher when they are associated with an abnormal or emergency situation.
You can find more information below:
In order to be in compliance with the ISO 9001:2015 standard, a company only need to have Document Control in place for documents and records relevant for the quality management system.
You can find more information about documentation below:
According to ISO 9001:2015 risks must be:
About determination I would provide a set of examples about risks and opportunities in processes, products, services and from the context, and I would train people to determine risks and opportunities.
About evaluation I would develop a simple matrix to reduce subjectivity in evaluating risk and opportunity relevance, and I would train people to evaluate risks and opportunities.
About acting, I would ask people to help develop actions to minimize probability of occurrence and/or minimize consequences of occurrence. I would also ask people how to monitor the implementation and effectiveness of those actions.
Show examples and invite them to be part of the approach.
You can find more information below about risks.
Requirement 7.5.6 consider the validation of processes for production and service provision. Section 4.1.6 considers software validation. In small companies, always is a question of how to implement this requirement. You have to understand that you need to validate only software that can have an impact on the or quality of your management system or on the safety of the medical device. This means that you do not need to validate word processor or spreadsheet software. But if you have software for managing your warehouse and delivery process, that you need to be sure that in the case of a software update, your warehouse quantity of goods, lot numbers, invoice numbers, and delivery notes have not changed.
If you have any software in the production, software that runs the machine, that software also needs to be validated.
However, these validations are not software type validations. With this validation, you need to prove that the software updates did not disrupt your database.
For example, for the number of the invoices and delivery notes, the easiest way is to check the is numbering in the expected sequence, for warehouse, does the quantity on the shelves corresponds to the number defined in the program.
You can see how the record for software validation looks like in our ISO 13485:2016 Documentation toolkit here: