Set of rules for information modeling in construction. Build it: a guide to construction and design

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

1. Electronic applications within the sphere of competence of the Ministry of Construction of Russia, filled out 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 for consideration to the department for working with citizens' appeals. The Ministry ensures objective, comprehensive and timely consideration of applications. Review of electronic appeals is free of charge.

4.According to Federal law dated 02.05.2006 N 59-FZ "On the procedure for considering citizens' appeals Russian Federation"electronic appeals are registered within three days and are 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 issues that are not within the competence of the Ministry of Construction of Russia is sent within seven days from day of registration to the relevant body or the relevant official, whose competence includes resolving the issues raised in the appeal, with notification of this to the citizen who sent the appeal.

5. Electronic appeal is not considered if:
- absence of the applicant’s surname and name;
- indication of an incomplete or unreliable postal address;
- the presence of obscene or offensive expressions in the text;
- presence in the text of a threat to life, health and property official, as well as members of his family;
- using a non-Cyrillic keyboard layout or only capital letters when typing;
- absence of punctuation marks in the text, 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 previously sent appeals.

6. The response to the applicant is sent to the postal address specified when filling out the form.

7. When considering an appeal, disclosure of information contained in the appeal, as well as information relating to privacy citizen, without his consent. Information about applicants’ personal data is stored and processed in compliance with the requirements of Russian legislation on personal data.

8. Appeals received through the site are summarized and presented 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”

Privacy Policy of the company "Konkurator"

This document “Privacy Policy” (hereinafter referred to as the “Policy”) was developed in accordance with the Federal Law of the Russian Federation dated July 27, 2006 No. 152-FZ “On Personal Data” and determines the procedure for processing, use and protection of personal data by Konkurator LLC "(hereinafter referred to as the "Company"), located at the address: 117036, Russia, Moscow, st. Profsoyuznaya, building 3, office 817.

For the purposes of this Policy, “personal data” means any information relating to directly or indirectly identified or determined to an individual. “Personal data processing” means any action (operation) or set of actions (operations) performed with or without the use of automation tools with personal data, including collection, recording, systematization, accumulation, storage, clarification (updating, changing) , extraction, use, transfer (distribution, provision, access), depersonalization, blocking, deletion, destruction of personal data.

By using our website and providing us with your personal data, filling out forms on our website, you consent to the processing of your personal data in accordance with this Policy.

The company collects, processes, uses and protects the following personal data that you provide to us when filling out form fields on our website (hereinafter referred to as the “Site”), when communicating with us in any form, when subscribing to the newsletter, when registering for events: Full name , contact phone number, address Email(e-mail), position, company and other information contained in the messages you send to us.

The Company processes your personal data solely for the purpose of providing you with information about the Company, our services and events; communication with you when you contact us; organizing your participation in our events and surveys; sending you our newsletters; for other purposes with your consent.

Technical data that is transmitted automatically by the device with which you use the Site, including specifications device, IP address, information from cookies, browser information, date and time of access to the site, addresses of requested pages and other similar information, unlike personal data, such information is anonymized in nature, and therefore is not included in personal data.

The Company may process technical data to: ensure the operation and security of the Site and improve the quality of the Site.

The company does not place your personal data in publicly available sources.

To protect your rights, the Company will provide, at your request, information regarding the processing of your personal data, in accordance with Part 7 of Article 14 of the Federal Law “On Personal Data”. You can contact us with a request regarding the processing of your personal data by sending us a letter with the subject line “Request for personal data” (or “Withdrawal of consent to the processing of personal data” in case of withdrawal of consent to the processing of personal data) to the email address: 4info@site

The company ensures that the necessary legal, organizational and technical measures are taken to protect personal data from unauthorized or accidental access, destruction, modification, blocking, copying, provision, distribution of personal data, as well as from other unlawful actions in relation to personal data, and also takes undertakes to maintain the confidentiality of your personal data.

