---
company: Arçelik Dishwasher Factory
project_name: |
  Designment and Application of Inspection \
  System for Mechanics Department

date: 10 December 2019

# team_no: 17
team_members:  
- Kudret Arman 
- Alper Ayhan
- A. Burcu ÇolakK
- Ali Hüseyin Demirci
- Fatih Ergen
- Dilek Ölez

industrial_advisors:
- N. Tanzer Tunçalp, Arçelik Dishwasher Factory, 
- Automatisation and Information Systems Manager

academic_advisors:
- Asst. Prof. M. Murat Fadıloğlu, Bilkent University
- Department of Industrial Engineering

abstract: |
  In the Arçelik Dishwasher Factory, lack of control system to calculate the performance of processes and the quality of products affects the productivity process negatively. The aim of this project is to prevent the data loss and to prepare the necessary infrastructure for the quality and improvement workers by designing and implementing a fast and user-friendly control system. The system is developed on Microsoft.NET platform using VisualBasic.NET programming language and Oracle 9.2 database. By the help of this system a sample efficiency improvement study was conducted and the efficiency is improved by 8% in terms of time and 3% in terms of productivity. 
  
keywords: GUI (Graphical User Interface), grid ergonomics, quality and performance improvement, process analysis.

output:
  bookdown::pdf_document2:
    template: IE477_478_latex_template.tex
    keep_tex: no
bibliography: report.bib
---

```{r setup, include=FALSE}
library(magrittr)
library(knitr)
library(pander)
opts_chunk$set(echo = FALSE)
doc.type <- knitr::opts_knit$get('rmarkdown.pandoc.to')
```

# Introduction

Section \@ref(rmarkdown) illustrates how to create tables, figures, refer to them, and cite others' work. Section \@ref(format) describes the report format if you are not using R Markdown.

# R Markdown {#rmarkdown}

This is an R Markdown document. Markdown is a simple formatting syntax for authoring HTML, PDF, and MS Word documents. For more details on using R Markdown, see <http://rmarkdown.rstudio.com>. 

Use RStudio to create R Markdown reports. In RStudioe, when you click the **Knit** button (or press `Ctrl-Shift-K`) a document will be generated that includes both content as well as the output of any embedded R code chunks within the document. You can embed an R code chunk like this:

```{r cars, echo=TRUE}
## cat(doc.type)
summary(cars)
```

## Including Plots

You can also embed plots as in Figure \@ref(fig:pressure), for example:

```{r pressure, echo = TRUE, fig.cap= "Pressure vs. temperature"}
plot(pressure)
```

Note that the `echo = TRUE` parameter was added to the code chunk to print the R code that generated the plot. In general, you will not want the code appear and thus set `echo = FALSE`. You can set it `FALSE` globally in the first chunk of your document.  Table \@ref(tab:presPanderTable) displays the first six lines of data plotted in Figure \@ref(fig:pressure).

```{r pressureTable2}
pressure %>% 
  head() %>% 
  pander(caption="(\\#tab:presPanderTable) The first six records of pressure versus temperature")
```

## Further Reading

Read Xie et al. [-@xie2018r] for more on R Markdown. @wickham2017r will also be useful.

# Report Format  {#format}

The text must be written in ‘Times New Roman’ font using 12 pt and single spaced and justified. The first paragraphs in each section/subsection/... should not be indented. All others should be indented 1 cm. There must be no line blanking between paragraphs.

## Margins

Top and bottom margins must be 3 cm, right and left margins must be 3.75 cm width.
All headings, tables, figures, texts and appendices must be between the spacing limits that are determined by margins, there must no text outside of these limits. ( Please ensure that all tables and figures that you used in the text and appendix are  between the margins.)

## Headings
Headings must be written in 16 pt, bold. The first character of each word must be a capital letter. In the headings of reports written in Turkish, conjunctions like ‘ve’, 'ile' must be written in lowercase. In the headings of reports written in English, auxiliary words like ‘the’, ‘on’, ‘for’ must be written in lowercase. All headings must be enumerated. 

## Subheading
Subheadings must be written in 12 pt, following the heading number. The first character of a subheading must be uppercase, and other characters must be lowercase. There must be no dot after the last character of any headings or subheadings. 

Headings should not be  chained without any remarks in between. When a new section or sub section or sub sub section is created, greet the reader with the purpose of section and give a brief review of its content and the contents of its sub sections.

