Additional requirements for programs for electronic computers and databases, information about which is included in the register of Russian software. Register of Russian software of the Ministry of Communications

5) Russian commercial organization without predominant foreign participation. A commercial organization is one if more than 50 percent in it is the total share of direct and (or) indirect participation:

Russian Federation,

municipalities

citizens of the Russian Federation.

6) to a citizen of the Russian Federation.

Requirement 2. The software is rightfully put into civil circulation on the territory of the Russian Federation. Instances of software or rights to use it are freely implemented throughout the Russian Federation.

Requirement 3. This requirement applies to the total amount of payments for a calendar year under license and other agreements (regardless of the type of agreement).

We are talking about contracts that:

1) provide for the granting of rights to the results of intellectual activity and means of individualization, performance of work, provision of services;

2) are associated with the development, adaptation and modification of software and are concluded for the development, adaptation and modification of software;

3) suggest payments:

to foreign legal entities and (or) individuals controlled by them to Russian commercial and (or) non-commercial organizations,

agents, representatives of foreign persons and Russian commercial and (or) non-profit organizations controlled by them.

The total amount of payments to such persons for a calendar year should be less than 30 percent of the revenue of the software copyright holder (s) from its sale (including the granting of rights to use).

Requirement 4. Information about the software does not constitute state secrets, and it does not contain the information that makes it up.

Requirement 5. The software meets the information security requirements. That is, there should be a certificate of a certification system for information protection means according to information security requirements. The procedure for its issuance is established by the Government of the Russian Federation.

This requirement applies only to software, which includes functions to protect confidential information.

Requirement 6. There is a license to carry out activities to develop and manufacture means of protecting confidential information if:

as part of the software, the functions of protecting confidential information are implemented.

Who can enter information in the Register

An authorized body (the Ministry of Communications and Mass Media of Russia) may apply to the inclusion of information in the Register by the software copyright holder or a person who is authorized by all copyright owners (paragraph 9 of the Rules).

If the exclusive right to the software belongs to the Russian Federation, the constituent entity of the Russian Federation, the municipality, then the application shall submit accordingly:

federal executive body

executive authority of the subject of the Russian Federation,

local government or

an organization that exercises control (disposal) of such a right.

In order for an organization or individual to be able to enter information about the software in the Register, it must have:

ESIA Account

It is needed in order to submit documents through the official website of the Registry. This is possible only after authorization in your account through ESIA.

If the copyright holder is an individual, then his verified account in ESIA is enough. It is more difficult with a legal entity - you need to register his account. To do this, you need to:

the legal entity had a qualified certificate of electronic signature issued to the head of the organization, and

the manager had a verified account as an individual at ESIA.

To create a legal entity account in ESIA, the head must in his personal account state service portal :

1) go to the tab "Organization",

2) select the item “Create an organization account”,

3) fill out the proposed form and

4) again confirm it with a qualified electronic signature.

Enhanced Qualified Electronic Signature

It is needed in order to sign an application for entering information about the software in the Registry.

If the copyright holder is an individual, then the application must be signed with a personal enhanced qualified electronic signature.

If the copyright holder is a legal entity, then we are already talking about an enhanced qualified electronic signature of the organization in the person of its head or authorized person (based on a power of attorney).

How to apply

In order to enter information about the software in the Register, it is necessary to submit to the Ministry of Communications of Russia the corresponding application and the documents and materials attached to it (paragraph 14 of the Rules).

To do this, fill out the electronic forms that are posted on the official registry website reestr.minsvyaz.ru (Order of the Ministry of Communications of Russia dated December 31, 2015 No. 614 “On the definition of the official site of the operator of the unified registry of Russian computer programs and databases in the Internet”).

This can be done after the applicant (paragraph 14 of the Rules).

Information, documents and materials necessary for applying(according to section IV The procedure for submitting an application for entering information about the software in the Register ):

1. The name of the software.You must specify the current software name (without product version numbers).

2. Previous and (or) alternative software names.This field can be left blank.

3. Product code (s).It is necessary to indicate one or several codes of OKPD 2. Their description is given in the All-Russian classifier of products by type of economic activity OK 034-2014 (CPA 2008).

4. The class (classes) of the software to which the software corresponds.You must specify one or more software classes. Moreover, under software class understand a group that:

combines software that has similar functional, technical and (or) operational characteristics, and

determined by the classifier (it was approved by the Ministry of Communications of Russia by order of December 31, 2015 No. 621).

Such a definition is given in paragraph 2 of the Rules.

The procedure to be followed in order to determine the class (classes) was approved by order of December 31, 2015 No. 622.

The classifier uses a hierarchical classification method and a sequential coding method. The code consists of 2-4 numeric characters.

Software corresponds to several classes if it fully or partially meets the functional, technical and (or) operational characteristics of such classes.

5. Status of copyright holder.Here you need to select one or more items from the list:

russian commercial organization;

russian commercial organization having in the chain of ownership of foreign persons (foreign organizations or trusts);

russian non-profit organization;

citizen of the Russian Federation.

6. Information about software copyright holders.The content depends on the status of the copyright holder:

1) in relation to a citizen, you must specify:

last name, first name, patronymic,

name and details of an identity document,

address of registration at the place of residence (stay) or, if there is no such registration, - address of the place of actual residence;

2) in relation to the organization, it is necessary to indicate the full name, PSRN and TIN.

7. Information on the shares of direct and indirect participation in the copyright holder:

Russian Federation,

subjects of the Russian Federation,

municipalities

russian non-profit organizations without predominant foreign participation and

citizens of the Russian Federation.

This field needs to be filled in two cases - if the exclusive right to the software belongs to the copyright holder :

“Russian commercial organization” or

"A Russian commercial organization having in the chain of ownership of foreign persons."

In the first case, you need to specify the final owners (Russian citizens) and the size of their shares.

In the second case, it is necessary to open the entire ownership chain in the form of a table and download scanned extracts (or other documents) from the registers of the respective states.

Information must be filled out in relation to all ultimate beneficiaries (Russian citizens) who own more than 5 percent of the authorized capital of the organization-holder.

A separate rule is established for the case when such beneficiaries collectively own less than 50 percent of the authorized capital (that is, it is impossible to verify the criterion of ownership of the exclusive right). In such a situation, it is necessary to include information about Russian citizens owning shares of less than 5 percent. This needs to be done so that the statement contains information about Russian citizens who, in the aggregate, own more than 50 percent of the authorized capital of the copyright holder organization. That is, it is not necessary to provide information about all the ultimate beneficiaries - Russian citizens.

8. Email address and telephone number for contacting the applicant.You must specify valid contacts to send notifications and requests for additional information.

9. The page address of the copyright holder’s website on the Internet with documentation that describes the functional characteristics of the software and information for its installation and operation. It's about user documentation.

10. Status of the person signing the application.In this field you need to select one item from the list:

representative of the copyright holder acting on the basis of a power of attorney;

a person having the right to act without a power of attorney on behalf of the copyright holder, which is a legal entity;

11. A document that confirms the authority of the person signing the application(if the application for inclusion of information in the Register is signed by a representative by proxy). We are talking about a power of attorney with the authority to carry out actions on behalf of the copyright holder (s) of the software. The applicant must download a scanned version of the power of attorney in pdf format.

12. A copy of the charter of the software copyright holder (if the application is submitted by the organization). You must download the scanned version of the charter in pdf format. You need to do this with one file.

13. Instance of software.In this section, you must provide a valid link to download the software distribution. You also need to attach instructions (in the form of a single document in any form) for downloading and installation. It should include (if necessary) a license key (serial number) for activation.

14. Documents that confirm that the software meets the requirement of exclusive ownership(if applying ) Download required:

a file with a description of the ownership chain in the form of a table (in any form) and

a scanned version of extracts (or other documents) from the registers of the respective states confirming the data in the table.

15. Information on the grounds for the occurrence by the copyright holder (s) of an exclusive right to software throughout the world and for the entire duration of the exclusive right. This field must be filled in text form (in any form).

The basis for the emergence of an exclusive right may be, for example, own development (creation of an official work) or acquisition of an exclusive right.

16. Documentation describing the functional characteristics of the software and information for its installation and operation. This documentation must be downloaded in text format.

17. Documentation that contains:

1) a description of the processes that support the software life cycle, including:

troubleshooting identified during the operation of the software,

software improvement;

2) information on the personnel necessary to provide such support.

This documentation must also be downloaded in text format.

18. Other documents.The applicant can attach any documents that confirm that the product meets the criteria of Russian software and software class.

Applicant must (paragraph 14 of the Rules).

Who and how includes information about the software in the Registry

In the process of including information about software in the Registry, except , you can distinguish three more actors.

1. Ministry of Communications of Russia. This is the authorized federal executive body for the formation and maintenance of the Register. The Ministry of Communications of Russia makes decisions on including information on software in the Register and on their exclusion from it.

