Early Start after Early Finish?
Forum Sponsor
Top Posters
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts
Hi to all
I would to share similar issue i faced .I just linked two items in the schedule with FS relationship.
Item 1 is assigned as start milestone and
Item 2 is assigned finish Milestone.
On running F9 the Item 2 which is chronologically the last one got the early dates one day earlier than item 1.
Kevin,
I agree with you, if some constraint functionality is to be applied it should be in the form of a marker that will highlight on the activity line a target or contractual date but with no effect on the network logic.
I have been asking for this for years but seem like the PMI and others can live with it as good practice, even a single occurrence can be enough to distort the network computations making it meaningless or impossible to follow the logic. The complications of real life modeling and resource constraining are a real and necessary need enough comlpicated enough to drive someone crazy, then why add unnecessary additional complications with date constraints, is not needed to highlight the target?
Best regards,
Rafael
Thanks Gary, thats pretty much what I thought. As a long time Primavera user and now Open Plan, I have always been against the use of Mandatory or Fixed constraints that ignore all network logic. If it were up to me they wouldnt exist in any software.
Cheers
Its clearly not conceptually possible to have an activity planned to start after its planned to finish.
I wouldnt call it a software bug, more that Open Plan has never been hot on checking the integrity of the data entered. Unless it causes an error in the algorithms they use (eg logical loops), you probably wont get a log or error message from Open Plan.
You could argue that Open Plan shouldnt allow it, but you could also argue that the user shouldnt be entering such data in the first place. Ultimately, no amount of data validation by the software will completely insure against a numpty at the keyboard!
This is one of the many reasons why people should be very careful when using constraints in schedules, particular the fixed types which overide logic and float calculations.
Cheers,
G