Viewing Matrices in Portfolio Optimizer
Projects can contain matrices that Portfolio Managers can view and edit using Portfolio Optimizer. Intersections within a matrix are converted to metrics that are viewable as columns within Portfolio Optimizer for each project within a portfolio or a scenario that contains the matrix. The matrix configuration and definition determines if a matrix is available to Portfolio Optimizer and how the data in the matrix is converted into columns that are viewable and editable within Portfolio Optimizer.
The following sections provide examples of potential matrix configurations and the resulting metrics available within Portfolio Optimizer.
Example 1 - Single Unique Column
Consider the following matrix definition that contains one unique metric.
| Name | Category | Data Type | Is Active | Unique |
|---|---|---|---|---|
| Year | Financial | Date | Yes | Yes |
| Cost | Financial | Number | Yes | |
| Sales | Financial | Number | Yes |
This matrix is associated with a process model and completed in a project. Within that project, the matrix within the project is completed as follows:
|
*Year |
Cost |
Sales |
|---|---|---|
| 2014 | 200 | 50 |
| 2015 | 300 | 100 |
| 2016 | 150 | 150 |
* The Year metric is set as unique in the matrix configuration.
When projects that contain this matrix are viewed in Portfolio Optimizer, a column is available for each year for each metric in the matrix, as Year is set to unique:
- 2014 Cost
- 2014 Sales
- 2015 Cost
- 2015 Sales
- 2016 Cost
- 2016 Sales
Example 2 - Multiple Unique Columns
Consider the following matrix definition that contains two unique metrics.
| Name | Category | Data Type | Is Active | Unique | Unique Order |
|---|---|---|---|---|---|
| Year | Financial | Date | Yes | Yes | 1 |
| Region | Financial | List | Yes | Yes | 2 |
| Cost | Financial | Number | Yes | ||
| Sales | Financial | Number | Yes |
This matrix is associated with a process model and completed in a project. Within that project, the matrix is completed as follows:
|
*Year |
*Region |
Cost |
Sales |
|---|---|---|---|
| 2014 | NorthAmer | 200 | 50 |
| 2014 | Europe | 150 | 50 |
| 2015 | NorthAmer | 300 | 100 |
| 2015 | Europe | 150 | 150 |
* The Year metric and the Region metric are set as unique in the matrix configuration.
When projects that contain this matrix are viewed in Portfolio Optimizer, a column is available for each Year/Region combination for each metric in the matrix, as Year and Region are set to unique:
- 2014 NorthAmer Cost
- 2014 NorthAmer Sales
- 2015 Europe Cost
- 2015 Europe Sales
In this example, if the Unique Order in the matrix configuration is reversed, and the Current metric is set to 1 and the Year set to 2, the columns in Portfolio Optimizer would be Current 2014 Cost, Current 2014 Sales, and so on.
Example 3 - Same Matrix Used in Multiple Projects
Consider the following matrix definition:
| Name | Category | Data Type | Is Active | Unique | Unique Order |
|---|---|---|---|---|---|
| Year | Financial | Date | Yes | Yes | 1 |
| Region | Financial | List | Yes | Yes | 2 |
| Cost | Financial | Number | Yes | ||
| Sales | Financial | Number | Yes |
This matrix is associated with a process model and completed in multiple projects. Within those projects, the matrix is completed as follows:
Matrix in Project A
|
Same Matrix in Project B
|
|||||||||||||||||||||||||||||||||||||||||
|
* The Year metric and the Region metric are set as unique in the matrix configuration. |
||||||||||||||||||||||||||||||||||||||||||
As in Example 2, when multiple projects containing the matrix above are viewed in Portfolio Optimizer, a column is available for each Year/Region metric combination for each metric, as Year and Region are set to unique. Portfolio Optimizer includes the metrics formed by the unique combination across both projects, but does not duplicate a metric combination that is available in both projects. The following columns are available in Portfolio Optimizer if both these projects are viewed:
- 2014 NoAmer Cost
- 2014 NoAmer Sales
- 2015 Europe Cost
- 2015 Europe Sales
- 2016 NoAmer Cost
- 2016 NoAmer Sales
- 2016 Europe Cost
- 2016 Europe Sales
Example 4 - Relative Date Column Names
Consider the following matrix definition, where the Relative Year is a number metric defined as a year that is relative to the project start date.
| Name | Category | Data Type | Is Active | Unique | Unique Order |
|---|---|---|---|---|---|
| Relative Year* | Financial | Number | Yes | Yes | 1 |
| Revenue | Financial | Number | Yes |
* The Relative Year metric is unique in the matrix configuration.
This matrix is associated with a process model and completed in a project whose project start date is June 2014. June 2014 is the anchor date and other entries for the relative year are relative, either positively or negatively to that date. For example, a relative year entry of -1 equals June 2013, and a relative date of 1 equals June 2015.
|
*Relative Year |
Revenue |
|---|---|
| -1 | 200 |
| 0 | 300 |
| 1 | 150 |
When project that contain this matrix are viewed in Portfolio Optimizer, a column is available for each Year for each metric in the matrix that reflects the offset from the project start date. These columns are useful for projection analysis. In addition, a column is available for each actual date based on the anchor date.
- Year -1 Revenue
- Year 0 Revenue
- Year 1 Revenue
- 2013 Revenue
- 2014 Revenue
- 2015 Revenue
When using the year offset columns, note that the actual years those columns represent can be different across projects. For example, Year 1 maybe 2014 in one project and 2016 in another.
In addition, if multiple projects use the matrix, specific columns are generated for each Year for each metric in the matrix, that shows an actual date based on the anchor date.
Matrix in Project A
|
Same Matrix in Project B
|
|||||||||||||||||
|
* Project A's start date is June 2014. Project B's start date is June 2015. |
||||||||||||||||||
When projects that contain this matrix are viewed in Portfolio Optimizer, a column is available for each Year for each metric in the matrix. The column names reflect the offset from the project creation date. Use these generic columns for analysis such as projections year over year.
- 2013 Revenue - Generated from Project A's -1 Relative Year matrix entry.
- 2014 Revenue - Generated from Project A's 0 Relative Year matrix entry.
- 2015 Revenue - Generated from Project A's 1 Relative Year matrix entry and Project B's 0 Relative Year matrix entry.
- 2016 Revenue - Generated from Project B's 1 Relative Year matrix entry.
|
Notes:
|