2. Registry Operator He is directly involved in maintaining the Register.

The Ministry of Communications of Russia attracts an operator in accordance with the Federal Law of April 5, 2013 No. 44-ФЗ “On the Contract System in the Sphere of Procurement of Goods, Work, and Services to Ensure State and Municipal Needs” (hereinafter - Law No. 44-FZ) (Section 6) Rules). It must meet two conditions:

have registration in the territory of the Russian Federation;

have the right to receive a mandatory copy of the software.

Three organizations meet these conditions, listed in Article 13 of the Federal Law of December 29, 1994 No. 77-FZ “On the Mandatory Copy of Documents”:

Interdisciplinary Research Institute "Integral";

Scientific and Technical Center "Informregister";

Presidential Library named after B.N. Yeltsin.

The operator from among its employees determines the persons authorized to include information in the register, change it and (or) exclude it from the register (paragraph 7 of the Rules).

3. Expert Council on Russian software. It is created by the Ministry of Communications of Russia in order to conduct an examination when including information about software in the Register (paragraph 8 of the Rules, order of the Ministry of Communications of Russia of December 30, 2015 No. 615 “On approval of the Regulation on the Expert Council on Russian Software under the Ministry of Communications and Mass Communications of the Russian Federation ”).

P the process of including information about software in the Registry can be divided into nine stages.

Stage 1.The authorized body checks the application and the documents and materials attached to it within 10 business days from the date of receipt (paragraph 16 of the Rules).

Stage 2. The authorized body, within 5 working days from the date of receipt of the application, requests from government authorities documents and information confirming the information in the application and the documents and materials attached to it (paragraph 20 of the Rules).

Stage 3. The authorized body registers the application (paragraph 19 of the Rules).

The applicant will be refused registration if (paragraph 17 of the Rules):

he violated the Rules;

the authorized body within 12 months prior to receipt of the application already:

refused the applicant to include information in the Register due to the fact that he submitted false documents, materials and (or) inaccurate information (sub. “a” paragraph 27 of the Rules), or

excluded information from the Register for the same reason (sub. "c" p. 33 of the Rules).

After the applicant eliminates the reasons specified in the first paragraph, he will be able to re-submit the application (paragraph 18 of the Rules).

Stage 4. The registry operator, no later than the business day following the day of registration of the application, places it in the public domain on the official website (paragraph 19 of the Rules). In this case, personal data (if any) is depersonalized.

Stage 5. The expert council considers the application within 30 working days from the date of its registration and approves the expert opinion (paragraph 21 of the Rules). It should contain conclusions about whether the software matches:

Stage 6. The expert report is transmitted to the system operator within one business day from the date of its approval (paragraph 21 of the Rules).

Stage 7. The registry operator places the expert opinion in the public domain on the official website (paragraph 21 of the Rules).

Stage 8. The authorized body decides to include information about the software in the Register. He must do this:

within 65 business days from the date of registration of the application, but

no later than 10 working days from the day when the expert council approved the expert opinion.

The specified decision is issued in the form of an order of the Ministry of Communications of Russia (paragraph 25 of the Rules).

The authorized body may refuse to include information on software in the Register for three reasons (paragraph 27 of the Rules):

the applicant submitted false documents, materials and (or) false information;

within 30 business days the applicant has not provided explanations and (or) documents at the request of the expert council (paragraph 22 of the Rules), if without them it is impossible to confirm the accuracy of the information provided and (or) the authenticity of the submitted documents;

Stage 9. Registry Operator:

places the decision of the authorized body on the official website and informs the applicant about it at the email address indicated in the application (paragraph 28 of the Rules);

includes information about software in the Register (paragraph 29 of the Rules).

The operator must do this no later than the business day following the day when the authorized body decides.

Created as part of measures taken by the state to limit the purchase of imported software in government agencies and companies with state participation. The registry has been operating since January 1, 2016. So. On September 21, 2016, the Minister of Telecom and Mass Communications of the Russian Federation Nikolay Nikiforov admitted the possibility of expanding the domestic software registry across the entire Eurasian Economic Union.

The Minister expressed his opinion at the 33rd World Conference of the International Association of Science Parks and Zones of Innovative Development (IASP) “The Common Technological Space of the Eurasian Economic Union (EAEU): a Model for Assembly”.

During the discussion, conference participants discussed the impact of regionalization on the global economy, the mechanisms and capabilities of the EAEU countries in the development of technology parks and innovation clusters. They noted the need to upgrade the status of technology parks and innovation clusters, their transition from national to international format.

The participants in the discussion touched upon the issue of developing a common position on a number of aspects of national legislations for joint work in the EAEU. In particular, the head of the Ministry of Telecommunications and Communications of Russia said that recently the Government of the Russian Federation adopted a decree securing for Russian manufacturers a price preference of 15% for the supply of products and services to state-owned companies. He also spoke about the experience of developing the registry of domestic software and invited representatives of the Union countries to consider the possibility of creating similar mechanisms in their legislation.

Russian software registry replenished with 645 new software products

In the framework of the fifth in-person meeting at the Ministry of Telecom and Mass Communications of the Russian Federation, in September 2016, the Expert Council on Russian Software voted to include 645 new products in a single register of Russian software, i.e. 1823 software products are already included in the Russian software registry.

The added software products were recognized as meeting the requirements established by paragraph 5 of the rules for the formation and maintenance of a unified register of Russian programs for electronic computers and databases, approved by RF Government Decree No. 1236 “On the prohibition of admission of software originating from foreign countries for the implementation procurement to ensure state and municipal needs ”of November 16, 2015

The Russian Software Expert Council is a permanent body that examines companies' applications for including information about their software products in a single register of Russian software. The council includes representatives of federal executive bodies, institutes of innovative development, as well as associations of Russian software developers. Representatives of departments cannot have more than 40% of the vote in it, while representatives of the IT industry, in whose interests the reform is being implemented, must have at least 50% of the vote. Decisions of the council are taken by a simple majority of votes of its members participating in the meeting, including remotely. In case of equality of votes, the chairman's vote is decisive.

The developer requires Nikiforov to include a product on an import platform in the Russian software registry

The Letograph company, the developer of the product of the same name for creating document management systems, sent a letter to the Minister of Communications Nikolai Nikiforov, demanding to reconsider the decision to include its product in the Russian software registry.

The order to refuse to include Letograph in the register of the Ministry of Communications issued in May and published in August 2016. The general director of the company, Gleb Lukin, told TAdviser that Letograph had sent a request to the department about the reason for the refusal, and its decision was justified by the Ministry of Communications because the key functionality of the announced Letograph software was implemented on the foreign proprietary platform Ensemble.

The Letograph states that such a basis for refusal is not provided for by law. The Letograph document management system fully meets the requirements specified in federal law dated June 29, 2015 No. 188-FZ and article 14 of the federal law and is completely domestic development, the company stated.

General Director "Letograph" Gleb Lukin does not agree with the decision of the Ministry of Communications on the refusal to include the company's product in the register

In No. 188-ФЗ “On Amendments to the Federal Law“ On Information, Information Technologies and the Protection of Information ”and Article 14 of the Federal Law“ On the Contract System in the Sphere of Procurement of Goods, Work, and Services to Ensure State and Municipal Needs ”, requirements are formulated for domestic software. In his letter to Letiforov Nikiforov, their software complies with all points, including exclusive rights to software of a Russian company, free distribution in the Russian Federation, amount of deductions for foreign components, not exceeding 30% of revenue from product sales, and Lack of information constituting a state secret in the software.

It also says that the product contains more than 500 MB of software code written by Russian developers and owned by a domestic commercial organization.

In a letter to the Minister, Letograph draws attention to the fact that all the EDMS presented on the domestic market require a DBMS developed by a third company to function, and products using imported DBMSs such as Microsoft SQL Server or Oracle are included in the registry. As an example, the developer cites EDS E1 Euphrates and Delo. In turn, Letograph is a completely domestic solution using InterSystems Cache or Ensemble solutions as a DBMS, the letter said.

In response to a letter to Nikolai Nikiforov, Letograph received a letter from Innokenty Dementyev, Deputy Director of the High Technologies Development Department of the Ministry of Communications and Mass Media, who recommended the company re-submit the application, eliminating the reasons for which it was previously refused to include information about the software product in the register, or attaching clarifications to the application on the issue of compliance of the product with the requirements established by the rules.

Earlier, in March, members of the Expert Council for Russian Software under the Ministry of Communications and Mass Media at one of the meetings agreed not to let decisions be included in the register if their key property is not based on domestic technologies, even if on the whole it formally meets the legislatively established criteria for “Russianness”. It was planned to apply this policy, including to open source software.

In this regard, several products already included in the registry were later removed from the Russian software registry, in relation to which their principal foreign origin was revealed.

Developer's revelations: “There are few chances to immediately get into the registry of Russian software”

