Completion Report
Project Summary
This project engaged with a wider set of stakeholders in colleges and business units with the aim of deploying a new university service for Mobile Device Management. This assumed a sufficient commonality of requirements to develop a 'standard' managed device and potentially a limited number of 'special use' cases, and also that the requirements can be met by the existing technology.
Objectives and Deliverables and Success Criteria
Description of the Objective |
||
Description of the Deliverables needed to achieve the objective | ||
Objective 1 |
Deploy an MDM Service to the University by the 31st July 2020 |
Success Criteria Achieved but in February 2023 |
Deliverable D1.1 | A standard mobile device | Achieved |
Deliverable D1.2 |
One or more specialist devices | Achieved |
Deliverable D1.3 | OLA/OLAs between Service Owner and Colleges, Business Units | not required as agreed with USD/Helpdesk |
Objective 2 |
A sustainable MDM Service | |
Deliverable D2.1 | A service which has committed resource and funding for ongoing maintenance, support and development | Achieved |
Deliverable D2.2 | ||
Objective 3 |
A sustainable Technology | |
Deliverable D3.1 |
Road map for future development of the underling technology | Achieved |
Deliverable D3.2 | A scalable solution that can expand to bring the service to a widening user base | Achieved |
Objective 4 |
A secure Technology | |
Deliverable D4.1 | A solution that provides secure access and secure data | Achieved |
Objective 5 |
||
Deliverable D5.1 | ||
Deliverable D5.2 |
Requirements
Requirement | User / Owner | MoSCoW | Associated Objective/Deliverable (Ox/Dx.x) |
A centrally managed mobile device management a service that meets the requirements of CAHSS. These requirements will be reviewed, agreed and approved by the end of the Requirement Gathering | Fraser Muir | Must | O1, O2, O3 Achieved |
A centrally managed mobile device management a service that meets the requirements of CSE. These requirements will be reviewed, agreed and approved by the end of the Requirement Gathering | Gareth Poxon | Should | O1, O2, O3 Achieved |
A centrally managed mobile device management a service that meets the requirements of CMVM. These requirements will be reviewed, agreed and approved by the end of the Requirement Gathering | Alan Gilchrist | Should | O1, O2, O3 Achieved |
A centrally managed mobile device management a service that meets the requirements of Estates. These requirements will be reviewed, agreed and approved by the end of the Requirement Gathering | Alistair Campbell | Should | O1, O2, O3 Achieved |
A centrally managed mobile device management that is secure | Garry Scobie | Should | O4 Achieved |
Benefits
1. Improved support for our students and staff, by ensuring devices have pro-active configuration and management that keeps devices up to date
2. Improved security by pro-active management that keep devices secure by up to date security upgrades and patches
3. Less effort locally to support mobile devices
4. Clear structure for supporting tablet style devices using clear use-case driven device categories.
6. Asset management of tablet style devices.
Lessons Learned - Issues and Risks
n/a
Project Audit
n/a
Outstanding issues
n/a