The specification of the non-functional requirements (‘NFRs’) expected from the Xoserve solution; The execution of performance testing on the Xoserve solution; Further analysis around the volume of Class 3 meter reads that can be expected from the industry; and Further testing of performance across Xoserve’s dress rehearsals, especially the assumptions around the volume of industry files that will require in the ‘catch-up’ effective day period. These elements have been shared across the Project Nexus industry forums, but a summary of the results and any outstanding risk areas is presented below: Area Key outcomes and results Residual questions and issues Limited engagement from The External Industry Non-functional industry participants Business Requirement requirements regarding likely transaction Principles Document (‘BRD’) (‘NFRs’) volumes. was agreed and approved by the industry during 2011 and 2012. Principles were taken into an Xoserve internally developed NFR BRD, which was approved in 2012. Industry BRD for NFR was discussed at PNUNC (Project Nexus UNC Group) and latest version of Principles document baselined at 5 Mar 13. The NFRs were subsequently validated at PNUNC during 2015 and 2016. The scope of IDR1 was Overall timeline not met Implementation communicated in advance. and required optimisation. Dress Rehearsal Some non-critical elements As a result, further (‘IDR’) 1 were de-scoped. performance IDR1 updates were improvements have been communicated via made and the number of Transition Progress Group days allowed for the transition increased Items removed from scope fully tested in IDR2 and IDR3. Not full e.g. With the exception of meter Performance test, and transition activity reads, proved performance executed over July not covered, but full under stressed conditions. through to December scope tested as part of Performance test updates 2016 IDR2 and IDR3. have been communicated via Decision taken by PNSG Transition Progress Group. that the demonstrated 32 million proven against level of likely meter read requirement for 42 million performance is class 3 meter reads on a daily acceptable. basis.
The specification of the non-functional requirements (‘NFRs’) expected from the Xoserve solution; The execution of performance testing on the Xoserve solution; Further analysis around the volume of Class 3 meter reads that can be expected from the industry; and Further testing of performance across Xoserve’s dress rehearsals, especially the assumptions around the volume of industry files that will require ‘catch-up’ in the day period. These elements have been shared across the Project Nexus industry forums, but a summary of the results and any outstanding risk areas is presented below: Area Key outcomes and results Residual questions and issues Non-functional requirements (‘NFRs’) The External Industry Business Requirement Principles Document (‘BRD’) was agreed and approved by the industry during 2011 and 2012. Principles were taken into an Xoserve internally developed NFR BRD, which was approved in 2012. Industry BRD for NFR was discussed at PNUNC (Project Nexus UNC Group) and latest version of Principles document baselined at 5 Mar 13. The NFRs were subsequently validated at PNUNC during 2015 and 2016. Limited engagement from industry participants regarding likely transaction volumes. Implementation Dress Rehearsal (‘IDR’) 1 The scope of IDR1 was communicated in advance. Some non-critical elements were de-scoped. IDR1 updates were communicated via Transition Progress Group Overall timeline not met and required optimisation. As a result, further performance improvements have been made and the number of days allowed for the transition increased Items removed from scope fully tested in IDR2 and IDR3. Performance test, executed over July through to December 2016 With the exception of meter reads, proved performance under stressed conditions. Performance test updates have been communicated via Transition Progress Group. 32 million proven against requirement for 42 million class 3 meter reads on a daily basis. Not full e.g. and transition activity not covered, but full scope tested as part of IDR2 and IDR3. Decision taken by PNSG that the demonstrated level of likely meter read performance is acceptable. effective