If the user edits the Maximum Units field, then Microsoft Project 2000 will update the Units value of the corresponding row in the Resource Availability table. If the current date is outside the range of any period currently shown in the table, then the behavior is as follows:
n If the current date is before any shown period, then a new row will be added to the table with a From date of NA and a To date equal to the latest From date minus 1.
n If the current date is after any shown period, then a new row will be added to the table with a To date of NA and a From date equal to the latest To date plus 1.
n If the current date is between two shown periods, a new row will be added between the two rows, which chronologically bracket the current date. The new row will have a From date that is one day later than the To date on the previous row, and a To date that is one day earlier than the From date on the following row.
These two fields are now read-only, and will contain the values of the period in the Resource Availability table corresponding to the current date. If there is no contour, or if the current date is outside the range of any period currently shown in the Resource Availability table, then these fields will both contain NA.
When resources are assigned, the default behavior is basically the same as in Microsoft Project 98. That is, the default assignment units’ value is the lesser of either 100% or the value of Maximum Units. The value of Maximum Units for the assignment is calculated as the value from the Resource Availability table for the period, which corresponds to the Start date of the assignment, except that if the value from the table is 0%, then 100% will be used (since it makes no sense to have a default assignment of 0%).
For example, consider a resource with the following contour:
|
Available From |
Available To |
Units |
|
NA |
7/1/98 |
75% |
|
7/7/98 |
7/14/98 |
125% |
|
7/15/98 |
NA |
100% |
Table 3
If the resource is assigned to a task that starts on 6/25/98 and ends on 7/15/98, the default assignment units will be 75% over the span of the assignment.
If the resource is assigned to a task that starts on 7/7/98 and finishes on 7/15/98, the default unit assignments will be 100% over the life of the assignment (100% is less than the Maximum Units of 125% that would be calculated as of 7/7/98).
If the resource is assigned to a task that starts on 7/5/98 and finishes on 7/15/98, the default unit assignments will be 100% over the life of the assignment (the Maximum Units would be calculated as 0% on 7/5/98, since 7/5 falls during a gap in the availability periods, so 100% will be used for the unit assignment value).
|
|
If a resource is based on a “split shift” calendar such as the Night Shift base calendar, there may be cases where the unit assignment value is not calculated as desired. A calendar must be set up with the earliest period in the day listed first even though the resource’s workday really begins before midnight, whereas the From and To dates in the Resource Availability table always begin/end at midnight. |
In the Resource Graph view, the Availability detail item has been renamed to “Remaining Availability” for consistency with the Resource Usage view. In addition, detail items have been added for Work Availability and Unit Availability.
|
|
Try This: Setting Resource Availability Do the following exercise to understand how user’s might |
1. In a new project create a two-day task.
2. Create a working resource and assign it to the new task.
3. In the resource information dialog box for the resource created in step 2, click the General tab.
4. In the Resource Availability section, change Units to 50%. Do not change anything else.
5. Notice that your resource is now over allocated. Attempt to level your project.
Where you able to level your project? If not, why?
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.
