Rate Models
Summarize
Summary of Rate Models
Rate models in ServiceNow enable you to derive date-effective, criteria-driven hourly rates for calculating planned and actual resource costs on projects or demands. Unlike labor rates that rely solely on user attributes, rate models can use up to ten attributes from entities like projects, demands, users, and roles for more granular rate determination. This flexibility helps you accurately assign costs based on various resource and project criteria.
Show less
Key Features
- Rate Lines: A rate model consists of multiple rate lines, each defining an hourly rate for a resource, group, or role over a specific date range with unique criteria. Multiple rate lines can exist for the same criteria with different date ranges, provided they do not overlap.
- Rate Model Processing: By associating a rate model with a project or demand, ServiceNow evaluates rate lines to return the appropriate hourly rate during resource planning, allocation, and time card processing. If no rate model is linked, default labor rate cards are used.
- Criteria Evaluation: The system filters rate lines by requested date range and sequentially matches criteria columns, using exact values, NULL, or wildcard () matches. If multiple matches exist with different date ranges, rates are applied proportionally by date segments.
- Rate Line Management: You can create or modify rate models and rate lines within them to define rates based on criteria and date ranges. Rate lines can be exported to Excel or CSV files for bulk updates and re-imported to streamline management.
Practical Use for ServiceNow Customers
By configuring rate models, you gain precise control over resource cost calculation in projects and demands, improving financial accuracy and planning. The ability to define multiple criteria and date-effective rates ensures flexibility for complex organizational needs. Export/import features facilitate efficient rate line maintenance, especially for large data sets.
When implementing rate models, link them to your projects or demands to enable automatic, criteria-driven cost derivation during resource allocation and time tracking, ensuring your cost data reflects current and relevant rate structures without manual adjustments.
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.
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.
-