Constraint Summary

Internal Table Name: OptimizationOutputConstraintSummary

This table provides details about the Constraints (regular constraints and Expression Constraints) that were included in the Optimization.

You can control the amount of information populated in the Constraint Summary using the Constraint Summary Output Detail Optimization Option. By default, only major constraints are populated; that is, only Min and Max type constraints are written for Network Optimization. When Infeasibility Diagnosis or Sequential Optimization is run, any violated hard constraints are displayed as well.

Scenario

Table: OptimizationOutputConstraintSummary

Internal Name: Not Applicable (Scenario column not in table)

The scenario for which the output data was generated.

Constraint

Table: OptimizationOutputConstraintSummary

Internal Name: Constraint

This indicates the type of constraint. For example, if you have defined a Flow Constraint, the value will be Flow. Expression Constraints will be shown as Expression.

If you have entered values for constraining fields the Inventory Policies table (such as Max Inventory, Min Inventory and Safety Stock), these will be reflected as records in the Constraint Summary table. The Constraint Names will be MaximumInventory, MinimumInventory and SafetyStock.

Expression

Table: OptimizationOutputConstraintSummary

Internal Name: Expression

This is the Expression Name entered in the constraints tables. If the constraint does not have an Expression Name, you see an Expression Name value such as:

  • AGGFLOWCON_<x> – The source constraint is an unnamed Flow Constraint.
  • AGGINVCON_<x> – The source constraint is an unnamed Inventory Constraint.
  • AGGPRODCON_<x> – The source constraint is an unnamed Production Constraint.
  • AGGEDPCONS_<x> – The source constraint is an unnamed Expression Constraint.

where x is an integer used to uniquely identify the constraint.

Site

Table: OptimizationOutputConstraintSummary

Internal Name: SiteName

This is the Site Name for Inventory Constraints and Production Constraints

Source

Table: OptimizationOutputConstraintSummary

Internal Name: SourceName

This is the Source Site for Flow Constraints.

Destination

Table: OptimizationOutputConstraintSummary

Internal Name: DestinationName

This is the Destination Site for Flow Constraints.

Organization Name

Table: OptimizationOutputConstraintSummary

Internal Name: OrganizationName

The Organization to which the constraint is allocated. When the constraint is associated with Sites that belong to the Organization, the constraint is attributed to the Organization as required.

Product

Table: OptimizationOutputConstraintSummary

Internal Name: ProductName

This is the Product Name for the constraint (all constraint types).

Mode

Table: OptimizationOutputConstraintSummary

Internal Name: ModeName

This is the Mode for Flow Constraints.

Period Name

Table: OptimizationOutputConstraintSummary

Internal Name: PeriodName

This is the Period Name for the constraint (all constraint types).

Period Number

Table: OptimizationOutputConstraintSummary

Internal Name: PeriodNo

This is the Period number for the constraint (all constraint types).

Asset

Table: OptimizationOutputConstraintSummary

Internal Name: AssetName

This is the name of the Transportation Asset for any asset-based constraint. For work center constraints, the Work Center Name is displayed here.

Process

Table: OptimizationOutputConstraintSummary

Internal Name: ProcessName

This is the Process Name for any process-based constraints.

Other

Table: OptimizationOutputConstraintSummary

Internal Name: Other

In the case of Open/Close Relations, this field is populated with the values of “OPEN” or “CLOSED” based on the definition of the constraint.

Range

Table: OptimizationOutputConstraintSummary

Internal Name: Range

When Shelf Life it used, this value represents the age to which the constraint applies.

Constraint Type

Table: OptimizationOutputConstraintSummary

Internal Name: ConstraintTyp

This is the requirement type for the constraint. It will be one of:

  • Min – The value specified in the Constraint Value must be reached.
  • Max – The value specified in the Constraint Value cannot be exceeded.
  • Fixed – The value specified in the Constraint Value must be used.
  • Cond Min – The value specified in the Constraint Value must be reached or none at all.
  • Define – Network Optimization does not use the Constraint Value to satisfy the constraint. This setting can be used when you are nesting Expression Constraints.

Constraint Activity

Table: OptimizationOutputConstraintSummary

Internal Name: ConstraintActivity

This is the activity incurred by the constraint. For example, if you have a Flow constraint with a requirement of 500 using a requirement type of Max, if the solution uses a Flow of 400, the Constraint Activity will be 400. If you have a Flow constraint with a requirement of 1000 using a requirement type of Min, if the solution uses a Flow of 1200, the Constraint Activity will be 1200.

Constraint Slack

Table: OptimizationOutputConstraintSummary

Internal Name: ConstraintSlack

This is the difference between the Constraint Value and the Constraint Activity; that is the amount of the constraint that was not used. For example, if you have a Flow constraint with a requirement of 500 using a requirement type of Max, if the solution uses a Flow of 400, the Constraint Activity will be 400 and the Constraint Slack will be 100. If you have a Flow constraint with a requirement of 1000 using a requirement type of Min, if the solution uses a Flow of 1200, the Constraint Slack will be 200.

Constraint Requirement

Table: OptimizationOutputConstraintSummary

Internal Name: ConstraintRequirement

This is the required value that is defined for the constraint.

Constraint Requirement Deviation

Table: OptimizationOutputConstraintSummary

Internal Name: ConstraintRequirementDeviation

Assume a constraint such as:

Flow >= 100

The Constraint Requirement Deviation is the amount needed to be added to or subtracted from the constraint value. This is either an excess or a deficit.

  • In the case of an excess, this is the amount to be added to the constraint requirement (left hand side of the equation) or alternatively be subtracted from the constraint requirement (right hand side of the equation).
  • In the case of a deficit, this is the amount needed to be subtracted from the constraint value (left hand side of the equation) or alternatively be added to the constraint requirement (right hand side of the equation).

Consider the following two examples:

Constraint Actual Flow Description
Flow <= 100 120 In this case, the Constraint Requirement Deviation is 20 because this is the amount that needs to be subtracted from the flow to satisfy the constraint.
Flow >= 100 70 In this case, the Constraint Requirement Deviation is 30 because this is the amount that needs to be added to the flow to satisfy the constraint.

Suggested Constraint Requirement

Table: OptimizationOutputConstraintSummary

Internal Name: SuggestedConstraintRequirement

When you run Infeasibility Diagnosis, the solver compares the Constraint Activity to the Constraint Requirement. If this results in either a deficit or an excess, the deviation is reported in the Constraint Requirement Deviation. The Suggested Constraint Requirement identifies the suggested value for the Constraint Requirement.

Assume a constraint such as:

Flow <= 100

If the Constraint Activity (the actual flow) is 120, the Constraint Requirement Deviation reports 20 and the Suggested Constraint Requirement reports 120.

Scenario ID

Table: OptimizationOutputConstraintSummary

Internal Name: ScenarioID

The identifier of the scenario for which the output data was generated.

Sub-Scenario ID

Table: OptimizationOutputConstraintSummary

Internal Name: StepNumber

The identifier of the sub-scenario, if applicable, for which the output data was generated.

Last modified: Wednesday May 15, 2024

Is this useful?