Software Asset Management at Sandia National Laboratories

1. Software Asset Managementat Sandia National Laboratories NLIT Summit 2009 June 2, 2009 Ramona K. Gallegos Programmer/Analyst Andrew H. Steele Programmer/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. Wait, have I seen this before? • 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

3. 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

4. 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

5. SAMS Development

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

7. ASP.NET Store

8. ASP.NET Store

9. ASP.NET Store

10. Modeling Software, What IS it? Challenges Our Approach Iteration, iteration, iteration End users, people currently managing software Start with the 80% solution • What attributes should be tracked? • What attributes are needed for the store? • Similarities and differences across vendors, types of software.

11. “Selling” Software Challenges Our Approach Both, but start with selling Those most often purchased today Leverage current JIT resellers Hire an administrator Start with the 80% solution • Sell and/or rent? • What products should we sell? • Vendor/reseller agreements • “True up” processes, how does the enterprise pay?

12. Installing Software Challenges 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 • Automated or manual? • How automated? • Similarities and differences across vendors, types of software? • Different for sale vs. rental? • Secondary use rights

13. User Base/Environment, What IS it? Challenges Our Approach Windows for now Target majority of users ASP.NET and progressive enhancement Start with the 80% solution • Windows, Mac, Linux • Digital natives or digital immigrants? • Mobile devices

14. Stakeholders Challenges Our Approach Stakeholders are a moving target Enterprise Tracking and inventory first, then sale Sale first, then installation • Identification of stakeholders • Enterprise solution or subset? • Which pieces to concentrate on first, second, third?

15. Contact Information • Ramona Gallegos, rkgalle@sandia.gov • (505) 284-8866 • Andrew Steele, ahsteel@sandia.gov • (505) 284-4442