| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Halttunen, Veikko", "language": null, "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "V\u00e4is\u00e4nen, Mika", "language": null, "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2024-06-14T09:49:04Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2024-06-14T09:49:04Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2024", "language": null, "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/95884", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Toiminnanohjausj\u00e4rjestelm\u00e4n (Enterprise Resource Planning, ERP) tarkoituksena on integroida organisaation keskeisimm\u00e4t ydintoiminnot yhden tietoj\u00e4rjestelm\u00e4n kautta hallittavaksi. ERP-j\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00f6nottoprojektit ovat tunnetusti resurssi-intensiivisi\u00e4 kokonaisuuksia, jotka ovat alttiita ep\u00e4onnistumiselle niiden kompleksisuuden takia. Kirjallisuuden mukaan ERP-j\u00e4rjestelmien k\u00e4ytt\u00f6\u00f6notossa ep\u00e4onnistumiset ovat yleisempi\u00e4 kuin onnistumiset, mink\u00e4 vuoksi niit\u00e4 on tutkittu viime vuosikymmenin\u00e4. ERP-j\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00f6nottoprosessi on laaja kokonaisuus, joka on tunnistettu tarpeiltaan organisaatiokohtaiseksi, mink\u00e4 vuoksi on vaikeaa m\u00e4\u00e4ritell\u00e4 yleist\u00e4, eri alojen v\u00e4list\u00e4 k\u00e4ytt\u00f6\u00f6nottomallia. Tutkimukset perustuvat usein ERP-j\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00f6nottoprosessiin yleisesti, alakohtaisiin k\u00e4ytt\u00f6\u00f6nottoprojekteihin tai yksitt\u00e4isiin tapaustutkimuksiin k\u00e4ytt\u00f6\u00f6notoista organisaatioissa. T\u00e4m\u00e4n my\u00f6t\u00e4 puutteita on vertailevasta tutkimuksesta, joka auttaisi tunnistamaan ERP-k\u00e4ytt\u00f6\u00f6nottoprosessin eroavaisuuksia eri alojen v\u00e4lill\u00e4. Eroavaisuuksien tiedostaminen voisi edist\u00e4\u00e4 k\u00e4ytt\u00f6\u00f6nottoprosessiin osallistuvien tahojen tietoisuutta eri aloilla tapahtuvien k\u00e4ytt\u00f6\u00f6nottoprojektien vaatimista erityispiirteist\u00e4, mik\u00e4 auttaisi parantamaan osaltaan niiden tuloksia. T\u00e4m\u00e4n vuoksi tutkielma k\u00e4sittelee ERP-j\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00f6nottoprosessin toimialakohtaisia eroavaisuuksia yksityisell\u00e4 sektorilla. Tutkielmassa tarkastellaan kirjallisuuskatsauksen avulla keskeist\u00e4 teoriaa liittyen ERP-j\u00e4rjestelm\u00e4\u00e4n, sen k\u00e4ytt\u00f6\u00f6nottoprosessiin ja relevanttiin oheistietoon sek\u00e4 toimialakohtaisiin tapaustutkimuksiin k\u00e4ytt\u00f6\u00f6nottoprosessista. Valitut toimialat tutkimukseen ovat teollisuudenala, kaupan ala ja finanssiala. Tutkielman tulokset osoittavat, ett\u00e4 ERP-j\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00f6nottoprosessin eroavaisuudet eri yksityisen sektorin toimialoilla liittyv\u00e4t vahvasti toimialakohtaisiin vaatimuksiin. Erilaiset vaatimukset toimialoittain vaikuttavat, kuinka organisaatio suunnittelee k\u00e4ytt\u00f6\u00f6nottoprosessin ja sen vaiheistuksen, millainen painoarvo eri liiketoiminnallisilla tekij\u00f6ill\u00e4 on ja miten erityispiirteet huomioidaan usein k\u00e4ytt\u00f6\u00f6nottoprosessiin kuuluvassa liiketoimintaprosessien analysoinnissa ja niiden p\u00e4ivitt\u00e4misess\u00e4 ERP-j\u00e4rjestelm\u00e4lle sopivaksi. Lopulta tutkielma havainnollistaa, kuinka ERP-j\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00f6nottoprosessi on enemm\u00e4nkin toimialakohtainen organisaatiomuutoksen kokonaisuus, eik\u00e4 ainoastaan uuden teknologian k\u00e4ytt\u00f6\u00f6nottoprojekti.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Enterprise resource planning (ERP) is designed to integrate the core functions of an enterprise into a single information system. ERP implementation projects are recognized to be resource-intensive which are prone to failures because of their complexity. According to the literature, ERP implementation projects often have more failures than successes, which is the reason they have been researched in the past decades. ERP implementation process is a large-scale entirety that has been identified as an organization-specific project, making it difficult to define a general cross-industry implementation model. The research is often based on the ERP system implementation process in general, industry-specific projects or individual case studies of implementations in organizations. As a result, there is a lack of comparative research that would help to identify differences in ERP implementation between different industries. Recognizing these differences contributes to raising awareness of the people involved in the process about the specificities required for the implementation of ERP, which would help to improve their results. Therefore, the purpose of this study is to address the differences in the implementation process of ERP system in the private sector. The method used for the study is literature review to examine the essential theory related to ERP in general, the ERP implementation process and other related information, as well as industry-specific case studies of ERP implementation in organizations. The industries selected for the study are manufacturing, retail, and finance. The results of the study indicate that the differences in the ERP implementation among different private sector organizations are closely tied to specific industry requirements. Different industry requirements affect how the implementation process is planned and phased, the importance assigned to different business factors, and how specific characteristics are considered when analyzing and conceivably updating an organization\u2019s business processes during the implementation. Ultimately, this study demonstrates that the ERP implementation process represents an industry-specific approach to organizational change rather than merely a project for adopting a new technology solution.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Miia Hakanen (mihakane@jyu.fi) on 2024-06-14T09:49:04Z\r\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2024-06-14T09:49:04Z (GMT). No. of bitstreams: 0\r\n Previous issue date: 2024", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "41", "language": null, "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.language.iso", "value": "fin", "language": null, "element": "language", "qualifier": "iso", "schema": "dc"}, {"key": "dc.rights", "value": "In Copyright", "language": "en", "element": "rights", "qualifier": null, "schema": "dc"}, {"key": "dc.subject.other", "value": "ERP", "language": null, "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "k\u00e4ytt\u00f6\u00f6notto", "language": null, "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "k\u00e4ytt\u00f6\u00f6nottoprosessi", "language": null, "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "implementointi", "language": null, "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "ERP-j\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00f6nottoprosessin toimialakohtaiset eroavaisuudet yksityisell\u00e4 sektorilla", "language": null, "element": "title", "qualifier": null, "schema": "dc"}, {"key": "dc.type", "value": "bachelor thesis", "language": null, "element": "type", "qualifier": null, "schema": "dc"}, {"key": "dc.identifier.urn", "value": "URN:NBN:fi:jyu-202406144650", "language": null, "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Bachelor's thesis", "language": "en", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Kandidaatinty\u00f6", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Informaatioteknologian tiedekunta", "language": "fi", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Faculty of Information Technology", "language": "en", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Informaatioteknologia", "language": "fi", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Information Technology", "language": "en", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "Jyv\u00e4skyl\u00e4n yliopisto", "language": "fi", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "University of Jyv\u00e4skyl\u00e4", "language": "en", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Tietoj\u00e4rjestelm\u00e4tiede", "language": "fi", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Information Systems Science", "language": "en", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "yvv.contractresearch.funding", "value": "0", "language": null, "element": "contractresearch", "qualifier": "funding", "schema": "yvv"}, {"key": "dc.type.coar", "value": "http://purl.org/coar/resource_type/c_7a1f", "language": null, "element": "type", "qualifier": "coar", "schema": "dc"}, {"key": "dc.rights.accesslevel", "value": "openAccess", "language": null, "element": "rights", "qualifier": "accesslevel", "schema": "dc"}, {"key": "dc.type.publication", "value": "bachelorThesis", "language": null, "element": "type", "qualifier": "publication", "schema": "dc"}, {"key": "dc.subject.oppiainekoodi", "value": "601", "language": null, "element": "subject", "qualifier": "oppiainekoodi", "schema": "dc"}, {"key": "dc.subject.yso", "value": "yksityinen sektori", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "erot", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "k\u00e4ytt\u00f6\u00f6notto", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "tietoj\u00e4rjestelm\u00e4t", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "toiminnanohjausj\u00e4rjestelm\u00e4t", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}]
|