"Asset management may be defined as a comprehensive and structured approach to the long term management of assets as tools for the efficient and effective delivery of community benefits. The emphasis is on the assets being a means to an end, not an end in themselves." (Austroads 1997 Strategy for Improving asset management practice, p4).
The World Road Association (PIARC) has adopted an OECD definition of asset management, which in turn was derived from a FHWA definition, viz:
"A systematic process of effectively maintaining, upgrading and operating assets, combining engineering principles with sound business practice and economic rationale, and providing the tools to facilitate a more organised and flexible approach to making decisions necessary to achieve the public's expectations."
In the light of these broad definitions, road asset management means managing a road network (roads, bridges, traffic facilities, etc) to satisfy the requirements of business and private road users, at the lowest possible cost over a long period of time.
The main streams in asset management are:
- identification of need for the asset, in the light of community requirements
- provision of the asset, including its ongoing maintenance and rehabilitation to suit continuing needs
- operation of the asset
- disposal of the asset when the need no longer exists or it is no longer appropriate for the asset to be retained.
Information Technology Asset Management
PURPOSE
Information technology asset management (ITAM) can help your agency reduce the life-cycle costs of its electronic equipment. This guidance will help organizations improve their existing ITAM practices, or develop a new ITAM process.
INFORMATION TECHNOLOGY ASSET MANAGEMENT GUIDANCE
Auditing Current Business Practices
Since all organizations are different, the most important first step is to map out the process by which information technology (IT) assets are managed throughout their life cycle, from purchase, all the way through to final disposition. Some key questions to look for in this self-audit are:
• How many steps are involved?
• What are the time and cost requirements and limitations?
• Are there redundancies inside and outside the organization?
• Are their viable alternatives?
• Who is involved in the process? Should they be involved? Are their others in the organization that should be part of the process?
• How structured/consistent is the ITAM system in currently in place?
• Is there training for ITAM?
• Do the current ITAM practices open the organization to legal or data security risks?
Planning the Future
If your organization plans for the future by requests, then the opportunity for improving efficiencies/output can be vastly improved by taking the time to plan for the future. What is the goal of the organization or the particular department and what are the applications critical to success? Then it is just a matter of developing a road map between the two.
Once the IT needs have been determined, they can be appropriated at the departmental and functional level. It is critical to identify the exact IT hardware and software requirements for each position; this will allow the agency to:
• Move desktops from power users to those with lesser needs, eliminating both overpowered desktops that waste IT dollars and conversely, under-powered desktops that can inhibit productivity. Ensure compatibility between individuals and/or units that need to share files.
• Establish minimum hardware standards to avoid obsolescence.
• Reduce the scope of acquisition, support and maintenance requirements.
• Institute an inventory of standard items, to better anticipate demand.
Receiving New Equipment
When new equipment comes in the door, it is important to evaluate the following, which are critical to successful ITAM:
• Reconcile assets received against original order;
Information Technology Asset Management
Check for damage;
Populate your database with serial numbers and all other relevant information;
Assign the equipment to a technician;
Prepare for installation, with attention to desktop standards, custom software, etc.;
Test and approve unit upon installation; and
Enter into the ITAM database the following: user, location, and configuration.
The Asset Lifecycle - Who? What? Where? When? How?
Considering the frequency of desktop changes, it is imperative ITAM best practices be instituted requiring ongoing inventory and tracking capabilities. How you implement regular inventory tracking will differ from agency to agency.
In particular, the agency needs to carefully monitor installation, movement, and disposition of equipment; adding and changing information to allow regularly scheduled reports. If successful, an organization should be able to answer questions such as:
• How many desktops are unassigned?
• How many employees have no equipment?
• How many desktops are assigned to end users who are no longer with the agency?
• How many end users have multiple desktops assigned?
• What can be gleaned from the repair, recycling?
Troubleshooting the Troubleshooting
Asset management information and best practices are invaluable in diagnosing individual desktop problems and minimizing end-user downtime, particularly when the auto-discovery data is integrated with the help desk system or tech support. Support staff should be able to access individual desktop configuration details directly from what ever system your agency has in place. Integrated warranty and maintenance data can also help the support team determine who is responsible for repairs.
Mitigating Hardware and Software Migrations
ITAM best practices should be integral part of migration planning. Before a decision to migrate is made, a report should be run answering the following:
• What percentage of the affected desktops fail to meet the prerequisites?
• What is required to bring those machines up to speed?
• What are the costs for parts and labor to bring them up to speed?
Software License Management
A key element of ITAM is managing the software. Keeping track of the number of licenses and the software loaded on to each desktop can yield substantial savings by monitoring installations and usage plus changes in the vendor’s pricing and licensing models. Ongoing portfolio management will also help you determine if end users have the tools they need, in compatible versions, and so on. Successful software management should:
• Establish and implement a clear software policy;
• Define the software acquisition process;
Information Technology Asset Management
• Inventory existing software assets, capturing, at a minimum, product name, version, location and manufacturer; and
• Proactively determine software license compliance, with at least semi-annual audits.
End of Life
Once an aging asset begins to hamper productivity, the organization needs to have a formal end of life strategy in place concerning final disposition. Final disposition is clearly more complicated than simply throwing a desktop out with the trash. There are numerous issues and recycling options to consider that go beyond getting rid of the old machine and receiving a new desktop. These issues include:
• Can the machine be moved to another end-user with fewer needs?
Conversely, is there another machine in the Agency that will meet this end-user’s needs?
• Even if the asset is obsolete, what about the parts, both hardware and software?
• Can the parts be relocated within the organization?
• Can the licensed software be used on other assets?
• Can the asset be donated?
• If the asset is donated, what happens with the licensed software?
• What process is in place to ensure proper final disposition of donated assets?
• Is there any proprietary information on the machine?
• Who erased the information on the machine?
• Who certified that all the information on the hard drive was erased?