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.

Improving inventory management

Having inventory to cover from all possible problems would increase the inventory level indefinitely in accordance with the standard deviation. If the materials in stock are not used, but kept just to be on the safe side, they are waste. The main objective of this study was to find out, how much inventory is required to cover the requirements, without causing delivery problems towards the end-customers, and how the inventory could be controlled efficiently. Several improvements were made in the controlling principles, and the inventory level was quickly decreased by more than 30 %, and kept on the reached level. The suitability of kanban control was investigated, and it was eventually taken into some use. A great advantage was found in the new procedures in securing the supply. The requests for quotations were diversified, and the faulty basis was corrected. Thus, the inventory surplus would later be avoided, and at the same time, a lot of valuable time was saved from daily routines to further improvement projects.

Kenttätietojen hyödyntäminen taajuusmuuttajan luotettavuuden suunnittelussa

Taajuusmuuttaja on yhä yleisempi laite perinteisten oikosulkumoottoreiden nopeuden säädössä, niin teollisuudessa kuin muilla käyttökohteissa. Ensimmäiset laitetyypit olivat mekaanisesti suurikokoisia ja vaativat laitteen tekniseltä tuelta ja kunnossapidolta hyvää teknistä perehtyneisyyttä laitteisiin. Teknologian kehittymisen myötä laitteiden teho/kokosuhde on pienentynyt ja tarjolla on useita eri sovelluskohteisiin suoraan soveltuvia taajuusmuuttajia varustettuna helppokäyttöisillä ja kaupallisilla käyttöliittymillä. Laitteen elinkaaren aikainen luotettavuusjohtaminen edellyttää valmistajalta varsinaisen laitesuunnittelun lisäksi tarkoituksenmukaisia testausmenetelmiä ja kokemusperäistä luotettavuustietoa myös asennetusta laitekannasta. Työssä on käyty taajuusmuuttajan suunnittelun kannalta läpi luotettavuuden käsitteistö sekä yleisimpiä luotettavuusmenetelmiä. Luotettavuusnäkökohtia verrataan asennetusta laitekannasta saatuihin kokemuksiin laitteen valmistajan ja tuotetuen kannalta. Työssä on esitetty luokittelun perusteita ja menetelmät, miten käytön aikana voidaan arvioida laitteen teknistä tilaa sekä huomioida se kunnossapidon suunnittelussa. Johtopäätöksenä huomataan, että asennuspaikka ja käyttösovellus määrittävät taajuusmuuttajan käytettävyyden. Kenttätietoja voidaan hyödyntää paikallisen kunnossapidon kannalta kunnossapidon ja investointien suunnittelussa. Toisaalta valmistajan tuotekehitys saa asennetuista laitteista kokemuksia seuraavan sukupolven tyypin suunnittelun perustaksi. Tekniikan voimakkaan kehittymisen seurauksena uusien taajuusmuuttajatyyppien valmistus kestää yhä lyhyemmän ajanjakson, jolloin asennetusta laitekannasta saatu kenttäkokemus on arvokasta tietoa laitevalmistajalle. Yhteenvetona valmistajan laiterekistereitä voidaan kehittää siten, että niihin on tallennettavissa laitekartoitusten perusteella kerättyä informaatiota, jota niin valmistajan myynti, tuotetuki kuin laitesuunnittelu voi omassa toiminnassaan hyödyntää.

Segmentation of Industrial Customers – Case: Finnish Mechanical Engineering Companies

