Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Livelink Staffng considerations 2

Status
Not open for further replies.

KHuie

MIS
Dec 15, 2008
17
US
All,

For a relatively small organization <500. What would be the Livelink staffing requirements and skill sets needed? Let's assume they are dedicated solely to Livelink.

My Thoughts:
* 2-3 Business Analysts (Requirements Gathering, Process Modeling)
* 2-3 Super User in Livelink (Training needs, WF development, Support)
* 2 Developers <OScript, others???> (System Mods, customizations, integration, etc.)
* 1-2 Sys Admins (T-shooting, Maintenance & Support, upgrades, etc.)
* 1 DBA

Please fill in the holes as there are likely many...
Also is there a means to quantify a need; i.e. for every 100 users you need 'blah, blah, blah' for staffing?

Thanks a Mill!
KHuie




 
Ken,
Not sure that you would need the developers, guess it depends on what you are doing, the DBA could also be a shared role as LL may not need a dedicated DBA for a small implementation.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006
 


Ken,

I agree with Greg. Being a longtime Livelink Admin/Analyst. I have been worn various hats (most at the same time) and they only pay me for one position :) Currently, I am the Livelink Admin, Analyst and Architect. I am not a developer but work closely with our web services (portal team) to facilitate integration with other Enterprise Systems. We don't have a "livelink developer" on staff but really don't need one. However like Greg says it all depends on what you want to do. I don't think you need separate staff to be a "Super User (Training needs, WF development, Support)" those roles are usually a train- the trainer concept and can be found/appointed by department. Open Text has a OKM/KM/end-user CIS model that in my opinion still works in most environments. Moreover, if you provide scripts for your help desk support personnel for Livelink general issues (there are always the same issues questions) you can already utilize your desktop/customer support. Actual technical issues (not permission, content issues) can be sent to your Livelink Admin Queue. I have worked as a consultant and employee at many different companies and there are definately some that have a better model than others. Hope it helps...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top