Dynamic Resource Scheduler
Whats New!
User Experience Changes
Security and Authentication
Modules and Utilities
Cyclical Scheduling - Configuration Interface
Cyclical Scheduling - Now Bulk Scheduling
Resource Quotas Improvements - Percentages
Architecture and Scheduling
Configuration
User Guides and Help
Get to Know Dynamic Resource Scheduler
How Does Dynamic Resource Scheduling Work
Speaking the Language of Scheduling
Navigating Dynamic Resource Scheduler
How your Data Links Together
Managing your Organisation
Viewing your Data
Your Customer Data
Your Service Orders
Your Jobs
Your Workers and Resources
Manage Your Tasks
Actioning your Jobs and Tasks
Job Templates
Find A Jobs Possible Workers
Locking Your Jobs
Create a Follow On Task
User Queues and Organising Your Tasks
Schedule and Organise
How to Optimise Your Scheduling
How to Schedule Manually
Scheduling Mutliple Jobs at Once
Reassign and Reschedule your Tasks
Managing Your Time and Durations
Managing your Comments and Contacts
Using Bookmarks to Drive Efficiency
Managing Your Job Status
Visualising Your Planning
Workers and Resources
Advanced Data Management
Creating Unavailability in your Workforce
Adding an Unavailability to an Individual Worker
Creating Unavailabilities for Multiple Days or Workers
Maps And Journey
Using Maps to Visualise Your Data
Using Maps With Your Data
Learn about our Closest Function
Your Journeys
Meetings and Non-Productive Planning
Administer Your Scheduler
Managing Your Organisations and Agencies
Managing Your Custom Data
Managing your Contracts
Customising Your Experience
Managing Depots and Starting Locations
Managing Diary Bookmarks
Managing your External Chart Views
KPI Settings
Managing Your Priorities
Learn about Sectors
Managing Your Follow On Templates
Get To Know Your Working Time Calendar
Managing your SOR Templates
Managing your Job Templates
Managing Your Vocabulary
Managing Your Bookmarks
Manage Your Customer Templates
Get to Know Import and Export
Managing Your Tenant Code Rules
Managing your Order Templates
Managing Your Unavailability Reasons
Get To Know Your Working Time Calendars
Managing your Worker Templates
Releases and Readiness
DRS 6, DRS 5.7 and Job Manager
User Guides and Help
Get to Know DRS
Dynamic Scheduling - How does it work
Navigating DRS
Vocabulary and Concepts
Customers
Orders
Jobs
Scheduling Jobs
Job Functions
Workers
Views
Object Inheritance
Agencies
DRS Modules
Scenario Based Planning
Managing your SMS Service
5.7 Documentation
Technical Documentation
Release Notes
DRS 6.1 Release Notes
DRS 6.1.22 - February 20, 2026
DRS 6.1.21 - September 10, 2025
DRS 6.1.20 - April 20th, 2025
DRS 6.1.19 - 11th April, 2025
DRS 6.1.18 - 13 February 2025
DRS 6.1.17 - 20th December 2024
DRS 6.1.16 - November 8th, 2024
DRS 6.1.15 - October 10th, 2024
DRS 6.1.14 - 6th September 2024
DRS 6.1.13 - 9th August 2024
DRS 6.1.12 Release Notes
DRS 6.1.11 Release Notes
DRS 6.1.10 Release Notes
DRS 6.1.9 Release Notes
DRS 6.1.8 Release Notes
DRS 6.1.7 Release Notes
DRS 6.1.6 Release Notes
DRS 6.1.5 Release Notes
DRS 6.1.4 Release Notes
DRS 6.1.3 Release Notes
DRS 6.1.2 Release Notes
DRS 6.1.1 Release Notes
DRS 6.1.0 Release Notes
DRS 6.0 Release Notes
DRS 6.0.0.0 Release Notes
DRS 6.0.0.1 Release Notes
DRS 6.0.0.2 Release Notes
DRS 6.0.0.3 Release Notes
DRS 6.0.0.4 Release Notes
DRS 6.0.0.6 Release Notes
DRS 6.0.1.0 Release Notes
DRS 6.0.1.1 Release Notes
DRS 6.0.1.2 Release Notes
DRS 6.0.1.3 Release Notes
DRS 6.0.1.4 Release Notes
DRS 6.0.1.5 Release Notes
Kirona Housing
Job Manager 9
Job Manager 9.3.0 - October 2024
Job Manager 9.1.0 - December 2022
Job Manager 9.2.0 - November 2023
Release Notes Disclaimer
Administering your Field Service Products
Supported Versions Policies
Contents
Contract Rename
Purpose
This article will help you understand how to best configure the Contract and Contract Prefixing values within DRS.
Contract rename allows you to prefix certain aspects of the system depending on the contract used. This will allow you to differentiate between different orders, properties and SORs based on the contract they are associated to.
DRS > Configuration > Contract Rename

Configuring Contract Rename
Clicking the Add or Selecting an existing Contract and clicking the Edit button will allow you to specify the contract and prefix of a contract.
In both cases, you will be presented with the following screen.

As part of your DRS configuration, you will need to maintain an entry for each CONTRACT value within the Business Data fields within this screen.
What is Contract Prefixing?
Prefixing is commonly used to allow a single set of data to be configured within DRS to create multiple different scheduling solutions.
A common usage of prefixing is to apply SOR Prefixing. SOR Prefixing will allow you to maintain a single list of SOR's in your Works Management or Housing system, but based on the Contract provided, allow DRS to apply a different scheduling solution, perhaps defining a different Skill, or have the work delivered by Worker resources with a specific Team Ability value.
Prefixing Options
For each individual contract, you will be able to specify some Prefixing options. Leaving any (or all) fields blank, will result in DRS ignoring this possible prefixing option.
The three areas you can apply prefixing options to are:
- Orders
- Properties
- SORs
Prefixing is applied to these objects on the creation of the object, whether that be when the Order, Property or Job is provided through the API to DRS, or, when creating a new Object in DRS such as a Follow On or new Property.
Column Name | Description |
Contract | This is the Contract value that has been added to either the Customer or Order Business Data. |
Prefix | If Prefix Type is set to Simple = This will add this prefix value to all the orders, customers and SOR’s. If Prefix Type is set to Complex = Enter “None” as the prefix value and specify in the In/Out fields what prefixing you want (If any). This is the most common setting. |
Order In | When the OrderCreate request comes in from the housing management system, if prefixed with this value it will remove the value. |
Order Internal | This value will be applied to the Order to be visible in DRS. |
Order Out | This will add a prefix outbound on the Booking Confirmation. |
Customer In | When the OrderCreate request comes in from the housing management system, if prefixed with this value it will remove the value. |
Customer Internal | This value will be prefixed to the customer ID when identifying the Customer ID/UPRN in DRS. |
Customer Out | This will add a prefix outbound on the Booking Confirmation. |
Customer Out PDA | This will add a prefix outbound on the getSchedule response to the mobile system |
SOR In | This value will be stripped from the SOR when identifying it in the SOR templates. |
SOR Internal | This value will be prefixed to the SOR when using it in DRS. This value must exist then in the SOR Templates. |
SOR Out | This will add a prefix outbound on the Booking Confirmation. |
Agency | This is the Agency that it will match to, configured in DRS. |
Prefix Type | Simple = This is if you want a global prefix to be applied as specified in the Prefix option. Complex = This is if you want different prefixes to be applied (In/Out/Internal) as specified in the other values. This is the most common as is also used if you do not want any prefixing as the other boxes can be left blank. |