Work Center Constraints

Internal Table Name: AggregateWorkCenterConstraints

Work Center Constraints behave as count constraints, similar to Production Count Constraints. These act as "number of constraints”, enabling you to limit the number of work centers used within a model structure.

Expression

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: ExpressionName

Type: Short Text (100)

This is an optional name for the Work Center Constraint. You can then use the Work Center Constraint in:

• an Expression Constraint by specifying the Expression for either the Expression 1 or Expression 2 value. This enables you to combine constraints.
• an Expression Based Cost by using this value in the Expression field. This enables you to defined fixed and variable cost components that are incurred as a result of the constraint.

Period

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: PeriodName

Type: Short Text (50)

One of (ALL_Periods) (All), (ALL_Periods) (Each), period name, period group.

This field allows you to select a specific period for the work center requirement, a period group, or the entire horizon. In multi-period models, once a work center has been “opened”, it cannot be “closed”. This field is not required; however if you are running a multi-period model, Network Optimization will consider the entire model horizon if left blank.

In a multi-period model, if you select no value for Period, it will behave the same as if you select (ALL_Periods) (All) and apply the constraint across the planning horizon. In order to ensure the correct behavior, Coupa recommends that you select the specific period or, when using (ALL_Periods) or another period filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full horizon/group
• (Each) to apply the constraint per period

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Work Center

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: WorkCenterName

Type: Short Text (100)

One of (ALL_WorkCenters) (All), (ALL_WorkCenters) (Each), work center name, work center group.

Select the work center to which the constraint applies. This can be a specific work center, a work center group, (ALL_WorkCenters) for all work centers, or blank which behaves the same as selecting (ALL_WorkCenters). If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group
• (Each) to apply the constraint per group member

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Site

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: SiteName

Type: Short Text (100)

One of (ALL_Sites) (All), (ALL_Sites) (Each), site name, site group.

Select the site to which the constraint applies. This can be a specific site, a site group, (ALL_Sites) for all sites, or blank which behaves the same as selecting (ALL_Sites). If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group
• (Each) to apply the constraint per group member

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Constraint Value

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: OpenWorkCentersValue

Type: Number (Long Integer)

Specify the number of work centers. This number is used as a constraint based on the Constraint Type value.

Constraint Type

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: OpenWorkCentersType

Type: Short Text (100)

One of Min, Max, Fixed, Define.

Specify whether the constraint Constraint Value represents:

• Min – The minimum number of sites that must be used.
• Max – The maximum number of sites that can be used.
• Fixed – The number of sites that must be used.
• Define – Network Optimization does not use the Constraint Value to satisfy the constraint. Instead, the requirement value is specified in the Expression Constraint. See Considerations for grouped constraints for additional information.

Status

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: AggregateWorkCenterConstraintStatus

Type: Short Text (25)

One of Include, Exclude.

Specify the status of the constraint:

• Include – The constraint is included when the model is run.
• Exclude – The constraint is excluded when the model is run.

Notes

Technology: NO

Table: AggregateWorkCenterConstraints

Internal Name: AggregateWorkCenterConstraintsNotes

Type: Memo

Enter optional descriptive notes about the work center constraint.