# data[].attributes.body
To enable us to trial things like new term structure

# data[].attributes.headline
Need anticipate where market growth will determine structure

# data[].attributes.subject
Need anticipate where market growth will determine structure

# data[].attributes.body
LLE - 30 credits = better suited to 4 term structure

# data[].attributes.body
Need to define what do we need to have implemented (term structure wise) to enable changes to curriculum structure

# data[].attributes.headline
How students see/ are communicated with re: their term/ year etc

# data[].attributes.subject
How students see/ are communicated with re: their term/ year etc

# data[].attributes.body
Could consider how this can be more effectively managed (without need for moving to 3/ multiple term structure)

# data[].attributes.body
Need to size what would remain non standard - determine what are the benefits of moving to a 3/ multiple term structure/  what problem(s) will this solve?

+ what resource would this demand overall

Need to define what do we need to have implemented (term structure wise) to enable changes to curriculum structure

# data[].attributes.body
A lot of current customisations are around non standard starts, need to consider/ analyse how this would impact move to multiple term structure

# data[].attributes.headline
Capture key docs which would need to be in CMS

# data[].attributes.subject
Capture key docs which would need to be in CMS

# data[].attributes.headline
Ability for AR to request info in system

# data[].attributes.subject
Ability for AR to request info in system

# data[].attributes.body
Automated process e.g. send out info to Course Leaders on an annual basis, asking them to update > feeds back into system

# data[].attributes.body
High level data quality/ visibility (for relevant staff, at relevant points in process)

# data[].attributes.headline
System which 'forces' compliance & consistency

# data[].attributes.subject
System which 'forces' compliance & consistency

# data[].attributes.body
Need to better understand scope of Curriculum WS incl timescales to determine what we should look at now Vs what should wait for WS to deliver

# data[].attributes.headline
HD to provide overview of Ellucian products

# data[].attributes.subject
HD to provide overview of Ellucian products

# data[].attributes.body
(MA) A view of the existing or upcoming Ellucian products that might support the requirements e.g. Apprenticeships for Banner, Banner Document Management

# data[].attributes.body
Curriculum data pulling into warehouse e.g. No of enrolment on x module, to inform curriculum efficiency, success of curriculum (MEQs)

# data[].attributes.body
e.g. CPD, Apprenticeships (Apprenticeships for Banner), HTQs, Skills Boot Camps and ensure that CMS/ systems/ processes take these into consideration

# data[].attributes.body
Consider scope of their requirements and how they intersect with Curriculum WS/ scope

# data[].attributes.headline
Requirement of system: ability to give schools a view of their data

# data[].attributes.subject
Requirement of system: ability to give schools a view of their data

# data[].attributes.body
Need to confirm what data/ what level/ what staff need to see data
Ability for schools to also see/ amend teaching team associated with module > integration with other systems Banner/ Starfish
Benefit:  this would likely prevent colleagues needing to ask AR for info

# data[].attributes.headline
Flexibility of alt models/ curric structures

# data[].attributes.subject
Flexibility of alt models/ curric structures

# data[].attributes.body
Underlying theme - systems and processes need to facilitate flexibility to allow us to adapt to change in market/ demand

# data[].attributes.body
System that enables us to 'put into boxes' things which fit, but provides flexibility for those that don't
AND
Flexibility to adapt system e.g. add additional fields where necessary

# data[].attributes.body
Need to ensure we communicate with stakeholders, clear, plain English re: what this work sets out to achieve

# data[].attributes.body
Challenges with current system - Word/ hard doc based
Hard to keep track of bloated curriculum @ UCLan

Benefits (of a curriculum management system): Ability to develop/ record/ manage curriculum in one place/ system
Flow of information/ data
Better data (management)
Less manual intervention/ risk of error
Integration between 2 systems more failsafe

# data[].attributes.body
Need to consider impact of LLE on curriculum structure as more info becomes known

# data[].attributes.headline
Structuring of curriculum data in CMS to enable reporting through Banner/ other means

# data[].attributes.subject
Structuring of curriculum data in CMS to enable reporting through Banner/ other means

# data[].attributes.body
Need to ensure data in CMS is structured effectively - to enable stat returns etc
CMS likely to be the front end/ staff view of curriculum
Banner 'back end' technical
BA piece to determine what data transfers from CMS > Banner

# data[].attributes.headline
Differing views/ requirements of e.g. AR/ ER/ AQU

# data[].attributes.subject
Differing views/ requirements of e.g. AR/ ER/ AQU