ITAM – ASSET MANAGEMENT
What is ITAM – Asset Management
IT asset management (also known as ITAM) is the process of ensuring an organization’s assets are accounted for, deployed, maintained, upgraded, and disposed of when the time comes. Put simply, it’s making sure that the valuable items, tangible and intangible, in your organization are tracked and being used.
IT assets have a finite period of use. To maximize the value an organization can generate from them, the IT asset lifecycle can be proactively managed. Each organization may define unique stages of that lifecycle, but they generally include planning, procurement, deployment, maintenance, and retirement. An important part of IT asset management is applying process across all lifecycle stages to understand the total cost of ownership and optimize the use of assets.
Benefits of ITAM:
Single Source
Providing a single source of truth
Utilization
Improving utilization and eliminating waste
Productivity
Enabling productivity without compromising reliability
ITSM
Supporting ITSM practices and enabling teams across organizations
ITAM Process:
IT asset management is not a project. You don’t do it once and expect it to be finished. ITAM is a process that teams execute on a regular basis or as assets, goals, and tools change.
- Inventory assets
- Calculate lifecycle costs
- Tracking
- Maintenance
- Financial Planning
Proposed Solution at Dr Reddy’s:
- SAP to trigger Asset request where asset needs to be refreshed. Notify user. No approval cycle for these requests
- PR and PO approval only by IT-HEAD / Director. Need to create schedule agreement prior
- Asset approval for exceptions will include L+1 and BU head
- Need a mechanism to move stock from one hub to another or from plant/user location to hub
- ITAM to take care of payments
Workflow Approvals Required:
- Users at level R3A and above are eligible for laptop by default. And this asset request for laptop does not require any approvals
- Users at level R2B and below are only eligible for desktop by default. If they need a laptop request, it follows the exception workflow, which require L+1 and R6 (BU head) approval
- For Desktop request by any User, it requires the approval of L+1, HOD
- Asset refresh does not require any approvals, if the request is for the same kind of asset that the user currently has.
Key Points & Assumptions
- All developments will be carried out in SAP
- Only one line item per request.
- Position ID / Employee ID will be considered in the request
- Assuming position ID is unique.
- Screen design will be in UI 5.
- Reports: 2 Reports considered for tracking.
- NRGP Integration: Assumed to use the existing NRGP process. master.
- Existing Processes: Considered to use the existing processes (PR, PO, Goods Receipt, Stock Transfer, Receipt at receiving location, Fixed Asset Management)
- New Hub Locations: Currently we have only 1 Central Location is configured in SAP. Assume for the Other locations, it will be the existing Plants (SAP) in which we can configure the Process.
- Bulk Request upload to be considered in phase 2
- Approval for the Request will be carried out based on the approval matrix shared.
- Automated PR creation process (From Reservation) can be considered
- Asset Labeling process not considered. Only tracking reports will be provided.
- The Effort estimation may vary after detailed requirement gathering.
- Asset clean up action not considered.
- Cut-over activities to be carried out by Client.
- Assuming that warranty dates are maintained in Asset