The company Elar, which specializes in creating, equipping and filling electronic archives and other IT services, spoke about the "pitfalls" encountered in the process of filing and reviewing applications for entering Russian software into the registry. The orders to refuse to include software products in a single register, first published by the Ministry of Communications in July 2016, list three Elar decisions: AIS Elar-Archive, Elar-SAAD and ELAR-Document Stream.

Formally, applications for inclusion of the company's software products in the registry were rejected due to the presence in the distributions of software components of foreign origin and the absence of some documents confirming the company's ownership of the software, explained Tadviser head of marketing department Elar Artem Vartanyan. However, such a “mismatch” with the requirements is a consequence of the fact that the procedure for entering domestic software in the registry is opaque, he said.

The lack of transparency of the mechanism for including software in the registry was also noted by some other developers who received refusals (see below in the subsection “Who and why they do not allow domestic software in the registry for”)

Developers and owners, submitting applications to the Ministry of Communications, rely on the following documents, explains the representative of Elar. Firstly, the Federal Law of the Russian Federation dated June 29, 2015 No. 188-ФЗ “On Amendments to the Federal Law“ On Information, Information Technologies and the Protection of Information ”and article 14 of the Federal Law“ On the Contract System in the Sphere of Procurement of Goods, ” works, services to ensure state and municipal needs ”, which formulates the requirements for domestic software. Secondly, on the “Rules for the Formation and Maintenance of a Unified Register of Russian Programs for Electronic Computers and Databases”. Thirdly, to the "Procedure for filing an application to include information about software in a single register of Russian programs for electronic computers and databases."

None of these documents say about the requirements for distributions or, for example, that to prove ownership of the software it is necessary to provide a staffing table that will convince the commission that it was our programmers who wrote the code, noted Artem Vartanyan in a conversation with TAdviser.

Who and for what is not allowed in the register of domestic software

In August 2016, the Ministry of Communications and Mass Media issued a series of orders refusing to include software products in a single register of Russian software. In 12 such documents issued at different times from February to May, there are about 230 products. Among the most famous companies and products on the lists are “Krok” with a corporate EDMS, a “daughter” of IT Co. Group “Logika Biznesa” with several solutions in the field of electronic document management, a solution for monitoring media outlets “Medialogy”, a number of products “MSVSfera” “ National Support and Development Center ", WorksPad" daughter "IT Co." Laboratory of Corporate Mobility ", a package of office applications" IvolgaPro "and others.

The Ministry of Communications does not explain the reasons for refusals to add all these programs to the register. Previously, there were precedents when products were excluded from the registry, as they were based on foreign technologies. For example, the two products of Business Logic are ECM ASL.ED, and ECM ASL. Electronic Archive ”was first included in the registry, and then excluded from it, as experts discovered IBM technologies used in them. At the time of publication of the rejection orders, the registry includes three other products of Business Logic. The company told TAdviser that the registration process is still ongoing, and the company will be ready to comment on this immediately upon completion.

A similar fate and for the same reason - the use of IBM software - befell the Karelian Medical Information System product of K-MIS. Also, the Metamodel Group company’s electronic document management platform “M1: ECM Platform”, based on EMC products, was removed from the registry.

The Ministry of Communications does not explain the reasons for the refusal to include products in the register

Kroc previously reported receiving EMC certification for a product with the same name as a filed in the registry, based on the EMC Documentum platform, and refused. The company did not specify TAdviser, the product on the basis of which platform was submitted to the registry, but noted that this is a solution of its own design that meets the requirements of the Ministry of Communications.

Igor Nikulin, director of the information technology department at Krok, told TAdviser that the company plans to wait for official notification and continue to interact with colleagues from the Ministry of Communications: “We are interested in the maximum number of our software developments being published in the registry, because the breadth of choice is healthy competition for the benefit of the customers themselves. ”

In turn, MSVSfera solutions that are not in the registry are based on Red Hat products. Earlier, members of the Expert Council for Russian Software under the Ministry of Communications and Mass Media, which made decisions on including software in the registry, agreed not to allow products, including open source products, if their key property is not based on domestic technologies.

As for the IvolgaPro product, previously the media wrote about the existence of a connection between this product and the products of the Latvian company Ascensio CIA (brand OnlyOfice). The company New Communications Technologies, the developer of IvolgaPro, told TAdviser that they did not understand the decision of the Ministry of Communications. The company did not receive written justifications for the refusal and can only “guess” what caused it. Perhaps the point is the imperfection of the mechanism for including software in the registry: "the mechanism for including software in the registry is very closed and opaque," says Lev Bannov, general director of the company. He added that the company does not agree with the decision.

The refusal did not change the company's plans, added Lev Bannov. The main tasks remain the same - to make a competitive product and find their place in the world system of division of labor. At the same time, the top manager does not believe in creating a purely Russian division of labor in the field of software: “This is fiction and self-deception. All programs included in the registry have imported components. Just for some reason, some are considered Russian, while others are not. ” He added that New Communication Technologies will wait for the situation to develop.

Some of the products could be in the rejected lists due to incorrectly executed or submitted documents or some other organizational reasons. So, for example, it was in the case of the decision. Bars. This decision is listed in the list of "refuseniks", but in fact at the time of publication it is present in the registry. The Bars Group explained to TAdviser that the reasons why this decision was on the list of refuseniks for inclusion in the register are purely organizational in nature.

In the case of the “CryptoPro CSP (version 4.0)” solution, which is on the lists but also on the registry, the registration was refused at the request of the developer company in accordance with the letter about the erroneous re-application.

Removed shells for IBM and EMC platforms from the Registry

On June 8, 2016, it became known about the removal of a number of software products from the Register of domestic software supervised by the Ministry of Telecommunications and Communications on the fact of their foreign origin.

The “rogue list” includes:

"Logic of the ECM ASL.EDMS" and "Logic of the ECM ASL. Electronic Archive ”of the Logic of Business company (part of the Aichi group),
Karelian Medical Information System of K-MIS and
"M1: ECM Platform" of the Metamodel Group company.

The first three products are listed at the beginning of April 2016, the last at the end of April.

The reason for this decision was “newly discovered information about the specifics of this software”, pointing to the platforms of foreign vendors based on the properties of these programs: IBM and EMC, which means applicants to the Registry do not have exclusive rights to them and do not control them.

There were no official reports of the department about the removal of software from the registry, but an analysis of the previous and current lists of the Registry programs indicates the absence of the listed products in it.

According to the source of the CNews publication, the software in question fell into the Register by mistake and oversight. He emphasized that the responsible expert, giving a preliminary opinion on the compliance of the software with the criteria of "purebred", had its own in each of the four cases. That is, there is no talk of someone else's systemic malicious connivance.

The expert believes that the Ministry of Communications, issuing an order to add products to the register (apparently, it is a “tranche” when IBM solutions were on the list), was aware of what was happening, but mechanically completed the formal process.

SAP-based partner solutions will claim to be in the Russian software registry

SAP is discussing with a number of Russian partners how to combine its software with their products so that it can be included in the Russian software registry as part of partner solutions, Rolf Schumann, CTO SAP in the EMEA & MEE Region told TAdviser in March 2016 (more )

84 new products, including Abbyy, MyOffice, Dr. Web, Docsvision

On February 18, an in-person meeting of the expert council on Russian software was held at the Ministry of Communications and Mass Media under the chairmanship of Minister Nikolai Nikiforov. According to its results, 84 new products were included in the register of domestic software.

The list included products from developers such as Cognitive Technologies, Dr. Web, Bars Group, New Cloud Technologies, Forecast, 1C-Bitrix, Doxvision, 1C, Alt Linux, etc. The products of the last two developers mentioned include the number of positions for inclusion in the registry was reduced, a source close to expert advice told TAdviser.

As of mid-February, more than 700 applications have been received to include information about software in the Russian software registry

The following classes of software products are now presented in the Russian software registry: operating systems, organization process management systems, DBMSs, cloud and distribution computing support tools, virtualization and storage systems, server and middleware, search engines, monitoring and control systems, information security tools , office applications, systems for the collection, storage, processing, analysis, modeling and visualization of data arrays, project management systems, research, times abotkoy, design and implementation, linguistic software.

Among the products included in the registry are 1C-Bitrix: Site Management (several versions), 1C-Bitrix24, ABBYY FineReader, ABBYY Lingvo, ABBYY Comparator, Dr.Web Desktop Security Suite, Dr.Web Katana, Prognoz Platform, Docsvision system, “1C: ERP Enterprise Management 8”, “1C: Accounting 8”, “1C: Retail 8”, “MyOffice Mail”, Digital Design: Secure Mobility, Bars Housing and Public Utilities, BARS. Monitoring - Education, Alt Linux KDesktop "," Alt Linux 7.0 Centaur "and others.

For some applications, it was decided to refuse to be included in the register. The source of TAdviser says that in many cases this happened even before the applications were submitted for consideration by the expert council, mainly because of the discrepancy between the electronic signature with which the applications are signed.

