ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Prices
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


IT Jobs

Become a ZDNet.co.uk member

RSS

Hardware News

How to spend your hardware budget

Shannon T. Kalvar

Published: 19 Feb 2004 11:10 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

IT managers need to know how to sift through all of the conflicting data to figure out what we really need to buy. Here's how.

The need for new hardware seems to constantly plague IT departments. Servers fail. Our clients constantly request new functionality without any clear understanding of the underlying hardware concerns. Leases run out, forcing us into replace-or-purchase decisions. New technologies refuse to work properly with older equipment, despite the manufacturer's warranty that everything will "play nicely together." How do we sift through all of the conflicting data to figure out what we really need to buy?

There are as many ways to work out the answers to the above questions as there are managers forced to make these decisions. However, all of us have specific triggers that cause these decision points to appear, as well as several generic decision parameters we plug our unique situations into. By balancing the factors of the triggering event with the various parameters, we can come to some kind of understanding about what kind of new hardware we actually need to purchase.

Triggering events
We don't generally wake up one morning and say, "let's go out and spend a million dollars on new desktops! That sounds like a great idea!" The need to buy new hardware, to deploy it, and to add it to the maintenance schedule comes about because some factor in the IT environment has changed. These changes come from a variety of sources, each requiring a slightly different approach to the analysis.

Common trigger events include:

  • Massive increases in hardware-related problem tickets.
  • Utilisation numbers reaching a critical threshold.
  • Leases running out.
  • The installation of a new software package.
  • Regime change in the executive management.
  • The requests of specific user groups for new equipment.
  • Next

    Previous

    1 2 3


    • Email
    • Trackback
    • Clip Link
    • Print friendly Print with Dell

    Did you find this article useful?
    85 out of 183 people found this useful


    Full Talkback thread

    0 comments

    Company/Topic Alerts

    Create a new alert from the list below:



    Related Jobs

    Analyst Programmer

    Provide an impact assessment and feasibility assessment for any change requests raised against a project. The team is responsible for ETL development ...

    Senior Project Manager

    Preparation of Client Invoicing Spreadsheet for current projects - Ensuring mitigating actions relating to issues are completed - Identifying and ...

    C# Lead Developer C#, ASP.NET, SQL Server Microsoft Gold Partner - Oxfordshire

    Were the market leader in providing IT Solutions to the UK Education sector, and our online assessment services division are seeking a talented Lead ...