Project Management Banana Curve & Primavera P6

Greetings. I agree with Olusegun. The top curve is the planned curved and bottom shows the latest activities can finish using up all the float. 1. When accessing a program prior to baselining excessive float can be corrected to optimise resources and cost impact. 2. In the updating and delay analysis, actual line on the curve can show a progression in to eating up the float. Which could end up in possible delay in the finish of the project. Fasttracking or crashing a schedule might be required.

I have one question. When I try to copy and paste (to excel) "remaining late units", from the Resource Assignements sheet, for example because I want to chart banana curve in excel, I can see that It doesn't work, becasue if an activity has a finish date on 22-Mar-2024 but Its dostribution of remaining late goes up to 28-Mar-2024, these last days units are not gonna be copied (units from 23 Mar 2024 onward are not copied). Any idea how to solve this ?

Early and Late curves can give a false response about whether a delay has occurred, therefore I'm not enthusiastic about this "tool" . At first glance one might think that if progress reached at any time (data date) is within the two curves, then no delay occurred as per comparison with baseline. Unfortunately, this is true only if no "out of sequence" occurred. However, as said in another comment, the reliability of the "banana" curves rely on the quality of the CPM network, but they are progress planned curves ultimately and not a tool to control critical path. Early and Late curves are more used in the oil and gas industry (since 90') where, for example, structural and piping erection are typically executed according to well established sequences of work, and the tool gives a realistic representation of the actual progress pertaining to specific parts or elements of the project (WBE). As curves are associated with progress (i.e. invoicing), the tool focuses on production rather than delay and this can lead to ignoring delays on a critical path. It's similar to consider SPI (by alone) as an appropriate method to monitor schedule delay which can be detected and monitored effectively only by using also a CPM.

A good visual to determine if your float values are accurate! Should both curves (Early and late) project further outwards, this would reflect doubts about the validity of the project float values. It definitely would need revisiting to determine as to why this has occurred. It could be due to danglining / open ended activities or wrong logic / sequence.

It looks similar to recovery curve against BL which recovers at certain point of time