Use this page to edit schedule steps.

If the checkboxes next to each schedule step on the Schedule View page were used, those steps will be highlighted. However, it will still be possible to edit other steps in the schedule.

The following fields can be edited per schedule step:

• Task Number: Changing the task number of a step will re-arrange the order of the steps. It may cause others to be renumbered as well. For example if Step #30 (of 30 sequentially numbered steps) is changed to #5, then Step #5 will become Step #6, Step #6 will become Step #7 and so on.
  
  
• Description: Input the description of the schedule step.
  
  
• CT: Check this box if the step is a critical task.
  
  
• MS: Check this box if the step is a milestone.
  
  
• Priority: Priority: Select an option from the pull-down menu. The task priority is used to indicate task importance and sort order in reports.
  
  
• Start Date: Input a start date for the step (format: mm/dd/yyyy) or click the calendar icon to choose one.
  
  
• Duration: Input a duration for the step (in days).
• Due Date: Input a due date for the step (format: mm/dd/yyyy) or click the calendar icon to choose one.
  
  Note: You only need to input 2 out of 3 criteria from above (start date, duration, due date) and it will calculate the 3rd.
  
  Note: Editing the Start Date of a task will shift it forward or backward, keeping Duration fixed.
  
  Note: Editing the Duration or Due Date of a task will not shift the task forward or backward, but it will extend or lengthen the task.
  
  
• %: Input the percent complete for the step. Note: This will only appear if the Percent Complete Type is manager inputted data.
  
  
• Subtask: To add subtasks to the step, click the Set link in this column. This will refresh the window with the number of subtask entries requested.
  
  

  The checkbox in the Subtask column is used to synchronize the main task with its subtasks. Synchronized main tasks will assume the properties of the subtasks for: start date, due date, percent complete, assigned users, and estimated and actual time. If a main task is not synchronized it can have separate and different data than its subtasks. Main tasks can be synchronized and un-synchronized throughout the duration of a project.
  
  

• Users: To add users to the step, click the Set link in this column. This will launch a popup window. Note: If subtasks are being used, users must be added to the subtasks, and not the main task.
  
  
• Total Estimated Duration of Step: Data cannot be input into this field. The field simply displays the estimated hours added on the step. Adding estimated hours to a step is done when users are assigned to the schedule step.
  
  
• Dependencies: To make the step dependent on another step, click the Set link in this column. This will launch a popup window.
  
  
• Notes: To add notes to the step click the plus icon. This will launch a popup window.

When finished, click the Save Changes button. This will refresh the page to the Schedule View page.

Editing Subtasks

Subtasks are associated with specific main tasks. The Task Numbers for subtasks are given extensions of the main step's task number, i.e. 1.1, 1.2, 1.3, etc. When you choose to edit subtasks, the page will refresh with the subtask fields displayed underneath the main task.

Note: When the subtasks are synchronized with the main task the earliest start date of the subtasks and the latest end date of the subtasks will automatically become the start and due dates of the main task.

The system supports an infinite number of levels for tasks, therefore it is possible to have subtasks under subtasks.

Note: If the Start Date and/or Due Date of any subtask is earlier or later than the Project Start Date and Delivery Date, the system will prompt you. You will be given the option of modifying the Project Start Date and Delivery Dates accordingly.

User Assignment/Adding Users to Schedule Steps

Adding users to a task and subtask is done the exact same way.

On the popup for adding users to a particular task, you will see the following:

• A list of all users assigned to the project.
  
  
• An Availability column which displays the percent available and hours available. Note: Availability numbers can only be provided if a Start Date and Due Date have been input for the task.
  
  
• An Assign column for determining who will be assigned to the task.
  
  
• A Work Type column for selecting the work type each user will be doing. If Default Work Types are set for each user (in the User system) the system will default to those choices.
  
  
• An Estimated Hours column for inputting the number of estimated hours for each user on the task.
  
  
• An Actual Hours column which displays the actual hours worked on the task (up to this point) based on timesheet entries.

When finished, click the Submit Entries button to add users to the task. The popup will close, and you will be returned to the Edit Schedule Steps page. You will see the number of users appear in the appropriate place, along with estimated hours, if any were included.

On this page it is also possible to modify the list of project members, by clicking the add/remove project members link.

Dependencies

In order to set dependencies for a task, the task must already have a Description, Start Date, and Due Date. Clicking the Set link in the Dependencies column will launch a popup window.

Vertabase only supports one type of dependency, which is called an FS dependency. It states that Step B cannot start before Step A is finished. The following functional logic issues are important:

1. If Step A is not completed before the Start Date of Step B, the system does not automatically push the Start Date of Step B forward.
   
   
2. If the End Date of Step A is edited past the Start Date of Step B, you will be prompted regarding the dependency. The prompt will ask if you wish to push the Start Date of Step B forward.
   
   
3. If the End Date of Step A is moved back, the system will not move the Start Date of Step B back as well, unless the Start Date of Step B was previously pushed forward due to a dependency shift. The Start Date of Step B will never move back beyond the End Date of Step A as well as its original start date.
   
   
4. If the Start Date of Step B is edited and set to a date earlier than the End Date of Step A, the system will prompt you with an error message that this is not allowed due to the dependency.
   
   
5. If the End Date of Step A is moved forward and shifts Step B forward due to the dependency, the Subtasks of Step B may shift as well. The Subtasks of Step B will shift if their Start Dates are earlier than the new Start Date of Step B.

Note: If Step A is not completed before the start date of Step B, the system does not push the start date of Step B forward. However, if the end date of Step A is edited, such that it goes past the start date of Step B, the start date of Step B will be pushed forward.

The popup window will display all tasks and subtasks that the current task (i.e. the one you are working on) can be dependent on. To set a dependency, use the checkboxes next to the task descriptions and click the Submit button.

Shifting Tasks

Schedules can be shifted in two ways:

1. By a new start date
2. By X number of days

Both ways allow you to shift backwards and forwards (so you can push or pull the schedule).

To shift the entire schedule simply input a new start date or a number of days to shift by and click either of the GO buttons. This will prompt you to make sure you want to shift the entire schedule. Click OK. Alternatively, you can check off the checkboxes in the final column of the schedule (all of them or a few of them) and shift only those tasks selected.

Global shifting will take dependencies into account (in the same way as editing a task). When you shift a task that has dependent tasks, the system will ask whether or not you want to shift the dependencies as well. It is possible to cancel the shifting at that time, but it will only impact the tasks related to the dependencies. Therefore if you are shifting two tasks, and one has a dependency and you click cancel to avoid shifting that dependency, the first task (and the dependent task) will not move forward, but the second, unrelated task will be pushed forward.