# data[].attributes.body
for whole Uni not just IS

# data[].attributes.body
Students, research, academic and professional service staff

# data[].attributes.body
rephrasing of vision statement. set strong vision for 2025. Education digital startegy neds to align too

# data[].attributes.body
The IT vision should underpin the education strategy and not be a vehicle to set it. More of a 'visionary' summary required

# data[].attributes.body
The IT vision should underpin the education strategy and not be a vehicle to set it;

# data[].attributes.body
acacdemic divisoion running acacdemic

# data[].attributes.body
acacdemic

# data[].attributes.body
Academic Division and Academic life cycle should be referenced and considered as this is a large and impact service in the university.

# data[].attributes.body
rfeerence to Simplyfying Kent in principles

# data[].attributes.body
3.2 doesn't meet Simplifying Kent principal and we should look at reffering to optimisation. This is covered in principals.

# data[].attributes.body
3rd bullet in Ownership of IT
NOT SURE QUITE WHAT TO DO WITH THIS AT THE MOMENT

# data[].attributes.body
Ownership led by IS*

# data[].attributes.body
Explain what Shadow IT is and what it means

# data[].attributes.body
Support in place for students, staff and visitors

# data[].attributes.body
Service relationship is not well defined in principals. Need to clarify this to link vision and principals in a more effective way

# data[].attributes.body
infrastructure, process, software, data?

# data[].attributes.body
Scope of sustainability - "solutions" as opposed to "equipment and hardware"

# data[].attributes.body
Ensure appropriate usage of cloud based on requirements, not necessarily cloud as a default

# data[].attributes.body
Not a budget for centralised licencing. Therefore, not departments stopping progress, but lack of budget. All can't be done centrally as schools need to be reactive and can't wait long term issues.

# data[].attributes.body
Agree principals for tools before we look at resources. Need to focus on student experience. Should not cut out requirements at local levels as departments and schools will have differing needs on same issues

# data[].attributes.body
5th point - provide clarity, feels odd.
VLE distance learning etc at the end, this feels like the document mentions specifics for the first time.
Final point - Hard to engage students for anything which they don't have credit for! Need to recognise that we need to provide systems for students that are intuitive and get on with it without training.

# data[].attributes.body
There isn't a strategy to help students with digital capability but not sure if this should be in IT strategy.

# data[].attributes.body
Missing information on technologies. Would like to see what future of differing technology stacks would be. Difficult to mainstream developments in schools and needs to be addressed.

# data[].attributes.body
4.1.6 Not necessarily felt to be a given and not sure if this correlates with idea of being cloud based. Is this a principal? Perhaps rewritten to improve resilience and link to information governance

# data[].attributes.body
We should explain that we're already 'doing cloud' on a number of important systems

# data[].attributes.body
Principal of using API rather than DB transfer. Perhaps look at real time implementation and move legacy implementation on to 'quality' APIs

# data[].attributes.body
Need to explain acronyms and describe in plain English for 'lay' IT. It needn't be technical. Remove tech language.

# data[].attributes.body
Hard at department to find policy and advice let alone at a central level. Needs to be clearly defined.

# data[].attributes.body
Touches on data management plan, perhaps this should be referenced

# data[].attributes.body
Touches on data management plan

# data[].attributes.body
Shouldn't be including details of IT Training as there are central teams providing this. IT Security doesn't not necessarily need to be included in the document. Remove legislative issues (last sentence P1 of 4.3.2). General statement of working with staff developemnt across university to ensure that skills and IT literacy are sufficient. Add that staff aunderstand responsibility.

# data[].attributes.body
4.4.2 - statement not principal
4.4.3 - Stakeholders should be defined as partners. Feels a bit vague. Is it just IT people included in that statement? Clearly define that it's relevant stakeholders

# data[].attributes.body
Clarify that we want to reduce unnecessary duplication and risk associated with some local IT service delivery

# data[].attributes.body
Concern about reducing pockets -  IT Reps are providing specialist requirements. Need to be careful how we word this and should remove the word reduce as this should cause alarm.
-Define this statement to include and define shadow IT and remove / reduceduplication.

# data[].attributes.body
Reword to Requirements Team and define further. Perhaps look at deleting as it doesn't seem to match 4.6

# data[].attributes.body
Regular cost / benefit calc of existing service / system

# data[].attributes.body
Reads like a strategy to review staff in schools and move to central services. Needs rewording. Poss looking at tasks rather than roles and people.

- Does this need to be in IT strategy as there is going to be a uni wide structure review?

# data[].attributes.body
What is 'above' criteria? REphrase for clarity.

# data[].attributes.body
Centralisation of tasks and roles rather than personnel

# data[].attributes.body
A lot sounds like principals and some principals sound like objectives.

Useful to rework, more clarity with restructure and then another review at a workshop agreed.

Once document reworked, will be circulated to the group for review before next workshop.