Implement Software Asset Management
Go beyond tracking licenses to proactively managing software throughout its lifecycle.
Book This Workshop
Poor software asset management practices lead to:
- High cost of software assets and needless procurement
- Licensing, liability, and legal violations
- Compromised security
- Increased management costs and effort
A standardized software asset management program leads to:
- More accurate forecasting and more predictable spend on software
- Improved contract management
- Reduced risk of exposure and noncompliance
- Fewer operational interruptions reduced IT support
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Book NowModule 1: Teams, scope & software procurement
The Purpose
- Assess current state and plan the scope of the SAM program, team, and budget.
Key Benefits Achieved
- Current state assessment
- Defined roles and responsibilities
- SAM budget plan
| Activities: | Outputs: | |
|---|---|---|
| 1.1 | Outline software asset management goals. |
|
| 1.2 | Review SAM maturity and anticipated milestones. |
|
| 1.3 | Define metrics and reporting requirements. |
|
| 1.4 | Define scope and classify software assets. |
|
| 1.5 | Define roles & responsibilities . |
|
Module 2: Software procurement and receiving
The Purpose
- Define processes for software requests, procurement, receiving, and deployment.
Key Benefits Achieved
- Defined standards for software procurement
- Documented processes for software receiving and deployment
| Activities: | Outputs: | |
|---|---|---|
| 2.1 | Identify procurement challenges. |
|
| 2.2 | Define standard and non-standard software requests. |
|
| 2.3 | Build a non-standard Software request form. |
|
| 2.4 | Review and document procurement workflow. |
|
| 2.5 | Design and document workflow for receiving and inventorying equipment. |
|
| 2.6 | Review/create policy for software procurement and receiving. |
|
Module 3: Software maintenance & disposal
The Purpose
- Define processes for software inventory, maintenance, harvest and redeployment, and retirement.
Key Benefits Achieved
- Defined process for conducting software inventory
- Maintenance and patch policy
- Documented workflows for software harvest and redeployment as well as retirement
| Activities: | Outputs: | |
|---|---|---|
| 3.1 | Define policy and process for tracking non-purchased software. |
|
| 3.2 | Design process and policies for software maintenance, warranty, and support documentation handling. |
|
| 3.3 | Define process for software deployment. |
|
| 3.4 | Identify challenges with software harvesting and disposal. |
|
| 3.5 | Design software asset recovery and disposal workflows. |
|
| 3.6 | Build a software disposition policy. |
|
Module 4: Budgets, inventory, roadmap & communications
The Purpose
- Build processes for audits, identify tool requirements, and plan the implementation.
Key Benefits Achieved
- Defined process for internal and external audits
- Tool requirements
- Communication and implementation plan
| Activities: | Outputs: | |
|---|---|---|
| 4.1 | Define requirements for RFP for software solution. |
|
| 4.2 | Define budgeting process and review Info-Tech’s SAM Budgeting Tool . |
|
| 4.3 | Identify data sources and methodology for inventory and data collection. |
|
| 4.4 | Develop a communication plan. |
|
| 4.5 | Develop a SAM implementation plan. |
|
