Closure Report

Project Summary

This project was continuation of EST093 Estates Strategic Reporting. As the scope of the project is considerably clearer than it was back in April 2016, it has been decided to create a new project EST109 to cover the remaining activities. The EST093 project brief was originally created in May 2016. The planning phase was completed and two pieces of business analysis were completed and signed-off. In December 2016 the project was put on hold for a number of reasons (resource constraints, changing business drivers, emerging EDW programme). As a different landscape emerged, the project was re-booted in June 2017. Based upon the current situation, the brief and associated artefacts have undergone a major revision. This document supersedes all previous versions of the brief. To refer back to the original brief, use the following link – https://www.projects.ed.ac.uk/project/est093

Scope

The scope of the EST129 project captured in the project brief and repeated here has been delivered,  with the following exception "the ability to extract data and generate their own custom analysis and reports" is limited to data available in the data universe extracted to support reports in scope of this project". 

The scope of this project is to deliver a strategic reporting solution for the following: Space Management. Covers the definitions and relationships between buildings, floors and rooms. Maintenance Management. Covers the activities of the hard services organisation when executing the ongoing planned and reactive maintenance of the University’s 550 buildings. This covers approximately 60,000 reactive maintenance tasks and 30,000 compliance tasks per annum.

The initial key reporting requirements centre on workload, performance & productivity, cost, and maintenance trend analysis. The solution in question will include: A set of agreed, certified reports. The provision of an ad-hoc query capability to a limited number of suitably trained users, giving them the ability to extract data and generate their own custom analysis and reports. The solution will utilise existing BI/MI services (SAP BI Suite), but based on a new capability; the Enterprise Data Warehouse (EDW).

The creation of the space and maintenance management subject-areas will not only serve the requirements of this project, but also act as a guiding light for all future Estates Management Information, Business Intelligence and strategic reporting projects. 5. EDW EDW is being delivered by a dedicated programme; part of the Digital transformation initiative (DTI). For further information refer to the following link: https://www.projects.ed.ac.uk/programme/dtiedw This project has a strong dependency on the overall EDW programme, and is considered to be an ‘early adopter’ of its services. This will has its advantages and disadvantages as detailed later in the document. The foundation layer within EDW will not actually contain a segregated storage area for Estates data; All EDW data will be stored in such a way that encourages links and relationships between datasets to be made.

The eventual aim (requiring further business data acquisition projects) will be to store all the important Estates data required to drive business intelligence and decision making both within Estates and across the University. This following diagram provide a visual representation of the BI/MI landscape that will be enabled by the EDW programme

 

Enterprise Data Warehouse Landscape

Objectives and Deliverables

 

No. Description Priority Achieved (Yes/no)
O1 Business Analysis    
D01

Space Management Business Analysis

The analysis was initially created and signed off in August 2016.  This analysis will be refreshed and will also make use of the new BI/MI analsysis toolkit, being produced by DTI019. Link to original document.  Space requirements document

Must have Yes (see lessons Learnt)
D02 Maintenance Management Business Analysis see D1.1 above to link to original document Must have Yes (see lessons Learnt)
O2 Technical Design    
D03

Space Management Data Design part of Application and Data Architecture document (ADA).

Notes on deliverable: The Technical Architecture Design (TAD) has been produced, IS project team are not familiar with  Application and Data Architecture document (ADA).

Must have Yes TAD
D04

Maintenance Management Data Design Part of Applications and Data Architecture document (ADA)

Notes on deliverable: The Technical Architecture Design (TAD) has been produced, IS project team are not familiar with  Application and Data Architecture document (ADA).

Must have Yes TAD
D005 Space Management SDS Must have Yes
D006 Maintenance Management SDS Must have Yes
O3 EDW Foundation Layer    
D07

Space Management Foundation Layer

Notes on deliverable, The foundation layer within EDW will not actually contain a segregated storage area for Estates data; All EDW data will be stored in such a way that encourages links and relationships between datasets to be made." which may cause confusion if two foundation layers are later listed as deliverables.

Must have Yes
D008

Maintenance Management Foundation Layer

Notes on deliverable, as per D07 stated above

Must have Yes
O4 EDW Access Layer    
D09 Space Managment Access layer(s) Must have Yes
D10 Maintenance Managment Acess layer(s) Must have Yes
O5 Semantic Layer    
D11 Space Management SAP/BI Suite Universe(s) Must have Yes
D12 Maintenance Management SAP/BI Suite Universe(s) Must have Yes
O6 Presentation Layer    
D13

