Running the Optimiser
Learn about the process of running the Optimiser
This article walks through a complete Optimisation run from start to finish. It starts from configuring your Optimisation run and continues all the way through to confirming your updated Records.
1. Define the Resource Pool
The first step in any Optimisation run is defining which Resources the Optimiser will consider.
In this example, let's assume our Planner shows a week with 51 unfilled Appointments, and we begin with 184 active Resources.
We open the Resource Pool and start applying filters to refine the group.
Select Resource Pool.
Click Add Criteria.
Choose a Field (e.g., Resource → Work Type).
Select an Operator (e.g., equals).
Select a Value (e.g., Full-Time).
After applying this first filter, our pool narrows from 184 → 126 Resources.
We then add a second filter:
Resource → Region equals East Metro
This reduces the pool further to 68 Resources.
Now, the Optimiser will only consider these 68 Resources when filling all 51 unfilled Appointments.
2. Define the Ranking Criteria
With the 68-person Resource Pool set, we now decide how those Resources should be scored.
Ranking Criteria uses the same Field → Operator → Value structure, but instead of filtering people out, it influences how well they score during optimisation.
For this example, let's say we add one criterion:
Resource → Gender equals Woman
This does not reduce the pool size (still 68), but Resources who match the rule will receive a higher scoring contribution.
If a Ranking rule is too strict (e.g., a value that no Resources have), optimisation may return no matches.
3. Configure Settings
Next, we tell Maica how much weight each category should have in the scoring formula.
We open the Settings panel, which displays the five weighted categories:
Skills
25%
Measures how many required skills the Resource has.
Availability
25%
Checks if the Resource has enough hours available for the Appointment.
Workload
25%
Compares the Resource’s total weekly hours against their limit.
Attributes
25%
Matches Resource attributes (e.g. gender, language) to Participant requirements.
Travel
0%
Ignored for this run, as all services are online.
We leave everything at 25%, except Travel = 0%.
This means each of the four categories contributes equally to the final Matching Score.
4. Run the Optimiser
We now select all 51 unfilled Appointments and click Optimise.
At the top of the Optimiser, the Progress Indicator shows:
0 of 51 filled
As the run progresses, the count updates in real time.
At any point in the time you can pause the optimisation process by clicking the progress spinner within the progress indicator. If you do so, Maica will save the records that had already been optimised before the run was paused. If you then continue without deselecting records, Maica will pick up from where your run left off
The Optimiser evaluates each Appointment one at a time based on our configuration:
It checks if the Appointment can be filled using the 68 Resources in the Pool.
It scores each eligible Resource against the Ranking Criteria and weightings.
It assigns the highest-scoring Resource(s).
If an Appointment cannot be filled, it’s skipped, given an error status, and the run continues. You can then review these after the optimisation run.
After a short period, we see:
37 of 51 filled
Some Appointments are now marked as fully optimised, and others remain unfilled or partially filled.
Please note, you can work in the Optimiser whilst a run is underway. If you wish to view Appointment Insights or perform other Actions whilst the run is ongoing, you can. The only thing that will interfere with the run is cancelling and closing the modal.
Once the run is complete, all Appointments will be sorted into Statuses: Filled, Partially Filled, Unfilled or Error.
6. Re-run the Optimiser for Remaining Appointments
Let's say, after the first run, 45 of the 51 Appointments have been successfully filled using our 68-person Resource Pool.
This leaves 6 Appointments still unfilled. Rather than adjusting Ranking Criteria or weightings, we decide to broaden our Resource Pool slightly to give the Optimiser more people to draw from.
We return to the Pool and remove the criterion:
Resource → Region equals East Metro
Our pool expands from 68 → 122 Resources.
With this wider set, we select only the remaining 6 unfilled Appointments and run the Optimiser again.
The Progress Indicator updates until all 6 are filled. We now have 51 of 51 Appointments filled across the week.
7. Respond to Changes — Manually Adjust an Appointment
Now, let's say one of our confirmed care workers calls in to say they are unwell and unable to attend a particular Appointment. We need to make an adjustment.
So, begin in the Resource Column for the required Appointment, and:
Open the dropdown menu on the Resource’s pill.
Select Withdraw.
The pill becomes greyed out, indicating the worker is no longer active for this Appointment but still visible for audit purposes. Our Confirmed Badge will also now turn back to Red, indicating the Confirmed Resources do not match the configured Requited on the Appointment.
Now, we need to allocate a replacement Resource. To do so:
In the same Appointment, select Find Resource Manually.
The modal shows all eligible Resources based on our updated 122-person Pool.
We scroll to find Nicolette O’Mahony (who scored 52%) and select her.
Click Confirm in the modal.
Nicolette is now added as the new confirmed Resource, while the withdrawn worker remains greyed out.
The Appointment is once again fully covered.
8. Confirm All Records
With all adjustments complete, we prepare to finalise the Optimiser session. To do so, we click Confirm at the bottom-right of the Optimiser.
A Summary Screen appears, outlining the number of Appointments or Shifts updated to each Status. Once we confirm this, all Optimiser results are written to the underlying Appointment and Shift records in Maica, and updates are made.
During this update of records, Maica will detect any further Validation or additional Errors that may arise. It will display them and give you the option of continuing or returning back to the Optimiser. An example of this step may be a Soft Unavailability detected. Here, Maica lets you know about it, but doesn't stop the Resource being assigned.
This marks the end of our run.
Last updated
Was this helpful?