📘 Resource Overview & Documentation Details

You are viewing the technical directory listing for Collaborative Robot Requirements: A User-Centered Method. This engineering resource is curated under our Collaborative Robots division to support automation specialists, control systems engineers, and manufacturing technicians looking for verified reference materials.

🔍 Contextual Abstract & Technical Scope

Share Summary:LinkedInEmail

Defining collaborative robot requirements is not just a matter of specifying a robot’s payload, reach or cycle time. In human-robot collaboration (HRC), the system must fit the production task and the people, equipment and conditions around it. A user-centered process helps engineering teams capture those factors early and turn them into requirements that can guide system design.

A methodology applied in the CoLLaboratE project illustrates how to do this across varied manufacturing applications. It combines qualitative information from use cases and interviews with structured analysis and prioritization. The result is a requirements foundation that can support later development of scenarios and system specifications.

Why collaborative robot requirements begin with users

Collaborative applications often divide work between robotic consistency and human judgment or experience. That balance depends on the task. Assembly may involve variable parts, precise handling or decisions that are difficult to automate fully. A design that considers only the robot’s operation can miss important needs related to ergonomics, usability, safety, training and the surrounding workflow.

Early involvement of operators and other end-users helps reveal how work is currently performed, where difficulties arise and what support a robotic system should provide. It also helps clarify how people will interact with the robot, whether through direct manipulation, an interface or awareness of the robot’s position and actions. These details can shape both the system concept and its eventual acceptance in the workplace.

The CoLLaboratE approach was designed around four distinct applications: windshield component installation and visual quality work, aerospace structure riveting, television assembly, and car starter assembly. The settings differ, but comparing them makes it possible to distinguish requirements that apply to one process from needs shared across several applications.

A practical process for gathering collaborative robot requirements

The methodology has three main stages: data collection, analysis and interpretation. Validation is also planned to test whether the resulting requirements reflect broader perspectives beyond the initial use cases.

Collect information about the task and work environment

Use-case representatives first provide materials such as text, pictures and video. These give the development team context about the application and the environment in which people and robots are expected to work. Semi-structured interviews then explore three broad areas:

  • Current work: How is the task performed today, and what problems are relevant to the proposed technology?
  • Users and environment: Who will use the system, what is their background, and what support or services may they need?
  • System expectations: What are the expectations for performance, maintenance, support, security, installation and safety?

Teams can use questions about hazards, environmental interaction, sensory feedback, workload, training, accuracy, required functions and optimization goals to guide discussion. The question set should not be treated as exhaustive: additional requirements may emerge as stakeholders describe the real process.

Convert observations into clear requirements

Interview notes and transcripts are analyzed and rewritten as concise statements, such as “The user needs…” or “The system shall…”. Similar needs identified in different applications can be consolidated, while their sources remain traceable. This creates two useful groups: case-specific requirements and common requirements that apply to multiple use cases.

In the project’s initial analysis, 101 user requirements were identified across the four applications. After repeated requirements were joined, the consolidated list contained 77. The figures show why comparison matters: similar needs may be expressed differently in separate processes, but can represent a shared design concern.

Organize and prioritize requirements

A categorized list makes it easier to see where user needs are concentrated. The methodology groups requirements into 11 areas: communication, configuration and adaptability, data handling, safety and security, fail-safe behavior, functions, documentation, user interface, training, maintenance, and availability or accessibility.

Prioritization then considers three perspectives:

  • Operators: usability, intuitiveness and satisfaction.
  • End-users: costs, risks and added value.
  • Development teams: technology readiness, feasibility and integrability.

Participants assess requirements using a 1-to-5 scale, with scores averaged to support comparison. A dissatisfaction score is also considered to reflect the potential impact of not implementing a requirement. Together, these measures help teams weigh user value and development considerations rather than treating every request as equally urgent.

Prioritized user requirements can then inform system requirements. In the described approach, the Volere methodology is used to structure system requirements as functional or non-functional. Functional requirements specify what the system should do and how its functions relate. Non-functional requirements describe desired properties, including performance, efficiency and usability.

What the use cases reveal about HRC design

The applications illustrate why requirements must be grounded in process details. In windshield assembly, the robot is intended to handle components and support installation while ergonomics and collision-related concerns are addressed. In aerospace riveting, a robot may take on one operator’s role while a human continues to make decisions that are challenging to automate. For television assembly, the robot and operator share a workspace, and operators are expected to teach positions and orientations by demonstration when models change. In car starter assembly, the target task—placing copper sliding rings into metal pallets—was described as difficult to automate.

These examples do not point to one universal collaborative-cell design. Instead, they show how requirements can reflect different combinations of task complexity, human decision-making, adaptability and interaction. A common requirement, such as accommodating different applications, may sit alongside needs that are specific to a particular assembly process.

From requirements to better design decisions

For engineering and operations teams, the practical value of this method is its traceable path from workplace input to design priorities. Interviews and use-case evidence help define the problem; categorization makes patterns visible; and prioritization gives stakeholders a basis for discussing trade-offs. Broader validation with industry and academic participants can further assess whether requirements gathered from specific applications are relevant beyond those cases.

Collaborative robot requirements are most useful when they describe both the intended function and the conditions for successful use. Involving operators early, preserving the distinction between shared and application-specific needs, and making priorities explicit can give system integrators and manufacturers a stronger basis for developing HRC solutions. The result is not a substitute for detailed engineering, but a clearer starting point for scenarios, system specifications and design decisions.

Access Official Technical PDF