Certified Space Management Reports

Delivered reports and current status is listed in a table at the end of this section

Must have Yes
D14

Certified Maintenance Management Reports

Delivered reports and current status is listed in a table at the end of this section

Must have Yes
O7 Training    
D15

SAP/BI Suite Training and Access

A combination of on line training and face to face training has been provided.  Access has be defined based on Gold copies available to Estates Systems Support Managers for Space & Maintenance reports and Senior Space Manager.  With run access to users based on job requirements.  

Should have Delivered
O8 Organisation and Support    
D16 The adaption of the Estates organisation and processes to encompass local support for BI/MI service(s) within the overall Service managment framework Should have

Work in progress at review stage within IS for the Operational Level Agreement.  At URL: https://www.wiki.ed.ac.uk/display/insite/Estates+EDW+OLA

Noted Production Services have stated that they are comfortable for this to be a post project closure deliverable

D17 Services Management - the inclusion of support for Estates within the overall Service Management BAU capability Should have

Work in progress at review stage within IS for the Service Definition.  At URL: https://uoe.sharepoint.com/:w:/s/SMEDSTeam/ERwwRYoUxQRMtfJkJhDT-zgBWVIB4h_Agu5qjFdj7m4VIw?e=lHJgP2

Noted Production Services have stated that they are comfortable for this to be a post project closure deliverable

O9 De-Commission preparation for Existing Space Mart Solution    
D18 De-Commission process Must have Service Management have confirmed that replacement reports have been moved to archive.  A McFarlane reaffirming with Estates users that they are in agreement
D19 Parallell run: existing solution vs new solutions Must have

For Space reports A McFarlane checking with Estate User Richard Mann if reports for August should be run by Production Management (Ron McLeod).  

The following reports have been released to production,

The current status on reports delivered is detailed in the following table, based on feedback from Estates Users.  The most likely estimates for fixes to enable business use is 10 days.  The maximum estimate is 15 days.   Estimates are available on known fixes, for several reports Estates will need to complete retests in Production. 

Report Production Pass Issue raised Changes - Must, should Area Owner Status Cost Impact (Likely) Notes on Cost Impact
R1 Space Transfers Retest     Space Report  Richard Mann      
R2 Rates Inactive Rooms  Retest     Space Report Richard Mann      
R3 Rates Rooms Still Active Retest     Space Report Richard Mann      
R4 Helpdesk Customer Survey Report Fail EST004, EST005, EST010, EST011 Must Maintenance Report Colin Pritchard EST005 must be fixed Business accepted close:  EST004, EST010, EST011 2 days Fix for EST005
R16 Maintenance Services - Productivity Report Fail EST004, EST016 Must Maintenance Report Colin Pritchard EST016 must be fixed Business accepted close:  EST004,  3 hours  
R17  Maintenance Services Productivity Trend Fail EST004, EST009, EST017, EST018  must Maintenance Report Colin Pritchard EST017 & EST018 must be fixed EST009 Estates Data Cleanse Business accepted close:  EST004,  2 hours  
R18 Contract Services Productivity Report Pass  EST004, EST006, EST009 No Maintenance Report Colin Pritchard EST009 Estates Data Cleanse Business accepted close:  EST004 & EST006,     
R19  Contract Services Productivity Trend Pass  EST006, EST009 No Maintenance Report Colin Pritchard EST009 Estates Data Cleanse Business accepted close:  EST006,     
R6 Number of Work Requests Per problem Type Fail EST004, EST005 Must Maintenance Report Colin Pritchard EST005 must be fixed Business accepted close:  EST004   Cost noted row 5, 
R7 Repair Type Exception Report Fail EST001, EST004, EST012, EST013 Must Maintenance Report Colin Pritchard EST001, EST012  EST013 must be fixed Business accepted close:  EST004 5 hours  
R8 & R9 - Escalated Work Requests: Maintenance & Contract Services Retest  EST004, EST009. EST014 Must Maintenance Report Colin Pritchard EST009 Estates Data Cleanse Business accepted close:  EST004 Retest EM EST014     
R11 Outstanding Work: Aging Report Fail EST001, EST002, EST009, EST015 Must Maintenance Report Colin Pritchard EST001, EST002 & EST015 must be fixed EST009 Estates Data Cleanse   2 days & 1 hour EST001 cost for change reported in row 11 Costs for EST002 & EST015 stated here
R12 PPM – Planned Preventative Maintenance Fail EST004, EST005 Must Maintenance Report Colin Pritchard Business accepted close:  EST004 Fix required EST005 & EST020 2 days & 1 hour Cost noted row 5 for EST005.  Cost here for EST020, 
R10 - Work Request Summary Report Accepted at UAT sign off EST003, EST004, EST005, EST009 No Maintenance Report Colin Pritchard This report was not on UAT test schedule.  It was accepted at Acceptance sign of to be delivered as is.  Incidents raised are based on reports using the same data & report styles. Business accepted close:  EST004 EST009 Estates Data Cleanse Fix required EST005 & EST003 7 hours  
R13 Quality and Quantity of Information Accepted at UAT sign off EST009 No Maintenance Report Colin Pritchard This report was not on UAT test schedule.  It was accepted at Acceptance sign of to be delivered as is.  Incidents raised are based on reports using the same data & report styles. EST009 Estates Data Cleanse      
R14 Performance Report Accepted at UAT sign off   No Maintenance Report Colin Pritchard Accepted at UAT sign off.  No incidents raised as this was not tested in production & does not share the same data or report features with other reports.    
R15 Performance Report Trend Report Accepted at UAT sign off   No Maintenance Report Colin Pritchard Accepted at UAT sign off.  No incidents raised as this was not tested in production & does not share the same data or report features with other reports.    

