Sage Journals: Discover world-class research

Abstract

Product engineering is a highly complex process faced with many challenges. To meet today’s challenges of society, such as climate change, energy production and demands, and demographic shifts, and to achieve economic success for companies, technical solutions in products and systems must evolve and advance. Hereby, university research provides a potent source of cutting-edge technologies and knowledge that companies can use as input to advance their solutions. However, many challenges and barriers hinder the process of transferring new technologies, concepts, and knowledge from research to corporate engineering. In this article, we present 22 recommendations to improve the usability of research results for the activities and processes of corporate product engineering. These recommendations address the three relevant target groups: (I) corporate engineers and companies, (II) researchers and research facilities, and (III) funding agencies and (research) policymakers. First, we offer recommendations for corporate engineers and companies to integrate research results more efficiently. Second, we present recommendations for researchers and research facilities to support the promotion and transferability of their research results. Third, we provide recommendations for funding agencies and (research) policymakers to positively influence the usability of research results in corporate engineering. We expect that implementing one or more of our recommendations will enhance the efficiency of knowledge and technology transfer into corporate product engineering. We anticipate this will lead to faster technological advancements for companies and social benefits by addressing today’s major challenges more effectively.

Keywords

System generation engineering product engineering reference system innovation management knowledge transfer technology transfer industry academia collaboration

Introduction (background and motivation)

Currently, Nvidia’s growth appears to be limitless.¹ The company specializes in producing microchips and holds a prime position in the field of AI applications. Microchips are the brain for various applications, including 5G, autonomous driving, and artificial intelligence. The main challenge for engineers is to increase these chips’ performance, energy efficiency, and cost-effectiveness.² Therefore, they aim to reduce the size of the chips. For this, laser technology must be improved to establish finer structures. A collaborative project between German companies and research institutions TRUMPF Lasersystems for Semiconductor Manufacturing, ZEISS, and Fraunhofer Institute for Applied Optics and Precision Engineering IOF has developed extreme ultraviolet light (EUV) lithography technology. This technology enables the production of “higher-performance and more energy-efficient and cost-effective microchips than ever before in this decade and the next”.² Nowadays, EUV technology is a core component within ASML microchip machinery. The collaboration led to more than 2000 patents, the German Federal President’s German Future Prize 2020 (Deutscher Zukunftspreis), and enormous economic success for the partners. This collaboration between research and industry generated over one billion euros in annual turnover and created over 3000 high-tech jobs.^2,3 Other examples of successful technology and knowledge transfer from research to industry include Boston Dynamics and their humanoid robots, which originated as a spin-off of MIT’s “Leg Lab.”,^4,5 and Apple’s development of their natural language assistant, Siri, based on the technology of a research project led by SRI International.^6,7 An example for the relevance and potential of technology and knowledge transfer from research to industry in the area of fiber-reinforced composites is the project SMiLE which is a lighthouse project of the BMBF (German Federal Ministry of Education and Research).⁸ SMiLE stands for system-integrative multi-material lightweight construction for electromobility. In this project, German automotive OEMs such as Volkswagen and Audi collaborate with material (e.g., BASF) and machinery (e.g., DIEFFENBACHER) experts as well as research institutions such as Fraunhofer and Karlsruhe Institute of Technology to leverage the potentials of fiber-reinforced composites for automotive bodies in electric mobility.^9–11

These examples demonstrate the importance and advantages of close interaction between research and corporate product engineering to promote innovation. It is crucial to have an efficient transfer of technology and knowledge from research to companies to deal with the complexity and speed of current technological and societal challenges, such as those in the fields of climate, energy, or demographic shift.¹² However, many challenges still hinder this transfer. Such challenges include poor communication, lack of resources, or IP issues.^12–16 Therefore, this contribution aims to provide recommendations for improving the transfer of technologies and knowledge developed in research institutions into companies.

Throughout this paper, we use the term ‘research' to refer to the activities of research facilities, such as universities or other research institutions, like the Fraunhofer Society. We do not consider activities conducted in corporate R&D departments.

We based this contribution on ALBERS’ work, which introduced the model of SGE – System Generation Engineering^17,18 (formerly known as the model of PGE – Product Generation Engineering¹⁹) and its core element, the reference system,²⁰ to explain and model each type of development of new products or systems based on already existing elements as input, known as reference system elements.²⁰

In the following, we present the scientific background that underlies our work. The research profile section details our research goal and methodology. Next, we present our results in the following two sections (measures and recommendations), followed by a discussion section of our results. Finally, we conclude and provide an outlook in the final section.

Reuse of knowledge, technologies, and other (sub-)systems in product engineering

Classical product engineering categorizes design into three main types: original design, adaptive design, and variant design. Original design tackles new engineering challenges by combining known solution principles or newly devised ones. Adaptive design maintains established solution principles while adjusting the embodiment to meet new design requirements. Variant design involves rearranging and resizing existing parts and subsystems within predefined limits while upholding the solution principle. However, drawing precise boundaries between these types for a specific system design is challenging.^21,22 Additionally, genuinely original design projects are rare in corporate product engineering, with only about 10% of design activities falling into this category.²¹ According to IYER et al., approximately 80% of planned original designs can be achieved by modifying or directly reusing existing designs.²³ ALBERS et al. support these findings, reporting that only 7% of engineering activities are dedicated to original designs, resulting in the majority of activities involving the reuse of existing elements.¹⁹ Leveraging existing solution principles or designs has advantages such as reducing technical and economic risks,^24,25 shortening development times, and increasing design flexibility.^23,26

The literature presents various approaches for describing a design process that involves reusing existing (sub-)systems, technologies, and knowledge. Under the term “Design Reuse”, the topic originates from informatics and software engineering.²⁷ It is summarized as “the process of using previous design artifacts in future designs”.²⁸ Here, the Design Reuse Model explains design by reuse as a process that searches knowledge resources for useful knowledge, retrieves and applies it to the new design.²⁹ The Flexible Design Model explicitly starts with an existing product and analyzes the market to identify relevant other products. These products serve as input for the new design based on a function analysis and comparison of their technical fulfillment.³⁰ However, the core elements of these models and processes still lack formalization.²⁷ With for example, Case-Based Reasoning (CBR) and Model-Based Reasoning (MBR), they offer methodical support for reusing knowledge. CBR aims to provide existing designs to reuse in new designs directly or as the starting point for new designs. MBR generalizes existing designs to provide more general design knowledge as input compared to CBR.^29,31 Contrary to the Design Reuse and Flexible Design Model, the C-K-Theory is a highly formalized but abstract design theory using mathematical relations.^32,33 The C-K-Theory distinguishes two spaces (sets in a mathematical sense), the Concept-Space and Knowledge-Space. All elements used in the design process are part of one of theses spaces. The K-Space collects all elements that were tested or validated for the design project. Thus, it is known whether the element works or isreasonable for the design problem, or does not work or is not reasonable. This knowledge highly depends on the individual engineer or engineering team. The C-Space contains all unvalidated or untested elements. Within the C-K-Theory, new designs are generated by extending or reducing existing elements, and product engineering represents the coevolution of the C and K-Spaces.³² While highly formalized, the C-K-Theory seems limited in practical application.³³

To establish a solid foundation for design research and design support development, ALBERS et al. developed the model of SGE – System Generation Engineering.¹⁹ Therefore, based on the observation of real engineering projects, the model of SGE combines aspects of both the approaches of design reuse and the C-K-Theory. It incorporates a hierarchical and structural concept of the system theory (cf.³⁴ and³⁵) and the description of the relations of already existing elements as references to the new design on a mathematical basis. The model of SGE can describe and model each type of development of a new system as a new system generation based on a reference system.¹⁹

The reference system within the model of SGE – System Generation Engineering

