dc.contributor.author | Haddara, Moutaz | |
dc.contributor.author | Elragal, Ahmed | |
dc.date.accessioned | 2011-10-10T11:33:04Z | |
dc.date.available | 2011-10-10T11:33:04Z | |
dc.date.issued | 2011 | |
dc.identifier.citation | Haddara, M., & Elragal, A. (2011). ERP lifecycle: When to retire your ERP system? In M. M. Cruz-Cunha, J. Varajao, P. Powell & R. Martinho (Eds.), Enterprise Information Systems (Vol. 219, pp. 168-177): Springer. | en_US |
dc.identifier.isbn | 978-3-642-24351-6 | |
dc.identifier.uri | http://hdl.handle.net/11250/136285 | |
dc.description | Published version of a chapter in the book: Enterprise information systems, vol 219, part 3, 168-177. Also available from the publisher at: http://dx.doi.org/10.1007/978-3-642-24358-5_17 | en_US |
dc.description.abstract | A lot of research has been undertaken focusing on ERP systems lifecycles, but very little paid attention to retirement. ERP retirement means the replacement of an ERP with another. The aim of this research paper is to investigate why and when should organizations retire their ERP systems. A convenience case study of an SME has been selected from Egypt. The case study under investigation has retired their local ERP system and replaced it with SAP ERP. Results of our analysis indicated that reasons of retirement were: wrong selection, users were not involved in the selection process, and lack of an official implementation methodology. This is considered a new finding since main stream literature was mainly focused on retirement after maturity. | en_US |
dc.language.iso | eng | en_US |
dc.publisher | Springer | en_US |
dc.relation.ispartofseries | Communications in Computer and Information Science;219 | |
dc.source | Enterprise information systems | |
dc.subject | ERP, retirement, lifecycle, case study | en_US |
dc.title | ERP lifecycle: When to retire your ERP system? | en_US |
dc.type | Chapter | en_US |
dc.type | Peer reviewed | en_US |
dc.subject.nsi | VDP::Social science: 200::Library and information science: 320::Information and communication systems: 321 | en_US |
dc.source.pagenumber | 168-177 | en_US |