Out of Scope

The following table lists Out of Scope deliverables.  The following out of scope deliverables have been delivered:

  1. OS-02 EST092 delivered 3 reports and was closed.  Operational reports have been provided in EST109 for Maintenance reporting.
  2. OS-04 Data analysis to enable Estates to solve "data quality issues within Estates Operational systems" has been delivered and is stated in the Production Log Issue a copy is available at the end of this report
  3. For OS-05, Removal of existing Estates 'Space Mart' solution, Service Management has started, refer to note D18, In Scope deliverable

 

No. What Details
OS-01 Provision of separate DW Infrastructure platform for Estates The Estates solution will be built entirely using the EDW platform
OS-02 Operational Reporting Operational reporting will be provided as part of Project EST092 and other follow-on projects.  For a comparison of the differences between operational and strategic reporting.
OS-03 Provision of MI Dashboards Dashboards will not be provided as part of this project
OS-04 Solving data quality issues within Estates Operational systems The project is likely to highlight data quality issues within Archibus and other source systems. The rectification of these data quality issues is outside the scope of this project.
OS-05 Removal of existing Estates 'Space Mart' solution The existing Space mart solution will be de-commissioned in live as a consequence of this project but NOT as part of it. The de-commissioning work will be a small apps mgmt task and outside the scope of this project.

 

Benefits

The listed benefits cannot be confirmed until reports are run in live alongside existing reports.  It is recommended that this area is revisited in an agreed time frame.

For BE- 02 was descoped in discussion with Richard Mann & the Data Architect. The data is in the EDW, and can be readily added to the Space reports, however Richard has confirmed that the underlying finance model the data comes from has been phased out and shouldn't be used.

  What Details
BE-01 Improved business intelligence regarding hard service maintenance mgmt operations.  Improved ability to drive customer satisfaction and efficiency.

Workload volumes and value of work being managed - operational (live), strategic (archived).

Performance

Number of jobs meeting or missing SLA targets

Productivity

Number of visits per craftsperson per productive period

Cost

Cost spent per work stream (e.g. fire alarm activity, or work team or member of staff)

Trend analysis

Reviewing repeated maintenance activity per location, asset work team

BE-02

Improved business intelligence regarding space mgmt; more regular reporting available.

Improved capability for driving the efficient use of space

 
BE-03 An enable for the combination of space data with financial data so that authoritative "cost per unit area" data is readily available.  
BE-04 The EST109 project establishes precedent and repeatable process for all subsequent business data acquisition projects, both in Estates and across the University. This will drive the creation of a set of project mgmt guidelines, a deliverable via the EDW programme.

 

Analysis of Resource Usage:

Staff Usage Estimate:  312 days

Staff Usage Actual:  679 days

Other Resource Estimate: £xxx

Other Resource Actual: £xxx

Other Resource Variance: xx%

 

 

Outcome

This project will close at the end of July 2020.  A budget for 20/21 finance year is not available.  A number of reports are in Retest and others have not met business requirements.  The IS estimates to fix the reports have been provided within this report to enable Estates to prioritise and manage changes as part of Services agreements.  

