Impact
Priority and Funding
This Compliance project has normal priority.
It must be noted that the project has been broken into two phases, a procurement and an implementation stage.
All aspects of Information Services, both during Phase One Procurement and Phase Two Implementation are Core funded from the Corporate Services Group.
Any Third Party Solution will be funded by the Business (H&S / Fire Safety Unit).
Both will require careful analysis and potentially an amount of re-planning at key points, the following milestones have been added to facilitate this:
- During the first phase, a strategy for procurement will need to be determined once responses to the PIN are received reference milestone: Prior Information Notice (PIN) Completed / Procurement Approach Determined (22-Mar-2019).
- The second is located at the end of the procurement phase reference milestone: Solution Implementation Planning Completed (13-Sep-2018)
Both could see a requirement to re-analyse / plan the project, particularly in terms of its timeline, resource and budget, if this is the case this will be handled utilising change management procedure.
There is also the chance that the Project itself could be subject to reappraisal or even closure if suitable responses / solutions cannot be found, the following exit points have been identified to track / help facilitate this:
- Exit Point - No Interest Received From Third Party Suppliers 29-Mar-2019
- Exit Point - No Supplier Chosen 23-Aug-2019
The total IS / Compliance budget for this Project is 284 days, split across the 2018/19 and 2019/20 financial years.
| Year | Estimate at 19/20 Planning Review | Revised Estimate |
| 2018/19 Estimate | 140 | 144 |
| 2019/20 Estimate | 60 | 140 |
Please note that this estimate is based on procurement of a internally hosted solution and the development of potential interfaces with existing UoE systems, eg. Estates Archibus system for building data. It should be noted that implementation costs would likely decrease if a SaaS solution is discovered and/or there was no development requirement;
- Saas solution could reduce estimate by around 15 days
- No development resource could reduce the estimate by around 14 days
A PICCL #1: Budget Readdress After Planning has been raised over the estimated increase to budget after planning.
Impact and Dependencies
This project will have no known impact on any existing operational systems on inception, though if during analysis it is deemed that integration into other systems would be beneficial, for instance to retrieve golden copy of building data, or assets for example, then this could be considered. Risk #7 System Integration to Obtain Data Could be Required has been raised to track the risk to budget / the current proposed timelines.
There is the distinct possibility that after analysis / procurement that a number of Business processes and / or policies may be subject to change. Risk #3 After the Procurement Phase it is Possible that an Appropriate Solution / System is not Discovered has been raised to track this.
Project Risks
