• Like
Web Page Load Cycle Time Six Sigma Case Study
Upcoming SlideShare
Loading in...5
×

Web Page Load Cycle Time Six Sigma Case Study

  • 162 views
Uploaded on

Six Sigma Project Case Study Overview by Master Black Belt Steven Bonacorsi, International Standard for Lean Six Sigma (ISLSS). General Electic ACFC "At the Customer, for the Customer"

Six Sigma Project Case Study Overview by Master Black Belt Steven Bonacorsi, International Standard for Lean Six Sigma (ISLSS). General Electic ACFC "At the Customer, for the Customer"

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
162
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Six Sigma in Action: Web Application PerformanceMaster Black Belt: Steven Bonacorsi
  • 2. Six Sigma in Action TEDS Systems PerformanceCustomer Profile - 31,000 active Training & EmployeeDevelopment System (TEDS) users – and potentially every GEMedical Systems employee, contractor, and vendor. Process Capability Analysis for Module 2nd C Process Capability – Before USLBusiness Problem & Impact USL Process Data 4.00000 ST LTAverage web page load time was 5.8 seconds. GEMS Learning Target LSL * * Mean 4.70867Solutions General Manager Pete McCabe requested a 4 sec. Sample N StDev (ST) 0.607092 21average time based on general rules from other web applications, StDev (LT) 0.624410such as the GEMS homepage. Potential (ST) Capability Cp *Measure & Analyze CPU CPL Cpk -0.39 -0.39 *Data Collection: Web page load time was measured. The existing Cpm * 3 4 5 6 7process sigma was less than 1. Overall (LT) Capability Observed Performance Expected ST Performance Expected LT Performance Pp * PPM < LSL * PPM < LSL * PPM < LSL *Root Cause: The JRun server was improperly configured not to PPU PPL -0.38 * PPM > USL PPM Total 904761.90 904761.90 PPM > USL PPM Total 878458.02 878458.02 PPM > USL PPM Total 871799.38 871799.38compile data, which slowed down many processes. Ppk -0.38Improve & Control Process Capability Analysis for Module 2nd CRemoved the Djava.compiler=none setting from JRun server, Process Capability – After USLtaking it out of debug mode and allowing it to run more USL Process Data 4.00000 ST Target * LTefficiently. Load times decreased 3.1 seconds and the sigma LSL * Mean 1.69512increased to greater than 6. To control the process, the TEDS Sample N 52 StDev (ST) 0.276561server was placed under the Topaz monitoring scheme, which StDev (LT) 0.325387sends a text message alert to a pager when the page load Potential (ST) Capabilitytime drops below 4 seconds. Cp CPU 2.78 * CPL *Results/Benefits Cpk Cpm 2.78 * 1.0 1.5 2.0 2.5 3.0 3.5 4.0By decreasing the web page load time of the average TEDS page Overall (LT) Capability Observed Performance Expected ST Performance Expected LT Performanceby 3.1 seconds (making it 47% faster), this frees up over $34K in Pp PPU 2.36 * PPM < LSL PPM > USL 0.00 * PPM < LSL PPM > USL 0.00 * PPM < LSL PPM > USL 0.00 *productivity cost savings per year. Additionally, all page load times PPL Ppk 2.36 * PPM Total 0.00 PPM Total 0.00 PPM Total 0.00average less than 4 seconds, satisfying the main customer CTQ. A savings of over $34,000 per year.