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.

Why use start instead of early start when filtering

3 replies [Last post]
Ahmet Tuter
User offline. Last seen 3 years 12 weeks ago. Offline
Joined: 7 Feb 2013
Posts: 52
Groups: None

In Primavera, they told me that using Start criteria instead of Early start (and then using data date range) is preferred. Why do we not use Early start within a range but not Start?

Replies

David Kelly
User offline. Last seen 2 years 2 weeks ago. Offline
Joined: 19 Oct 2004
Posts: 630

The "Start" field will contain the levelled start if you have levelled.  Whereas (as long as you have the correct option ticked in the levelling options) Early Start will continue to contain the forward pass result after levelling. So they can be different.

Tom Boyle
User offline. Last seen 3 weeks 6 days ago. Offline
Joined: 28 Nov 2006
Posts: 304
Groups: None

The Start field is accurate for all activities, while Early Start is only accurate for future activities.

The Start field takes the value of Actual Start when it exists and Early Start when it doesn't.  Early Start never reports an Actual Start date.  Under Retained Logic, Early Start rides the Data Date regardless of progress; under Progress Override or Actual Dates, it is blank if an Actual Start exists.

Makes no difference as long as the schedule is un-progressed or you are only interested in future work.  

Zoltan Palffy
User offline. Last seen 20 weeks 4 days ago. Offline
Joined: 13 Jul 2009
Posts: 3089
Groups: None

you can use either