You can use attributes to specify how criteria are used for comparisons.
Objective (a choice with predefined values)
Use the Objective to determine whether the goal is to minimize or maximize the criterion. For example, you might want to maximize the strategic value and minimize the cost of development. Typically, you maximize elements with high priorities and minimize elements with low priorities.
Question (a text field)
The Question is displayed in the Prioritize frame when elements are compared. If no question is specified, a standard question is displayed.
The clearer the question is, the easier and faster prioritization is. Write the question positively. For example, for the Strategic value criterion, you might ask, “Which project has higher strategic value?”
Estimate (an Integer or Float attribute)
You can use Estimate attributes to store the ID of the Integer or Float attribute that is used in the Estimate criteria.
For example, in the Projects module, you might have an attribute "Cost of development" that is of the Integer type that can be used to store the development cost for each project in the Projects module.
You can use an Estimate attribute to store the ID of the "Cost of development" integer attribute, and use that Estimate attribute to display the values in a chart. For example, you can plot the strategic value, which is based on pairwise comparisons, on the Y axis, and the cost of development, which is based on estimates, on the X axis.
Type (a choice with predefined values)
Use the Type attribute to determine whether the criterion is private, public, or sum.
Type
Description
Private
Members have individual sets of pairwise comparisons. Members cannot see or edit each other's comparisons.
Public
Members share the same set of pairwise comparisons.
Sum
Sum criteria do not use pairwise comparisons. Instead, priorities are calculated as the sum of the priorities of the children.
Sum criteria calculate the priorities regardless of the objectives of the criteria. If you mix maximize criteria with minimize criteria when you use sum, the results are meaningless.
Note Sum criteria calculate the priorities regardless of the objectives of the criteria. If you mix maximize criteria with minimize criteria when you use sum, the results are meaningless.
The public type is intended for normal use. Use private when you want several members to prioritize the elements in a view for the same criterion (for example, for market surveys). If the Estimate attribute is linked to an attribute, the Type attribute is ineffective. Only private and public criteria (with no estimate specified) are listed in the Prioritize frame.
