The development of decision limits for the GH-2000 detection methodology using additional insulin-like growth factor-I and amino-terminal pro-peptide of type III collagen assays.

The GH-2000 and GH-2004 projects have developed a method for detecting GH misuse based on measuring insulin-like growth factor-I (IGF-I) and the amino-terminal pro-peptide of type III collagen (P-III-NP). The objectives were to analyze more samples from elite athletes to improve the reliability of the decision limit estimates, to evaluate whether the existing decision limits needed revision, and to validate further non-radioisotopic assays for these markers. The study included 998 male and 931 female elite athletes. Blood samples were collected according to World Anti-Doping Agency (WADA) guidelines at various sporting events including the 2011 International Association of Athletics Federations (IAAF) World Athletics Championships in Daegu, South Korea. IGF-I was measured by the Immunotech A15729 IGF-I IRMA, the Immunodiagnostic Systems iSYS IGF-I assay and a recently developed mass spectrometry (LC-MS/MS) method. P-III-NP was measured by the Cisbio RIA-gnost P-III-P, Orion UniQ? PIIINP RIA and Siemens ADVIA Centaur P-III-NP assays. The GH-2000 score decision limits were developed using existing statistical techniques. Decision limits were determined using a specificity of 99.99% and an allowance for uncertainty because of the finite sample size. The revised Immunotech IGF-I - Orion P-III-NP assay combination decision limit did not change significantly following the addition of the new samples. The new decision limits are applied to currently available non-radioisotopic assays to measure IGF-I and P-III-NP in elite athletes, which should allow wider flexibility to implement the GH-2000 marker test for GH misuse while providing some resilience against manufacturer withdrawal or change of assays. Copyright © 2015 John Wiley & Sons, Ltd.

Maintenance process development for remote administration of network servers

Maintenance is a part of system development and it is possible to develop operation models for accomplishing maintenance tasks. These models can be applied to individual maintenance tasks, maintenance projects and version management. Beneficial operation models makes maintenance more effective and they assist in managing various changes. The purpose of this thesis was to develop a maintenance process which can be used to remote administer network servers. This consisted of defining those operation models and technical specifications which enable to set up, manage changes, maintain and monitor resources of information systems that are located in several different sites. At first in this thesis the needs of the process were determined and requirements were defined based on those needs. The meaning of processes in maintenance of information systems, maintenance workflows and challenges were studied. Then current practical problems and disadvantages of maintenance work were analyzed in order to focus the development to proper issues. Because available operation models did not cover all the recent needs, new maintenance process which fulfilled the requirements was developed.

Sähkösuunnittelun projektityön hallinta ja kehittäminen - Management and development of project work in electrical

Työssä on tutkittu sähkösuunnittelun projektityön hallintaa ja kehittämistä. Tavoitteena oli löytää ongelmia ja pyrkiä korjaamaan niitä, jotta suunnittelu olisi mahdollisimman toimivaa. Tutkimus perustuu kirjallisuuteen ja haastatteluihin. Työssä perehdytään kirjallisuuden avulla projektin peruskäsitteisiin ja hallintaan sekä sähkösuunnittelun projektin yleiseen toteutukseen. Haastattelujen avulla on selvitetty tämän hetkistä tilannetta sähkösuunnitteluprojektin hallinnasta ja siihen liittyvistä ongelmista Pöyryn Kouvolan konttorissa. Työn tuloksena on selvitetty merkittävimpiä ongelmia, jotka esiintyvät sähkösuunnitteluprojektissa. Työ keskittyy pääosin sähkösuunnitteluprojektin hallinnallisiin ongelmiin ja niiden toteutukseen. Kirjallisuuden ja haastattelujen pohjalta on koottu ohjeita sähkösuunnittelun projektinhallintaan

Implementing Agile Software Development Methods in a Small Organization

Currently there is a vogue for Agile Software Development methods and many software development organizations have already implemented or they are planning to implement agile methods. Objective of this thesis is to define how agile software development methods are implemented in a small organization. Agile methods covered in this thesis are Scrum and XP. From both methods the key practices are analysed and compared to waterfall method. This thesis also defines implementation strategy and actions how agile methods are implemented in a small organization. In practice organization must prepare well and all needed meters are defined before the implementation starts. In this work three different sample projects are introduced where agile methods were implemented. Experiences from these projects were encouraging although sample set of projects were too small to get trustworthy results.

