According to Valentin Makarov, President of the Non-Profit
Posted: Wed Jan 22, 2025 5:57 am
country.
Alexander Vakhitov is more cautious in his assessments, since the software replacement time depends on the size and needs of the customer: "For some, basic functionality is enough, while for others, compatibility and integration with solutions already implemented in the organization are important. In the latter case, a pilot project is conducted before purchasing, perhaps even more than one. Our company's experience shows that the duration of such projects varies from six months to a year and a half."
Alexander Cherny agrees that czech republic whatsapp number database OS and office software replacement projects take more than a year on average, which is further complicated by other factors: "They include such stages as design, procurement, implementation, and personnel training. It should also be taken into account that along with the OS replacement, the application software will also need to be changed, including the company's business process automation software to ensure compatibility or as part of the import substitution program. The implementation period for each of these projects, in turn, takes about a year on average."
Partnership "Russoft", the process of import substitution of software varies greatly for its different segments and depends on many factors, therefore, it is more likely that we can talk about ensuring import substitution of system software and critical applications within the specified timeframes, and for other software segments these timeframes can be not strictly set, only creating conditions that stimulate clients to import substitution. In his opinion, project deadlines depend more on customers than on vendors: "Currently, there are several competing operating systems and office software packages, and the timing of their replacement of products from world leaders in unfriendly countries depends not so much on the developers as on the customers themselves. The largest customers have not tried to interact with Russian manufacturers of operating systems and office software for many years, relying on the contractual obligations of world leaders and the decency of world politicians. Now they have to quickly replace the operating systems and office software in their, often very large, information systems. And this is indeed a serious task that may require a little more time than it seemed at first. And this is not sabotage - this is the reality of managing complex systems."
Will no-code help?
Igor Mityunin, Head of the Partnership Department at Nocode.ru, sees a solution in expanding the practice of using zerocode platforms: "On such platforms, you can set up business processes and permissions for different roles, add specific functionality to the service and integrate it with other systems using visual programming - that is, without dependence on the platform vendor.
Zerocode tools are not demanding on the qualifications of developers, so the development can be carried out by the customer company's team. This allows you to manage labor costs for creating a solution, develop and build its interaction with other services without restrictions." According to Igor Mityunin, the use of these technologies is especially relevant for such software classes as CRM, mobile signature services, IT infrastructure management systems and user support, as well as project management.
Vladimir Vigura, Director of the NOTA MODUS product, estimated the potential share of no-code systems in the public sector at 40%. At the same time, the use of no-code tools is the main factor that allows unifying the work of the project team and reducing the time spent on implementing solutions, especially in conditions of personnel shortage.
Alexander Vakhitov is more cautious in his assessments, since the software replacement time depends on the size and needs of the customer: "For some, basic functionality is enough, while for others, compatibility and integration with solutions already implemented in the organization are important. In the latter case, a pilot project is conducted before purchasing, perhaps even more than one. Our company's experience shows that the duration of such projects varies from six months to a year and a half."
Alexander Cherny agrees that czech republic whatsapp number database OS and office software replacement projects take more than a year on average, which is further complicated by other factors: "They include such stages as design, procurement, implementation, and personnel training. It should also be taken into account that along with the OS replacement, the application software will also need to be changed, including the company's business process automation software to ensure compatibility or as part of the import substitution program. The implementation period for each of these projects, in turn, takes about a year on average."
Partnership "Russoft", the process of import substitution of software varies greatly for its different segments and depends on many factors, therefore, it is more likely that we can talk about ensuring import substitution of system software and critical applications within the specified timeframes, and for other software segments these timeframes can be not strictly set, only creating conditions that stimulate clients to import substitution. In his opinion, project deadlines depend more on customers than on vendors: "Currently, there are several competing operating systems and office software packages, and the timing of their replacement of products from world leaders in unfriendly countries depends not so much on the developers as on the customers themselves. The largest customers have not tried to interact with Russian manufacturers of operating systems and office software for many years, relying on the contractual obligations of world leaders and the decency of world politicians. Now they have to quickly replace the operating systems and office software in their, often very large, information systems. And this is indeed a serious task that may require a little more time than it seemed at first. And this is not sabotage - this is the reality of managing complex systems."
Will no-code help?
Igor Mityunin, Head of the Partnership Department at Nocode.ru, sees a solution in expanding the practice of using zerocode platforms: "On such platforms, you can set up business processes and permissions for different roles, add specific functionality to the service and integrate it with other systems using visual programming - that is, without dependence on the platform vendor.
Zerocode tools are not demanding on the qualifications of developers, so the development can be carried out by the customer company's team. This allows you to manage labor costs for creating a solution, develop and build its interaction with other services without restrictions." According to Igor Mityunin, the use of these technologies is especially relevant for such software classes as CRM, mobile signature services, IT infrastructure management systems and user support, as well as project management.
Vladimir Vigura, Director of the NOTA MODUS product, estimated the potential share of no-code systems in the public sector at 40%. At the same time, the use of no-code tools is the main factor that allows unifying the work of the project team and reducing the time spent on implementing solutions, especially in conditions of personnel shortage.