Another source close to expert advice, TAdviser, notes that some products were rejected due to the fact that the developers did not provide the software product with the documents so that it could be viewed, and in some cases, because the final beneficiaries of the software are not Russian entities.

ESET Anti-Viruses May Get into the Registry

On February 5, 2016, it became known that ESET software could be recognized as Russian. Iset Development LLC proposed to include its integrated antivirus solution product in the domestic software registry (more).

The first products in the Russian software registry

On February 1, 2016, the Minister of Communications Nikolay Nikiforov signed an order to include the first three software products in a single register of Russian software. One of them was the Red Database database management system from Red Soft, developed on the basis of Firebird open source software. It is used in more than 30 government bodies and state organizations, in more than 150 banks. The largest client "Red Database" in the public sector is the FSSP.

The other two products included in the registry are “1C: School. Computer science. Grade 11 ”and“ 1C: School. Russian language. 5-6 grade. Lexicology ”from“ 1C-Publishing ”.

The decision to include products in the register was made during an in absentia meeting of the Russian Software Expert Council, which includes representatives of federal executive bodies, innovation development institutions, as well as associations of Russian software developers. Decisions of the council are made by a simple majority vote of its members. Based on the results of the vote, these software products were recognized as meeting the requirements established by the fifth paragraph of the rules for register formation.

EMC Documentum claims to be in the registry

In January 2016, EMC launched the process of registering a number of partnership developments based on its Documentum platform in the domestic software registry, said Vyacheslav Kadnikov, Regional Director of EMC ECD (Enterprise Content Division) for Eastern Europe, Russia and the CIS (more).

Registry Regulation

Approval of the rules for register formation

The rules for register formation were approved by the Government Decree of November 16, 2015 No. 1236.

Prior to signing the Government Decree, the Ministry of Communications did not have the authority to engage in the registry. With the signing of the document, the ministry becomes responsible for the registry, explained TAdviser Evgenia Vasilenko, executive director of the Association of Russian Software Developers (ARPP “Domestic Software”).

“There is little time before January 1, but there are many tasks. The Ministry of Communications and Mass Media needs to adopt regulations, determine the rules of work of the expert council, and appoint a registry operator. It is necessary to develop and approve the software classifier. Create a registry information system, ”says Vasilenko.

The association, she said, is ready to actively participate in these tasks.

“We are already doing the classifier and will pass it to the Ministry of Communications. We are ready to connect to the creation of an information system, but here we need specifics that can be worked out together with the regulator. Previously, we at ARPP discussed that we are ready to implement the system free of charge and transfer it to the ministry if we work together on it, primarily in terms of formalizing the requirements for the system, ”adds the director of ARPP.

The Ministry of Communications promises to answer questions about the formation of the register after the publication of the Government decree.

Registry Act

The creation of the Russian software registry is enshrined in federal law signed by President Vladimir Putin in June 2015.

The Federal Law defines the criteria that software must meet in order to get into this registry. Among them:

the exclusive right to software on the territory of the whole world and for the entire duration of the exclusive right must belong to: the Russian Federation, the constituent entity of the Russian Federation or the municipality; a Russian NPO, the supreme governing body of which is formed directly or indirectly by the Russian Federation, constituent entities of the Russian Federation, municipalities or Russians and which is not recognized as a Russian organization controlled by a foreign person; a Russian commercial organization with a total share of direct or indirect participation of the Russian Federation, constituent entities of the Russian Federation, municipalities, NPOs and direct or indirect participation of Russian citizens more than 50%; a citizen of the Russian Federation;

The software is available for sale;

the total amount of payments under license and other agreements providing for the granting of rights to the results of intellectual activity and means of individualization, the performance of work, the provision of services used to develop, adapt and modify software in favor of foreign persons controlled by them by Russian organizations, agents, representatives of foreign persons and the Russian organizations controlled by them, make up less than 30% of the revenue of the copyright holder from the sale of software for a calendar year;

information on the software copyright holder is entered in the register of accredited organizations operating in the field of information technology;

information about the software does not constitute state secrets, and the programs or databases themselves do not contain information constituting state secrets.

Decisions on the inclusion of specific software in the domestic software registry will be made by the expert council, which will form the Ministry of Communications.

The Ministry of Communications has been appointed responsible for the registry by a Government decree signed by Prime Minister Dmitry Medvedev in November 2015. The decree imposes restrictions on the purchase of imported software in government agencies and companies with state participation, if similar software is contained in the registry.

Software products included in the registry

Russian software registry