Explanation for variance

  1. Estimates for IS timelines were under estimated for a new technology delivery.
  2. There were several changes in personnel (Estates & IS) each change required a knowledge build period.
  3. The Project continued without project management support for a period resulting in additional spend.  An agreement has been reached between IS and Estates for a reduction in charges.

Key Learning Points

  1. This project raises the risk to projects of changes to key staff.  This is a lessons IS are aware of, and the recruitment strategy has changed from contractor to FTC.  Also, providing dedicated staff to Estates
  2. For a period IS continued to work on the project without support of a Project Manager.  As a consequence Monthly reports, the management of Risks and Issues and authorisation from IS and Estates stakeholders were missed.  Adherence to WIS Programme and Project governance must be applied to avoid a repeat.   
  3. The 2020 stage of this project has benefited from meetings between IS Data Architect Analyst and BI experts and Estates Users to clarify detail on business requirements.   An earlier engagement of the Data Architect Analyst, BI experts and Estates SME in the Requirements Gathering stage would have avoided redundant work, identified and resolved issues earlier, enabled more efficiencies and would have aligned specifically Maintenance reports closer to business needs.
  4. Agreement on detail to include in JIRAs: headers, description of issue, description of fix and rules, for example one issue per Jira should be agreed upfront and called out if not adhered to.  This  would avoid additional communications outside the error resolution process.   
  5.  Going forward an Agile iterative approach would be recommended to enable IS to build knowledge on current, constantly updated data and then enable early testing in the Production environment. 

Outstanding Issues

There are several issues  with the reports in production.  It is anticipated that Estates will prioritise fixes based on business needs and manage changes through production agreements.

The incumbent Project Manager will scheduled a performance review with Estates during October 2020 to gather lessons learnt and validate benefits.  Due to Estates priority business demands it is expected that retests will not be completed until October 2020.  

