- Channel HP
- :
- Enterprise Business Blogs
- :
- Services
- :
- ITILigent Service Management
- Mark all as New
- Mark all as Read
- Float this item to the top
- Bookmark
- Subscribe to RSS Feed
- Invite a Friend
How to architect a Service Management System? The Implementation View...
Architecting an ITIL based Service Management System for a medium to large enterprise organization requires more than a single picture to be produced. There are typically many stakeholders to take into account and multiple views are required to understand added value, positioning, content and implementation aspects.
This is the last of four blog posts that will each describe a different architectural view on realizing a Service Management System. The last view is called: The Implementation View.
How to architect a Service Management System? The Technical View...
Architecting an ITIL based Service Management System for a medium to large enterprise organization requires more than a single picture to be produced. There are typically many stakeholders to take into account and multiple views are required to understand added value, positioning, content and implementation aspects.
This is the third of four blog posts that will each describe a different architectural view on realizing a Service Management System. The third view is called: The Technical View.
How to architect a Service Management System? The Functional View...
Architecting an ITIL based Service Management System for a medium to large enterprise organization requires more than a single picture to be produced. There are typically many stakeholders to take into account and multiple views are required to understand added value, positioning, content and implementation aspects.
This is the second of four blog posts that will each describe a different architectural view on realizing a Service Management System. The second view is called: The Functional View.
How to architect a Service Management System? The Business View...
Architecting an ITIL based Service Management System for a medium to large enterprise organization requires more than a single picture to be produced. There are typically many stakeholders to take into account and multiple views are required to understand added value, positioning, content and implementation aspects.
This is the first of four blog posts that will each describe a different architectural view on realizing a Service Management System. The first view that we will take a look at is called: The Business View.
Why you need a Configuration Management System
My last blog post on the ITIL V3 Configuration Management System (CMS) is from 12-Dec-2007, while lots of people keep asking me questions about the components of a CMS and how that is different from and/or builds upon the concept of a CMDB.
And when I return the question "why do you need a Configuration Management System?", the answers vary from "because it is an ITIL best practice"
all the way to "because I want to bring together data about all Configuration Items and their relationships"
Are these the right arguments? I don't think so. And here is why...





