2. Gantt project creation

2.1 How do you create projects with the Gantt scheduler?

When you create a project, the Plan Start date is required but the Plan End date is not required. On the General tab, the Date, Name, and Currency are required. Depending on the project form, the Schedule tab or the Tasks tab contains several more required fields, Time Zone and Calculate Project From. The Date field auto-populates with the date that you create the project.

If you do not add a Plan Start date for the project, it defaults to the date that you created the project. All other fields must also contain the previously saved values. The fields in the Summary section can be changed as required except for Plan Start.

The default Constraint Type for new tasks is As Soon As Possible. The Gantt scheduler handles As Soon as Possible constraints on your tasks in two different ways, whether Gantt Strict mode is enabled or disabled.

2.2 Gantt Strict mode

If your application administrator has enabled Gantt Strict mode, the project Plan Start date determines the placement of your tasks. With Gantt Strict mode, all first tasks are required to start directly on the project Plan Start date or end directly on the project Plan End date depending on the value that you select for the project Calculate Project From field. First tasks are tasks that do not have incoming dependencies or constraints specified. All next tasks are moved left or right to be as close as possible to their ancestors and to not violate any dependencies or constraints.

By default, the as-shipped IBM TRIRIGA applications do not use Gantt Strict mode. When you create tasks, the tasks maintain the start date that you specify. The next tasks are moved left only to correct dependencies, and do not need to be close to their ancestors. Your application administrator can enable Gantt Strict mode by setting GANTT_STRICT_MODE=TRUE in the TRIRIGAWEB.properties file on the IBM TRIRIGA server. This setting is system-wide, so it must be consistent across all servers.

In addition, IBM TRIRIGA provides a "minimal" Gantt Strict mode. When you create tasks, the tasks maintain the start date that you specify. All next tasks are moved left or right to be as close as possible to their ancestors and to not violate any dependencies or constraints. Your application administrator can enable "minimal" mode by setting GANTT_STRICT_MODE=MINIMAL in the TRIRIGAWEB.properties file on the IBM TRIRIGA server. This setting is system-wide, so it must be consistent across all servers.

Note: The GANTT_STRICT_MODE=MINIMAL setting was introduced in IBM TRIRIGA 3.6.0.

2.3 Calculate project from

When a project is created, the required Calculate Project From field in the Summary section of the project defaults to Start. This option means that the project begins on a particular Plan Start date and runs through to completion. The purpose of this option is to manage the project from its beginning.

When Calculate Project From is set to End, then the project is tracked from the Plan End date of the project. This option is used when the project must be completed on a certain date and the start date might or might not be important. The Plan End date must be set for this setting to function properly.

As a result, the Calculate Project From field influences the critical path calculations and constraint violations.

Note: The Calculate Project From: Both option is deprecated. When you open existing projects, whose Calculate Project From field was set to Both, the product prompts you to select another option. If the value is set to Both, then the behavior is treated as if the field is set to Start.

a. Calculate Project From field

Calculate Project From field

2.4 Project calendar

The project and the tasks can contain a calendar that defines how hours in the task are distributed throughout the days in the project. If no calendar is selected, then the project is assumed to run on a 24-hour schedule. You can set a calendar for the entire project and you can also set calendars for individual tasks in the project if wanted. When a calendar is set, the tasks on the Gantt chart display a background that represents available time to work. Working hours are displayed as "white" and non-working hours are displayed as "gray".

The purpose of the calendar is to apply real-world availability to plan time for the project. For example, if no calendar is associated to the project or a task, and it takes 40 hours to complete that task, then the task displays in just under two days on the Gantt scheduler. If a calendar is specified with the standard working hours of 8AM-12PM and 1PM-5PM from Monday to Friday, then the task takes five working days to complete. So, depending on how the company carries out projects, planning for the completion of the task can be considered.

Note: If you want to set a calendar for the project, set it at the beginning of the project. The project calendar is applied to all tasks that are created after the calendar is in place. When you set a project calendar, it does not automatically set or change the calendar on tasks that are already created.

2.5 Setting project calendar

If all or most of the tasks within the project require a defined calendar, you can define an overall calendar for the project. To add a project calendar, open the project and go to the Calendar Details tab. In the Availability Calendar section, select a calendar. A calendar that is named DEFAULT with working hours of 8AM-12PM and 1PM-5PM from Monday to Friday, can be selected. Otherwise, you can add a calendar and define it based on the project requirements. The Find action allows the calendar to be selected or a new calendar to be added.

