Approved. By order of the Ministry of Construction and Housing and Communal Services of the Russian Federation of December 15, 2017 N 1674 / pr

Code of practice SP-328.1325800.2017

"INFORMATION MODELING IN CONSTRUCTION. RULES FOR DESCRIBING INFORMATION MODEL COMPONENTS"

Building information modeling. Components. Guidelines and requirements

Introduced for the first time

Introduction

This set of rules was developed in accordance with the Federal Law of December 30, 2009 N 384-FZ "Technical regulations on the safety of buildings and structures" in order to develop uniform requirements, rules and recommendations for the creation of components used to form information models of a construction object.

The set of rules was prepared by the team of authors of JSC "Research Center" Construction "- TsNIISK named after V.A.Kucherenko (work supervisor - Dr. Ananiev) and LLC "KONKURATOR" (M.G. Korol, S.E. Benklyan).

1 area of ​​use

1.1 This set of rules applies to the processes of information modeling of buildings and structures and establishes the requirements for the components of their information models.

1.2 This set of rules does not establish requirements for the methods of placement, maintenance, structure, form and content of digital libraries (catalogs / bases) of components.

2 Normative references

This set of rules uses normative references to the following documents:

GOST 2.303-68 Unified system for design documentation. Lines

GOST 2.306-68 Unified system for design documentation. Designations of graphic materials and rules for their application in drawings

Note - When using this set of rules, it is advisable to check the validity of reference documents in the public information system - on the official website of the federal executive body in the field of standardization on the Internet or according to the annual information index "National Standards", which was published as of January 1 of the current year , and on the issues of the monthly information index "National Standards" for the current year. If the referenced document to which the undated link is given is replaced, it is recommended that the current version of this document be used, taking into account all changes made to this version. If the referenced document to which the dated reference is given is replaced, it is recommended to use the version of this document with the above year of approval (acceptance). If, after the approval of this set of rules, a change is made to the referenced document to which the dated reference is given, affecting the provision to which the reference is made, then this provision is recommended to be applied without taking into account this change. If the referenced document is canceled without replacement, then the provision in which the link to it is given is recommended to be applied in the part that does not affect this link. It is advisable to check the information on the validity of the sets of rules in the Federal Information Fund of Standards.

3 Terms and definitions

In this document, the following terms and definitions are used:

3.1 component attributes: Essential properties of a component that are necessary to define its geometry or characteristics and have a name and meaning.

3.2 component geometric parameters: Attributes that define the size, shape and spatial position of a component.

3.3 graphic properties of a component: Properties that ensure the recognizability of a component in a three-dimensional projection, as well as in various projections and scales with the display of characteristic two-dimensional symbols, lines, hatches, text.

3.4 information modeling of construction objects: The process of creating and using information on under construction, as well as completed construction objects in order to coordinate input data, organize joint production and storage of data, as well as their use for various purposes at all stages of the life cycle.

3.5 component: A digital representation of the physical and functional characteristics of an individual element of a construction site, intended for repeated use.

Note - A component applied in a model becomes a model element.

3.6 component metadata: Structured data representing the characteristics of a described component for identifying, retrieving, evaluating and managing it.

3.7 open data exchange formats: Data formats with an open specification.

NOTE - IFC (Industry Base Classes) format is an open specification data format and schema. It is an international standard for data exchange in information modeling in the field of civil engineering and operations.

3.8 assembly: A named set of components that can be reused.

3.9 level of elaboration; LOD: A set of requirements defining the completeness of a digital information model element. The level of development sets the minimum amount of geometric, spatial, quantitative, as well as any attribute data required to solve information modeling problems at a particular stage of the object's life cycle.

3.10 functional behavior of a component: Changing a component in accordance with the rules of interaction with environmental conditions laid down in it.

3.11 digital information model: An object-oriented parametric three-dimensional model that digitally represents the physical, functional and other characteristics of an object (or its individual parts) in the form of a set of information-rich elements.

3.12 model element: Part of a digital information model representing an element, system or assembly within a construction site or construction site.

4 General

4.1 Components are characterized by geometric parameters, graphics properties, attributes and functional behavior.

4.2 Components should be separated:

By types:

Point - components with specified geometric shapes that are added to the model with reference to their insertion point.

NOTE Components such as window, door, beam, column, pump, furniture, etc .;

Linear - obtained by connecting a directed closed profile and a reference line as a generator.