Development of Collaborative Product Structure Management

The purpose of this thesis is to develop an environment or network that enables effective collaborative product structure management among stakeholders in each unit, throughout the entire product lifecycle and product data management. This thesis uses framework models as an approach to the problem. Framework model methods for development of collaborative product structure management are proposed in this study, there are three unique models depicted to support collaborative product structure management: organization model, process model and product model. In the organization model, the formation of product data management system (eDSTAT) key user network is specified. In the process model, development is based on the case company’s product development matrix. In the product model framework, product model management, product knowledge management and design knowledge management are defined as development tools and collaboration is based on web-based product structure management. Collaborative management is executed using all these approaches. A case study from an actual project at the case company is presented as an implementation; this is to verify the models’ applicability. A computer assisted design tool and the web-based product structure manager, have been used as tools of this collaboration with the support of the key user. The current PDM system, eDSTAT, is used as a piloting case for key user role. The result of this development is that the role of key user as a collaboration channel is defined and established. The key user is able to provide one on one support for the elevator projects. Also the management activities are improved through the application of process workflow by following criteria for each project milestone. The development shows effectiveness of product structure management in product lifecycle, improved production process by eliminating barriers (e.g. improvement of two-way communication) during design phase and production phase. The key user role is applicable on a global scale in the company.

Worker motivation in crowdsourcing new product development

In the study the recently appeared technology of crowdsourcing and its implications to new product development activities. The goal of the research is to figure out the motivating factors used in crowdsourcing projects related to new product development. The study is based on the theoretical backgrounds of crowdsourcing; new product development, and motivation, which resulted in the framework for the crowdsourcing cases assessment and the list of possible motivating factors used for the analysis. The research is based on 16 crowdsourcing projects divided in 4 sets according to the stage of new product development at which they are directed. The motivating factors present in the projects were distinguished and explained. Further analysis allowed making conclusions showing which of the motivating factors are suitable for the crowdsourcing projects related to the particular stage of new product development. The results can be used for creation or assessment of crowdsourcing projects for the companies because the main factor of success for crowdsourcing is motivation, and the work is answering how to motivate the workers.

Development of a project control procedure

The aim of this study is to develop a suitable project control procedure for a target company that can be used in engineering, procurement, and construction or con-struction management contracts. This procedure contains suitable project control software and a model for the use of the software in practice. This study is divided into two main sections. Theoretical part deals with project management, focusing on cost and time dimensions in projects. Empirical part deals with the development of the project control procedure for the target compa-ny. This development takes place in two parts. In the first part, semi-structured interviews are used to find out the company’s employees’ demands and desires for the project control software which will then be used in the developed procedure. These demands and desires are compared to available software in the market and the most suitable one will be chosen. Interview results show that important factors are cost tracking, integration with other software, English language availability, references, helpdesk, and no need for regular updates. The most suitable one is CMPro5 cost control software. The chosen software is used in a pilot project, where its functions and use are analyzed. Project control procedure which will be used in the future is developed based on these procedures. The five steps in developed procedure include employment of a cost engineer, whose task is to maintain the procedure in the target company.

Integration in project business : mechanisms for integrating customers and the project network during the life-cycle of industrial projects

