<< 1 >>
Rating: 
Summary: Insightful!
Review: Because this is a dense read, you won't be surprised to learn that the author, Daniel E. O'Leary, is a Ph.D. If you don't have a conversational grasp of acronyms - including, but not limited to ERP, LAN, WAN, SMEs BOPSE, MAPs, SAP and BAAN - then you'll have to decode as you read. If you're actually interested in using the business resource known as "Enterprise Resource Planning," or ERP, your company should be grossing some $200 million a year, because ERP costs about $15 million to implement. While O'Leary makes a very compelling case in favor of ERP, citing integration of information infrastructure, real-time data, value creation and other wonderful attributes, this is a very expensive and risky resource to pursue. Companies such as Microsoft and Cisco had a hard time implementing it and even they have to worry about cost. We [...] warn that this is serious tech for Big Money companies. Mom and Pop operations need not apply.
Rating: 
Summary: Comprehensive, cases, reference; one of great writing
Review: O'Leary did an excellent job in compiling the story of ERP in a single book. Unlike other ERP book, O'Leary provides the fundamental, technical, and practical of ERP system. Many presented cases are well organized with the contents in the book. The long case is brought up on and off to remind reader about the process. If you like "Why ERP?" by Jacobs but want more technical and further reference, please grasp this book and study it. Many references are provided for further research as well. Well done!!
Rating: 
Summary: Most issues are shared with usual IS
Review: The book does not lack interesting subjects, but most of them are not peculiar of ERP systems, and could be suitable for many other kinds of software systems. Gap analysis, costs, human resources and chains are problems people are dealing with since the first computer entered the business word. I would have liked a publication in which briefly summarized process and data issues would be referred to a proper functional, and even technological, architecture of ERP. I do need buy and read a book whose title is ERP in order to get a description of the problems whilst the book is supposed to dissert about their solutions. The latter target has been someway met, but not fully reached.
Rating:
Summary: Due diligence if you're evaluating ERP systems
Review: This book is more suited as an executive guide for anyone who is considering ERP or evaluating ERP systems. In fact, the book appears to have been designed with busy senior management and executives in mind because it's focused, hits all of the key points and each chapter is treated as a whitepaper that ends with case studies reinforcing the topic and references. Also, the author makes excellent use of window diagrams throughout to convey information. A random example if this is in chapter 11 where the linkage between implementation approach (big bang vs. phases) is shown by impact of the extent of changes to be made to ERP modules (minimal to extensive) vs. Number of modules in implementation (few to many) and how this translates to the preferred method. This is but one of many such examples.The book is organized into four parts: (1) introduction, (2) ERP systems and capabilities, (3) ERP life cycle (deciding, selecting, designing, post implementation and training) and (4) electronic commerce and risk. Each section is backed with cited references and necessary facts with which to decide whether or not to opt for an ERP system, and if so, how to select the correct package. The references and citations extend into every chapter, which I liked because when the author cites a fact, such as a typical cost of an ERP implementation ... you know where that figure came from. I normally do not like discussions of specific products in general books, but given the narrow field of ERP vendors the discussion of each of the major players, their company histories and market position is appropriate for this book given the subject and audience. I personally liked the case studies at the end of each chapter because there were specific to the chapter's topic, were drawn from real life, and were frank about the problems encountered and how they were addressed. This is a gold mine for executive management seeking to determine the true scope, cost and potential value of an ERP project. I also like how each option for implementation was thoroughly covered. Overall, this book provides complete coverage of all of the issues and factors that need to be examined before taking the plunge into an ERP system. It will definitely allow executive management to make informed decisions, and will also prepare IT and business stakeholders for the realities of an implementation. This book will pay for itself many times over for the intended audience. It is clear, concise and factual.
Rating:
Summary: Due diligence if you're evaluating ERP systems
Review: This book is more suited as an executive guide for anyone who is considering ERP or evaluating ERP systems. In fact, the book appears to have been designed with busy senior management and executives in mind because it's focused, hits all of the key points and each chapter is treated as a whitepaper that ends with case studies reinforcing the topic and references. Also, the author makes excellent use of window diagrams throughout to convey information. A random example if this is in chapter 11 where the linkage between implementation approach (big bang vs. phases) is shown by impact of the extent of changes to be made to ERP modules (minimal to extensive) vs. Number of modules in implementation (few to many) and how this translates to the preferred method. This is but one of many such examples. The book is organized into four parts: (1) introduction, (2) ERP systems and capabilities, (3) ERP life cycle (deciding, selecting, designing, post implementation and training) and (4) electronic commerce and risk. Each section is backed with cited references and necessary facts with which to decide whether or not to opt for an ERP system, and if so, how to select the correct package. The references and citations extend into every chapter, which I liked because when the author cites a fact, such as a typical cost of an ERP implementation ... you know where that figure came from. I normally do not like discussions of specific products in general books, but given the narrow field of ERP vendors the discussion of each of the major players, their company histories and market position is appropriate for this book given the subject and audience. I personally liked the case studies at the end of each chapter because there were specific to the chapter's topic, were drawn from real life, and were frank about the problems encountered and how they were addressed. This is a gold mine for executive management seeking to determine the true scope, cost and potential value of an ERP project. I also like how each option for implementation was thoroughly covered. Overall, this book provides complete coverage of all of the issues and factors that need to be examined before taking the plunge into an ERP system. It will definitely allow executive management to make informed decisions, and will also prepare IT and business stakeholders for the realities of an implementation. This book will pay for itself many times over for the intended audience. It is clear, concise and factual.
<< 1 >>
|
