• No results found

Requirements for REES design support : a survey among large companies and SMEs

N/A
N/A
Protected

Academic year: 2021

Share "Requirements for REES design support : a survey among large companies and SMEs"

Copied!
16
0
0

Loading.... (view fulltext now)

Full text

(1)

Requirements for REES design

support

– A survey among large companies and SMEs

Authors: Sergio A. Brambila-Macias, Tomohiko Sakao, Mattias Lindahl

Department: Division of Environmental Technology and Management, Department of Engineering and Management, Linköping University

Submission data: 6th of June 2018

Report Number: LIU-IEI-RR--18/00304—SE

Contact person: Tomohiko Sakao (tomohiko.sakao@liu.se), Project Manager

(2)

Acknowledgment

This research was supported by the Mistra REES (Resource Efficient and Effective Solutions) program, funded by Mistra (The Swedish Foundation for Strategic Environmental Research) (grant number DIA 2014/16). Sara Nilsson and Maria Widgren of Linköping University supported the work.

(3)

3

Table of Contents

Acknowledgment 2 1 Introduction ... 4 2 Results ... 6 2.1 Consolidated data ... 6

2.2 Comparison between large companies and SMEs ... 8

3 References ... 13

(4)

4

1 Introduction

This report presents the results of a survey carried out during 2017-2018 among 11 different companies as part of the REES1 programme (www.mistrarees.se) work package (WP) 2.2 of Project 2 (the project concerning design in the programme). The objective of the survey was to identify the most important requirements for design support that is being developed for REES designers in the manufacturing industry. The survey comprises results from a total of 25 participants from 5 SMEs and 6 large companies, which included 8 participants from SMEs and 17 from large companies. This classification was made according to the EU commission (2015) definition of SMEs (< 250 employees and ≤ EUR 50 million in annual turnover). The results presented are divided into Section 1 where an overview of the survey and the method is presented and section 2 results, where consolidated data and comparison between large companies and SMES is provided.

The adopted method was a web-based survey, where a respondent was asked to give importance ratings between pre-defined requirements for REES design support. A six level Likert scale was used (0 – not important at all, 5 – extremely important). During WP 2.2 of the project, relevant information was gathered from a literature review and 24 interviews with practitioners. That information served to identify 20 relevant requirements for REES design support. The literature review results and the interview results were published as REES reports; “State of the Art of Design Methods for Resource Efficient and Effective Solutions” (2017) and “Support for Designing Resource Efficient and Effective Solutions: Current Use and Requirements by Swedish Industry” (2017), respectively. These requirements are divided into: Outcome, Process, Content, Time and cost, and Users and detailed below.

Outcome

1. Useful in early design phase: Valuable outcome is derived before substantial resources of materials and personnel are allocated to activities.

2. Provide quantified results: providing results in a numerical manner.

3. Support visualisation of results: providing results in a graphical or pictorial manner.

4. Support managing risks of the offering: assessing, evaluating, and mitigating potential risks of the offering (product and/or service) since early design phase.

Process

5. Support standardising design processes: Guide users to follow an expected process. 6. Support prioritization of improvement areas in design: Prioritize items or tasks in design. 7. Support documentation: Document results and data used in the designing activity.

8. Support communication across relevant actors: Clear, concise and relevant information to be communicated across relevant actors.

9. Support collaboration across relevant actors: Collaboration here means creating valuable information together for a common solution beyond one actor’s own limited vision and control and may involve sharing resources of the actors.

Content

10. Support lifecycle thinking: The lifecycle consists of acquisition of raw materials from natural resources, production, logistics, use, service and final disposal of the product.

11. Support compliance with stakeholder requirements: List, prioritize and, if needed, solve conflicting stakeholder requirements.

12. Support articulation of stakeholder values: Take into account what all relevant stakeholders value most in the offering.

Time and cost

13. Reduce calendar time of activity from start to stop: Reducing calendar time of design activity.

(5)

5 14. Reduce total number of working hours for activity: Reducing working hours of design activity. 15. Low cost of usage: Low cost of implementing and using the support for design activity. Users

