Office 548, Bldg. 1, 55/59 Bolshaya Pochtovaya St., Moscow 105082 (Elektrozavodskaya metro station)

ERP implementation methodology for large enterprises and holding companies

ERP implementation methodology for large enterprises and holding companies

For large companies and holdings.

This methodology is designed for migrations from SAP and Oracle to 1C. It is also suitable for migrating from legacy 1C systems to more modern ones (for example, from 1C:UPP to 1C:ERP).

*Not suitable for the public sector or small businesses.

Most implementation projects fail because the client does not understand the need, or is not prepared, to devote enough time to the project and to work on it promptly. Unfortunately, a team cannot simply come in, set everything up, and leave. It is the client who must provide the information, make adjustments, test the results, make key decisions as the project progresses, and accept the completed work. Our methodology lets us see the project through to results, while the client takes part in every stage, stays informed, and can influence the process, and so ends up with exactly what it wanted.

Every project has to meet its deadlines, stay on budget, and achieve its goals.

Every client’s goal is to

1) move to the new system on time and within budget,

2) preserve key, business-critical processes without losing efficiency,

3) keep customizations in the new system to a minimum, since they always mean extra development and future support costs.

Implementing a new system is first and foremost consulting. Whereas implementations used to be driven by developers, today most of the work is done by analysts. The better the analysis, the fewer customizations are needed.

Key project tasks:

Stage 1: Design.

- Analyze the company’s current business processes and document them so that the Contractor and the Client share a single view of all processes.

- Model these processes in the new system. This means taking real documents and processes and trying to replicate them in the new system. We run a demo for the client and, based on the results, record the “bottlenecks” (functional gaps) that would prevent the system from working correctly.

When data has to be migrated from the old system to the new one, the scope of data to be migrated must be agreed on and migration tools developed.

Stage 2: Development.

Once critical gaps are identified, we develop solutions and agree on them with the client, showing the results of our work every week so that the client understands what they will get and can also steer the development.

Stage 3: Pilot operation.

A common problem: development is done and data is loaded, but the system doesn’t work because of errors. That is why comprehensive testing is needed.

We run 3 types of testing:

Internal testing: a complete end-to-end run of the system in-house, led by the technical and functional architects.

External testing: the same run, but this time together with the client. At this point, the client can request adjustments.

Acceptance testing: we prepare step-by-step test cases, and the client goes through the entire process on their own to check how the system works.

Based on the results, we fix any errors, prepare user guides, and train employees.

Stage 4: Full production use.

We always support the project for 3–6 months after go-live while employees get used to the system.

It is best to present all project information (plans, schedules, goals, and results) to the client as a presentation. This gives the client a first picture of the outcome. Clients usually do not realize that they, too, will have to do certain work. A presentation makes this clear.

Implementation cannot be left to the contractor’s team alone. By showing the scope of joint work, we effectively set out the rules on which the project’s success depends. Below is a table showing how the client’s employees are involved.

The project sponsor approves final decisions, allocates the budget, and accepts the project as a whole.

The project manager is the administrator of the entire project. For example, the provider has no authority within the client’s company, so an internal project manager is needed who can demand the necessary discipline from their subordinates.

Key users are the owners of the main areas for which we implement the system. They are usually department heads. For example, if we are implementing the finance module, this is the CFO, and so on.

Expert on the system we are migrating from. This is a technical specialist who prepares data in the existing system for migration to the new one.

IT specialists who work with external systems, grant the necessary access, provide internal tools, and carry out the required server work.

During implementation, we must always stay on schedule and within budget. However, people usually want to take their old system, customized over many years, and move it entirely into the new one, adding new requirements along the way; in other words, to take 1C and turn it into SAP. But let’s be realistic: you cannot achieve in six months to a year what took many years and huge budgets to build. In such cases, customization costs exceed the budget 3–4 times over.

So how do you decide what to do to stay within budget?

Here is how we resolve this conflict.

We propose ranking all business processes by criticality.

  • High: processes without which the company will “break down” and be unable to operate.
  • Medium: processes whose absence slows work down.
  • Low: wish-list items, convenience features, and nice-to-have improvements.

The budget usually covers the high-priority processes and part of the medium-priority ones. Low-criticality items are deferred to later development of the system.

Our experience shows that it is possible to complete implementation on time and within the planned budget by delivering the high- and medium-priority items. At go-live, however, usually only the high-criticality items are in place. Only after go-live do you continue refining the system, for one year, two, or even 10 years.

If you try to do everything at once, the project will stall, and we will not meet the schedule or the budget.

That is why we:

  1. implement the high-priority items first;
  2. finish the medium-priority items during full production use;
  3. then keep refining the system for years, as needed.

This phased approach gives the best chance of achieving the desired result.

Our ten years of experience in IT have helped us develop a methodology that answers the key project questions: how to implement automation on schedule and within budget with minimal customization, while preserving critical business processes and efficiency.

ERP case studies

Have questions? Write to us!

    or pick a time right away
    Book a free 1C:ERP project review →
    30 minutes online with a project manager. Pick a time that suits you in the calendar.