The reference system comprises all kinds of physical and non-physical – tangible and intangible – elements that engineers use as “the basis and starting point for the development of the new [system] generation”.²⁰ These elements are modeled as reference system elements.²⁰ The reference system is a complex system itself that many factors influence.³⁶ ALBERS et al. further discuss the internal structure of the reference system.³⁵ Figure 1 illustrates the basic principles of the model of SGE.

Figure 1.

The reference system within the model of SGE – System Generation Engineering. Each new system generation G_i is developed based on its reference system R_i through carryover variation (CV), attribute variation (AV), and principle variation (PV). The example shows how the first Tesla Roadster $G_{i = 1}^{T e s l a R o a d s t e r}$ relates to its corresponding reference system $R_{i = 1}^{T e s l a R o a d s t e r}$ which contains subsystems of reference products such as the battery technology of a laptop and the body of a Lotus Elise. The reference products were already available on the market in a later generation ( $G_{i = x}^{L a p t o p}$ and $G_{i = y}^{L o t u s E l i s e}$ with $x, y \in N_{> 1}$ ) when Tesla developed its Roadster. (based on²⁰).

The model of SGE explains how a new system generation (G_{i = n}) is developed based on the corresponding reference system (R_{i = n}). The variable i counts the system generations, where i = n represents the system generation in development that will be introduced to the market next. The model of SGE describes the design process as the projection of the reference system elements to the next system generation using a variation operator with three types of variation. First, carryover variation (CV) maintains the reference system elements without any changes. However, if necessary, interfaces are adjusted during the integration into the system in development. Second, attribute variation (AV) preserves the solution principle of the reference system element but modifies attributes such as the embodiment when integrated into the system in development. Third, principle variation (PV) alters the solution principle of the reference system element when integrated into the system in development (e.g., combustion engine vs electric engine).^19,20

According to ALBERS et al., reference system elements “originate from already existing or already planned socio-technical systems and the associated documentation”.²⁰ This definition also includes knowledge elements or technologies from research. Most reference system elements originate from previous system generations or further projects known to the engineering team.^37,38 However, reference system elements can originate from various sources, including competitors, clients, suppliers, research (as discussed in the next section), nature, or society.^20,39,40 Figure 2 presents a systematic analysis of possible sources for reference system elements. A total of 12 knowledge spaces offer potential reference system elements. Additionally, Figure 2 provides an overview of various methods and tools for harvesting these knowledge spaces.⁴⁰

Figure 2.

12 knowledge spaces offer possible reference system elements (RSEs). Various methods and tools can be used to harvest these knowledge spaces. Reference system elements can originate from the same branch, a different branch, research, or society/ nature. These elements may already be part of the corporate knowledge (internal knowledge), part of the total accessible knowledge, or part of the globally existing knowledge. (based on⁴⁰).

Here, research is a source for potential reference system elements of particular interest.

Research results as reference system elements

Research offers cutting-edge technologies and knowledge.^41,42 These advances are essential for corporate product engineering to develop solutions to significant technological and societal challenges, such as those related to climate change, energy, or demographic shifts.¹² In general, efficient usage of research results in corporate product engineering is a primary factor for the success and technological progress.^{12,13,15,41–43} While corporate engineers know about the value of research results and want to use them more, the integration of research results into their engineering activities needs improvement.⁴³ The literature describes identifying reference system elements in research and analyzing and managing them as core challenges of using research results as reference system elements.^23,27,37 University-company collaboration is one way to transfer knowledge and technology from research into corporate product engineering. These collaborations face, i.a., “transaction-related barriers” and “orientation-related barriers”,⁴⁴ as well as company-internal barriers.¹⁵ Using research results without direct collaboration offers further challenges. Figure 3 shows an overview of 26 barriers and challenges corporate engineers have to face when searching for reference system elements in research or using them.¹⁶ KEMPF et al. identified challenges and barriers related to the corporate engineer or company, the specific research results, the nature of research, and the search or application process or reference system elements from research. Furthermore, they link these challenges and barriers to different types of research results.¹⁶

Figure 3.

Overview of 26 challenges and barriers corporate engineers have to face when searching for reference system elements (RSE) in research or using them. The challenges and barriers affect different research result types (based on¹⁶).

These challenges and barriers hinder using research results as reference system elements in corporate product engineering. Therefore, they can slow down potential technological advancement. The goal of this contribution is to address the presented challenges as we present in the following.

Research profile – aims and methodology

Research aim and research questions

As presented in the introduction, research is a valuable source for corporate product engineering to search for reference system elements as input for developing new systems and products. However, many challenges exacerbate searching and using research results as reference system elements in corporate product engineering. Thus, the main goal of our paper is to improve the usability of research results as reference system elements in corporate product engineering. Therefore, this contribution aims to provide targeted recommendations to the relevant stakeholders of the knowledge and technology transfer from research into corporate product engineering. We provide recommendations for the three target groups: corporate product engineers and companies, researchers and research facilities, and funding agencies and (research) policymakers. To reach this goal, we formulated the following two research questions, which we answer in this paper:

1. What measures addressing the relevant stakeholders help to overcome the challenges and barriers in using research results as reference system elements in corporate product engineering?

2. How can the three target groups improve the usability of research results as reference system elements in corporate product engineering?

Answering these research questions, we formulate targeted recommendations to improve the usability of research results as reference system elements in corporate product engineering for all three target groups.

Research approach

We followed a two-stage approach to answer the presented research questions and reach the formulated research aim, as presented in Figure 4.

Figure 4.

Two-stage research approach to answer the research questions. In the first stage, we conducted an on-site workshop with 43 participants in the world-café style to answer the first research question. Based on the first stage, we developed the first version of recommendations, which we validated and refined iteratively in a two-step sounding board. We developed the final set of 22 recommendations to improve the usability of research results as reference system elements in corporate product engineering, answering the second research question.

In the first stage, we conducted a 90-min on-site expert workshop with 43 participants from corporate product engineering, research, and research funding and management during the system:ability conference 2023 to answer the first research question. The participants were all associated with research projects funded by the BMBF (German Federal Ministry of Education and Research) within the initiative “Handling the complexity of sociotechnical systems – a report on Advanced Systems Engineering for the value creation of tomorrow (PDA_ASE)” of the “Innovations for Tomorrow’s Production, Services, and Work” research program.

Based on the challenges and barriers of using research results as reference system elements in corporate product engineering, as KEMPF et al.¹⁶ presented, the participants derived and collected measures to overcome these barriers and challenges. To do so, we divided all participants into three groups and organized each group as an independent world-café setting (cf.⁴⁵ or⁴⁶) with two rounds. Thus, we split groups one and two into three teams working on measures addressing one of the three target groups: corporate product engineers/ companies, researchers/ research facilities, and funding agencies/ (research) policymakers. Due to the total number of participants, we split Group 3 into only two teams. As a result, group three did not work on measures and ideas for corporate product engineers/ companies. Each team began by developing and collecting measures addressing one of the target groups during the first round of 30 minutes and documented them on a poster. For the second round, one team member remained with the poster while the others reviewed the results of another team in their group. During a 30-min timeframe, they discussed the results of the first round and added their comments and further input. Finally, in the third step, one team per group presented their findings to all participants for one of the target groups and collected final comments from the plenary within 20 minutes. After the workshop, we condensed the results of all teams, removing duplications, resulting in a total of 66 measures. We present the results of this first stage in the next section.

Based on the set of 66 measures and our expertise, we developed the first version of 24 recommendations by combining similar and related measures. Here, we divided the recommendations into three target groups and eight fields of action. In the second stage, we used a two-step sounding board (cf.⁴⁷ or⁴⁸) approach to develop further and initially validate our set of recommendations with 37 participants in two iterations to answer the second research question. In the first step of the sounding board approach, we conducted a one-hour online workshop with 17 participants using an online whiteboard tool. Here, the 17 participants were all design/ engineering science researchers focused on engineering methods and part of our research groups. All of them had experience in industry-academia collaboration, too. In the workshop, we split the participants into two groups to review and sound 12 out of 24 recommendations per group within 40 minutes. The participants submitted their feedback in writing on sticky notes and providing oral comments. During this period, we engaged in answering questions and receiving oral feedback. The workshop concluded with 10 minutes of open discussion. We used all feedback to revise and develop the second version of the recommendations.

