Calendar Events - Standard and 24 hr. mix 2

[remeng]

All;

I have a project were I have a test setup that can only occur from M - F within an 8 hr period (8 am - 5 pm). I then have a second event that is proceeded by the setup time. This second event is the test cycle time. The testing cycle time is able to run for over 24 hrs without stopping. The only constraint for the test is that it can not start on Saturday or Sunday but can run those days (set and forget automation). What I am having a problem with is that when I assign a resource for the cycle time and set it to 24 hrs. It is not calculating the end day correctly.

MS Project 2010 scale is in Days

Setup Event (2 hrs = 0.25 days) - Standard Calendar
start Friday 8/8/13
End Friday 8/8/13
Technician only works 8 hr days
This event is calculated correctly

Machine Cycle Time (5 days) - 24 hr. Calendar
Start Friday 8/8/13
End is expected to be Tuesday 8/13/13
End is showing as Saturday 8/10/13
Tester can run 24 / 7
This event is proceeded by the setup event

What am I doing wrong?

Mike

 

[JulieInMaine]

Hi Mike,

When you said the machine cycle time duration is 5 days - Project interprets a day = 8 hours. So 5 days is 30 hours hence the finish on Saturday. Does the machine cycle time take 120 hours? if so, enter 120 hours in the duration or 15 days.

Julie

 

[remeng]

Hi Julie,

Thank you for the quick reply. Let me try and clarify what is need.

The Test take 5 day total and is able to run for all 24 hours in a day. For instance, if the test is started on Monday at 8 am, it will end on Friday at 8 am. So if we use a military calendar, here is how the schedule would look as run time. The test can only start M - F from 8 am - 5 pm, but can not be started on Saturday or Sunday. The other condition is while the test can not start on Saturday or Sunday, it can end on any day of the week as well as any time in the day. Another example would be to have the test start on Friday, run through the weekend and end on Tuesday. If this doesn't make sense let me know.

Monday
08:00
09:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21:00
22:00
23:00
24:00

Tuesday

01:00
02:00
03:00
04:00
05:00
06:00
07:00
08:00
09:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21:00
22:00
23:00
24:00

Wednesday
01:00
02:00
03:00
04:00
05:00
06:00
07:00
08:00
09:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21:00
22:00
23:00
24:00

Thursday
01:00
02:00
03:00
04:00
05:00
06:00
07:00
08:00
09:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21:00
22:00
23:00
24:00

Friday

01:00
02:00
03:00
04:00
05:00
06:00
07:00
08:00

 

[JulieInMaine]

I understand. Here's my suggestion. Break the task into two pieces - I am assuming the 'start test' is requiring human intervention - but once started, the test runs 25-7. The start test can use the regular project calendar (m-f 8-5). The machine test (non-human) can be assigned the 24 hours calendar as a task calendar. However, the issue of duration still applies. If you enter a 5 day duration to the machine test -= to project that equals 40 hours (5*8). If the machine test takes 5 24 hour days - you'll need to set the duration appropriately.

 

[remeng]

Currently the test is in 2 sections. There is the setup test and the test cycle time. The problem that I am running into is the cycle time criteria that I a fore mentioned. When I start the test on a date were the test will end on Saturday or Sunday, it will roll the hours into Monday which will completely through off the schedules. I need to be able to start the test on M - F but not Sat or Sun. I then need to allow the test to conclude any day of the week.

 

[JulieInMaine]

Are you applying the 24 hours calendar as a task calendar to the test cycle time?

 

[remeng]

Yes

 

[JulieInMaine]

Is this a file that can be zipped and emailed to me to take a look? If the test cycle time has the 24 hours calendar applied as a task calendar with no resources assigned, it should be working based upon that calendar.

 

[remeng]

I think I figured it out. Could you check to see if this will work for you too? Here is what I did.

Machine Time = 5 days (can start M - F, but only can run S - S)

Task Name = Machine
Resource 1 Name = M - F
Resource 2 Name = S - S
Resource 3: Machine Cycle Cost

M - F Parameters
Standard Calendar
Work

S - S
24 hr.
Work Time on Saturday and Sunday = 12 am - 12 pm
Work

Machine Cycle Cost
Standard Calendar
Material
$28/day


Task: Machine
Duration: 5 days
Resources: 1,2, & 3
Start date: Friday
End Date: Tuesday

Total Cost for 5 days equals $140

Thanks,

Mike

 

[JulieInMaine]

I don't follow your example - but it if is working for you - great. Be aware that Material resources (I think you Machine Cycle Cost ?) cannot have a calendar. I guess I'm still a bit baffled as to why you don't assign a modified 24 hours calendar to the cycle time task - it looks like you are trying to use resource calendars instead? Again - if you are getting the schedule you need - great.

 

[remeng]

Nope it doesn't work when calendar's are involved...

 

[JulieInMaine]

Not sure what is going on -- but it sounds as though you have it sorted out.

 

[remeng]

Late last night I came across a solution. If you add an e before the duration such as days, hours, minutes to edays, ehours, eminutes; it will allow MS Project to count the days exactly as indicated. For example if the task is scheduled for 7 days and starts on a Friday, 7 days = Friday of the following week. If you set the duration to 7 edays, the test ends on Thursday instead.

 

[JulieInMaine]

Yes, elapsed duration (signified by the "e") measures duration in clock time - not working time as defined in the project calendar. The only caution is assigning human resources to elapsed day tasks - they will be scheduled for 24 hours per day for the duration of the task. This will increase your work estimates as well as drive up cost estimates.

 

[remeng]

That is a very good point. Currently I have 2 tasks for each test. The first is the setup time with the labor rate. The second is the actual machine run time with the machine rate per hour. The second task will not have a labor rate assigned since the machine will run on its own. Do you see any issues with that?

 

[JulieInMaine]

You can set the machine up as a work resource and assign the hourly rate to the machine resource. Another option is material resource assigned at 1/hr - variable consumption rate.

 

[SkipVought]

Julie,

That was a nugget! Thx!

Skip,

_{Just traded in my old subtlety...
for a NUANCE!}

 

[JulieInMaine]

Glad you found it helpful, Skip.