SITS Module Processing Repeat Modules 30th August 2013

Topics Re-cap of project Changes to mark schemes Module Grades 2013/4 Brief, rationale, benefits and consultancy Changes to mark schemes Impact on processing of modules in SAS and RAS Module Grades 2013/4 Implications of changes Business Objects reports, MAP, exam scheduling Next steps

Re-cap of Project Brief – to review the existing method of recording modules being repeated, restarted or trailed Rationale – to improve the reporting of module completion, better recording of year on year module progress and to reduce the workload in re-attaching students to modules. Benefits – brings module data in line with Tribal’s recommendations; a more consistent approach in Exam Board reporting; easier preparation for exam scheduling; simplifies barcode submission and progression. Regular meetings held with School representatives SITS consultancy and testing

In a Nutshell

Existing Mark Schemes Assume that modules in SAS are at attempt 1. Designed to keep modules in RAS until maximum attempts reached. This results in SMRs being assigned to one academic year with RTS codes used to identify repeats/restarts/trails etc. Difficulty for Planning Team in determining module completion for SMRs in previous academic years. Numerous mark schemes are very similar and can be consolidated.

Module and Assessment Mark Schemes

New Mark Schemes Key changes in new mark schemes: Modules can be processed at attempt 2 (UG and PG) and attempt 3 (UG only) in SAS. Marks of 0 (zero) will default to grade AB. Modules in RAS will automatically close (apart from PL). Failed modules will close with grade FW by default. Grades Z, CD and FS removed. New assessment grade NX for non-attempt by exceptional circumstances. EX only used when an attempt is made. See ‘Aston University Mark Schemes – August 2013’ for full list of mark schemes and changes.

Scenarios: How the Mark Schemes Will Work How this affects calculating, setting and agreeing modules in SAS and RAS. Only referred students in RAS. Repeat, restart and trail modules COM with new SMO & SMR for following year. Number in RTS field overwrites attempt number.

Demo Demonstration of how mark schemes affect modules processed in SAS and RAS

Module Grades 2013/4 Amendments to module grades: New assessment grade NX for non-submissions with exceptional circumstances accepted Removal of CD, FS and Z grades. Importance of AB and NX grades in determining completion Continued use of Final Assessment flag in MAB Refer to HESA module grade document for full list of assessment and module grades

Implications of Changes 1 Business Objects reports Exam Board spreadsheets , Module Board reports and transcripts MAP Staff – module lookup and student view Students – My modules and provisional marks Exam Scheduling Simplified RAS = Referrals; SAS = Jan/Summer Exams Modules being repeated must be closed before scheduling

Implications of Changes 2 Progression Amendments to letters Changes of assessment/module Use of A13/4 Coursework submission SRRs for referrals only. SALs for all students in SAS HESA Return Distinct SMR for each year a module is taken Every module (not spanning years) should be COM at end of HESA year

Attaching Repeat Modules Manual attaching of repeat modules Significance of automatic incrementing and attempt number in RTS field Identifying existing repeat, restart and trail modules – x13/4 Labelling repeat, restart and trail SMOs with R, S and T in UDF Carrying forward assessment marks

Demo Demonstration of attaching new set of repeat SMOs and generating corresponding SMRs

Next Steps - Registry Creation of replacement mark schemes in SITS Live Global updating of MOD and MAV records with new mark scheme codes Updates to MAP lookups Prioritised updates to Business Objects reports

Next Steps - Schools Closing of repeat SMRs after September referred Exam Boards September progression as normal SMRs identified using RTS codes S13/4, R13/4 & T13/4 and will be in RAS under previous mark schemes Attaching repeat modules as new SMO for 2013/4 Registry to run a MAP in-tray message to repeat students with confirmation of modules and assessments to be repeated – this relies on SMO data being present and up-to-date assessment patterns in MAV To run when timetables go live

Key Dates Teaching timetables live – 30th September 2013 September progression deadline – 30th September 2013 SMR generation for exam scheduling and HEFCE PGT – 25th October 2013 UG – 31st October 2013

Conclusion Culture change - Different use of RTS codes and closing modules not referred in September Long term benefits in module reporting Eases introduction of online mark entry, UG progression and recording exceptional circumstances Effects on PGT students and progression Modules spanning years operates the same way Importance of testing new reports in advance of Exam Boards What else is going wrong? We need to know