16
1 Project Selection Is there a Customer Impact? Is data available or Easy to Generate? Do you know the Business Objective? Can the project be done in 1-2 Months? Is the Sponsor willing to Provide Resources? Is the project translatable to other Customers/Processes? Is there a benefit to Stakeholders? Is the project scope within control of the Project Team? Is there a readily available Measurement System or Process in Place? No s Yes Yes NA Yes No Yes Yes Yes

Reduce Manual Efforts for API

  • Upload
    dkriray

  • View
    233

  • Download
    1

Embed Size (px)

DESCRIPTION

API

Citation preview

1

Project Selection

Is there a Customer Impact?

Is data available or Easy to Generate?

Do you know the Business Objective?

Can the project be done in 1-2 Months?

Is the Sponsor willing to Provide Resources?

Is the project translatable to other Customers/Processes?

Is there a benefit to Stakeholders?

Is the project scope within control of the Project Team?

Is there a readily available Measurement System or Process in Place?

No

s

Yes

Yes

NA

Yes

No

Yes

Yes

Yes

2

Identifying Project CTQs - VoC

Customer (the user of process or

service or product)Sample Comments (VOC) (CTQs) Critical To Quality Parameter

Internal Customer- Akhilesh Saxena

To test online modules for LBG (Lloyds Banking Group) during unit testing requires reduction of manual efforts, manual errors and time taken. How can we reduce manual efforts, errors and time taken ?

Manual Efforts Manual errorsTime taken

3

CharterIn Scope

Specific Goal Statement

Out of Scope

Business Case (Including High Level Benefit Analysis)

Reduce manual effort and time by 3.4 % for testing of Online modules.

Specific Problem Statement

Reduce testing effort for Online modules, which are on an average tested 90-110 times a year, from 80 hours to 76.5 hours per module.

Since 5 year, Core Banking System(CBS) team is doing the code development for Lloyds Banking Group (LBG), which is further unit tested. CBS consist of many ONLINE modules which are tested through Application programming Interface (API).So for testing we need to generate the streams (Compile-link, Supur etc), which are done manually and it takes 5 to 7 minutes per stream, this activity is performed by each team member who is working on the API.The automation of stream generation will not only make the manual effort of testing more efficient but also improve the overall quality of testing.Benefits:Reduce manual errorsReduce manual effortsQuick completion of testing

On-line modulesaccount creation module(NEW01)Closure modules(CLO01, CLO04) etc

Batch ModulesSequential passDrip feed Module

5

Macro Map

Online module testing Compile link

Supur stream creation

Hit the API Start Online stream

Transaction Reporting Process is driven by the BRD issued by XYZ Group

Out of Scope

In Scope

6

COPIS for AS-IS Process

SupplierInputProcessOutput

C

Customer

O P I S

Out of Scope

In Scope

TCS TCS

Online stream generator tool

API testing complete in less

time and less effort

Start

Stop

Select the module to be tested

Use stream in testing

Generate the stream Compile-link/Supur/start online

TCS INTERNAL-7-

Method

People

Measurement

Mother Nature

As-Is Root Cause Analysis – Fish Bone Diagram

Large number of associates test online

modules

Environment Issues

Manually create streams

Manual efforts,errors and time involved in API testing is HIGH ?

Virtual machine Connectivity Issues

Manual Effort,errors

and time involved in

testing of API modules.

TCS INTERNAL-8-

Value Stream Map As-Is

Process Step 1 2 3 4 5 6 Total Time Total%0 420 300 120 420 2 3300 100.00%

Avg wait time between current and next Step(Secs) 0 0 2 0 0 0 600 10.00%Avg Total Time (Process+ Wait) (Secs) 0 420 302 120 420 2 3900 100.00%Value Added Time(Secs) 0 5 0 5 0.10%Value Enabling Time(Secs) 0 0 27 0 27 0.70%Non Value Added Time(Secs) 1800 900 525 600 3868 99.20%Wastes VE and NVA Breakup VE & NVA 99.90%Transportation(Material) 0Motion(Personnel) 0Inventory 0Waiting(Delay Set-up) 1 2 1 1 5Over Processing 0Over Production 0Defects(Int /Ext Failure) 0

AS – IS ProcessDetailed Processes

Select the module want to testManually create the compile

Manually create or run the Start onlineHit the API

Avg Processing Time of the Step 1 modules(Sec)Selec

Manually generate the Supur stream

TCS INTERNAL-9-

   HIGH MEDIUM LOW

INCONTROL

•Cross checking i•Manual effort and time involved in iterating through the DI History section.•Status reporting method.

• Large size of table used to retrieve data.

• Local Storage Space availability issues.

OUT OF CONTROL

• DI System Connectivity Issue.• DI Application fault.• Server and environment constraints.• Large Number work flow steps involved in DI cycle.

• Network speed• Large number of users logged in DI System.

As-Is Control Impact Matrix

IMPACT

CONTROL

Causes encircled were taken up for solution in each of 4 process steps (VSM) to reduce waiting time

TCS INTERNAL-10-

Brainstorming – Alternative Solutions

Reducing manual efforts, errors and quick completion of online modules testing

Solution

