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.

"Support for CIs of varying complexity, e.g. entire systems, releases, single hardware items, software modules"

"Automatic identification of other affected CIs when any CI is the subject of an incident...or RFC"

"the ability to show the hierarchy of relationships between 'parent' CIs and 'child' CIs"

Experience with ITIL V2 shows that having failed to make the mapping of services an explicit requirement the vendors will interpret this otherwise.

Syndicate content