You have an error in your question. The essence is in creating the list of activities, sequence, resources, durations. What is it that you want to know exactly?
It is better to read more about CPM and follow Raviraj and Rafael advice.
With kind regards,
Samer
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Mon, 2010-01-04 08:20
In the forward pass you calculate Early Dates, the date an activity can start, an activity can start after all predecessors are finished so you use the latest date, latest being a maximum value.
In the backward pass you calculate Late Dates, the latest date an activity can finish without delaying project finish date, equals the earliest of all successors latest’s start, earliest being a minimum value.
About float you have finish float as the difference of finish dates and start float the difference of start dates, therefore it is wrong to say an activity has float, is a singular statement, an activity have a start float and a finish float. It might be different under activity splitting and resource constraining,and or under PDM relationships other than FS and or after activities are in progress as activities finish dates might be pulled later by finish relationships or constraints.
As far as I remember P3 would allow you to define it to be either Start or Finish, so you have the option to mislead everyone. I always believed it to be wrong, a reflection of the inability of P3 to fully evolve with the more advanced PDM theory, the same as in the case with float that after resource leveling it means nothing under P3.
MS Project provides you with three definitions for Float with Slack as a synonym of Float:
1) Finish Slack = Late Finish - Early Finish
2) Start Slack = Late Start - Early Start
3) Total Slack = the smaller value of the Late Finish minus the Early Finish field, and the Late Start minus the Early Start field.
I also find MS Project to be misleading in its definition of Total Slack; it is ambiguous and should also be avoided. All software should provide you with both; it can be in a single column a single value if both equals and both values if different, and or on separate columns.
Member for
24 years 9 monthsThe calculations in some
The calculations in some popular software tools are incorrect, particularly float calculations. If you want to understand the correct mathematics see:
http://www.mosaicprojects.com.au/PDF/Schedule_Calculations.pdf
http://www.mosaicprojects.com.au/PDF/Links_Lags_Ladders.pdf
http://www.mosaicprojects.com.au/PDF/Schedule_Float.pdf
Member for
19 years 1 monthRE: Forward pass & Backward pass
Shahul,
I agree with Samer - "The essence is in creating the list of activities, sequence, resources, durations."
Forget Floats, its only good during summer!
Member for
16 years 11 monthsRE: Forward pass & Backward pass
Many thanks to all ,let me check the below mentioned procedure and get back to you for further clarification
Member for
17 years 3 monthsRE: Forward pass & Backward pass
Dear Shahul,
You have an error in your question. The essence is in creating the list of activities, sequence, resources, durations. What is it that you want to know exactly?
It is better to read more about CPM and follow Raviraj and Rafael advice.
With kind regards,
Samer
Member for
21 years 8 monthsRE: Forward pass & Backward pass
Shahul,
In the forward pass you calculate Early Dates, the date an activity can start, an activity can start after all predecessors are finished so you use the latest date, latest being a maximum value.
In the backward pass you calculate Late Dates, the latest date an activity can finish without delaying project finish date, equals the earliest of all successors latest’s start, earliest being a minimum value.
About float you have finish float as the difference of finish dates and start float the difference of start dates, therefore it is wrong to say an activity has float, is a singular statement, an activity have a start float and a finish float. It might be different under activity splitting and resource constraining,and or under PDM relationships other than FS and or after activities are in progress as activities finish dates might be pulled later by finish relationships or constraints.
As far as I remember P3 would allow you to define it to be either Start or Finish, so you have the option to mislead everyone. I always believed it to be wrong, a reflection of the inability of P3 to fully evolve with the more advanced PDM theory, the same as in the case with float that after resource leveling it means nothing under P3.
MS Project provides you with three definitions for Float with Slack as a synonym of Float:
1) Finish Slack = Late Finish - Early Finish
2) Start Slack = Late Start - Early Start
3) Total Slack = the smaller value of the Late Finish minus the Early Finish field, and the Late Start minus the Early Start field.
I also find MS Project to be misleading in its definition of Total Slack; it is ambiguous and should also be avoided. All software should provide you with both; it can be in a single column a single value if both equals and both values if different, and or on separate columns.
Best regards,
Rafael
Member for
18 years 5 monthsRE: Forward pass & Backward pass
Shahul,
Take a small CPM sample and then take max value for fwd pass calculation and then try using max value for backward pass calculation too.
Re-run it again and then u will find the difference.
Do u really need more advise for this?