Aim Management
We have made two additions to the Apprenticeship Dates page:
- Individual aims are now listed and the start & end dates can be edited individually
- Delivery owner per aim, including the option to add subcontractor details
Aim Dates
Programme aims are now displayed on the Apprenticeship Dates page of the enrolment:
Please note that any aims that have been exempted on the previous page will not be shown on the Apprenticeship Dates page.
The start and end date for each aim will be populated once the practical period start date and working hours have been populated. The aim dates will default to the programme build configuration.
You will be able to edit any of the start and end dates of the aims by either selecting another date in the date picker, or by manually typing in a new date. There is validation preventing you from selecting an aim start date before the practical period start date, or an aim end date after the planned practical period end date. This is to ensure that all aims are due to start and finish within the overall programme's duration and do not error in the ILR.
This feature will be available for in-flight learners by going through the edit flow.
For more information, please read this article.
Delivery Owner
When viewing the aims on the Apprenticeship Dates page, you have the option to select who will be responsible for delivering each aim. The selection will default to your training provider name.
If a subcontractor will be the delivery owner for an aim, you can select the "Subcontractor" option from the dropdown. You will then be able to provide:
- The subcontractor's name [mandatory]
- The subcontractor's UKPRN [optional]
The delivery owner for each aim, including any subcontractor details, will be displayed against each aim on the Training Plan document:
If you wish to generate a new Training Plan document with the delivery owner details for any in-flight learners, you will be able to do this by using the edit flow.
Additional skills bootcamps category codes available for assignment.
We have added the following skills bootcamps category codes to the platform:
- Z0060461 Skills Bootcamps - Care Services - Level 3 equivalent:
- Z0060464 Skills Bootcamps - Catering - Level 2 equivalent
- Z0060468 Skills Bootcamps - Hospitality - Level 2 equivalent
- Z0060465 Skills Bootcamps - Catering - Level 3 equivalent
- Z0060469 Skills Bootcamps - Hospitality - Level 3 equivalent
- Z0060466 Skills Bootcamps - Catering - Level 4 equivalent
- Z0060470 Skills Bootcamps - Hospitality - Level 4 equivalent
- Z0060467 Skills Bootcamps - Catering - Level 5 equivalent
- Z0060471 Skills Bootcamps - Hospitality - Level 5 equivalent
Multi Factor Authentication (MFA)
Strengthening Security with MFA Self-service controls
Bud has been improving its MFA capabilities to give customers greater control and flexibility over their organisation’s security settings. In line with GDPR best practices and our ongoing commitment to data protection, Training Providers can now manage MFA status directly for their own users, as well as for Learners and Employer contacts.
These self-service controls not only enhance the overall security position of our customers by reducing the risk of unauthorised access, but also minimise administrative overhead by allowing MFA to be enabled, disabled, or re-re-registered (e.g. in the event of a lost device) without the need to contact Bud Support.
Prerequisite requirements
Before Multi Factor Authentication (MFA) can be applied directly to specific users, providers will need to ensure that they have the "MFA" functionality enabled within their tenancy. Please contact Bud Support or your Customer Success representative if you need assistance with this.
In order to access the "Admin" navigation menu and subsequently the "Security Settings" page the training provider user must have the "System Administrator" role assigned. Due to the nature of the controls this enables, it is likely the number of users in your organisation with this elevated role will be limited and should continue to be assigned ONLY to those who will specifically need to use it in their job role.
Individual and Bulk updating of users
The self-service controls for MFA allow you to Enable, Disable and Re-register MFA for users on an individual basis (subject to their current status). It is also possible to "Bulk Enable" Internal users, Learners and Employers which will set all users of that type to MFA enabled which enforce the use of an authentication device for all future log-ins to Bud.
IMPORTANT - PLEASE NOTE: The "Bulk Enable All" process is NOT reversible for Learners and Employers and will result in all users of that type being set to MFA "enabled" permanently.
All Training Provider users will become enabled if used for that user type and will have to be individually set to "disabled" in order to undo the change.
Please ensure that this button is used will the full consent of your business following the correct consultations and business practice analysis.
For detailed information on the process for using the MFA self-service functionality including prerequisites, considerations and navigation the feature please refer to the following help centre article
Bug Fixes
On Tuesday 2nd Dec we released a number of Funding and Compliance bug fixes (release 6.4.0) as part of our continued drive to release benefits to our customers immediately where possible. In this interim release we deployed the following bug fixes:
Breaks In Learning (BILs) that occur before a component aim is started should be ignored for that aim - We have made changes to the BIL logic to ensure that a BIL that occurs before a component aim's learning start date should not be included in the calculation for that aim's learning deliveries in the ILR. The logic will now ensure that:
- Any BIL period that fully ends before a component aim’s learning start date must be ignored when generating ILR learning deliveries for that aim.
- Only BILs that overlap with or occur after the aim start date should influence the aim’s learning deliveries.
Funding adjustment for prior learning returning unexpected values - As an extension of the fix detailed above the "funding adjustment for prior learning" value applied to Maths and English aims on a return from a break in learning (RBIL) will be correct in the scenario detailed above where the component aim was started after the RBIL date.
LearnActEndDate removed from ILR after EPA Fail - We have resolved a bug which previously presented when a learner completed their EPA without achievement which subsequently resulted in their learning actual end date being removed from the ILR.
In scheduled release 6.5.0, we have fixed the following bugs:
Activity dates not updating correctly - on the specific scenario of changing the duration during the edit flow, activity dates were not correctly updating and sometimes resulted in activities planned for after the practical period end date.
Please note that this fix has only been applied to programme activities that are currently "unset" in the learning plan. Another fix for other activities will follow.
OST submissions not saving - when providers had disabled the "Bulk OTJH" feature switch, this was causing some OST submissions not to save.
Training Plan showing incorrect dates - occasionally, some activities on the Training Plan were showing incorrect dates (such as Jan 1970).
Self employment record not created in the ILR for OST learners - Following the recent introduction of the "self-employment" option in enrolment for OST learners we have resolved an issue where the correct employment record was not being created in the ILR. Users who declare they are self-employed during as OST enrolment will now have an employer entity added to their ILR record with the correct "EmpStat" code (10) and "EmpStatMonitoring" type and code applied (SEI1)
Completed Activities not shown in Reviews - We have resolved a bug where activities which are completed after a Review is complete, but on that same day, do not show in the next review as completed.
This means the activity fell through the gap and didn’t display on any review.
Refreshing the page when on a Review - We have resolved an issue where on some occasions, refreshing the page with a Review open, results in the navigation bar being hidden.
Business Intelligence - 10th December at 14:30
Embedded Reports Small Enhancements
Management Reports
We have made a change to the aggregated metrics table in the caseload tab of Management Reports. This table will now not show rows where the aggregations are null or zero values.
Employer Reports
We have increased the character count for the field RAG rating reason to enable additional context in the employer reports to be visible to employers using the portal. This change will also be present in all reports containing this field however there has been no change to the customer facing DWH field so no ETL amendments are needed.
Standard Reports
We have added the additional columns Trainer Name to both tables in the OTJH report.
We have also added the field ILR Planned End date to the below report pages to help identify original planned end dates and end of funding dates for learners. This can be used alongside the existing Planned End Date field to identify where a change to the Planned end date has been made in platform.
- In-Flight learners
- EPA Readiness
- In EPA
- Ofsted
- Withdrawals
- Completions
Bug Fixes
The following bugs have been fixed since the last release
QAR Percentages showing as decimals - within the potential achievers report, Activity Progress % and Required OTJH Progress % were showing as decimals not integers.
QAR Report is filtering out non-Bud learners - Following the 12th November update introducing Bud fields into the QAR, we noticed learners who did not match to a Bud record had been filtered out of the report.
Standard Reports Programme type slicer - The slicer "programme Type" in the in-flight learners report was showing options for learning plan status not programme type.
The following bug will be fixed in the 10th December release
ILR Reconciliations > Learning Support and Employer payments - Where multiple rows with the same ULN appeared, these ULNs were being summed in the table.
Data Warehouse Fields
No new fields have been added to the data warehouse in this release.