Segmentointi on perinteisesti ollut erityisesti kuluttajamarkkinoinnin työkalu, mutta siirtymä tuotteista palveluihin on lisännyt segmentointitarvetta myös teollisilla markkinoilla. Tämän tutkimuksen tavoite on löytää selkeästi toisistaan erottuvia asiakasryhmiä suomalaisen liikkeenjohdon konsultointiyritys Synocus Groupin tarjoaman case-materiaalin pohjalta. K-means-klusteroinnin avulla löydetään kolme potentiaalista markkinasegmenttiä perustuen siihen, mitkä tarjoamaelementit 105 valikoitua suomalaisen kone- ja metallituoteteollisuuden asiakasta ovat maininneet tärkeimmiksi. Ensimmäinen klusteri on hintatietoiset asiakkaat, jotka laskevat yksikkökohtaisia hintoja. Toinen klusteri koostuu huolto-orientoituneista asiakkaista, jotka laskevat tuntikustannuksia ja maksimoivat konekannan käyttötunteja. Tälle kohderyhmälle kannattaisi ehkä markkinoida teknisiä palveluja ja huoltosopimuksia. Kolmas klusteri on tuottavuussuuntautuneet asiakkaat, jotka ovat kiinnostuneita suorituskyvyn kehittämisestä ja laskevat tonnikohtaisia kustannuksia. He tavoittelevat alempia kokonaiskustannuksia lisääntyneen suorituskyvyn, pidemmän käyttöiän ja alempien huoltokustannusten kautta.

Tiedon hallinta varastonhallintajärjestelmän hankinnassa

Diplomityössä toteutettiin varastonhallintajärjestelmän hankinta prosessoimalla tietoa hallitusti varastonhallinnan kehittämiseksi. Kvalitatiivinen tapaustutkimus tehtiin tietojohtamisen näkökulmasta käyttäjälähtöisen C-CEI –menetelmän avulla haastattelemalla ja havainnoimalla tapausyritystä. Haastatteluja tehtiin 10 kertaa. Tutkimuksessa kartoitettiin ja kilpailutettiin kotimaiset järjestelmätoimittajat, joita löydettiin 15. Näistä toimittajista 6 vastasi vaatimuksia ja teki tarjouksen. Tutkimuksen lopuksi tehtiin järjestelmän hankintaehdotus. Tutkimuksen teoreettinen viitekehys koostui tietojohtamisesta, varastonhallinnasta ja ohjelmistotuotannosta. Tutkimuksessa pääkysymyksenä esitettiin miten tietojohtamisen avulla voidaan tukea varastonhallintajärjestelmän hankintaa. Tutkimuksessa havaittiin, että tietojärjestelmän hankinta varastonhallinnan osalta on moniulotteinen liiketoiminnan kehittämistehtävä. Tietojärjestelmähankinta tulisi siten nähdä liiketoimintaa eteenpäin vievänä mahdollisuutena. Lisäksi loppukäyttäjän vaatimusten kartoittamiseen tulisi sitoutua huolella ja suhtautua kriittisesti eri järjestelmävaihtoehtoihin. Vaatimusmäärittelyn asettaminen ja vaatimusten priorisoiminen ovat haasteellisia tehtäviä. Tiedon hallinnan aikana saatiin selville, että loppukäyttäjän vaatimusten mukainen tarjouspyyntö edesauttaa ensinnäkin tarjousten tekemistä mutta myös niiden prosessointia ja analysointia. Vain oikealla tiedolla ja sen yhteyksillä on merkitystä. Tutkimuksen perusteella tietojärjestelmän hankinta suositellaan tehtäväksi hallitsemalla tietoa systemaattisesti erityisesti sen alkuvaiheen aikana. Tietojohtaminen virtaviivaistaa hankkeen etenemistä ja aikataulutusta, vähentää loppukäyttäjän kustannuksia tehokkaalla kilpailutusmenettelyllä, edistää kilpailukykyä ja luo hyvän lähtökohdan koko tietojärjestelmän hankinnan läpiviemiselle ja yhteistyö-suhteen rakentumiselle kauppakumppaneiden välille.

Socially Competent Leadership - predictors, impacts and skilling in engineering

