Dear all,
I have a couple of questions regarding working with Portfolio
Q1: I still don’t understand what exactly the action "Update Portfolio" does. I tried to invoke it when the schedule of the project included in portfolio has changed, but it did not have any effect, portfolio was still showing old version after I did Update Portfolio =>New version.
Note: Consolidate/Distribute seems to be working as expected.
Q2: When performing resource constant scheduling of an individual project, only Standard Method is available if an option “Consider Portfolio Schedule”, is selected. Why is that?
Q3: When performing resource constant scheduling of an individual project and option “Consider Portfolio Schedule” is selected, then the following behavior is observed:
Resource leveling takes into account portfolio resources, without considering, that this project itself is already a part of ths portfolio, so it “double counts resources”. Example: when one has a portfolio of 2 projects, each consisting of Activity 1 with Resource A, when portfolio scheduling will be done, then in one of the projects Activity 1 will be correctly delayed by resource leveling.
If I now go to any of the projects and perform resource constrained scheduling, with the option “Consider Portfolio Schedule”, then I will see, that the Activity 1 will be delayed yet again, even though it is not needed, because it is already a part of the portfolio, hence total resources of the portfolio already take into account this project.
Did I miss something here?
Evgeny Z,
from my experience, each project in the project portfolio must have unique codes for activities and phases otherwhise Spider gets confused about which activity belongs where. I think the simplest way to change object codes would be to add prefixes or postfixes to the phases/activities (Right click the Code column header and use the Change Values option to add prefix or postfix to the phase/activity code).
[[wysiwyg_imageupload:1943:]]
Vladimir,
Q3: I did not do any comparison and behaviour is quite easy to reproduce:
Spider files are here:
https://drive.google.com/file/d/0B1FBt_G3gCVqUEtteHgyRUY0RWs/edit?usp=sharing
Step 1: Initial resource-leveled portfolio schedule
Step 2: Project 2, resource-leveled taking into account portfolio (you can see, it is delayed)
Q1. Portfolio is updated by changes in the schedules that were already included in project portfolio.
New version means that new version of portfolio is created, but newer project versions are ignored.
Q2. Spider uses special method, not the standard. You may notice that there is no choice for method selection in this case.
Q3. Please check if portfolio was compared with some other version before distributing projects. We recently found an error created recently in this case that soon will be fixed. If it happens without this please send an example.