NOTE Components such as walls, pipes, ducts, ducts, etc .;

Areal - volumetric components of significantly lower height, created by drawing a contour of a limited area.

NOTE Components such as floors, roofs, ceilings, etc .;

By reference to the manufacturer:

Generalized - the component is a digital representation of a product, the specific manufacturer of which is unknown;

Product - A component is a digital representation of a specific manufacturer's product.

By parameterization level:

Parametric components - components, placed instances of which can be configured by changing the attribute values ​​in the software interface (without the need to directly edit the component);

Nonparametric components are components that are created without the possibility of their configuration.

By scope:

Architecture;

Urban planning;

Building construction;

Engineering systems and networks;

Interior and exterior design;

Other areas of application.

5 General requirements for components

5.1 Component development should be performed using appropriate software tools that implement information modeling functionality.

5.2 When developing components, you should:

Consider the goals of using the digital information model;

Take into account the requirements for the levels of elaboration of model elements;

Determine the composition and number of geometric parameters;

Determine the composition and number of attributes.

6 Requirements for geometric parameters, levels of geometric elaboration and graphical display of components

6.1 Requirements for geometric parameters and graphical representation of a component include requirements for:

Geometric parameters;

Display of graphic symbols;

The level of geometric elaboration;

Reserving space occupied by a component;

Graphic display of materials.

6.2 Requirements for geometric parameters

6.2.1 When developing a component, you should:

Simulate geometry at a scale of 1: 1;

Define the insertion point (base point) for a point component;

Use the minimum number of construction elements (for example, construction planes and lines);

Use geometric parameters expressed in metric units.

6.2.2 Generic components shall include parameter values ​​defining nominal dimensions if the actual dimensions are not known.

6.2.3 Components of type "product" shall include parameter values ​​that define the exact dimensions.

6.2.4 Requirement for the display of graphic symbols:

the component must include graphic elements to convey information that cannot be displayed in a three-dimensional projection (for example, direction indicators, the direction of opening doors, ways of opening windows).

6.3 Requirements for the level of geometric elaboration

6.3.1 The insertion points (base points) of a component should be consistent across all levels of development.

6.4 Requirements for graphic display of materials

6.4.1 If an image is to fill the surface of a component, it must be square or rectangular in order to provide seamless repetition of the image (tiling).

6.4.2 Requirements for the file with the image of the material:

The size of square images - at least 512x512 pixels;

Size of rectangular images - at least 512 pixels along the longest side;

Image resolution - not less than 150 dots per inch.

7 Requirements for the level of attribution and attribute values

7.1 When developing components, the number, composition of attributes and the level of attributive elaboration should be determined taking into account:

Goals and objectives of using digital information models;

LOD requirements;

Requirements for the composition and content of technical documentation.

7.2 All created component attributes must be filled in.

7.3 Component attributes should be divided into mandatory and optional.

7.3.1 The mandatory attributes of a component should include those properties or technical characteristics that allow the component to be uniquely identified, and also contain data on the basis of which it is possible to develop technical documentation, order, purchase and install a specific component during the construction process.

7.3.2 Additional attributes should include properties or technical characteristics required for engineering calculations, information of a technical and economic nature, technical and operational and other characteristics.

7.4 If parameter values ​​are to control the geometric size or shape of a component, changing them should change the size and / or shape of the component in the model.

7.5 If the value of the attribute is not limited and allows the possibility of entering both numbers and letters, then the value of the attribute shall be assigned an alphanumeric data type.

7.6 The value of a text attribute of a component must not end with a period.

8 Functional requirements for components

8.1 A component shall "behave" in a manner that reflects its functionality and interrelationships with other components.

8.2 In a software environment, as a rule, it is possible to design a component with one or another number of predefined fixed parameters available in a real physical building element. If there are preconfigured variants of a component, the performance degradation or difficulty in using it should be minimal.

8.3 A component should be modeled so that it can be connected to and function in conjunction with other components if interoperability is supported and consistent with the objectives of the model being developed.

9 Rules for naming components and their attributes

9.1 The naming conventions for components in this section are intended for software based on a file storage system.

9.2 The naming system should consist of:

General naming rules;

Naming schemes.

NOTE - An example of a component file naming system is given in A.15-A.16 (Appendix A).

9.3 A component must have a unique name and description.

9.4 Attribute Naming Rules

9.4.1 Units of measurement are not indicated in the attribute name.

