Yes, as long as those documents are documented information that support the operation of processes you will need to register them. ISO 9001:2015 in clause 7.5 requires an organization to “Maintain documented information to the extent necessary to support the operation of processes and retain documented information to the extent necessary to have confident that the processes are being carried out as planned.”
Basically you will need to document, no matter what format you decide to use, the following:
- Documenting critical portions of the quality management system (QMS) such as its scope, key operational processes, policies, and objectives.
Documenting important, but less critical information that supports the QMS such as process flowcharts, specific quality and operational procedures, schedules, information collection approaches (i.e. forms, surveys), business plans, etc.
I was wondering how up to date it is and the sources of the information? We were considering purchasing a legal register, but I am not convinced that we need to.
Answer:
Unfortunately, this list is not fully up-to-date because it depends on voluntary contributions from our readers - therefore, it is likely that not all regulations are listed. To make sure you have the latest list of laws and regulations, it would be best to hire a local legal adviser.
Risk assessment
1. Would you please help to guide me how to start to do risk management (from Risk Identified --Risk Treatment Plan)?
This toolkit enables you to implement information security and business continuity risk management compliant with ISO 27001 and ISO 22301, and provides access to video tutorials to help fill in the documents with real data examples.
3. Is it possible to treat or prevent to be zero risk appetite?
Answer: It is not possible to treat risks to achieve zero risk appetite, because the cost to treat all possible risks an organization is exposed to would be prohibitive.
4. If I follow standard COBIT 5 for risk management, I don’t need to do SOA right?
Answer: Your understanding is correct. The Statement of Applicability is not a requirement for COBIT 5, so you do not need to develop such document if you follow COBIT 5 risk management approach.
Template content
Control 6.1.1 Information security roles and responsibilities is covered by all templates in the toolkit. For each required action on a template always it is required the definition of who must perform it (the field [job title]).
Please be aware that ISO 27001 does not require you to document each and every control you declare as applicable, you can simply describe the implementation of such undocumented controls in the Statement of Applicability. In order to avoid overhead for small companies, we have decided to include in the toolkit only those documents that are mandatory + those that are most commonly used; in other words, you will not find in the toolkit the documents that are not mandatory and that are not used very often.
The EU GDPR defines personal data as “any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person”. As long as the car is registered to an individual, the license plate would make that person indefinable so it would fall under the definition above.
Is this correct? Is this how they can be completed and meet the requirements for ISO 23001.
Answer:
ISO 22301 does not prescribe how Business Impact Analysis must be performed, only that you have to perform this task, so your approach to define recovering activities for a department as a whole rather than by each different activity will also meet the requirements for ISO 23001.
I received following question:
Answer:
Specific of Virtual Service Desk is that personnel is geographically dispersed and that they can be organized in various ways. That also provides options for measuring e.g. telecommunication costs, dropped calls, number of resolved incidents (or other calls) per group (if they are located e.g. on same location), availability of agents (e.g. if they work from home or office that is not supervised), etc.
Of course, all usual measurements related to the Service Desk apply also. This articles can give you idea:
ITIL Service Desk types https://advisera.com/20000academy/blog/2014/05/06/itil-service-desk-types/
Service Desk: Single point of contact https://advisera.com/20000academy/knowledgebase/service-desk-single-point-contact/
Design in AS9100 Rev D
Answer:
This is one example that I have used where a company that supplies products also has a service that they provide to customers. Even if you do not design the product, you certainly design the service of creating a drawing. If this is a new service that you are offering it would need to be designed as per the AS9100 Rev D requirements for design and development. As for your question on customer approval, this is a decision that is part of your customer requirements, not the AS9100 standard. If your customer states that they need approval over any documents you create to manufacture their parts then you would certainly need approval over the drawing.
For more information on how the design and development requirements apply in AS9100 see this article, “Can companies still exclude design and development from their AS9100 Rev D QMS?“; https://advisera.com/9100academy/blog/2017/10/09/can-companies-still-exclude-design-and-development-from-their-as9100-rev-d-qms/
ISO 9001 and root cause analysis
Answer:
An organization performs quality control on its products (clause 8.6). During quality control, an organization can detect product nonconformity (clause 8.7).
Also, an organization performs monitoring and measurement (clause 9.1.1) and analysis and evaluation of performance (clause 9.1.3)
Either because one particular product non-conformity is considered very serious, or because it is a recurring product non-conformity, an organization can decide that performance should be improved. For that reason, a corrective action should be developed (clause 10.2). Developing an effective corrective action must include determining the root cause of the product quality issue.
Let us suppose that the organization is not satisfied with the level of non-conformities on product X. So, the first step is to focus the effort of improvement, by performing a symptom diagnosis using, for example, a Pareto chart: https://www.screencast. com/t/cw2cpildI
After this initial screening the organization needs:
· to determine probable causes;
· make some tests or investigations to find root-cause(s);
· develop alternative solutions;
· select the best one;
· implement the solution;
· check the effectiveness of that solution
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.
If you decline, your information won't be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.