The Committed Portfolio Selection Decision (Cost) field shows the result of a cost constraint analysis on a project. You can choose Selected, Unselected, Forced-In/Out, or Custom Forced-In/Out.
Data Type Enumerated
Entry Type Calculated
Best Uses By working through a cost constraint analysis as part of a Portfolio Selection Scenario, you can choose which projects to invest in based on the value-to-cost ratio indicated by portfolio-level cost constraints. You can save multiple Portfolio Selection Scenarios, including various models for cost constraints, for further analysis.
After a cost constraint Portfolio Selection Scenario is committed, the selection decision for each project is saved in the Committed Portfolio Selection Decision (Cost) field for each project. The commitment decision is shown as Selected, Unselected, Forced-in, or Forced-out. There might an additional custom value for a Forced-in or Forced-out decision based on a custom lookup table that lists reasons for a Forced-in or Forced-out decision.
You can add the Committed Portfolio Selection Decision (Cost) field to Project Center views, reports, and project field Web Parts for review by project and portfolio stakeholders. By doing this, you and others on the team can see the commitment decision that was made as a result of the cost analysis.
Example As a result of working through the Portfolio Strategy process, you have asked Microsoft Project Server to run a high-level cost constraint analysis on the proposed “Develop SOX-compliant auditing mechanism” project. When you decide to commit to this project, you see that the Committed Portfolio Selection Decision (Cost) field displays “Forced-In” because this project is part of a regulatory requirement.
Remarks In Project Web App you can add this field to a Project Center summary view, for example.
