Thursday, 29 September 2011

IT Asset Management-as-a-Service

Through the delivery of nearly one thousand IT Asset Management (ITAM) assessments, Oneclick Mobile has come to believe that a successful ITAM discipline requires too much time and specialization on the part of busy IT professionals.
To address this challenge, Oneclick Mobile has developed an entirely new model and method of delivery called ‘ITAM-as-a-Service’. These offerings are founded on the belief that it is the design of the ITAM process itself that is the most important factor in delivering measurable, long-term business value.
To lay the foundation for an effective process, ITAM-as-a-Service combines access to expert consultative services with a centralized repository to help gather, analyze and present ITAM data. The result? More time available for organizations to engineer and action the right decisions that maximize investments, save money and reduce risk.
Oneclick Mobile’s ITAM-as-a-Service offers a flexible and cost-effective way to offload the majority of the cumbersome, detail oriented activities required to support an effective IT asset management strategy. This model combines:
  1. Scheduled, direct engagement with our certified ITAM consultants to produce actionable Oneclick Mobile ClickCheck™ Assessment reporting.
  2. Self-serve access to a centralized online repository for inventory data, which provides detailed drill-down reporting, comparison to valuable ITAM knowledge bases, and a customized document store.

ClickCheck™ Assessment Services

In addition to offering a continual ITAM-as-a-Service delivery package, Oneclick Mobile can provide point-in-time assessment service consultations customized to your unique needs. Our accredited IT Asset Management consultants will analyze the data generated by your existing inventory technology and give you actionable insights into your IT environment. With almost no time or resources invested on your part, Oneclick Mobile can provide the following consultations and deliverables:
  • Software Licensing Categorization
  • IT Policy & Vulnerabilities Analysis
  • PC Deployment & Migration Readiness
  • IT Contingency Plan

Wednesday, 28 September 2011

What is Asset Management? - IT Asset Management


"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?

IT Service Management

What’s a service?

There are a number of ways to define service. But the easiest and most rough-and-ready is that a service is what the end-user experiences, and the user’s experience of that service determines if the service is working or not. An email service is the ability to send and receive email, the ability to log into the email system and see new messages and existing messages, the ability to look up a user’s information in the address book, and so on. For an order entry system the service is the ability to create an order, to look up customer information, or to price a quote.
This definition is fine for user-oriented services, but some services are only used by other services. For example, Active Directory is typically not accessed directly by users, but rather by other applications (such as messaging) that users interact with. For example, Exchange can be considered a user of Active Directory. However, even in this case, the service is defined not by the IT concept of the Active Directory servers, but rather by whether Active Directory responds quickly and correctly to requests for directory information.
For the purposes of automated monitoring, most relevant services are, of course, implemented using a collection of IT elements working together.

Service level management

The user community of a service typically has a set of expectations the service’s performance, availability and quality. Often these expectations are formalized in a service level agreement (SLA) between the user community and the IT organization. To be successful, IT must manage the service in such a way to meet these service level agreements or expectations.
Service level management involves measuring the user’s experience of the service to get real-time and historical data. It also involves using that data to ensure the service and its underlying IT components are working, diagnose it if there is a problem and provide reports to show compliance with service level agreements or service level expectations. Service level management activities include:
• Measuring service quality from the end-user perspective
• Using metrics that represent customer experience
Typical metrics for service level management are availability of the service (can I log into the SAP system?) and response time (can I load the HR benefits site web page in less than 6 seconds?).
• Using SLAs to articulate target service quality required by customers
• Evaluating the service on a per-service, per-customer basis

Systems management

Systems management is the familiar activity of monitoring servers and other IT infrastructure to detect existing and potential problems and notifying IT personnel when a problem is detected. Systems management is focused toward the IT elements that provide services, such as servers, applications, computer hardware, switches and networks. The activities in systems management include:
• Monitoring the health of individual elements and applications
Typical systems management metrics are CPU, memory and network usage; application errors; and connectivity.
• Rolling element health up to service operational health
• Identifying failures which may lead to or cause service quality impacts
• Evaluating on per-server, per-application basis

Service mapping

Assuming that we have both service level management and systems management in hand, there’s still one piece missing from the complete puzzle. It goes back to the need for IT to be able to take responsibility for both the IT elements underlying the services as well as the services themselves. Associating the customer experience with what’s going on within your IT systems (inside your server room, so to speak) enables you to do a superior job of managing the IT resources.
It’s clear that doing monitoring from a user perspective provides good insight for the IT manager. But what is to be done if a problem is discovered from the user perspective? At this point the IT operator knows there may be a problem somewhere in the data center, but where is it? This is where the service map comes in. One of the key values provided by a service map is to show how service level measurements—in particular, service level problems—relate to IT elements.
For example, a service map may show that end points in Houston, Tokyo and Munich are all focused on monitoring user activities against the main Exchange site in San Jose. If Houston, Tokyo and Munich all start reporting availability problems, then the operator, referring to the service map, knows to look in San Jose for issues. Chances are the Exchange site in San Jose has already reported some problems via the element monitoring occurring on its elements—the service map provides a simple way to correlate problems detected inside the data center with user impact outside the center.
Service maps have additional benefits. For example, if two Exchange servers in San Jose are showing problems according to element monitoring but no users (as represented by end points in Houston, Tokyo or Munich) are affected by those problems yet. The service maps show that one Exchange server provides email for the organization’s executives, while the other email is a gateway for the Japanese branch office—and it’s 3am in Japan. Using this information it’s easy to prioritize the fixes for the Exchange problems—fix the executives’ server first, then the branch office gateway.
If you have service level agreements with your customers, and a formal service catalog, you would have specific obligations for service levels to these two organizations, and could use that information to prioritize your activities.


An example of service management close to home

Your home telephone is a good model for understanding a service and the interaction of service level management and systems management. From the perspective of the telephone company, the telephone system is provided by an extremely large, complex and resilient distributed system of computers, network devices, cables and software, as well as personnel like operators and supervisors. But from the perspective of the customer, there are a few basic expectations that define whether the telephone service is working: 1) when I pick up the phone, I hear a dial tone, 2) I can dial a number and get (and stay) connected, 3) if someone calls me, my phone rings and I can talk to them.
As far as managing the telephone service goes, the telephone company spends a lot of time and effort making sure the complex distributed system of computers, network devices and cabling can meet the expectations of its customers. This involves monitoring each of the components so that problems can be fixed before they affect customers, as well as using redundancy in the systems so that problems can be routed around while they are being fixed, and other techniques. But you can also be sure that the telephone company is “picking up the phone” on a regular basis, from many different locations, to ensure that what the customer gets is what the customer expects.
Furthermore, most states have public utility commissions, representing the users of the telephone service, that enforce strict service level agreements with telephone carriers that are analogous to the service level agreements IT enters into with its users.