How might a project team recommending an ERP design strategy justify its recommendation as compared with other types of design strategies?
[Student: The followingis also attached as a Word document]
I have worked in the field of designing, building, and supporting ERP systems for nearly fifteen years. For an enterprise (the "E" in ERP), the ERP design strategy like all aspects of this very important capital investment is about ROI: Return On Investment. How soon can a return begin and what will the total return be? Your question is specifically about ERP design strategy which is one phase, an initial phase. Considerations similar to what I am about to say can be considered for other phases, such as development, implementation, support, and end of life.
I can guarantee you that a competent project team recommending an ERP design strategy will justify its recommendation as compared with other types of design strategies based largely if not entirely on attributes of that plan will produce a quick and complete return on that investment. Specifically, some considerations may be:
- Will the design support outsourcing so that staffing needs during ...
Solution is a 680-word Word document covering current and recent considerations an ERP project team will consider.