This thesis focuses on integration in project business, i.e. how projectbased companies organize their product and process structures when they deliver industrial solutions to their customers. The customers that invest in these solutions run their businesses in different geographical, political and economical environments, which should be acknowledged by the supplier when providing solutions comprising of larger and more complex scopes than previously supplied to these customers. This means that the suppliers are increasing their supply range by taking over some of the activities in the value chain that have traditionally been handled by the customer. In order to be able to provide the functioning solutions, including more engineering hours, technical equipment and a wider project network, a change is needed in the mindset in order to be able to carry out and take the required responsibility that these new approaches bring. For the supplier it is important to be able to integrate technical products, systems and services, but the supplier also needs to have the capabilities to integrate the cross-functional organizations and departments in the project network, the knowledge and information between and within these organizations and departments, along with inputs from the customer into the product and process structures during the lifecycle of the project under development. Hence, the main objective of this thesis is to explore the challenges of integration that industrial projects meet, and based on that, to suggest a concept of how to manage integration in project business by making use of integration mechanisms. Integration is considered the essential process for accomplishing an industrial project, whereas the accomplishment of the industrial project is considered to be the result of the integration. The thesis consists of an extended summary and four papers, that are based on three studies in which integration mechanisms for value creation in industrial project networks and the management of integration in project business have been explored. The research is based on an inductive approach where in particular the design, commissioning and operations functions of industrial projects have been studied, addressing entire project life-cycles. The studies have been conducted in the shipbuilding and power generation industries where the scopes of supply consist of stand-alone equipment, equipment and engineering, and turnkey solutions. These industrial solutions include demanding efforts in engineering and organization. Addressing the calls for more studies on the evolving value chains of integrated solutions, mechanisms for inter- and intra-organizational integration and subsequent value creation in project networks have been explored. The research results in thirteen integration mechanisms and a typology for integration is proposed. Managing integration consists of integrating the project network (the supplier and the sub-suppliers) and the customer (the customer’s business purpose, operations environment and the end-user) into the project by making use of integration mechanisms. The findings bring new insight into research on industrial project business by proposing integration of technology and engineering related elements with elements related to customer oriented business performance in contemporary project environments. Thirteen mechanisms for combining products and the processes needed to deliver projects are described and categorized according to the impact that they have on the management of knowledge and information. These mechanisms directly relate to the performance of the supplier, and consequently to the functioning of the solution that the project provides. This thesis offers ways to promote integration of knowledge and information during the lifecycle of industrial projects, enhancing the development towards innovative solutions in project business.

Success factors of commercial open source software projects

Open source and open source software development have been interesting phenomena during the past decade. Traditional business models do not apply with open source, where the actual product is free. However, it is possible to make business with open source, even successfully, but the question is: how? The aim of this study is to find the key factors of successfully making business out of commercial open source software development. The task is achieved by finding the factors that influence open source projects, finding the relation between those factors, and find out why some factors explain the success more than others. The literature review concentrates first on background of open innovation, open source and open source software. Then business models, critical success factors and success measures are examined. Based on existing literature a framework was created. The framework contains categorized success factors that influence software projects in general as well as open source software projects. The main categories of success factors in software business are divided into community management, technology management, project management and market management. In order to find out which of the factors based on the existing literature are the most critical, empirical research was done by conducting unstructured personal interviews. The main finding based on the interviews is that the critical success factors in open source software business do not differ from those in traditional software business or in fact from those in any other business. Some factors in the framework came out in the interviews that can be considered as key factors: establishing and communicating hierarchy (community management), localization (technology management), good license know-how and IPR management (project management), and effective market management (market management). The critical success factors according to the interviewees are not listed in the framework: low price, good product and good business model development.

Practical Framework for Monitoring the Performance of Agile IT Projects in an Output-Based Outsourcing Context

Over the past decade, organizations worldwide have begun to widely adopt agile software development practices, which offer greater flexibility to frequently changing business requirements, better cost effectiveness due to minimization of waste, faster time-to-market, and closer collaboration between business and IT. At the same time, IT services are continuing to be increasingly outsourced to third parties providing the organizations with the ability to focus on their core capabilities as well as to take advantage of better demand scalability, access to specialized skills, and cost benefits. An output-based pricing model, where the customers pay directly for the functionality that was delivered rather than the effort spent, is quickly becoming a new trend in IT outsourcing allowing to transfer the risk away from the customer while at the same time offering much better incentives for the supplier to optimize processes and improve efficiency, and consequently producing a true win-win outcome. Despite the widespread adoption of both agile practices and output-based outsourcing, there is little formal research available on how the two can be effectively combined in practice. Moreover, little practical guidance exists on how companies can measure the performance of their agile projects, which are being delivered in an output-based outsourced environment. This research attempted to shed light on this issue by developing a practical project monitoring framework which may be readily applied by organizations to monitor the performance of agile projects in an output-based outsourcing context, thus taking advantage of the combined benefits of such an arrangement Modified from action research approach, this research was divided into two cycles, each consisting of the Identification, Analysis, Verification, and Conclusion phases. During Cycle 1, a list of six Key Performance Indicators (KPIs) was proposed and accepted by the professionals in the studied multinational organization, which formed the core of the proposed framework and answered the first research sub-question of what needs to be measured. In Cycle 2, a more in-depth analysis was provided for each of the suggested Key Performance Indicators including the techniques for capturing, calculating, and evaluating the information provided by each KPI. In the course of Cycle 2, the second research sub-question was answered, clarifying how the data for each KPI needed to be measured, interpreted, and acted upon. Consequently, after two incremental research cycles, the primary research question was answered describing the practical framework that may be used for monitoring the performance of agile IT projects delivered in an output-based outsourcing context. This framework was evaluated by the professionals within the context of the studied organization and received positive feedback across all four evaluation criteria set forth in this research, including the low overhead of data collection, high value of provided information, ease of understandability of the metric dashboard, and high generalizability of the proposed framework.