16. Easy to learn: The support does not require specialized or in-depth knowledge. 17. Easy to use: The support is self-guiding, logic and error proof.

18. Support designers’ creativity: Support creation and deployment of new ideas. 19. Provide learning opportunity: Guide users for enhancing their knowledge.

20. Support management of multiple projects: Manage each of parallel projects, including different activities and processes as well as responsible persons for them.

(6)

6

2 Results

The results presented provide a guide into what are deemed as more relevant for REES design support. Section 2.1 presents overall results for all 25 participants from both large companies and SMEs. Section 2.2 shows main differences between large companies and SMEs.

2.1 Consolidated data

Figure 1 shows the current job position of the 25 participants, while Figure 2 shows the job functions as percentage.

Figure 1 Participants’ current job positions

(7)

7 Figure 4 shows the general importance for each of the requirements. Those above the average red line of 3.5 in the figure are summarised in Table 1.

Figure 3 Large and SMEs results for 20 relevant requirements in design support Table 1 The highest ranked requirements for REES design support

Category Requirement Importance (mean) Users Easy to use 4.38

Users Support designers’ creativity 4.20

Users Easy to learn 4.17

Content Support lifecycle thinking 4.04

Process Support communication across relevant actors 3.83

Outcome Useful in early design phase 3.82

Process Support prioritization of improvement areas in design 3.67

Time and cost Low cost of usage 3.58

Process Support collaboration across relevant actors 3.56

A statistical analysis for the standard deviation among the answers for each requirement showed that participants agreed mostly in only 6 of these with a standard deviation of <1. This is presented below in Table 2 from least to highest standard deviation.

0.00 0.50 1.00 1.50 2.00 2.50 3.00 3.50 4.00 4.50 Useful in early design phase

Provide quantified results Support visualisation of results Support managing risks of the offering Support standardising design processes Support prioritization of improvement areas in design Support documentation Support communication across relevant actors Support collaboration across relevant actors Support lifecycle thinking Support compliance to stakeholder requirements Support articulation of stakeholder values Reduce calendar time of activity from start to stop Reduce total number of working hours for activity Low cost of usage Easy to learn Easy to use Support designers’ creativity Provide learning opportunity Support management of multiple projects

O ut co m e P ro ce ss C o nt ent Ti m e a nd co st Us er s Likert scale 0 - not important at all 5 - extremely important 20 m o st im po rt an t r equ ir em ent s

(8)

8 Table 2 Results for the most agreed requirements for design support

Category Requirement Average value Standard deviation Content Support lifecycle thinking 4.04 0.79

Users Easy to use 4.38 0.82

Users Support designers’ creativity 4.20 0.87

Process Support prioritization of improvement areas in design 3.67 0.87

Process Support communication across relevant actors 3.83 0.96

Users Easy to learn 4.17 0.96

2.2 Comparison between large companies and SMEs

The same analysis carried out above was done in this section to check if there were any differences between large companies and SMEs. Figure 4 shows how the different factors where evaluated according to a Likert scale. The red line shows the average number for the answers which is 3.60.

(9)

9 The table below shows the highest values for the factors that large companies consider most important.

Table 3 Results for the highest ranked requirements for design support according to large companies

Category Requirement Average value Users Easy to use 4.41

Users Support designers’ creativity 4.29

Outcome Useful in early design phase 4.20

Users Easy to learn 4.12

Content Support lifecycle thinking 4.06

Process Support communication across relevant actors 3.94

Process Support collaboration across relevant actors 3.94

Process Support prioritization of improvement areas in design 3.88

As in the analysis made in section 2.1, a statistical analysis was carried out to see how much participants agreed in each sub-factor according to a standard deviation of <1.

Table 4 Results for the most agreed requirements for design support among large companies

Category Requirement Average value Standard deviation Content Support lifecycle thinking 4.06 0.66

Outcome Useful in early design phase 4.20 0.68

Process Support prioritization of improvement areas in design 3.88 0.70

