Service Transition

ST p200 SCM or CMS?

ST p200 Heading "SCM and Service Knowledge Management System". Is "SCM" referring to Capacity, or is it a typo which should be "CMS" configuration mgmt system which would make sense?

The purpose of SACM

ST 4.3.1 p65
"The purpose of SACM is to: ..."

I must eb thick because I've read those four purposes over and over, and they sound like they are all the same one to me. I guess it is "purpose" singular but why the four bullets? Especially the last three would seem to be entirely redundant

automated change ?

automated change gets no mention, yet in this era of Web Services, grid computing and so on, ITIL needs to be ready for dynamically self-healing and self-reconfiguring systems. the only human intervention will be after-the-fact approval so someone knows what happened.

ST Figure 4.20 typo "assume" means "assure"

ST Figure 4.20 typo "assume deployment of service package or release" means "assure..."

[from ]

ST does not specify services in definition of CMS technical requirements

Page 195, section 7.3 Technical COnsiderations for CMS:

Nowhere does this part of the book specify or remind us that a service or other logical entity is a CI and therefore has to be stored and mapped in order to support catalogue, incident impact, root cause, chage impact, SLA analysis and reporting or any of the other essential activiites of ITIL.

instead the descriptions are entirely technical which is going to allow the vendors to pass off network mapping tools and asset discoverers as CMS.

Event generating a change ?

In Service Operation, page 38, figure 4.1 mentions an event can generate a change. Same is explained again in where an event triggers a change. But there is no mention of a change triggered by an event in Service Transition.

paragraph 2.4.3 should be the value of the volume to the business

chapter 2 in each book should describe it from a volume perspective: Therefor paragraph 2.4.3 should be the value of the volume to the business... (see service design). In SO it is a generic value to the business. In SS it does not have the value to the business described. Better alignment between these values would be beneficial.

All books 2.2.1 repeats service definition

pure pedantry:

Chapter 2 is in all books (though with very subtle editorial differences).

2.2.1 the text at the start in a box defining a service is almost identical with the following paragraph - should have been edited?

SO regards KEDB as distinct from CMS, ST does not

SO p66 "the KEDB, like the CMS, forms part of a larger... SKMS" Clearly distinct.

ST p 68 "The CMS maintains... any related ... known errors". included.

NB there appears to be no mention of KEDB in ST?

Figure 4.8 in Service Transition and Figure 4.6 in Service Operation

Figure 4.8 in Service Transition and Figure 4.6 in Service Operation are both exactly the same, but one is a representation of a CMS, the other a representation of a SKMS if you read the subtitles.

Syndicate content