ISO/IEC 20000 Checklist and/or Implementation Road Map

Z

ZeroDev

Does anyone have the check list for ISO 20000, implementation road map or any guides to implement ISO 20000
 

Marc

Fully vaccinated are you?
Leader
One last "Bump". My Thanks in advance to anyone who can help with this one!

Marc
 

john.b

Involved In Discussions
I have two versions of requirements checklists I made up for a 20000 gap analysis.

Note these were for the earlier version of the standard (2005), and they updated it since (2011). As far as I know one main change was a service catalogue is now required, and it wasn't then, so these wouldn't be accurate related to that (it wouldn't appear as a required reference document). Other 20000 2011 standard version changes should be reviewed.

To make these I only read through the standards and listed out requirements ("shalls"). It's not as easy as it sounds to just list them because some are a little vague (really!) and some list different requirements grouped together.

I also took 20000 implementation and auditing training classes, which don't hurt, but those are always a little disappointing because a few close reads of the standard cover most of the class content.


It seems obvious what these are and how to use them, but some notes anyway:


-one is set up to review 20k coverage by document type, the other by process area. they are the same, just two arrangements.

-field color coding would be useful for gap assessment (cited)

-individual fields cross-reference company documents and departments that relate to this. Obviously this is the part you need to fill in, and surely some coverage already exists. If almost none does then don't implement ISO 20000.

-they are set up to cross-reference 9001 and 27001 standards requirements. Maybe you would revise these to remove one or both, or add something else.

-a specific required "procedure," "record," or "role" is very clear; a required "process" is not. Obviously you need all the main processes implemented but other specific requirements say you "shall" have some specific sub-process in place. Maybe a procedure document covers this, maybe a "process" document makes sense to you; it's up to you to set it up as you like.

-roles: only a few are really required by specific clause references (and maybe those changed), but functionally roles for all processes would be needed for an actual ITSMS.


Let me know if I can answer any other questions.
 

Attachments

  • ISO 20000 Requirements by process (blank template).xlsx
    23.5 KB · Views: 1,330
  • ISO 20000 Requirements by type (blank template).xlsx
    20.7 KB · Views: 1,128
O

OnieXander

This is a really great information! Appreciate your sharing!:cool:
 
Top Bottom