Users Easy to use 4.41 0.71

Users Support designers’ creativity 4.29 0.77

Users Easy to learn 4.12 0.93

Process Support communication across relevant actors 3.94 0.97

For SMEs the results show that other factors are considered most relevant. Figure 5 shows the results for SMEs, the red line is the average response which was 3.27.

(10)

10 Figure 5 SMEs' results among 20 requirements for design support

The table below shows the highest values for the factors that SMEs consider most important. Table 5 Results for the highest ranked factors for design support according to

SMEs

Category Requirement Average value Users Easy to learn 4.29

Users Easy to use 4.29

Content Support lifecycle thinking 4.00

Users Support designers’ creativity 4.00

Process Support communication across relevant actors 3.57

Time and cost Low cost of usage 3.43

Users Provide learning opportunity 3.43

Users Support management of multiple projects 3.38

(11)

11 The statistical analysis carried out to see how much participants agreed in each sub-factor is shown below.

Table 6 Results for the most agreed factors for design support among SMEs

Category Requirement Average value Standard deviation Outcome Provide quantified results 3.29 0.76

Process Support standardising design processes 3.00 0.82

Process Support communication across relevant actors 3.57 0.98

The table below shows the relative importance of requirements showing the difference between large companies and SMEs.

Table 7 Relative importance of requirements between large companies and SMEs

Category Requirement Relative importance of larges/SMEs Outcome Useful in early design phase 1.40

Provide quantified results 0.95 Support visualisation of results 1.11 Support managing risks of the offering 1.36

Process Support standardising design processes 1.00 Support prioritization of improvement areas in design 1.24 Support documentation 1.04 Support communication across relevant actors 1.10 Support collaboration across relevant actors 1.43

Content Support lifecycle thinking 1.01 Support compliance to stakeholder requirements 1.14 Support articulation of stakeholder values 1.17

Time and cost Reduce calendar time of activity from start to stop 1.26 Reduce total number of working hours for activity 1.33

Low cost of usage 1.06

Users Easy to learn 0.96

Easy to use 1.03

Support designers’ creativity 1.07 Provide learning opportunity 0.91 Support management of multiple projects 1.00

(12)

12 Figure 6 Difference in requirements between large companies and SMEs

(13)

13

3 References

Brambila-Macias, S. A., Nilsson, S., Widgren, M., Lindahl, M., & Sakao, T. (2017). State of the Art of Design

Methods for Resource Efficient and Effective Solutions, Report from “Product and Service Design Methods for REES” Project of Mistra REES program. Linköping: Linköping University,

LIU-IEI-RR--17/00264—SE.

Brambila-Macias, S. A., Nilsson, S., Widgren, M., Lindahl, M., & Sakao, T. (2017). Support for Designing

Resource Efficient and Effective Solutions: Current Use and Requirements by Swedish Industry.

Linköping: Linköping University, LIU-IEI-RR--17/00281—SE.

European Commission. (2015). The Revised User Guide to the SME Definition 2015. Retrieved from

(14)

14

4 Appendix

(15)
(16)

References

Related documents

The variations in these parameters increase the problem complexity regarding the appropriate time for cost-effective replacement of grinding mill liners of ore dressing plants

In the present case, plastic will be used in the back case, stylus, foot, battery cover and protection case, and glass in the front case.. Regarding housings design,

The aim of this thesis is to develop a technique for image searching in historical handwritten document images, based on image processing techniques in addition with machine

In the following, a discussion is performed on the applicability of the partial factor method and reliability-based methods for design of shotcrete support, quantifying and

1) The Discrimination Act (2008:567).. CERTIFICATES AND PLANNING Students who have been diagnosed with disability can apply for educational support. One prerequisite for

By automating many manual process and having a user friendly support for the remaining processes we can free time for all user roles and make the end-result more correct and

interface, the analysts should have similar design opportunities. The, by the analyst designed, interface should contain summarized information from both internal and external

LayOM is a language model that provides explicit support for modelling constructs used during object-oriented design, such as design patterns, but also relations between objects