Objective Documenting the current state of any solution can be complex and time consuming.  What I have included are the steps to collect this information (manually), I know automated would be great but this should not be executed often.  Why do you need to execute this process?  Lets look at a few questions that has you Bing it (yes, Im from MSFT and we Bing vs. Google it J ) how to review existing SCSM solution

1. SCSM was deployed by technical team because you had the software?
2. Deployed more then what you needed from the solution?
3. User perception of this tool?
4. No project oversight when deployed?
5. No process owners for each layer?
6. You inherited SCSM! Congrats we will not ask what happened to the last owner.

The package will help you walk through the steps of inventorying the solution, look at some performance enhancements needed, Scorecard (leadership love scorecards) and detailed document that you will input your findings and base it on scorecard. This is the key for identifying what is the cause of your dissatisfaction and roadmap to improve.

File Share Link - http://1drv.ms/1LvABYu

Folder Name SCSM - Current State Analysis

• Edited by Jacob Esho [MSFT - ITSM]Microsoft employee 4 hours 14 minutes ago