RE: [None] Staffing Info

I just want to add that "number of servers" is way too often used as an 
inaccurate thumbrule for staffing levels.

I think a more accurate estimate would be some combination of "number of 
customers", "number of  problem tickets", "number of products", "number of 
custom requests", "number of upgrades per year", etc in addition to number 
of servers which can then be translated into manhours.

It can be just as hard to roll out/maintain a  base 100 server environment 
as a  1000 server  environment (other than the endpoints) if you have the 
same  number of  customers, products, requests, etc. Once an 
infrastructure is in place, it's easier to add incrementally to it as 
well.

My 2c.

- Mandar

On Mon, 31 Jan 2005, John Guadagnino wrote:

> Date: Mon, 31 Jan 2005 11:04:59 -0800
> From: John Guadagnino <John_Guadagnino@xxxxxxx>
> Reply-To: tme10@xxxxxxxxxxxxxxxx
> To: tme10@xxxxxxxxxxxxxxxx
> Subject: RE: [tme10] [None] Staffing Info
>
> Jason --  four guys just for engineering and another 7 for maintenance / 
> administration?!?!?   Send me some of your headcount please!!!!!!!
>
> We have 4 guys doing everything from-soup-to-nuts for a 6000 server environment.  DM, 
> ITM, Remote Control, TEC ... custom monitoring out the wazoo, custom notification 
> database, custom web interfaces for various components, integration with HPOV, PATROL, 
> Insight Manager ... I'm climbing the walls due to the never-ending requests for new 
> monitoring, reviewing & revising old monitors on a regular basis, regular 
> departmental re-orgs or transitions (very regular process around here) resulting in 
> changes to our monitoring schema because the Business Partners (i.e., internal 
> customers, the folks technically responsible for the stuff we're monitoring) change 
> their requirements with every burp & fart.  On top of that there's constant 
> maintenance and monitoring of the infrastructure .. i.e., monitor Tivoli itself because 
> shyte breaks.  Patches.  Upgrades.   Man ... what I wouldn't give for even
 a couple of "administrators" to take some of the daily grunt work off my hands 
...
> Donlen, you get neither sympathy nor advice from me  :-)
>
> John Guadagnino
> Gap Inc.
>
> -----Original Message-----
> From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]On 
> Behalf Of jason_shamroski@xxxxxxxxxxx
> Sent: Monday, January 31, 2005 6:37 AM
> To: tme10@xxxxxxxxxxxxxxxx
> Subject: Re: [tme10] [None] Staffing Info
>
>
>
> I think the sweet spot is 4-5 people and then it can go about with every 
> additional xxx number of endpoints.
>
> We have approximately 4 people doing the core engineering work around custom 
> monitors, tec rules, integrations, customization, etc... and then another group 
> of 7 people that perform all of the daily administration, changes, scheduling, 
> endpoint maintenance, etc...
>
> We have over 6000 servers with many custom DM and ITM resource models, over 35 
> integration points that flow events into TEC, autoticketing with Peregrine 
> Service Center and several other custom integrations that we had to build to 
> integrate with internally developed software.
>
> Jason
>
>
>
>
> Jason Shamroski
>         DRuffin@xxxxxxxx
> Sent by: owner-tme10@xxxxxxxxxxxxxxxx
>
>
> 01/31/2005 09:24 AM
> Please respond to tme10
>
>
>        To:        tme10@xxxxxxxxxxxxxxxx
>        cc:
>        Subject:        [tme10] [None] Staffing Info
>
>
>
> All,
>
> I am trying to justify additional headcount, and looking for some
> metrics to use.
>
> I have 2 people managing about 350 servers (Unix & Windows) with
> Framework (EP), ITM, TEC, and a few custom monitors, along with TWS.
>
> Can anyone provide information about their staffing and respective
> Tivoli products being managed ?
>
> Thanks
>
> Donlen
>
>
>
>
> This transmission may contain information that is privileged, confidential 
> and/or exempt from disclosure under applicable law. If you are not the intended 
> recipient, you are hereby notified that any disclosure, copying, distribution, 
> or use of the information contained herein (including any reliance thereon) is 
> STRICTLY PROHIBITED. If you received this transmission in error, please 
> immediately contact the sender and destroy the material in its entirety, 
> whether in electronic or hard copy format. Thank you.