The activities in each section have been progressed exactly the same for Actual Start, Remaining Duration and Percent Complete. Update Scenario:The Baseline schedule from above has been copied and none of the logic has changed. When that same schedule is updated with actual dates and the data date has been moved forward, negative lags will cause issues with forecasted dates and improper float values.
Using Negative Lags in a “baseline”, non‐statused schedule will work fine. See graphic below The graphic above shows that all Early Dates and Late Dates are perfectly in line and the float values match. In modeling a Proper Lag scenario that matches the dates in the Negative Lag scenario, activity B is tied to activity A, Finish to Finish (FF, 6). This is modeled below in the section titled Negative Lag.
The baseline data date is set at February 1st. The negative relationship proposed on the Linkedin post “Finish to Start with a Negative Lag” suggested that activity B is tied Finish to Start negative 4 days ( FS, ‐4) to Activity A. A baseline schedule was created as well as an update schedule to show the negative effects of negative lags when a schedule is statused and the data date moves. Baseline Scenerio:This is a simple schedule built with 5 activities modeling proper lag versus a negative lag scenario.
0 kommentar(er)
