Customers: Energomash of V.P. Glushko of NGO Khimki; Mechanical engineering and instrument making Contractors: Galaktika Corporation Product: Galaktika ERPSecond product: Galaktika AMM (Advanced Manufacturing Management) Project date: 2016/11
|
Content |
Since the end of 2016 the largest Russian enterprise for development of rocket engines of NPO Energomash entering into Roskosmos state corporation conducts the ERP system implementation project based on solutions Galaktika. Fully it is going to finish it in March, 2019.
Project Progress
As there was a choice of the solution and why SAP did not pass
In April, 2018 the Deputy CEO for development of IT NPO Energomash Denis Savenkov told how there was a choice of vendor of products for creation of the ERP system of the enterprise. The short list was initially created from systems which in NPO Energomash considered the most suitable. It included 1C, Galaktika Corporation, SAP and Raytstep.
In a case with SAP earlier successful experience of its implementation at the manufacturing enterprise of engines for carrier rockets JSC "Proton" - "JSC "Proton" – Perm Motors" (enters into NPO Energomash) was considered, Savenkov says. But in the area of a security service of state corporation with which the project was approved at that time "prohibition on communication" with SAP was delivered.
It were harbingers of import substitution, sanctions, risk of information leaks, the representative of NPO Energomash argues. Thus, the question was removed from SAP, and 1C and Galaktika remained the main applicants.
NPO Energomash also initiated comparative testing of SAP solutions, 1C and Galaktika for a period of one month on the tasks conforming to requirements of the enterprise. During tests, follows from Savenkov's words, Galaktika proved best of all, SAP appeared with it practically in parity, and 1C was shown by the least satisfactory result for the enterprise.
Denis Savenkov called customization and support of a product by vendor one of the major moments and noted that there can be problems when the vendor switches the customer to the partner and if something goes not so, advises the partner to replace, and itself is not responsible for result.
It is necessary to understand: the vendor does not bear any responsibility for your project, for result. The vendor says that there is a partner, and work with it, - Savenkov noted. |
It should be noted that at a project startup of Galaktika of NPO Energomash only just stopped implementing 1C regarding accounting and tax accounting.
When began to start Galaktika, it appeared - and why to us 1C? In Galaktika there are all "supporting documents", postings form automatically. And in what sense to keep one more system? – Savenkov shared. |
As a result, having weighed all circumstances, the decision of 1C to refuse was made.
Start of Project
The project started in November, 2016. It was preceded by a number of works:
- March-April, 2016: inspection, interview, internal departures, discussion of volumes, selection of priority tasks;
- April-May, 2016: data preparation of a control example, input and demonstration of the control example implemented by standard means of systems, discussion of necessary completions;
- June-July, 2016: formation of offers on a scope and project cost, discussion and protection of offers;
- August-September, 2016: approvals, holding competitive procedures.
By July, 2017 subsystems of the first stage were designed, there was their setup and preparation of commercial operation.
Functional scope of a system
Business process automation before implementation of ERP
According to Denis Savenkov, the low level of automation of the basic and auxiliary business processes at the enterprises of the integrated structure and scrappy automation of the "legacy" information systems which are not integrated among themselves took place earlier. Besides, there was incomplete and irrelevant a normative reference information.
At everything at the same time, Savenkov noted, the enterprise functioned and turned out products in time.
After the Roskosmos state corporation created from Federal Space Agency was formed radical reorganization of all industry began, there were problems of performance improvement and cost reduction. It found reflection in the created "Program of strategic conversions" which provided, including, creation by the centralized ERP at the enterprises connected with the central systems of Roskosmos.