Through my personal experience there are broadly 2 factors on customization projects - cosmetic customization and customization where you require a little more lower level work wherein you might need to build another application that might be driven together with your OTB application.
On cosmetic customizations usually 1 person - that too a part time resource should be sufficient to maintain your application until such times that this resource is able to impart the necessary maintenance schedules or routines developed to the DBA...
On the other hand if you are faced with the task of building applications and customizations wherein there is more development work involved you would require a long time resource or even a permanant resource with the skills of Remedy development, strong database knowledge, knowledge of other tools an added plus..
Regards
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Time Warner Cable Project,
Virginia.
----- Original Message ----
From: Will Du Chene <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Tuesday, July 18, 2006 3:49:25 PM
Subject: Re: OT:How many Administartors does it take ?
From: Will Du Chene <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Tuesday, July 18, 2006 3:49:25 PM
Subject: Re: OT:How many Administartors does it take ?
The only answer that I think of is: it depends.
The number of administrators and/or support staff is going to depend upon
what you intend to do with the product once you have it installed. Are you
planning on integrating it with existing systems? What are your support
hours going to be like? What sort of support coverage are you doing to
need?
It has been my experience that most AR Admins/Developers are the typical
over-worked,
not-happy-unless-they-are-moving-at-mach-2.5-with-the-hair-on-fire types.
They dread being idle, require lots of pizza and... Are you buying any of
this? No? Well, I tried... :-)
Most of the implementations which I have been a part of have always had at
minimum two admins. One was a primary, and the other was a backup. Having
just one admin is like having one foot and then expecting to run. It
doesn't work very well. Vacations, sick days, projects, other work all
factor into it. If you go with two, you might want to stagger schedules,
such that one comes in later in the morning and stays later in the evening
to do release migrations and to extend the coverage window into the
evening, etc.
One of the larger implementations (over 300 concurrent, numerous apps, the
AR System was their pimary tool) had six staff. There were two developers,
one manager and three analysts. Another had two developers, one manager
and one analyst. Other implementations of around a hundred or so had two
admins as well.
Piece of wisdom: develop sub-administrators or local subject matter
experts. Farm the care and daily feeding of certain aspects of your system
out to them, rather than relying upon your admins to maintain it. That
will free them up for more important things.
HTH.
> Hello All,
> I would like to find out on the average how many ARS Administrators are
> needed to maintain a modified out of the box Help Desk system.
> The type of shops I would like hear from create 800 - 1000 tickets per
> year with about 175 consecutive users.
>
> Thank You for you help,
> Tom
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
The number of administrators and/or support staff is going to depend upon
what you intend to do with the product once you have it installed. Are you
planning on integrating it with existing systems? What are your support
hours going to be like? What sort of support coverage are you doing to
need?
It has been my experience that most AR Admins/Developers are the typical
over-worked,
not-happy-unless-they-are-moving-at-mach-2.5-with-the-hair-on-fire types.
They dread being idle, require lots of pizza and... Are you buying any of
this? No? Well, I tried... :-)
Most of the implementations which I have been a part of have always had at
minimum two admins. One was a primary, and the other was a backup. Having
just one admin is like having one foot and then expecting to run. It
doesn't work very well. Vacations, sick days, projects, other work all
factor into it. If you go with two, you might want to stagger schedules,
such that one comes in later in the morning and stays later in the evening
to do release migrations and to extend the coverage window into the
evening, etc.
One of the larger implementations (over 300 concurrent, numerous apps, the
AR System was their pimary tool) had six staff. There were two developers,
one manager and three analysts. Another had two developers, one manager
and one analyst. Other implementations of around a hundred or so had two
admins as well.
Piece of wisdom: develop sub-administrators or local subject matter
experts. Farm the care and daily feeding of certain aspects of your system
out to them, rather than relying upon your admins to maintain it. That
will free them up for more important things.
HTH.
> Hello All,
> I would like to find out on the average how many ARS Administrators are
> needed to maintain a modified out of the box Help Desk system.
> The type of shops I would like hear from create 800 - 1000 tickets per
> year with about 175 consecutive users.
>
> Thank You for you help,
> Tom
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
