Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Log Record Problem

1 reply [Last post]
Tue, 2008-09-23 11:58
Anu Tor
User offline. Last seen 13 years 28 weeks ago. Offline
Joined: 7 Mar 2007
Posts: 53
Groups: Petro-Chem / Oil & Gas
When the log record is show " Activity started too early to allow it to finish after the expiration of its predecessor’s lag ". Please advise me, how to solve one?

Thank you.
Top

Replies

Tue, 2008-09-23 16:21
#1
Johny Kesserwany
User offline. Last seen 7 years 25 weeks ago. Offline
Joined: 18 Sep 2007
Posts: 118
Groups: Civil Engineering
Hi Anu,

This message appears in the Out-of-Sequence progress listing of a scheduling report when a successor activity starts too early to satisfy a finish-to-finish relationship with its predecessor. By default, P3 uses the contiguous duration scheduling option (Tools, Schedule, Options button), meaning that when a finish-to-finish predecessor delays its successor’s finish date, P3 also delays the successor’s start date because the workperiods of the activity must be contiguous. When the successor has an Actual Start date, P3 can not delay the start and the warning message is generated.

There are 2 options to prevent this message.

1. Remove the relationship between the two activities if it is no longer valid. This allows the remaining duration of the successor to be calculated from the Data date.

2. Go to Tools, Schedule and select the Options button. Schedule the project using the "Interruptible" durations option. If you choose Interruptible and a finish-to-finish predecessor delays an activity’s finish date, P3 delays only the finish of the activity; the start is scheduled separately on the Actual Start date.

Regards
Top