Earlier management studies have found a relationship between managerial qualities and subordinate impacts, but the effect of managers‘ social competence on leader perceptions has not been solidly established. To fill the related research gap, the present work embarks on a quantitative empirical effort to identify predictors of successful leadership. In particular, this study investigates relationships between perceived leader behavior and three selfreport instruments used to measure managerial capability: 1) the WOPI Work Personality Inventory, 2) Raven‘s general intelligence scale, and 3) the Emotive Communication Scale (ECS). This work complements previous research by resorting to both self-reports and other-reports: the results acquired from the managerial sample are compared to subordinate perceptions as measured through the ECS other-report and the WOPI360 multi-source appraisal. The quantitative research is comprised of a sample of 8o superiors and 354 subordinates operating in eight Finnish organizations. The strongest predictive value emerged from the ECS self- and other-reports and certain personality dimensions. In contrast, supervisors‘ logical intelligence did not correlate with leadership perceived as socially competent by subordinates. 16 of the superiors rated as most socially competent by their subordinates were selected for case analysis. Their qualitative narratives evidence the role of life history and post-traumatic growth in developing managerial skills. The results contribute to leadership theory in four ways. First, the ECS self-report devised for this research offers a reliable scale for predicting socially competent leader ability. Second, the work identifies dimensions of personality and emotive skills that can be considered predictors of managerial ability and benefited from in leader recruitment and career planning. Third, the Emotive Communication Model delineated on the basis of the empirical data allows for a systematic design and planning of communication and leadership education. Fourth, this workfurthers understanding of personal growth strategies and the role of life history in leader development and training. Finally, this research advances educational leadership by conceptualizing and operationalizing effective managerial communications. The Emotive Communication Model devised directs the pedagogic attention in engineering to assertion, emotional availability and inspiration skills. The proposed methodology addresses classroom management strategies drawing from problem-based learning, student empowerment, collaborative learning, and so-called socially competent teachership founded on teacher immediacy and perceived caring, all constituting strategies moving away from student compliance and teacher modelling. The ultimate educational objective embraces the development of individual engineers and organizational leaders that not only possess traditional analytical and technical expertise and substantive knowledge but are intelligent also creatively, practically, and socially.

Process approach in quality management - Case: ECO process development in EMS industry

The aim of the thesis was to study quality management with process approach and to find out how to utilize process management to improve quality. The operating environment of organizations has changed. Organizations are focusing on their core competences and networking with suppliers and customers to ensure more effective and efficient value creation for the end customer. Quality management is moving from inspection of the output to prevention of problems from occurring in the first place and management thinking is changing from functional approach to process approach. In the theoretical part of the thesis, it is studied how to define quality, how to achieve good quality, how to improve quality, and how to make sure the improvement goes on as never ending cycle. A selection of quality tools is introduced. Process approach to quality management is described and compared to functional approach, which is the traditional way to manage operations and quality. The customer focus is also studied, and it is presented, that to ensure long term customer commitment, organization needs to react to changing customer requirements and wishes by constantly improving the processes. In the experimental part the theories are tested in a process improvement business case. It is shown how to execute a process improvement project starting from defining the customer requirements, continuing to defining the process ownership, roles and responsibilities, boundaries, interfaces and the actual process activities. The control points and measures are determined for the process, as well as the feedback and corrective action process, to ensure continual improvement can be achieved and to enable verification that customer requirements are fulfilled.

Strategic Change Management Readiness Evaluation in Organizations

The objective of this study and paper was to find out how the strategic change management readiness in organizations can be evaluated. Based on theory and prior CMP model, the framework of strategic change management and issues related to it was constructed. Additionally a synthesis of the most important phases and interventions in strategic change process and project was created. These phases were starting point, planning, implementation and evaluation and securing phases. Qualitative approach was utilized in the empirical part of the study due to the need for in-depth information about the topics surveyed through semi-structured interview. There were 18 responders from the top management of large Finnish companies. In this study interventions, strengths and weaknesses during the various phases of strategic change projects were revealed. Additionally the interviewees’ opinion on the importance of each of the interventions in strategic change project success was asked. According to this study, the most important phases recognized through researching theoretical literature, prior CMP model and empirical information in starting point phase were analysis of current and desired state and need for change accompanied with guiding coalition formulation. In planning phase the most important interventions were project organization formulation, action plan creation, analysis of prior and current strategic change projects and organizational structure analysis. In the change project implementation phase the interventions of importance were launch, quick wins, sense of urgency creation, change resistance management and change communications. In the final evaluation and securing phase project evaluation was the most important intervention. Based on the results a tool for creating change management readiness profile was created.

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.

MASTER DATA MANAGEMENT MATURITY AND TECHNOLOGY ASSESSMENT - From theory to practice, case Ineo Oy