Licensing Model Development for Small Modular Reactors (SMRs) - Focusing on the Finnish Regulatory Framework

Recently, Small Modular Reactors (SMRs) have attracted increased public discussion. While large nuclear power plant new build projects are facing challenges, the focus of attention is turning to small modular reactors. One particular project challenge arises in the area of nuclear licensing, which plays a significant role in new build projects affecting their quality as well as costs and schedules. This dissertation - positioned in the field of nuclear engineering but also with a significant section in the field of systems engineering - examines the nuclear licensing processes and their suitability for the characteristics of SMRs. The study investigates the licensing processes in selected countries, as well as other safety critical industry fields. Viewing the licensing processes and their separate licensing steps in terms of SMRs, the study adopts two different analysis theories for review and comparison. The primary data consists of a literature review, semi-structured interviews, and questionnaire responses concerning licensing processes and practices. The result of the study is a recommendation for a new, optimized licensing process for SMRs. The most important SMR-specific feature, in terms of licensing, is the modularity of the design. Here the modularity indicates multi-module SMR designs, which creates new challenges in the licensing process. As this study focuses on Finland, the main features of the new licensing process are adapted to the current Finnish licensing process, aiming to achieve the main benefits with minimal modifications to the current process. The application of the new licensing process is developed using Systems Engineering, Requirements Management, and Project Management practices and tools. Nuclear licensing includes a large amount of data and documentation which needs to be managed in a suitable manner throughout the new build project and then during the whole life cycle of the nuclear power plant. To enable a smooth licensing process and therefore ensure the success of the new build nuclear power plant project, management processes and practices play a significant role. This study contributes to the theoretical understanding of how licensing processes are structured and how they are put into action in practice. The findings clarify the suitability of different licensing processes and their selected licensing steps for SMR licensing. The results combine the most suitable licensing steps into a new licensing process for SMRs. The results are also extended to the concept of licensing management practices and tools.

CTQ process flow development and the impact for cost of quality

Tämä työ tehtiin Kone Industrial Oy:lle Major Projects yksikköön, laatuosastolle. Kone Major Projects yksikkö keskittyy erikoisiin ja suuriin hissi- ja liukuporras projekteihin. Työn tavoitteena oli luoda harmonisoitu prosessi hissikomponenttien laaduntarkkailua varten sekä tarkastella ja vertailla kustannussäästöjä, jota tällä uudella prosessilla voidaan saavuttaa. Tavoitteena oli saavuttaa 80-prosentin kustannussäästöt laatukustannuksissa uuden laatuprosessin avulla. Työn taustana ja tutkimusongelmana ovat lisääntyneet erikoisprojektit ja niiden myötä lisääntynyt laaduntarkkailun tarve. Ongelmana laaduntarkkailussa voitiin pitää harmonisoidun ja selkeän prosessin puuttumista C-prosessikomponenttien valmistuksessa. Lisäksi kehitysprosessin aikana luotiin vanhojen työkalujen pohjalta keskeinen laaduntarkkailutyökalu, CTQ-työkalu. Työssä käsitellään ensin Konetta yhtiönä ja selvitetään Koneen keskeisimmät prosessit työn taustaksi. Teoria osuudessa käsitellään prosessin kehitykseen liittyviä teorioita sekä yleisiä laatukäsitteitä ja esitetään teorioita laadun asemasta nykypäivänä. Lopuksi käsitellään COQ eli laatukustannusten teoriaa ja esitellään teoria PAF-analyysille, jota käytetään työssä laatukustannusten vertailuun case esimerkin avulla. Työssä kuvataan CTQ prosessin luominen alusta loppuun ja case esimerkin avulla testataan uutta CTQ prosessia pilottihankkeessa. Tässä case esimerkissä projektin bracket eli johdekiinnitysklipsi tuotetaan uuden laatuprosessin avulla sekä tehdään kustannusvertailu saman projektin toisen bracketin kanssa, joka on tuotettu ennen uuden laatuprosessin implementoimista. Työn lopputuloksena CTQ prosessi saatiin luotua ja sitä pystyttiin testaamaan käytännössä case esimerkin avulla. Tulosten perusteella voidaan sanoa, että CTQ prosessin käyttö vähentää laatukustannuksia huomattavasti ja helpottaa laadunhallintaa C-prosessikomponenttien tuotannossa.

