You can create dependencies between tasks in the same project or in different projects using the Task Dependencies page. You can view a list of all of the tasks in the current project on the Select Tasks page. The Project field displays the name of the current project.
You can create dependencies between tasks in the same project or between tasks in different projects. You can only create one dependency at a time for a task, but a task can have dependencies to many tasks.
As with task constraints, Autoschedule uses task dependencies to help determine a work sequence for the project. Task dependencies allows you to designate a successor or predecessor task for a task and to indicate the type of relationship you want the tasks to have.
Example
You could indicate that the "Object Design" task must complete one day before the "Object Integration" task can begin. Autoschedule would consider this dependency and any other dependencies and constraints during autoscheduling.
To create task dependencies
The Task Properties page appears.
The Task Dependencies page appears.
The Select Tasks page appears.
The tasks assigned to that project display in the list.
The Task Dependency Properties page appears. The task you selected is identified on this page as the dependent task.
Defines the relationship between the current task and the task you selected. If you want the task you selected to precede the current task, select Predecessor. If you want the task you selected to secede the current task, select Successor.
Values: Predecessor, Successor
Default: Predecessor
Use this field to define the type of relationship you want to have between the two tasks.
Values: Finish-Finish, Finish-Start, Start-Finish, and Start-Start
Default: Finish-Start
Example: If you select predecessor as the relationship and Finish-Start as the type, the predecessor task is scheduled to finish before the successor task starts. Alternatively, if you select successor as the relationship, and Finish-Finish as the type, the successor task is scheduled to finish before the predecessor task finishes.
Identifies the lag period between the two tasks.
Default: 0.00
Example: Assuming a Finish-Start type of relationship, you could create a lag period of 5 days between the finish date of the predecessor task and the start of the successor task.
Use this field to indicate the type of lag you want to exist between the dependent tasks.
Values: Daily or Percent
Default: Daily
Example: If you enter 5 as the lag and daily as the lag type, a lag of 5 days is created. A lag time percent is based on the duration of the predecessor task. For example, if the duration is 100 days, and you enter 20 as the lag and percent as the lag type, for a lag of 20% of 100 days, a lag period of 20 days between the tasks is created.
The Task Dependencies page appears displaying the newly created dependency.
| Copyright © 2010 CA. All rights reserved. | Email CA Technologies about this topic |