Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
IT Asset Management
Transcript of IT Asset Management
It is a systematic process of operating, maintaining, upgrading, and disposing of assets cost-effectively,
Asset management is a business discipline.
Financial asset management
Public and corporate asset management
Enterprise asset management Currently we are using 3 different systems for hardware management:
STS Inventory System
SharePoint hardware installation and removal reports
Proton management system Single database to store all information
Modular design for differing team needs
Introduce concept of ownership (individual or department)
Automated workflows for hardware acquisition, removal and change
Real-time status for currently assigned hardware
Information sharing on a need to know basis
End to end inventory control
* Note: Financial modules are out of scope Zero sum system
End to end lifecycle management
Integration with service lifecycles Definition of scope:
Types of hardware
Data population IT Asset Management IT asset management (ITAM) is the set of business practices that join financial, contractual and inventory functions to support life cycle management and strategic decision making for the IT environment.
Examples of ITAM systems:
Altiris Asset Management
Microsoft Distribution and Asset Management Services
Oracle eAM Current System Architecture Disadvantages and shortfalls No concept of hardware ownership
No accurate way of determining device status
Different systems present different results
Non-homogenous systems result in loss of information
No defined process
Information sharing through auxiliary systems such as Lotus Notes, GSD and BuySmart Possession Proposed ITAM Architecture Moving Forward Software Development lifecycle Scope Requirements Assessment System Requirements Specification Resource Allocation ITO - Client Services SAMPLE DATASHEET