Completion Report

Project Summary:

Deliverables

The deliverables have been met by the ERM upgrade

• Upgraded the Enterprise Reagent Manager (ERM) Software to 7.0.2
• Provided  upgraded environments for Test and Live

Background Information

Enterprise Reagent Manager (ERM) is a chemical management and eOrdering tool currently integrated with SciQuest using Select Site.

ERM contributes to the efficient recording and reporting of chemical storage and usage, across the University where such reporting is required under government health and safety and terrorism legislation (Chemical Weapons (Notification) Regulations, and the Anti-Terrorism, Crime and Security Act 2001). 

Scope

ERM Version 7.0.2 includes improved functionality that resolves many of the user identified failings of the current version.  In particular:

• It removes the client/server system administration application which is becoming a support burden, delivering the required functionality as part of the browser based application.
• It makes the application available on Apple Macs, thus removing a barrier to adoption.

Objectives

• To achieve a supported ERM application by upgrading the Enterprise Reagent Manager (ERM) software to version 7.0.2
  • ERM Support runs out at the end of 2013
  • To ensure, as a minimum, that the existing functionality and processes are delivered.

Analysis of Resource Usage:

Staff Usage Estimate: 77 days

Staff Usage Actual: 50 days

Staff Usage Variance: -35%

Other Resource Estimate: 0 days

Other Resource Actual: 0 days

Other Resource Variance: 0%

Explanation for variance:

Changes to the project can be found :

Project Issues and Changes Log

This project has run very smoothly and to the correct timescales. This project has successfully achieved the best case estimate.

Estimation Budget

• The project has run very smoothly and that has resulted in us using less than the original approved budget.
  • The reduction from 77 days to 63 can be found in Item 6
  •  
  • Once the rest of the project had been completed with no new issues becoming evident, the number of days required resulted in 50 days being used by the IS Apps Project team
  • The reduction from 63 days to 50 can be found in Item 7
  • The Closure and DSOR have been submitted for WIS 21-Feb-14.

Milestone Impact

In October 13 the project required re-planned when SciQuest identified that they could not spend any time until January 14.

The project was the replanned for January agreeing to run the Chemistry and Procurement Testing concurrently, there by allowing the whole process elapsed time to be reduced.

SciQuest also had to agree to support the current ERM Version until ERM 7.0.2 was delivered (even although the previous version support had expired).

Different working hours were accommodated and agreed with Dev Tech and SciQuest to enable the project to go ahead without VPM access - this project used GoToMeeting (check with Ewan)

 The project budget was also able to be reduced again as it proceeded to run through with few  issues.

Key Learning Points:

When another ERM upgrade is required, there are a number of points to consider in the Brief and Planning steps:

• Before Test is refreshed from Live there a number of items to allow Procurement to schedule in Planning
  • Test Ease accounts will be required to be set up.
  • This can be done by Procurement, however when planning
    • A longer elapsed time should be scheduled in for this
    • This will enable more Chemistry customers to take part in the ERM testing (where a larger migration process is required)
    • This will have no effect on the project budget 
  • This should be scheduled before the actual the refresh of TEST from LIVE
    • This will enable more realistic and thorough testing.

When the TEST Plan is being written

• ensure that Chemistry AND Procurement know who is responsible for testing the particular item and following though the whole process.
  • An example was related to returning orders to ERM.
  • Add the team responsible for signoff of the TEST in the plan

For consideration in any future upgrades

• Negotiate with SciQuest to allow UOE to perform the LIVE implementation based on what was completed jointly in TEST  (a Technical point suggested by SciQuest, which Dev Tech are happy to complete as long as the Live database has been copied to Test at the start of the project).
• With this release there is now an option of running the application outwith the EDLAN network. (- Technical point)
  • There is no current requirement to access outwith EDLAN

Outstanding issues:

None identified for this project.