Before you begin: Verify the list of project phases resides in the Project Phase data definition pull-down data set. This is the same list that is used when selecting a project phase manually in the project properties window. You can add or modify the default list as needed. This list makes the phases available for any project or project template; for each project or template, you select which of the phases to use. Create any business processes that you plan to use to drive gates conditions and phase completion.
Step 1: Define Project Phases. For each project or template, you define the list of project phases to include in the setup, choosing from the entire list in the Project Phase data set.
Step 2: Define Gate Conditions. For each phase, define one or more gates conditions. A gate condition is a combination data element and trigger condition that enable transition to the next phase.
Step 3: Schedule Gates runs. The gates runs run the validation of gate conditions. You can schedule runs automatically. This is optional.
Step 4: Activate the gates setup.
Step 5: Define permissions.
Note: If you create a new project by copying a project template or an existing project, any existing gates setup in the source project is copied into the new project, including the gates status. The gates phases are restarted at the first phase in the new project, and the scheduled gates run is activated.
Example of a gates setup and conditions
Add project phases to the gates setup (Settings tab)
Change the order of project phases
Define gates runs schedule (Schedule tab)
Oracle Corporation
Primavera Unifier 9.10 • Copyright © 1998, 2012, Oracle and/or its affiliates. All rights reserved.