№	Title	Software class (in registry terminology)	Date of entry
1	Red Database	DBMS	January 29, 2016
2	1C: School. Russian language, grades 5–6. Lexicology	Organization process management systems,	January 29, 2016
3	1C: School. Computer Science, Grade 11		January 29, 2016
4	ABBYY ScanDifFinder SDK	Subroutine Libraries (SDKs), linguistic software,	February 20, 2016
5	Alt Linux 7.0 Centaur	Utilities and drivers, executable code preparation tools, source control version control tools, cloud and distributed computing tools, virtualization and data storage systems, development, testing and debugging environments, operating systems	February 20, 2016
6	1C: Integrated Automation 8	Organization Process Management Systems	February 20, 2016
7	Electronic periodical “Garant System”	Information systems for solving specific industry problems, general-purpose application software, search engines, databases, office applications	February 20, 2016
8	Alt Linux CD Desktop	Development, testing and debugging environments, utilities and drivers, means of version control of source code, means of providing cloud and distributed computing, means of virtualization and storage systems, operating systems, means of preparing executable code	February 20, 2016
9	E1 Euphrates	Office applications, systems for the collection, storage, processing, analysis, modeling and visualization of data arrays, general purpose application software,	February 20, 2016
10	Alt Linux SPT	Executable code preparation tools, cloud and distributed computing tools, virtualization and storage systems, utilities and drivers, development, testing and debugging environments, source control version control tools, operating systems	February 20, 2016
11	ABBYY PassportReader SDK	Subprogram libraries (SDK), systems for collecting, storing, processing, analyzing, modeling and visualizing data arrays, linguistic software	February 20, 2016
12	ABBYY FineReader Bank	Linguistic software, information systems for solving specific industry problems, systems for collecting, storing, processing, analyzing, modeling and visualizing data arrays	February 20, 2016
13	ABBYY Scan Station	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
14	ABBYY Screenshot Reader		February 20, 2016
15	ABBYY Business Card Reader	Office applications, linguistic software	February 20, 2016
16	ABBYY Recognition Server	Linguistic software, systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
17	ABBYY Lingvo	Linguistic software	February 20, 2016
18	ABBYY Comparator	Linguistic software, office applications	February 20, 2016
19	ABBYY PDF Transformer	General-purpose application software, office applications, linguistic software	February 20, 2016
20	ABBYY FineReader	Office applications, linguistic software, general-purpose application software	February 20, 2016
21	1C-Bitrix24 (Company)	Office applications, project management, research, development, design and implementation management systems, systems for collecting, storing, processing, analyzing, modeling and visualizing data arrays, organization process management systems	February 20, 2016
22	1C-Bitrix24 (Project +)	Office applications, organization process management systems, systems for collecting, storing, processing, analyzing, modeling and visualizing data arrays, project, research, development, design and implementation management systems	February 20, 2016
23	1C-Bitrix24 (Team)	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays, project management, research, development, design and implementation systems, organization process management systems, office applications	February 20, 2016
24	1C-Bitrix24 (Holding)	Office applications, organization process management systems, project, research, development, design and implementation management systems, systems for collecting, storing, processing, analyzing, modeling and visualizing data arrays	February 20, 2016
25	1C-Bitrix24 (Corporate Portal)	Organization process management systems, office applications, systems for the collection, storage, processing, analysis, modeling and visualization of data arrays, project, research, development, design and implementation management systems	February 20, 2016
26	1C-Bitrix: Site Management - Enterprise	Organization Process Management Systems	February 20, 2016
27	1C-Bitrix: Website Management - Business	Organization Process Management Systems	February 20, 2016
28	1C-Bitrix: Website Management - Expert	Organization Process Management Systems	February 20, 2016
29	1C-Bitrix: Site Management - Small Business	Organization Process Management Systems	February 20, 2016
30	1C-Bitrix: Website Management - Standard	Organization Process Management Systems	February 20, 2016
31	Information and reference system "Code"	systems for the collection, storage, processing, analysis, modeling and visualization of data arrays, office applications, search engines, database management systems, general-purpose application software, information systems for solving specific industry problems	February 20, 2016
32	Accounting for claims	General-purpose application software, search engines, information systems for solving specific industry problems, organization process management systems	February 20, 2016
33	Executive Mobile Workplace	General-purpose application software, office applications, systems for the collection, storage, processing, analysis, modeling and visualization of data arrays, organization process management systems	February 20, 2016
34	Secure mobility	Information security tools, organization process control systems, general-purpose application software, office applications	February 20, 2016
35	1C-Bitrix: Website Management - Start	Organization Process Management Systems	February 20, 2016
36	Docsvision	Project management systems, research, development, design and implementation, organization process management systems	February 20, 2016
37	RAIDIX 4.0	Operating systems, server and middleware, cloud and distributed computing, virtualization and storage	February 20, 2016
38	Dr.Web CureIt!	General-purpose application software, information security tools	February 20, 2016
39	Dr.Web Katana		February 20, 2016
40	Dr.Web CureNet!		February 20, 2016
41	Dr.Web Mobile Security Suite	Information security tools, general purpose application software	February 20, 2016
42	Dr.Web Gateway Security Suite	Server and middleware software, information security tools, general purpose application software	February 20, 2016
43	Dr.Web Mail Security Suite	Server and middleware, general-purpose application software, information security tools	February 20, 2016
44	BARS. Education - E-College	Information systems for solving specific industry problems	February 20, 2016
45	BARS. Education - E-school	General-purpose application software, information systems for solving specific industry problems	February 20, 2016
46	Dr.Web Server Security Suite	Information security tools, server and middleware, general purpose application software	February 20, 2016
47	Dr.Web Desktop Security Suite	Information security tools, general purpose application software	February 20, 2016
48	Dr.Web Enterprise Security Suite	Information security tools, general purpose application software	February 20, 2016
49	BARS. Housing and communal services	Information systems for solving specific industry problems	February 20, 2016
50	BARS Inventory	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
51	BARS. Construction complex	Organization process management systems, information systems for solving specific industry problems, systems for collecting, storing, processing, analyzing, modeling and visualizing data arrays, project, research, development, design and implementation management systems	February 20, 2016
52	BARS. Stroykompleks - KapStroy	Information systems for solving specific industry problems, project management systems, research, development, design and implementation, systems for collecting, storing, processing, analyzing, modeling and visualizing data arrays	February 20, 2016
53	BARS. Stroykompleks - Control and Supervision	Information systems for solving specific industry problems, systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
54	BARS.Portal - Education	Information systems for solving specific industry problems	February 20, 2016
55	BARS Portal - Housing and Public Utilities	Information systems for solving specific industry problems	February 20, 2016
56	BARS Effective Region	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
57	BARS Monitoring - Management Efficiency	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
58	BARS Monitoring - Energy Efficiency	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
59	BARS Monitoring - Transport	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
60	BARS Monitoring - Agriculture	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
61	BARS Monitoring - Education	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
62	BARS Monitoring-Youth Policy, Sports	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
63	BARS Monitoring - Health Insurance	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
64	BARS Monitoring - Culture	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays	February 20, 2016
65	BARS. Education - Electronic Kindergarten	Information systems for solving specific industry problems	February 20, 2016
66	BARS Property Management	Information systems for solving specific industry problems	February 20, 2016
67	BARS Energy Efficiency	Information systems for solving specific industry problems	February 20, 2016
68	BARS.ZHKH - Billing Center	Information systems for solving specific industry problems, general-purpose application software	February 20, 2016
69	Prognoz platform		February 20, 2016
70	1C: Retail 8		February 20, 2016
71	1C: Theater	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
72	1C: ERP Enterprise Management 8	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
73	MyOffice Mail	Office applications	February 20, 2016
74	Reporting Code Automation Complex (CASO)	Systems for the collection, storage, processing, analysis, modeling and visualization of data arrays, general-purpose application software, information systems for solving specific industry problems	February 20, 2016
75	Glonass Control and accounting of transport	Server and middleware, monitoring and control systems, information systems for solving specific industry problems	February 20, 2016
76	1C: Accounting 8	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
77	1C: School. History of the Middle Ages, Grade 6	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
78	TrueConf Server	Office applications, general-purpose application software, server and middleware	February 20, 2016
79	1C: Library	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
80	1C: School. Computer science. Grade 10	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
81	IS RPGU	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
82	IndorCAD / Road	Collection, storage, processing, analysis, modeling and visualization systems of data arrays, information systems for solving specific industry problems	February 20, 2016
83	Algorius Net Viewer		February 20, 2016
84	Algorius net watcher	Monitoring and control systems	February 20, 2016
85	1C: Museum	Organization process management systems, information systems for solving specific industry problems	February 20, 2016
86	System for automation of office work and electronic document management (“Case”)	Information security tools, organization process control systems, subprogram library (SDK), office applications, general purpose application software	February 20, 2016
87	Rp server	Development, testing and debugging environments, preparation tools for executable code, tools for version control of source code, library routines (SDK)	February 20, 2016

The current roster is available on the website of the Ministry of Communications

Starting January 1, 2016, all state and municipal authorities, state corporations Rosatom and Roskosmos, government bodies for state extra-budgetary funds, as well as state and budgetary institutions that make purchases in accordance with the requirements of the Contractual System for the Procurement of Goods, Works services to ensure state and municipal needs, ”are required to comply with the ban on the admission of software originating from foreign countries, for the purpose of procurement to ensure state gift and municipal needs.

In order to make a decision on the purchase of software, the customer needs to work with the registry. When working with the Russian software registry, the customer placing an order for the supply of software products must:

1) study the classifier and determine which class corresponds to the software planned for purchase;

2) go to the official website of the registry and find out if the registry contains information about the software for this class (how to do this, see below);

3) if information about one or several software products for the desired class is in the register, the customer will need to independently determine whether at least one of the products meets the characteristics that are required by the customer and which he plans to include in the description of the procurement object. To do this, it is advisable to determine the required functional, technical and operational characteristics of the software and compare them with similar characteristics of the software, information about which is placed in the registry.

An exemplary form of comparison of characteristics is given below:

No. p / p	Software Features	Required	Product A	Product B
1.	Functional characteristics
1.1.	Centralized management	Yes	Yes	Yes
1.2.	Physical and virtual infrastructure management	Yes	Limited	Yes
…	Ability to manage virtualization environments from multiple vendors	Yes	Yes	Yes
2.	Specifications
2.1.	Maximum number of virtualization hosts	64	64	200
2.2.	Maximum number of virtual machines	3000	8000	Not documented
2.3.	Automatic recovery of a VM after a failure (HA)	Yes	Yes	Yes
3.	Operational characteristics
3.1.	Integration with AD	Yes	Yes	No
3.2.	Centralized management via web browser	yes	Yes	Yes
3.3.	Availability of backup API	No	Yes	No

Note

It should be noted that in accordance with the Decree of the Government of the Russian Federation No. 1236 regarding software specifications, the registry entry contains only the address of the page of the copyright holder’s website in the information and telecommunication network Internet, which contains documentation describing the functional characteristics of the software and information necessary for installation and operating software. In practice, the site of the copyright holder does not always contain all the necessary information about the software. The mechanism for obtaining such information for the preparation of the justification is not regulated. In case of insufficient information on the necessary software, it is advisable to request the copyright holder to provide such characteristics.

Based on the results of the work, the customer makes one of two decisions: either purchase one of the Russian software products listed in the registry, or justify the purchase of software not included in the registry.

The second is possible if:

a) the registry does not contain information about the software of the desired class;

b) the software, information about which is included in the register for the required class, does not meet the requirements of the customer in terms of its functional, technical and (or) operational characteristics.

In this case, the customer must prepare, approve and publish (together with the procurement documentation). Such an obligation is established by Part 3 of Article 14 of Federal Law dated April 5, 2013 No. 44-ФЗ “On the Contract System in the Sphere of Procurement of Goods, Work, and Services to Ensure State and Municipal Needs”. The procedure for preparing the justification (Procedure) is approved.

It is worth paying attention that in accordance with paragraph 4 of the Procedure, the customer must approve the specified justification as of the date of placement of the notice on the procurement. It is not enough to approve the rationale at the same time as the entire package of procurement documents.

To comply with this provision, given the complex procurement procedures as a whole, customers should monitor not only the registry itself, but also applications submitted for inclusion in the registry (they are also available on the registry operator's website). This will make it possible to foresee the inclusion of one or another software in the registry.

It is advisable to prepare a draft justification at the time of preparation of the full package of procurement documentation, and then update and approve it on the day of publication.

The rationale should include an indication of:

a) the circumstance in connection with which it is impossible to comply with the ban (subparagraph “a” or “b” of paragraph 2 of Government Decree No. 1236 is selected);

b) the class (classes) of software to which (which) the software that is the subject of the purchase must correspond;

c) the requirements for the functional, technical and operational characteristics of the software that is the subject of the procurement, established by the customer (indicating the class (s) to which (which) the software must comply, see above);

d) functional, technical and (or) operational characteristics, including quantitative, for which software products from the registry do not meet the requirements established by the customer for the software product that is the subject of procurement for each software product from the registry (indicating its name). Software products thus compared must belong to the same class ().

