In the CyClaDes project a framework has been developed to organise existing knowledge and experience to support a more user-centred perspective in the design and approval of ships and ship systems. The framework addresses the following three main goals:

  1. To determine relevant requirements for design and operation that focus more on crew requirements.
  2. To identify what motivations and types of guidance should be provided to different groups of stakeholders involved in the design and approval of ships and ship systems, about how to implement user-friendly systems and work spaces aboard ships.
  3. To provide a selection of guidance and method(s) that enable designers, operators and approval authorities to assess systems and work spaces aboard ships with respect to crew-friendly systems.

The objective of the CyClaDes framework is to cover user requirements to the design and implementation of systems and processes that are specific to particular type of task or work space. The framework for the crew-centred design and operation of ships and ship systems was developed following a human-centred design process.

The requirements of different users of the future framework were elicited in a stakeholder analysis that built upon the results generated by a stakeholder workshop and a projectinternal persona analysis. This work yielded a specification of requirements from each stakeholder’s point of view. The following stakeholders were addressed by this work and these are considered the users of the framework:

  • system designers (users of tools ,methods and best practices for the human-centered design and analysis)
  • ship designers (users of tools, methods and best practices for the human-centred design and analysis of workspaces)
  • owners and operators (land-based personnel, typically former users) who are involved in requirements specification for newbuildings and planning of work processes)
  • authorities and rule makers (users of means for evaluation of designs with respect to human element influences)

Following the stakeholder analysis, information about human centred design (including tools, methods, guidelines, legal requirements, best practices and design examples) was collected in accordance with the requirements of each stakeholder group. The collected material includes best practices in the maritime (Task 2.2, documented in D2.1 Part B) and other industries (Task 2.3, see Part B of D2.1), results of the ethnographic study (WP1), as well as new methods that were developed in the CyClaDes project. Technical solutions were developed for archiving this material in the framework and making it accessible to stakeholders.

Based on the requirements of the identified stakeholders a publicly available web based framework has been developed that allows to store and access information about human centred design of ships. The structure of the framework is organized according to the subsystems used in shipbuilding and represents all ship equipment, systems and (control) areas on a ship where human-centred design aspects can be addressed.

It has been started to populate it with human-centred design information focussed on those equipment/system developments that are required by tasks in Work packages 3 and 4 of CyClaDes. Populating the framework with information covering the entire ship is not possible within the project’s budget and timeline.

The population of the framework will be continued during the whole project time of CyClaDes and beyond – if the framework is successfully adopted by the industry.

The framework in its present state addresses primarily the ship and system designers by presenting rules, guidelines, examples and methods to better include human factor into their designs.

Operators and authorities are intended to be addressed by a scoring system to quantify and compare different design solutions with regard to their user-friendliness has been developed and tried out on one (simple) example. The extension to more complex equipment or systems is an unresolved problem and therefore the functionality is not included in the framework.

The framework is available at: