Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
What do you mean by start-up? Let us consider two hypotheses:
So, for situation B it is too early to certify. For situation A, I think it is easier to get ISO certification than with an established company (with same resources and motivation). An established company has to unlearn some practices and that it is not always easy.
For situation B certification makes sense only after starting to scale.
You can find more information below:
Clause 8.1 does not require a procedure. It specifies the need to establish a management system and document it to the extent necessary so that the laboratory can achieve the requirements of ISO 17025. This means it is more applicable to apply clause 8.1 to a policy statement. e.g. State as a policy “The laboratory is committed to establishing, documenting and maintaining a management system to meet the general, structural, resource, process and management requirements of ISO 17025”. This is typically documented in the Quality Manual, not as a procedure. If the laboratory does not have a system already established in accordance with ISO 9001, then state that the Option A applies, where the clause 8 management requirements are addressed as part of ISO 17025. If the laboratory does have a system already established in accordance with ISO 9001, then state that the Option B applies, where the clause 8 management requirements are addressed as part of ISO 9001, including laboratory activities. This means that, for example how complaints and corrective action are handled, fall under the ISO 9001 activities and evidence can be shown of laboratory activities being included.You can link this clause 8.1 to your overall project planning to implement ISO 17025:2017.
Have a look at the ISO 17025 toolkit document templates for some more insight:
The following articles may be of interest :
Let us consider three situations:
a) Company does not perform design activities
b) Company performs design activities, but they are performed outside the scope of the quality management system
c) Company performs design activities, and they are performed within the scope of the quality management system and the company decides to exclude design from the certification process
Situations a) and b) are allowed, but the organization has to explain why design was excluded. These are common, pacific situations.
Situation c) is not allowed. If design is performed within the management system scope it must be included. Not including design is a major non-conformity.
The following material will provide you more information about exclusions:
I think that a quality department should develop three areas of expertise:
For quality control you can start with the risk-based thinking and developing a quality control plan from scratch: what to control, where, with what frequency, how, by whom, where to record, whit what specifications.
For quality improvement you start with the facts collected with quality control and customer satisfaction using tools to find trends, find priorities to improve your system.
Root cause analysis is fundamental for quality improvement and can be one of the bases for developing knowledge about how to design quality into products and services from the beginning.
The following material will provide you more information:
Please note that business continuity objectives depend on the organizational context and the organization's own business objectives and strategies, so it is unfeasible to provide specific inputs.
Generally speaking, you can have at least two types of objectives:
These articles will provide you a further explanation about BC objectives and organizational context (although the last article is about ISO 27001, the same concept applies to ISO 22301):
This material will also help you:
Please note that ISO 27001 does not approach specifics about processes and technologies. It only defines requirements for information security management and information security objectives to be achieved.
Considering that "License management" involves the control and documentation of the software products your business uses, and where and how they are used, you should consider at least auditing these controls:
This article will provide you a further explanation about developing an audit checklist:
These materials will also help you regarding performing an audit:
Considering ISO 27001 and ISO 22301, which have a lot of requirements in common, it is perfectly possible to integrate some documents. In fact, this can bring many benefits, like decreased costs in implementation, maintenance, and internal audits.
This article will provide you a further explanation about integrated implementation:
This material will provide further information:
This material will provide information about overlaps:
Transition is primarily about meeting the changed and new requirements. As a laboratory the transition means you need to identifying any gaps in your policies, objectives, processes, procedures and records, to meet ISO 17025:2017 scope of requirements (see clause 8.1.1 and 8.2). Revising and or establishing the necessary documents is part of the process, however there is no prescribed way to number your documents.
Many laboratories that used the ISO 17025:2005 clause numbering have realigned the numbering with the new clauses. Others have not. What is important is link everything to the management system (clause 8.2.4), remove obsolete documents from use and make sure personnel have clear access to all the information necessary to comply with the new version.
Decide what will work best for your laboratory, practically, considering opportunities and risks of different ways you could go about the changes to your documentation.
The following may assist you:
Broadly speaking, you must focus to keep the documents up to date and to make sure everyone complies with all the documents.
This approach ensures that all elements of your ISMS will be ready for the surveillance visit, regardless of the surveillance audit scope.
This article will provide you a further explanation about surveillance audit:
No, exclusion 7.3.7 Design and development validation is not possible since it is a strict requirement from the standard. They have to have documented validation plans and all other arrangments. However, this can be outsourced to some other company or laboratory, but then this should be explained as such.