Project Server Forum,
I have a client that is concerned that data in the Project Sites is "captive" (i.e. only accessible to someone with a CAL). They have existing Sharepoint sites that are currently used for Project Management information--and widely accessible to employees.
These two things (i.e. Project Sites and native Sharepoint Sites) seem to live in two different worlds--having a wall between them. (I do understand that Project Sites can share some things (e.g. webparts) with other sites, site collections and farms.
But data movement is more restrictive in the other direction, as you need a CAL to access the Project Site.)
My own view is that--for Project Server to be effective--all operational-level project management information from throughout the enterprise (i.e. even the native Sharepoint sites) needs to get pulled into Project Server. It could be that high-level
information about projects (i.e. strategic-level information) may continue to properly reside in Executive Information Systems (possible fed by Project Server)--and some of these may be native Sharepoint sites.
I am wondering how others have addressed this issue (i.e. how to reconcile existing Sharepoint sites having PM information with the existence of Project Sites--only accessible to those having a CAL). Any case studies, white papers, anecdotal information
will be appreciated.
The central issue, I think, is "where does operational-level project management data live?" Is it only in Project Server? Can some continue to live in native Sharepoint sites? (The answer, undoubtedly, is "only in Project Server"--but I
want to see what creative ideas others have implemented to deal with this issue.)
Ed
Dr. Edward M. Hanna, PMP President Data Express, Inc. Irvine, CA emhanna@sbcglobal.net
