Resources & Cost
A Shift
Shift is 24h limits for leveling; not a calendar; EPPM leveler ignores it
What a planner means
A resource shift is a 24-hour split of when a resource’s limits apply. Oracle: define shifts globally (Enterprise, Resource Shifts), then apply one or more to a resource. Segments must add to 24 hours, each at least one hour, start and end on the hour (8:00, not 8:30).
The resource calendar still decides when the resource can work. The shift supplies limits for that period when leveling calculates units and prices. Limits outside the shift definition are ignored. Minimum availability in every shift must cover minimum demand, or leveling cannot place the resource.
Oracle’s own note: this leveling-uses-shifts behavior applies only when P6 Professional is connected to a P6 Professional database. Leveling in P6 (EPPM) does not consider shifts.
A shift is not a calendar, not a resource curve, and not assignment lag. Calculate schedule does not read SHIFT.
XER
SHIFT (Shift Names):
| Column | Oracle label |
|---|---|
shift_id | Unique ID |
shift_name | Shift Name |
SHIFTPER (Shifts):
| Column | Oracle label |
|---|---|
shift_period_id | Unique ID |
shift_id | Shift Name |
shift_start_hr_num | Shift start hour number |
RSRC.shift_id is Shift. RSRCRATE.shift_period_id is labeled Shift (the period on that price/limit row). Stored hour numbering (0–23 vs 1–24) is unverified.
Microsoft Project
MSP resources have calendars and working times. There is no shift dictionary and no per-shift Max Units. Do not map SHIFT to a calendar or to Working Time.
Don't
- Treat a shift as a calendar or as
clndr_data. - Assume EPPM leveling honors shifts (Oracle: it does not).
- Invent
shift_start_hr_numencoding. - Map SHIFT to an MSP calendar or Working Time.