IT support staff.

I suggest that you search this site.

There have been a number of discussions on this topic. Along with a couple of articles.

Bottom line, there is no "fixed" "reliable" industry guideline.

Each situation is unique.
You need to determine for your situation what to measure to see if support is "adequate".

Chas

If you were a business I would say that you should have a
staff of of about 12.
2 Help desk generalist (determine if software or hardware)
$30,000 each + benefits

2 Escalation help desk
$40 - 45,000 each + benfits

2 Network (router and switch)
$60,000 each + benefits

2 Server
$55,000 each + benefits

2 Service and maintenance. High Schools require a lot of
reimaging.
$35-40,000 each + benefits

1 Network / Computer server Security FW, ITS, Anti-virus
$60-75,0000 + benfits

1 Manager
75,000 - 85000 + benefits

I know this is a tough sell, but it's what's needed for a first
class operation to be actively managing and maintaining
the systems. Whatever you do, please resist the urge to
use students for anything that requires access above user.
They are not evil. Just very curious.

For support I use 50 Staff to 1 IT. That will need to flex as a company grows so 50-60 is the best. Make sure your not geting too close to 70.

Larger firms tend to be more efficent and pamper less to users needs so figures of 100 to 1 and sometimes 150 to 1 can be common but they tend have long lead times for most tasks and dont provide a very responsive buisness.

400 Workstations and 1500 users will mean you will need to add a weighting to take in to account the extra training type questions you will get over an extended user base - Stuff like - How do I set up Out of Office etc.

Once you have worked that out you will then need to sort out your back-office staff.

Management of the Servers [Im assuming Windows Here] with little investment in tools to reduce the mundane tasks is about 25 Servers to 1 IT Member. With the right tools and experiance you can get about 50 to 1.

Management of the network is a tricky one - Do you have firewalls, VPN's, remote workers etc. Based on your supplied info the Network Administration could handle that workload but you will need to keep an eye on what volume he/she has so you can add extra staff if required.

Management of the department, board reports, liasing with Business heads, Business need research, Product Research, Support Management, Project and Change management, Documentation, Purchasing, Budget Management and general slack for Holiday cover means you will need at least 1 IT Manager.

These ratios will provide a balanced but effective department. Get that message accross and your manager etc can then say what response times, expectations should be delivered and you can then taylor it accordingly. If they want to reduce that service level [I.e server uptime, response times to requests etc] then you can show that by altering the Support Ratio etc. The last thing about this method however is that it makes justifying budget for department and IT staff investment really easy - something which can be difficult. For example - You want some software to monitor event logs and server health. This is currently done manaually once a week and consumes 2 hours. The software costs ?3,000 and if invested in would increase his ratio of capacity from '25 to 1' to '30 to 1'. The payback would be weeks and your department then has extra capacity [not doing a mundane task] to work on the nicer stuff. Works with training too.

Regards

John

We have one IT Manager (me) and one Network Manager and a Technician in a small college in London. Our infrastructure is as follows;

2 networks (teaching & admin)
8 servers 200 workstations 50 laptops 35 printers and networked photocopiers
a few graphics tablets, digital projectors, smartboards, wireless network, handheld/tablet PC's etc.

We get by with a ratio of 1:100 technicians to computers but I will be putting in a request for more support staff as our network grows. In the past I used to work on 1:50 but with active directory and the improved stability of Windows 2003 server and windows XP (over windows NT Windows 95/98)I think 1:100 is reasonable. I reckon I can provide a good level of service and support to the users and the organisation with this level of staff.

I am a dept of 1 right now (24x7 support) and handle all aspects of IT from Desktop on up including phone system and building security. I have mulitple locations: Corporate office has 70 pcs and phones, 8 servers, 3 switches, 1 router, A Nortel phone system and dvr for security cameras.
I have other offices connecting with terminal server and also support their systems.
How do I justify headcount?? I know I need help, but how do I convince upper management who sees me as a 'cost' center instead of a 'profit'center.

more things to consider that increase the complexity of your job and therefore drive up the cost:
* any special applications you need expertise on? IIS? internal web sites to support?
* are all the workstations identical in hardware and/or system/applications? are students and/or teachers allowed to load their own stuff [indicriminantly] on random computers?

My take [having managed 5 servers/200 mixed PC & MAC] is you ought to have one hardware type for caring for hte printers, network, odd hardware problem; 1 tech to support every 50 or so workstations; different techs need a specialty in server, IIS, email server, apps, etc.

I'll bet that the district HR or some education trade journal has statistics about school district staffing.

I suggest you change your thinking ... instead of trying to recommend based on standard ratios, look at what is getting done, what is not getting done, and the problems with the current staffing situation. Measure satisfaction among the users. Measure how long things take. If you don't have time to measure, make guesses or assumptions. Then make recommendations based on addressing the issues that come to light.

One of the best ways to quantify staffing levels for minimum level of IT support staff is to complete a risk/mitigation plan.
Identify groups or classes of problems and typical duties (log checks and so on), then associate a business risk value and mitigation value to each.
Once the values have been assigned, grade the groups of problems and mitigation by priority and associate average resolution times.
Equipped with this newly acquired arsenal you can develop a rich set of statistics which can help you plan (present and future) staffing levels versus fix response times, incorporate the use of deviation plans (for such things as upgrades/patches).
This of course is just one approach and not a definitive guide; nonetheless it is a good starting point. The key to such techniques is the upkeep, once started, management will become dependant upon the stat's you produce as they will soon realise that you are quantifying and justifying IT spend against business continuity which translates very nicely into boardroom communications.

At most high schools there is only one with a teaching staff member or 2 to assist and that is only because IT in that invironment is seen only as an extension of wood or metal work ... old school management thinking.

The positive is that younger management does recognise IT support and budget for staff.
Thus in todays environment schools are a business and must be viewed with that thinking supporting the academic environment in the very lucrative and highly competitive education environment.

You can approach your diliema by promoting your schools quality learning that is vigorously supported by IT however, to maintain its competitive edge and further increase your institutions standing requires increase in there support base with IT on a par with the teaching staff.
Though the other controlling fact is the schools budget. Unless a proposal is forwarded it cannot be bugeted for.

This is very broad ... hope it hleps

Be happy! hehe

I work at a School Distict in Eastern Canada.

My assigned duties (similar to my co workers)

9 Schools
800 Clients
9 Servers
3500 Users
9 Routers
10 Managed Switched
20 (Unmanaged)Switches
Lost count of printers (But there are over 60 networked)

I work 36.25 hrs a week. Salary. FT-Perm.

Our Dept has 3 Tech, 1 Manager, 1 Clerk

No, we can't keep up..... and we can't bail cause there are no jobs in Atlantic Canada to go to.

Kylex

I am managing;
1381 users
957 workstations
259 network printers
12 servers
47 switches
3 routers
1 Pix 515
1 Layer 3 fibre switch
in 5 facilities
all by myself working 50 hours a week on average.