Overview
Background
University of Edinburgh has the third largest estate in the UK university sector with a portfolio of 550 buildings and over 200 land assets spread across five campuses. A rolling 10 year capital programme in the region of £1.4bn will further enhance and add to the estate.
The Estates Department employs around 950 staff who are responsible for managing, administering and maintaining this vast estate.
In the course of their day-to-day operations, the various Estates business functions generate large amounts of documents in both electronic and paper form. The electronic documents are mainly created in Microsoft Office applications but digital images, PDF and CAD drawings are also generated.
Currently, the vast majority of documents are stored in a network drive (‘K’) although there are other locations such as personal drives and email folders, various applications with document repositories and additional network drives.
Over time, the various document repositories have grown substantially leading to a number of problems:
- Lack of structure and organisation making it difficult to find things
- Difficulty in fulfilling FOI requests
- Confusion over where the master copy of a document should reside
- Poor governance with the potential for privacy and security issues
- Key documents stored in locations not available to those who need them
- Duplication of documents which take up space unnecessarily and create confusion
- Lack of version control making it difficult to identify the current version of a document
In addition to the issues with the management of documents, there is also a lack of a central departmental communications hub where staff can go to access policy documents, guidance notes, training material and announcements.
A number of years ago a decision was made by the University to adopt Microsoft Office 365 as a cloud based service for staff. As well as the typical applications such as Word and Excel, Office 365 also provides SharePoint which can be used as a solution for document and content management. This has subsequently been rolled out to some areas of the University including HR, Legal Services, and the Building Services section of Estates and is viewed by senior management as an ideal solution for the department as a whole.
- The project aligns with UoE technical principles as incorporated UoE Service Excellence, Digital Transformation and Core Systems programs;
- The project aligns with Estates IS Strategy defined in Estates Business Vision May ’18 v1.3.
- The project aligns with ITIL methodology and aims to deliver business transformation, with a new operating model that supports the new business processes and tools, to ensure “whole-life” solution stability, and a continuous improvement management cycle.
- The project contributes to defining and adopting a reusable approach to be applied to all projects in the Estates IS Portfolio.
Scope
The project scope covers the areas listed below which are based on a requirements exercise carried out by the SharePoint Solutions Team and the Estates Records Manager.
Prioritisation of requirements will need to be decided by the Estates Department soon after this document has been signed off.
- Working with the business areas to understand the current landscape regarding the nature, creation and processing of documents
- Capturing the business needs in order to inform the requirements of the SharePoint solution for each of the Estates business areas
- Implementing Records Management to manage the lifecycle of Estates key documents and records
- Designing a SharePoint document management solution that meets the document management needs of each Estates business area
- A review of the SharePoint infrastructure to determine if it can handle the additional load of the Estates Department
- Configuring SharePoint to support existing document workflows
- Designing an integrated SharePoint Intranet that will be the communications hub for the Estates Department
- Creation of information governance policies to ensure the adoption of agreed working practices regarding data and documents
- Creation of an Estates taxonomy in order to consistently tag and index documents based on standardised metadata
- Creation of a permissions matrix in order to ensure users can carry out functions necessary for their job
- Migration of documents and content from current locations into SharePoint repositories using the existing tool (ShareGate)
- Migration of the existing Building Services SharePoint sites into the new solution
- Training of staff in the use of the SharePoint solution
- User acceptance testing necessary to demonstrate correct functioning of the solution
- Creation of support arrangements including service level agreements and procedures for post go live
- Educating and training staff in the use of new policies and procedures for information management
- Assessing the compatibility of in-house multi-function devices and SharePoint for efficient scanning
- Assessing options for third party tools and utilities to support email management, CAD integration and digital signatures
- Investigating integration options with the MyProject system in relation to template access, views of documents and reporting outputs
- Integration options for handling the record outputs from the Committee Management system
- Cleansing of data or documents prior to migration into SharePoint repositories
- A high level assessment of processes, document, data and information included in the Services Excellence Programme (HR and Finance Transformation)
- Recruitment- there will be recruitment of a SharePoint developer.
- Digitisation of paper documents (covered by a separate project)
Objectives
The primary high-level objective of the project is to implement a SharePoint solution that acts as a central location for the storage and management of documents and a communications hub for the Estates Department. This includes:
- Eliminating use of the ‘K’ drive through implementation of the SharePoint solution and migration of existing documents, where appropriate
- Improving the efficiency of document search and retrieval for all users through the use of metadata and staff training
- Improving the efficiency of document processes through the implementation of automated SharePoint workflows
- Eliminating confusion over current versions of documents through version control functionality in the solution
- Establishing clarity over the locations of master copies of documents through new procedures and governance
- Improving the efficiency of the filing of emails through staff education and the potential use of third party tools
- Improving quality control of document management through information governance and staff education
- Reducing the risk of non-compliance with GDPR and other legislation through information governance and appropriate security permissions
- Improving document management and storage through the Introduction of document retention policies (Records Management)
- Enhancing access security through improved and agreed security permissions
- Improving document sharing for internal staff through solution design and agreed security permissions
- Enhancing team collaboration through solution design
- Enhancing efficiency and consistency through the introduction of templates
- Allowing access to specific areas of the document management solution to external parties through solution design and agreed security permissions
- Improving department communications through the implementation of an Estates Intranet
- Allowing access to specific areas of the Intranet for external parties
These objectives will be delivered in workpackages. EST110 will concentrate on the following workpackages
|
Work Package |
Description |
Requirements identified |
|
Policy, Processes and Procedures |
A document management solution to manage and maintain policies, processes and procedures for Estates |
|
|
Records Management |
A formal document management solution to manage the lifecycle of Estates key documents and records |
|
| Sharing Documentation with Internal UoE Staff (Including Estates) | Gives the ability to manage permissions and access rights across UoE |
|
Deliverables (Outputs)
|
Benefits
The top level benefits are outlined below
|
01 |
Benefit |
|
|
By delivering a records management system we will have one single source of truth for all documents reducing the risk of out of date information and reducing labour time in sourcing the information |
|
02 |
By delivering a records management system we will reduce the response time to FOI |
|
03 |
By introducing the records management system we will be able to address the GDPR compliance |
|
04 |
In the case of a major disaster we will be able to still have our records available as these will be available on the cloud. |
Success Criteria
|
1 |
Functionality: The system provides the key functionality required by the Estates business functions as defined in the requirements document. |
|
2 |
Reliability: The system is stable, presenting no critical or major bugs. |
|
3 |
Searchable. The SharePoint repositories will be fully searchable and documents easily retrievable using metadata. |
|
4 |
Migration. All data will be held in the SharePoint repositories and nothing left in old drives. |
|
5 |
Adoption: All Estates staff are trained in the use of the system and are storing documents in the correct locations. The Estates Intranet is the default location for all users when looking for departmental communications or guidance, policy or training documentation. |
|
6 |
Support: There is a support model in place which is well understood by the user community and it delivers the required answers and actions within agreed service levels. |
|
7 |
Maintenance: There is a reliable and regular delivery of patches and upgrades which presents no loss of working time to the Estates business. |
|
8 |
Integration: Links to the MyProject system are in place and working as expected. |
|
9 |
External Access: Third parties (External to the University) are able to access permitted areas of the system to view and upload documents. |
Project Milestones
|
Note there is no decommissioning as we are not replacing any existing system as part of this project.
