...
- Add Constr. / Constraint Subdivision: A constraint can be divided into sub-constraints in the Setup Constraint SubdivisionsPartitions (partitions are also sometimes called subdivisions) window. When you execute the Activate Constraint Subdivision command, the system inserts records for each sub-constraint in the selected constraint subdivision. It enters the name of the constraint subdivision in the Add Constr. column and the name of the sub-constraint in the Constraint Subdivision column.
- Condition Threshold: This column is left blank except when the Constr. Type column is set to Percent Above Threshold. For this type, this column supplies the percentage value that will cause the analysis engine to stop. The percentage value is entered as a decimal value (for example, 10% is entered as 0.1).
- Constr. Type: This column contains a drop-down list of the allowed constraint types: Percent Above Threshold, Total, and Weighted Average. These three types are described below:
- Percent Above Threshold: The analysis engine will stop when the constraint value exceeds a threshold value by a certain percentage. The value for the threshold is entered in the Constraint Limit Value column and the percentage value is entered in the Condition Threshold column.
- Total: The analysis engine will stop when the constraint reaches the total amount shown in the Constraint Limit Value column.
- Weighted Average: This type is only used when multiple objectives are selected. It sets the relative weight of each objective against the other objectives.
- Constraint Column: This column contains a drop-down list. The list contains those columns with a check mark in the Is Constraint check box in the Setup Analysis Columns window. The constraint you select for this column is either the objective of the analysis or acts to limit what is considered for inclusion in the work plan by the analysis engine.
- Constraint Limit Value: This column is left blank except when the Constr. Type column is set to Percent Above Threshold or Total. For Percent Above Threshold, this column sets the threshold value that the constraint value must exceed (by a certain percentage) for the analysis engine to stop. For Total, this column supplies the value that will cause the analysis engine to stop.
- Is Objective: A check mark in this column indicates that the selected constraint is the objective of the analysis. You can select more than one objective, but if so the Constr. Type column should be set to Weighted Average, with the objective weights entered in the Objective Coefficients column.
- Objective Coefficient: This column is left blank unless you select multiple objectives. In this case, this column indicates the relative weight of each objective against the others.
- Scenario Year: This column is left blank for a constraint if the constraint will apply across all years of the analysis period. If the constraint will vary by year, then fill this field by right-clicking the pane to display the shortcut menu and select Propagate Years. The system will then create multiple records for the selected constraint, one for each year of the analysis period, and insert the analysis year in this column for each constraint record.
...
- Activate Constraint Subdivisions: This command inserts records for each of the constraint subdivisions into which the selected constraint is subdivided as configured in the the Setup Constraint Subdivisions Partitions window.
- Propagate Years: This command inserts a record for each of the years in the analysis period that is the same as the record you right-clicked (other than year).
- Set to Included MWP Budget: For each of the records selected in the Constraints pane, this command identifies the MWP projects that match the year and constraint partition of the record (and are within the analysis and MWP scope). It then calculates a total cost for these identified projects and inserts the cost in the Constraint Limit Value field of the record.
If the record in the Constraints pane does not include a year, then the command returns an error. For example, say the constraint is on treatment costs for the year 2012 with an "Interstate" functional class partition. The system finds all of the interstate sections included in the analysis scope and then finds all MWP projects within the year 2012 that intersect those sections. It then places the total project costs for those projects in the constraint record.
...
- Activate Constraint Subdivisions: This command inserts records for each of the constraint subdivisions into which the selected constraint is subdivided as configured in the the Setup Constraint Subdivisions Partitions window.