9.4.2 Attributes with values ​​that imply Boolean data types (Yes / No) should be named so that the value is necessarily assigned (for example, "Sill Presence" - Yes / No).

NOTE - An example of rules for naming attributes is given in A.17 (Appendix A).

9.5 Material naming conventions

9.5.1 The name of a material must begin with an uppercase letter followed by a lowercase letter. If the name consists of two or more words, then each word begins with a capital letter and all words are written together.

9.5.2 The file with the image of the material is named in the same way as for the material, with the extension corresponding to the format of the used graphic file.

NOTE - An example of rules for naming materials is given in A.18 (Appendix A).

10 Requirements for component formats

10.1 By file formats, components can be represented:

In open IFC format (versions 2x3 and higher);

In original formats (file formats of components and project files of the software used).

11 Component metadata requirements

11.1 When organizing databases / catalogs / libraries of components, for example, in the form of Internet storages, it is necessary to provide a convenient search for the required content. Typically, this search is carried out using metadata. Search by metadata - search by attributes of a component supported by a specific search engine.

Appendix A

A.1 Components can be combined into assemblies (for example, "plumbing", "heating unit", "transformer substation"), which are recommended to be used to form thematic catalogs / databases / libraries of reuse.

A.2 The component should be uniquely identified. For this it is recommended to use:

Unique name;

Globally unique identifier that is used to identify resources;

Classifier code (if any).

A.3 To minimize the number of components being developed and to unify them, it is recommended to create parametric components.

To comply with the requirements of ESKD and SPDS standards (for example, GOST 2.303 and GOST 2.306) for the design and working documentation, when developing a component, it is recommended to include conventional graphic symbols in its composition.

Note - Components at the LOD 100 development level are conceptual mass elements and, as such, do not need preliminary preparation of the corresponding components, and at the LOD 500 level, they are fully defined components that differ from the LOD 400 level only in dimensions that correspond to the actual implementation of the design decisions. For these reasons, LOD development levels of 200, 300 and 400 are recommended for the development of databases / libraries / catalogs of components.

NOTE In the absence of appropriate low-level components, higher-level components may be used.

A.8 It is recommended that the engineering / process equipment components be designed taking into account the maintenance space reserved, which is recommended to be included as part of the component.

A.9 If it is necessary to develop a component with a specific material, it is recommended to include colors, hatch / fill patterns and files with a texture image in the appropriate scale.

A.12 The value of a component attribute can be expressed as a formula if its value depends on other attributes.

A.13 If a component can represent different variants of an element of a construction object, it is recommended to represent them using an attribute with a value expressed in one of the following ways:

The only value is if there is only one choice for the value;

List value - if the ordered list contains several unique values ​​of the same type, the order of which is important (for example, 200, 400, 600, 800);

Range value - if there are upper and lower limits of this value (limit). The lower limit is indicated first, followed by the upper limit (eg 175-200 kW). If the range of values ​​includes positive and negative values, they are separated using the words "from" and "to" (for example, from minus 10 ° C to plus 20 ° C). If no value is specified, it means an unlimited limit (for example, 175 kW -<ноль>, i.e. all values ​​are greater than or equal to the lower limit value of 175 kW);

Numbered value - if the value provides for the selection of fixed values ​​from the established list. Separate elements must be separated from each other by comma and space (for example, a, b, c, d).

Note - These methods of expressing different variants of elements of a construction object, as a rule, are used in components of the "generalized" type.

A.14 A component is recommended to be modeled in such a way that it can be connected to other components and function in conjunction with them, if the joint functioning is supported and corresponds to the objectives of the developed model.

The file name consists of fields;

It is recommended to use the underscore "_" as a separator character between fields;

All fields in a file name start with an uppercase letter followed by a lowercase letter. If the field consists of two or more words, then each word begins with a capital letter and all words are written together;

Abbreviations and codes should be written in capital letters;

A.16 Component file name structure

<Поле1>_<Поле2>_<Поле3>_<Поле4>_<Поле5>_<Поле6>

where the fields have the meanings given in Table A.1.

Table A.1

If the component does not contain 3D geometry, at the end of "Fields2" (functional type), add "-2D".

Notes (edit)

1 The number of fields in the file name can vary from four to six, depending on the type of component (type "generic" or "product"), as well as the presence of additional identifying characteristics.

2 An example of naming components of the "generic" type:

ABV_Door_Double_Aluminum_GOST23747-2015

3 An example of naming components of the "product" type:

