Project Task Dependencies

The Project Task Dependencies report displays projects and their inter-project task dependency relationships. This gives you visibility between your project and dependent tasks in other projects. The report displays predecessor and successor dependencies as a diagram, and a detailed list. The diagram displays a maximum of five predecessor and five successor inter-project dependencies. The detailed list does not have this limit and shows all inter-project task dependencies. The report contains project summary and task information, including a dependency schedule stoplight and dependency type. The report also includes a checkmark icon indicating that the task or dependent task is on the critical path.
ccppmop156
The Project Task Dependencies report displays projects and their inter-project task dependency relationships. This gives you visibility between your project and dependent tasks in other projects. The report displays predecessor and successor dependencies as a diagram, and a detailed list. The diagram displays a maximum of five predecessor and five successor inter-project dependencies. The detailed list does not have this limit and shows all inter-project task dependencies. The report contains project summary and task information, including a dependency schedule stoplight and dependency type. The report also includes a checkmark icon indicating that the task or dependent task is on the critical path.
The following image displays the Project Task Dependencies report.
Image displaying the Project Task Dependencies report.
Report Prerequisites
Verify that you have completed the following prerequisites before you run this report:
  • The project must have at least one task or milestone with a dependency to a task or milestone in another project to display in the report.
  • For the project summary section, the project must have budgeted or planned cost that is entered on the financial summary of the project. If the project has a detailed budget or cost plan, then the approved budget amount or cost plan amount for the plan of record displays based on the financial plan type parameter that is selected when running the report.
Report Properties
The following values list the report properties
:
Name
: Project Task Dependencies
Resource ID
: CSK_PRJ_TaskDependencies
Description
: Project Management (PMO Accelerator)
Folder
: CA PPM/Reports/Project Management/Project Task Dependencies
Path
: /ca_ppm/reports/project_management/CSK_PRJ_TaskDependencies
Data Source
: CA PPM Bean Data Source
Report Parameter Options
The following table lists the report parameter options.
Prompt Text
Parameter Name
Type
Input Control Name
Input Control Resource ID
Mandatory
Default Value
Project OBS Type
projectOBSTypeKey_1
Single-select
Query
Project OBS Type
projectOBSTypeKey_1
No
Project OBS Unit
projectOBSUnitKey_1
Single-select
Query
Project OBS Unit
projectOBSUnitKey_1
No
Project Type
projectTypeKey_1
Multiple-select
Query
Project Type
projectTypeKey_1
No
Project Manager
projectManagerKey_1
Multiple-select
Query
Project Manager
projectManagerKey_1
No
Project
projectKey_1
Multiple-select
Query
Project
projectKey_1
No
Project Status
projectStatusKey_1
Multiple-select
Query
Project Status
projectStatusKey_1
No
Work Status
workStatusKey_1
Multiple-select
Query
Work Status
workStatusKey_1
No
Financial Plan Type
financialPlanTypeKey_1
Single-select
List of Values
Financial Plan Type
financialPlanTypeKey_1
Yes
Planned
Task Start From
taskStartFrom
Single Value
Date
Task Start From
taskStartFrom
No
Task Start To
taskStartTo
Single Value
Date
Task Start To
taskStartTo
No
Show Grid Details?
showGridDetail
Boolean
Show Grid Details?
showGridDetail
No
Checked
Include Inactive Projects?
includeInactiveProjects
Boolean
Include Inactive Projects?
includeInactiveProjects
No
Unchecked
Database Schema
ppmDBSchema
Hidden
Not applicable
Yes
Passed through
Clarity PPM
UI Theme
ppmUserUITheme
Hidden
Not applicable
Yes
Passed through
Clarity PPM
Language
ppmUserLanguage
Hidden
Not applicable
Yes
Passed through
Clarity PPM
User ID
ppmUser
Hidden
Not applicable
Yes
Passed through
Clarity PPM
Parameter Lookup Values
The following values list the lookup values:
Project Type
: Major Project, Application Change, Infrastructure Deployment
Work Status
: Requested, Active, On Hold, Cancelled, Complete
Financial Plan Type
: Budget, Planned
Parameter Explanations
The following list describes the parameters:
  • The Project OBS Type is a cascading parameter and determines which units are listed in the Project OBS Unit parameter. This parameter is not used to control which projects display in the report.
  • The Project OBS Unit parameter displays values that are based on the Project OBS Type selected. When you select an OBS unit in this parameter, the report displays the projects that are attached to the OBS unit and descendants of the unit you select.
  • The Work Status parameter is associated to the Work Status lookup in
    Clarity PPM
    . This lookup is configurable so lookup values can be added, modified, or deactivated.
  • The Financial Plan Type parameter allows you to select which type of financial plan cost amount to display in the project summary section of the report. You can run the report to display the budgeted or planned cost amount that is entered on the financial summary of the project. If the project has a detailed budget or cost plan, then the approved budget amount or cost plan amount for the plan of record displays. The Financial Plan Type parameter works as follows:
    • Budget
      . The report displays budgeted cost. The preceding screen capture was run with the option of planned. If it is run with the option of budget, then it displays "budgeted" where it displays "planned" in the project summary section of the report. 
    • Planned
      The report displays planned cost. The preceding screen capture displays planned cost in the project summary section because this is the parameter valued selected when running the report.
  • The Task Start From and Task Start To parameters determine the start date of the tasks that display in the report. If dates are entered, the report includes tasks with start dates within the range of dates that are entered in the parameters. This allows you to control which inter-project dependencies display in the report. The diagram displays a maximum of five predecessor and five successor inter-project dependencies, but you can leverage the date parameters to determine which appear if you have more than five dependencies.
  • The Show Grid Detail parameter controls whether the dependencies displayed in the diagram also display in a table below the diagram. The diagram displays a maximum of five predecessor and five successor inter-project dependencies. The detailed table does not have this limit and shows all inter-project task dependencies. If the parameter is checked, a table showing the dependencies display below the diagram for each project. If the parameter is not checked, the table does not display.
  • The project statuses are displayed based on the existing project statuses in the environment such as test, dev, or prod. For example, if there are projects with only Approved status, then only the Approved project status displays.