Process step 2,3 and 4 : Manually creates streams

The brainstormed possible solutions are:

Solution1: We need to reduce the effort and time in stream generation. User should provide the necessary inputs and stream should be generated in seconds.

Solution2: System up-gradationAlternate solution describes the up-gradation of System increasing CPU capability and decrease processing time of requests. This solution is cost and process intensive.

TCS INTERNAL-11-

The top solutions are highlighted in Turquoise

   

Processing time

Effectiveness Least Intrusion

Budget Complexity Total

   5 5 5 5 4  

1 Automation of streams 5 5 5 5 4 116

2 System up-gradation2 2 3 1 3 52

Extracting Specific columns for which system is performing full table scan on database

Solution Prioritization Matrix – Alternative SolutionsSolution

TCS INTERNAL-12-

To Be Process MapSolution

Start

Select the module to be tested

Generate the streams using API tool

Perform Testing

Stop

TCS INTERNAL-13-

Solution Cost benefit analysis

Methodology Used To Calculate Primary Savings in hours

1. Time saved in hours in testing/module = 3.5

2. Number of API built = 45

3. Number of API modules = 60

4. Total modules = 110

5. Manual effort saved = 3.5x 110 = 385 hours

6. Total effort saved / module

in P.D over a span of 10 days = 0.4375

1. Billing rate / day = 110 pounds

2. Total money saved in pound/ module = 48.125

3. Annual Saving in pound = 5053.125

4. Annual Saving in Dollars = 7933.40

Step 1Step 1 Summary Of Economic Benefits

Primary Savings : 7933.40 USD (Annually)

Cost incurred : 1760 USD (One time cost)

Step 2Step 2

1. Billing rate is $21.58/hour

2. Number of Online modules and New APIs.

Key Assumptions Utilised

1. Total Savings in Dollars = 7933.40

Primary Savings

TCS INTERNAL-14-

Solution Cost benefit analysis

Step 3Step 3

Step 5Step 5 Time Period 12 months

Annual Gross Benefits : 7933.40 USDCost Incurred : 690 USD

Annual Net Benefits : 7243.4 USD

Annual Gross Benefits : 7933.40 USDCost Incurred : 690 USD

Annual Net Benefits : 7243.4 USD

1. Effort taken to execute PI = 32 hours

2. Total billing for 1 hours is 21.58 dollars.

3. Cost incurred = 21.58 * 32 = $690

Cost Incurred

Step 4Step 4

Savings in using tool $7933.40 – $690 = $7243.4

Total cost savings

TCS INTERNAL-15-

To-Be Process Value Stream MapSolution

As-Is Process : Effort (Processing Time) = 3300 Seconds

To-Be Process : Effort (Response time)= 73 seconds

Process Step 1 2 3 4 Total Time Total%Avg Processing Time of the Step for 10 modules(Sec) 5 60 3 5 73 100.00%Avg wait time between current and next Step(Secs) 0 0 0 0 0 0.00%Avg Total Time (Process+ Wait) (Secs) 5 60 3 5 73 100.00%Value Added Time(Secs) 0 0 3 0 3 0.05%Value Enabling Time(Secs) 0 5 0 0 5 0.07%Non Value Added Time(Secs) 0 5 0 0 5 0.07%Wastes VE and NVA Breakup VE & NVA 0.14%Transportation(Material) 0Motion(Personnel) 0Inventory 0Waiting(Delay Set-up) 1 1 0 1 3Over Processing 0Over Production 0Defects(Int /Ext Failure) 0

AS – IS ProcessDetailed Processes

Copy DI Comments From DI System for each Module by QueryMaking List of selected DI'sCopying Comments for Selected DI”sCopy sheet to EOBR

TCS INTERNAL-16-

Take it forward Before Vs After

There is total savings of hours per annum by implementing this improvement

There is total savings of hours per annum by implementing this improvement

Sr No Proposal Time taken to complete of API modules in hours ResultsBefore After

1 1 3900 73 98% improvement

Before After0

500

1000

1500

2000

2500

3000

3500

4000

• Requires lot of manual effort which lead to errors. • Testing takes more time.

• After using this tool, manual effort and errors are reduced. • Testing takes less time.

AfterBefore

TCS INTERNAL-17-

Techniques Used : Value Stream Mapping, Fish Bone

Reduce processing time involved in opening of loan proposalAs-Is

SolutionTake it forward

Technique Used : Charter, CTQ Analysis, Macro Map, COPIS, VSM

Focus

Key cause identified was:

• Manual efforts ,errors and time to complete testing of oline modules.

Since 5 year, Core Banking System(CBS) team is doing the code development for Lloyds Banking Group (LBG), which is further unit tested. CBS consist of many ONLINE modules which are tested through Application programming Interface (API).

So for testing we need to generate the streams (Compile-link, Supur etc), which are done manually and it takes 5 to 7 minutes per stream, this activity is performed by each team member who is working on the API.

The automation of stream generation will not only make the manual effort of testing more efficient but also improve the overall quality of testing.

Benefits:

Reduce manual errors

Reduce manual efforts

Quick completion of testing

Goal: educe manual effort and time by 3.4 % for testing of Online modules.