Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
thanks Alessandra - much appreciated. :)
Let us consider two main barriers to implement the standard: a technical barrier and an organizational barrier.
Technical barriers are less frequent and derive from what is needed to close gaps in terms of compliance obligations and significant environmental aspects. Typical issues are lack of technical expertise, high capital costs, and sunk costs associated with the current operations.
Organizational barriers are more frequent and include things like lack of top management leadership and commitment, lack of communication, and people attitude.
You can find more information below:
The article mentioned lists the mandatory documents and records. To proceed I recommend starting with clause 6 of ISO 14001:2015.
From there you can determine where should be your organization’s priorities in order to improve its relationship with the environment. These are the foundations on which an EMS is structured and implemented
Please check this information below about implementation:
If acceptance is in a contract, you will need to store the contract with the customer acceptance (even electronically).One example can be contracted with mobile phone operators, you can buy a sim card in the shop and sign a contract, purchase one online and consent with electronic means (the website will store the client clicking on the checkbox of consent on Privacy notice) or even orally when you make a new contract with the call center operator. They ask you to say that you agree with data processing under their privacy notice, they register the conversation and store it on their servers linked to the number of clients.
Here you can find more information on consent.
If you need to understand how to process consent under GDPR, you can consider enrolling in our free online training EU GDPR Foundations Course: https://advisera.com/training/eu-gdpr-foundations-course//
1) We are OEM company, so one product will be sell to few customers. a) the market region might be differ according to customers. So how should I put into the design input as it also covers the markets region. Example, the product is design to customer A for US market. After few years customer B would like to purchase the same product but for Australia market. Should we just revised the design input or need to remark into design changes? Need your comment.
Since this is a change in the input data the best way would be to put market change as a design change. Any change to an existing approved document is considered a change to the document. In Design and development process there are two types of changes: changes in design and changes in the process. A design change is an alteration of the device's design basis. The incentive for design change is often field or other quality problems. Process changes change process management methods, but are not intended to change design; however, a design change can force changes in the process. Your market change is a design change.
For more information, see:
2. Can you elaborate further for IS0 13485 clause 7.3.3 Design Inputs which stated " Requirement shall be complete, unambigous, able to be verified or validated, and not conflict to each other" ? How can we verify these ?
The main point here is to check are your design inputs written well enough. The key is to avoid being overly broad. Think narrowly instead. When you defined your inputs, think in advance are those inputs can be verified or validated, are there any tests that can prove those input data. So, for some input data there will be possible to verify, but some not. For example, the market data that you mentioned in the previous question can not be verified or validated. But, if as input data you defined some physical characteristics, then definitively you can have some tests with which you will prove it.
1. as we made the Risk Assessment initially, a couple of months ago, we've had some servers in one of the locations, which had high Risk levels. Now, we've moved them to the cloud, and don't have those risks anymore. Should we now perform the Risk Assessment again?
ISO 27001 requires a risk assessment to be performed at planned intervals, or when significant changes are proposed or occur, and normally servers change can be characterized as a significant change, so you must perform risk assessment again.
But please note that moving servers to the cloud may not mean that all related risks are eliminated. Some of them may have been only transferred. For example, if your servers are in a service provider´s cloud, the physical related risks are now with the provider (e.g., physical servers hosting your virtual server can fail), and to handle this risk you must ensure the existence of proper security clauses in the contract or service agreement with the provider.
For further information, see:
2. If yes, should the previous version be saved as well?
ISO 27001 requires results of risk assessment to be kept, so the previous version of risk assessment must be kept.
This article will provide you a further explanation about record management:
These materials will also help you regarding record management:
Thank you very much for clarifying my doubts about the updates to the iso 27001 standard. Kind regards.
No, just based on ISO 9001:2015 the mandatory documents and records do not include clause 6.2.2. Please check this article - List of mandatory documents required by ISO 9001:2015 - https://advisera.com/9001academy/knowledgebase/list-of-mandatory-documents-required-by-iso-90012015/ .
However, as an auditor you can ask:
The following material will provide you more information:
It depends on the data involved in your activity. If your start-up deals with health data (maybe developing a tracking health app for mobile)? Does it monitor consumer’s behavior for marketing purposes? Is it processing children’s data because develops videogames? In all these cases time to achieve GDPR compliance can be longer than if your start-up processes only personal data of staff, clients, and providers for example because it works on AI solutions with anonymized data or it is an animation studio.It can take from 3 to 6 months to reach GDPR compliance, but it depends on budget, time, and resources (intended as staff) available. In case the data processing involves a large scale of sensitive data or a transfer of data outside the EU, it may take more time because of the Data Protection Impact Assessment and safeguards for the transfer of data need to be considered and implemented.
Our Toolkit helps controller to implement GDPR requirements with the assistance of our expert team.
EU GDPR Documentation Toolkit https://advisera.com/eugdpracademy/eu-gdpr-documentation-toolkit/
Here you can find more information for starting to be compliant with GDPR
If you need to understand how to comply with GDPR, you can consider enrolling in our free online training EU GDPR Foundations Course: https://advisera.com/training/eu-gdpr-foundations-course//
Maintaining a quality system is a day-to-day business. Every quality system has some kind of records that are proof of some work done. For example, if you need to procure something (raw materials, equipment) you have a purchase order, communication with the supplier. Then, when those goods arrive at your company you have an invoice, a receipt at the warehouse, a check to see if the goods that arrived are in line with what was ordered and the like. All of this is evidence that some work has been done, but so are the elements of the quality system.
If there are (non-conformities) omissions related to daily work, it is necessary to record such omissions and resolve them. Therefore, there are records of non-compliance, on the basis of which it is necessary to initiate corrective or preventive actions. This is also a day-to-day business.
As far as audits are concerned, an internal audit usually takes place once a year. When that will depend on your business. This can be at the end of one year, or at the beginning of another year, before submitting the final accounts and the like, whichever suits you. Management review is also conducted mostly once a year and is most often after an internal audit is conducted.
So the maintenance of the quality system takes place throughout the year.
The following articles can be helpful: