Биография Наука Обучение SAP Программы Достижения Новости    Услуги RU















































































































































Обучение

Статья


Автор

Организация


Ссылка


Abstract: it's induction session dedicated to problem domains of ERP-system realization, including low level modelling techniques based on responsibility to project processes; basic development concepts to compile programs; all testing approaches to test software and cutover strategies to go-live.
Keywords: enterprise resource planning, erp, enterprise resource planning systems, erp-systems, erp software, management information systems, erp system implementation, erp software implementation timeline, phases of ERP implementation, stages of ERP implementation, business process modeling, program development process, cutover planning & management, cutover strategy, system cutover strategy.


Enterprise resource planning systems implementation projects can last more than a year. During the implementation, all team members get accustomed to designs so that there are no questions like «how, why and for what it’s done like this». Unfortunately, while solving similar problems in the future the only explanation will be «it’s done this way previously». It is definitely wrong due to there is a basic theory of enterprise resource planning systems. Moreover, participation in different projects should provide alternative while taking designs. The course «Analysis, design and development of enterprise resource planning systems» will describe these issues. And first we'll start from fundamental terms and definitions. Enterprise resource planning (or ERP) is a strategy of logistics, finance and human integration to optimize enterprise resources by means of special program applications. ERP-system is a program application to realize this strategy. Following the definitions next question arises: are ERP and ERP-system synonyms?

Рубрикатор
Теория
Тренинг
Тренинг1
SAP

We defined ERP-system, let’s go to implementation process. Most of implementation methodologies are delivered by vendors, such as: MDSS from Microsoft, OUM from Oracle and ASAP from SAP. However, inspite of methodology, one can highlight typical implementation stages. Having explored logical relationships between activities, contents and durations of each stage, we can give an answer to the question: why are there no some stages like pilot run in the projects? There are a lot of persons involved in ERP-system implementation such as technical specialists, business consultants, managers etc. The more people involved the more chaos exists because of responsibility mixture. For instance, does consultant have to be worried about deadlines, content approvals and budget exceeding? The answer is related to ERP-system implementation levels. ERP-system can be considered as a set of information systems integrated together within corporation. Therefore, basic principles of information system designs can be used to implement ERP-system. Is there only one cascade model of ERP-system implementation? Definitely, not. We can start business process analysis, having chosen methodology as well as implementation model. The ways exploring business processes are not restricted only by discussions at a time processes can be projected by means of IDEF, DFD, UML and ARIS methods. In real life CASE-technologies are not used well enough. Then why business processes typically modeled using ARIS eEPC notation?

Explored business processes are used for Fit/Gap-analysis, including comparison of business requirements and standard ERP-system functionality. Functional shortage has to be covered by system development which usually carried out upon program specifications. We have a question, is it possible to select universal requirements applied to any program development? Developed ERP-system is displayed to customer. Project documentation is prepared after successful integration testing and resolving critical defects. Next end users have to be trained so that training materials are going to be ready. Which approaches do exist to shape training instructions? What are their advantages and disadvantages? Pilot run means the end of ERP-system implementation process. Final step is cutover to production usage. Here we face questions regarding data migration and cutover strategy. Why does system go-live at the beginning of the year? What’s the most safety cutover strategy? Answers to these questions will be given within training «Analysis, design and development of enterprise resource planning systems».

References

  1. Stepanov D.Yu. Analysis, design and development of enterprise resource planning systems: theory and practice // Russian technological journal. – 2015. – vol.8, №3. – p.227-238 (in Russian).
  2. Stepanov D.Yu. ERP-system implementation issues: application level // Management today. – 2015. – vol.87, №3. – p.180-191 (in Russian).
  3. Stepanov D.Yu. ABAP-programs universal requirements to prepare software module specification // Open issues of science. – 2014. – vol.78, №4. – p.258-268 (in Russian).



Рейтинг@Mail.ru Яндекс.Метрика



Дмитрий Степанов корпоративные информационные системы, КИС, САП, логистика http://stepanovd.com/search_display_1.png к.т.н., доц. МГТУ МИРЭА
Training «Analysis, design and development of enterprise resource planning systems: abstract» enterprise resource planning, erp, enterprise resource planning systems, erp-systems, erp software, management information systems, erp system implementation, erp software implementation timeline, phases of ERP implementation, stages of ERP implementation, business process modeling, program development process, cutover planning & management, cutover strategy, system cutover strategy Dmitry Stepanov 2017-07-27
Права защищены