Platform selection
From the registry, with a check that the entry is current on the date of purchase, since it can change.
The work starts with a check of the applicable requirements: the registry is not required by everyone or for everything.
From the registry, with a check that the entry is current on the date of purchase, since it can change.
Confirmations for tender documentation and for inspectors.
Implementation on the chosen platform, allowing for its limitations.
Transfer of data and logic from foreign solutions, including customised configurations.
Exchange with 1C and other systems that remain in the landscape.
Preparing users: the interfaces differ, and without training the transition stalls.
The project runs longer than a typical one: compatibility checks and training are added. Plan for three months upwards.
What is mandatory under the regulations for you specifically, and what can be left as it is.
Choosing a platform and testing it on a limited landscape with real data.
Transfer department by department, with the option to work in two systems during the transition.
Reinforced support for the first month and removal of the old licences from the bill.
Check the registry entry on the date of purchase, not on the date of choice. Entries do get removed, and a solution that was in the registry six months ago may no longer be there. For tender documentation this is critical: the discrepancy surfaces at acceptance.
Government customers, owners of significant critical infrastructure facilities and participants in a number of tenders are. Commercial companies without such requirements are not, though some choose to switch for the sake of access to tenders.
In terms of capabilities Russian platforms usually fall short of mature foreign analogues, and pretending otherwise would be dishonest. For typical automation tasks the difference is not critical, for complex scenarios it has to be assessed before the decision.
That is the narrowest point. There are fewer ready made connectors, and part of the exchanges has to be written by hand. That is why we always build an integration check into the pilot, since that is where projects get stuck most often.
Tell us about the requirements and your current systems. We will check the registry and estimate the scope of the migration.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.