DOCSLIB.ORG

D1 Cyber Secure Supply Chain – Requirements Specification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
D1 Cyber Secure Supply Chain – Requirements Specification Project acronym: SECURED BY BLOCKCHAIN Project title: Secured by Blockchain: Developing cyber risk free supply chains Funding Scheme: Ateneo 2019 D1 Cyber Secure Supply Chain – Requirements Specification Submission date: 23/01/2020 Start date of project: 01/07/2019 Duration: 6M Organisation name of lead contractor for this deliverable: LIUC First Outline Dissemination Level Restricted to a group specified by the consortium (including the Commission RE Services) RE* RESTREINT Project partners and Advisory Board Members SECURED BY BLOCKCHAIN D1 – LIUC UNIVERSITÀ CARLO CATTANEO - 20.01.2020 - ITALY Document summary Information Authors and contributors Initial Name Organisation Role YBG Yari Borbon Galvez LIUC Partner AC Alessandro Creazza LIUC Partner CC Claudia Colicchia POLI Partner FS Fernanda Strozzi LIUC Partner NE Niloofar Etemadi LIUC Partner RO Riccardo Occa LIUC Partner DM David Menachof FAU Partner Revision history Revision Date Who Comment Draft v0.1 20/01/2020 LIUC team Draft v0.2 21/01/2020 LIUC team Draft v0.3 24/01/2020 Draft v0.4 31/01/2020 V1.0 07/02/2020 Final 14/02/2020 LIUC library LIUC research work in progress website Quality control Role Who Date Project manager Fabrizio Dallari 21/01/2020 Disclaimer The content of the publication herein is the sole responsibility of the publishers and it does not necessarily represent the views expressed by LIUC Università Carlo Cattaneo or its services. While the information contained in the documents is believed to be accurate, the authors(s) or any other participant in the SECURED BY BLOCKCHAIN consortium make no warranty of any kind with regard to this material including, but not limited to the implied warranties of merchantability and fitness for a particular purpose. Neither the SECURED BY BLOCKCHAIN Consortium nor any of its members, their officers, employees or agents shall be responsible or liable in negligence or otherwise howsoever in respect of any inaccuracy or omission herein. Without derogating from the generality of the foregoing neither the SECURED BY BLOCKCHAIN Consortium nor any of its members, their officers, employees or agents shall be liable for any direct or indirect or consequential loss or damage caused by or arising from any information advice or inaccuracy or omission herein. Page 2 of 54 SECURED BY BLOCKCHAIN D1 – LIUC UNIVERSITÀ CARLO CATTANEO - 20.01.2020 - ITALY Contents D1 CYBER SECURE SUPPLY CHAIN – REQUIREMENTS SPECIFICATION ............................................................... 1 1 EXECUTIVE SUMMARY ............................................................................................................................. 4 2 BACKGROUND ......................................................................................................................................... 5 2.1 INTRODUCTION .......................................................................................................................................... 5 2.2 CYBER SUPPLY CHAIN RISK MANAGEMENT (CSCRM) ......................................................................................... 7 2.3 BLOCKCHAIN AND SUPPLY CHAIN MANAGEMENT ............................................................................................... 8 3 DEFINITION OF THE SCOPE OF THE SECURED BY BLOCKCHAIN PROJECT ................................................ 10 3.1 APPROACH .............................................................................................................................................. 10 3.2 TESTING ................................................................................................................................................. 11 3.3 ASSESSMENT ........................................................................................................................................... 11 4 REQUIREMENTS AND SPECIFICATIONS .................................................................................................. 12 4.1 INTRODUCTION ........................................................................................................................................ 12 4.2 META-ANALYSIS: SUPPLY CHAIN CYBERSECURITY & BLOCKCHAIN RESEARCH ......................................................... 15 4.2.1 SYSTEMATIC LITERATURE ANALYSIS .............................................................................................................. 16 4.2.1.1 IDENTIFY, SELECT IN AND OUT, AND CLASSIFY THE LITERATURE ....................................................................... 17 4.2.2 ASSOCIATION ANALYSIS (CONTINGENCY TABLES AND PEARSON’S CHI-SQUARE TEST) .............................................. 23 4.2.2.1 DISCUSSION OF THE PEARSON’S CHI-SQUARE TEST’S RESULTS ........................................................................ 23 4.2.3 REQUIREMENTS SPECIFICATIONS ANALYSIS ..................................................................................................... 25 4.2.3.1 SPECIFICATIONS ................................................................................................................................... 25 4.2.3.2 Scope .......................................................................................................................................... 25 4.2.3.3 Cybersecurity and blockchain solutions ...................................................................................... 25 4.2.3.4 Requirements specification ........................................................................................................ 37 5 REFERENCES .......................................................................................................................................... 40 Page 3 of 54 SECURED BY BLOCKCHAIN D1 – LIUC UNIVERSITÀ CARLO CATTANEO - 20.01.2020 - ITALY 1 Executive summary This deliverable captures the SECURED BY BLOCKCHAIN project Requirements Specifications. It is a core specification document describing the project scope, approach and initial requirements specifications for developing a blockchain architecture in WP2. The purpose of the document is to provide the initial specifications of a cyber secure supply chain blockchain architecture. - T1.1 – Meta-analysis of the supply chain cyber security & and blockchain, - T1.2 – Identification of the cyber security requirements specifications for a blockchain architecture applied to supply chain transactions The document describes the scope, approach, and main components. The initial requirements specifications for SECURED BY BLOCKCHAIN include the following components: - Supply chain functions - Cyber risks - Blockchain security capabilities The document provides a consolidated table of requirement specifications for the above core components. Such specifications will be the ground field for the development of Key Performance Indicators (KPIs) in WP2. Page 4 of 54 SECURED BY BLOCKCHAIN D1 – LIUC UNIVERSITÀ CARLO CATTANEO - 20.01.2020 - ITALY 2 BACKGROUND 2.1 Introduction The fragility of international supply chains is evidenced with cyber-attacks like the one to Norsk Hydro’s operations in the U.S. and Europe in 2019 which left the company without automated production lines and running on manual production processes (Burton & Cho Walsgard, 2019). Cyber-attacks have costly consequences, for instance, it is reported an average cost of 3 million Euro for each cyber-attacks to Italian companies’ data in 2018 (Resilience360, 2018). The sources of cyber threat evolve over time. Hinde (2000) reported several cyberattacks leading to denial of services over the internet, like system’s failures, incompatibilities, uncertainty of safety of the systems for the users, internal threats, and so on. He also described the first large scale cyberattack to corporations like eBay, Amazon, CNN, latimes.com, with a computer virus ‘Stacheldraht’, which allows hackers to launch data traffic to targeted sites to saturate and block the websites. Surprisingly, although the cybersecurity community was aware of external threats, Vavra and Hromada (2015) explained how the protection of ‘Industrial Control Systems’ was still focused on insider threats and accidental malware introductions. It was only after the damage caused by the computer worm ‘Stuxnet’ in 2010, that the approach to cybersecurity changed radically to external threats because of information and communication systems’ growing openness (Langner, 2011). Solutions to cyber threats also evolve over time. Early cybersecurity consisted in authentication methods like passwords and PINs, access controls like firewalls, intrusion detection methods like exceeding number of users, and as reported by Yesberg and Henderson (2001) the cybersecurity community was much focused on the access to network components. Cybersecurity changed in early 2000’s to include real time threat analyses to network components (Chi, Park, Jung, & Lee, 2001). In mid2000’s operations research methods started playing a role for network survivability, intrusion detection, countering denial of service attacks, risk assessments, limit access to confidential data, legitimate access, and so on (Wright, Liberatore, & Nydick, 2006). In the early 2010’s the Supply chain cybersecurity made its great debut, with the inclusion three key factors: governance and organizational relationships tier, it and cyber-physical systems integration tier, and the operations and protocols tier (Boyson, 2014). Page 5 of 54 SECURED BY BLOCKCHAIN D1 – LIUC UNIVERSITÀ CARLO CATTANEO - 20.01.2020 - ITALY New technologies come with new risks,
Load more