Ref. Date Report Name /Number Description of Issue  IS Reviewer Date Assigned IS Reviewer Recommended IS resolution Date Assigned Estates Reviewer Estates Response Estimated effort to correct, where applicable Agreed solution  Status Date Closed
EST001 10/7/2020 R11 - Outstanding Work: Ageing Report Raised under Jira EST109_196 Status breakdown table to be re-ordered to match WR workflow Required to make report more user friendly and clearly define those status outside normal workflow (assigned/rejected/cancelled) Andrew McF 20/07/2020 Andrew to provide Estimate to change report - 2 hours max 20/07/2020 24/07/2020 EM & CMacK Must have Changes would be significant for users that are running reports monthly.    2   Open with Estimate   
EST002 10/7/2020 R11 - Outstanding Work: Ageing Report Data mismatch - Report run 08/07/20 for work team BLD_Serv, shows 4 jobs raised in Jun 2020 but was 5 showing in webcentral and client.  Re-checked 09/07/20 in case changes had been made in webcentral recently, and figures still do not match.  Upon further comparisions it seems the figures are off for most months. Wilbert K 20/07/2020 The underlying issue is in the data supply. It affects 360 work requests or less. I would estimate the time required for analysis and rework: Minimum: one day Maximum: three days Most likely: two days 20/07/2020 24/07/2020 EM & CMacK MUST be changed, report as is - is not fit for business purpose  14   Open with estimate  
EST003 13/7/2020 R10 Floor codes are missing from 160,000 work request records Wilbert K 20/07/2020 Requires a change to the way identifiers are constructed in the foundation layer (add type to facility_id) Estimate for rework: Minimum: one day Maximum: three day Most likely: one day 20/07/2020 24/07/2020 EM & CMacK MUST be changed, report as is - is not fit for business purpose Issue will impact future self build reports   7   Open with estimate  
EST004 13/7/2020 R4, 6, 7, 8, 9, 10, 11, 12, 16, 17, 18 WR without a corresponding WO in source won't get a workteam value in the EDW. The vast majority of these WR have been cancelled or rejected.   20/07/2020 It was agreed to leave this issue and not resolve it now. 20/07/2020 24/07/2020 EM & CMacK Agreed mirrors BAU No further actions   No further actions Closed 24/07/2020
EST005 13/7/2020 R4, 6, 10, 12 EDW reports 20 odd fewer work requests with a cause than Archibus does. Out of 142,099. Update: the work requests affected tend to be recent- most are from 2020. The EDW sometimes reports a status Archibus doesn't have, and vice versa. Cause isn't clear.    20/07/2020 This issue needs further investigation and resolution. The issue lies in the staging or foundation layer. Effort required: Minimum: 1 day Most likely: 2 days Maximum: 3 days 20/07/2020 24/07/2020 EM & CMacK MUST be changed, report as is - is not fit for business purpose Issue will impact future self build reports   14   Open  
EST006 13/7/2020  R18 and 19, depending on the need for Purchase Orders without Work Requests. Purchase Order with associated work requests are doubled up: once with, once without the work request code. Because P.O.s without work requests aren't currently reported on, it doesn't affect current reports.   20/07/2020 Resolution would require changing the way foundation to access ETL selects records. The issue is unlikely to affect any reports in their current form. However, if the reports were to be altered to include P.O.s without associated work requests, then the issue would need to be resolved. 20/07/2020 24/07/2020 EM & CMacK Not a business requirement to change data count for this report.  Reports only looking at PO with WR.  Noted that this may be  a requirement for future reports from Contract Services   No further actions Closed 24/07/2020
EST007 13/7/2020   140,000 account codes missing from purchase orders Wilbert K 20/07/2020 Issue: Change the source to foundation ETL such that the contract_gl_account gets populated with all the corresponding gl_account and contract records This does not affect any current reports, but may be a major issue for any new/changed reports. 20/07/2020 24/07/2020 EM & CMacK Not a business requirement to change.  Estates not reporting at this level.   No further actions Closed 24/07/2020
EST008 13/7/2020   140,000 job codes missing from purchase orders Wilbert K 20/07/2020 Issue: Change the source to foundation ETL such that the contract_budget table gets populated with all the corresponding gl_account and budget records This does not affect any current reports, but may be a major issue for any new/changed reports. 20/07/2020 24/07/2020 EM & CMacK Not a business requirement to change.  Estates not reporting at this level.   No further actions Closed 24/07/2020
EST009   R8, 9, 10, 11, 13, 17, 18, 19 The names of two work requestors fail to show. This is due to spelling differences and potential duplication. Update: the vast majority of POs with missing names are of one person: Colin Bambery with 255. The remainder are 5 people with between 1 and 3 each. Cause is unclear- there are no spelling or duplication issues in the source       20/07/2020 22/07/2020 Pauline Smith & Jane Brodie Estates to review and cleanse data   Estates data cleanse Open Estates 22/07/2020
EST010 20/07/2020 R4 Filter bar only shows prompts, unable to add drill filters Andrew McF 20/07/2020 No Further Action 20/07/2020 24/07/2020 EM & CMacK Agreed that solution in production is fit for business purpose.  Add to lessons Learnt - report design should include drill filters    Lesson Learnt Add LL 24/07/2020
EST011 20/07/2021 R4 May have already been discussed, but it would be prefered to only see entries where survey has been completed, reducing the amount of time spent applying filters Andrew McF 20/07/2020 No Further Action 20/07/2021 24/07/2020 EM & CMacK Agreed that solution in production is fit for business purpose.  Add to lessons Learnt - report design should include drill filters    Lesson Learnt Add LL 24/07/2020
EST012 20/07/2022 R7 High level problem type column also contains detail problem types, but not grouped under high level as in other reports.  Wilbert K 24/07/2020 This looks like an issue with the regular expression in the universe that separates the high level from the low level codes. The access layer is sound. Estimated time to resolve: 2 hours   20/07/2022 24/07/2020 EM & CMacK Must Have Changes would be significant for users that are running reports monthly. Critical data count will be missed   2   Open with Estimate  
EST013 20/07/2023 R7  Detailed table is broken into various small tables with title "view based on chosen drill filter :unfiltered" Andrew McF 24/07/2020 Section needs removed. Estimate: 1 hour. 20/07/2020 24/07/2020 EM & CMacK Must Have Changes would be significant for users that are running reports monthly. Critical data count will be missed   1   Open with Estimate  
EST014 20/07/2024 R8&9 Data comparison needed, parameter - date 19/07/2020, work team HD_G_L_PC_FA, Craftsperson Emma Lewis (EDW 92 Webcentral 90)     Update 24/07/2020 assigned to Eileen Action assigned 20/07/20 NFI Andrew to provide Estimate to change report  ( IS email 20/07/2020 contains comprison report provided by Eileen - unsure what this is request is for) 24/07/2020 24/07/2020 EM & CMacK Eileen to rerun reports      Estates to re test  
EST015 20/07/2025 R11  unclosed end of period" criteria needs to be checked, appears to be counting cancelled WRs here parameters - date 01/10/17 to 31/10/17, Work Team BLD_SERVICES Wilbert K 24/07/2020 The 'Total Work Requests' variable needs to exclude cancelled work requests. Estimate: one hour 20/07/2020 24/07/2020 EM & CMacK Must have 1   Open with Estimate  
EST016 20/07/2026 R16  Live and Completed tabs have the same values, parameters - dates 23/03/18 to 30/03/18, work team MS_KINGSB Wilbert K 20/07/2020 The change is limited to changing the work request status variables rather than changing the report level filters; about 3 hours 20/07/2020 24/07/2020 EM & CMacK Must have, change assumption agreed 3   Open with estimate  
EST017 20/07/2027 R17 Do not count Work Request with problem type = CALL OUT   Andrew McF 20/07/2020 Andrew to provide Estimate to change report - 1 hour 20/07/2020 24/07/2020 EM & CMacK Must have 1   Open with estimate  
EST018 20/07/2028 R17 Primary Trade seems to reflect current value held, which will affect historic reports, parameters - dates 23/03/18 to 30/03/18, Work team MS_KINGSB (example CPs Gary Stewart/Kevin Cameron/Jamie Forbes) Wilbert K 20/07/2020 Assuming that the change required is to define sections by Requested Trade (on Work Request) rather than Primary Trade (on the Craftsperson): 1 hour   20/07/2020 24/07/2020 EM & CMacK Agreed fix details as described  - Must have 1   Open with estimate  
EST019 21/07/2020   Click on a value to drill feature does no work.  Issue is that clicking on a value in table does not return a breaddown of that value but only splices by universe dimension. To fix measure variable on the reports would not made into universe objects so they could be used in a drill hierarchy. This will take a lot of scoping work. Andrew McF 21/07/2020 Scoping could be circa 3 days. Implementation could be in the weeks. 24/07/2020 24/07/2020 EM & CMacK Can work with deliverables.  As work round available.   To be noted in Closure Report that Drill down features do not match feature described in BRD.     Lesson Learnt Add LL 24/07/2020
EST020 22/07/20 R12 22,225 entries.  Same dates entered into Archibus on OPPPM report view return 25,980 entries.  Believe this is related to EST005 Wilbert K   While we'd have to know what parameters were used in the reports to arrive at these precise numbers, there does seem to be an issue with PMP and PMS codes on work requests (WR). Report 12 filters WR on the presence of PMP codes. The issue is that the PMP and PMS codes on work requests in Archibus don't link to codes in the PMP and PMS tables in Archibus. I think old codes are deleted from those tables, while the WR records stay the same. One solution would be to bring back the old codes in the Archibus PMS and PMP tables, so that everything links up again. Another solution would be to let the issue 'age out'; new WR will have linked PMP and PMS codes, ones without it are already older.   Finally, we could source PMP and PMS codes from the WR table for the EDW instead of the PMS and PMP tables, as per BRD. This would be a new attribute. Worst case estimate: 3 days Best case estimate: 1 day Most likely: 2 days 24/07/2020 24/07/2020 EM & CMacK MUST have 14   Open with estimate  
EST021 29/072020 R17 The issue was reported on Jira EST109 -196 Date work started: 01/01/18 – 30/12/18 Work team: Ms Roofer Craftsperson: Bruce Reynolds Problem type: External   Should bring back a total of 44 work requests and 50 visits Client returned 43 Work Requests and 51 Visits     Investigations by Wilbert K identified an issue with how date had been recorded.  A fix has been executed.  29/07/2020 As agreed with Estates on call 29/07/2020.  The PM will close this Jira on behalf of Estates. Estates to schedule time to Retest       Estates to re test  

 

 

 

AttachmentSize
Image icon edw.jpg73.05 KB

Project Info

Project
Estates Strategic Reporting - Space & Maintenance Mgmt
Code
EST109
Programme
Estates Systems & Technology Maintenance (EST)
Management Office
ISG PMO
Project Manager
Josephine McDonald
Project Sponsor
Karen Adamson
Current Stage
Close
Status
Closed
Project Classification
Grow
Start Date
02-Oct-2017
Planning Date
06-Oct-2017
Delivery Date
26-Jun-2020
Close Date
31-Jul-2020
Programme Priority
3
Overall Priority
Higher
Category
Discretionary