Overview
Background
To establish the processes and documentation that are required in order to allow the creation of a central support service for the University’s industry engagement, using the processes and platform (CRM) already developed for Edinburgh Innovation (EI), the Bayes Institute and the Principal’s Office. This service will centralise support that would otherwise be carried out by specialists in each business unit.
This service is needed immediately, in order to handle the volume and pace of work required for the City Deal in particular and the increasing demand for industry relationship management (IRM) across the University.
It is expected that this Project will form the basis of a number of further Projects that will likely see the formation of a CRM Programme within IS in the 2019/20 financial year.
Scope
- Determine and document the service strategy and support requirements for the IRM service
- Establish supporting SLA/OLAs
- Complete a procurement options appraisal, the precursor to a procurement strategy and understand if licensing can be consolidated
- Establish and document any training requirements
- Agree the required processes / contact point(s) in support of the new Centralised Service
Out of Scope
The following items will most likely form deliverables of future projects, this project is a feeder for these:
- The completion of a procurement strategy and any subsequent actions required
- This Project will establish requirements / the ability to run / support a Service from within Service Management, however implementation will not be possible until Resourcing is available, recruitment is out of scope
Objectives and Deliverables
Priority: M = Must Have; S = Should Have; C = Could Have; W = Want
- M = has to be satisfied for the final solution to be acceptable in terms of delivery dates, compliance, viability etc.
- S = high-priority requirement that should be included if possible -workarounds may be available
- C = a nice-to-have requirement
- W = want but will not be part of this project
- O = Objective
- D = Deliverable
Ref. | Objectives and Deliverables | Owner | Priority |
O1 | Determine the scope of the IRM service | ||
D1 | Work with the Business and IS / Service Management to determine and document support requirements | Business Analyst | M |
D2 | Work with the Business and IS / Service Management to determine / document the Business / Service Strategy and Requirements, in order to establish the required SLAs/OLAs | Business Analyst | M |
D3 | Identify and document the Business Service Owner | Project Sponsor / Business Analyst | M |
D4 | Establish and document support processes and reporting need for the IRM Partner Groups | Business Analyst / Business Lead | S |
D5 | Analyse EI's CRM's integration with EASE / IDM and determine any authorisation / User account support requirements moving forwards | App Man / Dev Tech | S |
D6 | Complete a Service Design Document for the IRM System Services - this document, along with other supporting documentation will be the chief deliverable of the Project | Business Analyst / Business Lead | M |
D13 | Agree and document the job description for the Service Manager post | Business Analyst / Business Lead | S |
O2 | Determine the Procurement / Licensing Requirements | ||
D7 | Produce a paper on CRM technology utilised, what is to / not be consolidated and associated questions / decisions required, please note that not all of the questions / decisions might be answered at this stage, but they will be documented ready for a suitable Project to pick them up / action them at a later stage, if required | Business Analyst | M |
D8 | Work with Procurement to complete a procurement options appraisal for the technology platform underpinning the IRM | Business Analyst | M |
D9 | Work with Procurement and Production to see if licensing can be consolidated with the Supplier | Business Analyst | S |
O3 | Deliver Training Strategy | ||
D10 | Agree a strategy and document, by which the service will provide training when required to do so | Business Analyst / Business Lead | M |
O4 | Deliver / Deploy | ||
D11 | Agree and document the strategy for / handover of the Service to IS Service Management / Production | Business Analyst / Business Lead | M |
D12 | Agree and document / put in place any required processes / contact point(s) in support of the new Centralised Service | Business Analyst / Business Lead | S |
Benefits
Users of the IS (Service Management) Supported IRM Service would benefit from:
- Project based approach for future onboarding
- Change Management
- Relationship with the IRM Business Owner
- Establishment of SLAs/OLAs
- The service will provide central management for the vendor relationship, with the possibility of negotiating reduced licence costs
- The provision of a centralised Support Service for the various IRM User Groups within the University
- Consolidation of technical knowledge and support
Success Criteria
- The ability to be able to establish a new central IRM Support Service within Service Management with a clear engagement process
- Delivery of SLAs/OLAs
- A plan / strategy for the consolidation of licensing for CRM across the UoE for IRM (where possible)
Project Milestones
Stage | Milestone | Due Date | Previous Date | Complete | |
---|---|---|---|---|---|
Plan | End of Planning | 05-Jul-2019 | 14-Jun-2019 | No | |
Analyse | Map existing EI processes | 02-Aug-2019 | No date available | No | |
Analyse | Map existing EI training processes / define a Training Strategy | 09-Aug-2019 | No date available | No | |
Deliver | Determine support & reporting requirements / produce a Service Definition Document | 30-Aug-2019 | No date available | No | |
Deliver | Establish / agree OLA/SLAs | 30-Aug-2019 | No date available | No | |
Deliver | Produce an Options Appraisal document | 13-Sep-2019 | No date available | No | |
Deliver | Produce a paper on CRM's technology utilised, what is to / not be consolidated and associated questions / decisions required | 20-Sep-2019 | No date available | No | |
Deliver | Delivery | 25-Sep-2019 | 19-Jul-2019 | No | |
Close | Closure | 27-Sep-2019 | 02-Aug-2019 | No |