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.

Price/Time

1 reply [Last post]
Matthew Lin
User offline. Last seen 11 years 18 weeks ago. Offline
Joined: 20 Apr 2010
Posts: 20

Dear Planners,

 

Is there any one understand below message from Integrity checking?

 

2. Check Activity Resource Assignment for: Assignment with Price/Time = 0
>>>Warnings:
 Activity Resource Assignment: O16C10000060, C.BS-PLF - Not Fixed: Please examine and correct the data manually.
 Activity Resource Assignment: O16C10000070, C.BS-PLF - Not Fixed: Please examine and correct the data manually.

 

3.Check Activity Resource Assignment for: Assignment with resource Price/Time or Overtime Factor out of sync
>>>Warnings:
 Activity Resource Assignment: O16C10000060, C.BS-PLF - Not Fixed: Please examine and correct the data manually.
 Activity Resource Assignment: O16C10000070, C.BS-PLF - Not Fixed: Please examine and correct the data manually.

 

Thanks,

Matthew

Replies

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

I think that the error message is quite clear; go to Activities O16C10000060 and O16C10000070 and look at the resource tab.  Find activity resource C.BS-PLF and reference the Price/Time factor.  Also look at the Overtime factor. Manually enter the correct values.

 

The fields should not be blank nor should they be 0.  To compute duration for a fixed price, one must divide the price by Price/Time.  You cannot divide a number by zero.  It ends up being a really, really large number.  Good luck!

 

By the way, what is with these horribly large Activity IDs?  Who likes typing 12-digit numbers with an un-readable number of zeros in the middle?  The IDs end up taking up too much space on the screen and in reports.  Why not sick with four or five digits?  Think of the time you will save and the errors you will miss.  Just a thought...