none
Commit a Portfolio Analysis - Does it affect resource availability for your next analysis? RRS feed

  • Question

  • Hello everyone

    Just a quick question.

    I run a simple portfolio analysis with 3 future projects and 2 speicific roles (2FTEs) within the Resource plan.

    These two roles is the actual availability and I pick to use them on project number 1 which is selected by the analysis.

    Then I commit the portfolio analysis.

    When I start a new portfolio analysis having those 2 speciifc roles in the resource plans of 3 other projects (included in the new analysis) it shows that they are available to use (within specific time periods which are identical to the first analysis) although already commited by the first analysis.

    Is this correct?

    Thanks   

    Friday, August 31, 2012 6:51 AM

Answers

  • Manos,

    The commit action does not do anything other than populate 6 start/finish fields in project server. Hence there is no change in resource status whatsover. 

    What you really need is a process from the point of hitting the commit button to actually "lock" the resources in per the committed portfolio. An example process could be as follows:

    • All proposals are put in with Generic Resources
    • You conduct portfolio analysis and hit the commit button
    • Based your "workflow", or even just by the fact that there is a value in the "committed start date" field, you could then ask your resource managers to replace the generics with named resources
    • again based on your process, these Named resources could be "proposed" or "committed" booking type (not to be confused with commit button above).
    • Having assignments on projects with "committed" booking type is what locks in the capacity for resources.

    Hope that helps.


    Prasanna Adavi, PMP, MCTS http://thinkepm.blogspot.com

    • Marked as answer by Manos Sm Monday, September 3, 2012 7:30 AM
    Friday, August 31, 2012 3:49 PM
    Moderator

All replies

  • Hi,

    What I know of the commit button is that it only saves your selection and can be used with workflows ect.

    Here you can find some more information about what commit does:

    http://technet.microsoft.com/en-us/library/gg597665.aspx

    http://social.technet.microsoft.com/Forums/en-US/projectserver2010general/thread/5fe9eb13-728f-4b53-829b-1902192c8461

    Maybe some others could clarify further.

    Hope it helps.

    Robin Kruithof


    Technical Consultant EPM

    Friday, August 31, 2012 7:26 AM
  • Manos,

    The commit action does not do anything other than populate 6 start/finish fields in project server. Hence there is no change in resource status whatsover. 

    What you really need is a process from the point of hitting the commit button to actually "lock" the resources in per the committed portfolio. An example process could be as follows:

    • All proposals are put in with Generic Resources
    • You conduct portfolio analysis and hit the commit button
    • Based your "workflow", or even just by the fact that there is a value in the "committed start date" field, you could then ask your resource managers to replace the generics with named resources
    • again based on your process, these Named resources could be "proposed" or "committed" booking type (not to be confused with commit button above).
    • Having assignments on projects with "committed" booking type is what locks in the capacity for resources.

    Hope that helps.


    Prasanna Adavi, PMP, MCTS http://thinkepm.blogspot.com

    • Marked as answer by Manos Sm Monday, September 3, 2012 7:30 AM
    Friday, August 31, 2012 3:49 PM
    Moderator
  • Thanks a lot. That makes sense.

    Monday, September 3, 2012 7:30 AM