Rate Models
Summarize
Summary of Rate Models
Rate models are essential for deriving date-effective, criteria-driven hourly rates for calculating resource costs associated with projects or demands. Unlike standard labor rates, rate models can utilize up to ten attributes from predefined entities like projects, demands, users, and roles. Starting March 2026, you will be able to create rate models based on primary attributes to align with your organizational needs.
Show less
Key Features
- Rate Lines: A rate model comprises multiple rate lines, each representing a unique combination of criteria that defines the hourly rate for a resource, group, or role over a specific date range. You can create multiple rate lines for the same criteria as long as their date ranges do not overlap.
- Rate Model Processing: To calculate hourly rates, associate a rate model with a project or demand. If no rate model is assigned, the system defaults to labor rate cards. The model evaluates rate lines based on the requested criteria and returns the appropriate hourly rate.
- Evaluation Process: The system identifies applicable rate lines, checks for matches in the criteria, and processes them in order of priority. If multiple matches exist, rates are applied according to the number of hours requested within the specified date ranges.
- Creation and Modification: Users can create or modify rate models to set criteria and define rate lines based on specific attributes. Additionally, rate lines can be exported to Excel or CSV for easier updates and imported back into the model.
Key Outcomes
By utilizing rate models, ServiceNow customers can accurately determine planned and actual costs for resources, ensuring better financial management of projects and demands. The ability to customize rate lines based on various attributes and date ranges enhances flexibility and precision in resource planning.
Use a rate model to derive date-effective, criteria-driven hourly rates for calculating planned and actual resource costs for a project or demand.
Unlike labor rates, which are based on the user attribute only, a rate model can derive hourly rates based on up to ten attributes. These attributes can be selected from predefined entities such as projects, demands, users, and roles.
Starting March 2026 release, you can create rate models for resource assignments based on the primary attributes mapping to meet with the organizational requirements.
Rate lines
A rate model is a collection of multiple rate lines. A rate line is a unique combination of different criteria values that defines the hourly rate for a resource, group, or role for a specific date range. For the same set of criteria, you can create multiple rate lines with different rates for different date ranges provided that the dates don't overlap.
Rate model processing
The rate model associated with a project or demand evaluates the rate lines to find and return the hourly rate that matches the requested criteria. The rates are derived from the rate model during resource planning or allocation, and during time card processing.
The rate is returned in the functional currency specified in the matching rate line.
The following video describes how to set up a rate model and the evaluation method to find and return the hourly rate for a request.
When a rate is requested, the rate model uses the following process.
- Finds the rate lines in the requested date range and discards the remaining rate lines.
- Evaluates the identified rate lines
to find values matching the requested value in the first criteria column and discards the remaining rate lines.
If the requested value is empty, it checks for rate lines containing NULL.
If no exact match is found, it checks for the rate line having the value
All other (*).The evaluation is repeated for the other criteria columns in order of priority until all criteria columns are processed.
- Returns the rate if one or more rate lines match the request.
-
If a single rate line is found, the corresponding rate is returned.
- If multiple rate lines are found, the system determines the number of hours in the request that applies to each rate.
- For example, say the rate requested is for resource allocation from July 1 to July 30. The rate model has one rate from July 1 to July 15 and a different rate from July 16 to July 30 for the same set of criteria. The rate model applies the first rate to the requested hours for July 1–15 and the second rate to the requested hours for July 16–30.
If no rate lines match the request, then the request uses the default rate card.
-