%%%%%%%%%%%%%%%%%%%%%%% file icad-template.tex %%%%%%%%%%%%%%%%%%%%%%%%%
% $Id: icad-template.tex 196 2020-03-20 12:09:24Z foley $
% $URL: https://repository.cs.ru.is/svn/template/tvd/journal/journal-of-physics/icad-template.tex $
%
% This is a template file for Journal of Physics Conference Series
% which is used for the International Conference of Axiomatic Design as of 2020
%
%%%%%%%%%%%%%%%%%%%%%%%
\documentclass[a4paper]{jpconf}
%% Allow Icelandic characters
\usepackage[icelandic,english]{babel}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\graphicspath{{./}{Graphics/}}
\bibliographystyle{iopart-num}
%\usepackage{citesort}
\usepackage{booktabs}
\usepackage{array} %% needed for advanced table manipulation
%% Column types from http://tex.stackexchange.com/questions/54069/table-with-text-wrapping
\newcolumntype{L}[1]{>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
\newcolumntype{C}[1]{>{\centering\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
\newcolumntype{R}[1]{>{\raggedleft\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
\usepackage{custom}
\usepackage{url}%%URL should also be the last package loaded along with hyperref if needed
\begin{document}
\title{International Conference of Axiomatic Design 2020+ Template: \jpcs}
\author{J T Foley$^{1,2}$, M J P S Cavique$^{3}$, A J F Mourão$^{4}$, J M Fradinho$^{4}$}
\address{$^{1}$Reykjavik University, Menntavegur 1, Reykjavik 102, Iceland}
\address{$^{2}$Massachusetts Institute of Technology, 77 Massachusetts Ave, Cambridge MA 02139, USA}
\address{$^{3}$Naval Academy (PT), Department of Sciences and Technology, Base Naval --- Alfeite, Almada, 2810-001, Portugal}
\address{$^{4}$Faculdade de Ci\^{e}ncias e Technologia, Universidade Nova De Lisboa, 2829-516 Caparica, Portugal}
\ead{foley AT ru.is}
\begin{abstract}
All articles {\it must} contain an abstract.
This document describes the preparation of a conference paper to be published in \jpcs\ using \LaTeXe\ and the \cls\ class file.
The abstract follows the addresses and should give readers concise information about the content of the article and indicate the main results obtained and conclusions drawn.
As the abstract is not part of the text it should be complete in itself; no table numbers, figure numbers, references or displayed mathematical expressions should be included.
It should be suitable for direct inclusion in abstracting services and should not normally exceed 200 words.
The abstract should generally be restricted to a single paragraph.
Since contemporary information-retrieval systems rely heavily on the content of titles and abstracts to identify relevant articles in literature searches, great care should be taken in constructing both.
\end{abstract}
\section*{Important Information}
This ICAD template is a customized version from the one provided by Jacky Mucklow \texttt{jacky.mucklow@iop.org} for \jpcs.
The original template and more information can be found at \url{https://publishingsupport.iopscience.iop.org/author-guidelines-for-conference-proceedings/}
IOP Publishing is to grateful Mark A Caprio, Center for Theoretical Physics, Yale University, for permission to include the {\tt iopart-num} \BibTeX package (version 2.0, December 21, 2006) with this documentation. Updates and new releases of {\tt iopart-num} can be found on \verb"www.ctan.org" (CTAN).
\textbf{Template Author's Notes (2019--02--11):}
This version of the template has descriptive sections and examples for an Axiomatic Design/Product Design paper.
If you are looking for the original MATEC LaTeX template, it can be found in \path{Instructions/JPSCLaTeXGuidelines.tex}; a PDF of the same name can be found with this file.
The original template has a lot of detailed instructions on formatting the paper, but most of that is already taken care of if you are using LaTeX.
This template takes care of formatting and placement of the citations, as long as you fill in the BibTeX file \path{references.bib} and \path{references-ad.bib} correctly.
If you are using crossrefs (to fill in the conference proceeding information), they must go at the end of the \path{.bib} file.
\subsection*{\LaTeX{} Hints}
\begin{itemize}
\item Put one sentence per line.
This makes it easier to debug errors (which are by line) and to do grammar checking with \url{http://grammarly.com}.
\item Compile the document often and look for errors.
If you find one, try commenting out the area to locate the source of the problem.
\item Watch out for \& and \%. They have to have a left-slash in front of them.
\item Underscore ``\verb|_|''is only usable in math as a subscript.
Don't put it in normal text.
\end{itemize}
\section{Introduction}
What is the idea? What is it called and why?
Who is the target customer?
\subsection{Customer Needs}
What would a customer need the item to do?
Using Axiomatic Design theory, this is stated as a numbered list of Customer Needs(CN)~\cite{suh1990principles}.
The top level is \CN0.
This is often (but not always) decomposed into \CN1, \CN2, etc.
Here is an example of a top level:
\begin{quote} \textbf{\CN0} A transfer bin for whole salmon, compatible with the SureTrack grader, cheaper and less prone to cracking due to skewing.
The bin should be adaptable to a pure transfer task and be able to discharge anywhere along its path without
accidental discharge.~\cite{gerhard2016suretrack}
\end{quote}
\section{Prior Art}
What exists that is similar? How is yours better/distinctive?
Give at least two examples and quantify the differences (numeric values).
If you say something is cheaper, you need to give the costs for both items.
An example of a figure is the grey square in Fig.~\ref{fig:grey-square}.
\begin{figure}
\centering
\includegraphics[width=\columnwidth]{grey-square}
\caption{Grey square.}\label{fig:grey-square}
\end{figure}
\subsection*{Sources}
You will want to cite all these similar concepts/products.
As an example of a citation, Carryer et al.~\cite{carryer2011IntroMechatronics} is the textbook for T-411-MECH Mechatronics 1.
\section{Design}
As previously mentioned, using Axiomatic Design Theory is a good way to develop your design.
Here is a brief synopsis from Omarsdóttir et al.\cite{omarsdottir2016chessmate}:
\begin{quotation}
Rather, the focus was placed on developing comprehensive FR and DP lists, then evaluating the coupling between them.
This coupling is symbolized in a design matrix, which is a Cartesian product of all FR and DP combinations~\cite{cochran2016msdd, benevides2012aed}.
Where there is an interaction between an FR and DP, this is denoted by a non-zero coefficient, or in the case of the value being unknown, simply a placeholder variable $X$.
Minor levels of coupling, often considered higher-order effects, are annotated with $x$ to show their lessened effect.
A diagonal matrix is ``uncoupled'' and satisfies the Independence Axiom: ``to maintain the independence of the functional requirements~(FRs)''~\cite{suh2001axiomatic}.
Such a design can be easily optimized by adjusting a particular FR or DPs without affecting others.
A diagonal matrix indicates a ``decoupled'' or ``path-dependent'' solution, which can still be optimized, but the ordering of parameter choice selection becomes important.
All other design matrices are ``coupled'' and may have a usable local solution but usually resist modification and optimization~\cite{suh2001axiomatic}.
Needless to say, the focus is on minimizing coupling wherever it may appear.
ADT's second axiom is ``minimize the information content of the design.''
Simply put, ensure that the design has the highest probability of meeting the stated FRs.
When systems are not able to meet FRs all of the time, this is denoted in ADT as ``complexity'' and is deeply explored in~\cite{suh2005complexity}.
As will become apparent in the next section, this axiom became integral to the design of the interaction between the robot and its chess pieces.
Finally, any factors to be considered that are not functional are categorized as ``Constraints.''
These are often resource-focused and affect all of the design decisions; they need to be revisited often especially when choosing between otherwise equivalent implementations.
\end{quotation}
The first axiom is often called the Independence Axiom, and the second, the Information Axiom.
From the Customer Needs, we build a list of Functional Requirements.
Again, we start with a top-level \FR0: ``Contain \SI{25}{\kilogram} of fish on SureTrack conveyor until release is triggered''
From this, a top-level Design Parameter \DP0: Gable-reinforced stainless-steel locking bin with bi-directional discharge
\cite{gerhard2016suretrack}.
We continue a ``zig-zag'' procedure to decompose and map the FRs to the DPs as shown in Table~\ref{tab:first_level-frdp}.
\begin{table}
\center
\caption{First level FR-DP mapping.~\cite{gerhard2016suretrack}}\label{tab:first_level-frdp}
\begin{tabular}{lll} \toprule
ID& Functional Requirement & Design Parameter \\ \midrule
1&Contain product&Main weldment\\
2&Move product&Support system\\
3&Discharge product &Discharge system\\
\bottomrule
\end{tabular}
\end{table}
From this mapping we develop a design matrix as shown in Equation~\ref{eq:top-design-matrix} from~\cite{gerhard2016suretrack}.
\begin{equation}\label{eq:top-design-matrix}
\begin{Bmatrix}
\FR{1}\\
\FR{2}\\
\FR{3}
\end{Bmatrix}=
\begin{bmatrix}
X & 0 & X\\
0 & X & 0\\
0 & 0 & X
\end{bmatrix}
\begin{Bmatrix}
\DP{1}\\
\DP{2}\\
\DP{3}
\end{Bmatrix}
\end{equation}
This matrix is de-coupled i.e.\ path-dependent, meaning it can be optimized, but the order matters.
\section{Experiments}
\section{Results and Discussion}
\section{Conclusion}
\subsection{Future work}
\subsection{Summary}
\section*{References}
\bibliography{iopart-num-demo,references,references-ad}
\end{document}
%%% Local Variables:
%%% mode: latex
%%% TeX-master: t
%%% End: