(report cover page)

Contents
Introduction.................................................................................................................................................3
1 Problem analysis.....................................................................................................................................4
1.1 Needs, requirements and stakeholders............................................................................................4
1.2 Technical performance characteristics.............................................................................................4
1.3 Requirements - performance characteristics relationship matrix......................................................5
1.4 Target values for the technical performance....................................................................................5
2 Operating and control application design................................................................................................6
2.1 The process flow; functions to be implemented...............................................................................6
2.2 User roles........................................................................................................................................6
2.3 User personas..................................................................................................................................6
2.4 Usecases.........................................................................................................................................6
2.5 Managed data.................................................................................................................................6
3 Interface design.......................................................................................................................................7
3.1 Get inspired......................................................................................................................................7
3.2 Usability requirements.....................................................................................................................7
3.3 Wireframing.....................................................................................................................................7
4 Interface implementation details............................................................................................................8
4.1 Technology selection.......................................................................................................................8
4.2 Home screen implementation.........................................................................................................8
4.3 Navigation mechanism implementation..........................................................................................8
4.4 Functionality implementation.........................................................................................................8
4.5 Usability evaluation.........................................................................................................................8
Conclusions.................................................................................................................................................9
Resources..................................................................................................................................................10
Introduction
When this project report is nearly finished, replace the text below with a proper introduction that should
contain the goal of your project, and the project methodology.
Project goal
For Robotics students: This project's goal is to develop an interface prototype for the control and
monitoring of a robotized line for assembling / packing / palletizing of a product (chess game). The
robotized line is designed at the Manufacturing Robotization II discipline.
Pentru studenţii de la Design Industrial: Scopul acestui proiect este de a dezvolta un prototip de interfaţă
pentru un produs care va fi fabricat industrial (ideile de produs sunt cele de la temele de licenţă). Dacă
produsul nu are interfaţă software/grafică, scopul proiectului va fi de a dezvolta portalul de Customer
Support pentru produs.
The result of this technical endeavour will be the software application prototype (developed using a
technology of your choice), together with the documentation regarding its analysis and design.
Problem description
To effectively implement the monitoring and control application of the robotized line (or - in general – our
industrial product or system), we should identify those functionalities that will allow the users to execute
monitoring tasks (like being informed on the line functioning state, productivity figures, errors and issues,
parts count), quality inspection tasks (e.g. check a sample product for defects, document the defects), and
control tasks (like starting or stopping the line, maintenance tasks or changing various settings).
To identify these functionalities we first need to understand the needs and requirements for the product or
system we’re designing (e.g. the robotized line which will automate the chess game assembly / quality
check / packing / palletizing operations), its performance characteristics, and the functions it needs to
provide to the users (i.e. the process activities).
Refer to the first section of the project guide (1 - Formulating the problem) for further details.
Project methodology
Before starting the work on this project, read the entire guide in order to understand the methodology we
follow (methodology: a system of methods used in a particular area of study or activity).
How to use this document
Adapt each section of this document to your own project. Don't leave any explanatory text in this template
"as it is", as this will make your project to be marked down.
You can insert new document sections, if you consider this necessary. You cannot delete sections (except
this one). Complete the first page (the report cover). Update the contents. Complete the reference list!

When this project report is nearly finished, replace the above text with a proper introduction that should
contain the goal of your project, and the project methodology.
1 Problem analysis
Refer to sections 1, 3 and 4 in the project guide for details on how to complete this section.

1.1 Needs, requirements and stakeholders

This section should describe:
a. Stakeholders for our product or system (e.g. the robotized line we have to develop) – for instance the
robotized line users (the operators), the maintenance engineers, the safety engineers, the customer
(the company investing in your robotized line), your organization (including all your departments),
national / international authorities dealing with health and safety issues. Justify, for each stakeholder,
within one paragraph, the reason why they're interested in the robotized line.
b. Requirements and needs identified for our product or system (e.g. the robotized line), centralized in
the requirements list. Describe who needs each requirement (and why). Use, as model, the example
from the Quality Planning course.
Identify requirements and needs considering all the steps in an industrial system’s life cycle: design, use,
disposal.
Here are design directions for the design phase:
 Design for short time to market
 Design for reliability
 Design for test
 Design for safety
 Design for quality
 Design against corrosion damage
 Design for minimum risk
 Design to cost
 Design to standards
 Design for assembly
 Design for manufacturability
 Design for logistics
Design directions for the use phase:
 Design for user-friendliness
 Design for ergonomics
 Design for aesthetics
 Design for serviceability
 Design for maintainability
Design directions for the disposal phase:
 Remanufacturing
 Design for recycling
Be careful, the needs and requirements refer to the robotized line you have to design (both hardware and
software), not the product to be assembled and packaged by the robotized line.

1.2 Technical performance characteristics

This section should present the performance characteristics (similar names: quality characteristics,
performance metrics, technical descriptors) for the robotized line (as discussed during the course
meetings). Remember that the performance characteristics refer to the process we're automating (i.e.
assembly / quality check / pack / palletize) and not to the product we're assembling.
Explain each performance characteristic (within 1-2 phrases). Indicate the measurement unit and the
optimization trend of each characteristic.
Use a table like in the guide to list all the performance characteristics.

1.3 Requirements - performance characteristics relationship matrix

This section should present the House of Quality. Use the provided template for this.

1.4 Target values for the technical performance

This section should discuss the target values you established for your performance characteristics. For
each performance characteristic, write a short paragraph explaining why you chose the corresponding
target value. The target values represent "how much" for the technical descriptors, and the final robotized
line design should reflect these target values.
Describe here also the project challenges that your team has opted for. Also describe each team member’s
role (who does what).
2 Operating and control application design
Refer to sections 5, 6 and 7 in the project guide for details on how to complete this section.

