Dear all,
if I look at the resource overload report, then it produces new set of entries for every working day of a resource.
Is there any way to tweak Spider to create only one entry for a the whole period, when resource overload is caused by the same factors?
In my case I would like to receive only one entry from 03.02.14 - 07.02.14
Rafael,
Thanks, I have downloaded the file and looked at it.
But agree, that searching at the negative value of quantity of all of the available resources is not the same as getting report about just overloaded resources. These are slightly different reports.
So, may be we can ask Vladimir to consider to have an option to consolidate records in the resource overloads report in such a way, that if a group of resource overloads are caused by the same reason (same rresource, same resource availability, same activities, then these records would be shown as one record, rather than many).
Regards.
Evgeny
the media fire link, which you have posted does not work, can you re-post it please?
Totally separate question: how do you use spider in the environment, when everybody around doesn't? You must be doing a lot of explanation in order to make sure, that your stakeholders agree to use Spider?
Rafael,
the medialfire link, which you have posted does not work, can you reposte it please?
Totally separate question: how do you use spider in the environment, when everybody around doesn't? You must be doing a lot of explaination in order to make sure, that your stakeholders agree to use Spider?
P.S.
By the way, I have submitted a Spider Project wikipedia article for approval. Once it is approved, I am planning to invite everybody, and definitely yourself to contribute to it.
https://en.wikipedia.org/wiki/Wikipedia_talk:Articles_for_creation/Spider_Project_(software)
Rafael,
thanks. But the question is still:
So in my case I think it would be much more informative to receive the following table
Regards.
Evgeny
Evgeny,
Managing resources is not always as simple as clicking the mouse or as if a cooking recipe, you might still have to execute some control as to improve what the resource leveling algorithm determined, it is limited by constraints you might release, it is of much value but some decisions must be made by the manager not the computer. Therefore at times I compare unleveled schedule to leveled schedule and look for over-allocations, here another field of much help is delay reason.
Managing of resources is better done by an in-house planner and his team, those that know better the schedule and to whom activities have real meaning rather than abstracts. Using optimization algorithm on every update can change activities sequence more than needed, stability of the activities sequencing is something you got to manage.
By the way, this is how I would like all my jobs be managed but local practice is poor, perhaps due to prevalence of poor resource planning software. Many do not realize how big a difference the tool can make; like running on foot against a Lamborghini, but they do not know the existence of the modern car, they still move on bare foot.
Best regards,
Rafael
Rafael,
thanks.
One can say, that there is not much use in them, since Spider would take care to make sure, that there are no overallocations.
In Microsoft project one can look at resource usage report and there it provides quite a good view on which resources are overallocated (but MSP is not good in automatically resolving these overallocations)
Regards.
Evgeny
It looks like the report is designed to identify continuous ranges, can be hours, minutes or days. Therefore if you define the resource to work non continuous hours instead of 24/7 the interruption will be shown at least once every day.
The following figure shows what happens when using 24/7 calendars and true continuous over-allocations, but I do not think you want to do that.
The report is great for finding over-allocations that are less than one day but for larger it might be easier at looking at the diagrams rather than at the table. To find over-allocations as small as 1 hr on the diagrams require expanding the timescale to hours and scrolling a long way, not a good idea. Over-allocations do matter, no matter how small, as it means the schedule is not feasible as long as there is a single over-allocation.
Imagine expanding following figure to display hours and then scrolling to visually find small over-allocations. For each resource doing the same hundreds of times.