locked
How to connect other subsidiaries to project server? RRS feed

  • Question

  • Hi guys,

    At the moment, I've got a main PWA instance on which one department does their work. I think about how to connect other subsidiaries to the project server and search for PROs and CONs. I see two ways how to treat this:

    1. Connect other subsidiaries to our instance

    • PRO: planning ressources globally.
    • CON: work of other subsidiaries is visible for all projectmanagers.

    2. Create new instance for each subsidiary.

    • PRO: work of other subsidiaries is not visible for all projectmanagers.
    • CON: planning ressources globally is not possible.

    Now I search for more PROs and CONs. Do you have experiences with this topic?

    Thank you very much in advance

    Björn


    • Edited by bbod Thursday, January 19, 2012 10:06 AM
    Thursday, January 19, 2012 10:04 AM

Answers

  • Bjorn --
     
    I would personally favor option #1.  The PRO of planning resources globally is a HUGE benefit.  You can work around the CON by using custom Groups and Categories to control which projects each subsidiary can see.  Hope this helps.

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Proposed as answer by Christophe FiessingerMicrosoft employee Thursday, January 19, 2012 6:44 PM
    • Marked as answer by bbod Friday, January 20, 2012 9:08 AM
    • Unmarked as answer by bbod Friday, January 20, 2012 9:08 AM
    • Marked as answer by bbod Monday, January 23, 2012 3:21 PM
    Thursday, January 19, 2012 2:37 PM

All replies

  • Bjorn --
     
    I would personally favor option #1.  The PRO of planning resources globally is a HUGE benefit.  You can work around the CON by using custom Groups and Categories to control which projects each subsidiary can see.  Hope this helps.

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Proposed as answer by Christophe FiessingerMicrosoft employee Thursday, January 19, 2012 6:44 PM
    • Marked as answer by bbod Friday, January 20, 2012 9:08 AM
    • Unmarked as answer by bbod Friday, January 20, 2012 9:08 AM
    • Marked as answer by bbod Monday, January 23, 2012 3:21 PM
    Thursday, January 19, 2012 2:37 PM
  • In addition to Dale's comment, a single instance will enable reporting of all PPM activities very easily. In 2010 you could leverage the "department" feature to segregrate data by sub. The assumptions of a single instance is that all will be using the same methology to track timesheets and status.
    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Thursday, January 19, 2012 6:46 PM
  • Christophe --
     
    Pithy comments, my friend.  I appreciate you following up with these additional thoughts.  How much snow and ice do you have on the ground currently? 

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Thursday, January 19, 2012 7:03 PM
  • Thank you for your answers.

    The problem ist, that e.g. teammembers in subsidiary a have different rights then teammembers in subsidiary b. Using custom groups is very difficult in my opinion, because there is no clear definition. So there could be unclear teammembers groups (teammembers_a - teammembers_x).

    Is there another possibility?

    Friday, January 20, 2012 9:07 AM