how do i find a good agency for interface and hmi design?
good interface and hmi design connects people with technical systems. hmi stands for human-machine interface and includes, for example, displays, buttons, and feedback from a machine. a competent agency considers these elements in conjunction with the workflow. it examines how to distinguish between normal operation, malfunctions, and different user roles.
scope of services and delimitation
interface and hmi design shapes the interface between people and technical systems. hmi stands for human machine interface and can include displays, buttons, controls, or other forms of feedback. when selecting a partner, it is important to consider whether physical operation, information, and machine status are taken into account together. a screen interface that lacks this systemic context may leave important operational questions unanswered.
the tasks vary depending on the role and operating mode. setup, monitoring, and maintenance may require different information and access rights. determine which processes need to be designed and how coordination with control systems and software development will take place. safety functions require a separately designated person with technical responsibility.
the machine must make its status clear.
a control panel is often used while the operator is in a specific posture and with fluctuating levels of attention. the most important information must therefore be relevant to the task at hand. a long list of equally weighted items makes it difficult to navigate. in the briefing, describe what decisions the operator must make and what feedback they need to make those decisions. the physical layout and screen design should be developed jointly based on this information.
four criteria for choosing a partner
- prioritizing tasks: setup, monitoring, and troubleshooting require different types of information and access.
- consider hardware factors: display position, buttons, gloves, and ambient light all affect actual operation.
- clarify state logic: have them illustrate how operating modes, feedback, and required actions are related.
- support implementation: software, control systems, and design must use the same terminology and behavior.
compare performance and work results
| task | possible work result | how it is assessed |
|---|---|---|
| operating model | roles, operating modes, and state changes | comparison with actual machine operations |
| interface | interaction between the display and controls | tests conducted at a relevant viewing distance and in a relevant environment |
| integration | consistent feedback and terminology | review with control-system and software development |
project process and decisions
first, user roles and typical workflows are identified. next, a model of the relevant states and transitions is created. simple prototypes are used to test the information hierarchy before the user interface is designed in detail. test the implementation, if possible, on the intended device or a representative setup. any unresolved technical questions regarding safety-related functions must be addressed by the responsible technical teams.
example of a device with multiple operating modes
suppose a device can be set up and then monitored in automatic mode. the same screen displays all settings at all times. as a result, important status information can get lost among options that are rarely used. a well-designed interface distinguishes between tasks and makes the current status clear.
test prototypes to determine whether users can identify relevant information and find the next intended step. at the same time, the designed behavior is compared with the actual control logic. this hypothetical example illustrates the connection between the information hierarchy and the actual device status.
common mistakes in selection and contracting
avoid uncritically adopting user interface patterns from smartphone apps. gloves, viewing distance, or divided attention may require different solutions. inconsistent terminology between the display and physical elements is also problematic. ask about how state changes and feedback are handled. if the design suggests an immediate change but the technology responds with a delay, the interface must clearly convey this actual situation.
compare costs and schedules effectively
costs and duration depend on the number of operating modes, hardware requirements, and coordination with control system development. have research, development, prototypes, and external consulting services listed separately. also, specify which revision cycles are included and who approves feedback. a schedule is only meaningful once these decisions and dependencies are known.
the briefing for an initial meeting
define operating modes, user roles, and typical tasks. list the hardware, display sizes, viewing distances, and environmental conditions. supplement existing control logic and known user errors. identify technical and safety personnel. determine which physical and digital elements can be modified. a shared glossary and a clear definition of states facilitate coordination between design and implementation.
frequently asked questions about interface and hmi design
how are transitions between operating modes handled?
by consistently describing the current state, possible actions, and relevant feedback. ensure this aligns with the actual control logic. tests should also consider transitions, since views that make sense in isolation do not guarantee a comprehensible overall flow.
why are consistent terms important in hmi?
users must be able to associate information on the display, the device, and work documents. inconsistent terminology makes this association difficult. a jointly maintained glossary helps the teams involved use consistent terminology in both design and implementation.
what should be included in the offer?
user interface logic, relevant states, visual design, and coordination with the implementation. the scope and responsibility for technical functions should be explicitly defined.
when do physical controls make sense?
when the task and the environment require direct or haptically distinguishable access, digital and physical elements can complement each other. the decision should be based on the relevant actions and aligned with the technical and safety-related constraints.
how is an hmi prototype tested?
with defined tasks and the states essential to them. where relevant, the hardware location, viewing direction, and environment should be depicted realistically. a click prototype can verify the information logic, but it does not automatically and completely replicate the behavior of the eventual machine.
what distinguishes an hmi from general ui design?
an hmi is often directly linked to a physical system and its operating conditions. as a result, hardware, timing, and the work environment become particularly important. ui expertise can contribute to this, but it must be combined with a concrete understanding of the technical system.
the perspective of f/p design
with the morita veraview x800, our portfolio combines product design with an adjustable touch panel. for a new hmi project, we therefore also discuss placement, viewing angle, and usability. the screen interface is part of this spatial user experience.
are you planning a project in this area? talk to f/p design about your project, its current status, and your desired outcome. together, we’ll determine the right design approach and the next steps.
