Software Asset Management (SAM)

Transcription

1 Software Asset Management (SAM) Sarah Lawrence Software Asset Auditor, Software & IBM TSS SOFTWARE

2 What is Software Asset Management Audit Readiness License Position SAM Process/ Policies Cost Savings Compliance Optimisation

3 High Level SAM Plan Inventory SAM Optimisation Organisation Policies & Procedures

4 High Level SAM Plan Inventory Organisation SAM Optimisation Policies & Procedures

5 High Level SAM Plan Organisation SAM Optimisation Policies & Procedures Inventory What do you have already? Where is it allocated? Is it still in regular use? Discovery tools or manual?

6 High Level SAM Plan Inventory SAM Optimisation Policies & Procedures Organisation Inventory all licenses and proof of purchase Record and organise license evidence Do they match the versions you re using now?

7 High Level SAM Plan Inventory Organisation Policies & Procedures Establish the software lifecycle in order to manage it effectively Acquisition, retirement, storage, disaster recovery all need a process Create a SAM culture throughout your organisation SAM Optimisation

8 High Level SAM Plan Inventory Organisation SAM Optimisation Maintain your SAM plan using the following: Spot checks Inventory reports Quarterly audits Working with other departments Policies & Procedures

9 Audits by Industry Sector 100% 67% 40% Finance Retail IT

10 Complexities of SAM Emerging Technologies Cloud Infrastructure changes, virtualisation SAM Tools, Vendor specific requirements Tracking Software usage Audit Readiness Deployment and Cloning Governance and IT processes License metrics constantly changing Huge variety of Vendors

11 Ensuring Audit Readiness Around 40-60% of midsize and large businesses can expect an external audit Audits tie up valuable company resources Would you know how to negotiate? Are you prepared to deal with aggressive third party auditors? Vendors will keep coming

12 PVU Licensing - Full Capacity vs Sub Capacity VM: IBM Product 1 VM: IBM Product 1 4 cores available 2 cores utilised 4 cores available 4 cores utilised Host 1 License Requirement = 4 Cores Sub Cap: 400 PVU required Host 2 License Requirement = 8 Cores Sub Cap: 800 PVU required

13 IBM Sub-Capacity - What's the catch? 90 IBM License Metric Tool (ILMT) Install updates promptly Collect deployment data for each EP Reports prepared at least once per quarter Exception = Servers licensed to full-capacity

14 i-series: Manual Audit Reports Server Name Type Model Part number Processor Technology Activated Cores PVU Count - Full Cap Partition Details PVU Count - Sub Cap

15 APSU SAM Managed Service Identify SW deployed vs SW entitlement Identify changes in hardware, VMs and PVU counts Deploy Bigfix, ILMT and Bigfix Inventory APSU SAM Reduce costs or enable cost avoidance where possible Managed Service Produce quarterly reports on IBM sub capacity products Review SAM processes and product lifecycle Recommend actions for risk management Consult on usage terms, license suits and renewals

16 SAM Tools

17 ILMT 3 Must be deployed within 3 months of sub cap products being installed Agents sit on each VM and feed into BigFix Monitors all servers on an estate regardless of OS Allocates a PVU (processor value unit) to each server PVU count determines number of licenses required If not installing ILMT, full capacity licensing must be used Costly alternative unless the physical cores are being fully utilised

18 Big Fix Inventory 3 Agents sit on each VM and feed into BigFix Gives usage reports Uses software catalogue to produce reports on over 10,000 products No need for long-winded or technical set up Can log all contracts alongside licensing Useful when: Harvesting unused licenses Identifying leavers Reducing purchase costs of new licenses