In a livelink system there are system administration tasks
versus document administration,taxonomy maintenance etc.If there is a well laid out plan and trained power users in your organization,user account creation,taxonomy maintenance
etc can be handled very easily by a trained power user.The system adminsiatrator acts as the interface between disparate systems,for eg he(she) may be the central person talking to Webservices group,DB group,Storage group etc.A system adminstrator for livelink is in my opinion a person who understands,OT's recommendations with a lot of common sense.If you search the OT knowledge base there might be actually numbers to the chores performed.Unless the system architechture is known(whether it is document centric,search centric,workflow centric,lapi centric),user load(how many hits per day,per hour),user expectations(is your system mission critical ?),Extranet/Intranet percentage
it is hard to throw numbers.What I have seen in two companies I have previously served is One System administrator+ a backup admin(or a willing person),several co-ordinators(they generally add users,maintains taxonomy for workspaces ,understands or is capable of developing maps for workflows).Most livelink problems are usually desktop or local computer related stuff,by slowly developing a methodology,FAQ ,you can drive down the hours spent by a user adminsiatrator.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
