Audience: Dispatchers, administrators
When a technician moves to a different city or an organization restructures, resources can permanently move to a new location. Once you initiate the transfer, you can assign unresolved future team-based commitments to resources at the old location.
Example
When a field technician applies to transfer to a branch in a different state, the regional manager migrates the technician's profile to the new territory. When the technician is flagged as being part of a heavy maintenance crew next Tuesday in their old territory, the manager removes them from that future crew shell. When they re-run the transfer, the system permanently moves the technician to the new OC.
Prerequisites
Before you start, ensure the resource isn’t assigned to any teams (crew shell) for the current day or any date in the future. If the resource is part of a crew shell, the system:
-
Aborts the transfer process.
-
Generates a system block notice with the date and name of the conflicting crew shell, so it can be resolved.
Follow the UI path
All instructions start on this system path:
Features > Core > Resource Management > Resources
Change operations centers
Important: Unlike a temporary resource loan, this fully removes the resource from their current OC and transfers their calendar, profile, and availability within the new OC. See Loan a Resource to another Operations Center.
To transfer the resource to a new OC permanently:
-
On the Resources page, in the Filters panel, enter desired parameters.
-
Click Search.
-
In the Scheduling resources list, on the left of a resource, click the Three dots menu > Change operations center.
-
In the Change operations center window, select a new operations center from the dropdown.
-
Click Save.
-
In the Warning pop-up, click Continue.
Note: There is a blocking notice if resources are a part of a crew shell today or tomorrow.