Anand,

Two situations where I have used priority codes to level:-

1. Shutdowns where the removal activities prior to the inspection activities share the same resources as the re-install activities. The inspection activity will determine the scope and time required to overhaul the piece of equipment (valve, vessel, etc). Due to limitation on space at the workface it is not possible to increase the resourcing and it becomes crucial to have the removal and inspection activities completed as early as possible in the shutdown so the correct timing of the resource required to re-install the equipment can be establish and leveled to ensure the plant is operational when required. Using a priority code to give preference to the removal activities ensures we establish the true scope of the overhaul process as early as possible so we can better plan the re-installation and commissioning. Quite often the critical resource in both the removal and re-installation is the crane required to lift the equipment.
2. A Project Group that contains separate independent projects that draw from the same limited resource pool. Quite often senior management will set absolute priorities on some projects at the expense of the others based on contract conditions or type of project (e.g. internal versus external). In this case using a priority code allows you to reflect their desires whilst still allowing the system to fully utilize the available resource and report the impact of their decisions on the outstanding projects. e.g. Design department that has to satisfy the projects in hand but still needs to support the tendering process and their own internal process improvement. Very useful when the organization has imposed head count limits and a policy of not using external resource. With allow you to quickly reflect the impact on end dates due to the ever changing priorities.

Whenever multiple activities with a resource conflict that are scheduled on the same end dates, are on the critical path so they have the same float, P3 will ultimately default to allocating the resource using first in, best dressed i.e. activity id. If you want some control over which activity should get the resource, a priority code will allow you to achieve this.

A priority codes can be used to complement the late start and total float.

Anand,

Please explain the the point of a schedule with no logical links? Should you attempt to resource level such a schedule, it would schedule the longest activities with the highest priority first, down to the shortest activities with the lowest priority last. At the end of the day there will be no sense. You obviously do such a schedule with constraints?
Also there will be no sense in trying to resource level a schedule with one logical chain.

The purpose of resource levelling is to minimise the maximum limit of resources, as this will reduce P’s & G’s. Thus resources levelling is normally used in projects with multiple logical paths, with differing total float.

Steve,

The leveling priority should be set at the activity level, SureTrak does have a standard field called priority and it is by activity. P3 has a leveling constraint called Imediate Priority which will force the resource to be assigned on the scheduled dates (ie can NOT be delayed by the levelling process) and again this is by activity.

As P3 will not allow you to create a code with a blank value the only options is to create a 0 value and use either:-
1. Fill Cell
2. Global Change
3. Import/Export
4. ODBC drivers to Excel/Access
5. Ra
or 6. Batch

to change the unassigned priority code to 0.

A filter or organise and fill cell should take a couple of minutes at most and is less error prone than the others mentioned.

Could you not populate your code using global change, rather than exporting to Excel ?

Also, should priority not be a resource code ?. I seem to remember P3 already had something like that in the resource definitions, or perhaps it was SureTrak.