Schedule Project

Explanation

This enables the planner to quickly calculate the Critical Path for the Service Project based on the Task Duration and Dependencies. The Critical Path shall be identified as the longest chain of dependent Tasks that determines the Project Planned End Date. The calculation shall determine Planned Start Dates and Planned End Dates by selecting a Base Date, scheduling Tasks using Duration and Dependencies, and rolling up calculated end dates through the hierarchy Project, Request or Request Quotation , Scope, Task.

Calculation

Base Date Selection

The Base Date shall be determined in the following order,

  • Use Project Planned Start Date if available
  • If not, use Project Requested Start Date
  • Else neither is available, use the System Date.
  • Arrange Task

  • Starting from the Base Date, the system shall perform a top-down (forward pass) calculation to determine Task Planned Start and Task Planned End dates.
  • Task scheduling shall consider Task Duration and Task Dependencies
  • Dependencies shall be applied only between Tasks within the same Scope
  • Requests with Status = Closed or Cancelled and Scopes with Status = Closed or Cancelled shall be excluded from recalculation.
  • Tasks with Status = Finished will be used as dependency constraints in calculation to figure out the dates of the successors but shall not have their Planned Dates altered.
  • Actual Dates shall not be used for calculation purposes.

    Planned Start and End Dates

    The system shall roll up Planned End Dates through the hierarchy as follows:

  • Scope Planned End Date = Maximum Planned End Date of eligible Tasks
  • Request Planned End Date = Maximum Planned End Date of eligible Scopes
  • Project Planned End Date = Maximum Planned End Date of eligible Requests
  • For Tasks with multiple predecessors, the Planned Start Date shall be the maximum of all applicable dependency constraints.

    Dependency Handling

  • The system shall support Finish-to-Start (FS) and Start-to-Start (SS) dependencies between Tasks within the same Scope.
  • FS Dependency: A successor Task’s Planned Start Date shall be constrained by the Predecessor Task’s Planned Finish Date.
  • SS Dependency: A successor Task’s Planned Start Date shall be constrained by the Predecessor Task’s Planned Start Date.

    Prerequisites

    A Service Project Should be created with an underlying structure.

    System Effects

    As a result of this activity, the Project will be scheduled along with its underlying structure.