& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:14
A constraint is a time-based limitation used
00:17
to describe when work can or should occur.
00:20
An activity in Flow Generative Scheduling is a task, milestone,
00:24
or summary such as a shot, asset, or sequence.
00:28
All activities in Flow Generative Scheduling can have constraints.
00:33
To easily apply a constraint, first, open the schedule tab.
00:40
Next, select an activity.
00:43
Now open the controls tab.
00:48
Select add a constraint and choose a constraint from the list.
00:53
When the generate button is selected,
00:55
the newly set constraints will be taken
00:57
into consideration in the newly output schedule.
01:02
Constraints can be used to enforce that work must
01:05
start as soon or as late as possible,
01:07
start or finish on a specific date,
01:11
start no earlier or later than a specific date, and
01:14
finish no earlier or later than a specific date.
01:17
The types of available constraints depend on the type of activity
01:21
and what other constraints have been applied to the same activity.
01:24
Let's take a look at an example. Lowlands is a film project with sequences and shots.
01:30
DRV is a sequence and DRV 2 is a shot.
01:35
To complete the shot
01:36
DRV 2, 10 different tasks need to be accomplished including match move, layout,
01:43
animation, and lighting.
01:44
So far, no constraints have been applied to this schedule.
01:48
Any one of the tasks within DRV 2 can have any constraint applied.
01:53
Going up
01:54
one level constraints can also be applied to the shot. Constraints applied
01:58
to this shot will be applied to everything in the shot's hierarchy,
02:02
which in this case is the 10 displayed tasks.
02:06
While the individual tasks have eight available constraints that can be applied.
02:10
the shot only has four. Going up two more
02:13
levels through the sequence to the project level,
02:16
only two possible constraints are available for the project as a whole.
02:20
While tasks, milestones and summaries all have constraints,
02:25
not all types of constraints are relevant to each type of activity.
02:29
Some constraints can contradict others. Constraints may not be available
02:34
if an activity already has contradictory constraints applied.
02:38
For example, we can set a constraint on the DRV sequence.
02:42
We can choose to add a constraint to start no earlier than November 4th.
02:46
If we want to add an additional constraint,
02:49
the only option will be to finish no later than a certain date.
02:53
The add a constraint button will be grayed out when
02:56
no further constraints can be applied to the activity.
02:59
Select the garbage can icon to the right of
03:01
the constraint to remove it from the activity.
03:04
Instead of setting the start and finish constraints,
03:07
I can choose as soon as possible.
03:10
Once this
03:10
constraint is applied, no further constraints will be available.
03:14
The as soon as possible constraint is an example of an exclusive constraint.
03:19
Exclusive constraints cannot be combined with other constraints.
03:23
Here, you can see which constraints are exclusive or not.
03:30
When a constraint has been applied to an activity,
03:33
it will be visible in the activity list in the schedule tab under constraints.
03:41
It's possible to apply infeasible constraints.
03:44
An infeasible constraint means that the constraint applied
03:47
to their activity is not possible to do
03:50
when you try to apply an infeasible constraint. The constraint will appear red.
03:54
In this example,
03:56
I have a Matchmove task selected and want to
03:58
set it to finish no later than November 15th.
04:01
This constraint is
04:02
not possible, since in this playground,
04:05
the scheduled data was imported to have a start date of November 18th.
04:10
There are two tasks on which the Matchmove task is dependent, with a
04:14
duration of three days each occurring simultaneously.
04:18
With a project start date of Monday,
04:20
November 18th and three working days required to complete the upstream
04:24
dependencies,
04:25
the earliest start date for the match move task is Thursday, November 21st.
04:30
The match move task will take three days to
04:32
complete. Assuming Saturday and Sunday are non working days,
04:36
the earliest finish date for this task is Monday, November 25th.
04:41
All finish dates prior to November 25th appear red, as they are infeasible.
04:47
As you add more constraints to a schedule,
04:49
some can become infeasible to enforce. The filter menu makes
04:53
it easy to locate activities with this type of constrain. To
04:57
find activities with infeasible constraints, in the schedule tab open the
05:02
filter menu. From the constraint section select Has infeasible constraints.
05:07
The Gantt chart will update to display
05:09
only the activities with infeasible constraints.
05:12
Infeasible constraints will appear red.
05:15
The activity list will display a warning
05:17
next to the activity with infeasible constraints.
05:23
Locked activities happen when a schedule is imported
05:26
with activities that start in the past.
05:28
Any activities that are done will be locked and won't be editable.
05:32
Locked activities happen when a schedule is imported with activities
05:36
that start in the past or end in the past.
05:40
Any activities that are locked won't be editable.
05:43
An example of this is an asset containing
05:45
tasks that were already completed in the past.
05:48
A locked activity will display with diagonal lines in the Gantt chart.
05:52
Partially locked activities occur when a schedule is imported with
05:56
activities that start in the past and some of
05:59
the activities in the same hierarchy are completed,
06:02
while others are not.
06:04
An example of this is an asset containing tasks that are already completed and
06:09
other tasks that have not yet been started and still need to be scheduled.
06:13
A lock icon appears in the activity list next to the completed tasks.
06:19
An activity can be partially locked and have infeasible constraints applied.
06:24
In these scenarios, the Gantt chart will display in red with diagonal lines.
00:14
A constraint is a time-based limitation used
00:17
to describe when work can or should occur.
00:20
An activity in Flow Generative Scheduling is a task, milestone,
00:24
or summary such as a shot, asset, or sequence.
00:28
All activities in Flow Generative Scheduling can have constraints.
00:33
To easily apply a constraint, first, open the schedule tab.
00:40
Next, select an activity.
00:43
Now open the controls tab.
00:48
Select add a constraint and choose a constraint from the list.
00:53
When the generate button is selected,
00:55
the newly set constraints will be taken
00:57
into consideration in the newly output schedule.
01:02
Constraints can be used to enforce that work must
01:05
start as soon or as late as possible,
01:07
start or finish on a specific date,
01:11
start no earlier or later than a specific date, and
01:14
finish no earlier or later than a specific date.
01:17
The types of available constraints depend on the type of activity
01:21
and what other constraints have been applied to the same activity.
01:24
Let's take a look at an example. Lowlands is a film project with sequences and shots.
01:30
DRV is a sequence and DRV 2 is a shot.
01:35
To complete the shot
01:36
DRV 2, 10 different tasks need to be accomplished including match move, layout,
01:43
animation, and lighting.
01:44
So far, no constraints have been applied to this schedule.
01:48
Any one of the tasks within DRV 2 can have any constraint applied.
01:53
Going up
01:54
one level constraints can also be applied to the shot. Constraints applied
01:58
to this shot will be applied to everything in the shot's hierarchy,
02:02
which in this case is the 10 displayed tasks.
02:06
While the individual tasks have eight available constraints that can be applied.
02:10
the shot only has four. Going up two more
02:13
levels through the sequence to the project level,
02:16
only two possible constraints are available for the project as a whole.
02:20
While tasks, milestones and summaries all have constraints,
02:25
not all types of constraints are relevant to each type of activity.
02:29
Some constraints can contradict others. Constraints may not be available
02:34
if an activity already has contradictory constraints applied.
02:38
For example, we can set a constraint on the DRV sequence.
02:42
We can choose to add a constraint to start no earlier than November 4th.
02:46
If we want to add an additional constraint,
02:49
the only option will be to finish no later than a certain date.
02:53
The add a constraint button will be grayed out when
02:56
no further constraints can be applied to the activity.
02:59
Select the garbage can icon to the right of
03:01
the constraint to remove it from the activity.
03:04
Instead of setting the start and finish constraints,
03:07
I can choose as soon as possible.
03:10
Once this
03:10
constraint is applied, no further constraints will be available.
03:14
The as soon as possible constraint is an example of an exclusive constraint.
03:19
Exclusive constraints cannot be combined with other constraints.
03:23
Here, you can see which constraints are exclusive or not.
03:30
When a constraint has been applied to an activity,
03:33
it will be visible in the activity list in the schedule tab under constraints.
03:41
It's possible to apply infeasible constraints.
03:44
An infeasible constraint means that the constraint applied
03:47
to their activity is not possible to do
03:50
when you try to apply an infeasible constraint. The constraint will appear red.
03:54
In this example,
03:56
I have a Matchmove task selected and want to
03:58
set it to finish no later than November 15th.
04:01
This constraint is
04:02
not possible, since in this playground,
04:05
the scheduled data was imported to have a start date of November 18th.
04:10
There are two tasks on which the Matchmove task is dependent, with a
04:14
duration of three days each occurring simultaneously.
04:18
With a project start date of Monday,
04:20
November 18th and three working days required to complete the upstream
04:24
dependencies,
04:25
the earliest start date for the match move task is Thursday, November 21st.
04:30
The match move task will take three days to
04:32
complete. Assuming Saturday and Sunday are non working days,
04:36
the earliest finish date for this task is Monday, November 25th.
04:41
All finish dates prior to November 25th appear red, as they are infeasible.
04:47
As you add more constraints to a schedule,
04:49
some can become infeasible to enforce. The filter menu makes
04:53
it easy to locate activities with this type of constrain. To
04:57
find activities with infeasible constraints, in the schedule tab open the
05:02
filter menu. From the constraint section select Has infeasible constraints.
05:07
The Gantt chart will update to display
05:09
only the activities with infeasible constraints.
05:12
Infeasible constraints will appear red.
05:15
The activity list will display a warning
05:17
next to the activity with infeasible constraints.
05:23
Locked activities happen when a schedule is imported
05:26
with activities that start in the past.
05:28
Any activities that are done will be locked and won't be editable.
05:32
Locked activities happen when a schedule is imported with activities
05:36
that start in the past or end in the past.
05:40
Any activities that are locked won't be editable.
05:43
An example of this is an asset containing
05:45
tasks that were already completed in the past.
05:48
A locked activity will display with diagonal lines in the Gantt chart.
05:52
Partially locked activities occur when a schedule is imported with
05:56
activities that start in the past and some of
05:59
the activities in the same hierarchy are completed,
06:02
while others are not.
06:04
An example of this is an asset containing tasks that are already completed and
06:09
other tasks that have not yet been started and still need to be scheduled.
06:13
A lock icon appears in the activity list next to the completed tasks.
06:19
An activity can be partially locked and have infeasible constraints applied.
06:24
In these scenarios, the Gantt chart will display in red with diagonal lines.
A constraint is a time-based limitation used to describe when work can or should occur.
An activity in Flow Generative Scheduling is a task, milestone, or summary, such as a shot, asset, or sequence.
All activities in Flow Generative Scheduling can have constraints.
To easily apply a constraint:
When the Generate button is selected, the newly set constraints will be taken into consideration in the newly output schedule.
Constraints can be used to enforce that work must:
The types of available constraints depend on the type of activity, and what other constraints have been applied to the same activity.
Let's take a look at an example.
Lowlands is a film project with sequences and shots. DRV is a sequence, and DRV_0002 is a shot.
To complete the shot DRV_0002, 10 different tasks need to be accomplished, including matchmove, layout, animation, and lighting.
So far, no constraints have been applied to this schedule. Any one of the tasks within DRV_0002 can have any constraint applied.
Going up one level, constraints can also be applied to the shot. Constraints applied to this shot will be applied to everything in the shot’s hierarchy, which in this case is the 10 displayed tasks.
While the individual tasks have 8 available constraints that can be applied, the shot only has 4.
Going up two more levels through the sequence to the project-level, only 2 possible constraints are available for the project as whole.
While tasks, milestones, and summaries can all have constraints, not all types of constraints are relevant to each type of activity. Some constraints can contradict others. Constraints may not be available if an activity already has contradictory constraints applied.
For example, we can set a constraint on the DRV sequence.
We can choose to add a constraint to start no earlier than November 4. If we want to add an additional constraint, the only option will be to finish no later than a certain date.
Select the garbage can icon to the right of the constraint to remove it from the activity.
The + Add a constraint button will be greyed out when no further constraints can be applied to the activity.
Instead of setting the start and finish constraints, I can choose As soon as possible.
Once this constraint is applied, no further constraints will be available.
The As soon as possible constraint is an example of an exclusive constraint. Exclusive constraints cannot be combined with other constraints. See the chart below for more details on which constraints are exclusive.
When a constraint has been applied to an activity, it will be visible in the activity list in the Schedule tab under Constraints.
It's possible to apply infeasible constraints. An infeasible constraint means that the constraint applied to that activity is not possible to do.
When you try to apply an infeasible constraint, the constraint will appear red.
In the example below, I have a matchmove task selected and want to set it to finish no later than November 15.
As you add more constraints to a schedule, some can become infeasible to enforce. The Filter menu makes it easy to locate activities with this type of constraints.
To find activities with infeasible constraints:
The Gantt chart will update to display only the activities with infeasible constraints. Infeasible constraints will appear red. The activity list will display a warning next to the activity with infeasible constraints.
Locked activities happen when a schedule is imported with activities that start in the past. Any activities that are done will be locked and won't be editable. An example of this is an asset containing tasks that were already completed in the past.
A locked activity will display with diagonal lines on the Gantt chart.
Partially locked activities occur when a schedule is imported with activities that start in the past, and some of the activities in the same hierarchy are completed, while others are not.
An example of this is an asset containing some tasks that are already completed, and other tasks that have not been started and still need to be scheduled.
In the example above, one art and one modeling task have been completed on the PROP_IceCreamCone asset, while one modeling, and two texturing tasks still need to be scheduled.
A lock icon appears in the activity list next to the completed tasks.
An activity can be partially locked and have infeasible constraints applied. In these scenarios, the Gantt chart will display in red and with diagonal lines.