Recommended publications
  • Idempiere ERP Modern, Scalable, Adaptable & Affordable Open Source ERP Solution for Enterprise
    iDempiere ERP Modern, Scalable, Adaptable & Affordable Open Source ERP Solution for Enterprise By Deptha Bagus Oc Current – Managing Director - Andromedia SAP Deployment Lead – Cargill APAC Quick Intro CEO – Avolut Global Indonesia · 2011 – 2016 About Me – Design SAP for Cargill Worldwide Instance – Deploy SAP over 10 company and 245 location in Asia Pacific region Attend BPM, ITSM, TGRC & PPM Course - – Implement iDempiere over 20 company with · various business model in Indonesia 2011 2010 – Entitle for EC Council Project Manager Founded Avolut Global · IT Manager for Sorini Agro Group Infor SyteLine Consulant with Sorini - 2009 · 2008 – Lead SAP B1 implementation with Join Andromedia – 2008 Soltius in Nigeria, Philipones & France Started ADempiere Team for SME project · · 2007 – Entitle for SAP Project Manager Functional SAP Consultant MM, PP, WM – · 7 completed project in 2 years 2006 2005 – Graduated from SI ITS Oracle OCP training & certification · – Join ABAP developer for Wings Started as Road Warior Programmer - 2003 · Group 2001 – Registered as SI ITS student Introduction A Glance on ERP 20 min Selecting ERP Products 20 min Open Source ERP 10 min Q&A 15 min iDempiere ERP in a Glance What is iDempiere ERP 30 min Functional Introduction 10 min Configurability & Extendability 15 min Features & Functional Overview 30 min Success Story 30 min Q&A 15 min A Glance About ERP and How to Select ERP’s • Facilitates Company-wide What Is ERP? integrated Information Systems Covering all functional Areas Software solution that addresses all and processes. the needs of an enterprise with the • Performs core Corporate process view of an organization to activities and increases meet the organizational goals and customer service augmenting integrate all the functions of the Corporate Image.
    [Show full text]
  • Idempiere Fixed Asset User Manual
    iDempiere Fixed Asset User Manual Created By Edwin Ang Created On June 12, 2012 Version 0.1 Introduction The iDempiere Fixed Asset extension package is developed based on the work of these three remarkable men: 1. Robert Klein, who developed the first ever Fixed Assets extension for Compiere 2. Teo Sarca, who modernized Robert Klein's work to use Adempiere more modern document structure. His work was however not properly documented and was influenced with his country local requirement. 3. Redhuan D. Oon (Red1), who took the work published by Teo Sarca, created the migration scripts from the 2Pack, and done some stabilization work. However Red1 somehow mixed Klein's solution to Teo Sarca's which made the design somehow inconsistent. This work was started from where red1 left. I have spent considerable hours try to understand all those three men's design consideration. Somehow, I decided to recover to Teo Sarca's core design and done the work to (1) repair bad codes and AD Configuration, (2) remove – what I thought was – localization codes and AD Configuration, and (3) add missing code and AD Configuration. After many many test iterations and two installation observations, I am confident that I have achieved a certainly working package. Hence this is the FA version 1.0. What functionality that can be expected in this FA v1.0: 1. Asset Addition from Match Invoice 2. Asset Addition from Import Asset 3. Asset Addition from Manual 4. Asset Addition from Project 5. Asset Depreciation using Straight Line Depreciation Method 6. Asset Disposal 7. Each document: Asset Addition, Asset Depreciation, and Asset Disposal can generate their own accounting facts What should not be expected: 1.
    [Show full text]
  • Connecting ERP and E-Commerce Systems
    MASARYKOVA UNIVERZITA FAKULTA}w¡¢£¤¥¦§¨ INFORMATIKY !"#$%&'()+,-./012345<yA| Connecting ERP and e-commerce systems DIPLOMOVÁ PRÁCA Ján Segé ˇn Brno, 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Ján Segéˇn Advisor: Ing. Leonard Walletzký, Ph.D. ii Acknowledgement I would like to express my gratitude to Ing. Leonard Walletzký, Ph.D. for his guidance and assistance during the writing of this thesis. Furt- hermore I would like to thank my family, friends, flat mates and my girlfriend for the continuous support and faith they have given me. The final thanks goes to my newly acquired angry birds mascot who has supplied me with luck for the duration of writing this thesis and hopefully will continue to do so. iii Abstract The goal of this thesis is to analyze and compare the way different online shops store and process information. Find useful similarities and utilize them to implement a tool that enables the open-source ERP system iDempiere to establish a communication link to the elect- ronic stores categorized as compatible, effectively giving iDempiere e-commerce capabilities. iv Keywords ERP,iDempiere, e-commerce, e-shop, electronic store, eConnect, plug- in, data connector, import, export, data synchronization v Obsah 1 Introduction ............................ 1 2 ERP Systems ............................ 3 2.1 History of ERP ........................ 4 2.2 ERP classification ...................... 6 2.3 Current trends in ERP ................... 7 2.4 Adapting ERP .......................
    [Show full text]
  • Customer Relationship Management Software February 2019
    CUSTOMER RELATIONSHIP MANAGEMENT SOFTWARE FEBRUARY 2019 Powered by Methodology CONTENTS 3 Introduction 5 Defining CRM Software 6 FrontRunners (Small Vendors) 8 FrontRunners (Enterprise Vendors) 10 Runners Up 24 Methodology Basics 2 INTRODUCTION his FrontRunners analysis graphic had a minimum qualifying Tis a data-driven assessment score of 4.01 for Usability and 4.11 identifying products in the Customer for User Recommended, while Relationship Management (CRM) the Small Vendor graphic had a software market that offer the minimum qualifying score of 4.31 best capability and value for small for Usability and 4.31 for User businesses. For a given market, Recommended. products are evaluated and given a score for Usability (x-axis) and To be considered for the CRM User Recommended (y-axis). FrontRunners, a product needed FrontRunners then plots 10-15 a minimum of 20 user reviews products each on a Small Vendor published within 18 months of the and an Enterprise Vendor graphic, evaluation period. Products needed based on vendor business size, per a minimum user rating score of category. 3.0 for both Usability and User Recommended in both the Small In the CRM FrontRunners and Enterprise graphics. infographic, the Enterprise Vendor 3 INTRODUCTION The minimum score cutoff to be included in the FrontRunners graphic varies by category, depending on the range of scores in each category. No product with a score less than 3.0 in either dimension is included in any FrontRunners graphic. For products included, the Usability and User Recommended scores determine their positions on the FrontRunners graphic. 4 DEFINING CRM SOFTWARE ustomer Relationship Software Advice’s FrontRunners CManagement (CRM) software is focused on the North American helps organizations manage CRM market.
    [Show full text]
  • Oprogramowanie Klasy Erp Dystrybuowane Na Zasadach Licencji Open Source
    OPROGRAMOWANIE KLASY ERP DYSTRYBUOWANE NA ZASADACH LICENCJI OPEN SOURCE Stanisław IWAN Streszczenie: Jedn ą z istotnych trudno ści, zwi ązanych z wykorzystywaniem technologii informacyjnych do wspomagania procesów zarz ądzania s ą wysokie koszty zwi ązane z opłatami licencyjnymi za oprogramowanie komputerowe. Mog ą one ulec znacznemu obni żeniu przy zastosowaniu alternatywnych metod dystrybuowania programów. W opracowaniu przedstawiono ogólne zało żenia licencji open source oraz wybrane przykłady systemów klasy ERP dystrybuowanych na jej zasadach. Słowa kluczowe: ERP, licencje oprogramowania, otwarte oprogramowanie, open source, technologie sieciowe. 1. Wprowadzenie Jedn ą z istotnych trudno ści, zwi ązanych z wykorzystywaniem technologii informacyjnych do wspomagania procesów zarz ądzania s ą wysokie koszty z tym zwi ązane. Cho ć znaczn ą ich cz ęść stanowi ą koszty zakupu i eksploatacji sprz ętu komputerowego, to jednak koszty zakupu licencji oprogramowania mog ą w wielu wypadkach (szczególnie w odniesieniu do mocno wyspecjalizowanych zada ń) stanowi ć element dominuj ący i niekiedy znacznie przewy ższa ć koszty sprz ętu. Dodatkowo firmy software’owe stosuj ą ró żne metody utrzymania klientów i zapewnienia sobie stałego dopływu opłat licencyjnych. Przykładem niechaj b ędą niektóre kontrowersyjne zapisy, zawarte w umowach licencyjnych jednego z producentów, mówi ące, że: − użytkownik nie jest wła ścicielem oprogramowania, które zakupił; − użytkownik nie mo że uruchamia ć wi ęcej ni ż jednej kopii systemu; − system operacyjny stanowi cz ęść zestawu oprogramowanie-komputer, nie mo że zatem by ć u żytkowany na komputerze innym, ni ż ten na którym został zainstalowany i zarejestrowany po raz pierwszy; − producent nie ponosi odpowiedzialno ści za straty, jakie poniesie u żytkownik w skutek u żytkowania systemu (pomimo wysokich opłat licencyjnych).
    [Show full text]
  • Idempiere About Idempiere Idempiere Is a Powerful, Open-Source ERP/CRM/SCM System Targeted to Medium and Big Companies and Supported by a Skilful Community
    iDempiere About iDempiere iDempiere is a powerful, open-source ERP/CRM/SCM system targeted to medium and big companies and supported by a skilful community. The project focuses on high-quality software, a philosophy of openness and its collaborative community that includes subject matter specialists, implementers, developers and end-users. Our mission is to help companies around the world to grow with freedom. To do this, we focus on high-quality code and we have established a culture that supports, recognizes, and respects our great community, so they can share their knowledge with the world. The project is built with ZK, Maven, PostgreSQL or Oracle, Jetty, OSGi and it is written mainly in Java. The challenge Having a worldwide community present tough challenges such as coordinating different needs without letting the code to become a mess. By making contributors use the ZK Java approach consistently, ZK helps us address this challenge. Furthermore, handling client-side validations in this kind of software could be a tedious and risky task as it consumes plenty of development time and when done sloppily it opens security breaches. ZK's server-centric approach lets us control all validations on the server without exposing unnecessary data. Why ZK? Formerly the project front end was built using Swing. When we recognized the need to switch to new web-based technology, there was an attempt to create a web interface with JSF, but that didn't get enough interest and traction from the community. One community member developed a proof of concept using ZK, this allowed us to identify that the switch from Swing to ZK was more natural as there were similar concepts and components.
    [Show full text]
  • The Integration of Idempiere and Wanda POS Documentation
    The Integration of iDempiere and Wanda POS Documentation By Ing. Tatioti Mbogning Raoul Under the direction of : Dr.-Ing Stanley A. Mungwe Sponsored by IT Kamer Company Ltd, Cameroon Table of Contents 1 iDempiere’s Wanda POS Integration Plugin 5 1.1 Download the plugin . .5 1.2 Install the plugin . .5 2 Use the plugin 7 2.1 Wanda POS iDempiere’s Menu . .9 2.2 Setup ActiveMQ in iDempiere . .9 2.3 Start ActiveMQ Server . 11 2.4 Add Product in iDempiere . 13 2.5 Export Products and Customers from iDempiere . 15 2.6 Import Products and Customers to Wanda POS . 18 2.6.1 New Products . 21 2.6.2 New Customers . 23 2.7 Export Orders from Wanda POS . 23 2.7.1 Place Orders . 24 2.7.2 Orders Synchronization . 25 2.8 Import Orders to iDempiere . 26 2.8.1 Process Imported Orders . 28 2.9 Stop ActiveMQ Server . 29 2.10 Wanda POS Synchronisation Workflow . 30 3 Thanks 30 4 About Me 30 Copyright (c) 2014 IT-Kamer Company LTD1 Ing. Tatioti Mbogning Raoul List of Figures 1 Apache Felix Web Console . .5 2 Install or Update Wanda POS Plugin . .6 3 Wanda POS Plugin . .6 4 iDempiere login account . .7 5 iDempiere login account . .8 6 Wanda POS Synchronization Menu . .9 7 Start ActiveMQ Server from iDempiere . 11 8 ActiveMQ Web Admin . 12 9 Add Product in iDempiere . 13 10 Product Price List in iDempiere . 14 11 Product Price List in iDempiere . 14 12 Export Data to Queue Process . 15 13 Export Data to Queue Result .
    [Show full text]
  • Gnuaccounting Manual
    Gnuaccounting Manual 1/39 Table of Contents 1 Requirements, installation and start...................................................................................5 1.1 System requirements...................................................................................................5 1.2 Installation....................................................................................................................5 1.3 In Windows..................................................................................................................5 1.3.1 With the installer package....................................................................................5 1.3.2 With the Zip-file.....................................................................................................5 1.3.3 In 64bit Windows..................................................................................................5 1.3.4 The portable version for USB-Sticks....................................................................6 1.3.5 Gnuaccounting standalone and OpenOfficePortable...........................................7 1.3.6 Gnuaccounting and LibreOffice............................................................................7 1.4 In Linux........................................................................................................................7 1.4.1 Ubuntu, SuSE.......................................................................................................7 1.4.2 OpenSuSE experimental......................................................................................8
    [Show full text]
  • Facultad De Ingeniería Carrera Profesional De Ingeniería De Sistemas E Informática
    UNIVERSIDAD PRIVADA DE TRUJILLO FACULTAD DE INGENIERÍA CARRERA PROFESIONAL DE INGENIERÍA DE SISTEMAS E INFORMÁTICA CRITERIOS DE EVALUACIÓN PARA LA SELECCIÓN DE UN SISTEMA ERP OPEN SOURCE PARA LA EMPRESA INVERSIONES AVÍCOLA GÉNESIS, TRUJILLO, 2020. TESIS PARA OPTAR EL TÍTULO PROFESIONAL DE INGENIERO DE SISTEMAS E INFORMÁTICA AUTOR: Bach. Kennedy Vidal Valverde Alvites ASESOR: Ing. José Alberto Gómez Ávila Trujillo – Perú 2021 CRITERIOS DE EVALUACIÓN PARA LA SELECCIÓN DE UN SISTEMA ERP OPEN SOURCE PARA LA EMPRESA INVERSIONES AVÍCOLA GÉNESIS, TRUJILLO, 2020. APROBACIÓN DE LA TESIS El asesor y los miembros del jurado evaluador asignados, APRUEBAN la tesis desarrollada por el Bachiller Kennedy Vidal Valverde Alvites, denominada: “CRITERIOS DE EVALUACIÓN PARA LA SELECCIÓN DE UN SISTEMA ERP OPEN SOURCE PARA LA EMPRESA INVERSIONES AVÍCOLA GÉNESIS, TRUJILLO, 2020” Dr. Gómez Ávila José Alberto PRESIDENTE Mg. Santos Fernández Juan Pedro SECRETARIO Mg. Díaz Díaz Franklin Alexis VOCAL VALVERDE ALVITES, KENNEDY VIDAL Pág. ii CRITERIOS DE EVALUACIÓN PARA LA SELECCIÓN DE UN SISTEMA ERP OPEN SOURCE PARA LA EMPRESA INVERSIONES AVÍCOLA GÉNESIS, TRUJILLO, 2020. DEDICATORIA A Dios todopoderoso, creador de los cielos y la tierra, el Alfa y la Omega, el que es y que era y que ha de venir. A mi padre Vidal y a mi madre Alvina, con mucho amor. A mis hermanos Joel, Benony, Paúl, Rafael y mi hermana Jackelyne, en mis alegrías y tristezas, con mucho cariño. VALVERDE ALVITES, KENNEDY VIDAL Pág. iii CRITERIOS DE EVALUACIÓN PARA LA SELECCIÓN DE UN SISTEMA ERP OPEN SOURCE PARA LA EMPRESA INVERSIONES AVÍCOLA GÉNESIS, TRUJILLO, 2020. AGRADECIMIENTO A mi Dios Eterno, por darme la vida, la sabiduría, por cuidarme y guiarme en sus caminos.
    [Show full text]
  • Implementation of Idempiere Erp on Human Resources Management Module (A Case Study Approach)
    International Journal of Mechanical Engineering and Technology (IJMET) Volume 9, Issue 9, September 2018, pp. 338–347, Article ID: IJMET_09_09_037 Available online at http://iaeme.com/Home/issue/IJMET?Volume=9&Issue=9 ISSN Print: 0976-6340 and ISSN Online: 0976-6359 © IAEME Publication Scopus Indexed IMPLEMENTATION OF IDEMPIERE ERP ON HUMAN RESOURCES MANAGEMENT MODULE (A CASE STUDY APPROACH) Yohannes Kurniawan, Vina Georgiana, Vincent Paruh, Jorvan and Anton Emil Information Systems Department, School of Information Systems, Bina Nusantara University, Jakarta, Indonesia 11480 ABSTRACT The purpose of this research is to design and implement iDempiere ERP System on Human Capital Management Module using the Accelerated SAP (ASAP) method that refers to business blueprint and realization. The analysis is performed on the current business process, then the result will be converted into the blueprint design of the proposed system, furthermore the blueprint design of the proposed system will be configured into the iDempiere ERP. The proposed system can help company especially Human Resources and General Departments for conducting activities related to human resources, otherwise it will facilitate employees to be able to perform permission activities through Employee Self Service System. Keywords: Human Capital Management, Enterprise Resource Planning, iDempiere ERP, Accelerated SAP. Cite this Article: Yohannes Kurniawan, Vina Georgiana, Vincent Paruh, Jorvan and Anton Emil, Implementation of Idempiere Erp on Human Resources Management Module (A Case Study Approach), International Journal of Mechanical Engineering and Technology, 9(9), 2018, pp. 338–347. http://iaeme.com/Home/issue/IJMET?Volume=9&Issue=9 1. INTRODUCTION Today, information technology and information systems has grown very quickly and influential in business world.
    [Show full text]
  • Application of Open-Source Enterprise Information System Modules: an Empirical Study
    University of Nebraska - Lincoln DigitalCommons@University of Nebraska - Lincoln Dissertations, Theses, and Student Research from the College of Business Business, College of Summer 7-20-2010 APPLICATION OF OPEN-SOURCE ENTERPRISE INFORMATION SYSTEM MODULES: AN EMPIRICAL STUDY Sang-Heui Lee University of Nebraska-Lincoln Follow this and additional works at: https://digitalcommons.unl.edu/businessdiss Part of the Management Information Systems Commons, Other Business Commons, and the Technology and Innovation Commons Lee, Sang-Heui, "APPLICATION OF OPEN-SOURCE ENTERPRISE INFORMATION SYSTEM MODULES: AN EMPIRICAL STUDY" (2010). Dissertations, Theses, and Student Research from the College of Business. 13. https://digitalcommons.unl.edu/businessdiss/13 This Article is brought to you for free and open access by the Business, College of at DigitalCommons@University of Nebraska - Lincoln. It has been accepted for inclusion in Dissertations, Theses, and Student Research from the College of Business by an authorized administrator of DigitalCommons@University of Nebraska - Lincoln. APPLICATION OF OPEN-SOURCE ENTERPRISE INFORMATION SYSTEM MODULES: AN EMPIRICAL STUDY by Sang-Heui Lee A DISSERTATION Presented to the Faculty of The Graduate College at the University of Nebraska In Partial Fulfillment of Requirements For the Degree of Doctor of Philosophy Major: Interdepartmental Area of Business (Management) Under the Supervision of Professor Sang M. Lee Lincoln, Nebraska July 2010 APPLICATION OF OPEN-SOURCE ENTERPRISE INFORMATION SYSTEM MODULES: AN EMPIRICAL STUDY Sang-Heui Lee, Ph.D. University of Nebraska, 2010 Advisor: Sang M. Lee Although there have been a number of studies on large scale implementation of proprietary enterprise information systems (EIS), open-source software (OSS) for EIS has received limited attention in spite of its potential as a disruptive innovation.
    [Show full text]
  • History of SAP R/3 Releases Organization
    From Wikipedia, the free encyclopedia SAP R/3 is the former name of the main enterprise resource planning software produced by SAP AG. It is an enterprise-wide information system designed to coordinate all the resources, information, and activities needed to complete business processes such as order fulfillment or billing.[1] History of SAP R/3 The first version of SAP's flagship enterprise software was a financial Accounting system named R/1 called as YSR. This was replaced by R/2 at the end of the 1970s. SAP R/2 was in a mainframe based business application software suite that was very successful in the 1980s and early 1990s. It was particularly popular with large multinational European companies who required soft-real-time business applications, with multi-currency and multi-language capabilities built in. With the advent of distributed client–server computing SAP AG brought out a client–server version of the software called SAP R/3 (The "R" was for "Real-time data processing" and 3 was for 3-tier). This new architecture is compatible with multiple platforms and operating systems, such as Microsoft Windows or UNIX. This opened up SAP to a whole new customer base. SAP R/3 was officially launched on 6 July 1992. It was renamed SAP ERP and later again renamed ECC (ERP Central Component). SAP came to dominate the large business applications market over the next 10 years. SAP ECC 5.0 ERP is the successor of SAP R/3 4.70. The newest version of the suite is SAP ERP 6.0 – the path to SAP Business Suite 7.
    [Show full text]