Manage IT assets through their life cycle to make sure that their use delivers value at optimal cost, they remain operational (fit for purpose), they are accounted for and physically protected, and those assets that are critical to support service capability are reliable and available. Manage software licences to ensure that the optimal number are acquired, retained and deployed in relation to required business usage, and the software installed is in compliance with licence agreements.


Process Purpose Statement Account for all IT assets and optimize the value provided by these assets.




  • Updates to asset inventory
  • Configuration repository
  • <?>


  • Asset register
  • Results of physical inventory checks
  • Results of fit-for-purpose reviews
  • Communication of planned maintenance downtime
  • Maintenance agreements
  • Approved asset procurement requests
  • Asset register revisions
  • Authorized asset retirements
  • Results of cost optimization reviews
  • Opportunities to reduce asset costs or increase value
  • Register of software licences
  • Results of installed licence audits
  • Action plan to adjust licence numbers and allocations
  • <?>



Task Instructions:

Identify and Record Current Assets

    1. Identify all owned assets in an asset register that records current status. Maintain alignment with the change management and configuration management processes, the configuration management system, and the financial accounting records.

    2. Identify legal, regulatory, or contractual requirements that need to be addressed when managing the asset.

    3. Verify the existence of all owned assets by performing regular physical and logical inventory checks and reconciliation, including the use of software discovery tools.

    4. Verify that the assets are fit for purpose (i.e., in a useful condition).

    5. Determine on a regular basis whether each asset continues to provide value and, if so, estimate the expected useful life for delivering value.

    6. Ensure accounting for all assets.

Manage Critical Assets

    1. Identify assets that are critical in providing service capability by referencing requirements in service definitions, SLAs, and the configuration management system.

    2. Monitor the performance of critical assets by examining incident trends and, where necessary, take action to repair or replace.

    3. On a regular basis, consider the risk of failure or need for replacement of each critical asset.

    4. Maintain the resilience of critical assets by applying regular preventive maintenance, monitoring performance, and, if required, providing alternative and/or additional assets to minimize the likelihood of failure.

    5. Establish a preventive maintenance plan for all hardware, considering cost-benefit analysis, vendor recommendations, risk of an outage, qualified personnel, and other relevant factors.

    6. Establish maintenance agreements involving third-party access to organizational IT facilities for on-site and off-site activities (e.g., outsourcing). Establish formal service contracts containing or referring to all necessary security conditions, including access authorisation procedures, to ensure compliance with the organizational security policies and standards.

    7. Communicate to affected customers and users the expected impact (e.g., performance restrictions) of maintenance activities.

    8. Ensure that remote access services and user profiles (or other means used for maintenance or diagnosis) are active only when required.

    9. Incorporate planned downtime in an overall production schedule, and schedule the maintenance activities to minimize the adverse impact on business processes.

Manage the Asset Life Cycle

    1. Procure all assets based on approved requests and in accordance with the enterprise procurement policies and practices.

    2. Source, receive, verify, test, and record all assets in a controlled manner, including physical labeling, as required.

    3. Approve payments and complete the process with suppliers according to agreed-on contract conditions.

    4. Deploy assets following the standard implementation life cycle, including change management and acceptance testing.

    5. Allocate assets to users, with acceptance of responsibilities and sign-off, as appropriate.

    6. Reallocate assets whenever possible when they are no longer required due to a change of user role, redundancy within a service, or retirement of a service.

    7. Dispose of assets when they serve no useful purpose due to the retirement of all related services, obsolete technology, or lack of users.

    8. Dispose of assets securely, considering, e.g., the permanent deletion of any recorded data on media devices and potential damage to the environment.

    9. Plan, authorize, and implement retirement-related activities, retaining appropriate records to meet ongoing business and regulatory needs.

Optimize Asset Costs

    1. On a regular basis, review the overall asset base, considering whether it is aligned with business requirements.

    2. Assess maintenance costs, consider reasonableness, and identify lower-cost options, including, where necessary, replacement with new alternatives.

    3. Review warranties and consider value for money and replacement strategies to determine the lowest-cost options.

    4. Review the overall base to identify opportunities for standardization, single sourcing, and other strategies that may lower procurement, support, and maintenance costs.

    5. Use capacity and utilization statistics to identify underutilized or redundant assets that could be considered for disposal or replacement to lower costs.

    6. Review the overall state to identify opportunities to leverage emerging technologies or alternative sourcing strategies to reduce costs or increase value for money.

Manage Licences

    1. Maintain a register of all purchased software licenses and associated license agreements.

    2. On a regular basis, conduct an audit to identify all instances of installed licensed software.

    3. Compare the number of installed software instances with the number of licenses owned.

    4. When instances are lower than the number owned, decide whether there is a need to retain or terminate licenses, considering the potential to save on unnecessary maintenance, training, and other costs.

    5. When instances are higher than the number owned, consider first the opportunity to uninstall instances that are no longer required or justified, and then, if necessary, purchase additional licenses to comply with the license agreement.

    6. On a regular basis, consider whether better value can be obtained by upgrading products and associated licenses.