In the second step of the sounding board, we asked an expert group of 20 participants to sound the second version of the recommendations in written form. Here, the participants could choose between online form-based and document-based sounding to meet their preferences. The 20 participants in the second step do not overlap with the previous participants. Eight of the 20 participants were leading German design/ engineering science researchers. Another eight were leading experts in German medium-sized and large companies in the automotive, automation technology, and industrial engineering sectors. Four were part of the German funding agencies working for the BMBF and an industry-driven network. We split the participants into two groups, sounding 13 of the 24 recommendations each (two were sounded by both groups). Figure 5 shows the allocations of the participants to the recommendations.

Figure 5.

Allocation of the participants into two groups and allocation of recommendations to the groups. Based on the feedback, we rejected the initial recommendations 6 and 21.

Three participants of the group of funding agencies, one of the researchers, and one of the corporate experts did sound all the recommendations. As guiding questions, we asked the participants to comment on the strengths and weaknesses and to add potential missing aspects or recommendations. Furthermore, we asked the participants to rate the relevance of the recommendations on a six-point Likert scale ranging from 1 – non-relevant to 6 – very relevant. For this round of sounding, we translated the recommendations into German. Based on the sounding board’s feedback, we rejected the initial recommendations 6 and 21 because the sounding board deemed them already implemented or irrelevant. Finally, we developed the final version of 22 recommendations, as presented in the after next section (recommendations).

Following our recommendations, we developed short video clips to present them in an attractive and easily accessible format.

The two-step sounding board was designed and conducted during a master thesis.⁴⁹

Measures to overcome the challenges and barriers to using research results as reference system elements in corporate product engineering

Table 1 presents the results of the world-café workshop. We identified 16 measures addressing the target group of corporate product engineers/ companies, 24 for researchers/ research facilities, and 26 for funding agencies/ (research) policymakers.

Table 1.

Measures to overcome the challenges and barriers in using research results as reference system elements in corporate product engineering developed during the world-café at the system:ability conference.

