Completion Report

Project Summary:

Th objective of the project is to migrate the current METERology system  from the existing Estates PC to a Virtualised Server on a supported IS Apps Infrastructure, ensuring the application continued to function as required.

Deliverables

1. Deliver METERology to an IS Apps managed supported infrastructure  
2. Ability that METERology can continue to Send and Receive data on the new/changed server
3. Ability to add meters
4. Deliverables assumptions: No special hardware requirements, dongles, etc. However agreement reached to enable Meterology access to maintain operational aspects of the system, such as adding new meters.

All deliverables have been met successfully.

Analysis of Resource Usage:

Staff Usage Estimate: 56 days

Staff Usage Actual: 63.5 days

Staff Usage Variance: 13%

Other Resource Estimate: 0 days

Other Resource Actual: 0 days

Other Resource Variance: 0%

Explanation for variance:

Originally the scope was to migrate the Meterology work to a supported UoE server, where updates and support could only be managed in regular hours. However, due to the Supplier also supporting the application, sometimes at weekends or overnight, the decisions were made to put Meterology on a Private Secure BEMS network. Apps Support still require to be informed when updates have taken place, but it enables Meterology the flexibility when they require to support the application. The Private network ensures that Meterology do not have access to other University applications.

This decision was made after the Brief had been agreed and the project was planned. The details of the scope changes where only a LIVE VM was required, changed how the original project was envisaged totally. However in a lot of ways this simplified the project, but did effect the way on how the project was supported and how it effected IS Apps and Tech Man and what was expected of them. Please see PICCL 4 for more information The elapsed time for the project was extended by 5 to 6 weeks due to supplier access requirement and subsequent design.

The scope changes included the following:

1. Project originally required 4 servers to accommodate TEST and LIVE. However the agreed design required in only 1 server as the d/b and application were combined on 1 virtual server. In addition the business directed there was no need for a Test environment.
2. Having proceeded with only LIVE, the requirement was then made essential (whilst discussing the Technical Architecture document) to provide 24 hour access to METERology (Vendor)
   1. The Vendor is not only the supplier but updates our service with new meters etc when required.
3. Due to a number of changes in the Project Technical Architecture Design and the decision we have made to go with the Private secure network which will house the METERology VM server. As a result of the above this changed the impact on the project budget.

Disaster  Recovery was carried out and allowed for 8 days budget, however there were other items that were reduced, so in the end it resulted in a 6 day project increase to 62 days.

The decision was made to move to a VM server on a closed private BEMS network. This resulted in updating the supporting  documentation, and extending project  management time  Estimation increase is covered in : PICCL 7

Key Learning Points:

The project was able to deliver the required supplier remote access on terms both acceptable to the business, supplier and IS Apps due to engaging with all parties and understanding their requirements.

As a consequence of the supplier requiring 24 hour access the decision was made to house the Estates network on a private server so that no other applications are affected (and no risk to them either).

Outstanding issues:

Post go live activity

Items that required sorted (6-May):

1. Has the secondary DNS been removed yet as discussed last week?  'meterology-live'
   1. A Unidesk call I140507-0750 has been raised  (7-May) with ITI and this will be carried out, so this is in progress and currently being verified 13-May - ITI Architecture call has been completed and closed.
   2. Unidesk call I140513-0618 has now been raised as 'meterology-live' still exists. - in progress with ITI IS CIS Projects and Services (Networks). Networks completed work 21-May. Further action still required 22-May as did not remove the extra DNS. This was resolved on 26-may and verified 27-28 May, call has ben completed and Cclosed
2. Estates tried to RDP onto the server this morning but got a 'request to change password' message?  We don't get this on the other virtual servers?  (He hasn't changed it yet)
   1. This has been corrected and Estates have verified to works as expected now. Completed 7-May
3. Will we be able to run Excel on the server as requested by Martin? - Completed 13-May   details below

   1. PM queried regarding Excel on the VM Server, can we understand from our perspective why you require excel on the server please?

      If it is to create a file that you can transfer elsewhere then the excel spreadsheet will be held on an Estates PC, If it  is a spreadsheet you need on the server for something there that is different.

      It is more to increase our understanding of your requirement please?

   2. Information from Estates Business.  'We do have Excel on the Sigma virtual server so it obviously can be done.  Whilst we can probably do some work around for the others at the moment by transferring via clients, it's a bit inconvenient.  Also, I've just been to a  demo of a potential replacement for the Optima system and that requires Excel on the server for reporting purposes so I don't want to back myself into a corner on this one as we really don't know what the next developments are on these systems.  If IS are digging their heels in on this one - and I really can't see why as it's been done already on the Sigma server - then we'll just have to live with it I suppose but we must have the proviso that if we do find we require Excel, then it will be installed at a later date.  I fully appreciate that it may not be the 'norm' to install Excel on IS virtual servers.  However, I think these metering and BEMS virtual projects have demonstrated that these are not 'normal' systems and do have some odd, sometimes quirky requirements. (7-May)

   3. Being followed up with Production Management

      1. If Excel has to be added to the server as a delivery of the Metering system as this is needed in future upgrades

      2. Production Management agreed - 'Please go ahead with delivering Excel on the server as part of this project' (8-May)

      3. Excel has been delivered onto the server - Delivered 13-May

      4. That's Excel checked and exporting OK from the Meterology server (DW) Completed 13-May