Background 

With the introduction of new ERP (Enterprise Resource Planning) applications imminent, three separate Police Forces required data from legacy applications to be migrated from legacy applications to the new ERP applications. The vast majority of data was to be moved from legacy applications via existing data migration routines.

Some of the legacy data, the shift patterns, was not suitable for data-data migration due to a lack of equivalence in this area between the legacy applications and one of the ERP applications, CARM (Computer Aided Resource Management software). Originally this unsuitable data was to be keyed into CARM manually by experienced HR users. This was estimated to require hundreds of hours of effort over an 11 week period.

Testing Performance suggested that there may be a better approach and developed the solution from concept through planning to delivery.

Challenges

There were estimated to be upwards of 3000 shift patterns with many consisting of five weeks or more. Some rules needed to be implemented depending on the timing and duration of some individual shifts. Extracted shifts originated from two different legacy applications.

Requirement

Testing Performance were responsible for the planning and implementation of an approach for the migration of staff shift patterns from three legacy systems into CARM.

Early discussion during pre-engagement resulted in agreement to use an automated test tool to develop a bespoke utility to perform the migration. The automated test tool selected was able to interact with the CARM user interface whilst having a scripting language capable of the complex algorithms required to transform and map the legacy data.

Solutions

Testing Performance designed and created a utility that was capable of analysing shift pattern data exported from the legacy systems. The data was then reformatted, mapped and then automatically entered into CARM UI. An automated test tool was used to perform both the data manipulation and the UI automation.

The migration is performed as and when shift pattern data is made available. Due to this iterative approach, duplicate shift patterns are identified by interrogating the UI at the time of creation. In such an event, the shift pattern is marked as duplicate and reported for manual resolution.

The phases for the solution were as follows:

•  Discover / Planning phase where requirements were understood, and the way ahead was agreed.

•  Design / Develop where detail of the deliverables was determined and designed.

•  Test where, as far as possible, the accuracy and performance of the utility was tested.

•  Deliver / Deploy where the utility was deployed on-site and executed, a workshop would feedback and demonstrate assets migrated in order to achieve sign-off.

•  One senior resource to design and develop the utility off-site.

•  One senior resource to ensure the utility’s on-site deployment and perform minor modifications and updates to accommodate the CARM UI and any tweaks required to the entry workflow, execution on the customer’s first batches of legacy data.

•  One junior resource to perform migration of the remaining batches of shift patterns as and when they become available.

Testing Performance reviewed documentation and interviewed key personal to understand requirements. This allowed for the following Design and Build phases to be defined with a high-level view of requirements.

Results

• Huge amounts of data and information were processed to form the basis of Performance Testing Requirements, Approach and Scope. The Volumetric Workload model was fully documented and easily maintainable, accounting for current workload volumes and for observing developing trends. This analysis and planning underpinned the performance testing for the transformation project allowing the customer to confidently predict expected performance in production.

The challenge of regular weekly releases into Production was met often exceeding target with multiple weekly releases. As a result:

• There is no-longer a back-log of features waiting to be released.
• The programme is still releasing weekly and at the same time ensuring existing functionality in live has not regressed.
• Release Managers have created the ability to release multiple features together in order to meet the key programme milestones.
• Our Release Managers have cultivated a culture of continuous improvement, they are using forums to drive for more improvements, for example; containerisation and automation of smoke tests. 

Outcome

Due to the off-site preparations, it was possible to update the utility to interact with the CARM UI, enter and validate a selection of shift patterns by the end of first day of the on-site activity.

This example demonstrates:

•  Working with a customer, providing consultancy that genuinely results in a better experience for the customer, saving time and money while at the same time increasing quality.

•  Testing Performance’s ability to take a customer on a journey, taking a concept and working with the customer through to successful implementation of a solution.

•  The ability to supply and deploy appropriately skilled personnel at each stage of the overall delivery process.

•  Flexibility to provide personnel as the project demands.

Return to Public Sector Case Studies