Hi Alison

I've seen various validation rules with Project S exceptions on them (ie ignore when LDM 395 is present), but suspect they haven't caught them all... Which ones in particular are firing when you think they shouldn't be?

Hi Steve,

We thought they would get through validation just by recording LDM 395 but this is not the case as we are getting an error stating the learning aim reference is not valid for the academic year. The learners are not low wage or on benefits.

Regards,

Alison

Sure, but what's the specific error (also, nosiness really, do you not have a special Project S contact you can tell?). There's a dozen LearnAimRef rules that exclude 395 according to the Validation Rules spreadsheet, need to work out if it's one of them not working properly or another one they need to add the exception to.

Hi Steve,

For the same learner currently getting errors R148, LearnAimRef_105, 112, 113. No, we don't seem to have a specific contact for this project with regard to ILR coding. I have emailed the usual helpdesk but still waiting for a reply.

Regards,

Alison

Right, all three of those LearningAimRef ones *should* be excluding 395, so it's just not working right, nothing else you should do except complain it's not working ;) Just to check, is this via SLD or FIS (and, if FIS, have you got the most up to date one!?), as they're all V3 updates?

R148 is more interesting as that doesn't currently have a 395 exception and probably needs one...

We're also on the Project S Pilot and had the same issue, we got the response below from the ESFA, after adding the 391 they are no longer erroring.

LDM395 allows you to record the learner as part of the Project S pilot S, but does not affect funding; you will need to use LDM391 for this. While learners may not meet the actual criteria for use of LDM391, your recording of the Project S code will allow this flexibility.

Your Pilot S representative at the department will then be able to see learning aims (from your data returns) where you have exercised this flexibility.

I suggest that you follow up with your Project S representative to confirm the above.

Regards Martin

Alison, for the learning aim 60054992 it looks like it's no longer valid for any new starts except for MCA/GLA:

I wouldn't trust any response from the general helpdesk, I find it very unlikely they'll know what to do with this. I've had a query in with the team actually dealing with Project S for a number of weeks, and no response. With all of using different flexibilities, we just need to tell them which specific rules are popping up, and get them to put an exception in for 395. Some of ours error even when 391 when using flexibilities we informed ESFA about, so that's not a solution.

Also, like, you're all Grant-funded right? So, as long as it's fixed by R14, it doesn't actually matter? Feels like this should be the mantra of Project S?

Our Exec/Finance would have concerns if there was a big hole in the R04 funding! I have no expectation that ESFA will provide a solution before then, so I'm planning to calculate how much funding won't appear in R04 as a result of these ILR errors, but that we assume we'll get somehow by the end of the year.

Ugh, yeah, can see R04 being a pain for SP if they're not changing how they do your lagged funding calc as part of this...

I guess I kind of thought the point of Project S was "you get the money no matter what the data says", otherwise where's the Simplification [rhetorical]?

Hi,

Has anyone got any further with Project S enrolments not going through validation? We have added LDM391 but are still getting errors.

Regards,

Alison

Alison Robinson Some of the ILR validation rules have had an exception added for 395, but not all of the ones we reported. We're just asking them again to add the ones they missed. If not by R04, I've calculated the amount of money not going in our R04 and reported to my bosses.