Document Control
Initiation
design
build
delivery
Architecture Vision
High Level Design
Data Protection Impact Assessment
DR checklist
For projects where new architecture across the estate is required
typically the largest projects
completed by SSOLA
"big picture" overview of the objective
describes existing & to be configs
highlights what happens with data & technologies
required where a new provider will be handling school (or our) data
defines scope of project
identifies risks, assumptions, and dependancies
estimates costs to design, deliver and support
Implementation plan
Service Definition (SD)
Continuity Plan
Configuration
Customer Knowledge
Software KA
1st Line knowledge
3rd line knowledge
Supplier Knowledge
Application release template
Test plans
Application portfolio entry
New subscriptions
Supplier requirements
Functional requirements
Cessation checklist
Source Control
Split into phases
describes exactly which team does which task
PMs use to create tasks in Service Now for appropriate teams
Needs to be signed off before ending UAT phase
Defines the service in a way that can be displayed on our website
schools sign up to a service based on whats contained in this. It explains what they will recieve within their subscription, exclusions and how it works
Defines what will happen if the server driving this fails
includes items like restoring VM from backup, building from scratch, where instructions are to do this etc
describes the technical configuration of the service
includes onboarding/offboarding technical actions for subscribers
how new EDS staff are added to administer it
details of agents, servers, firewall ports, technologies
if any software is written (scripted solutions etc), these are documented here
includes the 'big picture' topography, so that support staff can understand the solution holistically
easy questions to answer
Operational Definition
doc
xls
cat items
escalation routes
access to catalog items to open for schools
FAQs
Configuration docs
Installation docs
quick reference sheets
detailed support docs
Who are the supplier?
Account Manager
Support routes. Phone/email/web
hours of support team operation
How licensing works
dependancies on other licenses. SQL CALs for SIMS etc
How test & dev devices are licensed
when licenses need to be renewed
License number & schedule
Supplier needs to comply with XYZ
Service needs to function in this way
NEeds to work with these other applications
Is there code involved?
Does it need to change/be maintained?
GitLab on AD
Functional
cover all expected environments
capture unexpected consequences
all items need to be baseline in "known good" config
Can differ between internal/UAT/early adopter/Live, but need to provide the same function
processes. What happens when someone buys this?
installation of software
entry into CRM
Addition to central server
Accounts / federation activity
when we want to stop this whole service, what will we need to do?
servers
firewall rules
knowledge
opdefs/cat items
Add to the Software Centre