Example Configuration

Below is a sample configuration for Workforce and Talent Management

To implement Workforce and Talent management, you will need to plan out your program. It is perhaps best to start with a checklist and then compare that against what you already have In ASM. Below is the configuration that was placed in the product for ITIL V4 compliance. It may not all work for your organization and that is OK! Pull from it what is useful.

Contact Professional Services at [e-mail] if you want more information, details, or design specifics.

Part 1: Planning Checklist

• What does the Employee Journey look like? Will you want to manage all of it in ASM?

• What will be automated? Candidate Qualifications review (checklists?)

• Will you publish open roles to the internet or only to the portal?

• Who is on the hiring team(s)?

• Will you allow anonymous access to open roles?

• What data is required for an applicant to apply for an open role? This is information we can collect on the screens and validate.

• What training is required for each kind of role and where will the LMS be housed?

• Will you integrate to the LMS?

• How will you validate employment, education and perform background checks. If you want this automated, you will need to gather inputs from the source systems.

• What PII (Personally Identifiable Information) should be secured in the system and who should be able to see the PII, and who should not?

Part 2: System Administration Settings

Once you have roughed in a plan for all the specific information you need for your strategy, its time to set the system up to accomodate it. In our test system, we updated the following:

1. Partitioning. We setup partitioning and partitioned screens, call templates, workflow templates and the bulletin board (to send public notices to non-employees) in addition to all the other standard partition settings.

2. Security Profile. We setup a security profile for HR in order to be able to slectively hide PII on screen from everyone but HR.

3. CMDB Item Types. We added CMDB Item types for Employees, Manager-Mentors, Mentees, Workforce Role and Workforce Candidates. It is important to not get confused between Employees, Candidates and Mentors and Mentees as CI and those same individuals as People in the system. The person record created is merely there to facilitate access to the Portal and to ASM and nothing more, really. The records of these individuals in the Federated CMDB as a 'CI" however is where all of the data is housed and where the journey is actually managed. This is critical because we are able to create the kinds and tyoes of dependencies and relationships we would not otherwise be able to accomplish by only using a person type entity. The person entity in ASM is an account record, and nothing more.

4. In Workflow Management, we created the request screen sets for publishing Roles and for onboarding new candidates. We also created a screen set for requesting training and Professional Development. Finally, we created screens for managing Reviews, time off, sick leave and off-boarding.

5. We also set up the relevant Employee Journey phase and status values in Workflow Management. Consider each screen and the data you want on each. You will need to configure the correct system values before you build your screens.

Part 3: Screens

After you have configured your system, you can begin building your screens to support your Employee Journey Strategy. You will have several. Below is an example of the screen build for an open Job Posting (AKA WF-Role CMDB Item Type). The basic elements are provided for all the listed screens, but using Designer, you can fit them to your organization, specifically.

Part 4: Workflows

Several workflows (and related screens) are already configured to support Workforce and Talent Management but you will need to visit each one and alter it to suit your organization and your potential integrations. They include:

1. Employee Management

   • Disciplinary

   • Sickness

   • EPR - Master Request

     • EPR - 360

     • EPR - MBO ( Management By Objectives)

2. Employee Journey

   • Prospective Employee

   • New Starter

   • Employee Off Boarding

3. Training

   • Training Request (General)

   • Group Cyber Security Training Request

Example: Employee Journey - Prospective Employee Workflow

Part 5: Integrations and Automations

Planning for your integrations and automation is likely the most extensive part of work you will have when deciding to implement your strategy. Familiarise yourself with the RestFul API, and then as above, make a plan for the data that will passed to and from ASM.