ABC_Washbasin_Ceramic_Factory1_VersionA

If you need to enter additional fields, it is recommended to add them at the end of the name.

A.17 Attribute naming rules

<Поле1>_<Поле2>

where the fields have the following meanings given in Table A.2

Table A.2

NOTE - Examples of naming attributes:

Profile Width

ABC_AreaApartments

<Поле1>_<Поле2>_<Поле3>_<Поле4>_<Поле5>

where the fields have the following meanings given in Table A.3

Table A.3

NOTE - Example of naming materials:

ABC_Tiles_Bituminous_Continent_Manufacturer

May 28th, 2018 Tatiana Bekh

GOST and SP for BIM

We decided to collect a list of normative documents regulating the direction of information technology in construction. Here's what was found on present day!

List of normative documents on BIM:

• GOST R 57310 —2016 (ISO 29481 —1: 2010) Information modeling in construction. Delivery information guide. Methodology and format. Date of introduction 2017 —07 —01
• GOST R 57311 —2016 Information modeling in construction. Requirements to operational documentation of completed construction objects. Date of introduction 2017 —07 —01
• GOST R 57309 —2016 (ISO 16354: 2013) Guidelines for knowledge libraries and object libraries. Date of introduction 2017 —07 —01.
• GOST R 57563 —2017 / ISO / TS 12911: 2012 Information modeling in construction. Fundamentals for the development of standards information modeling of buildings and structures (with Amendment). Date of introduction 2017 —10 —01.
• GOST R ISO 12006 —2 —2017 Construction. Model for organizing construction data. Part 2 . Basics of information classification. Date of introduction 2017 —10 —01.
• GOST R ISO 12006 —3 —2017 Construction. Model for organizing construction data. Part 3. Object exchange basics - oriented information. Date of introduction 2017 —10 —01
• GOST R ISO 22263 —2017 Model for organizing construction data. Project information management structure. Date of introduction 2017 —10 —01.
• GOST R 57295 —2016 Design-management systems. Design Management Guide in Construction. Date of introduction 2018 —01 —01.
• SP 301 .1325800 .2017 Information modeling in construction. Work organization rules production- technical departments. Date of introduction 2018 —03 —02.

Updated 03.23.2018. WITH On March 2018, three of them will come into force on BIM:

• SP 328.1325800.2017 “Information modeling in construction. The rules for describing the components of the information model "(order dated 15.12.2017 No. 1674 / pr). This set of rules applies to the processes of information modeling of buildings and structures and establishes requirements for the components of their information models, but does not establish requirements for the methods of placement, maintenance, structure, form and content of digital libraries (catalogs / bases) of components. The document will come into force on June 16, 2018.
• SP 331.1325800.2017 “Information modeling in construction. Rules for the exchange between information models of objects and models used in software systems "(order dated September 18, 2017 No. 1230 / pr). SP 331.1325800.2017 is based on the basic requirements for the creation and operation of information systems that interact with each other throughout the life cycle of a building or structure and implement information modeling technology for a construction object. The set of rules entered into force on March 19, 2018.
• SP 333.1325800.2017 “Information modeling in construction. Rules for the formation of an information model of objects at various stages of the life cycle "(order dated September 18, 2017 No. 1227 / pr). The document contains requirements for information models of objects of mass construction and their development at various stages of the life cycle, aimed at increasing the validity and quality of design solutions, increasing the level of safety during construction and operation. General approaches to the formation of information models will provide ease of use and increase the efficiency of the information modeling process. The set of rules entered into force on March 19, 2018.

In the near future, we are promised to expand the regulatory and technical documentation on BIM in two directions:

Basic documents:

• 3 GOST R
• 4 SP

Documents for different stages of the object's life cycle

• 2 GOST R
• 6 SP

Do not forget that today there are two categories of regulatory documents.

On August 23, a public discussion began on four joint ventures developed by order of the Ministry of Construction and Housing and Utilities of the Russian Federation. List with direct links below. The term for discussion is 60 calendar days.

Some of the links can still download the texts of the draft documents. Another and guaranteed way to get texts is to send a request to the address: [email protected]

It is recommended to write comments and suggestions in the prescribed form. All comments will be considered and answered and / or corresponding changes will be made to the second edition. You can send comments to the same address, or through the form on the FAU FTSS website.

On September 8, comments were received from members of PK-5 TK-465 and members of the Ministry of Construction, on the site of which the documents were published in the first place.

