READ THIS FIRST - rpDashboard Administration Overview
V1.2 6/14/11 PMe
There are four basic administration actions within a supervisor's rpDashboard™
A supervisor can perform any one of the following actions within their rpDashboard (generally these actions would be for people and relationships within the "reports to me" section of their rpDashboard):
Action 1. Edit or change any work role name as situations or changes may require (not shown on above graphic). Note: this changes the work role's name only, and effects no changes regarding the person in the work role relationship.
Action 2. Add a new work role relationship with a new person, who is not being transferred from another rpDashboard. Reminder: one person can have more than one (different) work role and one person can be within one or more rpDashboards.
Action 3. Delete a work role relationship with a person. This would typically be used when a person is leaving the organization, such as voluntary or involuntary exits. Please use extreme care if the person is being transferred to another supervisor's dashboard, by so indicating when asked to do so during this process! (See following item C.)
Action 4. Transfer a person to another supervisor's rpDashboard. This is a two-step process. First delete and remove them from dashboard and so note that this is a "transfer" within the process when asked. This places them into "transfer pool." Second, "import" this into the applicable, new supervisor's rpDashboard.
The above graphic illustrates each of these actions. The following information provides more basic orientation and each offer links to a separate, more specific instructional lesson for each of these actions.
Action 1. Editing work role names within the rpDashboard.
You can change or edit the name of any work role title within an rpDashboard. Doing so will not effect the person within the applicable work role relationship.
Action 2. Adding new person and new work role relationship.
A new person and work role relationship can easily be added to an rpDashboard. Keep in mind, to address workplace realities, one person may have multiple, different work role relationships; and thus, may be within one, or more, rpDashboards.
This function is for those persons who are NOT being transferred from another supervisor's rpDashboard.
Persons being transferred into an rpDashboard from another supervisor's rpDashboard should be done so in the manner described in Step #4 below.
Action 3. Deleting a person and the work role relationship (note: not transferring them to another rpDashboard, but rather deleting them from an rpDashboard and the rpPaQ system)
Whenever people are exiting the organization, or for whatever reason need to be removed from further rpPaQ™ involvement, this action of "deleting" should be chosen.
This action should not be chosen for those persons who are presently, or in the near future, being transferred to another supervisor's rpDashboard. Generally, this action is for a worker who is leaving the organization.
Indicate during the process if the reason for doing so is:
A) a voluntary exit (in other words, the reason for the exit is based solely upon the worker's decision to leave/exit the organization)
B) an involuntary exit (based upon an organizational decision the worker should no longer be in the organization and its work role)
C) an internal transfer from one supervisor's rpDashboard, to another supervisor's rpDashboard (If this is the case, please follow the procedures in the following step 4 and related instructions.)
1. Never simply delete a person who is being transferred to another supervisor's rpDashboard without so noting during the process that you are doing so as a "transfer" (as per the following step 4 and its related instructions).
2. Care must be exercised if the person being deleted is themselves within a supervisory work role, and with their own rpDashboard and its "reports to me" relationships, to ensure future systems and information integrity.
Note: whenever persons are deleted, they and their related rpPaQ information are archived.
Action 4. Transferring a person to another supervisor's rpDashboard is a two-step process.
There are many reasons that it may be preferable to use the two-step process to transfer a person from one rpDashboard to another. This is especially true when there is a desire to have continuity of rpPaQ-related information and history related to the person, and even more so when the person being transferred is in a supervisory role themselves, thus have their own "reports to me" relationships that need to be correctly addressed.
The two-step process is:
A) First remove the person by "deleting" them and the work role relationship. When asked to do so during the process, indicate they are being transferred to another rpDashboard from the present/original rpDashboard. Once this is done, they are placed in a "transfer pool" (an invisible database for this purpose). Doing so makes this person and their information available to other rpDashboards within a licensed rpPaQ community. If the person being removed are themselves a supervisor, choices will be offered as to system instruction for their reporting relationships.
B) Once they have been removed from the original rpDashboard (and only then), this person will be available to be imported into another supervisor's rpDashboard.
G E N E R A L T A L E N T LLC All rights reserved 2011 Patents & patents pending. License required for any usage or applications.