& Construction

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

Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:14
To prioritize the scheduling of certain activities,
00:17
you can set a priority number in Flow Generative Scheduling.
00:20
All activities can have priorities.
00:23
Priority is an arbitrary number relative to the other numbers you select.
00:27
For example,
00:29
an activity with a priority of 100 will be
00:31
prioritized above an activity with a priority of 35.
00:36
Priority goes from minus 1000 to plus 1000 to
00:40
give you plenty of priority numbers to play with.
00:43
By default, all activities start with a priority of zero.
00:50
To easily apply a priority, open the schedule tab.
00:55
Select an activity.
00:58
Open the controls tab.
01:02
Enter a number into the priority value field.
01:08
Remove priorities by selecting the X in the priority value field.
01:14
Priority will apply to an entire hierarchy.
01:17
For example, all the tasks within a sequence will inherit the sequence priority. In
01:23
this example, the CRA sequence has a priority of 150.
01:28
All of the shots within the sequence have inherited the same priority.
01:33
Within the sequence,
01:34
priority can be changed on individual shots
01:37
to prioritize certain shots over others.
01:40
In
01:40
this example,
01:41
the shots in the CRA sequence will be prioritized
01:44
over shots of other sequences with a lower priority.
01:48
While CRA 2 will be prioritized over the other shots in the CRA sequence.
01:57
Priority is used to describe the relative
01:59
importance of different parts of your schedule.
02:02
Priority can be seen as a soft objective, as opposed
02:05
to constraints or dependencies which are more strictly enforced.
02:09
For example, you may be working on a film project with sequences and shots.
02:14
Your client would like to see progress on certain key shots first.
02:19
While you may want to prioritize that certain shots are worked on before others,
02:23
there is no specific time-based constraint
02:26
or any dependency between the sequences.
02:30
In this case,
02:31
you could set these more important shots to have a higher priority than the others.
02:36
In this example,
02:36
a priority of 100 has been added to three shots,
02:40
while others maintain a priority of zero.
02:43
If there is a hard requirement that something should be done
02:46
in a specific order or in a specific time frame,
02:49
you can add constraints.
02:51
For example, instead of wanting to simply see progress on those key shots first,
02:56
your client is putting together a trailer and needs work
02:59
on those shots to be completed by a certain date.
03:02
In this
03:02
scenario, a Finish no later than constraint has been added to three shots.
00:14
To prioritize the scheduling of certain activities,
00:17
you can set a priority number in Flow Generative Scheduling.
00:20
All activities can have priorities.
00:23
Priority is an arbitrary number relative to the other numbers you select.
00:27
For example,
00:29
an activity with a priority of 100 will be
00:31
prioritized above an activity with a priority of 35.
00:36
Priority goes from minus 1000 to plus 1000 to
00:40
give you plenty of priority numbers to play with.
00:43
By default, all activities start with a priority of zero.
00:50
To easily apply a priority, open the schedule tab.
00:55
Select an activity.
00:58
Open the controls tab.
01:02
Enter a number into the priority value field.
01:08
Remove priorities by selecting the X in the priority value field.
01:14
Priority will apply to an entire hierarchy.
01:17
For example, all the tasks within a sequence will inherit the sequence priority. In
01:23
this example, the CRA sequence has a priority of 150.
01:28
All of the shots within the sequence have inherited the same priority.
01:33
Within the sequence,
01:34
priority can be changed on individual shots
01:37
to prioritize certain shots over others.
01:40
In
01:40
this example,
01:41
the shots in the CRA sequence will be prioritized
01:44
over shots of other sequences with a lower priority.
01:48
While CRA 2 will be prioritized over the other shots in the CRA sequence.
01:57
Priority is used to describe the relative
01:59
importance of different parts of your schedule.
02:02
Priority can be seen as a soft objective, as opposed
02:05
to constraints or dependencies which are more strictly enforced.
02:09
For example, you may be working on a film project with sequences and shots.
02:14
Your client would like to see progress on certain key shots first.
02:19
While you may want to prioritize that certain shots are worked on before others,
02:23
there is no specific time-based constraint
02:26
or any dependency between the sequences.
02:30
In this case,
02:31
you could set these more important shots to have a higher priority than the others.
02:36
In this example,
02:36
a priority of 100 has been added to three shots,
02:40
while others maintain a priority of zero.
02:43
If there is a hard requirement that something should be done
02:46
in a specific order or in a specific time frame,
02:49
you can add constraints.
02:51
For example, instead of wanting to simply see progress on those key shots first,
02:56
your client is putting together a trailer and needs work
02:59
on those shots to be completed by a certain date.
03:02
In this
03:02
scenario, a Finish no later than constraint has been added to three shots.
To prioritize the scheduling of certain activities, you can set a priority number in Flow Generative Scheduling.
All activities can have priorities.
Priority is an arbitrary number, relative to the other numbers you select. For example, an activity with a priority of 100 will be prioritized above an activity with a priority of 35.
Priority goes from -1000 to +1000, to give you plenty of priority numbers to play with. By default, all activities start with a priority of 0.
To easily apply a priority:
Remove priorities by selecting the X in the Priority value field.
Priority will apply to an entire hierarchy. For example, all the tasks within a sequence will inherit the sequence priority. In the example below, the CRA sequence has a priority of 150. All of the shots within the sequence have inherited the same priority.
Within the sequence, priority can be changed on individual shots to prioritize certain shots over others. In this same example, the shots in the CRA sequence will be prioritized over the shots of other sequences with a lower priority, while CRA_0002 will be prioritized over the other shots in the CRA sequence.
Priority is used to describe the relative importance of different parts of your schedule.
Priority can be seen as a soft objective, as opposed to constraints or dependencies, which are more strictly enforced.
For example, you may be working on a film project with sequences and shots. Your client would like to see progress on certain key shots first.
While you may want to prioritize that certain shots are worked on before others, there is no specific time-based constraints or any dependency between the sequences. In this case, you could set these more important shots to have a higher priority than the others. In this example, a priority of 100 has been added to 3 shots, while others maintain a priority of 0.
If there is a hard requirement that something should be done in a specific order or in a specific time frame, you can add constraints.
For example, instead of wanting to simply see progress on those key shots first, your client is putting together a trailer and needs work on those shots to be completed by a certain date. In this scenario, a Finish no later than constraint has been added to three shots.