See also examples of justifications for the impossibility of purchasing software from the registry:; . You can see more examples of similar documents presented in support of the inability to purchase a domestic software product.

If the registry does not contain information about the software for the desired class (subparagraph “a” of paragraph 2 of Government Decree No. 1236 is selected), the last block (“g”) is not included in the rationale.

For this block (“d”), it should also be borne in mind that the Decree of the Government of the Russian Federation No. 1236 does not provide for a mandatory indication of the functional, technical, and operational characteristics of the purchased software in order to prove its difference from the software specified in the registry. Nevertheless, incorrectly specified characteristics of both the software required by the customer and the software placed in the registry may serve as a basis for claims by regulatory authorities. The reason for the claims may be, for example, an appeal from a software developer, the details of which are entered in the registry, with a complaint to the Federal Antimonopoly Service about the incorrect justification by the customer of the impossibility of observing the ban.

In case of insufficient information on the characteristics of the software, information about which is placed in the registry, it is advisable to request the copyright holder to provide such characteristics.

If such information is not provided, it is advisable to take screenshots of the pages of the copyright holder’s site, which contain information about the characteristics of the software from the registry (at the time of justification publication), and attach these screenshots to the justification.

An example of the justification of the inability to comply with the prohibition on the purchase of software is given in.

Checking the registry for information about software for a particular class on the reestr.minsvyaz.ru website in its current form is performed as follows:

1) on the Russian software registry website, go to the "Registry" section;

2) select the necessary class (classes) of software:

3a) if there is no information on the software for the required class in the registry, the corresponding message appears:

3b) if the registry contains information about the software of the desired class, a list of software products appears:

Actual additions (as of December 2017)

In March 2017, the government approved programs for electronic computers and databases, the details of which are included in the register of Russian software. Requirements determine the composition, architecture, functions of the software needed to replace imported counterparts.

In particular, the software interface should be implemented in Russian. The software should not require the installation of other software (additional software modules, fonts) that has any restrictions on its free distribution in Russia, with the exception of operating systems. Software updates should only be performed after confirmation by the user or authorized personnel. At the same time, for each type of software (operating system, communication software, office suite, mail applications, organizer, viewing tools, Internet browser, presentation editor, spreadsheet editor, text editor, file manager software, legal reference system (PCA), software electronic document management systems and anti-virus protection tools) special requirements are provided.

According to the resolution, the registry entry is supplemented with information on compliance or non-compliance of the software with additional requirements. However, as of the end of 2017, such information in the registry could not be found.

In June 2017, the Ministry of Communications announced the implementation of plans for the transition of federal executive bodies and state extra-budgetary funds to the use of domestic office software, including in exchange for previously purchased office software.

For a complete list of regulations related to software import substitution, see

Dear Colleagues!

Interesting and useful material for state and municipal customers is available on the website of the Expert Center of the Electronic State d-russia.ru. This material contains step-by-step instructions on the application of Decree of the Government of the Russian Federation of November 16, 2015 No. 1236 “On the establishment of a ban on the admission of software originating from foreign states for the purpose of procurement to meet state and municipal needs”.

Russian software registry - instructions for government customers

Starting January 1, 2016, all state and municipal authorities, state corporations Rosatom and Roscosmos, government bodies for state extra-budgetary funds, as well as state and budgetary institutions engaged in procurement in accordance with the requirements of Federal Law No. 44 of April 5, 2013 -FZ "On the contract system in the field of procurement of goods, work, services to meet state and municipal needs", are required to comply with the ban on the admission of software originating from foreign countries, for the purposes of suschestvleniya purchases for state and municipal needs.

1) examine the classifier and determine which class corresponds to the software planned for purchase;

2) go to the official website of the registry and find out if there is information in the registry about software for this class (see below for how to do this);

3) if there is information about one or several software products for the desired class in the registry, the customer will need to independently determine whether at least one of the products meets the characteristics that are required by the customer and which he plans to include in the description of the procurement object. To do this, it is advisable to determine the required functional, technical and operational characteristics of the software and compare them with similar characteristics of the software, information about which is placed in the registry.

An exemplary form of comparison of characteristics is given below:

No. p / p	Software Features	Required	Product A	Product B
1.	Functional characteristics
1.1.	Centralized management	Yes	Yes	Yes
1.2.	Physical and virtual infrastructure management	Yes	Limited	Yes
…	Ability to manage virtualization environments from multiple vendors	Yes	Yes	Yes
2.	Specifications
2.1.	Maximum number of virtualization hosts	64	64	200
2.2.	Maximum number of virtual machines	3000	8000	Not documented
2.3.	Automatic recovery of a VM after a failure (HA)	Yes	Yes	Yes
3.	Operational characteristics
3.1.	Integration with AD	Yes	Yes	No
3.2.	Centralized management via web browser	yes	Yes	Yes
3.3.	Availability of backup API	No	Yes	No

Note

The second is possible if:

and) the registry does not contain information about the software of the desired class;

b) software, information about which is included in the register for the required class, does not meet the requirements of the customer in terms of its functional, technical and (or) operational characteristics.

In this case, the customer must prepare, approve and publish (together with the procurement documentation) a rationale for the impossibility of complying with the ban. Such an obligation is established by Part 3 of Article 14 of Federal Law dated April 5, 2013 No. 44-ФЗ “On the Contract System in the Sphere of Procurement of Goods, Work, and Services to Ensure State and Municipal Needs”. The procedure for preparing the justification (Procedure) was approved by the Government Decree of November 16, 2015 No. 1236.

It is advisable to prepare a draft justification at the time of preparation of the full package of procurement documentation, and then update and approve it on the day of publication.

The rationale should include an indication of:

and) the circumstance in connection with which it is impossible to comply with the prohibition (subparagraph “a” or “b” of paragraph 2 of Government Decree No. 1236 is chosen);

b) the class (classes) of software to which (which) the software being the object of the purchase must correspond;

at) requirements for the functional, technical and operational characteristics of the software being the object of purchase established by the customer (indicating the class (s) to which (which) the software should correspond, see above);

d) functional, technical and (or) operational characteristics, including quantitative ones, for which software products from the registry do not meet the requirements established by the customer for the software product that is the subject of procurement for each software product from the registry (with its name). Software products thus compared should belong to the same class ( software product comparison example).

On this block ("G") it should also be borne in mind that the Decree of the Government of the Russian Federation No. 1236 does not provide for a mandatory indication of the functional, technical, and operational characteristics of the purchased software in order to prove its difference from the software specified in the registry. Nevertheless, incorrectly specified characteristics of both the software required by the customer and the software placed in the registry may serve as a basis for claims by regulatory authorities. The reason for the claims may be, for example, an appeal from a software developer, the details of which are entered in the registry, with a complaint to the Federal Antimonopoly Service about the incorrect justification by the customer of the impossibility of observing the ban.

An example of the justification of the inability to comply with the prohibition on the purchase of software is given in the appendix.

Checking the registry for information about software for a particular class on the reestr.minsvyaz.ru website in its current form is performed as follows:

1) on the Russian software registry website, go to the "Registry" section;

2) we select the necessary class (classes) of software:

3a) if there is no information on the software for the required class in the registry, the corresponding message appears:

3b) if the registry contains information about the software of the desired class, a list of software products appears:

Decree of the Government of the Russian Federation of March 23, 2017 No. 325 “On approval of additional requirements for programs for electronic computers and databases, information about which is included in the register of Russian software, and amendments to the Rules for the formation and maintenance of a unified register of Russian programs for electronic computers and databases ”

In accordance with paragraph 6 of Article 12.1 of the Federal Law "On Information, Information Technologies and the Protection of Information", the Government of the Russian Federation decides:

1. Approve the attached:

additional requirements for programs for electronic computers and databases, information about which is included in the register of Russian software;

amendments to the Rules for the Formation and Maintenance of a Unified Register of Russian Programs for Electronic Computers and Databases, approved by Decree of the Government of the Russian Federation of November 16, 2015 No. 1236 "On the establishment of a ban on the admission of software originating from foreign countries, for the purposes of the implementation of procurements to ensure state and municipal needs "(Collected Legislation of the Russian Federation, 2015, No. 47, Article 6600).

2. To the federal executive bodies and state extra-budgetary funds, when procuring programs for electronic computers and databases to meet state needs, information about which is included in the Russian software registry, to ensure that additional requirements approved by this resolution are met.

3. The Ministry of Telecom and Mass Communications of the Russian Federation:

to approve the procedure and methodology for confirming compliance of programs for electronic computers and databases, the details of which are included in the register of Russian software, with additional requirements approved by this resolution;

bring regulatory legal acts in accordance with this resolution;

within 6 months from the date of the official publication of this resolution, to provide confirmation of the compliance of the software included in the Russian software registry with the additional requirements approved by this resolution.