Measures for corporate product engineers/companies	Measures for researchers/research facilities	Measures for funding agencies/(research) policymakers
Translating research question	Stakeholder-specific preparation of results	Requesting specific use cases
Mindset for failures	Presentation of partial results via success stories	Transparent communication of the shift in goal/focus
Dismissing the need for ROI in research projects	Publication of learnings from “failures”	Offering (flexible) funding for demonstrators
Central repository for research results^{F/P, R}	Ensuring quality and use case relation by, e.g., using reporting templates for research results or standardizing of the preparation of methods (e.g., methods development kits)	Enabling easy and direct exchange between politics, companies, and research
Preparation and presentation of the concepts in the corporate context to present to the management	Developing competencies (integrated with company and research) such as “transfer to teaching” using e.g., competency navi	Requesting specific work packages for transfer within projects (+ funding of, e.g., transfer platforms)
Explaining abstract concepts by explaining benefits (e.g., economic, technological, methodical, organizational, administrative) in terms of, e.g., business case, interpretation/ transferability^R	Early involvement of companies (reflection canvas) by, e.g., co-creation workshops with interdisciplinary teams, using reflexive methods (e.g., sprints/ agile approaches and methods/ adaption/ process step/ project) to reach honest reflection in the consortium + company + politics/ funding agencies	Offering long-term funding for the operation of results and transfer platforms
Integrating intermediaries, e.g., transfer and competence centers or consultancies/ service providers	Improving transferability by, e.g., integrating best practices, involving company partners, collecting requirements, publishing results and methodology	Ensuring the continuation by, e.g., working groups, initiatives, standards, associated partners
Providing enough time for research/ investigations	Considering a specific use case (building an industry research tandem)	Simplifying/ accelerating the application process
Staying close to research facilities (in terms of staff)	Videos with corporate partners, etc. (Interviews, Q&A)	Requesting/ offering contact persons beyond the end of the project
Capability to analyze research repositories methodically^{F/P, R}	Focusing on public relations and evolving research communication (e.g., involving PR agencies)	Requesting/ offering transfer roles in the consortia
Decreasing obstacles for cooperative formats	Focusing on open-source science, open access (including data and algorithms)	Increasing transparency in the evaluation of success
Providing R&D budget	Considering the transfer to other companies	Supporting start-up
Budget for high-risk projects	Requesting and promoting publications from working groups, committees, etc.^F/P	Requesting/including additional funding from companies
Specific user-oriented addressing of benefits, boundary conditions, limitations, and comparable examples^R	Synchronizing “jargon”/wording (two languages: Paper vs. natural language) by, e.g., using publications as a basis for discussions (not only presentation of results, talking with each other, using graphical representation (if possible, using standardized systems such as UML), guided tours/open house, events for exchanges	Adding KPIs after project run time to the evaluation (e.g., successful transfer of technologies)
Transferring research results to company-related examples	Using personal networks to transfer to companies that are not involved	Improving the conditions for open-access publication
Offers with differentiated entry points, requirements for the company, and support services^{F/P, R}	Improving research communication by using a common language within the project (including, e.g., expanded internal knowledge management, glossary)	Flexible follow-up funding of projects, including, e.g., time buffer for follow-up projects (for bridging)
	Focusing on use cases at conferences	Considering user needs for call formulation
	Visualizing the big picture at conferences	Requesting best practice formalization
	Additional paper chapter: Risks and benefits using a specific case study	Requesting/offering a central exchange platform with sponsors (online)
	Basic funding (stipends, funding projects, industrial projects) ^F/P	Including politicians as a multiplier and supporter to increase the visibility of results
	“Reducing” the long development time by, e.g., reducing formalization, breaking down the task into sub-work packages, sharing of intermediate results (e.g., through retrospectives), adjusting proposals to possible agile working formats^F/P	Enabling flexible proposals to extend the consortium, funding, and funding period
	Increasing venture capital for research^C	Connecting developers/users
	Ending “publish or perish” (often publications are the only success factor)	Providing contact persons who help with/expedite applications
	Considering interfaces within project calls^F/P	Looking for (external) investors
		Considering trends for call formulation
		Stressing known barriers

^C Relevant for corporate product engineers/ companies, too.

^R Relevant for researchers/ research facilities, too.

^F/P Relevant for funding agencies/ (research) policymakers, too.

Reviewing the ideas for measures to improve the usability of research results as reference system elements, we observed that some of the participants’ ideas were better suited for a different target group. We marked these inputs with the exponents ^C, ^R, and ^F/P to indicate the fit within the respective target group. Furthermore, we discovered that the participants had difficulties elaborating their ideas in further detail, but they provided us with many ideas for measures covering a wide variety of aspects. These ideas range from presenting research results in alternative formats to soft and hard skills and adjustments to the corporate and research organizations and resources.

Recommendations to improve the usability of research results as reference system elements

Based on the measures presented in the previous section, we developed 22 recommendations for the three target groups: corporate product engineers and companies, researchers and research institutes, and funding agencies and (research) policymakers. We developed eight fields of action that consist of two to four recommendations each. Figure 6 illustrates the allocation of the recommendations to the fields of action.

Figure 6.

Overview of the 22 final recommendations to improve the usability of research results as reference system elements in corporate product engineering. We allocated the interconnected recommendations to eight fields of action addressing the target groups: corporate product engineers and companies, researchers and research institutes, and funding agencies and (research) policymakers.

We present the individual recommendations for each target group in the following three subsections. The recommendations presented are the result of the research approach as presented before. In addition to the following explanation, we created short video clips to present all recommendations visually (following our recommendation 12).⁵⁰

Recommendations for corporate product engineers/companies

In total, we developed eight recommendations for corporate product engineers and companies to improve the usability of research results within their engineering projects. As shown in Figure 7, we clustered the recommendations within three fields of action.

Figure 7.

Overview of the recommendations for corporate product engineers and companies. The first three fields of action contain recommendations one to eight addressing the corporate side to improve the usability of research results as reference system elements within their engineering projects.

In the following subsections, we present the recommendations for each field of action.

Field of action 1: Corporate organization and structure - encouraging the usage of research results as reference system elements

The first field of action collects recommendations that address the organization and structure of a company. These recommendations aim to create an encouraging environment for product engineers to use research results as reference system elements in their engineering activities.

Recommendation 1: Raising the awareness of engineers for the potential of research results as reference system elements

Companies should regularly (e.g., quarterly) publish updates on the successful integration of technologies, process elements, knowledge elements, etc., from research into their (sub-)systems within the company. E.g., they can post success stories on the intranet or organize internal events. Here, they should include how the company benefited as well as the learnings of the colleagues involved. In addition, companies should share interesting research results with their engineers via regular updates. Even if the persons who identified the research results (e.g., through scouting activities) do not have an application yet, it may trigger another engineer.

Recommendation 2: Encouraging engineers to search for research results as reference system elements

Companies should encourage their engineers to look for research results that can serve as reference system elements. To make this possible, companies should

1. provide their product engineers with a dedicated budget and time to search for valuable and relevant research results. These resources give engineers the freedom to harvest research despite their daily work.

2. Install an open-minded management with a scientific background that encourages the engineers to refer to research results in their engineering activities.

3. Send their engineers to participate in (scientific) conferences to stay up to date on research developments. Furthermore, they should strengthen their networks; novel approaches can spark their association and creativity.

4. Strengthen their collaboration with research facilities (e.g., by conducting collaborative workshops). Thereby, the transfer of concrete research results can be supported. Furthermore, the participating corporate engineers benefit from the researchers’ influence and stay open-minded about the potential of research.

Recommendation 3: Managing research results as reference system elements

Companies should set up a research results management system to centrally coordinate the knowledge and associated information gathered from research. Therefore, the company should collect

1. Research results already used within the company. These research results should be linked to the (sub-)systems they were the basis for or integrated into.

2. Research results with potential that were identified but have not been implemented yet. Initial ideas or potential applications of the research results can be linked to these research results.

3. The research facilities/ researchers and involved partners that developed the research results and link them to the respective research results.

4. Interesting research facilities/ researcher contacts even though they have not used their research results yet.

5. The contacts of the corporate engineers who identified and/ or used the research results and link them to the research results.

6. The in-house contact persons for different research facilities/ researchers and link them to the research facilities/ researchers.

7. The best practices and challenges of the involved product engineers and link them to the research results and/ or research facilities/ researchers.

Field of action 2: Knowledge and technology transfer - first steps after the identification of research results as reference system elements

The second field of action’s recommendations aim to support corporate product engineers in the first steps after they identify potentially valuable and interesting research results.

Recommendation 4: Translating the research language to corporate language

The corporate engineers should translate the uncommon research-specific language used in the research result or its description into a language common to the company (e.g., by reformulating research questions as a description of the topic and goal of the research result). If not described already, corporate engineers should derive

1. The possible use cases and/ or applications of the research results.

2. An (initial) description of the expected benefits of using the research results in their (sub-)systems. Therefore, they should consider the benefit

a. For themselves (the company) as a provider of a (sub-)system by using the research result.

b. Generated for customers of the (sub-)system when the research result is used in it.

c. For the users of the (sub-)system when the research result is used in it.

Recommendation 5: Assessing the maturity of the research results as well as risks using it as reference system elements

Corporate engineers should analyze the maturity and validity of the research result. For example, the Technology Readiness Levels (TRLs – cf.⁵¹ or⁵²) concept can help to analyze the maturity. Furthermore, the corporate engineers should execute a risk assessment (e.g., using an FMEA or Gartner hype cycle) to identify possible risks of using the research result as input for their engineering activities. Finally, the corporate engineers should identify the next steps for using the research result in their engineering activities. Necessary steps can be, for example, validation activities.

Field of action 3: Design support - supporting corporate engineers in the integration of research results as reference system elements in their engineering activities

The third field of action collects recommendations for design support (tools) that companies should implement to support their product engineers in using research results as reference system elements within their engineering activities.

Recommendation 6: Designing the reference system with conscious and explicit consideration of research as a valuable source

The design of the reference system is a complex and creative task that the engineers should consciously conduct throughout the entire development process of a new (sub-)system generation. Corporate engineers should be aware of this and specifically consider research as a valuable source for reference system elements.

Recommendation 7: Identifying situations/engineering activities that benefit from research results as reference system elements

Corporate engineers/companies should analyze their engineering activities to identify situations where using reference system elements from research could be beneficial. This analysis serves as the basis for the development/implementation of design support, which makes corporate engineers look into research at the right moments. Including researchers in identifying such situations for scientific assistance will be beneficial (cf. Recommendation 14).

Recommendation 8: Proposing potentially suitable research results as reference system elements during engineering activities

The company should implement a tool that suggests research results (e.g., stored and characterized according to Recommendation 3) as reference system elements on the fly during engineering activities. e.g., this could be an AI tool that compares the present engineering activity with the characteristics of the research results. A prerequisite for this recommendation is to know about the relevant situations, as explained in Recommendation 7.

Recommendations for researchers/research facilities

In total, we developed nine recommendations for researchers and research institutes to improve the usability of their research results within corporate engineering projects. As shown in Figure 8, we clustered the recommendations within three fields of action.

Figure 8.

Overview of the recommendations for researchers and research facilities. The fields of actions four to six contain recommendations 9 to 17 addressing the research side to improve the usability of their research results as reference system elements within corporate engineering projects.

In the following subsections, we present the recommendations for each field of action.

Field of action 4: Research organization - promoting research results and supporting the transfer

The fourth field of action contains recommendations for research organizations to support and coach their researchers in communicating and transferring their research results.

Recommendation 9: Increasing the proficiency in the communication of research results

Research facilities should support the researchers in disseminating and promoting their results in up-to-date and attractive formats beyond text-based publications, e.g., short clips on the state of research. To this end, they should engage PR experts and develop a social media strategy. They should offer various options for presenting research results to address specific stakeholders’ needs. Based on this strategy, the research facilities should offer coaching to the researchers. In addition, the research facilities can set up a presentation space. The presentation space offers researchers a professional environment to produce promotional and presentation material (e.g., photos, videos) or welcome interested industrial partners to present their results.

Recommendation 10: Supporting the transfer and accessibility of research results

The research facility should provide a transfer-friendly environment by supporting spin-offs, patent strategies, etc. Furthermore, research facilities should provide (long-term) repositories of research results. A well-structured overview and collection of research results will help interested parties to find them. In accordance, a well-described presentation of the research activities of the research facility also increases the findability of corresponding expertise.

Field of action 5: Researchers - adjusting research results to the customers (corporate engineers)

The goal of the fifth field of action’s recommendations is to directly support the researchers in presenting their results in a way that adjusts to the needs of corporate product engineers.

Recommendation 11: Including the benefits bundle in publications

Researchers should address the (expected) benefits bundle in their results (e.g., scientific publications). Here, researchers should describe the potential benefits for

1. The corporate engineers/companies that use the research result as a reference system element in developing their (sub-)system.

2. The customers of a (sub-)system when the research result is used in it.

3. Users of a (sub-)system when the research result is used in it.

Additionally, the researchers should describe potential use cases or applications for their research results. Based on a risk assessment (e.g., SWOT) and description of the maturity (e.g., RRL, TRL), researchers should outline the next steps for using their research results in corporate engineering activities (cf. Recommendations 4, 5, and 18).

Recommendation 12: Using new communication and presentation formats for research results

Researchers should adapt to the changing ways in which information is consumed. Thus, they should use social media and more visual (e.g., video, photo) ways of presenting and explaining their research results (cf. Recommendatoin 9 and 19). Additionally, the researchers should keep the language common in practice in mind (cf. Recommendation 4) and/ or provide a glossary.

Recommendation 13: Communicating additional information - success stories, best practices, learnings from failures

In addition to presenting classical research results, researchers should communicate success stories and best practices for using their research results within corporate engineering activities. Besides the positive learnings, researchers should communicate failures and corresponding learnings within research as well as the transfer and use of research results in corporate engineering activities. To do so, cooperation with corporate partners is necessary and increases the validity of such learnings.

Field of action 6: Design research - developing design supports for using research results as reference system elements in corporate product engineering

The sixth field of action comprises recommendations for researchers to develop new design supports. These design supports will assist corporate product engineers in using research results as reference system elements within their engineering activities.

Recommendation 14: Developing design support for identifying situations/engineering activities that benefit from research results as reference system elements

In cooperation with corporate product engineers, researchers should develop design support to identify the situations and engineering activities in product engineering that can benefit from considering research results. Such design support (e.g., a method or tool) can help raise awareness of the potential of research results and target efforts. In addition to general findings, such support needs to be specified for the individual companies, as it will depend on, for example, the sector, the position in the value chain, and the position in the competition (cf. first mover vs follower).

Recommendation 14 corresponds to Recommendation 7: Identifying situations/engineering activities that benefit from research results as reference system elements and forms the basis for Recommendation 8: Proposing potentially suitable research results as reference system elements during engineering activities and Recommendation 16: Developing design support for the systematic consideration of research results in the synthesis of reference systems.

Recommendation 15: Developing search tools for screening research activities and results (beyond paper databases)

Researchers should develop support for corporate product engineers to search for research results systematically. Scientific databases for publications do allow systematic analysis. However, otherwise, the search for research results is mainly unsystematic (personal networks, conference participation, etc.). Methods and tools for searching for knowledge, technologies, etc., are rarely explicitly linked to research. Researchers could develop a “meta-crawler” harvesting different sources for research results.

Recommendation 16: Developing design support for the systematic consideration of research results in the synthesis of reference systems

Researchers should develop support for the systematic consideration of research results in the synthesis of the reference system. Here, the range spans from, e.g., making the reference system explicit and systematically modeling the reference system (e.g., using MBSE) to identifying and working with valuable research results. Creating a reference system is a complex and creative endeavor that generally has not yet received sufficient systematic support. That makes the process of synthesizing a reference system a research area that needs to be explored further. (cf. Recommendation 6).

Recommendation 17: Developing a repository for research results beyond scientific publications

Researchers should develop a repository for researchers to share their research findings. Although the academic community effectively organizes and shares written research publications and data, other data formats, such as videos, digital models, and physical demonstrators, are not consistently archived and distributed across the research community. A repository can help to systematically complete the picture of research activities and results from research facilities and researchers.

Recommendations for funding agencies/(research) policymakers

In total, we developed five recommendations for funding agencies and (research) policymakers to influence the research ecosystem in a way that fosters the usability of research results as reference system elements in corporate engineering projects. As shown in Figure 9, we clustered the recommendations within two fields of action.

Figure 9.

Overview of the recommendations for funding agencies and (research) policymakers. The fields of actions seven and eight contain recommendations 19 to 22 addressing the public governance side to improve the usability of research results as reference system elements within corporate engineering projects.

In the following subsections, we present the recommendations for each field of action.

Field of action 7: Engineering relevance and dissemination - meeting the needs of the industry

Field of action seven collects recommendations for funding agencies and (research) policymakers that foster the accessibility of research results.

Recommendation 18: Requesting the expected benefits bundle in the proposal

Funding agencies should consider the expected benefits bundle of the proposed research when selecting projects for funding. To do so, they should ask the applicants to describe the expected benefits of their research results. The applicants should

1. Describe the benefits for the corporate engineers/companies that use the research results as reference system elements in developing their (sub-)system.

2. Explain the potential benefits created for the customers of a (sub-)system when the research results are used in it.

3. Outline the potential benefits created for users of a (sub-)system when the research results are used in it.

In addition, the applicants should describe potential use cases or applications for their research results.

Recommendation 19: Funding and requesting demonstrators and transfer activities beyond scientific exchange

Funding agencies should request demonstrators to showcase the functionality of the research results and as a vehicle for transfer. The format of the demonstrators is highly dependent on the specific research project. Funding agencies should provide the necessary funding to enable the development of demonstrators. Furthermore, the demonstrators should be integrated into additional transfer activities (cf. Recommendations 9 and 10). As a result, funding agencies should request researchers to outline transfer activities in their project proposals beyond participation and publication in scientific conferences and journals. The active participation of researchers in standardization activities can be such a measure.

Recommendation 20: Introducing regular thematic exchanges beyond project consortia

The funding agencies should support and organize regular thematic exchange meetings. Linking members of related project consortia and interested third parties can help to promote (and further develop) the research results and activities. This approach allows funding agencies to direct the audience and ensure the research results are disseminated within a local area, in addition to the usually global scientific conferences or journals. Partnering with, e.g., standardization organizations is beneficial to encourage productive meeting settings and goals. The format of the exchange meetings can vary (e.g., presentation vs working sessions) and require thorough preparation and agenda to keep the stakeholders interested.

Field of action 8: Researcher incentives - adjusting the success measurement of research projects

The last field of action’s recommendations aim to provide measurables (KPIs – Key Performance Indicators) for funding agencies and (research) policymakers to monitor and motivate researchers and research facilities to emphasize transfer activities. The instrument of KPIs is highly sensible because it can foster misuse, too. Thus, funding agencies and (research) policymakers should pay special attention to this field if implemented.

Recommendation 21: Introducing transfer KPIs on the research facility level

Funding agencies and research policymakers should increase the significance of transfer key performance indicators (KPIs) for research facilities. Focus should emphasize, for example, spin-offs, patents, or companies participating in research projects.

Recommendation 22: Introducing transfer KPIs on the researcher level

Funding agencies and research policymakers should increase the significance of transfer key performance indicators (KPIs) for researchers. Focus should emphasize, for example, patents, standards, open access publications, companies involved in research projects, and transfers of research results to companies.

Discussion

We developed the final set of 22 recommendations incorporating the feedback of both sounding board steps as presented in the previous section. In the second round of the sounding board, we also asked the participants to rate the relevance of the recommendations. Figure 10 shows the results of this rating. All of the final 22 recommendations were rated rather relevant to very relevant, which is why we kept them all.

Figure 10.

Average relevance of the final 22 recommendations on a six-point-Likert scale (1 – non-relevant to 6 – very relevant).

Of the initial 24 recommendations, we rejected two based on feedback from experts of the sounding board who deemed them too trivial and already implemented (cf. the research approach subsection).

Following the presented research approach, we believe the set of 22 final recommendations is highly relevant and addresses the most critical challenges of using research results as reference system elements in corporate engineering. Especially the second step of the sounding board with 20 selected experts from all three relevant stakeholder groups ensures the validity and relevance of the recommendations. However, it is important to note that our results are limited to the German industry-academia situation, as the experts we consulted are primarily from these communities. Furthermore, the validation by the sounding board approach must be considered initially, as we did not validate all aspects of our recommendations (such as the applicability – cf. DRM,⁵³ e.g.). In the following, we discuss the recommendations on a general and specific level.

“Every engineering process is unique and individual”.⁵⁴ In the same way, the situation in every company, research facility, and funding agency/funding program is unique and individual. It is crucial to understand that we provide a set of 22 recommendations as a baseline to improve the usability of research results as reference system elements in corporate engineering. It is obvious that the current situation in the different entities is totally individual. Thus, every addressee of the recommendations needs to select the most valuable recommendations for their specific needs, for example, assessing a field with significant potential for improvement. The implementation of our recommendations naturally requires additional effort during implementation. Therefore, addressees must carry out a cost-benefit assessment. While some entities might already follow some of our recommendations, our validation showed that others do not. Thus, not all recommendations will be new to all addressees. Looking at the field of action 4 (Research organization - Promoting research results and supporting the transfer), e.g., various research facilities are already taking action and/ or providing support for their researchers. However, this is not a standard yet.

Additionally, different entities have different goals and boundary conditions (e.g., funding agencies focused on basic research without industry collaboration vs with industry collaboration, IP rights, strategic goals, etc.). Accordingly, not all recommendations will apply to everybody in the same way. The addressees have to adjust the recommendations according to their current situation. In the recommendations, we propose the what but only examples of the how. Addressees should best apply and incorporate our recommendations within their existing tooling and process landscape. We do not recommend introducing multiple new tools or processes if it does not seem necessary.

We designed the recommendations as stand-alone recommendations. Thereby, addressees can select individual recommendations to implement or start with. However, as indicated by the many interconnections of the recommendations, the full potential can only be lifted by the holistic improvement of all affected stakeholders. Furthermore, for some recommendations, we strongly recommend that corporate and research partners collaborate. The development of design support, in particular, as described in the fields of action 3 and 6, requires such a collaboration.

The corporate side finds it easier to use research results as reference system elements in their engineering activities in the early phases, or advance engineering instead of serial engineering. However, research results can also be valuable input for serial development, even though more rigorous boundary conditions and validation criteria might be in place. In the third recommendation, we propose a research results management system. Managing corporate knowledge is a highly relevant task in corporate practice, anyway. Thus, we recommend adding the used or potentially valuable research results and allocated knowledge and experience to the knowledge management system. Of course, such a management system has to deal with a heterogeneous composition of knowledge. Research results serving as reference system elements for process development differ from technical systems’ development (cf.³⁵). The first recommendation is to raise engineers’ awareness of the potential of reference system elements from research in a low-threshold manner. Therefore, companies should use their established intranet to inform the engineers about, for example, success stories. Of course, the concrete design of such “posts” is a non-trivial activity itself. The companies must fulfill different, partly opposing goals. There will be, most likely, two groups of readers. One is a probably relatively small group that is really interested in the solution and implementation of the research result and needs in-depth information. The second, probably quite a big group, is only meant to be informed about the success, needing a high-level post.

Of the recommendations addressing researchers and research facilities, the sounding board members heavily discussed recommendation 17 (developing a repository for research results beyond scientific publications). Many participants argued that many repositories for research results exist already. However, we decided to keep this recommendation. While repositories to share written research results (e.g., scientific papers) and raw data (e.g., measured or simulated data) within the communities exist, comparable repositories for other formats, such as digital models or physical demonstrators, are unknown to us.

Looking at recommendation 18 (requesting the expected benefits bundle in the proposal), the sounding board members criticized that it would not be possible to specify a benefits bundle during the proposal phase of research projects in all cases. The concern is that this recommendation would hinder the acceptance of qualitative proposals. In this recommendation, we recommend that funding agencies ask for the specification of the expected benefits bundle in the proposal. As indicated before, the concrete elaboration of this recommendation depends on the concrete situation. Thus, a benefits bundle specified in a proposal submitted to a funding agency focused on basic research without industry collaboration (as, e.g., in many DFG - German Research Foundation projects) will look totally different from the specified benefits bundle in a proposal for a research project submitted to a funding agency focused on collaborative industry-academia research projects (as, e.g., in many BMBF - German Federal Ministry of Education and Research funded research projects). However, we believe it is beneficial for the quality of all proposals if the applicants specify the potential benefit of their project. The research results do not always have to benefit corporate activities directly. However, they can form the basis for further research, too, still aiming for a benefit for engineering at some point. The last field of action (Researcher incentives - adjusting the success measurement of research projects) contains the recommendations discussed most controversial by the sounding board. KPIs allure to optimize according to these numbers losing sight of the overall quality/ situation. However, they offer an objective instrument to assess the performance of research facilities (e.g., research institutes, research groups, etc. – cf. Recommendation 21) or individuals (cf. Recommendation 22). Not all essential activities of research facilities (e.g., basic research) directly add to these KPIs. Thus, we stress that if KPIs are implemented, it is essential to use these numbers as additional guidance or steering instruments only. The main focus must remain on the research proposals’ overall quality and expected benefit.

Conclusion and outlook

In this contribution, we presented 22 recommendations to improve the usability of research results as reference system elements in corporate product engineering. Therefore, we formulated eight recommendations addressing corporate engineers and companies within three fields of action. Nine recommendations address researchers and research facilities clustered in three fields of action. Five recommendations address funding agencies and (research) policymakers within two fields of action. We have designed all of the recommendations to be individually applicable. This way, the addressees can select recommendations that best fit their current situation and goals. Thereby, we intend to lower the starting barrier. However, many recommendations are interconnected and do influence each other. Addressees must consider these relations when implementing more recommendations.

Furthermore, many recommendations do have links to recommendations of other target groups. Thus, collaboration is beneficial and recommended for these recommendations. Following the recommendations implies extra effort, at least in the development and introduction phase. However, we believe that the potential benefit of an easier integration of research results in corporate engineering activities and processes outweighs these efforts in the long run. To reduce the necessary effort, we recommend integrating our suggestions into already existing systems and tools (especially on the corporate side) rather than developing new ones. At the same time, this integration will likely increase the acceptance. While we believe all recommendations are precious and not sufficiently followed in the broad range of engineering companies, research facilities, and funding agencies, individual entities already fulfill some of our recommendations. Thus, each addressee must decide on the recommendations most valuable for them in their specific situation and boundary conditions.

Due to the design of our study, we have confidence in the validity of our recommendations. We collected measures from 43 experts involved in industry-academia collaboration projects to overcome the challenges of using research results as reference system elements in corporate product engineering. These participants covered all three of our target groups. We then condensed these measures to 24 recommendations. We improved and validated these recommendations using a sounding board approach in two iterations. For the first round, we invited 17 selected experts in design research, and for the second round, we invited 20 selected experts representing all three target groups of the recommendations. As a result, we designed the final set of 22 recommendations.

Although we believe in the soundness of our methodological approach, it is important to recognize the limitations of this study. Firstly, we can only consider the validation as initial, as we only validated the content of the recommendations. We did not explicitly validate or test their applicability beyond relying on the experts’ and our own expertise. Secondly, our study only included experts from German communities. The research and engineering culture in other regions is quite different. Thus, it is impossible to generalize about the global interaction of the three target groups. However, we believe the situation in Germany is somewhat representative, and our results can also be applied to other regions.

Following our recommendations can improve the usability of research results as reference system elements in corporate product engineering activities and processes. This, in turn, supports the technical advancement of technical systems and products and the efficiency of engineering processes by improving the transfer of knowledge and technologies from research to companies, reducing the gap between them. Closing this gap is essential for facing challenges such as climate change, energy usage, and demographic shifts, as well as preserving or even increasing the prosperity of our societies.

Based on the results presented in this contribution, we will continue our research by developing implementation strategies for the recommendations. Furthermore, we will research and develop the suggested design supports as described in the recommendations (cf. Field of action 3 and 6).

Footnotes

Acknowledgements

The research documented in this manuscript/presentation has been funded by the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation), project number 255730231, within the International Research Training Group “Integrated engineering of continuous-discontinuous long fiber reinforced polymer structures” (GRK 2078). The support by the German Research Foundation (DFG) is gratefully acknowledged.

