I need help about backward leveling,I created a P3 file which includes some activities without predecessor and successor and I want those activities to be scheduled as late as possible without causing any delay on project finish date,I tried to level backward but it didn't work.

thanks

Use float constraint, if you don't want these activities to affect the start date of their successors, select Zero free float, otherwise you can use Zero total float.

Hope this helps,

Ahmet Cetin

OK, I do not know what "float constraint" means, but have you tried putting in "As Late As Possible" constraints on those activities and scheduling? What was the result?

Cheers

Hello tilt,
In P3.1, there is no "As Late As Possible" constraint, instead there is "Float Constraint". To be honest, it is even better than in P6 still, because you are able to select Free Float or Total Float.

Cheers,

Ahmet Cetin

Oh, sorry, I did not realise this was 3.1!

Cheers

Hello Gorkem,
As I understand you would like to see "backward-pass" not "backward-leveling". Backward leveling is related with resource allocation. When you schedule, Primavera calculates both forward-pass and backward-pass at the same time. So, if you want to see the Late Start and Late Finish dates for all activities in your schedule, you can add these columns to the table. If you want to show it on the Gantt chart, then follow these steps:
1. Go to Format, Bars and add a bar by clicking on the + button.
2. Change the Description to read Late Bar.
3. Change the Start Point to Late Start.
4. Change the End Point to Late Finish.
5. Click OK to save the bar.
6. Change the Position of the Late Bar to a number other than the other visible bars and check the Visible box.

In this way, you can compare the dates calculated by forward-pass and backward-pass.

Hope this helps,

Ahmet Cetin

In addition, you shall start from the latest milestone of your project, put a mandatory finish constraint to this milestone (this way your milestone will not move), and link your activities in a sequence from the last to beginning accurately, but my suggestion for activity relations is to put as finish to finish if you are following a backward-pass logic. Finally, you can remove the mandatory link or superceed it with early finish constraint, when you ensure your schedule has no slippage.