Part I. Construct a control chart based on our red bead exercise and analyze your result.
WORKER |
WEEK1 |
WEEK2 |
WEEK3 |
WEEK4 |
Total: |
Alan |
11 |
6 |
10 |
12 |
39 |
Mingda |
8 |
12 |
13 |
8 |
41 |
Greg |
6 |
14 |
13 |
11 |
44 |
Charlie |
14 |
6 |
9 |
9 |
38 |
Total: |
39 |
38 |
45 |
40 |
162 |
|
|
|
|
|
|
|
Recorder: |
Andrew |
|
Inspector: |
Danielle |
Process Analysis
Select a process that has a very short cycle time to study in real time.
- Design a plan of action to monitor the process.
- Visit the site to observe the process.
- Create a process flow chart that describes the process. Indicate on the flow chart those points where problems might arise and describe the potential problems.
- Create an Ishikawa Diagram for one of the potential problems in your process. Decide on avariables measurement that will help you better understand the problem.
- List operational definitions for all aspects of the data collection process, including start and end points of the process.
- Collect preliminary data (30 or so observations) according to your plan.
- Create a pilot control chart with these data (use n=3).
- Discuss your first visit and your observations with your team. Modify your plan for monitoring this process in the future and revise your operational definitions based on what you learned during your first visit to observe the process.
- As you monitored the process, what issues or problems needed clarification? How were these issues resolved? Also, list any unresolved issues or problems regarding your data collection.
- Review your Flow Chart and Ishikawa Diagram and make any additions or changes that you deem appropriate.
- Schedule collection of data for the final control chart (90 or more observations).
Submit a professionally written report (suitable for a Board of Directors) that includes:
(1) a cover letter to the board that states what you studied and what your conclusions are.
(2) An appendix with Table of Contents that includes the problems you overcame in your study, a final flow chart, Ishikawa diagram, control chart, your method of analysis, operational definitions and other deliberations that were part of your study. Also, in the appendix indicate what your next steps would be, if you were to continue to analyze this process
Tips on Writing A Professional Report
The Cover Letter:
· The letter to the board should contain the answer to the question you were asked to address.
· The letter should not contain details on methodology.
· If the letter is sent in electronic format, it should be submitted in a format that would also look professional if printed out on 8 ½” x 11” paper (in USA).
· The letter should be presented in portrait style.
· The letter should be short. No more than a few paragraphs on one sheet of paper.
· Use a twelve-point font (Times New Roman, or Helvetica, or comparable).
· Do not use different fonts, italics, underscores, or bold print anywhere in the letter.
· Company logos are trademarked. Do not use company logos without permission from the company.
· Don’t include filler-phrases, helper phrases, pap, jargon, or information not asked for.
· Check your letter for spelling and grammar.
Attachments to the Letter:
· Any details, graphs, tables, or description of methodology should be included as attachments in an Appendix to the letter.
· The appendix should have a Table of Contents.
· Attachments should follow a logical sequence.
· The entire report should be printable on 8 ½” x 11” paper (in USA).
· All pages should have a comfortable one inch margin on all sides.
· Pages in the appendix should be numbered.
· Each table and graph should be able to stand on its own, without dependence on any other table or text not found within the table or graph.
· Each table and graph should fit comfortably on one page.
· If a table or graph must be turned landscape style, make sure the top of the table is to the left in the document.
· Never include a ‘naked’ spreadsheet of data. Convert any data you wish to include into a table that is labeled fully and pleasant to view.
· Never include a table with one column or one row only. Convert it to multiple columns or rows. For example, if you have 120 data points you wish to share, don’t send a spreadsheet with one column and 120 lines. Create a compact table. For example, breakup the data by year. Have twelve columns (one for each month) and ten rows (one for each year), or the other way around, ten columns and twelve rows. Be sure to label the table. Every column and every row should have a title or name.
· Tables should have a purpose, be clear, easy to read, and have
o Comfortable margins around all sides (at least one inch).
o A title that gives sufficient detail that the reader knows what he’s looking at
o Headings on each column and row.
o No more than four digits in a column; less, if possible without loosing meaningful distinctions.
o No number showing more digits than statistically significant
o Denominations on all axes.
o Only content actually used in the report.
o A professional look.
· Graphs and diagrams should be included only when they add value to understanding the content. They should be clear, easy to interpret, and have
o Comfortable margins around all sides (at least one inch).
o A title that gives sufficient detail that the reader knows what he’s looking at.
o Headings on all axes.
o Denominations of all content.
o Only content actually used in the report.
o A professional look.
· When sending a report by e-mail Focus on content and professional appearance rather than trying to jazz up the report with color photos, cute references, or logos.
§ Always include all of your pages in no more than one attachment.
§ Use print setup (in Word) to test and ensure that pages print out as they should.
§ Make sure no blank pages will print out after the report, or between pages in the report.
§ Always assume the report will be printed out on a non-color printer. So, don’t get fancy with the colors, if they can’t be distinguished in a black-and-white printout.
Normal
0
false
false
false
FR
JA
X-NONE
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:””;
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:”Cambria”,serif;
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-ansi-language:FR;
mso-fareast-language:FR;}