Probably one of the most important changes, the GDPR will enjoy extended applicability affecting entities not established in the EU. Of course, some conditions must be met for the extraterritoriality to be applicable. The EU GDPR will apply to the processing of personal data of EU data subjects, regardless of whether the processing activities take place in the EU or not. The EU GDPR is also applicable to entities established outside the EU if they offer goods or services to individuals in the Union, or if they monitor the behavior of individuals in the Union (i.e., profiling activities, tracking individuals’ activities on the internet, etc.).
The key to understanding when EU GDPR is applicable is understanding the meaning of “in the Union.” The EU GDPR will only apply to personal data regarding individuals within the Union, while the nationality or habitual residence of those individuals is irrelevant. For example, a company based in the EU which is processing the data of Japanese individuals located in Japan will still need to comply with the EU GDPR. Conseque ntly, the Japanese individuals will be benefiting from all rights according to the EU GDPR, even if these rights do not exist in their own nation’s laws.
When the data of EU citizens is processed outside of the EU by companies which are also outside the EU, then this is not considered to be “in the Union”. For example, the EU GDPR will not be applicable for a school which is based in the United States just because there is a possibility that one or several of its students would be EU citizens. In this case, the processing does not take place “in the Union,” nor is the individual “in the Union”.
You must approach a scope extension as if it was a new implementation project (the steps are basically the same). The difference is that as a scope extension you have to assess how this inclusion will affect your current scope. For example, how you will handle access of the personnel of the new part of the scope to the current one? Access levels will be the same or will have to be updated? Since this new scope will include paper assets, how this will affect you information classification policy?
Although largely known as ISO 27001, to refer to the Standard only as ISO 27001 is inaccurate.
The full official name of this standard is ISO/IEC 27001:2013, because this standard was developed by a joint technical committee (ISO/IEC JTC 1) formed by these two organizations.
The participation of IEC in the development of this standard helps ensure that its content is aligned with standards developed by IEC without participation of ISO personnel, such as IEC 62351 Power System Control and Associated Communications – Data and Communication Security.
Additionally, not using the official name can lead people not used to ISO documents to the misinterpretation that there are more than one 27001 standard, which is not true.
Examples of positive issues
yacht rental praslin
Using a designated hold location for defective product
Answer
Please check ISO 9001:2015 clause 8.7 b). Segregation is one of the possible ways of dealing with a defective product. Sometimes physical segregation to a designated hold area is not possible, for example, the defective product is very big or there is not enough space for a hold location. So, segregation in a designated hold location is not mandatory. What is mandatory is to avoid the unintended use of defective products. For example, sometimes a red label is the way used to warn about product status.
Lo primero que debe de hacer es contar con el apoyo de la dirección de la organización, que será clave durante la implementación de ISO 9001:2015, también para proporcionar los recursos necesarios.
Después lo que puede hacer es un análisis GAP o de brecha, que le va a ayudar a identificar aquellos requisitos que ya cumple y los que le debe aún cumplir. Aquí puede llevar a cabo el análisis de forma gratuita: https://advisera.com/9001academy/iso-9001-gap-analysis-tool/
Luego ya podría empezar con la implementación de la norma: la definición de la política de calidad, los objetivos de calidad y planes para llevarlos a cabo, el contexto de la organización y sus partes interesadas, el alcance del SGC, etc...hasta llegar a la auditoría interna y la revisión por la dirección, que sería el paso previo para certificarse. En este enlace puede descargarse un checklist para la implementación de la norma - Porject checklist for ISO 9001:2015: https://info.advisera.com/9001academy/free-download/project-checklist-for-iso-9001-2015-implementation
I would keep that revision table at the end of the document but would add some kind of revision number, or date, or color to warn users that something in the page was changed. In a QMS we want to avoid the unintended use of obsolete documents. Perhaps these documents could bring more information to the topic "Common mistakes with ISO 13485:2016 documentation control and how to avoid them" https://advisera.com/13485academy/blog/2018/03/14/common-mistakes-with-iso-134852016-documentation-control-and-how-to-avoid-them/
Quality assurance vs quality control
Answer
Quality control is about checking if product or service specifications are being met. You can have a Quality Control Plan that states what to control, when and where, how, by whom, with what specifications and methods. Quality assurance is about the set of processes in place to provide confidence that quality requirements will be met.
This type of ISO standard is out of our field of expertise, but what we can tell you is that ISO standards related to content identification and description are under responsibility of ISO working group ISO TC 46 SC 9 and the current available standards can be found at this link: https://www.iso.org/committee/48836/x/catalogue/p/1/u/0/w/0/d/0
We hope that one or some of these standards can fulfill your needs.