The processing of personal data is carried out without a time limit, in any legal way. The company stops processing your personal data at your request if the personal data being processed is illegally obtained or is not necessary for the stated purpose of processing and if you withdraw your consent to processing.

The company has the right to make changes to this Policy. The new Privacy Policy comes into force from the moment it is posted on the Site.

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

Set of rules SP-328.1325800.2017

"INFORMATION MODELING IN CONSTRUCTION. RULES FOR DESCRIPTION OF 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 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 generate information models of a construction site.

The set of rules was prepared by the team of authors of JSC "Research Center "Construction" - Central Research Institute of Construction named after V.A. Kucherenko (work supervisor - Doctor of Technical Sciences I.I. Vedyakov; Candidate of Technical Sciences Yu.N. Zhuk, A.V. . Ananyev) 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 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 (catalogues/databases) of components.

2 Normative references

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

GOST 2.303-68 Unified system of design documentation. Lines

GOST 2.306-68 Unified system of 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 the reference documents in the information system common use- 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 according to the releases of the monthly information index "National Standards" for the current year. If a referenced document to which an undated reference is given is replaced, it is recommended that the current version of that document be used, taking into account any changes made to that version. If a reference document to which a dated reference is given is replaced, it is recommended to use the version of this document with the year of approval (acceptance) indicated above. If, after the approval of this set of rules, a change is made to the referenced document to which a dated reference is made that affects the provision to which the reference is given, then it is recommended that this provision be applied without taking into account this change. If the reference document is canceled without replacement, then the provision in which a reference to it is given is recommended to be applied in the part that does not affect this reference. It is advisable to check information about the operation of sets of rules in the Federal Information Fund of Standards.

3 Terms and definitions

The following terms with their respective definitions are used in this document:

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

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

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

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

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

Note - A component applied to a model becomes an element of the model.

3.6 component metadata: Structured data that represents the characteristics of the component being described for identifying, searching, evaluating, and managing it.

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

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

3.8 assembly: A named collection of components intended for repeated use.

3.9 level of development; LOD: A set of requirements that determines the completeness of development of an element of a digital information model. The level of elaboration specifies the minimum amount of geometric, spatial, quantitative, as well as any attribute data necessary to solve information modeling problems at a specific stage of the object’s life cycle.

3.10 functional behavior of a component: Change of a component in accordance with the rules of interaction with environmental conditions embedded 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 project or construction site.

4 General provisions

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

4.2 Components should be separated:

By type:

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

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

Linear - obtained by connecting a directional closed profile and a reference line as a generatrix.

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

Area - volumetric components, significantly smaller in height, created by drawing the 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 whose specific manufacturer is unknown;

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

By parameterization level:

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

Non-parametric 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 applications.

5 General requirements to components

5.1 The development of components must be carried out using appropriate software tools that implement information modeling functionality.

5.2 When developing components you should:

Consider the purposes of using the digital information model;

Take into account the requirements for the levels of development 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 graphic display of components

6.1 Requirements for geometric parameters and graphic display of a component include requirements for:

Geometric parameters;

Display of graphic symbols;

Level of geometric elaboration;

Reserving the space occupied by the component;

Graphic display of materials.

6.2 Requirements for geometric parameters

6.2.1 When developing a component you should:

Model geometry on a 1:1 scale;

Define the insertion point (base point) for a component of type "point";

Use a minimum number of auxiliary elements (for example, auxiliary planes and lines);

Use geometric parameters expressed in the metric system of units.

6.2.2 Components of the "generalized" type must include parameter values ​​that define nominal dimensions if the actual dimensions are unknown.

6.2.3 Product type components shall include parameter values ​​that define the exact dimensions.

6.2.4 Requirements for displaying graphic symbols:

The component must include graphic elements to convey information that cannot be displayed in a three-dimensional projection (for example, direction indicators, door opening direction, window opening methods).

6.3 Requirements for the level of geometric elaboration

