Skip to main content

ISO 20K Certification Process

Thinking about ISO/IEC 20000 certification? Here are the steps involved.

1. Questionnaire:
The service provider contacts one or several Registered Certification Bodies (RCBs). Each RCB will send a questionnaire with information needed to submit a quotation. Based on the quotations, the provider can select a RCB.

2. Application for assessment:
An application form is completed and returned to the chosen RCB. A lead auditor is assigned and an initial visit scheduled. The auditor will explain the assessment process, an audit program will be agreed and the assessment date selected.

3. Optional pre-audit:
This is a high-level evaluation to determine where the company stands in compliance with ISO/IEC 20000. The auditor will point out any areas of concern to give the provider an opportunity to improve before the initial audit.

4. Initial audit:
In this session the scoping statement is agreed upon and the auditor plans the certification audit. Documentation and evidence of compliance are reviewed. Non conformance items are added to the Corrective Action Plan (CAP).

5. Certification audit:
The assessment to the standard is now being executed. The RCB will look for records, proof, that the management system is in line with the ISO 20000 specification. On completion of the audit the RCB will present the findings in a written report. Non conformances will feed into the CAP. Following a successful certification audit and the decision by the RCB to grant registration; a certificate of registration is awarded. The client is now permitted to use the certification body certification mark and the relevant ISO 20000 certification mark.

6. Surveillance audits:
A schedule of surveillance audits are undertaken over a three year period to ensure that the management system is working properly. The actual frequency will depend on the RCB.

7. Re-certification audit:
This is carried out every three years. All controls are evaluated to ensure that the QMS is operating properly and if it is, certification is renewed for another three years. Any non-conformity will be added to the CAP, where it will be addressed. The three year surveillance audit process starts all over again.

Comments

Excellent Information, Thanks very much

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…