Progress Report

Report Date

March 2015

The overall progress with this project has been hampered progress this month due to a combination of technical issues, absences and holidays

Achievements

• Whilst the outline workflow process regarding the creation of a work request through to allocation to a specific tradesman has been completed, it has only been achieved using established work around.  This however, will require to be corrected prior to any general demonstrations are provided and user acceptance testing 
• Whilst it has been possible to process and update work orders via the mobile application, it has been noted that there is the requirement to replace the building code and work requested id with their narrative equivalents. Whilst this will not delay any testing, this will require to be resolved before full user acceptance testing. 
• - currently there are some errors that can be by-passed, however these will require fixed
• Admin User Guide has been completed
• JIRAs have been raised and classified to keep track of progress
• With regards the monthly communications bulletins
  • The February issue was distributed via the established mailing list 
  • The first draft of the March issue has been prepared and circulated within the project team to review

Issues

• A number of issues have been formally raised as part of the initial proof of concept testing. These are currently being worked through with both Mass and Archibus
• As part of the proof of concept, it has been noted that there will be the requirement to enable additional information to be captured on the mobile application in relation to; internal stores, gas related work orders and PAT testing. Potential solutions to these items are currently being explored with Mass
• An unexpected issue has subsequently occurred whereby it is not possible to assign a work order to a tradesman and this is currently being investigated by Mass. 
• Due to the above issues,
  • it has not been possible to provide a full demonstration of the On Demand process to the project team
  • consultation with the Estates business partners has been delayed
  • a weekly meeting is now being organised with Mass to review outstanding issues
  • there has been the requirement to re-plan the project based on the understanding that the proof of concept can be completed by the end of April.  However, the plan has still to be agreed with both the project team and project sponsor
• It has not been possible to progress with the fault reporting classifications due to lack of resource within the project team

Next Steps

• Continue to work through the remaining outstanding issues with Mass with a view to completing the proof of concept
• Customers User Guide will be started in April
• Requirement to confirm no impact on the application after the scheduled upgrade to Archibus 21.3 has been completed 
• To refine workflow process, if required, following feedback from project team
• Continue definition of the two-tier fault reporting hierarchy
• Commence consultation with the Estates department business partners regarding fault reporting
• Put through more scenarios in the system, including Furniture and Landscaping scenarios, and test mobile device integration
• The trades representatives will be taking part in the acceptance testing.
• The trades representatives will be logging results and issues

Due to the on-going issues and the unexpected delays, the project has been assigned a RAG status of RED whilst discussions and investigations are on-going with Mass to resolve the reported issues

Milestones

 Milestones required refined and approved with the Project Sponsor once a Demo of the system is available to show