AITP / Project Management Institute (PMI) Joint Meeting

October 16, 2003

 

A computer system is just that a system of hardware and software when connected enables users to efficiently perform their job. For the purpose of this paper we are focusing on the following areas:

 

            Server Software – Application and Operating System

            Server Hardware – Computer which will serve as a server for applications and/or files.

            Computer infrastructure – Cabling Printers, Network Equipment and Workstations

 

 

Server Software Considerations:

 

                        What is the purpose of this purchase?

 

                        Are the end-users of the software involved, why or why not?

 

Have you solicited user input for additional roles or services that this software may provide?

 

What operating system will be used?

 

How will it be configured (i.e. what role(s) services need to be running for this software to do its job)? 

 

Do you have another server that will be a “model” for the installation and configuration of this new one?

 

What additional software or utilities will be loaded on this same server?  Any incompatibilities?

 

If additional, related services are needed, is there another step-up product worth consideration?

 

Have all appropriate licenses been purchased and allocated for use by this server?

 

           

Server Hardware Considerations:

 

After defining the server software refer to the software documentation and user-groups for recommended hardware. Consider all software packages and number of users.

 

Are you using existing hardware or purchasing new?

 

If you are using existing hardware will an upgrade be necessary, and how much down time will be required?

 

How critical is up time once the server is on-line?

 

                        What is needed to ensure this level of up time?

 

                        Is the cost to ensure up time acceptable?

 

                        What, if any, equipment is needed to backup the system?

 

What data backup procedures will be needed?

 

Who will be responsible for running the backups?

 

                        What brands of equipment has the organization standardized upon? 

 

What is the current financial health of your organizations major computer equipment vendors?

 

Will the new server “play nice” with existing servers?  Are its components fully compatible?

 

                        How many operating system upgrades (versions) do you anticipate for this server before replacement?

 

How do you envision the role that this server plays to change over the course of its life cycle?

 

Have you allowed at least 25% of “headroom” for “growth” in the role of this server?

 

                        Has a test lab/location been prepared for this new server, or is it “live” as soon as it’s booted?

 

                        What is the testing period allowed before “going live” with the new server?

 

                        Who will determine testing requirements, perform and report the tests?

 

Is this server dependent on other equipment, e.g. shared memory, network attached storage?

 

Have you examined extended warranty and support options?  Are these important to you?

 

                        Once operational, what is your plan for support concerning this server?

 

What is your plan for training of users?

 

Who will be responsible for training?

 

Who will be responsible for the day-to-day operations of this server?

 

                        Once operational, who decides what “patches” and upgrades will be applied and when?

 

Who decides which “hot fixes”, “patches” and service packs should be installed?

 

Who decides which hot fixes”, “patches” and service packs be avoided?

 

How will this computer be physically protected from unauthorized access?

 

How will this computer be protected from Internet, e-mail and other electronic threats?

 

How will the files on this server be protected?

 

 

Best Practices for server maintenance:

 

                        Do not install anything you don’t need.

 

Disable any services that you don’t need.

 

Limit the number of key services hosted on a single server.

 

 

Infrastructure Equipment:

 

                        What is the purpose of this purchase; does it provide a new service, or replacement hardware?

 

If a replacement product, have you double-checked to make certain that no features are lost?

 

If this product provides multiple services, what it your plan to replace these services in the event of a failure?

 

                        What brands of equipment has the organization standardized upon? 

 

What is the expected “life-cycle” of this new product? 

 

How do you envision the role that this product plays to change over the course of its life cycle?

 

Have you allowed at least 25% of “headroom” for “growth” in the function of this product?

 

                        Has a test lab/location been prepared for the new product?

 

                        What is the testing period allowed before “going live” with the new product?

 

                        Who will determine testing requirements, perform and report the tests?

 

Will all aspects and functions of the product be tested, even if some of them are not planned for immediate production use?

 

Have you examined extended warranty and support options?  Are these important to you?  Examine your previous repair records for similar equipment in your organization.

 

 

Best Practices for infrastructure equipment:

 

                        Standardize on the same make and model of equipment when possible.

 

                        Check the vendor’s web site frequently for known issues, firmware or other upgrades and security issues.

 

Establish a benchmark for performance standards as soon as possible, after introducing the product into production use.  Check this routinely to record discrepancies.

 

 

Financial Considerations:

 

 

How much do you want to spend?

 

How much are you allowed to spend?

 

How much do you really NEED to spend to get the features you want?

 

                        Is there room for compromise?

 

Have all purchasing options been examined to determine the best cost and means of purchase?

 

                        What is the expected “life-cycle” of this new server? 

 

If your quote is more than 45 days old, ask for a new quote – yes, prices can change that often.

 

If your quote is more than 90 days old, be sure that you ask for a new quote, also, with this much time lag; spend a time researching your options again, at least from the selected vendor.  A new model, with a different price point and more features may well be available.

 

Always ask the question, “Is that your best price”, from any vendor.

 

Are any special “user” or “node” licenses required for any function of this product?  Consider these in to your total cost.

 

What is the current financial health of your organizations major computer equipment vendors?