986 resultados para ERP-järjestelmä
Resumo:
The main objective of this study was to examine how culture influences knowledge transfer and sharing within multicultural ERP project implementation in China. The main interest was to explain how national culture and knowledge are linked by understanding how culture influences knowledge transfer and sharing in a project organization. The other objective of this work was to discuss what Chinese cultural characteristic inhibit and en-hance knowledge sharing in ERP project. The perspective of this study was qualitative and the empirical material was collected from theme interviews among Stora Enso employees. Conclusion of this thesis is that Finns have a very direct style of communication and sharing knowledge whereas Chinese respect face shaving and indirect communication. Another conclusion is that knowledge sharing does not “just happen”, it is needed that project members understand national culture to get all project members commitment to project. In China most important is understand local business processes and understand role of trust and guanxi.
Resumo:
Pitkäaikaishankkeen tuotot ja kustannukset tulee jakaa osatuloutuksen keinoin hankkeen valmistusajalle. Tässä tapaustutkimuksessa tarkastellaan pitkäaikaishankkeiden osatulouttamista osana ERP -investointia. Tavoite on kartoittaa kohdeyrityksen nykyistä osatuloutuskäytäntöä sekä tutkia tähän liittyviä mahdollisia muutoksia ja niiden vaikutuksia. Tutkimuksessa hahmotetaan ensin ERP:n toimintaa ja etenkin SAP:n tarjoamia mahdollisuuksia osatulouttamiselle. Tämän jälkeen selvitetään osatuloutusta koskevaa sääntelyä ja siihen liittyvää muutoshanketta. Empiirisessä osassa osatuloutusta käsitellään kohdeyrityksen näkökulmasta laskelmien, kirjallisuuden ja osallistuvan havainnoinnin kautta. Tutkimuksen mukaan case -yrityksen kannattaa toteuttaa osatuloutusta siten, että myös komponenttikustannukset kerryttävät valmistusastetta. Käytännössä tämän toteuttaminen on kuitenkin erittäin haasteellista. Tutkimus suositteleekin siirtymistä sisäisen laskennan osalta käyttämään komponenttien hinnoittelun pohjana standardikustannushintoja.
Resumo:
IT Service Management plays a key role in many IT organizations today. First IT Service Management principles founded in the early 1980s but the real adaption emerged in the end 2000s. IT Financial Management is one of IT Service Management’s processes. The main purpose of this thesis was study how IT Financial Management approach can be improved in a case company. Budgeting, accounting and charging are IT Financial Management functions. These functions are researched in this thesis. Thesis materials consist of both qualitative and quantitative material. The theoretical part consists mostly of IT Service Management literature while interviews and the case company’s information systems are researched in the empirical part. Thesis also reviews different kind of the systems which supports and automates IT Financial Management functions. The biggest challenge is the cost allocation with the current ERP system in the case company. It is worth to take group based system for allocation in use before there is a holistic system in a market. The case company should also develop its IT service processes forward.
Resumo:
Työn aihe on lähtöisin toiminnanohjausjärjestelmän laatumoduulista, mikä painottuu tiedonkulkuun, aikataulutukseen, dokumenttien- ja reklamaatioiden hallintaan. Diplomityössä etsitään ratkaisua voiko laatumoduulin osioita soveltaa projektityössä. Työ on luonteeltaan kvalitatiivinen tapauskohtainen konstruktiivinen tutkimus. Teoria osassa käsitellään toiminnan laadun kehittämistä, jossa keskitytään muun maussa jatkuvaan parantamiseen ja muutosjohtamiseen. Kirjallisuudessa korostetaan ennaltaehkäisevää toimintaa, jolla pyritään välttämään virhekustannuksia ja ajan tuhlausta. Työn empiirisessä osassa on haastateltu niitä henkilöitä, jotka työskentelevät laadun parissa yrityksessä. Haastatteluiden tarkoitus on saada tietoa laatumoduulista ja siihen liittyvistä prosesseista. Yhteenvedossa päädyttiin muun muassa seuraaviin johtopäätöksiin että, osa laatumoduulin osioista soveltuu projektityöskentelyyn. Laatumoduulin osiot voivat tehostaa tiedonkulkua ja prosessien toimivuutta. Parhaimmillaan laatumoduulin avulla on mahdollista välttää ennaltaehkäisevästi virhekustannuksia.
Resumo:
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.
Resumo:
kuv., 15 x 22 cm
Resumo:
Implementing an enterprise resource planning (ERP) system often means a major change to an organization and involves significant risks. It is typical that many of the ERP system implementations fail resulting in tremendous damage to the business. Moreover, running normal business operations during an ERP system implementation is far more complicated than normally. This thesis focuses on how an organization should manage the ERP system implementation process in order to maintain supply performance during the implementation phase. The theoretical framework in this thesis focuses on ERP system implementations with a critical success factor approach. Critical success factors can be divided into strategic and tactical level success factors. By considering these critical success factors, ERP system implementation project’s timeline and best practices of an ERP implementation, a critical success factor based ERP system implementation management framework is presented. The framework can be used as a theoretical framework when the goal is to avoid ERP system implementation phase issues that are driven by the ERP system implementation project and that may decrease organization’s supply performance. This thesis is a case study that was written on an assignment to a confectionary company Cloetta Suomi Oy. In order to collect data, interviews of the case company personnel were conducted. In addition, several other data collection methods were used throughout the research process. These data collection methods include examination of presentations and archival records as well as direct observations in case company meetings and in various work duties. The results of this thesis indicate that there are several factors that may decrease organization’s supply performance during the ERP system implementation. These issues are categorized under external and internal issues and further into six risk drivers that are suppliers, customers, products, staff, information systems and other projects. After the description and categorization of each issue, the thesis focuses on finding solutions on how to avoid or mitigate the impact of these issues on the organization’s supply performance. This examination leads to several operational activities that are also practical to business practitioners. It is also stated that a successful ERP system implementation that also causes minimal disturbance to organization’s supply performance during the ERP system implementation, is achieved by considering three levels of actions.
Resumo:
ERP system is now attracting the SMEs, as it is now economical and affordable for them. The current research emphasizes on “how to make ERP successful for SMEs”. The researchers have identified various critical success factors in implementation of ERP. The research gap noticed by author is the missing point of view of ERP consultant. This thesis investigates the answer of research question “What are the critical success factors in implementation of ERP system in SMEs in opinion of ERP consultants and acquiring organizations”. The purpose of this study is to identify the highly important and less important factors. The study results will suggest the ERP managers where they have to concentrate more in order to achieve success. Literature is reviewed in order to setup a base for empirical study. Aplenty of work is found related to CSFs, SMEs and ERP. The authors and factors are organized in form of a table that tells which author is agreed upon which factor. Final result of literature review is a list of 14 CSFs. The qualitative research methodology is used to investigate the ERP in Pakistani SMEs. A case study approach is selected because of unified nature of SMEs in Pakistan. A rice mill is selected as a case because it contains maximum SME attributes. The opinion of a Microsoft certified consultant is obtained by a semi-structured interview. Similarly a semi-structured interview is conducted with CIO of SME that acquired ERP. Both the interviewees are asked about all 14 factors, whether they are agree or not and why. The collected evidences then analyzed by tabulation. The factors upon which both the participants found agreed, taken as highly important. Similarly the factors upon which both participants found disagree, taken as less important. Study results present a grid with four quadrants, the CSFs highly important in opinion of both, the CSFs less important in opinion of both, CSFs important in opinion of consultant but not client, CSFs important in opinion of client but not consultant. In discussion part, the significance of each factor is discussed individually. It is discussed that why some factors are high/less important for SMEs in Pakistan. The study output communicates a message that the success of ERP system in SMEs is linked with careful management of five important factors, the project management, top management support, user training and education, consultant participation and ERP teamwork and composition. The ERP consultants and managers can divert their concentration from less important factors such as user involvement, culture readiness and ERP package selection, toward the highly important factors. The limitations of the study are small number of interviews and less people involved, provide an opportunity for future research in this field of information system.
Resumo:
Tutkimuksen tarkoituksena on selvittää miten ja mitä tieto- ja viestintä teknologiaorganisaatio (=ICT –organisaatio) oppii järjestelmien ja toimintatapojen kehitysprojektissa. Tutkimuksen tavoitteena on saada tietoa miten kehitysprojektiin osallistuneet henkilöt ovat kokeneet projektin ensimmäisen vaiheen vaikuttaneen omaan ja organisaation oppimiseen. Samalla halutaan selvittää missä on onnistuttu ja mitä olisi voinut tehdä toisin. Aiheesta ei löytynyt täysin vastaavia aikaisempia tutkimuksia. Tutkimus on luonteeltaan laadullinen. Aineisto kerättiin haastattelemalla kuutta järjestelmien ja toimintatapojen kehitysprojektiin osallistunutta henkilöä. Haastattelut toteutettiin yksilöhaastatteluina teemahaastattelua apuna käyttäen. Tutkimuksen teoriaosassa käsiteltiin aikuisten oppimista, organisaation oppimista ja kerrottiin muutamista samantyyppisistä järjestelmä- ja toimintatapojen kehitysprojekteista. Tutkimuksessa tuli esiin, että aikuiset oppivat parhaiten ryhmässä. Aikaisempi tieto ja kokemus, hyvä ilmapiiri, motivaatio ja sitoutuminen edistävät oppimista. Kiire, ongelmat tiedonkulussa ja epäselvät roolit ja vastuut organisaatiossa koettiin oppimisen esteiksi. Projektin onnistumisina koettiin myönteinen ilmapiiri ja se, että on oppinut uutta muilta projektin jäseniltä. Projektin kehityskohteissa tuli esille suunnitelmallisuuden puute, tavoiteaikataulun venyminen ja kuten myös oppimisen esteissä, ongelmat tiedonkulussa ja epäselvyydet rooleissa ja vastuissa. Tutkimuksen tulosten perusteella aikuisten ja organisaation oppimisen ja projektin onnistumisen avaimet ovat: hyvä suunnittelu, hyvä ilmapiiri, motivaatio, sitoutuminen, ryhmässä oppiminen, selkeät roolit ja vastuut, hallittu tiedonjakaminen, hallittu ajankäyttö. Tutkimuksen tuloksissa korostuivat erityisesti tiedonkulun, aikataulutuksen ja epäselvien roolien ja vastuiden vaikutus oppimiseen ja projektin onnistumiseen. Sitä olisi mielenkiintoista tutkia vielä lisää.
Resumo:
This bachelor’s thesis, written for Lappeenranta University of Technology and implemented in a medium-sized enterprise (SME), examines a distributed document migration system. The system was created to migrate a large number of electronic documents, along with their metadata, from one document management system to another, so as to enable a rapid switchover of an enterprise resource planning systems inside the company. The paper examines, through theoretical analysis, messaging as a possible enabler of distributing applications and how it naturally fits an event based model, whereby system transitions and states are expressed through recorded behaviours. This is put into practice by analysing the implemented migration systems and how the core components, MassTransit, RabbitMQ and MongoDB, were orchestrated together to realize such a system. As a result, the paper presents an architecture for a scalable and distributed system that could migrate hundreds of thousands of documents over weekend, serving its goals in enabling a rapid system switchover.
Resumo:
This paper takes a fresh approach to ERP projects by examining the upstream organizations and their sales and marketing processes.