2.1 The process flow; functions to be implemented

For Robotics students, this section should start with:
(a) the process flow diagram (normally you should just “import” it from the Manufacturing Robotization
project)
(b) a draft view of the assembly / quality check / pack / palletize process (you can use a screen capture
from the Manufacturing Robotization project). You should not include too much detail here, but make
sure that the line layout can be understood. Explain briefly each area of the robotized line (assembly,
quality check, packing, palletizing).
For Industrial Design students, this section should start with a draft view of the product or system you are
designing (include here any screen captures you consider relevant). Include here also a list with the
functions your product will provide to your users.
Keep in mind that there are functions corresponding to hardware equipment (e.g. extract one pallet from
the pallet stack on the conveyor towards the loading point, move and precisely position the extracted pallet to
the loading point, etc.) and functions that will be implemented software in the operating and maintenance
application (like – but not limited to – operator login and logout, display robotized line status screen, display
warnings and issues, display process status).

2.2 User roles

Describe here the user roles for the application whose interface you are modelling (the monitoring and
control application, or the product you are designing). Examples of user roles: operator, quality inspector,
maintenance technician / technical supervisor.

2.3 User personas

Describe here the user personas (insert here the work already carried out during the project meetings). Use
one table / card for each user persona.

2.4 Usecases
Include here the use case diagram. Include here also one usecase table for each user role, for whichever
function you prefer. For usecases use the recommended template (table). For instance, a function for the
quality inspector role could be “check one chess game product for defects”. For the maintenance
technician role, a usecase could be “visualize the maintenance task calendar” or “report a recently
performed maintenance task in the system”.

2.5 Managed data

Include here the data you intend to collect and process through the operating and control application.
Present it in a structured form (tables for which you should describe each column). Recall the discussion on
information architecture and data structures from week 10. Also, recall the course topic on dashboards.
3 Interface design
Refer to section 8 in the project guide and to the courses on usability and UX design for details on how to
complete this section.

3.1 Get inspired

Perform a web search for inspiring examples. Query, for instance, Google Images, using keywords such as
“industrial user interface”, “industrial HMI”, “industrial mobile hmi” or anything similar.
Document here your findings – include in this section 4-5 examples you like most. Include also the
information source (e.g. the web link or the YouTube movie URL). For each example, describe briefly why
you found it interesting (e.g. colour scheme, menu structure, cleanness, etc).

3.2 Usability requirements

Based on the user personas, describe and argument the required usability level of your interface. Do your
target users present any particularity (age, gender, culture, education)? What’s the required training time &
effort? How will the HMI be used (e.g. while standing, sitting, or maybe walking (the mobile component)?
How is the ambient light and / or noise? Use also 3-4 paragraphs for this purpose (not less / no more).

3.3 Wireframing
Sketch the interface (screen, or screens) for each function described by the usecases. You can draw the
wireframes using any software tool, or you can draw them on paper and insert here a photo of the
drawing. For each wireframe write down the usecase it corresponds to (note that, for one usecase, several
wireframes might exist). Keep in mind that there may be several hardware devices on which your
application will run (for instance the operator panel, the operator’s mobile phone, the quality inspector’s
screen etc.). As such, you may need several application components (one to run on the operator panel, one
on the mobile, one on the quality inspector screen etc).
4 Interface implementation details

4.1 Technology selection

Motivate, in this paragraph, why you selected your development technology.

4.2 Home screen implementation

Describe here how you implemented the home screens (dashboards) for your user types. Insert relevant
screenshots and describe them. Describe additional features you may have used (e.g. notifications,
progressive disclosure techniques, etc). Briefly describe the meaning of the information presented in the
home screens / dashboards (e.g. KPIs you decided to display).

4.3 Navigation mechanism implementation

Describe here how you implemented the navigation mechanism of the operating and control application(s)
(menus, toolbars, shortcuts, navigation buttons etc.). Insert relevant screenshots and describe them.
Describe additional interfaces you may have used (e.g. a voice interface).

4.4 Functionality implementation

Describe here how you implemented the prototype of the operating and control application (the screens
corresponding to the functionalities). Insert relevant screenshots and describe them. Describe additional
interfaces you may have used (e.g. a voice interface).
Group the screenshots according to the functionalities they visually represent (consider the functions you
planned and presented in Section 2.1).

4.5 Usability evaluation

This is to be done by another team (some of your colleagues). For this, prepare and provide them a short
technical report of what you have developed (use the provided template).
In turn, you will receive a similar technical report from some of your colleagues; please evaluate the
usability of their solution. Follow these steps:
• analyse their goal, the requirements, the usability requirements, and – based on this – set a list of
minimum 5 usability criteria against which you will assess their interface prototype (if necessary,
review the usability and UXD courses to set these criteria)
• evaluate their interface proposal with respect to each usability criteria you selected and write
down your conclusions
• check their performance metrics target values and decide if these target values are realistic or
correct
• send your colleagues back, in due time, your conclusions so that they can attach them to their
project report
Please copy here the conclusions drawn by the colleagues who evaluated your interface’s usability.
Conclusions
General conclusions
Insert here the general conclusions that can be drawn after completing the project steps.
Discussion on technical performance target values
Argument how each target value (for each performance characteristic) is achieved. Discuss here the
performance characteristics related to the interface and/or the application usability.
Discussion on limitations
Discuss here what you consider to be limitations of your interface prototype: what’s not yet perfect and
how you would have done it better, given more time or resources.
Resources
Insert here bibliographic resources you may have mentioned in the text above.