Skip to main content

Adding new populations to the Equus Platform

Bringing more of your mobile employee populations into the Equus Platform provides numerous benefits from providing a central point for global reporting and insights to increasing compliance and reduc

Updated over 2 weeks ago

Bringing more of your mobile employee populations into the Equus Platform provides numerous benefits from providing a central point for global reporting and insights to increasing compliance and reducing risk.

Check out the top tips for adding new populations to the Equus Platform:

1. Know your process flow

Understanding what you want to achieve and what the end state will look like is essential to any successful launch

  1. Map out the user journey for initiating and managing each mobility type

  2. Some areas to consider could include:

    • Who should be initiating these cases? What user access do they need?

    • Will the initiator have the information that is being requested of them?

    • Should any notifications be triggered throughout the initiation process to alert stakeholders of a request?

    • Which stakeholders are required for the approval process?

    • Are there any other processes that should be followed for the new population that could be supported by a checklist? e.g. Raising Service Orders

    • What reporting is required?

2. Configure the configurable (in a test environment)

Check out the Mobility Handbooks to understand what is available out-of-the-box, and what can be configured

  • Does the out-of-the-box functionality meet your needs or do you need to make some updates?

3. Conduct an impact analysis

While reporting and automation in your site enhances processes and is generally considered a huge benefit, it is important to consider which of these components will be appropriate for your new populations.

An impact analysis will help you identify system areas that could trigger or be impacted by adding a new population.

You can check the following features to consider on how to conduct the impact analysis, recommended steps to mitigate the risk and the next steps:

Note: these are generalized for a broad audience, please seek specialist assistance from your Client Success Team when conducting an impact analysis.

Quick Workflow

To conduct an impact analysis, you can run a user report to identify the trigger points and filters available on any active quick workflows. This can include hyperlinks to the quick workflows on the user report can speed up the review and mitigation process.

While adding your population, assume that, unless stated otherwise in the filters, any quick workflow with an ‘Assignment level’ trigger, could now also trigger for your new population. To mitigate this, identify if any quick workflow that should not trigger using the report and add filters to ensure it only triggers for specific policies.

For example, if you want the QWF to trigger only for Short Term Assignments, the filter should define which Policies should be included and will automatically exclude any other policies, for example:

QWF Condition of Assignment: Relocation Policy is equal to Short Term Assignment

Make sure to test the workflows triggers or doesn’t trigger as expect, and note of any configuration that needs to be migrated to the production site.

User Reports

User Reports can be reported on to identify where specific filters are used, or field names such as Assignment: Relocation Policy, are referenced. You can include hyperlinks to the user reports can speed up the review and mitigation process.

The report will help identify:

  • If where additional filters may be required to include or exclude the new population.

  • Any scheduled reports, including those related to compensation & payroll that may be sent automatically.

Consider which reports you would like to include the new population, and those you would not. You should include filters where necessary. For example, if you want to only include Long Term Assignment and Short Term Assignment records in a report, the filters could display:

User Report Filter of Assignment: Relocation Policy is equal to Short Term Assignment or Long Term Assignment

Test the user reports by running them independently once a few test cases of the new population have been added to the test site. Make sure to note of any updated reports for migration to the production site.

Checklist

To conduct an impact analysis, you can run a user report to identify any company or system level checklists that have automatic trigger points that could be triggered for the new mobility type records incorrectly. This can include hyperlinks to the checklists on the user report can speed up the review and mitigation process.

If necessary, include conditions to either trigger for specific policies only, or exclude a specific Mobility type case. For example, if you want the checklist to trigger for existing commuter population and the business travel records, the filter would display:

Checklist Condition of Assignment: Relocation Policy is equal to Commuter and Assignment: Move Type is equal to Business Travel

Make sure to test the checklist is not triggered for the new mobility type records, and note of any updates for migration to the production site.

Assignment Package Batches

Audit your Assignment Package Batch criteria to identify any ‘at risk’ combinations, these include if the criteria do not include filters for:

  • Policy

  • Home Payroll System

  • Host Payroll System

  • Home Segment Levels

  • Host Segment Levels

If your batch criteria do not include any of the flagged filters and the new Mobility Type population should not be included in the batch, consider adding Relocation Policy to the batch criteria moving forward. This will ensure that unwanted records that do not have an assignment package license, do not get included in the batch.

If changes are made, test the assignment package batch criteria to ensure the correct records are included and note of any process changes for future assignment package batches.

HRIS Integration

Reach out to your Equus Representatives for support.

Did this answer your question?