The contributions of netnography in new product development

Netnography has been studying in various aspects (e.g. definitions of netnography, application of netngoraphy, conducting procedure…) within different industrial contexts. Besides, there are many studies and researches about new product development in various perspectives, such as new product development models, management of new product development project, or interaction between customers and new product design, and so on. However, the connection and the interaction between netnography and new product development have not been studied recently. This opens opportunities for the writer to study and explore unrevealed issues regarding to applying netnography in new product development. In term of the relation between netnography and new product development, there are numerous of matters need to be explored; for instance, the process of applying netnography in order to benefit to new product development, the involvement degree of netnography in new product development process, or eliminating useless information from netnography so that only crucial data is utilized, and so on. In this thesis, writer focuses on exploring how netnography is applied in new product development process, and what benefits netnography can contribute to the succeed of the project. The aims of this study are to understand how netnography is conducted for new product development purpose, and to analyse the contributions of netnography in the new product development process. To do so, a case-study strategy will be conducted with triple case studies. The case studies are chosen bases on many different criteria in order to select the most relevant cases. Eventually, the writer selected three case studies, which are Sunless tanning product project (HYVE), Listerine (NetBase), and Nivea co-creation and netnography in black and white deodorant. The case study strategy applied in this thesis includes four steps e.g. case selection, data collection, case study analysis, and generating the research outcomes from the analysis. This study of the contributions of netnography in the new product development process may be useful for the readers in many ways. It offers the fundamental knowledge of netnography market research method and basic understanding of new product development process. Additionally, it emphasizes the differences between netnography and other market research methods in order to explain the reasons why many companies and market research agents recently utilized netnography in their market research projects. Furthermore, it highlights the contributions of netnography in the new product development process in order to indicate the importance of netnography in developing new product. Thus, the potential readers of the study can be students, marketers, researchers, product developers, or business managers.

Project Management Tools in Agile Embedded Systems Development

Agile methods have become increasingly popular in the field of software engineering. While agile methods are now generally considered applicable to software projects of many different kinds, they have not been widely adopted in embedded systems development. This is partly due to the natural constraints that are present in embedded systems development (e.g. hardware–software interdependencies) that challenge the utilization of agile values, principles and practices. The research in agile embedded systems development has been very limited, and this thesis tackles an even less researched theme related to it: the suitability of different project management tools in agile embedded systems development. The thesis covers the basic aspects of many different agile tool types from physical tools, such as task boards and cards, to web-based agile tools that offer all-round solutions for application lifecycle management. In addition to these two extremities, there is also a wide range of lighter agile tools that focus on the core agile practices, such as backlog management. Also other non-agile tools, such as bug trackers, can be used to support agile development, for instance, with plug-ins. To investigate the special tool requirements in agile embedded development, the author observed tool related issues and solutions in a case study involving three different companies operating in the field of embedded systems development. All three companies had a distinct situation in the beginning of the case and thus the tool solutions varied from a backlog spreadsheet built from scratch to plug-in development for an already existing agile software tool. Detailed reports are presented of all three tool cases. Based on the knowledge gathered from agile tools and the case study experiences, it is concluded that there are tool related issues in the pilot phase, such as backlog management and user motivation. These can be overcome in various ways epending on the type of a team in question. Finally, five principles are formed to give guidelines for tool selection and usage in agile embedded systems development.

Software development methods and quality assurance: Special focus on South Korea

The purpose of this study was to explore software development methods and quality assurance practices used by South Korean software industry. Empirical data was collected by conducting a survey that focused on three main parts: software life cycle models and methods, software quality assurance including quality standards, the strengths and weaknesses of South Korean software industry. The results of the completed survey showed that the use of agile methods is slightly surpassing the use of traditional software development methods. The survey also revealed an interesting result that almost half of the South Korean companies do not use any software quality assurance plan in their projects. For the state of South Korean software industry large number of the respondents thought that despite of the weakness, the status of software development in South Korea will improve in the future.