Software Asset Managementat Sandia National Laboratories

NLIT Summit 2009

June 2, 2009

Ramona K. GallegosProgrammer/Analyst

Andrew H. SteeleProgrammer/Analyst

Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company,for the United States Department of Energy’s National Nuclear Security Administration

under contract DE-AC04-94AL85000.

2

• If you attended NLIT 2007 you may have seen my presentation about the Software Asset Management System (SAMS) at Sandia

• This year, we’re updating you on the status of SAMS and reporting on some of the challenges we have faced and our approach to handle them

• We’ll also demonstrate the ASP.NET store where Sandia personnel can procure software

Wait, have I seen this before?

Overview if you Missed NLIT 2007

• What is SAMS?– A system designed to treat software as an asset

– It has two high level goals:• Allow for tracking of software licenses in which

Sandia has an interest• Enable reapplication of software licenses across the

enterprise

Overview if you Missed NLIT 2007

• Why Sams?– Budget, accountability, licensing compliance– Inventory is key to management of software assets– Management of software assets requires

• knowledge of annual maintenance or software assurance costs

• knowledge of the number of licenses you own and can apply

• knowledge of how the software assets are in use in the enterprise

• the ability to reapply these assets across the enterprise

4

SAMS Development

Governance/Compliance

Rental

Store

Capture Existing SW Assets

Customer/User Support

Foundation

6

SAMS Current State

• Backend administration and tracking of licenses is up and running, already producing significant cost savings

• First iteration of online store for purchase of software licenses is in pilot phase

• Processes and procedures to support online store are being developed

• Software is being evaluated and packaged for delivery via SMS/SCCM when possible

ASP.NET Store

ASP.NET Store

ASP.NET Store

Modeling Software, What IS it?

Challenges• What attributes should

be tracked?• What attributes are

needed for the store?• Similarities and

differences across vendors, types of software.

Our Approach• Iteration, iteration,

iteration• End users, people

currently managing software

• Start with the 80% solution

“Selling” Software

Challenges• Sell and/or rent?• What products should

we sell?• Vendor/reseller

agreements• “True up” processes,

how does the enterprise pay?

Our Approach• Both, but start with

selling• Those most often

purchased today• Leverage current JIT

resellers• Hire an administrator• Start with the 80%

solution

Installing Software

Challenges• Automated or manual?• How automated?• Similarities and

differences across vendors, types of software?

• Different for sale vs. rental?

• Secondary use rights

Our Approach• Evaluate each vendor,

piece of software• Realize variety of

solutions will be used (fully automated, fully manual, install on client, stream, terminal server)

• Start with the 80% solution

User Base/Environment, What IS it?

Challenges• Windows, Mac, Linux• Digital natives or digital

immigrants?• Mobile devices

Our Approach• Windows for now• Target majority of users• ASP.NET and

progressive enhancement

• Start with the 80% solution

Stakeholders

Challenges• Identification of

stakeholders• Enterprise solution or

subset?• Which pieces to

concentrate on first, second, third?

Our Approach• Stakeholders are a

moving target• Enterprise• Tracking and inventory

first, then sale• Sale first, then

installation

Contact Information

• Ramona Gallegos, rkgalle@sandia.gov– (505) 284-8866

• Andrew Steele, ahsteel@sandia.gov– (505) 284-4442