Declaration of conflicting interests

The author(s) declared no potential conflicts of interest with respect to the research, authorship, and/or publication of this article.

Funding

The author(s) disclosed receipt of the following financial support for the research, authorship, and/or publication of this article: This work was supported by the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation), project number 255730231.

ORCID iDs

Christoph Kempf

Katharina Ritzer

Michael Schlegel

Albert Albers

References

Clark

. Nvidia says growth will continue as A.I. Hits ‘Tipping Point’, 2024. https://www.nytimes.com/2024/02/21/technology/nvidia-earnings.html (accessed 23 February 2024).

Fraunhofer-Gesellschaft . ZEISS, TRUMPF and Fraunhofer research team awarded the Deutscher Zukunftspreis 2020 for the development of EUV lithography. https://www.fraunhofer.de/en/press/research-news/2020/november/zeiss-tumpf-and-fraunhofer-research-team-awarded-the-deutscher-zukunftspreis-2020-for-the-development-of-euv-litography.html (2023), accessed 19 April 2023.

Buchenau

. Zukunftspreis geht an Entwickler von Fertigungstechnik für Mikrochips. https://www.handelsblatt.com/technik/forschung-innovation/euv-lithografie-entwickler-von-zeiss-trumpf-und-fraunhofer-erhalten-deutschen-zukunftspreis/26659346.html (2020), accessed 24 April 2023.

