Primavera P6 has many unique project constraints that you can utilize to an activity. Out of these, you can view them as either hard or delicate project constraints. As we’ve examined some of them recently.

There’s one Primavera P6 constraint nevertheless that can be truly helpful in certain circumstances. Yet it doesn’t appear to fit into either of the groups. How about, if we investigate the ‘As Late As Possible’ constraint?

Setting project constraints like an ‘As Late As Possible’ (ALAP) on the action can utilize to keep project away from the delay between the end of a task. And the start of its subsequent functions.

• If taken a chance that an action has project constraints as an ‘As Late As Possible’ constraint in Primavera P6, it will carry on in the behavior in the following way:
• The ‘As Late As Possible’ constraint in Primavera P6 will plan the activity to begin as late as possible. This condition implies if the action has a positive free float.
  i.e., (an inevitable delay between the action’s end and the start date of its successor, not a slack). Primavera P6 will compel the free float deferral to be 0.
• The ‘As Late As Possible’ project constraints of Primavera P6 won’t influence the beginning or end dates of succeeding tasks. There’s a chance that succeeding tasks go in reverse/forward in the arrangement with the ‘As Late As Possible’ project constraints. It will consequently plan itself to begin as late as possible.

‘As Late As Possible’ project constraints work contrastingly in MS Project. The venture will delay the beginning of successors when an ‘As Late As Possible’ constraint gets connected.

For example, consider that I applied the ‘As Late As Possible’ constraint (with a slack of 10d). You can observe on the Gantt Chart the shift of Delivery milestone is quite far into the future so that it can start 10 days before the Drywall activity.

The case of “Acquirement” Activities-

An example of the ‘As Late As Possible’ project constraints in Primavera P6 is a task that has acquirement of materials. The acquisition of materials needs to go before the task that they required for.

Typically ventures are not driven by the procurement tasks. Therefore, there will be a postponement of the end date of the obtainment. And also the beginning date of the task that requires the materials (not a preferable circumstance).

By including ‘As Late As Possible’ project constraints of Primavera P6, into the acquirement tasks they push ahead until the point when they complete the start of the task that requires them.

This will have a positive cash-out stream. And materials won’t stay nearby until the point that they require (Be mindful that they are not late! You should provide some buffer).

The case of “Pictures required by” Activities-

Before something can get developed, illustrations regularly require it. These figures frequently need a predefined timeframe before the actual initiation of the task that requires those pictures.

Utilizing the ALAP project constraints of Primavera P6 will enable the task planned. And it will set some days preceding the start of this task. These connected tasks together can do with a finish-to-start relationship and can apply to a 30 day slack.

At that point assign an ‘As Late As Possible’ constraint of Primavera P6 to the necessities of illustrations task.

Utilizing ‘As Late As Possible’ project constraints in Primavera P6 can help you all the more to precisely display the situations in a task. Run and try different things with them.

This was all about the Primavera P6 and its project constraints.