The article was written in addition to at the request of the community.
In this article, we will deal with the magic of numbers in decimal numbers. And consider the numbering not only adopted in ESKD (Unified system for design documentation), as well as in ESPD (Unified system of program documentation) and KSAS (Set of standards for automated systems), since Harb is mostly made up of IT specialists.
In accordance with the requirements of the ESKD, ESPD and KSAS standards, each product (program, system) must be assigned a designation - a decimal number.
The designation is assigned in accordance with the rules established in the standards. This was invented by people in ancient times to unify and simplify the identification of products and documentation, record keeping and archives.
Let's look at a simple procedure for assigning a decimal number so that it does not seem like an ancient ritual, and the assigned numbers are magic numbers.
For each set of standards, we will consider the procedure separately.
Unified system for design documentation
In ESKD, the system for designating products and their design documents is established by .
Each product has its own unique designation.
A product designation can be assigned in two ways:
- centrally - within the framework of the procedure determined by the ministry, department, within the industry;
- decentralized - in accordance with the rules adopted in the developer organization.
The structure of the product designation and the main design document is shown in Figure 1.
|
|
| Fig.1 - Structure of the product designation |
The four-digit code of the organization-developer of design documentation, consisting of letters of the ABVG type, is assigned according to the Code of Development Organizations.
To obtain a four-digit letter code, the developer organization must contact . Please note that this service is paid. For example: The enterprise NVP "Bolid" has a four-digit code of the developer organization "ADDR", CJSC" Bastion "-"FIASHΒ«.
It is allowed for civilian products instead of a four-digit alphabetic code to use a code from the all-Russian classifier of enterprises and organizations () developer enterprise. The OKPO code (an eight- or ten-digit number) is a mandatory requisite of any organization and changes only when the enterprise changes the direction and specifics of its activity, otherwise it remains constant for the entire period of the company's existence.
The code of the classification characteristic is assigned to the product and the design document according to the classifier of products and design documents of mechanical engineering and instrumentation (ESKD Classifier). In the Russian Federation, the "All-Russian classifier of products and design documents" is in force, , is a systematized set of names of classification groups of objects of classification - products of the main and auxiliary production of all sectors of the national economy, general technical documents and their codes and is an integral part of the Unified System for Classifying and Coding Technical and Economic Information.
The classification characteristic is the main part of the designation of the product and its design document. The classification characteristic code is assigned according to the ESKD Classifier and is a six-digit number that sequentially designates the class (first two characters), subclass, group, subgroup, species (one character each). The ESKD classifier is built according to a hierarchical decimal method based on a logical transition from the general to the particular in the classified set.
The structure of the classification characteristic code designation is as follows:
|
|
| Fig. 2 - The structure of the classification characteristic code |
The classifier is accompanied by detailed recommendations for finding and determining the code of the product's classification characteristic.
For example, you should define a classification characteristic code for a single-channel power supply with a supply voltage of 220V AC, a frequency of 50Hz, a stabilized DC output voltage of 12V and an active power of 60W.
First you need to determine the class number in the grid of classes and subclasses by product name.
In this case, the class 43XXXX "Microcircuits, semiconductor devices, electrovacuum, piezoelectric, quantum electronics, resistors connectors, power converters, secondary power supplies".
You should also select a subclass. 436XXX "Systems and sources of secondary power supply".
According to the grid of groups, subgroups and types, it is necessary to determine the group in the selected subclass, based on the characteristics of the device being developed: 4362XX "Single-channel secondary power supplies with input AC single-phase voltage", subgroup: 43623 times "With output constant voltage and output parameters" and view: 436234 "Power, W St. 10 to 100 incl. voltage, V up to 100 incl.".
Thus, the classification characteristic code for a single-channel power supply with a supply voltage of 220V AC with a frequency of 50Hz with an output stabilized DC voltage of 12V and an active power of 60W will be: 436234.
The serial registration number is assigned according to the classification characteristic from 001 to 999 within the code of the developer organization in case of decentralized assignment of the designation, and in case of centralized assignment - within the code of the organization allocated for centralized assignment.
For example, this number can be the serial number of the entry in the product designation accounting card. The form and procedure for maintaining a designation accounting card are established in GOST 2.201-80.
Thus, for the considered example of choosing a classification characteristic, the product designation may look like this:
The designation of a minor design document must consist of a product designation and a document code established by the ESKD standards, is written to the designation of products without a space, assigned in accordance with table 3 GOST 2.102-2013 "Types and completeness of design documents".
|
|
| Fig.3 - Designation of a minor design document |
For example, the electrical circuit diagram: FIASH.436234.610E3
Designation of versions of the product and documents in the group and basic method of execution of design documents, the serial number of the version is added to the designation of the product through a hyphen. With a group method of executing documents, one execution should be conditionally taken as the main one. Such a version should have only a basic designation without a serial number of the version, for example, ATSDR.436234.255. For other versions, the serial number of the version from 01 to 98 is added to the base designation. For example: ATSDR.436234.255-05
It is allowed to designate performances with the addition of three-digit serial numbers from 001 to 999.
With a large range of products that have common design features, it is allowed to use an additional version number, which is written through a dot and must be in the form of a two-digit number, except for 00. The structure of such a designation is shown in Figure 4.
|
|
| Fig. 4 - Application of the version number and additional version number |
Versions with an additional number are designated in the presence of variable characteristics (coatings, parameters, their maximum deviations, climatic operating conditions, additional configuration of the product with components, etc.), which are possible for all versions.
The additional version number must be a two-digit number, except for 00. The number or each of its digits can indicate one characteristic or a set of interrelated characteristics.
Newly developed components of these products, which depend on the same characteristics, are designated using the same additional design number. If necessary, such parts can be designated without the use of an additional version number.
If there is an additional number, all versions should be designated using a two-digit serial number of the version from 01 to 98.
Ordinal and additional numbers of performances are set independently of each other.
At the stage of development of a draft design, it is recommended that draft and design design documents be designated according to the following structure:
|
|
| Fig.5 - Designation of draft design documents |
Unified system of program documentation
Designations of programs and program documents are assigned in accordance with the instructions .
The designation of programs and documents should consist of groups of characters separated by dots (after the country code and code of the developer organization), spaces (after the document revision number and document type code), hyphens (after the registration number and document number of this type).
A registration system for naming programs and program documents is being established.
As in ESKDIn ESPD it is envisaged that the designation of the product is also the designation of its program document - the specification.
The structure of the designation of the program and its program document - specification is shown in Figure 6.
|
|
| Fig. 6 - The structure of the designation of programs |
The country code is assigned in accordance with the instructions , while the choice of encoding (Latin, Cyrillic or digital code) is carried out by the developer in accordance with the rules adopted by the enterprise. It is permissible to use a four-digit letter code or OKPO code as the code of the developer organization.
GOST 19.103 states that the registration number of the program should be assigned in accordance with the All-Union Classifier of Programs, but it has never been published, so it is allowed to assign such a code from 00001 to 99999 in accordance with the procedure established by the program developer.
In some cases, to form the registration number of the program, the all-Russian classifier of products by type of economic activity is used. .
The serial number of the program edition must be in the format from 01 to 99.
Program designation example:
- when using the code of the developer organization of four letters:
- ROF.ABVG.62.01.29-01
- 643.ABVG.62.01.29-01
- when using the OKPO code:
- ROF.98765432.62.01.29-01
- RU.98765432.62.01.29-01
- RU.98765432.62.01.29-01
- 643.98765432.62.01.29-01
The designation structure of other policy documents is shown in Figure 7:
|
|
| Fig.7 - The structure of the designation of other policy documents |
The serial number of the document revision must be in the format from 01 to 99. The document type code is assigned in accordance with Table 4 . If necessary, the document is assigned a document number of this type in ascending order from 01 to 99, a document part number in ascending order from 1 to 9.
Examples of the designation of the document "Operator's Manual" (the second such document for this program, part 3):
- Π ΠΠ€.ΠΠΠΠ.62.01.29-01 34 02-3
- 643.ΠΠΠΠ.62.01.29-01 34 02-3
- Π ΠΠ€.98765432.62.01.29-01 34 02-3
- RU.98765432.62.01.29-01 34 02-3
- RUS.98765432.62.01.29-01 34 02-3
- 643.98765432.62.01.29-01 34 02-3
The final version of the applied designation system for programs and program documents must be determined by the developer in internal regulatory documents.
Set of standards for automated systems
The formation of the decemal number of the automated system should be sought in .
In accordance with GOST, each developed document must be assigned an independent designation. A document made on different data carriers must have the same designation. The letter "M" is added to the designation of documents made on machine media.
The document designation has the following structure:
|
|
| Fig. 8 - The structure of the designation of documents for automated systems |
The structure of the designation of an automated system or part of it is as follows:
|
|
| Fig. 9 - The structure of the designation of an automated system or its part |
The GOST proposes to select the code of the developer organization in accordance with the All-Union Classifier of Enterprises, Institutions and Organizations (OKPO) according to the rules established by industry RTDs. At the moment, it is not the all-union invalid document that should be used, but the all-Russian classifier - OKPO. It is also permissible to use the four-letter code from FSUE "STANDARTINFORM" as the code of the developer organization.
The system rating code should be selected from , which replaced the all-Union product classifier mentioned in GOST 34.201-89, as well as the all-Russian product classifier (OKP) canceled from January 01, 2017.
It should be borne in mind that the classification characteristic code from OKPD2 can be selected by the name of the automation object, for example: 26.51.43.120 - information electrical measuring systems, measuring and computing complexes and installations for measuring electrical and magnetic quantities (for example, an automated information and measuring system for commercial accounting of electricity (AIIS KUE)), 70.22.17 - business process management services (APCS); 26.20.40.140 - information security tools, as well as information and telecommunication systems protected using information security tools (information Internet portals).
Also, GOST 34.201-89 proposes to use the All-Union Classifier of Subsystems and Complexes of ACS Tasks (OKPZ) to assign this characteristic. This classifier has ceased to operate on the territory of the Russian Federation, and no replacement has been developed for it. Therefore, there is currently no alternative to choosing the classification characteristic of an automated system according to OKPD2.
The serial registration number of the system (part of the system) is assigned by the service of the developer's organization, which is responsible for maintaining a file cabinet and accounting for designations. Registration numbers are assigned from 001 to 999 for each classification characteristic code.
The document code consists of two alphanumeric characters and is separated from the system designation by a dot. The code for the documents defined by this standard is affixed in accordance with column 3 of Table 2. The code of additional documents is formed as follows: the first character is a letter indicating the type of document according to Table 1, the second character is a number or letter indicating the serial number of the document of this type.
The remaining positions are included in the designation of the document, if necessary.
The serial numbers of documents of the same name (2 characters) are assigned, starting from the second, and separated from the previous designation by a dot.
The revision number of the document is assigned, starting from the second in ascending order from 2 to 9, and separated from the previous value by a dot. The next edition number is assigned in cases of preservation (not cancellation) of the previous edition.
The part number of the document is separated from the previous designation by a hyphen. If the document consists of one part, then the hyphen is not put down and the part number of the document is not assigned.
A sign of a document made on machine media is entered if necessary. The letter "M" is separated from the previous designation by a dot.
Thus, the AIIS KUE designation may look like this:
- 98765432.26.51.43.120.012
- ABVG.26.51.43.120.012
An example of the designation of the document "Technological instruction" (the third document of this type, the second edition, part 5, is made in electronic form):
- 98765432.26.51.43.120.012.I2.03.02.05M
- ABVG.26.51.43.120.012.I2.03.02.05M
Structural diagram of a complex of technical means (the only document of this type in the project, the only edition, in one part, was issued on paper):
- 98765432.26.51.43.120.012.C1
- ABVG.26.51.43.120.012.C1
Conclusion
It is allowed to use a unique identification system that is accepted in the developer organization. But it should be borne in mind that without special explanations, this system will not be clear to anyone. The described system for assigning designations to products and documents in accordance with the standards can be deciphered by any specialist (designer, developer, programmer).
The following sources were also used in writing the article:
Source: habr.com