4. Changes approved by this resolution shall enter into force after 6 months from the date of official publication of this resolution.

APPROVED
government decree
Russian Federation
march 23, 2017 No. 325

Additional requirements
to programs for electronic computers and databases, information about which is included in the register of Russian software

I. General Provisions

1. This document defines the requirements for programs for electronic computers and databases, the details of which are included in the Russian software registry, in terms of the composition and functional characteristics of software intended, inter alia, to automate the functions of employees of federal executive bodies and state extra-budgetary funds of the Russian Federation in the performance of official duties (hereinafter referred to as users, software).

2. Information support for users (hereinafter referred to as user support) should be provided in accordance with this document throughout the Russian Federation without restrictions.

II. Requirements for the composition, functional characteristics and functioning environment of office software

3. Office software includes the operating system, communication software, office suite, mail applications, organizer, viewers, Internet browser, presentation editor, spreadsheet editor, text editor, file manager software, legal reference system, software electronic document management systems and anti-virus protection tools.

Office software consists of stand-alone and / or network software and client software. Office software can be a set of interconnected software products that correspond to the classifier of programs for electronic computers and databases in accordance with the legislation of the Russian Federation.

4. Office software should provide users with personal electronic computers, terminal access devices and subscriber radio mobile devices without connecting to local area networks, and (or) using the Internet information and telecommunication network, and (or) using infrastructure providing information and technological interaction of information systems used to provide public services and execution of state real functions in electronic form, creation, access, processing, storage and deletion of electronic documents ("cloud" technology), and (or) using local area networks of user access to software installed on server hardware.

5. If the office software has a user identification and authentication function, it should be possible to identify and authenticate users using, among other things, the federal state information system "Unified System for Identification and Authentication in the Infrastructure that Provides Information and Technology Interaction of Information Systems Used to Provide state and municipal services in electronic form "in the manner prescribed Russian legislation.

6. The office software interface should be implemented in Russian. The office software interface can be implemented using additional other languages.

7. Office software should not require the installation of other software (additional software modules, fonts) that has any restrictions on its free distribution in the Russian Federation, with the exception of operating systems.

8. Updates to office software should only be performed after confirmation by the user of the office software or authorized employees.

9. If a user accesses office software using Internet browser tools, office software must provide the ability to use Internet browsers of at least 3 different copyright holders of exclusive rights to a program for electronic computers or a database (copyright holders, groups of copyright holders), information about one of which is included in the unified register of Russian software.

10. Office software must comply with the requirements of the legislation of the Russian Federation on the protection of information and on the protection of personal data in cases established by the legislation of the Russian Federation.

Data transmission via communication channels, including text messages and (or) electronic documents, voice, sound, visual and other information using office software should be subject to the requirements of the legislation of the Russian Federation on information protection and communication.

11. The functional characteristics of office software and its operating environment must comply with the following requirements:

a) requirements for the functioning environment of office software:

office software, with the exception of operating systems, must run the following operating systems:

for a user's workstation (personal electronic computer or terminal access device) - running at least 2 different operating systems, the details of which are included in the unified register of Russian software, and Microsoft Windows operating systems (version 7 and higher) certified in compliance with the requirements of the legislation of the Russian Federation on information protection;

for server equipment - running at least 2 operating systems, information about which is included in the unified register of Russian software, and Microsoft Windows Server operating systems (versions 2008 and higher), while ensuring the functioning of office software running operating systems for server equipment can be used virtualization tools;

for radio mobile subscriber devices - running Android, iOS operating systems;

operating systems for the user's workstation should include an operating mode that allows implementing the functionality of office software that operates and works in other operating systems specified in the third paragraph of this subclause;

b) requirements for communication software:

communication software, which is software for the creation and processing of information, as well as user interaction through the transmission of information using telecommunication channels, including secure communication channels, and (or) local area networks, using an automated workstation and (or ) subscriber devices of mobile radio communication of the user must provide:

creation, viewing, editing, copying, printing of information processed using communication software, and transmission of information using telecommunication channels and local area networks, including the attachment of electronic documents, electronic messages, including text messages, images, audio files and video files;

delivery to the user of notifications of electronic messages transmitted by other users of the communication software to the terminal access equipment of the user on which the communication software is installed or with which access to the communication software installed on the server equipment is carried out;

the ability to disable the user’s function of delivering notifications of electronic messages received by him;

the ability to save and delete text messages and electronic documents on personal electronic computers and on subscriber radio mobile devices;

the ability to perform searches on saved text messages and electronic documents in case of lack of user access to server software using a local area network or lack of access to the Internet telecommunications network;

the ability to store electronic messages and electronic documents on personal electronic computers, server equipment and subscriber radio mobile devices, as well as transfer electronic messages and electronic documents to a centralized repository;

transfer of text messages and electronic documents created by users using communication software to federal information systems;

the ability to print information processed using communication software;

data transfer using communication software can be carried out through open communication channels, as well as secure communication channels using encryption (cryptographic) means of information protection, certified in accordance with the requirements of the legislation of the Russian Federation;

c) requirements for an office package:

office suite, which is a separate software or a set of interconnected office software with a unified interface for creating, viewing, editing, saving, deleting electronic documents, exchanging electronic documents and implementing other ways of processing them, as well as providing the ability to print information if necessary processed using appropriate software should provide functionality of at least 4 of the following types of software:

text editor;

spreadsheet editor;

presentation editor;

mail applications

communication software;

file manager software;

organizer

viewers

the office suite in terms of a text editor, spreadsheet editor, and presentation editor should provide for joint work on an electronic document of a group of users, including the ability to record changes in an electronic document in real time;

the office suite must meet the requirements for the functional characteristics of the corresponding software;

d) requirements for the mail application:

an email application, which is software (hereinafter referred to as email software) for viewing, creating, editing, deleting, saving, printing, and transmitting email messages, must provide:

creation, editing, deletion and transmission of electronic text messages and attachment of electronic documents to them, automatic saving of electronic documents and email messages;

creation, deletion, renaming of directories of e-mail messages in the electronic mail system (hereinafter referred to as directories of the electronic mail system);

the ability to save, delete, copy and move email messages in directories of the electronic mail system;

the ability to search for e-mail messages in the user's e-mail inbox using, among other things, various search criteria for e-mail messages;

creation, editing, deletion and transmission of electronic text messages in several electronic mailboxes (email addresses) using a single user interface;

displaying, using a single user interface, the e-mail software, e-mail messages from several electronic mailboxes of the user (e-mail addresses);

unified display of email messages on topics using a single user interface;

automatic creation and change of settings of connected electronic mailboxes of the user on all user devices on which the email software is installed and used;

creating, deleting, changing the processing order of e-mail messages in accordance with the criteria set by the user, including automatic transfer of e-mail messages to directories of the e-mail system, delayed sending of e-mail messages at a time set by the user, automatic reply to received e-mail messages

creating, deleting, editing user information and automatically adding such information to the generated electronic message;

the ability of the user to select the email address of the other recipient (s) of the email message using the organization’s user directory and the user's personal directory;

the ability to print information processed using e-mail software;

the possibility of using certified electronic signature means using qualified certificates in order to ensure the integrity of transmitted email messages;

information and technological interaction between the server email software and client email software should be carried out including using the following protocols:

SMTP or ESMTP - for sending email messages;

IMAP or POP3 - to receive email messages;

HTTPS - for interaction with the web client of the electronic mail system;

CalDav - to create and receive information about events entered in the calendar;

CardDav - to create and receive a list of personal contacts and a list of users of the organization;

in email software should be implemented:

means for automatically detecting unwanted email messages and automatically moving them to the appropriate directory of the electronic mail system;

integration tools with external anti-virus software, information about which is included in the unified register of Russian software;

in order to ensure the confidentiality of e-mail messages and electronic documents processed using e-mail software, this software must be able to integrate with cryptographic information protection means certified in accordance with the legislation of the Russian Federation;

e) requirements for the organizer - the organizer, which is software for creating, editing, storing, deleting and transmitting information about contacts, tasks and events of the user, must provide:

creation of information about contacts, tasks and user events;

view schedule information in the user's calendar

removing an event from the user's calendar

editing events in the user's calendar;

the ability to support user collaboration;

the ability to differentiate user access rights to information;

the ability to provide information about user events to other users;

information exchange between server software and client software installed on the user's workstations and on the user's mobile radio subscriber devices, which should be carried out using CalDav information exchange protocols as well;

f) requirements for viewers - viewers, which are software for viewing electronic documents without the possibility of changing them, should provide the ability to view electronic documents stored, including in formats corresponding to various extensions of electronic documents, including bmp, jpg, jpeg, png, gif, tif, tiff, OOXML, docx, doc, pptx, rtf, txt, pdf, xls, xlsx, odt, ods, odp, avi, mpeg, mp3;

g) requirements for an Internet browser - Internet browser tools must support html5, CSS3, javascript technologies, as well as other technologies;

