Just read a Gartner report that answers some of my question.  It goes
into detail the metrics that need to be considered to determine your
company/industry staffing levels, etc....  But this is what I was
interested in knowing:
 
Gartner (March 2007)
Typical Staffing Ratio Ranges.  1 FTE can support...
Service desk - 280-480 users
Desktop L2 - 100-250 PC's
Desktop L3 - 500-1000 PC's
Windows server 15-75 servers
Unix Server 10-50 servers
 
Anyone else want to throw their numbers out to the list?

 
________________________________

From: Magnuson, Sig 
Sent: Tuesday, July 08, 2008 3:41 PM
To: 'CLUG General'
Subject: Optimal employee to server/device ratio


 
Just wondering what employee to server/device ratio's others have.  I
have heard that the optimal employee to server ratio is 1 admin to 15
servers.  Not sure if this is still accurate today or not.  I know that
automation (deployments/patching/monitoring) plays a role in this as
well as job responsibilities (operations work,  project work, or both)
 
A previous employer was 1 admin to ~70 devices (including storage, unix
server, linux server, backups, limited automation (automated OS
deployments), and both operations/project work) (3 admins total)
    Overall health of the env on a scale of 1 to 5 with 1 being best I
would say was a 4.  
    What did occur was mainly project work and break/fix operations
 
Another employer was 1 admin to ~60 devices (including storage, unix
server, linux server, no automation, and both operations/project work)
(3 admins total)
    Overall health of the env on a scale of 1 to 5 with 1 being best I
would say was a 4.  
    What did occur was mainly project work and break/fix operations
 
What is your company like?
What would you say is an ideal number?
 
I hear this book has some guidelines/formula for determining staffing.
http://www.amazon.com/Practice-System-Network-Administration/dp/02017027
11
 
looking forward to the responses.
sig
 


************************************************************************
This e-mail message is intended only for the person(s) named above and
may contain confidential or privileged information. If you are not the
person named or have not been authorized by them to access their mail,
please notify the sender immediately and delete this e-mail and any 
attachments without reading, saving, or forwarding.
************************************************************************
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to