Resources Availavility

[ohmaps]

Let me know if it's possible to manage this information:

Resource A:with two statuses clean or dirty.

For use that resource it must be clean.

The cleaning of that resource has expiration time of 3 days (then
days after cleaning, that resource will be dirty and not available).



Regards

 

[Dave]

Not sure this is a Project question but anyway ...

What triggers the cleaning of a resource? If that is an activity that
can be recorded then the dirty point is simply 3 days after the end of
the cleaning activity.

If this isn't right could you post a better description please.

 

[ohmaps]

I will try to explain it better:

The task A requires the resource T, but this resource should be clean.

The task B is the T cleaning. In this example 7 days will be th
expiration time of that cleaning.

The question is that task A or any activity that requires T shoul
begin in the 7 days after cleaning (task B) or an aditional cleanin
will be done.

What we require is that I schedule task A when T is not available (n
clean) the system will notify it.


Regards

 

[Dave]

It's still not entirely clear. Is the cleaning periodic or is the
cleaning stimulated by usage of the resource.

If the cleaning is periodic then you could make a Task Calendar that
reflected the true availability of the resource.

If it is only after a certain amount of usage of T then you need to
break A up into the chunks that represent the amount of working time
available before it is needs cleaning again.

I think I'd schedule the cleaning activities and give them a priority of
1000 so that I can level Task A around that (remember to allow A to split).

 

[ohmaps]

Thank for your support.
I'll try again.

The cleaning is performed after each use or if the cleaning expires.

In the attached example I have included a new task, equpipment clean
and ready to use, with a duration of 7 days (expiration time) and a
priority of 1000to avoid rescheduling.

I understand that your idea is to link the next use to avoid that these
Next use begin after vie 05/12/08 11:00 (expiration of the cleaning). I
don't know if it's possible.


Idealy I want to avoid include a new task and we able to manage
resources and after that date and hour that resource should be not ready
to use if we not repeat the cleanig


Regards.


+-------------------------------------------------------------------+
|Filename: Doc1.doc |
|Download: http://forums.techarena.in/attachment.php?attachmentid=7449|
+-------------------------------------------------------------------+

 

[Dave]

Firstly I don't know why 20 is linked to 21 with a finish-finish
relationship.

Let's try this approach. I am assuming that there are two tasks (which
may repeat). There is cleaning and there is "using the clean
equipment". This equipment uses some resource which is a machine.

Start with a cleaning task. Make it priority 1000 as it has to be done
as a precursor to the "using the clean equipment" task.

Now enter the "using the clean equipment" task. Assign the machine
resource to both tasks. If you level the "using ..." task should occur
after the cleaning task.

Now if the "using ... " task is longer than 7 days, add a new cleaning
task. Add a link from the "using ..." task to the cleaning task with a
lag of 7 days. Make the new cleaning task priority 100.

Level but allow the application to split tasks, so that the "using ..."
task wraps around the cleaning task.

You will need cleaning after the "using ..." so create another cleaning
activity and link from "using ..." to this cleaning task.

Then, add your next "using ..." task and level around the fixed cleaning
tasks. The cleaning tasks should all have priority 1000.

Are you sure that there is no way that you can simply schedule cleaning
every 7 days as this would greatly simplify the production of this plan.
You are going to spend all your time managing the distribution of
cleaning tasks if you proceed down this route.

 

[ohmaps]

It doesn't work.

The problem is that these resource can be used in diferent task.

Then using that approach I don't avoid mistakes with that resourc
availavility.

I should be able to know if that resource is ready to use, that mean
clean and cleaned in the last seven days.

And after each use that resource should change it status to dirty t
avoid schedule a new task without cleanint it.

Regards

 

[Dave]

Well I think it ought to work. The only new thing that you have
introduced is the multiple tasks using the resource.

In algorithmic terms, if you start with a cleaning cycle, then you can
schedule the next usage cycle. If after 7 days that is not complete,
you then have to schedule another cleaning cycle which interrupts the
usage cycle and so on.

I can't see how there can be an easy way of scheduling this because of
the complexity of integrating the cleaning cycles with the usage cycles.

This could be done with VBA but that may not be a route you want to go down.

There are a number of factors which prevent a good answer to this at
this stage. I don't know how many usage tasks you have for example and
I don't know how long your overall plan is (although that is to a degree
immaterial as this is going to require a lot of manual tweaking).

You could try levelling the plan without any cleaning cycles. Then
determine when the first cycle is and insert that task. Level around it
and then determine when the next cycle occurs and insert another
cleaning cycle. This might be easier than trying to create complex
linkages between the usage tasks and the cleaning tasks.

How accurately do you need to schedule this? Do you have to book the
cleaning or is it always available to you. You know that at best you
have to have a cleaning cycle every 7 days. At worst, you have to have
a cleaning cycle at the end of every usage cycle. So the number of
cleaning cycles is dependant on the number of short usage tasks that you
have.