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.

Data Date Time

2 replies [Last post]
Mike Testro
User offline. Last seen 5 weeks 4 days ago. Offline
Joined: 14 Dec 2005
Posts: 4418

Hi All

I was reviweing a contractor's schedule as part of a delay analysis exercise when I noticed that the time set on the data date progress line was 08:00.

The work calendar is due to start on 07:00 so for every progress report one hour is lost on the programme.

It could have been much worse if the data date time was 12:00.

I suggest that the time on the data date is set earlier than the dominant work patter start time.

Best regards

Mike Testro

Replies

Ronald Winter
User offline. Last seen 3 years 6 weeks ago. Offline
Joined: 4 Jan 2003
Posts: 928
Groups: None

Oracle/Primavera’s definition of a Data Date is the first moment that new work is able to start or resume.  It is not the same thing as a status date. 

In Mike’s example, he is quite correct to request that the Data Date be set to 07:00.  I believe that P6 automatically sets it to 08:00 as a default.

Gary Whitehead
User offline. Last seen 4 years 46 weeks ago. Offline

Hi Mike,

 

I've always worked on the basis that the data date (& time) should be set to the last point for which you have progress information.

Hence if dominant work pattern finished at 6pm on a friday, my data date for a weekly update would be 6pm on a friday

 

Cheers,

 

G