< back
Service Template
Availability
- Who is allowed to use this service (Internal to the group, Everyone in the college, Multiple colleges, Entire University, Global)?
Life cycle
- Living will - What happens when funding or support is removed for this service (data will be safely exported, data will be archived, VM will be archived, What will the recovery cost be for extracting data)?
- OS patching frequency - How often will we update the underlying OS/OVA/Appliance/Firmware? Ideas: We will run on a 10 day lag, As soon as available, Next possible maintenance window. Who will do this?
- Application
updates?updates - How often will we update the application providing the service. Ideas: We will run on a 10 day lag, As soon as available, Next possible maintenance window. Who will do this?
- Sunset plan - How and when will we re-evaluate the service.
Dependencies
Workflows
Service requests
- Change requests
- Uptime
- Maintenance
- Announcements
- Update policy
- SLA
- Time to resolution on service request
- Service survivability and recovery
- Data access policy
- Under what circumstances can ITS look at this data
- Data stewardship
- Back up
- Retention
- Survivability
- Appropriate use policy
- Don’t put 10 TB of bin files in gitlab
- Budget