Bora

. The Boston Dynamics Story - TechStory: the complete story of the company that has redefined what robots can do. https://techstory.in/the-boston-dynamics-story/ (2018), accessed 19 October 2022.

Boston Dynamics . Boston Dynamics | changing your idea of what robots can do. https://www.bostondynamics.com/ (2022), accessed 19 October 2022.

International, sri . Siri. https://www.sri.com/hoi/siri/ (2021, accessed 15 November 2022).

Giffin

. The Creator of Siri: “Make your prototype magic”. https://scet.berkeley.edu/the-creator-of-siri/ (2021), accessed 15 November 2022.

German Federal Ministry of Education and Research . Bundesregierung nominiert 7 leuchtturmprojekte elektromobilität: pressemitteilung: 083/2015, 2015. https://nachrichten.idw-online.de/2015/06/15/bundesregierung-nominiert-7-leuchtturmprojekte-elektromobilitaet

Link

Baumgärtner

Dörr

, et al. Hybrid thermoplastic composites for automotive applications—development and manufacture of a lightweight rear floor structure in multi-material design. In: ECCM18 - 18th European Conference on Composite Materials, Athens, Greece, 25-28 June 2018, pp. 1–8.

10.

Kärger

. SMiLE - system-integrative multi-material lightweight construction for electromobility. https://www.fast.kit.edu/english/lbt/4590_7737.php (2017), accessed 11 November 2024.

