Capital Projects / Projects / Execute
Capital Projects / Projects / Plan
Capital Projects / Commissioning / Design
Assets / Enterprise Assets / various roles / Project Proposal Console

Estimating Design Schedules

After a project has been approved, you can estimate the design schedules for the project's actions. The design estimates are based on information that has been provided by architects, designers, and contractors who have analyzed a project's requirements. Design estimates are defined after a project has been approved, in the project planning phase. The design estimates provide you with detailed information that supplements the initial baseline cost and schedule information that you gathered prior to approving a project.

You can work with the Gantt chart from the Management Console (from either the Execute or Manage process, depending on your role). From the Management Console, you select a project and then select the Gantt tab to work with the schedule for that one project.

For Commissioning, you update commissioning plans as design professional and commissioning agents review design submissions and provide input.

The Gantt chart report provides a quick and easy visual representation of how project action items are proceeding, and enables you to find critical dependencies that need to be expedited so that the schedule is not adversely affected.

From the Estimate Design Schedule and Durations task, you can:

You may also want to review these topics:

Estimating Design Schedules from the Enterprise Assets / Project Proposal Console

Working from the Project Proposal Console, you can estimate design schedules for projects with the status of Proposed. These projects are being developed to analyze different proposals, so the schedule is a key aspect of this evaluation. From the Project Proposal Console, you work with projects that are not approved, but you are developing design schedules as part of your evaluation.

Estimating Design Schedules from the Management or Commissioning Consoles

From the Management or Commissioning Console's Plan / Schedule Actions tab, you can estimate design schedules for project actions using the Gantt chart. Using this task from the Management or Commissioning Consoles, you can work with projects having any status. After you select a project, you can then view the actions for that project, or for that project's work packages. See Scheduling Actions Using the Management or Commissioning Consoles.

Setting the Days Worked Per Week

You will be using a Gantt chart to review and edit the design schedules. The Gantt chart timelines show time in terms of work days. It is important to remember when estimating design schedules that the timeline in the Gantt chart depends on the project/work package Days Per Week setting in addition to the start date and duration. The Days Per Week setting defines how many days per week will be work days. For example, if an action item is 20 days of duration and the Days Per Week setting is 5, then the timeline will show four weeks for this action item, because the work will not be done on weekends. Alternately, if you enter a duration for an action, the program calculates the end date (Date - Calc. Completion) using the Days Per Week value you enter.

For information on defining the work package / project Days Per Week setting, see the Creating and Editing Work Packages or the Requesting a Project topics.

Note: Before you can estimate design schedules, you must enter initial values for each action's Date to Perform and Duration - Est. Design fields. These values can be added in the Plan/Add or Edit Actions task.

Estimating Design Schedules and Duration

To estimate design schedules and durations:

Note:  Alternately, you can use either of the following methods to access the Gantt chart:
- Run the Management Console Plan task, and then select the Schedule Actions tab to review and edit actions using the Gantt chart. From the Management Console task, you can view actions for projects having any status, and you work with a single project at a time.
- Run the Enterprise Assets / Project Proposal Console, select a project ,and then use the Gantt Tab to work with the project's actions on the timeline.

Setting an Action to Precede Another Action

Note: Actions are linked in a "Finish to Start" relationship, meaning that the first action you select (the predecessor action) must end before the next action you select (the successor action) can start, and so on. When you set an action as a predecessor, a workflow rule updates the date fields for dependent actions. See How the Gantt Chart Updates Dependent Actions.

To set an action to precede another action: 

  1. In the Gantt chart panel, click on the action item you wish to be the predecessor.
  2. In the right pane, click and hold on the Finish circle of the first action item.
  3. Drag to the Start circle of the second action ite.
  4. A popup message asks you to confirm the change.

  5. Click OK. The action item number for the action that is the Predecessor is entered in the Predecessor field for the action it must precede.

How the Gantt Chart Updates Dates for Dependent Actions

When you set an action to precede another action, the Gantt Chart automatically ensures that the date field for the dependent action conforms to its predecessors' date, that is, that the dependent action begins after the predecessor action ends. For example, if a predecessor's dates are extended and now overlap with its dependent action, the dependent action's dates must be shifted to start after the end date of its predecessor.

The Gantt chart accomplishes this using a workflow rule, cascadeAllTaskDependencies, that is called whenever:

The cascadeAllTaskDependencies workflow rule does the following:

  1. Checks the predecessor field of the action and modifies both baseline and design dates to come after the corresponding predecessor's dates.
  2. Checks the days_per_week field of the action's enclosing work package (or of the project if not in a work package), and modifies the start and end dates to take into account the working days per week for the work package or project.
  3. Cascades any changes; that is, checks if the action is a predecessor of other actions and checks those action dates against their predecessors. A chain of dependent actions may exist and all actions in the chain shift over when a predecessor's dates are extended.
  4. Checks for dependent loops; for example, Action A is listed as a predecessor of Action B and Action B is listed as a predecessor of Action A, whether directly or indirectly. As this is an impossible scenario, a warning is issued if this condition exists.