Cost justification for moving to CM2012

Anyone done a cost justification for moving from ConfigMgr 2007 to ConfigMgr 2012?

Rod,
 
We haven't done a hard cost because we already own it.  In general, we're justifying the soft costs of our upgrade by describing how it helps improve effectiveness (get more done) and efficiency (using less resources).  There are a lot of major improvement areas that show resource and dollar savings for us:

- Endpoint Protection:  We'll save hard dollars versus paying for yet another solution on both our desktops and servers.  There are soft savings on not having to support the separate AV infrastructure.
 
- Software Updates:  We've got a team that manually handles our current testing, pilot, and production deployments.  In CM12, we'll have these rules set to automatically create the deployments and that team of people will just get SRSS reports automatically emailed to them.
 
- User Centric Management:  The new application deployment model, the improvements in User Device Affinity, and the application catalog greatly reduce the time for users to get what they need, and reduce/eliminate the work of our helpdesk and desktop techs in numerous scenarios.
 
- Simplified Infrastructure:  Besides political reasons, there is almost no legitimate reason for multiple sites if you have < 100,000 devices.  This greatly reduces the number of servers needed to provide the infrastructure.

- RBAC:  Role based administration is for real now.  It is easy to make it so people have access to everything they need... and nothing more.   Let the areas that do a particular thing well do it everywhere without having to make them administrators.
 
 
I hope that helps!
 
 
Nash  

Really good points!
 
I'm also looking for overall cost justification from a hardware standpoint, too.  I know there will be some hardware costs for many orgs, particularly those that need 64bit servers.

I have to figure hardware will be relatively as easy or hard to manage as just managing the life cycle of your machines.  If you just bought new servers last year or this year, you had to know the world was going x64 and would almost have had to go out of your way to get something not x64 compatible.  My old CM07 servers are 3-4 years old and are all x64.  Bought for CM07, they should be up for replacement anyway.  Should management decide not to replace them, they're still x64 ready and would work for CM12.  Then it's a matter of shuffling around.
 
I do suppose that in most cases, folks will require at least one new primary site if nothing else.  It would be just so hard to quantify the labor saved on savings in processes from CM12.  It's late.  I'm blabbling.  Look forward to what others have to say here.