Better quality, lower cost

Highest quality of ERP implementations. We treat each client individually, first recognizing his needs, and then, together with him, we build an optimal service support plan and a model of consulting cooperation. Thanks to the comprehensive environment and the service and implementation platform, we provide faster and better implementations and migrations, an efficient post-implementation service including adjustments to changing and new legal regulations, with the option of a flat-rate settlement of consulting works related to their implementation.


Comprehensive and modern methodology combining the best practices of Waterfall and Scrum technologies.

Implementation portal – to carry out some of the implementation works: building a prototype, data migration, process testing – thanks to which you can significantly reduce the costs of implementation or system migration.

Datacentre services (cloud) for the running environment – if such a model is chosen by the customer.

Internet service center – supporting the communication of our service department with the client as part of the reports registered by him.

L-Systems implements and migrates the ERP IFS system based on the Waterfall methodology, with the simultaneous use of elements of the agile methodology – Scrum. Thanks to this approach, we are able to determine the duration and budget of the project (cascade methodology) while being highly open to changes in the concept of the solution being developed (agile methodology). Our approach allows us to provide a system that is as best suited to the client’s requirements as possible, while significantly reducing the costs of implementation or migration (over 30%) and building high competences of the client’s employees in the use of the system, along with the ability to independently implement business issues, from the very first working day in the running system.


We are able to achieve excellent quality effects of implementations and migrations with a simultaneous reduction of costs by several dozen percent thanks to the fact that:

1. During the analysis stage, we focus on discussing the processes specific to a given company, e.g. production, configurator operation, discussing service activities. For them, maps are built based on the EPC methodology. Other processes typical for most enterprises, e.g. accounting, purchasing, sales and HR processes, are discussed in terms of identifying possible nuances specific to a given enterprise, and maps are not built for these processes.

2. The scope of the prototype documentation covers the method of implementation of processes in the IFS system. Elements that are irrelevant to the course of the process, e.g. dictionaries, global settings, etc., are not described.

3. Development of job instructions (if required) is on the part of key users. Key users are able to create instructions based on the prototype document, knowledge gained from system design sessions, training, and participation in testing. It is an important element of building internal competences of the IFS system, as well as the awareness of its functioning and the independence of its operation and process design.

4. We use unique implementation, migration and service tools:

     a. Configuration module of the implementation and service portal (L-Systems ICS). Based on the data entered into the portal, a basic system configuration is generated, which is modified during system design meetings (prototype building). The portal offers the so-called preconfigured version of the IFS system with the most commonly used dictionaries and settings. Thus, the key user works with the preconfigured settings, modifying or supplementing them as needed. In the case of migration, the input data is read into the portal from the source system, and then supplemented and modified to create a prototype of the migrated system.

     b.Migration module of the implementation and service portal (L-Systems ICS). From the portal level, the client gets access to migration templates. He places the migrated data there in order to verify their correctness in terms of system parameterization, then generates data files from its level and imports it to the IFS system on its own.

      c. Product Backlog and Sprint Backlog. Testing of the prototype by key users on the client’s part is based on the Agile Scrum methodology. A product backlog is created (a list of all tasks that should be tested in a system prototype), and the so-called sprint backlogs, to which tasks planned to be performed in the near future are selected, the so-called sprint. Users report the progress of tasks on an ongoing basis, which gives project managers (both on the client side and L-Systems) an excellent overview of the progress in testing the system. L-Systems trains the team on the client’s side to use the scrum tools it provides.

     d. Service module of the implementation and service portal (L-Systems ICS). The customer receives a weekly and round-the-clock access to the registration of service and development requests. The module allows for full monitoring of the progress of work on submissions.


  • IFS service and maintenance

  • Create printouts and reports on request

  • Implementation and parameterization

  • Custom modification creation

  • Upgrading the system version

  • Training and consultation.