Documents are developed by different teams, so the procedure for handling comments may be slightly different. In October, the discussion of the documents will end at the PP-5 meeting, to which, most likely, authors of significant comments will also be invited.

Part 2. Informal

1. Our team is involved in the development of two of the four documents. We are very pleased to have the opportunity to participate in the formation of the regulatory and technical field for information modeling in the Russian Federation. We guarantee that the quality of the final version will be of the highest international standard. We are very interested in this and therefore invite all specialists with knowledge and experience in a specific subject area, corresponding to the subject of the joint venture, to speak on the merits and in a dialogue come to the best (at the present historical moment) formulations.

2. In the Russian Federation, work on the Plan (program, roadmap) of a phased transition to BIM has been going on since the end of 2012. Dozens of people took part in the development and discussion. Therefore, in this document at the moment there are more than FIVE obvious points. And the roadmap itself is now under consideration by the Government of the Russian Federation. (I have no information whether it has been accepted or not yet).

3. As a member of the Working Group and Expert Council on the topic, I declare that in national standardization documents no specific software products are and will not be given preference. (Software developers have the right, at their discretion, to develop standards that provide for work in their software). In this regard, I suggest that authors who allegations of violations of antimonopoly legislation and the federal law on the protection of competition illustrate this with texts from the relevant laws and the joint venture.

I would like to draw your attention to the name of the joint venture, because of which this heated discussion began - "Rules of exchange between information models of objects and models used in software systems." The developers of this joint venture, in fact, were caught in a vice. Some reviewers require specificity from them, detailed rules, and not general considerations. (Who will tell you how this can be done if any mention of products is vetoed?) Others, on the contrary, demand that any mentions be deleted. The way out, obviously, lies in the development of additional methodological recommendations, where it will be permissible to mention the products.

In a recent sensational publication, there was a mention of BIM happiness at the expense of a certain vendor, I ask the author to "arm" his eyes and give me specific examples from the text. Due to my roles (see the first sentence of point 3), I really need to ensure the neutrality of regulations regarding BIM platforms.

4. In Great Britain, the share of government orders in construction is about 40%. The RF has SIGNIFICANTLY LOWER. I could not find the exact figure, but NOPRIZ insists that it is no more than 5% (!). From other sources, I heard the figure up to 15%. (And why break a spear - or a rake?) That is, a private customer dominates in construction. And he is free to order as he likes, without breaking the law. And including determining the formats in which he wants to receive the product. What then are we arguing about? If a state customer starts asking for 20% of a small volume in BIM, how much business will an individual designer lose who does not want to hear anything about BIM? Nothing. Will not go to the state tender and will continue to paint for a private trader until he asks BIM.

5. Now about the "veiled restrictions to hide the weaknesses of the promoted product." About the "product" see item 3. As for the restrictions, the above phrase suggests that its author is not familiar with similar documents developed in other countries that have outstripped us in this area. Such documents are full of formulations like "due to limited software support" or "as BIM skills and software tools for this purpose are still immature", etc. Yes, we have to admit that the software products at our disposal are not perfect yet and we have to take this into account ... Therefore, we apply similar reservations in the text and will continue to do so.

6. And in conclusion I would like to appeal to those who were really disappointed in what they saw - the texts of documents and calls them raw, etc. What did you expect to find there and did not find? Maybe we should sort it out and be more specific? If we bring together all the topics covered by similar national documents on BIM in different countries, then we will find that they reflect modeling techniques, approaches to determining the levels of development of information model elements (LOD, LOI), new roles and responsibilities of participants in the process, BIM implementation plans -projects, rules for the development of library elements, issues of interoperability and organization of teamwork. That's practically all the topics. Only then are they still decomposed into different participants and stages of the life cycle. Items from this list are partially covered by the submitted joint ventures, and the rest are included by the Ministry in the plan for further development.

I invite all those who are disappointed to a constructive dialogue. If you do not want to write an official appeal, and at the same time we are already familiar with you, write in a personal. Let's figure it out.

Three new sets of rules (JV) in the field of information technology have been approved and will come into effect on March 1. This was announced by Alexander Stepanov, Deputy Head of the Department of Urban Development and Architecture of the Ministry of Construction and Housing and Communal Services of the Russian Federation, within the framework of the seminar “Information Modeling. Digital environment as a basis for interaction ”, organized by the Federal Center for Rationing, Standardization and Technical Conformity Assessment in Construction, subordinate to the Ministry of Construction of Russia, together with the RSPP Committee on Technical Regulation, Standardization and Conformity Assessment. The event was held on February 21 with the participation of a representative team of experts.