h) requirements for the presentation editor - presentation editor, which is a software for viewing, creating, editing, deleting and printing information processed using the presentation editor, and saving presentation materials in the form of electronic documents consisting of a set of slides containing user-defined structured information, including textual, graphical, tabular and audiovisual information (hereinafter referred to as slides), must provide:

creation of new electronic presentation documents, including the Open Document Format (GOST R ISO / IEC 26300-2010) and Office Open XML (OOXML, PPTX) formats;

opening of existing electronic presentation documents, including the Open Document Format (GOST R ISO / IEC 26300-2010) and Office Open XML (OOXML, PPTX) formats;

the use of various fonts to design text information placed on slides;

design of text information placed on slides using various colors and backgrounds;

design of text information placed on slides using user-set fonts in bold, italic and underlined, as well as an arbitrary font size;

ensuring alignment of textual information in the center of the zone of information, on the left or right border of the zone of information, as well as the width of the zone of information;

insertion into the slide and removal from the slide of graphic and other elements, including graphic images, audio and video information;

setting up a slide show;

printing slides using document printing devices;

slide show, as well as displaying information posted on slides using the equipment of the terminal interface;

saving electronic presentation documents in formats supported by software, including Open Document Format (GOST R ISO / IEC 26300-2010), Office Open XML (OOXML, PPTX) and Portable Document Format (PDF);

i) requirements for a spreadsheet editor - a spreadsheet editor (spreadsheet editor), which is software for viewing, creating, editing, deleting and saving an electronic document (including a spreadsheet document), must provide:

creation of new electronic spreadsheet documents, including Open Document Format (GOST R ISO / IEC 26300-2010) Office Open XML (OOXML, XLSX);

opening of existing electronic spreadsheet documents, including the Open Document Format (GOST R ISO / IEC 26300-2010) and Office Open XML (OOXML, XLSX) formats;

data entry into the table;

deleting data from a table;

editing and copying data, including adding, changing, deleting and copying the contents of cells and ranges of table cells;

design of tabular data, including combining and separating table cells, selecting the font, color of the input information, cell background, designing the borders of the table as a whole and its parts;

formatting data in table cells, including data in the formats of numerical, text, monetary, financial and percentage;

support for the ability to display graphs and charts;

the ability to create and delete sheets of an electronic spreadsheet document;

the ability to apply formulas (including mathematical ones) in Russian and English to the table data, as well as automatically display the calculation results of user-selected formulas by the selected cell or range of cells in the status bar;

the ability to cancel any operation committed during the editing process and return the canceled operations;

joint editing of the table without limiting the functionality of the software;

use of table templates;

printing information contained in tables using document printing devices;

saving tables in formats supported by the software, including the Open Document Format (GOST R ISO / IEC 26300-2010), Office Open XML (OOXML, XLSX) and Portable Document Format (PDF) formats;

j) requirements for a text editor - a text editor, which is software for viewing, creating, editing and saving an electronic document, must provide:

creation of electronic text documents, including the Open Document Format (GOST R ISO / IEC 26300-2010) and Office Open XML (OOXML, DOCX) formats;

opening of existing electronic text documents, including the Open Document Format (GOST R ISO / IEC 26300-2010) and Office Open XML (OOXML, DOCX) formats;

data input into an electronic text document, as well as their editing;

preparation of electronic text documents on forms A0, A1, A2, A3, A4, A5, A6;

longitudinal arrangement of details on the form of an electronic text document;

setting an arbitrary size of indentation from the left edge of the electronic text document;

enabling the numbering of various list items;

the ability to use user-set fonts in bold, italic, underlined, as well as font sizes of 10, 12, 13, 14 or any size;

the ability to highlight the text in the letter in capital letters and spaced;

the ability to align text information in an electronic text document in the center, on the left and right border of the text field, as well as the width of the text field;

the ability to set the line spacing;

the ability to set a separate numbering for the first and subsequent pages of an electronic text document, including page numbering in the center of the header or footer;

the ability to set the indent from the border of the upper field of an electronic text document;

the ability to set the width of the upper, lower, right and left margins of an electronic text document;

the ability to cancel any operations completed during the editing process and return canceled operations;

the ability to record corrections in an electronic text document;

joint editing of an electronic text document by several users (up to 10 or more users);

the ability to automatically check spelling, syntax and punctuation in accordance with the rules of the Russian language, including the ability to use external electronic spelling dictionaries of the Russian language;

saving an electronic text document in formats supported by the software, including the Open Document Format (GOST R ISO / IEC 26300-2010), Office Open XML (OOXML, DOCX) and Portable Document Format (PDF) formats;

providing the possibility of preparing electronic text documents based on standard document templates in accordance with GOST R 6.30-2003 and the requirements of the legislation of the Russian Federation in the field of organization of office work and document circulation in the activities of state bodies;

k) requirements for the file manager software — the file manager, which is software for creating, copying, renaming, and deleting directories of electronic documents, must provide the ability to delete, copy, and move electronic documents;

l) requirements for legal reference systems - a legal reference system should:

provide a permanent information retrieval service for the provision of legal acts and reference information documents;

provide a network version of a legal reference system with a regularly updated databank of federal and regional legislation, installed on a user's local computer network and allowing work with a legal reference system, including when there is no access to the Internet information and telecommunication network;

m) requirements for software of the electronic document management system - the software of the electronic document management system must comply with the requirements of the legislation of the Russian Federation for information systems of electronic document management;

n) requirements for anti-virus protection means - anti-virus protection means must protect data processed using information and communication technologies in accordance with the requirements for an information system in which anti-virus protection means are used, with the possibility of operational monitoring and analysis of event logs from a single Admin Console

12. Office software, if necessary, import (export) of data should provide the ability to process data in one of the following formats:

Open Document Format (GOST R ISO / IEC 26300-2010);

Office Open XML (OOXML, DOCX, XLSX, PPTX, project ISO / IEC IS 29500: 2008);

PDF / A-1, which complies with ISO 19005-1: 2005, “Document management. Electronic document file format for long-term preservation. Part I: Use of PDF 1.4 (PDF / A-1)” (Document management - Electronic document file format for long-term preservation - Part I: Use of PDF 1.4 (PDF / A-1) in accordance with the legislation of the Russian Federation;

common files for exchanging audio and video information, electronic text documents (for example, bmp, jpg, jpeg, png, gif, tif, tiff, rtf, txt, zip, avi, mpeg, mp3).

13. In office software, program interfaces (APIs) must be implemented and documented for integration with other systems.

14. Office software must ensure compatibility with document formats based on the Open Document Format (GOST R ISO / IEC 26300-2010), as well as the Portable Document Format (PDF).

15. The operational documentation supplied with the office software must contain materials in electronic form in Russian, including:

user's manual;

installation guide;

administration Guide

system requirements;

information about the new software version.

III. Software Maintenance Requirements

16. User support is provided through the use of telephone communications and electronic mail in Russian around the clock.

17. Contact and other information necessary for the interaction of users and the copyright holder of the software in the framework of user support should be published on the official website of the software manufacturer in the information and telecommunication network "Internet".

APPROVED
government decree
Russian Federation
march 23, 2017 No. 325

Changes
which are entered into the Rules for the formation and maintenance of a single register of Russian programs for electronic computers and databases

1. Paragraph 4 shall be supplemented with subparagraph "n" as follows:

“m) information on compliance or non-compliance of software with additional requirements for programs for electronic computers and databases, information about which is included in the register of Russian software approved by the Government of the Russian Federation dated March 23, 2017 No. 325“ On approval of additional requirements to programs for electronic computers and databases, information about which is included in the register of Russian software, and amendments to the Rules and the formation and maintenance of a single register of Russian programs for electronic computers and databases "(hereinafter - additional requirements).".

2. Paragraph 19 shall be supplemented with a paragraph as follows:

"The authorized body, within 30 days from the date of inclusion of information in the registry, ensures verification and confirmation of compliance of the software with additional requirements in accordance with the procedure and methodology approved by the authorized body for confirming compliance of programs for electronic computers and databases, information about which is included in the register of the Russian software collateral, additional requirements. ".

Document Overview

Additional requirements are established for domestic office software included in the Russian Software Registry. They will be used as part of public procurement.

The software includes the operating system, communication software, office suite mail applications, organizer, viewers, Internet browser presentation editor, spreadsheet editor, text editor, file manager software, legal reference system (PCA), electronic document management system software and tools antivirus protection.

Requirements determine the composition, architecture, functions of the software needed to replace imported counterparts.

Moreover, for each type of software special requirements are provided.

So, ATP should provide a permanent information retrieval service for the provision of legal acts and reference information documents, as well as provide a network version with a regularly updated databank of federal and regional legislation, installed on a user's local computer network and allowing work with ATP in t including in the absence of access to the Internet.

The registry entry is supplemented by information on compliance or non-compliance of the software with additional requirements.