11.

Malnati

. Hybrid thermoplastics give load floor impact strength: project leads to development of new compression process for selective application of D-LFT on UD tape laminates. Composites World 2018: 44–47. https://www.compositesworld.com/blog/post/multi-material-thermoplastics-give-load-floor-impact-strength (accessed 11 November 2024).

12.

Frank

Meyer-Guckel

Schneider

. Innovationsfaktor Kooperation: Bericht des Stifterverbandes zur Zusammenarbeit zwischen Unternehmen und Hochschulen, 2007. https://www.stifterverband.de/pdf/innovationsfaktor_kooperation.pdf.

13.

Kempf

Schlegel

Rapp

, et al. Reasons and triggers using research results in corporate product engineering. International Journal of Innovation Management. 2023; 27: 1–16. DOI: 10.1142/S1363919623400054.

14.

Bauernhansl

Nestler

. Expertenkommission ingenieurwissenschaften@ BW2025: abschlussbericht, 2015. https://mwk.baden-wuerttemberg.de/fileadmin/redaktion/mmwk/intern/dateien/Anlagen_PM/2015/132_PM_Anlage_Abschlussbericht_Expertenkommission_Ingenieurwissenschaften@BW2025_.pdf.

15.

Kleiner-Schaefer

Schaefer

. Barriers to university–industry collaboration in an emerging market: firm-level evidence from Turkey. J Technol Tran 2022; 47: 872–905. DOI: 10.1007/s10961-022-09919-z.

16.

Kempf

Thapak

Rapp

, et al. Challenges in reference system management – descriptive model of barriers using research results as reference system elements in corporate product engineering. Procedia CIRP 2023; 119: 384–389. DOI: 10.1016/j.procir.2023.01.005.

17.

Albers

Kürten

Rapp

, et al. SGE – Systemgenerationsentwicklung: Analyse und Zusammenhänge von Entwicklungspfaden in der Produktentstehung. KIT Scientific Working Papers. 2022; 199. DOI: 10.5445/IR/1000151151.

18.

Albers

Rapp

. Model of SGE: system generation engineering as basis for structured planning and management of development. In: Krause

Heyden

(eds). Design Methodology for Future Products: Data Driven, Agile and Flexible. 1 ed. Cham: Springer, 2022, pp. 27–46. DOI: 10.1007/978-3-030-78368-6_2.

19.

Albers

Bursac

Wintergerst

. Product generation development – importance and challenges from a design research perspective. In: Proceedings of the International Conference on Mechanical Engineering (ME 2015): New Developments in Mechanics and Mechanical Engineering , Vienna, Austria, 15-17 March 2015, pp. 16–21.

20.

Albers

Rapp

Spadinger

, et al. The reference system in the model of PGE: proposing a generalized description of reference products and their interrelations. In Proceedings of the 22nd International Conference on Engineering Design (ICED19), Delft, The Netherlands, 5-8 August 2019, pp. 1693–1702. DOI: 10.1017/dsi.2019.175.

21.

Ehrlenspiel

. Integrierte produktentwicklung. München: Carl Hanser Verlag GmbH & Co. KG, 2009.

22.

Feldhusen

Grote

K-H

(eds). Pahl/Beitz Konstruktionslehre: Methoden und Anwendung erfolgreicher Produktentwicklung. 8., vollst. überarb. Aufl. Berlin/Heidelberg: Springer-Verlag, 2013.

23.

Iyer

Jayanti

Lou

, et al. Three-dimensional shape searching: state-of-the-art review and future trends. Comput Aided Des 2005; 37: 509–530. DOI: 10.1016/j.cad.2004.07.002.

24.

Deubzer

Lindemann

. Networked product modeling – use and interaction of product models and methods during analysis and synthesis. In: Proceedings of ICED 09, Palo Alto, CA, USA, 24-27.08.2009, pp. 371–380.

25.

Eckert

Alink

Albers

. Issue driven analysis of an existing product at different levels of abstraction. In: Marjanović

Štorga

Pavković

, et al. (eds). Proceedings of DESIGN 2010. Dubrovnik, Croatia. Zagreb: University of Zagreb, 2010, pp. 673–682.

26.

Eckert

Clarkson

Zanker

. Change and customisation in complex engineering domains. Res Eng Des 2004; 15: 1–21. DOI: 10.1007/s00163-003-0031-7.

27.

Sivaloganathan

Shahin

TMM

. Design reuse: an overview. Proc IME B J Eng Manufact 1999; 213: 641–654. DOI: 10.1243/0954405991517092.

28.

Alblas

Jayaram

. Design resilience in the fuzzy front end (FFE) context: an empirical examination. Int J Prod Res 2015; 53: 6820–6838. DOI: 10.1080/00207543.2014.899718.

29.

Duffy

AHB

MacCallum

. A design reuse model. In: Proceedings of the 10th International Conference on Engineering Design (ICED 95), Prague, Czech Republic, 22-24.08.1995, pp. 490–495.

30.

King

Sivaloganathan

. Flexible design: a strategy for design reuse. In: Sivaloganathan

Shahin

TMM

(eds). Proceedings of Engineering Design Conference 98 on Design Reuse. London, UK: Professional Engineering Publishing Limited, 1998.

31.

Maher