After decades of mergers and acquisitions and successive technology trends such as CRM, ERP and DW, the data in enterprise systems is scattered and inconsistent. Global organizations face the challenge of addressing local uses of shared business entities, such as customer and material, and at the same time have a consistent, unique, and consolidate view of financial indicators. In addition, current enterprise systems do not accommodate the pace of organizational changes and immense efforts are required to maintain data. When it comes to systems integration, ERPs are considered “closed” and expensive. Data structures are complex and the “out-of-the-box” integration options offered are not based on industry standards. Therefore expensive and time-consuming projects are undertaken in order to have required data flowing according to business processes needs. Master Data Management (MDM) emerges as one discipline focused on ensuring long-term data consistency. Presented as a technology-enabled business discipline, it emphasizes business process and governance to model and maintain the data related to key business entities. There are immense technical and organizational challenges to accomplish the “single version of the truth” MDM mantra. Adding one central repository of master data might prove unfeasible in a few scenarios, thus an incremental approach is recommended, starting from areas most critically affected by data issues. This research aims at understanding the current literature on MDM and contrasting it with views from professionals. The data collected from interviews revealed details on the complexities of data structures and data management practices in global organizations, reinforcing the call for more in-depth research on organizational aspects of MDM. The most difficult piece of master data to manage is the “local” part, the attributes related to the sourcing and storing of materials in one particular warehouse in The Netherlands or a complex set of pricing rules for a subsidiary of a customer in Brazil. From a practical perspective, this research evaluates one MDM solution under development at a Finnish IT solution-provider. By means of applying an existing assessment method, the research attempts at providing the company with one possible tool to evaluate its product from a vendor-agnostics perspective.

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.

Working capital management in the small and medium-sized enterprises Case: Project-based business environment in Flowrox Oy

This Master´s thesis illustrates how growing a business ties up the company´s working capital and what the cost of committed capital. In order to manage a company´s working capital in rapid business growth phase, the thesis suggests that by monitoring and managing the operating and cash conversion cycles of customers´ projects, a company can find ways to secure the required amount of capital. The research method of this thesis was based on literature reviews and case study research. The theoretical review presents the concepts of working capital and provides the background for understanding how to improve working capital management. The company in subject is a global small and medium-sized enterprise that manufactures pumps and valves for demanding process conditions. The company is expanding, which creates lots of challenges. This thesis concentrates to the company´s working capital management and its efficiency through the supply chain and value chain perspective. The main elements of working capital management are inventory management, accounts receivable management and accounts payable management. Prepayments also play a significant role, particularly in project-based businesses. Developing companies´ working capital management requires knowledge from different kind of key operations´ in the company, like purchasing, production, sales, logistics and financing. The perspective to develop and describe working capital management is an operational. After literature reviews the thesis present pilot projects that formed the basis of a model to monitor working capital in the case company. Based on analysis and pilot projects, the thesis introduces a rough model for monitoring capital commitments in short time period. With the model the company can more efficiently monitor and manage their customer projects.

De-escalation of commitment management strategy in IT project management methodology: case of ERP implementation project by IT consulting company

According to several surveys and observations, the percentage of successfully conducted IT projects without over-budgeting and delays in time schedule are extremely low. Many projects also are evaluated as failures in terms of delivered functionality. Nuldén (1996) compares IT projects with bad movies; after watching for 2 hours, one still tries to finish it even though one understands that it is a complete waste of time. The argument for that is 'I've already invested too much time to terminate it now'. The same happens with IT projects: sometimes the company continues wasting money on these projects for a long time, even though there are no expected benefits from these projects. Eventually these projects are terminated anyway, but until this moment, the company spends a lot. The situation described above is a consequence of “escalation of commitment” - project continuation even after a manager receives negative feedback of the project’s success probability. According to Keil and Mähring (2010), even though escalation can occur in any type of project, it is more common among complex technological projects, such as IT projects. Escalation of commitment very often results in runaway projects. In order to avoid it, managers use de-escalation strategies, which allow the resources to be used in more effective. These strategies lead to project termination or turning around, which stops the flow of wasted investments. Numbers of researches explore escalation of commitment phenomena based on experiments and business cases. Moreover, during the last decade several frameworks were proposed for de-escalation strategy. However, there is no evidence of successful implementation of the de-escalation of commitment strategy in the literature. In addition, despite that fact that IT project management methodologies are widely used in the companies, none of them cover the topic of escalation of commitment risks. At the same time, there are no researches proposing the way to implement de-escalation of commitment strategy into the existing project management methodology The research is focused on a single case of large ERP implementation project by the consulting company. Hence, the main deliverables of the study include suggestions of improvement in de-escalation methods and techniques in the project and in the company. Moreover, the way to implement these methods into existing project management methodology and into the company general policies is found.

