Scheduling policy

Available for edit only in project settings, regardless of whether the scheduling policy can be edited by project managers.

• If you set a default start date, when you schedule a work plan, PPM schedules the entire work plan forward from the date. You can still change the date in the Schedule Work Plan window.
• If you leave this option empty, when you schedule a work plan, PPM schedules the entire work plan forward from the current date. You can still change the date in the Schedule Work Plan window.

This option only works when the project work plan is Active and for In Progress tasks.

If you select this option, when you schedule a work plan, the schedule start dates and scheduled finish dates of In Progress tasks are getting adjusted based on their actual start dates and finish dates as long as the actual dates are specified.

• All resources are available: When you schedule a work plan, PPM only includes the days in the schedule when all resources are present.
• At least 1 resource is available: When you schedule a work plan, PPM only includes the days in the schedule when at least 1 resource is present.
• Include all working days from calendar (ignore resource availability): When you schedule a work plan, PPM includes all the working days in the schedule, regardless of whether there is a resource present on any of the days.

A work plan's critical path is the series of tasks that determines the duration of the project.

The Critical Path Threshold is the amount of slack (the amount of time that a task may be delayed from its start without delaying the project) specified as the threshold for identifying a task as part of the critical path.

Tasks with slack less than or equal to this value are on the critical path. See How PPM calculates task's slack.

The use of a threshold allows the project manager to control the degree of risk tolerated in management of the work plan.

Select how the project progress is calculated.

• Work Plan Progress: PPM shows the project progress based on the progress of the project's work plan.

• Project Field: Project progress is calculated by your custom method.

  Click the Select button to select a project field that indicates the project progress calculated by your custom method. PPM will show the project progress based on the field value.

  You cannot specify the field until the project type is created.

  Only the field that uses the Percentage Text Field validation can be used to define the project progress.

Project Date Conflicts

This warning occurs when the work plan dates extend beyond the project's Planned Start Period or Planned Finish Period. It also occurs when the constraint defined on the task is outside the project's Planned Start Period or Planned Finish Period.

Bring the plan within the project's dates by adjusting dependencies, duration, resources, or any combination thereof, and rescheduling.

In some cases, resolution may involve expanding project-level dates, which should be coordinated with the project financial summary and staffing profile.

Dependency Conflicts

These warnings occur when a predecessor dependency defined for the task could not be honored because other constraints or task information prevents it.

For example, a task may be expected to start on October 10 based on its predecessor relationships, but might have a Start No Later Than constraint defined for October 1st. The task cannot meet both requirements.

Rework the plan to remove the conflicts.

Constraint Inheritance Conflicts

These warnings occur when there is a direct conflict between the constraints defined for a task and its parents, such that only one can be satisfied. Both related tasks are marked.

Rework the plan to remove the conflicts.

If both constraints are valid, you may need to file a project issue.

Resources Could Not Be Scheduled

The scheduler could not identify sufficient available working days for the assigned resources to schedule the task. This warning is evaluated only when the scheduler runs.

This usually occurs when the scheduler attempts to schedule a resource after the resource's end date or before the resource's start date. Check resource information, and if necessary, change the task resource or change task dependencies so that it can occur during the right dates.

Task Constraint Could Not Be Met

This warning occurs when the constraint defined on the task could not be honored because other conflicting information takes precedence.

This usually occurs when using actuals during scheduling and the task's actual start date conflicts with a constraint defined for the task. This may not require explicit resolution.

This warning occurs when the total effort (actual effort + estimated remaining effort) on a task is more or less than the scheduled effort by more than the specified tolerance percentage.

If the scheduled effort differs from the total effort by more than this threshold, a warning indicator is added to the schedule warnings column of the work plan.