### Sub sub heading
The same subheading rules apply. A fourth subheading should not be used like 3.2.2.1. If there is a heading, definition etc. that you do not want to enumerate, it must be written in italic and there must be “:” (double dot) after that. *Example:*

 MDB:
 : Main distribution base.

 MDB network:
 : the network that is created by main distribution bases and their connection.


## Bulleting and Indexing 

### Bulleting 

Bulleting should be left-aligned and only the round shape should be used. Manuscripts should start from 1 cm inside. *Example:*

The objectives can be listed in more detail as follows:

* Measuring the performance of molds, operators and press machines where products are produced, in line with the expectations of the enterprise.
  * Measuring the molds in which the products are produced, in line with the expectations of the enterprise.
  * Measuring the molds in which the products are produced, in line with the expectations of the enterprise.

* A system design that will allow the measurement of the quality of all kinds of raw materials, semi-finished products and espacially the materials from the supplier companies that are processed in press machines.

* All performance analysis reports are designed to be available to senior management in an intranet environment and include multiple user levels (senior management, system management and operators), allowing all units to access the data in the fastest way.

### Indexing 
Numbering should be written in the same format as the bulleting, an example is as follows. *Example:*

The objectives can be listed in more detail as follows:

@. Measuring the performance of molds, operators and press machines where products are produced, in line with the expectations of the enterprise.
    a.  Measuring the molds in which the products are produced, in line with the expectations of the enterprise.
    a.  Measuring the molds in which the products are produced, in line with the expectations of the enterprise.

@. A system design that will allow the measurement of the quality of all kinds of raw materials, semi-finished products and espacially the materials from the supplier companies that are processed in press machines.

@. All performance analysis reports are designed to be available to senior management in an intranet environment and include multiple user levels (senior management, system management and operators), allowing all units to access the data in the fastest way.

@. Establishing a database that will prepare the infrastructure for the total quality management activities that are being carried out in the enterprise, and providing the opportunity to obtain a healthy data for these studies.

### Figures and Tables

### Tables {-}

Tables should be within the specified writing range and should not protrude in any way. The title of the table should be numbered; see Table \@ref(tab:materials) as an example, centered on the table and there should be one empty line before and after the table.

-----------------------------------
Material Name     Material Level   
---------------  ------------------
 Chasis           5,000            

 Side Wall        15,000-17,000  

 Door             15,000-17,000  

 TOTAL            35,000-39,000   
------------------------------------

