Administor profile

S

Siva

In order to implement / support any EPM initiative, there has to be a
good support structure.

What are typical responsibilities of a Project Server administrator?

Is the ideal person one, who is a strong functional person or a
technical person?

Thanks for any valuable input.
 
G

Gary L. Chefetz \(MVP\)

Siva:

We see two roles: A technical administrator and a business administrator.
One of the largest challenges for a business unit implementing Project
Server in a non-IT environment, and often within an IT organization, is
getting the IT to agree to an SLA for Project Server. In most cases, the
technical folks contribute little support to an EPM solution beyond
maintaining the platform and platform technologies. It is wise for the PMO
or implementing business unit to retrain control of the configuration and
day-to-day system administration. This leads to better, faster and more
intelligent internal support model and doesn't require deep technical skills
whereas it requires a significant depth of knowledge in the organization,
its personalities and its process.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-
 
M

mark.everett

Many organizations clearly differentiate between system administration
and application administration. For example, the Windows 2003 Server
and SQL DB would be handled by the system admins. The application
admin would admin Project Server and PWA and would maintain a close
relationship with the system admins, to include, hopefully, the ability
to log into the server in at least a read only mode to see the logs and
settings.

The application admin for Project Server and PWA should know Project
well, but doesn't need to be an expert. They should know project
management very well. The typical responsibilities are:

Collect requirements
Implement the system and changes, including establishing the ERP,
Custom Fields and Outline Codes, Views, and Analyzer Views. Set up
Groups and Categories for security permissions.
Document the system
Admin the system - admin users, ongoing security
etc.

I would say the person should have a good mix of functional experience
with technical experience or a group of technical people he or she can
work with. Functional is probably more important.

Hope this helps.

Mark
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top