Resource Management Configuration
About 17% of the CIS-SPM exam — see all 10 domains.
Balances the supply of people against the demand for work.
Resource plans vs. resource assignments. Historically work was resourced via resource plans (request a role/group/person for a period and effort). Starting in Utah and maturing through Vancouver/Washington, ServiceNow introduced resource assignments (Resource Management Workspace) as the modern way to manage resourcing: attribute based, with a heat-map view of availability by allocation level. Zurich states that resource plans will no longer be available for new customers in future releases. Know both models; the exam spans releases.
Allocations. A classic resource plan moves Planning → Requested → Confirmed → Allocated → Completed (or Rejected, Canceled). Confirming a plan creates soft allocations (temporary bookings with no calendar events); allocating it converts them to hard allocations, after which the resource is not available for other plans (Confirm and Allocate does both). Requests can be for a group, a user in a group, a user, or a role. The allocation spread is Even, Front load, or Smart Even Load. Actuals come from approved time cards.
Capacity planning. Capacity is a resource's available hours and is derived from the user's schedule, not from FTE (FTE only converts FTE requests into planned hours). Operational resource assignments for time off, training, or meetings reduce the capacity left for project work. Availability is capacity minus soft and hard allocations; forecasted utilization is (allocated + confirmed hours) / capacity and committed utilization is allocated hours / capacity. Capacity planning balances supply vs. demand across a portfolio using planning attributes as the common currency. A single screen lists resource plans with capacity, availability, soft & hard allocations, actuals, and % utilization. Strategic capacity planning is enabled by installing the Portfolio/Strategic Planning Workspace (Project Workspace and Resource Management Workspace are required).
Configuration topics likely tested: resource definitions, user/group capacity & schedules, availability and time-off, confirming, allocating and rejecting resource plans, the classic Resource Workbench and Resource Management Workspace, planning attributes, and how time cards roll up to actuals.
Sample questions from this domain
Three of the 51 in this domain, with the reasoning. The full set is in the question bank.
In SPM Resource Management, a Resource Plan is created against which kind of parent record?
- A. A labor rate card that prices the requested hours
- B. A cost plan breakdown for a single fiscal period
- C. A project, demand, or other planned work record ✓
- D. A resource group that owns the requested users
Why: Resource plans are created against parent work such as projects or demands, and any type of task (for example a project task or a change request) can be added to a resource plan. A labor rate card only supplies hourly rates for cost calculation, a cost plan breakdown is a financial record (a resource plan can feed a cost plan, not the reverse), and a resource group is the resource being requested through the Group field, not the parent work record.
Which Resource Management term describes the formal ask for a person or group's capacity over a time period?
- A. Resource request/allocation request ✓
- B. Resource event on the user calendar
- C. Hard allocation (Hard booking type)
- D. Resource aggregate capacity record
Why: A resource (allocation) request, captured as requested allocations on a resource plan, is the formal ask for a person's or group's capacity over a period. A resource event is the block of time that appears on the user's calendar after allocation, a hard allocation is the committed booking a resource manager creates later in the process, and a resource aggregate record stores calculated capacity and allocation totals. None of these is the request itself.
What is the difference between a soft allocation and a hard allocation in Resource Management?
- A. Soft is created when the plan is Requested and reserves capacity; hard is created when it is Confirmed and adds calendar events
- B. Soft applies to group resource plans and splits hours across members; hard applies to user resource plans with one named person
- C. Soft bookings carry planned cost from the labor rate card; hard bookings carry actual cost from approved time cards
- D. Soft is a tentative booking created when the plan is Confirmed; hard is the committed booking created when it is Allocated ✓
Why: Confirming a resource plan creates soft allocations, which act like temporary bookings and create no calendar events, and allocating it converts them to hard allocations that commit the resource and put the booked time on the user calendar. Submitting a plan (Requested) creates no soft allocations, and the Confirmed state produces soft bookings, not hard ones. The booking type does not depend on whether a group or a single user is requested, and it is not a split between planned cost from rate cards and actual cost from time cards.