JV “Information Modeling in Construction. Rules for describing the components of the information model ”,“ Information modeling in construction. The rules for the formation of an information model of objects at various stages of the life cycle "and" Information modeling in construction. The rules for exchange between information models of objects and models used in software systems "will come into effect on March 1, 2018.

According to Alexander Stepanov, the system of national documents being created in the field of information modeling technologies in construction includes basic standards and codes of practice that provide digital infrastructure, including those that define the basic provisions, principles and terminology of BIM, as well as standards and codes of practice that define the conceptual framework and a methodology for introducing information modeling into practice at certain stages of the life cycle - from justifying investments to utilization and demolition of buildings and structures.

In 2018, the development of basic standards that define the basic principles, concepts and terminology of BIM began: GOST R “Organization of information about construction work. Information management using information modeling. Part 1. Basic principles and concepts "and GOST R" Organization of information about construction work. Information management using information modeling. Part 2. The stage of asset creation ”. Similar ISO standards (ISO 19650-1 and ISO 19650-2) are currently in their final stages of development. Experts of PC 13 "Processing, storage and exchange of information related to construction work" TC 465 "Construction" have been taking part in these works since 2017.

Now undergoing the registration procedure GOST R “Information modeling in construction. Industry base classes (IFCs) for information exchange throughout the life cycle. Basic Provisions ". “If the state customer is provided with the opportunity to require the provision of information for control in the IFC format, then there will be no need to spend budget funds on the purchase of a large number of various software products and on the maintenance of an excessive staff of specialists capable of working in these programs,” said Alexander Stepanov.

The system of normative and technical documents in total will include 15 national standards (GOST R), 10 sets of rules, including: 13 GOST R and 4 SP - documents developed in fundamental (basic) directions; 2 GOST R and 6 sets of rules - for individual stages of the life cycle.

Currently, in the field of BIM, 7 GOSTs and 4 sets of rules are available for practical use.

The event was attended by specialists from TC 465 "Construction", KazNIISA (Kazakhstan), the Center for Digital Economy of Moscow State University, JSC Research Center "Construction", NIIPromzdaniy, FAU FTSS, etc.

Before sending an electronic appeal to the Ministry of Construction of Russia, please read the following rules for the operation of this interactive service.

1. Electronic applications within the competence of the Ministry of Construction of Russia, completed in accordance with the attached form, are accepted for consideration.

2. An electronic appeal may contain a statement, complaint, proposal or request.

3. Electronic appeals sent through the official Internet portal of the Ministry of Construction of Russia are submitted to the department for work with citizens' appeals for consideration. The Ministry ensures an objective, comprehensive and timely consideration of applications. Consideration of electronic applications is free of charge.

4. In accordance with the Federal Law of 02.05.2006, N 59-FZ "On the Procedure for Considering Appeals of Citizens of the Russian Federation," electronic appeals are registered within three days and sent, depending on the content, to the structural divisions of the Ministry. The appeal is considered within 30 days from the date of registration. An electronic appeal containing questions the solution of which is not within the competence of the Ministry of Construction of Russia is sent within seven days from the date of registration to the appropriate authority or to the relevant official, whose competence is to resolve the issues raised in the appeal, with notification of this to the citizen who sent the appeal.

5. Electronic appeal is not considered when:
- absence of the name and surname of the applicant;
- indication of an incomplete or inaccurate postal address;
- presence of obscene or offensive language in the text;
- the presence in the text of a threat to the life, health and property of the official, as well as his family members;
- using a non-Cyrillic keyboard layout or only capital letters when typing;
- the absence of punctuation marks in the text, the presence of incomprehensible abbreviations;
- the presence in the text of a question to which the applicant has already been given a written answer on the merits in connection with the previously sent appeals.

6. The response to the applicant is sent to the mailing address indicated when filling out the form.

7. When considering an appeal, it is not allowed to disclose information contained in the appeal, as well as information concerning the private life of a citizen, without his consent. Information about the personal data of the applicants is stored and processed in compliance with the requirements of the Russian legislation on personal data.

8. Applications received through the site are summarized and submitted to the leadership of the Ministry for information. Answers to the most frequently asked questions are periodically published in the sections "for residents" and "for specialists"