6.3.1 The insertion points (base points) of the component must be the same at all levels of development.

6.4 Requirements for graphic display of materials

6.4.1 If an image needs to fill the surface of a component, it must be square or rectangular in shape to ensure seamless repetition of the image (in the form of a mosaic).

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

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

The size of rectangular images is at least 512 pixels along the longest side;

Image resolution is at least 150 dpi.

7 Requirements for the level of attribute elaboration and attribute values

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

Goals and objectives of using digital information models;

LOD requirements;

Requirements for composition and content 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 Mandatory attributes of a component should include those properties or technical characteristics that allow one to uniquely identify the component, 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 necessary for carrying out engineering calculations, information of a technical and economic nature, technical and operational and other characteristics.

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

7.5 If the attribute value is unrestricted and allows both numbers and letters to be entered, then the attribute value must be assigned an alphanumeric data type.

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

8 Functional requirements for components

8.1 A component must “behave” in a way that reflects its functionality and relationships with other components.

8.2 In a software environment, it is generally possible to develop a component with a number of predefined fixed parameters that are available in a real physical building element. If you have preconfigured variants of a component, there should be minimal performance degradation or difficulty in using it.

8.3 A component should be modeled in such a way that it can be connected to and function together with other components, if the joint functioning is supported and consistent with the objectives of the model being developed.

9 Rules for naming components and their attributes

9.1 The component naming rules given in this section are intended for software running on a file storage system.

9.2 The naming system should consist of:

General naming rules;

Naming schemes.

Note - An example of a naming system for component files is given in A.15-A.16 (Appendix A).

9.3 The 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 assume logical data types (Yes/No) must be named so that the value must be assigned (for example, “Presence of Window Sill” - Yes/No).

Note - An example of attribute naming rules is given in A.17 (Appendix A).

9.5 Rules for naming materials

9.5.1 The material name must begin with a capital letter followed by lowercase letters. 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 the material, with an extension corresponding to the format of the graphic file used.

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

10 Requirements for component formats

10.1 According to file formats, components can be represented:

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

In source formats (component file formats and project files of the software used).

11 Component metadata requirements

11.1 When organizing databases/catalogues/libraries of components, for example, in the form of online storage, it is necessary to ensure convenient search for the required content. Typically, such a search is carried out using metadata. Metadata Search - Search by component attributes supported by a specific search engine.

Appendix A

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

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

Unique name;

A globally unique identifier that is used to identify resources;

Classifier code (if available).

A.3 To minimize the number of developed components and their unification, 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 preparation of 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 level of development are conceptual form-building elements and as such do not require preliminary preparation of the corresponding components, and at the LOD 500 level are fully defined components that differ from the LOD 400 level only in dimensions that correspond to the actual execution of design solutions. For these reasons, LOD levels of 200, 300, and 400 are recommended for the development of component databases/libraries/catalogs.

Note - In the absence of corresponding components of a low level of development, it is allowed to use components of a higher level.

A.8 Engineering/process equipment components are recommended to be designed with provision for service space, 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 texture files at 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 variations of a construction item, it is recommended that they be represented using an attribute with a value expressed in one of the following ways:

Single value - if there is only one choice for the value;

List value - if the ordered list has 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 for this value (limit). The lower limit is indicated first, and then the upper limit (for example, 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 ​​greater than or equal to the lower limit value of 175 kW);

Numbered value - if the value provides a choice of fixed values ​​from a specified list. Individual elements must be separated by a comma and a space (for example, a, b, c, d).

Note - These methods of expressing various options for elements of a construction object are usually used in components of the “generalized” type.

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

The file name consists of fields;

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

All fields in the file name begin with a capital letter followed by lowercase letters. 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 values ​​given in Table A.1.

Table A.1

If the component does not contain 3D geometry, at the end of "Field2" ( functional type), "-2D" should be added.

Notes

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

2 Example of naming components of the “generalized” type:

