Slashdot Mirror
Prioritizing Computer Replacements?
cuzality asks: "The public library I work for is (hopefully) going to get some money in the coming months to replace some of our computers. Since we can't replace all of them at the same time, we need to decide which machines to replace first. We have begun working on a survey instrument to help us accomplish this, but since this is the first time we are replacing computers (most were bought in 1999), this is also the first time we have tried to put together a survey for this purpose. What kind of criteria have you used to prioritize replacement of computers? Examples of surveys you have used would also be very helpful..."
at least that's what we always do....
Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
Now quite frankly.. what kind of stupid question is that?
1. Are there broken computers or computers which are beginning to show critical signs of wear?
2. Are the computers sufficiently fast for the tasks assigned to them?
How many hours a week is each computer used?
What functions does each computer perform (surfing web, accessing custom library application, etc.) and what's the breakdown of those functions in percentages?
Assemble a list of all functions the computers are used for, determine how each function would benefit from running on newer hardware.
What new functions would the library like to incorporate utilizing newer computrs? Assemble a wish list, and then determine through a panel which of those functions are likely to be implemented in the next year if new computing resources are available.
With this information you should be able to determine which computers will benefit most from an upgrade. Other factors to consider are that it's more estheticly pleasing to have similar computers together (mild preference for grouping computers of the same type). Publicly usable computers that are upgraded can make a positive statement to library patrons (preference for visibility).
---
I support spreading santorum
- Figure out what you are doing or want to do with the computers. Is that what the survey is for?
- Figure out what you would replace them with (including networking, licenses for proprietary software, etc.) and figure out what it will cost and thus how many you can buy.
- Figure out which of your current machines are serving you the least in this capacity. If you have a bunch of unstable Win95 or Win98 machines that crash a lot, I'd say those are good candidates. If you have older machines that are stable, consider leaving them alone if it will allow you to replace more of the unstable ones.
- Go over the list you make, poke holes in it, and start again. When you're done, show it to others and don't look at it for a week, then come back to it and see what you think of your logic.
There. Any other part of your job you'd like us to do for you? I mean, how hard was that?While some machines are broken, or so slow that they need replacing, the time taken to replace other machines is often non-trivial for a benefit that is minimal. Sometimes, simple upgrades have much more effect for the amount of time and money spent. A common one is more RAM, but a lot of users would benefit a lot from a new monitor or a flat screen - or a second screen even. Little things, like replacing ball mice with optical ones go down well.
You might also look at some the infrastructure. If everything is slow because the network is overloaded, replacing machines won't make any difference.
In a lot of firms, the top people get new kit regularly (which they don't need), and the bottom people suffer with old cast-offs. Look at the entire setup, and see where people are needing upgrades the most, then replace those parts.
-- Steve
FWIW, I used to be automation consultant for a regional library system, and we generally recommended folks look at things in this order:
:)
...brig
PUBLIC machines first
As much for PR reasons as any.
SHARED STAFF MACHINES second
Usually most cost-effective distribution.
DEDICATED STAFF MACHINES third
Meaning the director's desktop usually gets upgraded last!
Within each category, we then looked at how old the BIOS was and how much RAM each machine had. Then we looked at budget issues.
These are, of course, general guidelines... sometimes things are done differently because you either have a funding source wanting to push a particular program or service... sometimes you have a machine which fails or is unreliable. Common sense should always override a plan, if it hasn't already been incorporated within the plan.
-- When I grow up I'd like to be a systems defenestrator.
IMHO, 90% of the operations office staff and library patrons perform do not require specialized, personal PC's. Diskless "thin" clients are by far the least problematic with respect to hardware failure or OS maintenance.
Unless you absolutely require Windows clients, which I highly doubt given that most Library databases are searchable via Internet or Intranet sites, stay away from them. If the recent IE exploits hadn't scared you away yet, nothing will.
assert(expired(knowledge));