## Time constraint MIN

In the property Time constraint MIN, you specify the time for the relationship between this process and the previous process, as given by the Time constraint method.
Time constraint MIN is defined as "not shorter than".

To set Time constraint MIN with an expression, please see this topic.

Format

The time constraint method is specified using the following grammar: <Total move time>

 := | ';' ... := | '/' | '@' (Resource Code) | '#' := ... | ... := | := "+" := "+" := "-" := "-" := Integral value := "S" | "M" |"H" | "D" | "W" := 'M' | 'S0' | ... | 'S9' | 'I0' | ... | 'I9' | 'm' | 's0' | ... | 's9' | 'i0' | ... | 'i9' := Real value

* <...> is a nonterminal symbol and (...) is a terminal symbol.
:= indicates that the notation of the table’s left cell is defined to be the term on the right of :=.
| means “or”.

#### Example

[Integrated Master Editor]
Time constraint
60Separates at least 60 minutes.
3600SSeparates at least 3600 seconds.
60MSeparates at least 60 minutes.
1HSeparates at least 1 hour.
1DSeparates at least 1 day.
1WSeparates at least 1 week.
H1DSeparates at least until the beginning of the next day.
H1D;3HSeparates at least until 3 hours after the beginning of the next day.
1D/MSeparates at least 1 day measured along the working time of the main resource in the next process.
1D/mSeparates at least 1 day measured along the working time of the main resource in the previous process.
1D/S0Separates at least 1 day measured along the working time of the sub resource 0 in the next process.
1D/s0Separates at least 1 day measured along the working time of the sub resource 0 in the previous process.
1D/I0Separates at least 1 day measured along the working time of the setup resource 0 in the next process.
1D/i0Separates at least 1 day measured along the working time of the setup resource 0 in the previous process.
1D/S1Separates at least 1 day measured along the working time of the sub resource 1 in the next process.
1D@R1Separates at least 1 day measured along the working time of the resource R1 in the next process.
#1.5Separates at least the time it takes to produce 1.5 items.
#1.5;1D/M;1DSeparates at least the time it takes to produce 1.5 items + 1 day measured along the working time of the main resource in the next process + 1 day.

If you specify <Relative Notation> with no other description after the <Relative Notation>, it means that the time is not measured along any particular resource's working time. Resource types in capital letters represent "assigned resource in the current process" and those in lower-case letters represent "assigned resource in the previous process".

However, if you specify the time beginning with "H" such as "H1D", it is meaningless to specify a resource.

For <Unit>, "S" stands for seconds, "M" stands for minutes, "H" stands for hours, "D" stands for days, and "W" stands for weeks. Specifying no unit means that the time is in minutes.
"1D" is equal to "24H" and "1W" is equal to "7D".

When "#N" (corresponding to N production quantity of the previous process) is specified for move time, the capacity value in the master data will not be referred to but the value will be calculated based on actually assigned time.

Setting more than one time

Multiple times can be given by separating with either a plus sign, or a semicolon.
The meaning of these two setting methods differs depending on the assignment direction and whether HnD is used.

Using with forward scheduling

H1D+3H means forward H1D, then forward 3H

H1D;3H means forward H1D, then forward 3H

1D+3H means forward the result of adding 1D and 3H

1D;3H means forward H1D, then forward 3H

Using with backward scheduling

H1D+3H means back 3H, then back H1D

H1D;3H means back 3H, then back H1D

1D+3H means back the result of adding 1D and 3H

1D;3H means back 3H, then back 1D

So the plus sign signifies an addition of the times as you might expect. The semicolon signifies that the two times are processes separately. The exception to the rule is where HnD is used, in which case plus sign has the same meaning as the semicolon.

Thus, the plus sign and the semicolon are interpreted differently. When HnD is included, both are processed in the same manner, but the recommended setting is to

use the semicolon when time settings are to be separated by element.

The exception to the rule is where HnD is used, in which case plus sign has the same meaning as the semicolon.

!!DELETE!!

This behavior applies from Ver. 4.3.0 onwards.
For previous behaviors, please see this topic.

Restrictions

1. When using HnD, the assigned positions for operations may differ between forward scheduling and backward scheduling.

For information on Time constraint MAX, please see this topic.