Reflecting Physical % Completed values on Tracking Gantt

[Jac]

hi,

The Tracking Table in Tracking Gantt view has a column named Physical %
Completed, this column's values will not be reflected on the Tracking Gantt
as what % Completed would; is there any way to reflect the Physical %
Completed values on Tracking Gantt?

Another thing is if 50% lag time is added in a duration, the start time &
finish time changed to 1:00pm & 12:00pm respectively. But why if 40% lag time
is added, the start time & finish time changed to 9:36am & 9:36am
respectively (seem to base on 24 hours)? is it because the start time is no
longer based on the Standard Calendar?

Thanks!

 

[Gérard Ducouret]

Hello Jac,

1° - The Physical % Completed is just used to alter the calculation of BCWP
in the Earned value method. It doesn't appear in a graphic view.
2° - The lag time, if it's set in percentage in a dependency relationship,
must be understood as a percentage of the predecessor's duration.

Hope this helps,

Gérard Ducouret

 

[Jac]

Hi,

Thanks for replying.
So, you mean there is no way to reflect the Physical % Completed values on
Gantt Chart?

 

[Steve House]

Note that the 'X' axis of the Gantt chart is time and time spent is what %
Complete tracks, hence it is logical to have it displayed in the Tracking
Gantt view. But there is no chart axis that represents the number of units
of whatever that the task is to create and so there's no axis on which to
graph the number that have actually been accomplished to date. So there
really is no valid basis for displaying % Physical Complete except possibly
as a text note, which is just what showing that field in the associated
table accomplishes.

Lag times deal with time BETWEEN two tasks, not duration WITHIN a task. If
you say a task link has a 40% lag time, Project first takes 40% of the
duration of the predecessor and it will only be the luck of the draw that it
falls to an even hour number - Project does all of its actual calculations
in minutes. Now it adds that resulting time value into the link between
that task and its successor, using the Project Calendar to determine the
start and end of the delay in the same manner duration is calculated.

Let's say we had two tasks A & B linked FS. All calendars are Project's
Standard calendar. A starts Monday 8am and finishes Thursday 5pm, duration
4 days. Task B starts Friday 8am. Now I add 30% lag time to the link. 30%
of task A's duration of 4 days (32 hours) is 9 hours 36 minutes. Starting
at the next working time minute after 5pm Thursday, ie 8am Friday, we count
off 9h36m of working time as defined by the Project calendar. That brings
us to 9:36am Monday and that's where Project places the lagged start of task
B.

 

[Gérard Ducouret]

Jac,

While the Physical % Completed values are not displayed by default in the
Gantt chart, you can display them:
- As a field beside a task bar : Format / Bar Styles / Text / add this
field to the left or to the right of the bar
- As a new symbol bar : Format / Bar Styles
From : Actual Start
To : Physical % Complete
NB : this symbol needs that %Complete is <> 0 so that it is able to
display.

Gérard Ducouret

 

[Jac]

Hi,

Thanks for your guidance! : )

Jac,

While the Physical % Completed values are not displayed by default in the
Gantt chart, you can display them:
- As a field beside a task bar : Format / Bar Styles / Text / add this
field to the left or to the right of the bar
- As a new symbol bar : Format / Bar Styles
From : Actual Start
To : Physical % Complete
NB : this symbol needs that %Complete is <> 0 so that it is able to
display.

Gérard Ducouret

 

[Jac]

Hi,

Thanks for your reply. : )

Note that the 'X' axis of the Gantt chart is time and time spent is what %
Complete tracks, hence it is logical to have it displayed in the Tracking
Gantt view. But there is no chart axis that represents the number of units
of whatever that the task is to create and so there's no axis on which to
graph the number that have actually been accomplished to date. So there
really is no valid basis for displaying % Physical Complete except possibly
as a text note, which is just what showing that field in the associated
table accomplishes.

Lag times deal with time BETWEEN two tasks, not duration WITHIN a task. If
you say a task link has a 40% lag time, Project first takes 40% of the
duration of the predecessor and it will only be the luck of the draw that it
falls to an even hour number - Project does all of its actual calculations
in minutes. Now it adds that resulting time value into the link between
that task and its successor, using the Project Calendar to determine the
start and end of the delay in the same manner duration is calculated.

Let's say we had two tasks A & B linked FS. All calendars are Project's
Standard calendar. A starts Monday 8am and finishes Thursday 5pm, duration
4 days. Task B starts Friday 8am. Now I add 30% lag time to the link. 30%
of task A's duration of 4 days (32 hours) is 9 hours 36 minutes. Starting
at the next working time minute after 5pm Thursday, ie 8am Friday, we count
off 9h36m of working time as defined by the Project calendar. That brings
us to 9:36am Monday and that's where Project places the lagged start of task
B.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs

hi,

The Tracking Table in Tracking Gantt view has a column named Physical %
Completed, this column's values will not be reflected on the Tracking
Gantt
as what % Completed would; is there any way to reflect the Physical %
Completed values on Tracking Gantt?

Another thing is if 50% lag time is added in a duration, the start time &
finish time changed to 1:00pm & 12:00pm respectively. But why if 40% lag
time
is added, the start time & finish time changed to 9:36am & 9:36am
respectively (seem to base on 24 hours)? is it because the start time is
no
longer based on the Standard Calendar?

Thanks!

 

[Gérard Ducouret]

You are welcome, Jac!

Hi,

Thanks for your guidance! : )