Innovation Project Portfolio Management

Companies today are forced to innovate in order to remain within business. Such innovation projects undertaken by the companies are defined in this study as creative ideas which have been managed through “Stage-Gate” innovation process. This process is used to manage innovation projects as they proceed from being newly created to ready for launching/implementing. This has ensured that the companies manage the innovation project right. However, with so many new creative ideas the companies can come up within limited resources, the companies must rely on Innovation Project Portfolio Management (IPPM) to ensure that they are managing only the right innovation projects. Although, there are many tools and techniques available for use within Project Portfolio Management, there is still no consensus on which are the most effective and no standard framework has been established especially for IPPM. Thus, this study proposes a practical framework for which individual innovative organization can follow as a guideline to manage its innovation project portfolio. The study theoretically first addresses the key differences between project portfolio management of innovation projects and other traditional projects - one of which is the stage nature of innovation projects due to their unclear objectives from the beginning compare to clearly established objectives of traditional projects. Secondly, different tools and techniques which can be used are examined based on the three goals of IPPM: (1) Maximizing the Value of Innovation Project Portfolio: Financial Methods, Decision Trees, Scoring Models and Checklists; (2) Balancing Innovation Project Portfolio: Visual Representations; and (3) Aligning Innovation Project Portfolio with Strategy: Bottom-Up (Scoring Models with Strategic Criteria) and Top-Down (Strategic Buckets). Finally, the two approaches in which IPPM can be integrated with Stage-Gate innovation process are discussed: (1) Gates- Dominated; and (2) Portfolio Reviews-Dominated. Practically, this study investigates IPPM of a case organization, and through analysis of the case study results proposes a practical framework for case organization to improve its current management of innovation project portfolio. This framework is then generalized to propose a final practical framework or guideline for which an innovative organization can follow to manage its innovation project portfolio.

Evaluating the Maturity of Data Management Practices in a Major Energy Provider Company

Data is the most important asset of a company in the information age. Other assets, such as technology, facilities or products can be copied or reverse-engineered, employees can be brought over, but data remains unique to every company. As data management topics are slowly moving from unknown unknowns to known unknowns, tools to evaluate and manage data properly are developed and refined. Many projects are in progress today to develop various maturity models for evaluating information and data management practices. These maturity models come in many shapes and sizes: from short and concise ones meant for a quick assessment, to complex ones that call for an expert assessment by experienced consultants. In this paper several of them, made not only by external inter-organizational groups and authors, but also developed internally at a Major Energy Provider Company (MEPC) are juxtaposed and thoroughly analyzed. Apart from analyzing the available maturity models related to Data Management, this paper also selects the one with the most merit and describes and analyzes using it to perform a maturity assessment in MEPC. The utility of maturity models is two-fold: descriptive and prescriptive. Besides recording the current state of Data Management practices maturity by performing the assessments, this maturity model is also used to chart the way forward. Thus, after the current situation is presented, analysis and recommendations on how to improve it based on the definitions of higher levels of maturity are given. Generally, the main trend observed was the widening of the Data Management field to include more business and “soft” areas (as opposed to technical ones) and the change of focus towards business value of data, while assuming that the underlying IT systems for managing data are “ideal”, that is, left to the purely technical disciplines to design and maintain. This trend is not only present in Data Management but in other technological areas as well, where more and more attention is given to innovative use of technology, while acknowledging that the strategic importance of IT as such is diminishing.