Table: (\#tab:materials)  Daily average intermediate stock levels in mechanical production.

### Figures {-} 

Figures should be within the specified writing range and should not protrude in any way. All graphics and photographs except tables should be presented as figures.  Figures should be included in the text and should be legible. The title of the figure should be numbered, centered below the figure; see Figure \@ref(fig:ui) as an example, and an empty line should be left before and after the figure.

![(\#fig:ui) User interface example](figures/ui.png){width=500px}

### Referencing the tables and figures {-}

When referring to the figures and tables, the name of the figure and the table can be written in parentheses (Table \@ref(tab:materials)), or in the sentence "as shown in Figure \@ref(fig:pressure)". All the other uses (see table-\@ref(tab:materials), figure: \@ref(fig:pressure)) are not correct.

### Numbers and punctuation marks

In Turkish spelling, “,” (comma) is used as the fractional number separator and “.” (Dot) is used as the separator for thousands of digits (three zeros). *Examples:* 2.23; 12356.2.

In English spelling, “.” (Dot) is used as a fractional number separator and ”,” (comma) is used as a separator for thousands of digits (three zeros). *Examples:* 2.23; 12,356.2.
Thousands of digits are used for numbers with five or more digits. Four-digit numbers do not use thousands separators. *Example:* 4234 (four thousand two hundred and thirty-four).

In Turkish writing, the percent sign (%) is before the number (*Example:* %15). In the English spelling, the percentage (%) sign is located after the number (*Example:* 15%).
Numbers from one to nine are written in text and numbers greater than or equal to 10 are written as numbers.

The letters and symbols in mathematical expressions are written in *italic* characters, whereas the numbers and punctuation marks (such as parenthesis, colon, equality) are written in normal (non-italic) characters. In R Markdown, one can write math with LaTeX commands [@lshort]. Inline and dsplayed math example [Wikipedia -@wiki:news]:

> The standard newswender profit function is $f(p) = E[p \min(p, D)] - c p$, where $D$ is the random demand with cdf $F$, each unit is sold for price $p$ and purchased for price $c$, the number of units stocked (decision variable) is $q$. The stocking quantity of the newsvendor that maximizes expected profit is given by
$$
q^* = F^{-1}\left( \frac{p-c}{p}\right).
$$

Fertilizer linear programming example [Wikipedia -@wiki:lin]:
\begin{alignat*}{5}
\text{Maximize} \quad S_1 &x_1 + S_2 &x_2 &&&\quad(\text{maximize the revenue}) \\
\text{s.t} \qquad\\
    & x_1 +  \phantom{} & x_2 &\le L & &\quad (\text{limit on total area}) \\
 F_1& x_1 +         F_2 & x_2 &\le F & &\quad (\text{limit on fertilize}) \\
 P_1& x_1 +         P_2 & x_2 &\le P & &\quad (\text{limit on pesticide}) \\
    & x_1 \ge 0,        & x_2 &\ge 0 & &\quad (\text{cannot plant a negative area}).
\end{alignat*}

### Common mistakes
The English word ‘data’ is plural, so there is no ‘datas’ in English, ‘veriler’ is the corresponding Turkish word. In Turkish, ‘veri’ or ‘veriler’ words should be preferred. 

The word "heuristic" in English can be used as both a noun and an adjective. The Turkish equivalent of the word, ‘sezgisel’ is an adjective. Therefore, whether or not the word ‘heuristic’ is used as a noun or adjective in an English text or speech, for the Turkish equivalents, ‘sezgisel algoritma’ or ‘sezgisel yöntem’ should be used.

"Agenda" or "Outline" titles may be used in English to indicate the content of the presentation at the beginning of a presentation. Some of the Turkish words that correspond to these words may be ‘gündem’, ‘acenda’ or ‘içerik’. The use of the word ‘Ajanda’ in this sense is incorrect.

GAMS, CPLEX, AMPL, EXPRESS, EXCEL have different functions for modeling and solution of developed mathematical models. These functions must be correctly expressed in the text. Software such as GAMS and AMPL are interface software where mathematical models can be algebraically expressed with their own syntax and can communicate with a solver. The mathematical models encoded with these softwares are optimized by a decoder program such as CPLEX and EXPRESS. 

Similarly, mathematical models can be expressed in Excel worksheets with Excel software. These models can be optimized with Solver, an Excel add-on. Therefore, in Turkish (English) texts, statements such as 

> “Matematiksel modelimizi GAMS’de çözdürdük” (“We solved our mathematical model by GAMS”), 

> “Bir GAMS modeli geliştirdik” (“We developed a GAMS model”), 

> "Problemimizi GAMS'de modelledik" (“We formulated our problem in GAMS”) 

\noindent are false. Correct expressions in the Turkish (English) text as follows: 

> "Problemimiz için bir matematiksel model geliştirdik." (“We developed a mathematical model for our problem”), 

> "Matematiksel modelimizi GAMS ile kodladık ve CPLEX ile çözdürdük." (We coded our mathematical model in GAMS and optimized with CPLEX”), 

> "EXPRESS programı ile modelimizi kodladık ve optimal değerleri bulduk." (“We coded our model and optimized in EXPRESS.”), 

> “AMPL arayüzünü kullanarak modellediğimiz problemimizin optimal çözümünü bulabilmek için CPLEX çözücüsünü kullandık.” (“We used AMPL interface to optimize our model by CPLEX solver”).

### Bibliography

Bibliography should be included at the end of the report, starting from a separate page. The title of the bibliography should not be numbered and should be written in bold, 12-point Times New Roman, capital letters. 

All articles, books, internet pages etc. citations should be included in the text and listed in the bibliography. **Studies not referred to in the text should not be included in the bibliography.**

All references listed in the bibliography should be given after a line space followed by the title and aligned to the left hand side only. References should be given in the second line starting from 1 cm inside (paragraph settings: 1 cm hanging). 

In the bibliography, the authors should be mentioned primarily using their last name, followed by the first letters of their names. The bibliography should be prepared alphabetically by the last name of the authors and chronologically for each author.

Turkish texts should not contain any English words except the title of the source in the bibliography. (E.g. and, volume (vol.), number (no.), page (p.) do not use words such as.)

One way to avoid the hassle of formatting bibliographic entries is this: 1) find BibTeX entries for books from Google Books, [BibSonomy](https://www.bibsonomy.org/) and for articles from journal web sites (try googling the article title and bibtex as well),  2) save them in a .bib file, 3) give the .bib file name across bibliography field in the R Markdown file (inspect report.bib file), and cite the work with its bibtex identifier.

Include an in-text citation when you refer to, summarize, paraphrase, or quote from another source. For every in-text citation in your report, there must be a corresponding entry in your bibliography.

APA in-text citation style uses the author's last name and the year of publication, for example: @porteus2002foundations . This is the case if the source is single authored. If it is two authors, write two authors’ last names using “and”, and the year of publication again, for example: @CS04.  If it is more than two authors, write as, for example: @CIBBA06. 

In Turkish texts, use again the author's last name and the year of publication, for example: @porteus2002foundations. This is the case if the source is single authored. If it is two authors, write two authors’ last names using “and”, and the year of publication again, for example: Cooper ve Kameri -@CS04. If it is more than two authors, write as, for example: Dix vd. -@DRM02. 

When referring to a source in a sentence, the structure of the sentence must be established as if it does not refer to the source itself but to its authors. A *correct* example in Turkish text: 

> “Özellikle, @A00 ve @Hoc00 form ergonomileri üzerine yapılan çalışmaların gerekliliğini göstermiştir”. 

\noindent An **incorrect** example in Turkish text: 

> “Form ergonomileri üzerine yapılan çalışmaların gerekliliği @A00 ve @Hoc00'da gösterilmiştir”.

\noindent A *correct* example in English text: 

>“@CS04 characterize optimal ordering policies for an uncapacitated serial inventory system”. 

\noindent An **incorrect** example in English text:  

>“Optimal ordering policies for an uncapacitated serial inventory system is characterized in @CS04”. 

For multiple works of an author that have appeared in the same year, the distinction is made with letters after the year, respectively. Example: [@wiki:lin;@wiki:news;@F81;@wickham2017r]. A similar path is followed for internet addresses. *Example:* the internet addresses given in the bibliography below should be referred to as @BS05 and Turkish Statistical Institute -@Tuik06. 

For direct quotations, include the page number as well, for example: @CS04[pg. 14]. For sources such as websites and e-books that have no page numbers, use a paragraph number. More information on citing sources without pagination is given on the [APA Style web page](http://www.apastyle.org/learn/faqs/cite-website-material.aspx). *Example paragraph with in-text citation:*

> A few researchers in the linguistics field have developed training programs designed to improve native speakers' ability to understand accented speech [@DRM02; @T04]. Their training techniques are based on the research described above indicating that comprehension improves with exposure to non-native speech. @DRM02 conducted their training with students preparing to be social workers, but note that other professionals who work with non-native speakers could benefit from a similar program. See the examples in the bibliography section at the end.

\clearpage
# (APPENDIX) Appendix {-}

# Appendices {-}

The Appendix should start on a seperate page. The title should be written in bold and capital letters.

All appendices should be labeled consecutively and each one must have a title. If an appendix has subheadings, they should be numbered as well (e.g., Appendix A.1). 
Appendix can be referenced just as an ordinary section; for example, Figure \@ref(fig:flowfig) in Appendix \@ref(flowapp), consult Appendix \@ref(methodapp), \@ref(uiapp). For example, “organization chart of the company can be seen in Appendix 2.”

Appendices should be included in the same file as the continuation of the report. Appendicies should not have a landscape layout. (However, pictures and tables can be positioned horizontally as shown in Appendix 5.) The appendicies must not exceed the specified document margins.

# Raw Material Flow Chart {#flowapp}

![(\#fig:flowfig) Raw Material Flow Chart shows that ... ](figures/flow.png){width=550px}

\clearpage
## Routing Plan Obtained From the Heuristic Method {#methodapp}

![(\#fig:routingfig) Routing Plan was obtained with the heuristic method developed in Section \@ref(format).](figures/routing.png){width=550px}

\clearpage
## Sample Report in the User Interface {#uiapp}

![(\#fig:uifig) This report shows that ...](figures/ui2.png){width=500px}

![(\#fig:uifig3) Connecting with other computers](figures/ui3.png){width=500px}

\clearpage
# Locations of the Distribution Centers

![(\#fig:locfig) Solid triangles show the hubs whereas solid circles are the demand points.](figures/location.png){width=200px}


<!-- Write nothing beyond this point -->

\clearpage
# Bibliography {-}
 <!-- Need the following lines for bibliography to have hanging indentations -->
\setlength{\parindent}{-0.4in}
\setlength{\leftskip}{0.4in}
\setlength{\parskip}{8pt}
\noindent