Gomez de Silva Garza

. Case-based reasoning in design. IEEE Expert 1997; 12: 34–41. DOI: 10.1109/64.585102.

32.

Hatchuel

Weil

. A new approach of innovative design: an introduction to CK theory. In: Folkeson

Gralén

Norell

, et al. (eds). Proceedings of ICED 03: the 14th International Conference on Engineering Design. Stockholm, Sweden: The Design Society, 2003, pp. 109–124.

33.

Agogué

Kazakçi

. 10 Years of C–K theory: a survey on the academic and industrial impacts of a design theory. In: Chakrabarti

Blessing

(eds). An Anthology of Theories and Models of Design: Philosophy, Approaches and Empirical Explorations. London: Springer, 2014, pp. 219–235. DOI: 10.1007/978-1-4471-6338-1_11.

34.

Ropohl

(ed). Systemtechnik: Grundlagen und Anwendung. München: Carl Hanser Verlag, 1975.

35.

Albers

Kempf

Haberkern

, et al. The reference system in product generation engineering: structuring reference system elements for advanced systems engineering based on the system triple. Des Sci 2024; 10: e35. DOI: 10.1017/dsj.2024.41.

36.

Kempf

Sanke

Heimicke

, et al. Identifying factors influencing the design of a suitable knowledge base in product engineering projects. Proc Des Soc 2022; 2: 733–742. DOI: 10.1017/pds.2022.75.

37.

Shahin

TMM

Andrews

PTJ

Sivaloganathan

. A design reuse system. Proc IME B J Eng Manufact 1999; 213: 621–627. DOI: 10.1243/0954405991517065.

38.

Ahmed

Wallace

Blessing

. Understanding the differences between how novice and experienced designers approach design tasks. Res Eng Des 2003; 14: 1–11. DOI: 10.1007/s00163-002-0023-z.

39.

Hajialibeigi

. Is more diverse always the better? External knowledge source clusters and innovation performance in Germany. Econ Innovat N Technol 2021; 32: 663–681. DOI: 10.1080/10438599.2021.2007093.

40.

Kempf

Rapp

Behdinan

, et al. Reference System Element Identification Atlas – methods and tools to identify references system elements in product engineering. World Patent Inf 2023; 75: 102239. https://www.sciencedirect.com/science/article/pii/S0172219023000698

41.

Guerrero

Urbano

Herrera

. Innovation practices in emerging economies: do university partnerships matter? J Technol Tran 2019; 44: 615–646. https://link.springer.com/article/10.1007/s10961-017-9578-8

42.

Expertenkommission Forschung und Innovation . Report on research, innovation and technological performance in Germany 2022. Berlin: EFI, 2022.

43.

Kempf

Rapp

Albers

. Potentials and needs of research references in corporate product engineering. ISPIM connects athens - the role of innovation: past, present, future. Athens: November: LUT Scientific and Expertise Publications, pp. 28–30.

44.

Bruneel

D’Este

Salter

. Investigating the factors that diminish the barriers to university–industry collaboration. Res Pol 2010; 39: 858–868. DOI: 10.1016/j.respol.2010.03.006.

45.

Brown

Isaacs

. The world café: shaping our futures through conversations that matter. San Francisco, Calif: BK Berrett-Koehler Publishers, 2005.

46.

Tan

Brown

. The world café in Singapore. J Appl Behav Sci 2005; 41: 83–90. DOI: 10.1177/0021886304272851.

47.

Dittrich-Brauner

Dittmann

List

, et al. Interaktive großgruppen. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013.

48.

Walter

Albers

Schelleis

, et al. Efficient use of sounding board method at project milestones and its potentials for virtualization. Procedia CIRP 2017; 60: 284–289. DOI: 10.1016/j.procir.2017.02.004.

49.

Molz

. Evaluation und Weiterentwicklung von Empfehlungen, um die Nutzbarkeit von Forschungsergebnissen als Referenzsystemelemente in Unternehmen zu verbessern. Master Thesis. Karlsruhe: Karlsruher Institute of Technology (KIT), 2024.

50.

Kempf

Molz

. Videos of recommendations to improve the usability of research results as reference system elements in corporate product engineering addressing corporate engineers, researchers, and policymakers. Figshare. 2024. DOI: 10.6084/m9.figshare.25498255.v1.

51.

Mankins

. Technology readiness levels: a white paper. Washington, DC: NASA, 1995.

52.

Mankins

. Technology readiness assessments: a retrospective. Acta Astronaut 2009; 65: 1216–1223. DOI: 10.1016/j.actaastro.2009.03.058.

53.

Blessing

Chakrabarti

. DRM, a design research methodology. London: Springer London, 2009.

54.

Albers

. Five hypotheses about engineering processes and their consequences. Proceedings of the 8th International Symposium on Tools and Methods of Competitive Engineering, TMCE 2010. TMCE, 2010, pp. 343–356.

Recommendations to improve the usability of research results as reference system elements addressing corporate engineers,researchers,and policymakers

Abstract

Keywords

Introduction (background and motivation)

Reuse of knowledge, technologies, and other (sub-)systems in product engineering

The reference system within the model of SGE – System Generation Engineering

Research results as reference system elements

Research profile – aims and methodology

Research aim and research questions

Research approach

Measures to overcome the challenges and barriers to using research results as reference system elements in corporate product engineering

Recommendations to improve the usability of research results as reference system elements

Recommendations for corporate product engineers/companies

Field of action 1: Corporate organization and structure - encouraging the usage of research results as reference system elements

Recommendation 1: Raising the awareness of engineers for the potential of research results as reference system elements

Recommendation 2: Encouraging engineers to search for research results as reference system elements

Recommendation 3: Managing research results as reference system elements

Field of action 2: Knowledge and technology transfer - first steps after the identification of research results as reference system elements

Recommendation 4: Translating the research language to corporate language

Recommendation 5: Assessing the maturity of the research results as well as risks using it as reference system elements

Field of action 3: Design support - supporting corporate engineers in the integration of research results as reference system elements in their engineering activities

Recommendation 6: Designing the reference system with conscious and explicit consideration of research as a valuable source

Recommendation 7: Identifying situations/engineering activities that benefit from research results as reference system elements

Recommendation 8: Proposing potentially suitable research results as reference system elements during engineering activities

Recommendations for researchers/research facilities

Field of action 4: Research organization - promoting research results and supporting the transfer

Recommendation 9: Increasing the proficiency in the communication of research results

Recommendation 10: Supporting the transfer and accessibility of research results

Field of action 5: Researchers - adjusting research results to the customers (corporate engineers)

Recommendation 11: Including the benefits bundle in publications

Recommendation 12: Using new communication and presentation formats for research results

Recommendation 13: Communicating additional information - success stories, best practices, learnings from failures

Field of action 6: Design research - developing design supports for using research results as reference system elements in corporate product engineering

Recommendation 14: Developing design support for identifying situations/engineering activities that benefit from research results as reference system elements

Recommendation 15: Developing search tools for screening research activities and results (beyond paper databases)

Recommendation 16: Developing design support for the systematic consideration of research results in the synthesis of reference systems

Recommendation 17: Developing a repository for research results beyond scientific publications

Recommendations for funding agencies/(research) policymakers

Field of action 7: Engineering relevance and dissemination - meeting the needs of the industry

Recommendation 18: Requesting the expected benefits bundle in the proposal

Recommendation 19: Funding and requesting demonstrators and transfer activities beyond scientific exchange

Recommendation 20: Introducing regular thematic exchanges beyond project consortia

Field of action 8: Researcher incentives - adjusting the success measurement of research projects

Recommendation 21: Introducing transfer KPIs on the research facility level

Recommendation 22: Introducing transfer KPIs on the researcher level

Discussion

Conclusion and outlook

Footnotes

Acknowledgements

Declaration of conflicting interests

Funding

ORCID iDs

References