Wales & West Utilities – CR Impact Assessment

for CR – 10993 Code update of Key forms in

connections process
Response by

Enzen Global Limited

Submitted on July 2015

 Enzen Global Limited

11, Blythe Valley Innovation Centre • Central Boulevard • Blythe Valley Park
Solihull B90 8AJ • United Kingdom
Phone +44 121 506 9000 • Fax +44 121 506 9001
http://enzenglobal.co.uk

We are shaped by our thoughts - we become what we think Page 1 of 7

Circulation List

Name Role Contact Details

Ankit Tyagi IA Author(s) Ankit.tyagi@wwutilities.co.uk

Tamoghna Dasgupta IA Reviewer(s) Tamoghna.dasgupta@wwutilities.co.uk

Antony Guy CR Owner(s) Antony.guy@wwutilities.co.uk

Antony Guy UAT Owner(s) Antony.guy@wwutilities.co.uk

Nicki Horlock CR Manager Nicki.Horlock@wwutilities.co.uk

Version History

Version Version Date Changes Done Changes Done by

V0.1 23/06/2015 Initial version Vijay

Change request document

We are shaped by our thoughts - we become what we think Page 2 of 7

 Table of Contents
SOLUTION DETAILS: 4
DEPENDENCIES & ASSUMPTIONS 4
TESTING: 5
CHECKLIST 5
Efforts & Commercials 6

We are shaped by our thoughts - we become what we think Page 3 of 7

Solution Details:

Business requirement: WWU’s Adobe forms contain windows-centric code that takes data from CRM,
transfers it to the form and packages it as a pdf document for distribution to the customer (email). Unless the
customer is using a windows based machine they will not be able to view the CRM data that is contained
within the form. This issue is most common when viewing forms via apple devices.

Objective of Development: Within Business Services, nearly all of our key documents are emailed. On a
daily basis the business have to field a number of calls from the public explaining why they are unable to view
their documents. Being able to introduce this code change will reduce telephone traffic. Moreover this will
flexibility to the users in opening the forms we are sending to customers.

Benefits of implementing the CR:

1. After implementing the changes in the form , the customers will be able to open those forms in their
Machine running on iOS (iPhone/iPad).
2. Currently customers can open their documents in window based machine and android machines.
This will give the flexibility to customers and in turn will reduce the time spent on telephone calls.

Technical Details:
1. We have to implement the new logic for each field we are using in our adobe forms.
2. We have to download the XML schema’s for each form and then needs to change in Adobe life cycle
designer.
3. Each field need to be test with Android, window and IOS machines.
4. After implementing the change, we have to upload the XML schema back in the systems i.e. CRM DEV,
QA and PROD.

We are shaped by our thoughts - we become what we think Page 4 of 7

Dependencies & Assumptions
 As per the CR document, we are considering the one dozen forms which needs to be changed.

 Business has to confirm on the form details.

Testing:
System Testing will be conducted by Enzen team and will be in line with the WWU Testing Strategy
Key activities include

1) Define & develop Test Strategy, Test Plan and Test Scripts for System Testing
2) Execution of end-to-end testing
3) Maintaining the testing artefacts in Original Soft Qualify
4) Defects Management process as per WWU Testing Strategy
5) QA Release Management process as per WWU Testing Strategy

Key deliverables include

1) Signed-off System Tested system available for UAT

2) Test Summary Report with Test runs, passed/failed scenarios, outstanding defects, etc.
User Acceptance Testing will be carried out upon completion of System testing, business will undertake end-
to-end testing to ensure that the functionality is working as expected. In the UAT phase all relevant
stakeholders from business will be involved to do an end to end testing of all possible scenarios.
Key activities include

1) WWU business to define UAT Plan and Test Scripts for UAT
2) WWU Business to execute the UAT scripts with support from Enzen project and business engagement team
3) Defects Management Process as per WWU standards

We are shaped by our thoughts - we become what we think Page 5 of 7

4) Release Management Process as per WWU Standards
Key deliverables include

1) Signed off UAT document covering all business testing scenarios for future reference & Go-Live Support

Checklist
This section provides a high-level check list to understand the impacts on various systems
Impacted?
Checklist Item Relevant details/comments
(Yes/No/NA)
SAP R/3 - Impacts

User Interface and Screen changes No

Master data / tables update No

Work order types impacted No

PM Act types and Std Text Keys impacted No

New validations No

Changes to existing validations No

Impact on Custom reports No

SAP BW – Impacts

BW reports changes No

BW daily load / delta refresh changes No

BW extractor changes No

BW structures impacted No

webMethods – Impacts

New interfaces No

Changes to existing interfaces No

Table changes No

New validations No

Changes to existing validations No

Other Critical Systems – Impacts

e-Timesheet No

ESRI No

Ventyx No

Insight No

Add others, if any Adobe Forms (CRM)

Basis - Impacts

We are shaped by our thoughts - we become what we think Page 6 of 7

 New role creation No

Existing role modification required No

New Transaction required No

Efforts & Commercials

IA Activity Effort in Days
Impact Assessment 5
Analysis and Design 7
Build and Unit Testing 20
System Integration Testing 5
UAT & Post Implementation support 6
Total Cost 43

We are shaped by our thoughts - we become what we think Page 7 of 7