cosign-discuss at umich.edu
general discussion of cosign development and deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Total cost of Ownership
I'm sorry about the delay replying. It was difficult to separate
cosign development/community support from running the weblogin server &
supporting campus. Running our actual servers is greatly simplified by
our use of Radmind <http://radmind.org/>.
The time spent running, monitoring, and maintaining the weblogin
servers and gathering usage statistics is slightly less than an hour
per week. This is our only fixed cost.
Signing CSRs for CoSign services takes about ten minutes per request.
Apache users are basically self-sufficient: we get an e-mail message
from them asking for a service name and that's basically the first we
hear from them (and the last). IIS users have, thus far, required
slightly more support, but I believe that has changed since the IIS
filter reached 1.0. There is also time spent per week getting the word
out about CoSign on campus. These costs are approximately linear with
the number of users we interact with. Some users take a couple of
minutes to get started, some take a few hours. We spend between 2 and
4 hours per week supporting campus users. We're pretty big (>100,000
users) and decentralized, though, so YMMV.
On Apr 5, 2004, at 10:10 PM, Brett Lomas wrote:
Hi Kevin and others
I am just evaluating what the Total Cost of Ownership would be for
CoSign if deployed within the UoA. Can I get an estimate on the number
of hours you all spend doing day-to-day maintenance on the system?
This would include support, patching and upgrades etc but not bug
fixing and development? Just a rough number of person hours per week
would be good.
Information Technology Systems and Services
The University of Auckland
Phone: +64 9 373 599 extn 86499
Mobile: +64 21 757 096
... "In, as you say, the mud." ...