Evgeny,

we discuss actual data. And in my example with meeting I don't know what time will take the travel for all meeting participants (and I did not mean meeting with the customers).

Spider Project is used for management of all consruction projects (about 300) for preparation of 2014 Winter Olympic Games. We helped with the management of this portfolio. In one of reports it was written that some bridge is 90% ready and the photo was attached with cars moving on this bridge in both ways. When I asked why this bridge is only 90% ready when it is functioning, the answer was that everything is ready except getting the formal permission to build this bridge.

It is not right but it happens. We do not plan this way but permit people to enter actual data the way it really happens. It could not be calculated. If activity is actually finished and following activity can be performed, remaining work on finished activity may be entered as resource assignment duration.

Vladimir,

What you say it makes sense to me, just look at the following reference.

http://www.nflaace.org/index_files/john_orr_cost_loaded_schedule_updating_pdf.pdf

Spider allows for The Great Divorce. 

I believe we shall look for ways to keep the historic records in practical ways that in case of a claim after an analysis can tell us what really happened but without unneeded granularity nobody is to follow.

Entering on the CPM database resource hours at the individual resource level can be too much, it is enough to report man-hours per activity, but man-hours for every named resource is too much. Also it might be better to report actual hours per update period but not the per-hour detail, leave it to the payroll records. Even if using a time card software it shall condense the data to manageable scale at the activity level. 

On a Condominium Building we usually have a cement plaster activity per floor, say 20 floors 20 activities, but we want to track cost for a single cost account, same as hours, if for 20 individual activities is too much, just imagine tracking hours per named resource on each activity, even per trade is too much. At times your plan is for 10 masons, 10 mason helpers, 4 laborers but in actual execution the composition of the crew varies every day.  Keeping such level of detail on a CPM just because the database can handle it is nuts. Weekly total man-hours for labor resources per activity shall be enough while for future work planning we still need the detailed crew composition. 

We usually update our schedules at end of the month but at the cutoff date we do not have resource hours until the following week payroll period ends, the same goes for other costs, many entered on the system weeks after, when invoice is received.  Most of us do not implement job costing at the PO but at the Invoice, very frequently they do not match and making adjusting entries on the system would be too much.  We should be able to update schedule for status and time projections purposes but latter to add some costs and resource hours after schedule update.  The data entry screen for each purpose shall be simplified, a single table with hundreds of columns drives me crazy. 

Always keep it simple enough, otherwise no one will implement it.  Needless to say this posting represents a change of mind from my prior postings, to me a search for constant improvement that will never end. 

Best Regards,

Rafael

how do you do this on your real projects? Do you just manually check, that this misalignment between resource work and project duration is never entered by those responsible?  

• I use Include in Actual Data Input Table without Show Assignments option. In this way the software assumes the quantities as per activity duration avoiding any such conflict.  I know it does not represents true actual resource usage. We look at the CPM tool more as a forward looking tool rather than as a claim tool that requires too much granularity.  
• Even when resource loading some of our jobs we do not keep track of resource usage via the CPM database.  Spider method is easy but it still requires a lot of work, time most contractors do not want to spend. I believe for the sake of keeping contemporary records it is worth it. We shall look for methods that reduce required data entry while keeping the record close enough to actual performance. If an Actual Data Input record have significant distribution difference then splitting the record in several chunks shall give us enough approximation to reality. To the minute records are not needed and will not add real value.  
• Spider provides for an easy method to enter actual resource hours but there is still some room for improvement. You have just mentioned something that can be improved, why allow human errors that can be detected by the software?
• For your knowledge in actual practice at home we are usually required to use P6 a software that is so bad at resource loading that the mere initial data entry promote to avoid resource loading on our jobs, not to mention its inability to model many real life resource allocations such as variable quantity and variable workload as to avoid idle resources.  Because PMs are concerned about cost, they must handle the missing functionality using manual calculations of their own. Under these circumstances we consider resource loading of not much value as to justify it, better than wasting time on something useless. 
• In the case of a claim then with the use of the Job Costing records we can find out total resource hours actually used and determine if there was pacing or not. But these records submitted after the facts can be questioned, matching standard job cost accounts to individual activities is no easy task, at times impossible, better if submitted on every update within the CPM database. 

Re "The fact that resources and activities can have different calendars and that actual performance might have broken scheduled work time makes it to me a bit complicated"

I agree with you, that calendars shall be taken into account only when we are talking about the activities ahead of Data Date (in the future). When it comes to actually performed work, tool shall allow to overwrites this. Just because the reality always overwrites plans.

• The following is a screen that graphically display how resources working on the same activity at different hours (different shifts) are taken into consideration to estimate activity remaining duration.
• 
• But same as calendars are taken into account for remaining durations maybe actual work hours shall be taken into account for actual activity duration calculations. The problem is on how to enter the data without use of time card software. Some assumptions shall be made as to simplify data entry. I suggest for the reporting period the average work hours per day to be equally distributed from start of resource work hours in the direction of end of day, if not enough the remaining in the direction of start of day. Will not be an exact distribution but will keep on record the work-hours during the period on contemporary updates. 

Rafael

Evgeny,

I agree with you, I am trying to find a logic on how it shall be done. It shall be easy to program the software to automatically change the activity dates to prevent resource usage outside activity range.

I am having issues on how to date activity duration shall be calculated and how this impact remaining duration calculations. The fact that resources and activities can have different calendars, that actual resource performance might have broken scheduled work time and that activities might progress without resource loading makes it to me a bit complicated.

For a start I would like to understand actual algorithm for such calculations. 

Best Regards,

Rafael

Evgeny,

Not only you can edit resource finish to finish after activity finish but also to start before activity start. 

An update record at the Actual Data Input Table consists of one activity line to report progress under no resource presence and a separate line for every resource usage being reported.

I believe that maybe: 

1. The Actual Data Input Table shall accept multiple update records for a single activity. 
2. For every record each individual resource duration shall be computed based the activity as well as resource calendars unless the user manually override it from 0 up to the maximum number of natural hours between start and finish time. We got to realize work is not always realized within the as planned calendars, overtime occurs even when not planned, but actual total time shall be reported as it happened. There is no need for every single hour be specifically entered, it is enough to enter totals within a small period and distributed on some daily average. 
3. To date resource hours will be computed by adding resource records while activity hours shall be based on a different roll-up algorithm. 

Hope this helps to communicate some ideas fresh from the oven, not fully cooked, one more turn and back to the oven. 

Best Regards,

Rafael