Use the Scheduling tab on the Project Properties dialog to define the scheduling attributes, such as the start and finish dates of the project. This data is used when scheduling the project. Schedule all project tasks to begin and end during the project period.
Note: If you use autoschedule, these dates may change according to the resource assignments, task dependencies, and constraints.
Follow these steps:
Defines the project's start date.
Default: The current system date.
Specifies whether or not you want to impose a start date for the project.
Note: You must select this field if you later autoschedule your project from its start date. When selected, autoschedule cannot change the project's start date to accommodate any changes it makes to the start and end dates of the project's tasks, no matter when the first task starts.
Defines the anticipated project completion date. The project's finish date must equal or be beyond the finish date of the last task. This date is used as the finish date for the last task in the CPM Network.
Specifies whether or not you want to impose a finish date for the project.
Note: You must select this field if you later autoschedule your project from its finish date. When selected, autoschedule cannot change the project's end date to accommodate any changes it makes to the start and end dates of the project's tasks, no matter when the last task finishes.
Defines the date that is used as a reference point when performing Earned Value Analysis (EVA) calculations. If you do not enter an as-of date, zero (0) displays in earned value fields such as Actual Cost of Work Performed (ACWP) and Budgeted Cost of Work Performed (BCWP).
Note: When using autoschedule to schedule a project, the As-of date for the project defines the date to include data in time and budget estimates. This date is used in Earned Value Analysis (EVA) calculations, such as Budgeted Cost of Work Scheduled (BCWS) and drives the calculations for costs. ETC for a project is not scheduled on or before the As-of date.
Defines the order in which subprojects are scheduled within a master project. The priority amount that you enter here is used as the default priority for summary tasks. Any lower-level WBS tasks that have been marked as inheriting the priority of its parent assume this priority amount. For example, if the project has a priority of 0 through 9, its tasks are given the highest priority during scheduling. If the project has a priority of 11 through 36, its tasks are given the lowest priority during scheduling.
Default: 10
Values: 0 through 36 (A lower number indicates a higher priority.)
Defines on which dates to base the critical path during CPM calculations.
Default: Current
Values:
Specifies whether you want CPM to calculate the project's critical path separately for each subnet. When cleared, one critical path is calculated for the entire project.
Default: Cleared
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|