Your SlideShare is downloading. ×
0
Operating System Six Sigma Case Study
Operating System Six Sigma Case Study
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Operating System Six Sigma Case Study

89

Published on

Lean Six Sigma Group Free Project Case Study Overviews http://www.linkedin.com/groups/Lean-Six-Sigma-37987 …

Lean Six Sigma Group Free Project Case Study Overviews http://www.linkedin.com/groups/Lean-Six-Sigma-37987
Sponsored by the International Standard for Lean Six Sigma, e-Zsigma http://www.e-zsigma.com, IQPC, and PEX Network.

Please contact Lean Six Sigma Master Black Belt, Steven Bonacorsi, Owner of the Lean Six Sigma Group to have your project case studies to be added to the Lean Six Sigma Group Library. Steve Bonacorsi sbonacorsi@comcast.net

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
89
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
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. Windows 2000 Scheduling GE Aircraft Engines AccountProject Leader: Michael Lisenby Project CoordinatorStart Date: May 1, 2002 Master Black Belt: Steven Bonacorsi
  • 2. Six Sigma in Action W2K Schedule AccuracyCustomer Profile – 18,000 seat Aircraft Engines Business. Observations/Conclusion The major types of problems (exceptions) with theBusiness Problem & Impact data submitted is Bi Modal by Type as some fieldsThe initial process for upgrading users to Windows 2000 we never completed by anyone.invited missed appointments, erroneously handled user 68.1% of problems are due to Windows 2000notifications, faulty user/requestor information, and duplicated already existing on users machines, PCs that havework efforts. It did not lend itself to a means of manageable been replaced, and Incompatible applications.scheduling for the customer, nor any financial benefit to ITS. 95% Confident that each form will have an average of 8 defective fields per unit and is statisticallyMeasure & Analyze significant with a P-Value of 0.000Data Collection: Degree of completion of work requests were 95% Confident that each form will have an averagemeasured. The existing process sigma was 0.53. of 2 successful fields and is statistically significantRoot Causes: Operational definitions and attention to data with a P-Value of 0.000requirements were identified as root causes.Improve & Control 5 ImprovedThe data collection method was fully digitized, and the C.E. Operationalwas instrumental in improved scheduling by contacting (more definitionsresponsive) users directly. resulted in Success 98% successResults/Benefits Defect rate forAfter the 3 month project, Labor efficiency contributed $56,800 digitized dataand increased revenue contributed $30,720 to an overall collection. 295$87.5K annual benefit. A savings of US$87.5K in 2002!

×