About program deliverable dependencies

Program deliverable dependencies allow the program planner to set up dependencies between program deliverables and use that information to sequence the order in which the deliverables for events, projects, and subprojects should be completed. This lets the responsible users assigned to the deliverables know the order in which they should be worked.

A deliverable can be assigned the following dependencies:

• Preceding — A deliverable dependency that must be completed before working on the current deliverable.
• Concurrent — A deliverable dependency that can be worked on at the same time as the current deliverable.
• Succeeding — A deliverable dependency that will be worked on after the current deliverable.

Example: five deliverables with various dependencies assigned. Users looking at these deliverables see that they can work on deliverable 1 and 2 at the same time because they are concurrent. However, due to the preceding dependency between deliverable 2 and 4, the users know that deliverable 2 must be completed before starting work on deliverable 4.

When deliverable dependencies are created, Active Workspace sequences the order of the deliverables. This helps the program planner better plan the project work and ensures that deliverables are worked in the proper order. As work continues on the program and dependencies are added, modified, or removed, Active Workspace can resequence the deliverables as needed. This ensures that the program deliverables and their dependencies are always accurate and up-to-date.

Program Planning, 2606 — Unpublished work. © 2025 Siemens