Note: To create a 24-hour Availability Calendar, the Start Time must say "0:00 AM", the End Time must say "24:00 AM", and the # of Hours must say "24".

a. Gantt chart with project calendar

Gantt chart with project calendar

You can remove the project calendar from any individual task if preferred. To remove the project calendar from a task, open the task, go to the Calendar Details tab, and remove the calendar from the Availability Calendar section.

b. Project calendar and one task with no calendar

Project calendar and one task with no calendar

2.6 Setting calendars for tasks

If most of your project tasks require the same calendar, you can set a default project level calendar as described, and then create your tasks. Then, for tasks that do not follow the project level calendar, you can set a different calendar. For example, say that some tasks must be done Monday through Friday, and others can be done only on the weekend, Saturday and Sunday. The calendars that you specify for tasks do not need to be the same calendar. The task calendars can be set individually, based on need. They are independent of each other.

To specify a calendar for an individual task, open the task, and go to the Calendar Details tab. Click Find in the Availability Calendar section, select the preferred calendar, and click OK. If a task already contains a calendar, such as the default project calendar, and you want to change it, select the calendar in the Availability Calendar section and click Remove. Then, add the preferred calendar.

If you do not see a calendar that fits the requirements of the task, you can create a calendar by clicking Add and specifying the required schedule. After you set the scheduling assumptions, working hours, and so on, click Create Draft, then click Activate. Make sure to select that calendar for the task and click Activate or Save.

Another case where you might want to specify calendars at the individual-task level is if you created tasks before you specify a project calendar. Those tasks do not have the project calendar that is automatically assigned to them. You can specify a calendar for those tasks, whether it is the calendar that you chose for the project or a different calendar.

a. Project calendar (1), task with no calendar (2), and task with different calendar (3)

Project calendar (1), task with no calendar (2), and task with different calendar (3)

2.7 Setting project time zone

The time zone for a project must be set based on where the project takes place. Note that if the profile of the user who is creating the project is set to a particular time zone, the project defaults to that user's time zone. Accordingly, change the time zone.

When a calendar is applied to the project or tasks, the users from different time zones view the tasks in their own time zone in the Gantt scheduler project. The times of the tasks shift based on the user's time zone.

If no calendar is in place, then the tasks use the 24-hour calendar. All tasks that are created in the Gantt section default to the current time. Of course, relationships and dependencies with other tasks in the project, and constraints on tasks, can affect some of the task start times.

For example, let's say that a project is created in the Pacific time zone (GMT -08) and a user from the Athens time zone (GMT +02) logs in and views the project. Instead of tasks that start at 8am or 08:00, like they do in the US Pacific time zone, the tasks start at 6pm or 18:00, which is the time in Athens, Greece.

Note: Syncing task time zones

The way in which the Gantt scheduler handles time zones can be complex. The interaction of the project time zone, the user time zone, and the server time zone can all affect the time zone of the task that is added to the Gantt scheduler. The Project Tasks Gantt section, the Project Tasks section, and the Summary section of the Schedule tab can get out of sync.

To refresh the project, select Save in the Project Tasks Gantt section, then select the Save action in the Project window. The save refreshes the Gantt scheduler and properly displays the tasks. If there are multiple constraint or dependency violations, you might need to save several times. For more information, see Constraint violations.

The time zone is required to be set in the project in the Summary section of the Schedule tab. When a task is created in a project with the time zone set, the task adopts the same time zone regardless of the time zone that the user lists in their profile. The time of the task can be initially set with the time of the server on which the task is created. If this happens, the Gantt scheduler and project must be saved for the tasks to be in sync. The task can be opened after creation and the time zone can be changed independently. The time zone for the task can be changed on the Calendar Details tab of the task. If no calendar exists in the Gantt scheduler, then the time zone changes are not as obvious.

a. Project calendar and one task in a different time zone

Project calendar and one task in a different time zone

2.8 How do you apply a project template?

If the same project is intended to be run multiple times, then it might be easier to create a project template. You create a template by selecting Projects > Project Set Up > Project Templates.

The project template contains all of the tasks and relationships that are necessary for the project to be completed. The template can then be imported into each new project with the same tasks required. When the tasks and dependencies are imported, they are automatically set to the Plan Start date of the new project. Of course, tasks can be added or deleted, and relationships can be modified.

To apply the project template, perform the following steps.

Step 1. Create a project and populate the required fields at minimum.

Step 2. Select Save Draft.

Step 3. Click More > Apply Template.

Step 4. Select the project template and click Continue.

a. Capital Project > More > Apply Template

Capital Project > More > Apply Template