• Right-click the
Architectural Description or
Service Description that is to own the NPV-1 Acquisition Clusters, point to New, point to Matrix/Table, point to NAF, and then click NPV-1 Acquisition Clusters.
After creating the NPV-1 Acquisition Clusters, Modeler opens a dialog for you to select whether the table shows Organization Responsibilities or Project Categorization.
When you open an NPV-1 Acquisition Clusters, Modeler can generate it as HTML for viewing in your Internet browser, or generate it as a spreadsheet for viewing in Microsoft Excel. To specify how matrices and tables are opened for a model: in the Packages pane, right-click the Model, point to Tools > Options, click Matrix/Table Generation Format, and then select HyperTextMarkupLanguage_HTML or Excel_XLS.
Each time you open an NPV-1 Acquisition Clusters, Modeler generates the product using the latest data from the model.
To change the type of an NPV-1 Acquisition Clusters:
• Right-click the NPV-1 Acquisition Clusters, point to Set, and then click Table Type. From the dialog, select Organization Responsibilities or Project Categorization as required.
Purpose
An NPV-1 Acquisition Clusters can be set up to show Organization Responsibilities or Project Categorization:
In addition, a row is created for each Actual Organization and Actual Post that has project responsibility for an
Actual Project that is found in the analyzed Packages.
• For each Actual Organization or Actual Post, the NPV-1 Acquisition Clusters shows the Actual Project elements for which the Actual Organization or Actual Post is a responsible resource.
For information about setting up this relationship, see the example that follows.
For Project Categorization:
An NPV-1 Acquisition Clusters shows the following elements:
• A row is created for each
Project Type that is found in the analyzed Packages.
In addition, a row is created for each Project Type that is a classifier for an
Actual Project that is found in the analyzed Packages.
• For each Project Type, the NPV-1 Acquisition Clusters shows the Actual Project elements that use that Project Type as a classifier.
Analyzed Packages
For Organizational Responsibilities:
By default, the NPV-1 Acquisition Clusters searches for Actual Organization, Actual Post and Actual Project elements that are contained within the Architectural Description or Service Description that owns the NPV-1 Acquisition Clusters.
To search for Actual Organization, Actual Post and Actual Project elements from other Architectural Description and Service Description packages: right-click the NPV-1 Acquisition Clusters, point to Links, and then click Analyzed Packages. From the Links Editor, select the Architectural Description and Service Description packages from which you want to search for Actual Organization, Actual Post and Actual Project elements.
For Project Categorization:
By default, the NPV-1 Acquisition Clusters searches for Project Type and Actual Project elements that are contained within the Architectural Description or Service Description that owns the NPV-1 Acquisition Clusters.
To search for Project Type and Actual Project elements from other Architectural Description and Service Description packages: right-click the NPV-1 Acquisition Clusters, point to Links, and then click Analyzed Packages. From the Links Editor, select the Architectural Description and Service Description packages from which you want to search for Project Type and Actual Project elements.
Example
For Organizational Responsibilities:
In this example, Architectural Description1 owns NPV-1 Acquisition Clusters1 and contains Actual Organization1 and Actual Post1.
We set up Actual Organization1 to have project responsibility for Actual Project1.
To create this relationship from an Actual Organization: right-click the Actual Organization, point to Links, point to Programme, and then click Project Responsibility.
When generated, NPV-1 Acquisition Clusters1 appears as follows.
From the generated table you can see the following:
• A row has been created for each Actual Organization and Actual Post in Architectural Description1, that is, Actual Organization1 and Actual Post1.
• Actual Organization1 has project responsibility for Actual Project1.
For Project Categorization:
In this example, Architectural Description1 owns NPV-1 Acquisition Clusters1 and contains Project Type1, Project Type2 and Actual Project1. Actual Project1 uses Project Type1 as its classifier.
When generated, NPV-1 Acquisition Clusters1 appears as follows.
From the generated table you can see the following:
• A row has been created for each Project Type in Architectural Description1, that is, Project Type1 and Project Type2.
• Project Type1 is the classifier of Actual Project1.