ABC_Door_Double-leaf_Aluminium_GOST23747-2015

3 Example of naming components of the “product” type:

ABC_Washbasin_Ceramic_Plant1_ExecutionA

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 following values given in Table A.2

Table A.2

Note - Examples of attribute naming:

ProfileWidth

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_Bitumen_Continent_Manufacturer

Using some of the links you can still download the texts of the draft documents. Another and guaranteed way to receive texts is to send a request to: [email protected].

It is recommended to write comments and suggestions in the prescribed form. All comments will be considered and responses will be provided and/or appropriate changes will be made to the second edition. You can send comments to the same address, or through the form on the FAA FCS website.

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

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

Part 2. Informal

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

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

I would like to draw your attention to the name of the joint venture, because of which this heated discussion began - “Rules for the exchange between information models of objects and models used in software systems.” The developers of this joint venture actually found themselves squeezed in a vice. Some reviewers require specifics, detailed rules, rather than general considerations. (Who will tell you how this can be done if any mention of products is vetoed?) And others, on the contrary, demand that any mention be excluded. The solution, obviously, is to develop additional methodological recommendations, where it will be permissible to mention 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 view and give me specific examples from the text. Due to my roles (see first sentence of point 3) I really need to ensure neutrality regulatory documents regarding BIM platforms.

4. In the UK, the share of government orders in construction is about 40%. IN THE RF – SIGNIFICANTLY LOWER. I was not able to find the exact figure, but NOPRIZ insists that this is no more than 5% (!). From other sources I have heard figures up to 15%. (And why break spears - or rakes?) That is, in our construction the private customer dominates. And he is free to order as he likes without breaking the law. And including determining the formats in which the product wants to be received. What are we arguing about then? If a government customer starts asking for 20% of a small volume in BIM, how much business will an individual designer who doesn’t want to hear anything about BIM lose? Nothing. He will not go to the state tender and will continue to draw for a private owner until he asks to BIM.

5. Now about “veiled restrictions that allow you to hide weak sides promoted product." For “product”, see paragraph 3. As for the limitations, the above phrase suggests that its author is not familiar with similar documents developed in other countries that are ahead of us in this area. Such documents are full of statements 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 yet perfect 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 address those who are really disappointed in what they saw - the texts of the documents and call them crude, etc. What did you expect to find there and did not find? Maybe we should break things down and be more specific? If we summarize all the topics covered by similar national BIM documents into 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 process participants, plans for the implementation of BIM projects, rules for the development of library elements, issues of interoperability and organization of teamwork . That's almost all the topics. Only then are they further divided into different participants and stages of the life cycle. The items from this list are partially covered by the presented joint ventures, and the rest are included by the Ministry in the plan for further developments.

I invite all those who are disappointed to a constructive dialogue. If you don’t want to write an official appeal, and we already know each other, write in a personal message. Let's figure it out.

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

1. Electronic applications within the sphere of competence of the Ministry of Construction of Russia, filled out 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 for consideration to the department for working with citizens' appeals. The Ministry ensures objective, comprehensive and timely consideration of applications. Review of electronic appeals is free of charge.

4. In accordance with Federal Law No. 59-FZ dated May 2, 2006 “On the procedure for considering appeals from 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 issues 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 relevant body or the relevant official whose competence includes resolving the issues raised in the appeal, with notification of this to the citizen who sent the appeal.

5. Electronic appeal is not considered if:
- absence of the applicant’s surname and name;
- indication of an incomplete or unreliable postal address;
- the presence of obscene or offensive expressions in the text;
- the presence in the text of a threat to the life, health and property of an official, as well as members of his family;
- using a non-Cyrillic keyboard layout or only capital letters when typing;
- absence of punctuation marks in the text, 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 previously sent appeals.

6. The response to the applicant is sent to the postal address specified when filling out the form.

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

8. Appeals received through the site are summarized and presented 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”