Report Fields and Calculations
The report displays the project name, project ID, project type, project manager, work status, start date, finish date, planned or budgeted cost, and objective in the project summary section. The report has a financial plan type parameter, allowing you to select whether to display the planned or budgeted cost.
The report displays only projects with inter-project task dependency relationships (that is., dependencies to tasks or milestones in other projects). The report includes a diagram as a visual representation of these inter-project dependencies. The diagram uses rectangles to represent the main project and its dependent projects. The main project is at the center of the diagram. The predecessor projects are located above the main project; the successor projects are located below the main project. The dependency relationships are represented by lines connecting dependent projects to the main project, with the arrows pointing to the successor projects. The diagram displays a maximum of five predecessor and five successor projects. If there are more than five inter-project dependencies, the diagram displays the first five projects in alphabetical order. The other dependencies display as part of the grid when you select the Show Grid Detail parameter. The report also has Task Start From/To parameters to control which inter-project dependencies display in the report.
When the Show Grid Detail parameter is checked, the report includes a table that displays information about each project dependency that is associated to the main project. The project dependency information is displayed in the first eight columns and includes: dependent project name, dependent project ID, dependent task name, dependency schedule stoplight, dependent task start date, dependent task finish date, type (Predecessor, Successor), and dependency type (Finish-Finish, Finish-Start, Start-Finish, Start-Start). The main project information is displayed in the last three columns and includes: task name, task start date, and task finish date. The main project name displays above these columns. The report also displays a checkmark icon, to the right of task name, indicating that the task or dependent task is critical.
Programs and templates are excluded. This report contains the following calculations:
  • Dependency Schedule
    The dependency schedule stoplight is the number of days the task or milestone is late and considers the following items:
    • Whether a baseline exists
    • Task or milestone status
      If a baseline exists, then days late is calculated as task or milestone finish date minus baseline finish date. A positive number indicates that the task or milestone is late according to the baseline. A negative number indicates that it is early according to the baseline.
      If a baseline exists and the task or milestone finish date is the same as the baseline finish date, then the task or milestone is considered late if it is not completed and it was due before today's date. In this case, days late is calculated as today's date minus task or milestone finish date.
      If there is no baseline, then days late is calculated if the task or milestone is not completed and it was due before today's date. In this case, days late is calculated as today's date minus task or milestone finish date. Dependency Schedule stoplight color is determined as follows:
      • Green= On Schedule (<=0)
      • Red= Late (>0) 
  • Dependency Diagram
    The dependency diagram uses rectangles to represent the main project and its dependent projects. The main project is in the center of the diagram. The predecessor projects are located above the main project; the successor projects are located below the main project. The color of the rectangle for the dependent projects is determined by the dependency schedule stoplight of their tasks or milestones. If a dependent project has at least one task or milestone with a red dependency schedule stoplight, then the rectangle in the diagram is red for that dependent project. The color of the rectangle for the main project is based on the project  schedule, which is the number of days the main project is late, and considers the following items:
    • Whether a baseline exists
    • Project progress
      If a baseline exists, then days late is calculated as project finish date minus baseline finish date. A positive number indicates that the project is late according to the baseline. A negative number indicates that it is early according to the baseline.
      If a baseline exists and the project finish date is the same as the baseline finish date, then the project is considered late if it is not completed and it was due before today's date. In this case, the number of days late is calculated as today's date minus project finish date.
      If there is no baseline, then days late is calculated if the project is not completed and it was due before today's date. In this case, the number of days late is calculated as today's date minus project finish date. Schedule color is determined as follows:
      • Green= On Schedule (<=0)
      • Red= Late (>0)
Report Security
Security is determined by project view rights.