Portfolio /
Development of state and corporate information systems
Catalogue of goods, works and services

The main task of the Unified information system in the field of procurement – (UIS) is to increase the transparency of public procurement and ensure a full cycle of interaction between the customer and the supplier.

UES automates work with purchases according to two Federal laws-223 and 44, and controls-search, analysis, participation in the auction, the conclusion and execution of contracts, signing of acts of the performed works.


The key module of the EIS is the catalogue of goods, works, services (TRU)for state and municipal needs. KTRU is designed to systematize the search for public procurement positions and download data from external systems.

Previously, it was possible to create and place public procurement positions formed using the all-Russian classifier OKPD2 in the KIRU. We have expanded the functionality, now the system works with the all-Russian classifier of economic activities (OKVED2), the directory of medical devices, allows you to create custom classifiers. Additionally, you can group items that have differences in classification into separate headings, use headings and custom classifiers in search engines.

Mass operations designer

Another extension of the functionality of the catalogue of goods, works, services (KTRU), was the solution for mass creation, editing, placement and exclusion of catalogue items.


KTRU contains tens of thousands of public procurement items. These positions are systematized using the all-Russian classifiers OKPD2 and OKVED 2, which in turn have thousands of elements. In addition, each purchase has dozens of parameters. According to the parameters of the purchase can be attributed to different rubrics, or groups. Performing the same type of changes took a long time, and led to errors. After implementation of the designer of mass operations, work with the system became easier and more efficient.

State property management

The software package provides accounting and management of state and municipal property. The task is to improve the efficiency and quality of land and real estate management.

Users are committees and departments for management of the property of constituent entities of the Russian Federation and municipal formations.

The functionality of the system is maintenance of users, their roles and powers, directory management, calculation of financial liabilities, import of property information from external sources, management of electronic signature certificates, event logging. The accounting capabilities are realized – subjects of law, the initial and residual value of the object, the internal structure of the building while preserving the history, reconstructions, housing stock, cadastral value, proceeds in the context of legal relations, the history of legal relations, and the rental fund.


Automation of key scenarios provides growth of non-tax revenues to the regional and municipal budgets, planning and control of revenues, reduction of outstanding payments, reduction of risks from inefficiently used property, increase in productivity in the implementation of administrative procedures, increase in revenues from the provision of paid services to the population.

Access to the system is possible from any device.

The project used the following technologies:

  • Frontend: Vaadin
  • Backend: Spring 4.x, Hibernate, Tomcat 8.x.
  • Database PostgreSQL 9.3.
Automation of insurance policies

Solution in automation for the insurance policy consists of a mobile application, on which the agent operates onsite inspection of the insured object and the server application, on which the operator of an insurance company acts. The information from the mobile application is sent to the server via a secure channel so that the operator sees every action of the agent in real time. The mobile application is organized in the form of a sequence of simple and clear steps to register the inspection of the object. For example, the application asks for a photo of the car in a certain angle or the year of construction of the property.

It is possible to go to the next step only by completing the previous one. The application ensures that all the necessary information has been collected, so any agent can conduct an inspection without special training. From the personal account of the server application, the operator can assign and schedule inspections on agents, send messages to agents, publish application updates, view analytical reports. The system itself will notify agents about upcoming tasks and send a reminder on a schedule.


The decision to automate the registration of insurance policies:

  • Improves the quality of service when working with clients. Now the inspection of the object, the calculation of the cost of insurance and the conclusion of the contract takes place in one meeting with the client.
  • Reduces the cost of insurance policies, because the application does not require training of insurance agents.
  • Guarantees the correctness of the policy, thanks to the step-by-step process, and the ability to receive feedback from the operator Online.
  • Optimizes the load on operators. Now the data from mobile applications of agents comes to operators evenly.
  • Provides the ability to generate financial reports on the results of agents and track commercial performance: sales, profits, commissions agents, the number of policies sold and others.
Return statements

The module “Return statements” within the framework of a large-scale information system of a logistics operator is designed to manage the process of returning parcels. It aggregates and stores information from other modules about the need to return parcels, initiates the process in an optimal way and provides system components with access to status information.

The peculiarity of the project was that part of the functionality was implemented on the basis of a different stack of technologies and with a different behavior. During the development the project, we solved the problems of integration and intermodule interaction. Continuous work is important for business, so we implemented integration and synchronization with the previous system – and developed a logic for a seamless transition to new functionality.


The project used the following technologies:

  • Server technologies: Java 8, Spring, RabbitMQ, MyBatis
  • Database: PostgresSQL
Third Party Logistics

Third Party Logistics (3PL) is a module that is designed for the interaction of a logistics operator with partner companies that participate in the transportation of parcels on separate sections of the delivery chain.

The objective of the 3PL module is to obtain data from the information systems of partner companies, process this data and provide information about the location and status of parcels in a unified format.

The module architecture allows you to quickly perform typical integrations with third-party systems, and also lays the foundation for more complex integrations and extensions of the exchange system.

As a result of the project, customers of the logistics operator were able to track parcels at any part of the delivery chain.


The project used the following technologies:

  • Server technologies: Java 8, Spring, RabbitMQ, MyBatis
  • Database: PostgresSQL

The tasks of the Geoservice module in the courier service information system:

  • At the destination address, determine the department that will be responsible for delivery
  • Provide identification and storage of addresses in a single format
  • Minimize the budget for accessing paid services

The most important attribute of parcels in the courier service information system is the destination address. The address is specified manually, for this reason there are situations when the same address is written differently. Daily, the courier service delivers about 200,000 parcels. Thus in order to work correctly with addresses, it is necessary to accurately determine them.

We used Yandex services to recognize and store addresses in a unified format and to determine coordinates at a given address. In addition, we have developed a functionality that finds the nearest delivery service unit by coordinates.

To minimize the budget, we made a cache to store statistics of calls to Yandex services for the last month.The startup of the Geoservice project improved the quality of address processing, reduced the load on sorting centers and reduced the number of calls to paid services.


The following technologies were used on the project:

  • Server technologies: Java 8, Spring, RabbitMQ, MyBatis