- My View
I was recently playing with Resource Management and an interesting question came up. Lets say I've already planned and allocated resources, but then stuff happens?
Someone quits, or goes on leave, or something unexpected. I've committed ResourceX at 20 hours a week. How can I recalibrate? Backfill the resource by re-assessing availability for the team.
Can the tool cover this use case?
In Helsinki I don't see a built-in solution, or a workaround I would recommend if the RPLN plan has a state of 'Allocated'. Here are 2 messy, not-recommended options I see:
In Istanbul, this can be done. Istanbul features a change in Resource Plan states and features. Below is an explanation of these changes. FYI I will be creating an Istanbul Release post in the next couple of days listing major changes and known major INT's.
Resource Plan State Model Change
The following changes have been introduced in this release
•Confirmed State – A new state, ‘Confirmed’ has been introduced in this release. If a resource manager/steering committee want to commit/block/confirm resources for future projects/demands, it can move the resource plan to ‘Confirmed’ state.
•Allocations records and states
•Requested Allocations – When a resource plan is in planning state, requested allocations are created. When the resource plan moves to requested state, the requested allocations are retained as is. Please note, until last release, soft allocations were being created when resource plan was moving to requested state. The soft allocations will no longer be created in requested state
•Soft allocations – When resource plan moves to confirmed state, soft allocations are created
•Hard allocations – When resource plan moves to allocated state, the soft allocations will be converted to hard allocations
•New actions - Confirm and Confirm & Allocate
•Confirm – Confirms the resource plan; resource plan moves to confirmed state
•Confirm & Allocate – If a resource manager wants to directly allocate resources ( when resource plan is in ‘Requested’ state), she can take ‘Confirm & Allocate’ action, that moves resource plan to allocated state directly form requested state
•Modification in confirmed and allocated state
•From this release, a resource manager is allowed to modify a resource plan in allocated state ( and in newly introduced confirmed state).
•She can modify, create and delete resource allocation records
•If she changes, the resource plan header, a. All resource allocations ( soft/hard) will be deleted. b. requested allocations will be re-created with changed values. c. Resource plan will move back to requested state.
ServiceNow PPM/PPS Specialist
Yes... I was worried it would come down to the project user manipulating line item records.
Is there a better way to handle these types resource changes mid-project with Jakarta or Kingston? Just curious the best way to handle if someone from a Group (resource pool) leaves that group and a new person joins, can we "swap" them 1-for-1? Or do you just have to cancel the Resource Plan and create a new one?
Well, the resource plan is the process of asking for and committing resources, right?
So the Resource Manager who's looking at the submitted resource plan ultimately allocates the resources. But the interface provided feels extremely "heavy", because they're editing line items.