Few questions...

Question 1: For those that pull your server data in from CMDB - what install statuses do you show?  Is there a particular install status that you filter out before extracting the data (aside from retired)? 

Question 2: We have a status for 'In Maintenance', for example.  I know we've paid for the servers and they are still in service, but the month we get the data and it shows that status, it's not 'in service' at that point, which can create fallout.  I'm wondering if I should filter those out in order to send the cost to the servers in service at that time. 

Question 3: What about 'Pending Decommission'?  Another status we have that comes through sometimes.  I guess for those, they're still up and running, while the process is completing in the background, though...

Thoughts?  Thank you!

99+% of our servers are in one of the following states:  Live, Build, Inactive, or Retiring.  Everything else is a mixture of real states (Reserved, Retired, Pending Refresh, Available) and several make believe states (read Dirty Data).  We drop Servers in Build, Reserved, Retired, and the illogical ones and flow the rest though allocations.

We don't have a maintenance status but my first instinct would be to keep them out of allocations until they move back into service.  I guess that would depend on what percentage of the fleet they make up.  

Our equivalent of your Pending Decommission is Retiring and we do keep them in until they are really gone.  

Thank you, George!  Super helpful!!

We include statuses "Deployed" and "Being Assembled" but we also track any depreciation for servers outside of those statuses and allocate the costs across the active state servers.  Goal is to make sure server costs are flowing up to applications.