Title (English): Industrial automation systems and integration. Product data representation and exchange. Part 203. Application protocol. Configuration controlled design Application area: This International Standard defines the integrated resources needed to describe the scope of data exchange between application systems and the information requirements for three-dimensional designs (designs) of mechanical parts and subassemblies. Configuration in this context only covers data and processes that manage 3D product design data. The concept of exchange is used to extend the scope of the standard only to data used as part of the 3D product definition. Organizations exchanging data in accordance with this standard may be bound by contractual relationships that are not covered in the standard.
The scope of this standard covers:
a) products consisting of mechanical parts and assembly units;
b) data that defines the product and controls its configuration related to the product design stage;
c) change of the design (design) and data associated with documenting the process of making changes;
d) five types of part shape representations, which include wireframe and surface representation without topology, wireframe geometry with topology, dissimilar surfaces with topology, faceted boundary representation, and boundary representation;
f) alternative representations of data according to various rules (disciplines) at the design stage in the product life cycle;
f) designation of government, industry, company or other specifications for the design (construction), process, surface treatment and materials that are defined by the designer for the constructed product;
g) state, industry, company or other designation of standard parts in order to include them in the design (project) of the product;
h) data needed to monitor the progress of the project;
i) data needed to control design approval, design aspects, or product configuration control;
j) data identifying the supplier of the product or its design and, where applicable, certain information about the supplier;
k) designation of the contract and reference to it, if the part is developed according to the contract;
l) designation of the level of protection (confidentiality) classification of an individual part or a part that is a component of an assembly unit;
m) data used in the design review, or the results of its verification, used to justify changes to the design.
The scope of this standard does not cover:
a) data used in the analysis of the project, or the results of its verification, not used to justify changes to the project;
b) data on changes in the project from the results of the initial analysis before the end of this project;
c) data defining the product and its configuration management, relating to any stages of the product development life cycle other than its design;
d) business data for structural design management;
e) alternative representations of data for different rules (disciplines), except for the design stage (for example, at the production stage);
f) using 3D Boolean geometry to represent design objects;
g) data relating to the visual representation of any form of product or its configuration management

On my site there are several reviews of photo exposure meters - devices for measuring the level of illumination of a subject and calculating exposure.

In reviews, I compare the exposure calculated on a Soviet exposure meter with the parameters recommended by my digital SLR.

Let's think about whether such a comparison is correct? After all, one of the parameters that is involved in the calculation of exposure is film sensitivity.

On digital cameras, the sensitivity is set in ISO units, and on Soviet exposure meters (including those built into cameras) - in GOST units.

If you noticed, when comparing exposure calculations, I equate these units. With a slight correction, for example, to the fact that the Soviet exposure meter has a mark of 130 units on its scale, and a modern device allows you to set only 125.

Is it possible to equate GOST and ISO units?

In the forums, I met several times, for example, opinions of this kind:

“GOST 65 = 100 ISO

GOST 130 = 200 ISO”

Need to figure it out.

To start, a little history.

In the days of the USSR, the ISO system did not yet exist as such, and the sensitivity scales were national.

Since 1928, according to GOST 2817-45, the Herter and Driffield photosensitivity scale (H&D) has been used in the Union. This system appeared in England in 1890.

In our country, this scale was abbreviated as "X and D".
In 1951, the USSR switched to another scale - GOST 2817-50. Since that time, the Soviet units of sensitivity began to be called simply "GOST"

The GOST scale was close to the American ASA (American Standards Association) scale of 1947.

Here I will make an important caveat. If you approach the most mathematically rigorously, then the GOST and ASA scales are different.

GOST was not completely copied from ASA. Naturally, in the USSR and the USA there were different approaches to calculations based on other different standards, tolerances, and traditions.

However, if you do not dive into mathematics, then the scales will be VERY close. So close that they were simply equated on the marking of exposure meters.

You also need to take into account that the ASA standard itself has not stood still. For example, there is a table in the Wiki in the corresponding article, in which the units of sensitivity correspond to the 1960 standard.
In parallel with the ASA, the German DIN scale (Deutsche Industrie Normen) was used in the USSR. This system was introduced in Germany in 1934.

The DIN scale stands apart from others. If for all other units of measurement - the real sensitivity of the film doubles when the nominal unit of measurement is doubled, then according to the DIN scale, the sensitivity doubles when the unit of measurement is increased by about 3.

So, 65 (ASA, GOST) = 19 (DIN), and 125 (ASA, GOST) = 22 (DIN)

The notation of DIN units as shown in the example above was introduced in 1960. Before that, it was supposed to show a fraction with a denominator of 10 and a degree sign.

For example, so - "22/10 °". See the first photo for an example.

In 1957, the formula for calculating DIN changed. For example, 18 DIN became 21 DIN. In 1960, this scale was harmonized with the American ASA standard.

The ISO standard (from the International Standards Organization of the same name) was adopted in 1974. They didn't get smart. The standard simply combines ASA and DIN.

The full ISO sensitivity record looks like this: "250/25 °". 250 is ASA, 25 is DIN.

In the USSR in 1987 a new GOST (10691-84) was adopted for photosensitivity. This GOST has been brought into line with the international ISO standard.

The digital sensitivity standard describes ISO 12232:2006

Here is such a story.

What do we have in the dry residue?

First.

Sensitivity measurement standards, both foreign and Soviet, have changed over time. 125 units of the 50s, strictly speaking, are not the same as 125 units of the 80s.

In fact, there were two GOSTs.

1. GOST 2817-50 from 1951 to 1986

2. GOST 10691-84 from 1987 to this day, as it were ....

“X and D” I do not take into account, since this scale had a proper name, although it, of course, also had GOST.

The changes, meanwhile, were not too radical. Formulas changed, standards were brought into line with each other.

Devaluations and denominations with the aim of precisely shifting the scales have not been carried out.

Second.

Soviet GOST has always been similar to ASA. The ISO standard is also based on the ASA. The new Soviet GOST was specially aligned with ISO.

Conclusion:

GOST is sufficiently consistent with ISO. Moreover, both the new GOST and the old one, which is from 1951.

Yes, there will be no complete arithmetic identity. But we are not analyzing the formulas, but studying the practical side of the issue.

Where does the information about the discrepancy, which is described at the very beginning, come from?

I think that the legs here grow from this table:

Exposure Meter Scale Marking	Film sensitivity
GOST 2817-50	GOST 10691-84
16	16–20–25
32	32–40–50
65	64–80–100
130	125–160–200
250	250–320–400

What does the table say?

In photographic exposure meters designed for the old GOST, only the main - discrete - sensitivity values ​​\u200b\u200bare often indicated.

The range of film sensitivities was wider and also contained intermediate values.

So, the table shows which types of films according to the new GOST correspond to each value set in the exposure meter according to the old GOST.

Bold values ​​in the right column give the highest match.

So, if you, using an ancient Soviet exposure meter (provided that it has retained its operability and accuracy), determined the exposure for a film with a sensitivity of 130 GOST units, then you can transfer this exposure to your digital camera and indicate the sensitivity of the matrix 125 or 160 or 200 ISO.

For all three options, the result will be good. But the closest, yes, is 200.

In this case, the sensitivity of the film on which 125 GOST / ASA is written will be equal to the sensitivity of the digital matrix, for which 125 ISO units are set.

The table does not compare the sensitivity of photographic materials.

The table only says that for ancient exposure meters, the entire range of film sensitivity corresponded to one division on the calculator. Any of the values ​​in the interval were correct. But the smallest error according to the formulas gave the highest sensitivity value.

Hope I didn't get confused. :about)

Is the statement true

GOST 65 = 100 ISO

GOST 130 = 200 ISO?

Looking for what.

Firstly, as I said, it is not about comparing the sensitivity of photographic materials. The sensitivity according to the old GOST, according to the new and according to ISO are approximately the same. The new GOST is closer, of course.

This ratio should be relied upon only when using old exposure meters to calculate the exposure of modern films / matrices.

Secondly, the new GOST complies with ISO. Therefore, even a Soviet exposure meter released after 1987 (Sverdlovsk-4, for example) should give correct values.

Okay, question on the forehead. :about)

Have I correctly compared the work of OPTEK and tabular exposure meters with the operation of a digital SLR exposure meter in the light of everything written here? These exposure meters are designed for the old GOST.

Answer: Yes, in my opinion, it is correct. I set the ISO sensitivity to GOST and this is acceptable, according to the table, although this is not the most accurate option.

Not the most accurate, but one of the acceptable ones.

In any case, the error that I encounter in this case is less than one stop, which is completely normal for both digital and even more so for film photography.

If you have an opinion on this matter, write!

That's all for me. Good luck!

P.S. If you often buy something in online stores, I can recommend a cashback service LetyShops. It allows you to return up to 5% of the purchase price.
To do this, you need to register. Further on the main page LetyShops choose the online store you are interested in. There are more than two thousand of them, such popular sites as AliExpress, My-Shop and many others are represented. By clicking on the button in the store, make purchases there as usual.

After placing an order, to your account in LetyShops cashback will be credited. It will become available for withdrawal after receiving the goods.
You can withdraw money in various ways. I transfer to the cell phone balance. There are no fees with this option.
There is a limit on the withdrawal of the minimum amount of 500 rubles, but if you use promotional codes that are easy to find on the network, then this restriction is removed.

Very pleasant service LetyShops, recommend. Link for registration.

Dear readers!
Pages – business cards – have been created in social networks for the USSR Phototechnics website.
If you are interested in my resource, I invite you to support the project and become a member of any of the communities. Share your experience, express your thoughts, ask questions, participate in discussions!
I pay special attention to the new page in Instagram.

Document's name:
Document Number:	24.104-85
Document type:	GOST
Host body:	State Standard of the USSR
Status:	Document canceled in part current
Published:	official publication
Acceptance date:	December 20, 1985
Effective start date:	January 01, 1987
Revision date:	July 01, 2009

GOST 24.104-85

Group P87

INTERSTATE STANDARD

Unified system of standards for automated control systems

AUTOMATED CONTROL SYSTEMS

General requirements

Unified system of standards of computer control systems. computer control systems. General requirements

MKS 35.240
OKSTU 0024

Introduction date 1987-01-01

Decree of the USSR State Committee for Standards dated December 20, 1985 N 4632, the date of introduction was set as January 1, 1987

INSTEAD OF GOST 17195-76, GOST 20912-75, GOST 24205-80

EDITION (July 2009) as amended (IUS 8-2003).


This standard applies to automated control systems (ACS) of all types (except for national ones) and establishes general requirements for ACS in general, ACS functions, personnel training and types of ACS support, safety and ergonomics, types and procedures for testing when putting ACS into operation, completeness of ACS, guarantees.

The standard does not establish requirements for automated control systems, determined by the specifics of control objects. These requirements are formulated in the terms of reference for the creation or development of each automated control system or in other regulatory and technical documents of the department of the customer of the automated control system.

Additional requirements for automated control systems for technological processes, automated control systems for enterprises, industrial and research and production associations, industry-specific automated control systems are established in mandatory appendices 2-3, respectively.

Appendix 4 provides explanations for some of the terms used in the standard.

1. REQUIREMENTS FOR ACS

1. REQUIREMENTS FOR ACS

1.1. Requirements for ACS in general

1.1.1. An automated control system of any kind must comply with the requirements of this standard, the requirements of the terms of reference for its creation or development (hereinafter referred to as the TOR for the automated control system), as well as the requirements of regulatory and technical documents in force in the department of the customer of the automated control system.

1.1.2. The commissioning of an automated control system should lead to useful technical, economic, social or other results, for example:

- decrease in the number of managerial personnel;

- improving the quality of the functioning of the control object;

- improving the quality of management, etc.

1.1.3. The specific content of the requirements under paragraphs 1.1.2, 1.1.5-1.1.11, 1.2, 1.3, 1.4.2, 1.4.3, 1.4.6, 1.4.9, 1.5.2, 1.5.4, 1.5.6, 1.5.7, 1.6.2, 1.6.6, 1.6.12, 1.7.2, 1.7.3 are set in the ToR for the ACS.

1.1.4. The automated control system should ensure the achievement of the goals of its creation (development) established in the TOR for the automated control system.

1.1.5. The ACS must ensure compatibility between its parts, as well as with automated systems (AS) interconnected with this ACS.

In cases where an automated control system or a set of automated control systems (AS) is created on the basis of a computer network, to ensure compatibility between the elements of such a network, systems of protocols for multilevel interaction should be applied.

1.1.6. The automated control system as a whole and all types of its support must be adapted to modernization, development and expansion within the requirements specified in the TOR for the automated control system.

1.1.7. The reliability of the automated control system as a whole and each of its automated functions should be sufficient to achieve the established goals of the system functioning under the given conditions of use.

1.1.8. The adaptability of the automated control system should be sufficient to achieve the established goals of its operation in a given range of changes in the conditions of use.

1.1.9. The automated control system should provide for monitoring the correctness of the implementation of automated functions and diagnosing, indicating the place, type and cause of violations of the correct functioning of the automated control system.

1.1.10. In automated control systems with measuring channels, it should be possible to control the metrological characteristics of the measuring channels.

1.1.11. The automated control system must provide for measures to protect against incorrect actions of personnel leading to an emergency state of an object or control system, from accidental changes and destruction of information and programs, as well as from unauthorized interference.

1.1.12. Any information entering the ACS is entered into the system once using one input channel, if this does not lead to non-fulfillment of the requirements established in the TOR for the ACS (in terms of reliability, reliability, etc.).

1.1.13. Output information of the same semantic content should be generated in the ACS once, regardless of the number of recipients.

1.1.14. The information contained in the ACS databases must be updated in accordance with the frequency of its use in the performance of system functions.

1.1.15. The automated control system must be protected from information leakage, if it is stipulated in the TOR for the automated control system.

1.1.16. The name of the ACS should include the names of the ACS type and the control object.

For example:

- PCS for metal heating in a process furnace;

- organizational and technological automated control system for workshop No. 5;

- Automatic control system of the "Sickle and Hammer" plant.

1.2. Requirements for ACS functions

1.2.1. ACS in the required volumes should automatically perform:

- collection, processing and analysis of information (signals, messages, documents, etc.) about the state of the control object;

- development of control actions (programs, plans, etc.);

- transfer of control actions (signals, instructions, documents) for execution and its control;

- implementation and control of the implementation of control actions;

- exchange of information (documents, messages, etc.) with interconnected automated systems.

1.2.2. The composition of automated functions (tasks, task complexes - hereinafter referred to as functions) of the ACS should provide the ability to control the corresponding object in accordance with any of the goals established in the TOR for the ACS.

1.2.3. The composition of the automated functions of the automated control system and the degree of their automation must be technically, economically and (or) socially justified, taking into account the need to free personnel from performing repetitive actions and create conditions for using their creative abilities in the process of work.

1.3. Requirements for the preparedness of ACS personnel

1.3.1. The qualification of the personnel of the automated control system should ensure the effective functioning of the system in all specified modes.

1.3.2. ACS personnel should be prepared to perform their duties in accordance with the instructions of organizational support.

1.3.3. Each person who is part of the ACS personnel must be able to apply the appropriate information models and work with the technical means and documentation used by him, which determine the procedure for his activities.

1.4. Requirements for the technical support of automated control systems

1.4.1. The complex of technical means of the automated control system should be sufficient to perform all automated functions of the automated control system.

1.4.2. In the complex of technical means of automated control systems, technical means of mass production should be mainly used. If necessary, the use of technical means of single production is allowed.

1.4.3. Replicated automated control systems and their parts should be built on the basis of unified technical means.

1.4.4. The technical means of the automated control system must be placed in compliance with the requirements contained in the technical, including operational, documentation for them, and so that it is convenient to use them during the operation of the automated control system and perform maintenance.

1.4.5. The placement of technical means used by the personnel of the automated control system when performing automated functions must comply with the requirements of ergonomics: for production equipment in accordance with GOST 12.2.049-80, for means of presenting visual information in accordance with GOST 21829-76, including for boards for collective use from digital sign-synthesizing electroluminescent indicators according to GOST 29.05.002-82.

1.4.6. The technical means of the automated control system used in the interaction of the automated control system with other systems must be compatible in interfaces with the corresponding technical means of these systems and the communication systems used.

1.4.7. The automated control system must use technical means with a service life of at least ten years. The use of technical means with a shorter service life is allowed only in justified cases and in agreement with the customer of the automated control system.

1.4.8. Any of the technical means of the automated control system must allow its replacement by a tool of a similar functional purpose without any structural changes or adjustments in the remaining technical means of the automated control system (except for cases specifically provided for in the technical documentation for the automated control system).

1.4.9. ACS technical means may be used only under the conditions specified in the operational documentation for them. In cases where it is necessary to use them in an environment whose parameters exceed the permissible values ​​established for these technical means, measures should be taken to protect individual technical means of the automated control system from the influence of external influencing factors.

1.4.10. The automated control system must use computer technology that meets the general technical requirements in accordance with GOST 21552-84.

1.4.11. The ACS should use technical means corresponding to:

- in terms of stability and external influencing factors - GOST 12997-84 * GOST 14254-96 for shells of electrical products, GOST 17516-72 for electrical products in terms of the impact of mechanical environmental factors, GOST 21552-84
________________
GOST R 52931-2008.


- in terms of power supply - GOST 12997-84 for industrial devices and automation equipment GSP, GOST 21552-84 for computer equipment;

- according to the performance category - GOST 12997-84 for industrial devices and automation equipment GSP, GOST 21552-84 for computer equipment.

1.4.12. The protection of the ACS technical equipment from the impact of external electric and magnetic fields, as well as interference in the power circuits, must be sufficient for the ACS technical equipment to effectively fulfill its purpose during the ACS operation.

1.4.13. In the automated control system, in accordance with the requirements provided for by the "All-Union norms of permissible industrial interference" 1-72 - 9-72 and GOST 23450-79 *, measures must be taken to protect the environment from industrial radio interference emitted by the technical means of the automated control system during operation, as well as at the time of switching on and off.
_________________
* GOST R 51318.11-2006 is valid on the territory of the Russian Federation.

1.4.14. General ergonomic requirements for mnemonic diagrams - in accordance with GOST 21480-76, for counting devices of visual indicators - in accordance with GOST 22902-78, for collective use boards on digital sign-synthesizing electroluminescent indicators - in accordance with GOST 29.05.002-82, for cathode-beam tubes for displaying visual information - according to GOST 29.05.006-85.

1.4.15. General ergonomic requirements for switches and switches on consoles: rotary - according to GOST 22613-77, keyboard and push-button - according to GOST 22614-77, "Toggle" type - according to GOST 22615-77.

1.4.16. General ergonomic requirements for signaling devices for sound primary messages - according to GOST 21786-76.

1.4.17. General ergonomic requirements governing the organization of the workplace, the relative position of information display facilities, controls and communications within the workplace - according to GOST 22269-76, including consoles - according to GOST 23000-78.

1.4.18. General ergonomic requirements for operator seats - according to GOST 21889-76.

1.4.19. General ergonomic requirements for the hall, operator cabins and the relative position of workplaces - according to GOST 21958-76.

1.5. ACS software requirements

1.5.1. The ACS software must be sufficient to perform all the ACS functions implemented using computer technology, and also have the means to organize all the required data processing processes, allowing timely performance of all automated functions in all regulated ACS operation modes.

1.5.2. The ACS software should have the following properties:

- functional sufficiency (completeness);

- reliability (including recoverability, availability of error detection tools);

- adaptability;

- modifiability;

- modularity of construction and ease of use.

1.5.3. ACS software should be mainly built on the basis of existing application software packages and other programs borrowed from state, industry and other funds of algorithms and programs, allow loading and verification in parts and allow replacing some programs without correcting others.

1.5.4. The automated control system should mainly use database management systems (DBMS) registered in the prescribed manner.

1.5.5. The ACS software should be built in such a way that the absence of individual data does not affect the performance of the ACS functions, in the implementation of which these data are not used.

1.5.6. The ACS software must have the means of diagnosing the technical means of the ACS and control the reliability of the input information.

1.5.7. In the software of the automated control system, measures should be implemented to protect against errors during the input and processing of information, ensuring the specified quality of the performance of the functions of the automated control system.

1.5.8. The general software of the automated control system should allow the configuration of the components of special software and the further development of the software of the automated control system without interrupting the process of its operation. The already generated and loaded piece of software must be protected from accidental changes.

1.5.9. All special software programs of a particular automated control system must be compatible both with each other and with its general software.

1.5.10. Operational software documentation for the automated control system must comply with the standards of the ESPD and contain all the information necessary for the personnel of the automated control system to use the software of the automated control system, for its initial download and (or) generation, downloading information from the internal machine information base, launching the automated control system programs, checking their operation using appropriate tests .

1.5.11. Newly developed when creating a specific automated control system, software products included in its software must be registered in the state, industry or other funds of algorithms and programs (as appropriate).

1.6. Requirements for information support of automated control systems

1.6.1. The information support of the automated control system should be sufficient to perform all automated functions of the automated control system.

1.6.2. To encode information used only in this automated control system, classifiers adopted by the customer of the automated control system should be applied.

1.6.3. To encode in the ACS output information used at a higher level, classifiers of higher control systems should be used, except for specially stipulated cases.

1.6.4. General ergonomic requirements for information coding - according to GOST 21829-76.

1.6.5. In the automated control system for communication between devices of a complex of technical means, the following should be applied:

- input and output signals:

Electrical - current and voltage according to GOST 26.011-80, with a discrete change in parameters according to GOST 26.013-81, coded according to GOST 26.014-81,

- hydraulic according to GOST 26.012-94,

- pneumatic according to GOST 26.015-81;

- alphanumeric character sets according to GOST 27465-87;

- 8-bit codes according to GOST 19768-93.

1.6.6. The information support of the automated control system must be compatible with the information support of the systems interacting with it, in terms of content, coding system, addressing methods, data formats and the form of presentation of information received and issued by the automated control system.

1.6.7. The forms of documents created by the ACS must comply with the requirements of the standards of the DRC or regulatory and technical documents of the department of the customer of the ACS.

1.6.8. The forms of documents and video frames input, output or corrected through the ACS terminals must be consistent with the relevant technical characteristics of the terminals.

1.6.9. The set of information arrays of the automated control system should be organized in the form of databases on machine media.

1.6.10. The form of presentation of the output information of the automated control system must be agreed with the customer (user) of the system.

1.6.11. The terms and abbreviations used in the ACS output documents must be generally accepted in the given subject area and agreed with the system customer.

1.6.12. The ACS must provide the necessary measures to control and update data in the information arrays of the ACS, restore the arrays after the failure of any technical means of the ACS, as well as control the identity of the information of the same name in the databases.

1.7. Requirements for the organizational support of automated control systems

1.7.1. The organizational support of the automated control system should be sufficient for the effective performance of the duties assigned to it by the personnel of the automated control system in the implementation of automated and related non-automated functions of the system.

1.7.2. The organizational structure of the automated control system should allow all the functions of the automated control system to be performed, taking into account their distribution by management levels.

1.7.3. The requirements for the distribution of duties among the personnel involved in the operation of the automated control system in real time are determined taking into account the requirements of clause 11 of the mandatory Appendix 1.

1.7.4. Instructions for the organizational support of the ACS should determine the actions of the ACS personnel necessary to perform each automated function, in all modes of operation of the ACS, taking into account the specified requirements for the accuracy and speed of the implementation by the ACS personnel of their functional duties, and also contain specific instructions on actions in case of emergencies. or violation of the normal operating conditions of the automated control system. Requirements for the content of instructions - according to RD 50-698-90 *.

________________

*Document not cited. See the link for more information. - Database manufacturer's note.

1.7.5. For each automated function that is performed in the interaction of this automated control system with other systems, instructions to the personnel of the automated control system and these systems must be interconnected for all modes of performing this function and contain instructions on the actions of personnel in case of failure of the technical means of the automated control system.

1.8. Requirements for the linguistic support of automated control systems

1.8.1. The linguistic support of the ACS should be sufficient for communication of various categories of users in a form convenient for them with automation tools for the ACS and for the implementation of transformation procedures and machine representation of the information processed in the ACS.

1.8.2. The linguistic support of ACS should include:

language means are provided for describing any information used in the ACS;

- used language means are unified;

- standardized descriptions of the same type of information elements and records of syntactic constructions;

- provided convenience, unambiguity and stability of communication between users and automated control systems;

- means are provided for correcting errors that occur when users communicate with the technical means of the automated control system.

1.8.3. The linguistic support of the automated control system should be reflected in the documentation (instructions, descriptions) of the organizational support of the automated control system in the form of rules for users to communicate with the technical means of the automated control system in all modes of operation of the system.

1.9. Requirements for the legal support of automated control systems

Legal support of automated control systems should include a set of legal norms:

Determining the legal force of information on data carriers and documents used in the functioning of the automated control system and created by the system;

- regulating legal relations between persons who are members of the ACS personnel (rights, duties and responsibilities), as well as between the ACS personnel and the personnel of systems interacting with the ACS.

Note. Rules and regulations arising from the legal force of information on data carriers and legal norms should be included in the instructions for organizational support and regulations on the relevant ACS services.

1.10. Requirements for operational documentation for automated control systems

1.10.1. The operational documentation for the ACS should be sufficient for the commissioning of the ACS and its effective functioning.

1.10.2. Operational documentation for the ACS should:

- contain the information necessary for the rapid and high-quality development and proper operation of automated control systems;

- contain instructions on the activities of the ACS personnel in emergency situations or in violation of the normal operating conditions of the ACS;

- do not contain provisions that allow ambiguous interpretation.

2. SAFETY REQUIREMENTS

2.1. Incorrect actions of the ACS personnel should not lead to an emergency.

2.2. Safety requirements for electrical products used in automated control systems - according to GOST 12.2.007.0-75.

2.3. Safety requirements for computer equipment used in automated control systems - according to GOST 25861-83.

2.4. All external elements of the ACS technical equipment that are energized must be protected from accidental contact, and the technical equipment themselves must have grounding or protective grounding in accordance with GOST 12.1.030-81 and the "Electrical Installation Rules".

2.5. Technical means of automated control systems located at explosive and fire hazardous installations must meet the requirements of the "Electrical Installation Rules".

2.6. The technical means of the automated control system must be installed so that their safe operation and maintenance are ensured.

2.7. Safety requirements must be established by a special section of job descriptions and (or) ACS operating instructions and have links to technical equipment operating instructions.

2.8. General ergonomic requirements for workplaces of ACS personnel - according to GOST 22269-76.

2.9. Comfortable living conditions for ACS personnel must comply with current sanitary standards, maximum allowable living conditions - in accordance with GOST 12.1.005-88, permissible levels of influence of hazardous and harmful production factors - in accordance with GOST 12.0.003-74.

2.10. General ergonomic requirements for the microclimate of the working premises of the ACS personnel are in accordance with GOST 12.1.005-88.

2.11. Noise and sound power levels at the locations of ACS personnel should not exceed the values ​​established by GOST 12.1.003-83 and sanitary standards, while taking into account the noise and sound power levels generated by all sources, including acoustic means of data transmission.

2.12. Illumination levels of workplaces of ACS personnel should correspond to the nature and working conditions. Protection against glare and glare must be provided.

2.13. General ergonomic requirements for vibration of equipment at workplaces of ACS personnel - according to GOST 12.1.012-2004.

2.14. Signal colors and safety signs - according to GOST 12.4.026-76 *.
__________________
* GOST R 12.4.026-2001 is valid on the territory of the Russian Federation.

3. TYPES AND PROCEDURE FOR CARRYING OUT TESTS WHEN PUTTING ACS INTO OPERATION - according to GOST 34.603-92

3.1-3.7.13 (Deleted, Amendment).

4. COMPLETENESS OF THE ACS TO BE COMMISSIONED

4.1. The ACS should include:

- technical means of automated control systems in the form of a complex of technical means of automated control systems, prepared for operation;

- spare parts and devices (SPTA), devices and devices for checking the performance, adjusting technical means and monitoring the metrological characteristics of the measuring channels of the automated control system in the amount provided for by the custom design documentation agreed with the customer of the automated control system and the user's metrology service in terms of verification equipment;

- operational documentation in accordance with GOST 2.601-2006 for each of the products included in the KTS ACS;

- at least two copies of programs on data carriers and operational documentation for them in accordance with GOST 19.101-77, subject to restrictions and additions in accordance with GOST 34.201-89 and RD 50-698-90;

- a form for the ACS software as a whole or for the software of the ACS function put into operation separately and forms for software products (according to GOST 19781-90), each in one copy. Requirements for the form - according to GOST 19.501-78;

- two copies of the operational documentation for the automated control system in accordance with GOST 34.201-89, including the necessary documentation for the information support of the automated control system (a single copy of the automated control system form).

By agreement between the ACS developer and the ACS customer, the completeness of the ACS can be expanded.

4.2. The states of the automated control system must be staffed with personnel that meet the requirements of clause 1.3.

4.3. To complete the created automated control system, the following can be used, supplied as products for industrial purposes:

- a complex (complexes) of hardware and software with operational documentation for them in accordance with GOST 2.601-2006;

- software products with operational documentation for them in accordance with GOST 19.101-77;

- technical means with operational documentation for them in accordance with GOST 2.601-2006.

4.4. The procedure for developing, putting into production and testing the supplied components used in the automated control system must comply with the State Standards for the system for developing and putting products into production.

Before being put into production, prototypes of components are subjected to acceptance (state, interdepartmental, departmental) tests.

5. WARRANTY

5.1. The developer of the automated control system guarantees the compliance of the automated control system with the requirements of this standard and the TOR for the automated control system, provided that the user observes the conditions and rules of operation.

5.2. The compliance of the technical, software and automation equipment complexes used in the automated control systems and supplied as products for industrial purposes with the requirements of standards and specifications for them is guaranteed by the manufacturers of these types of products, provided that the user observes the conditions and operating rules.

5.3. The warranty period for the ACS is calculated from the day the ACS is put into operation.

5.4. The warranty period for the operation of the automated control system must be set in the ToR for the automated control system and cannot be less than 18 months.

APPENDIX 1 (mandatory). ADDITIONAL REQUIREMENTS FOR AUTOMATED PROCESS CONTROL SYSTEMS (APCS)

APPENDIX 1
Mandatory

1. APCS in industry and the non-industrial sector must manage the technological object as a whole and supply the systems interconnected with it with reliable technological and technical and economic information about the operation of the technological control object (TOU).

2. APCS should develop and implement control actions that are rational in terms of the goals and criteria of management on the TOU in real time of the flow of the technological process in the control object.

3. APCS must perform control, information and support functions.

4. APCS must be compatible with all interconnected automated systems (AS) specified in the TOR for APCS, including systems that are part of flexible automated production together with this APCS, for example, CAD technology, automated warehouse and transport systems, AS for technological preparation of production.

5. Control actions in the automated process control system must be generated automatically or formed by its operational personnel using a set of automation tools included in the system.

6. The automated process control system must ensure the control of the facility in normal, transient and pre-emergency conditions of its operation, as well as the protection or shutdown of the facility in the event of a threat of an accident.

7. The automated process control system should carry out the function of monitoring the execution of control actions on the TOU and signal the output of the executive bodies to the maximum permissible positions.

8. When implementing the function of emergency automatic shutdown of equipment in the automated process control system, an alarm about this to operational personnel should be provided using light and, if necessary, sound signals with automatic registration of the shutdown time.

9. As the main technical means of automated process control systems, products of the State System of Industrial Instruments and Automation Equipment (GSP), other products that meet the requirements of ESSP standards, and computer equipment that comply with GOST 21552-84 should be used.

10. Technical means of automated process control systems placed on technological equipment must comply with the requirements for their operating conditions.

11. Responsibilities between operators should be distributed taking into account:

- participation of personnel in the performance of non-automated functions of the system and its interaction with other systems;

- the permissible level of psycho-physiological and emotional load of operators established by industry regulatory and technical documents associated with the fulfillment of the duties assigned to each of them and his responsibility for the final and intermediate results of work, as well as the required level of his activity in the process of work.

12. Each person who is part of the staff must have:

- knowledge, the volume and depth of which allows him to perform all the actions (interactions) included in the corresponding automated and related non-automated functions of the APCS, as well as make the right decisions in emergency situations or other violations of normal operation;

- proven skills that allow you to perform all actions and interactions with the given accuracy and speed.

13. The APCS software must provide, and the organizational support reflects the language means for communication of operational personnel with the APCS CTS, convenient and accessible to persons who do not have the qualifications of a programmer.

14. Codes and symbols used in the automated process control system should be close to the terms and concepts used by the technological personnel of the control object, and should not cause difficulties in their perception.

15. The measuring channels of the automated process control system must have metrological characteristics that ensure the performance of its information functions with the indicators specified in the TOR for the automated process control system.

16. Requirements for testing automated process control systems

16.1. Preliminary tests of automated process control systems are carried out at the operating TOU.

16.2. Preliminary tests of the APCS functions required for the start-up and run-in of process equipment may be carried out at the facility using simulators.

16.3. The determination of the actual values ​​of indicators of technical and economic efficiency and reliability of the automated process control system is carried out after its commissioning. The operating time of the automated process control system, necessary to determine the actual values ​​of its indicators, is calculated according to the appropriate methods approved in the prescribed manner.

APPENDIX 2 (mandatory). ADDITIONAL REQUIREMENTS FOR ACS BY ENTERPRISES, INDUSTRIAL AND SCIENTIFIC AND PRODUCTION ASSOCIATIONS

APPENDIX 2
Mandatory

1. ACS should improve the efficiency of the production and economic activities of an enterprise, production or research and production association (hereinafter referred to as the enterprise).

2. ACS by an enterprise (APCS) should provide automated collection and processing of information with a wide use of optimization methods for the main tasks and control subsystems of the general plant and workshop level, including, if necessary, in real time in teleprocessing and dialogue mode.

3. The automated control system should be implemented as a set of jointly functioning subsystems, the interaction between which should occur through a common (single or distributed) database.

4. Organizational support of the automated control system should provide for the improvement of management methods and the structure of the enterprise management system during the creation and development of automated control systems.

APPENDIX 3 (mandatory). ADDITIONAL REQUIREMENTS FOR INDUSTRY AUTOMATED CONTROL SYSTEMS (SAC)

APPENDIX 3
Mandatory

1. OSAS should provide:

- improving the characteristics of the control object (increasing labor productivity in the industry, improving product quality, timely delivery of products, reducing the cost of products);

- improvement of information processing processes (reducing the cost of information processing, increasing the reliability of initial data, increasing the accuracy and efficiency of calculations);

- improvement of the organization of the performance of management functions (in particular, the rational distribution of work between departments of the administrative apparatus, computer centers and research organizations and enterprises).

2. The functions of industry management should be automated in the OAS, for example:

- forecasting and planning of production and industry resources;

- management of scientific and technical development of the industry and technical preparation of industry production;

- management of the labor resources of the industry;

- management of material resources of the industry;

- management of capital construction in the industry;

- management of financial resources of the industry;

- management, including operational management, of the main production at the industry level, etc.

3. OAS should be implemented as a set of jointly functioning subsystems, the interaction between which should occur through common databases.

4. OACS should include a data collection system based on the computer centers of OACS, organizations and enterprises of the industry, ensuring rational distribution of information in databases for solving interacting tasks and transferring information between systems via communication channels and on machine media.

5. OACS should provide an interactive mode of working with the system databases.

6. Establishment of the OASMS should lead to the improvement of the methods and structure of the industry management.

7. The duration of the trial operation of parts of the OACS should ensure a one-time performance of all calculations necessary to perform the automated functions of the introduced part of the OASU, and should not exceed 3 months.

The specific duration of the trial operation of the OSCS is set by agreement between the developer and the customer.

APPENDIX 4 (informative). EXPLANATION TO SOME TERMS USED IN THIS STANDARD

APPENDIX 4
Reference

Complex of automation means (KSA)- supplied set of mutually agreed complexes of hardware and software (products), designed and manufactured as products for industrial purposes. The KSA may also include other products and (or) documents included in the information, organizational or other types of support for automated systems.

Building ACS- a set of measures taken in the ACS when expanding its control object without changing the composition of the ACS functions.

Video frame (in ACS)- the image on the screen of the cathode ray tube of the document of the picture or the text of the message used in the automated control system.

ACS measuring channel- a functionally combined set of technical and (if necessary) software tools designed to implement one simple measuring function of the automated control system.

Preliminary tests of automated control systems- control tests carried out in order to determine the possibility of accepting the automated control system for trial operation.

Acceptance tests of automated control systems- control tests of the automated control system, carried out to determine its compliance with the terms of reference for the creation of an automated control system, the requirements of standards and to determine the possibility of putting the automated control system into operation.

State tests- acceptance tests of automated control systems, conducted by the state commission.

Interdepartmental testing of automated control systems- acceptance tests of automated control systems, conducted by a commission of representatives of several interested ministries and (or) departments.

Departmental tests of automated control systems- acceptance tests of automated control systems, conducted by a commission of representatives of the interested ministry or department.



Electronic text of the document
prepared by Kodeks JSC and verified against:
official publication
Information technology.
Automated systems.
Basic provisions:
Sat. GOSTs. -
M.: Standartinform, 2009

GOST 24.104-85 Unified system of standards for automated control systems. Automated control systems. General requirements

Document's name:	GOST 24.104-85 Unified system of standards for automated control systems. Automated control systems. General requirements
Document Number:	24.104-85
Document type:	GOST
Host body:	State Standard of the USSR
Status:	Document canceled in part current
Published:	official publication Information technology. Automated systems. Basic provisions: Sat. GOSTs. - M.: Standartinform, 2009
Acceptance date:	December 20, 1985
Effective start date:	January 01, 1987
Revision date:	July 01, 2009

First of all, I propose to remember for those who knew and forgot, and to determine for those who forgot and did not know what it is - APCS.

An automated process control system (APCS) is a set of hardware and software designed to automate the control of process equipment at industrial enterprises.

In accordance with GOST 34.601-90 - “Automated Systems. Stages of creation”, the process of creating automated systems (AS, APCS) is a set of time-ordered, interconnected, combined into stages and stages of work, the implementation of which is necessary and sufficient to create an AU that meets the specified requirements.

The stages and stages of the creation of AS are distinguished as parts of the creation process for reasons of rational planning and organization of work, ending with a given result.

This standard applies to automated systems (AS, APCS) used in various activities (research, design, management, etc.), including their combinations created in organizations, associations and enterprises (hereinafter - organizations).

This GOST divides the creation of an AU into stages and stages of work, which we will consider below.

1. The first stage is: the formation of requirements for the AU.

Stages of work with their content:

1.1 Inspection of the facility and justification of the need to create an automated process control system:

• collection of data on the automation object and ongoing activities;
• assessment of the quality of the functioning of the object and the types of activities carried out, identification of problems that can be solved by means of automation;
• assessment (technical, economic, social, etc.) of the feasibility of creating an automated process control system.

1.2 Formation of user requirements for process control systems:

• preparation of initial data for the formation of the requirements of the process control system (characteristics of the automation object, description of the requirements for the system, limits on the allowable costs for development, commissioning and operation, the effect expected from the system, conditions for the creation and operation of the system);
• formulation and execution of user requirements for process control systems.

1.3 Registration of a report on the work performed and an application for the development of an AU (tactical and technical specifications):

• preparation of a report on the work performed at this stage;
• registration of an application for the development of a process control system (tactical and technical assignment) or another document replacing it with a similar content.

2. Stage: Development of the AU concept.

2.1 Study of the object.

2.2 Carrying out research work:

• At stages 2.1 and 2.2, the developer organization conducts a detailed study of the automation object and the necessary research work (R&D) related to finding ways and assessing the possibility of implementing user requirements, draw up and approve R&D reports.

2.3 Development of options for the APCS concept and selection of a variant of the APCS concept that meets the requirements of the user:

• development of alternative versions of the concept created by the AU and plans for their implementation;
• assessment of the necessary resources for their implementation and maintenance;
• assessment of the advantages and disadvantages of each option;
• comparison of user requirements and characteristics of the proposed system and selection of the best option;
• determination of the procedure for assessing the quality and conditions for the acceptance of the system;
• assessment of the effects received from the system.

2.4 Making a report on the work performed:

• preparation and execution of a report containing a description of the work performed at the stage of description and justification of the proposed version of the system concept.

3. Terms of reference.

3.1 Development and approval of terms of reference for the creation of process control systems:

• carrying out the development, execution, coordination and approval of the terms of reference for the NPP and, if necessary, the terms of reference for the part of the process control system.

4. Draft design.

4.1. Development of preliminary design solutions for the system and its parts:

• APCS functions;
• functions of subsystems, their goals and effects;
• composition of task complexes and individual tasks;
• the concept of the information base, its enlarged structure;
• database management system functions;
• composition of the computer system;
• functions and parameters of the main software tools.

4.2. Development of documentation for process control systems and its parts:

5. Technical project.

5.1. Development of design solutions for the system and its parts:

• At this stage, the development of common solutions is carried out:
• on the system and its parts;
• functional-algorithmic structure of the system;
• by personnel functions and organizational structure;
• by the structure of technical means;
• algorithms for solving problems and languages ​​used;
• on the organization and maintenance of the information base, the system of classification and coding of information;
• by software.

5.2. Development of documentation for the AU and its parts:

• development, execution, coordination and approval of documentation in the amount necessary to describe the full set of design decisions adopted, and sufficient to carry out work on the creation of process control systems.

5.3. Development and execution of documentation for the supply of products for the acquisition of process control systems and (or) technical requirements (technical specifications) for their development:

• preparation and execution of documentation for the supply of products for the acquisition of automated process control systems;
• determination of technical requirements and preparation of technical specifications for the development of products that are not mass-produced.

5.4. Development of design tasks in adjacent parts of the automation object project:

• At this stage, development, execution, coordination and approval of design assignments in adjacent parts of the automation object project for construction, electrical, sanitary and other preparatory work related to the creation of the NPP are carried out.

6. Working documentation.

6.1. Development of working documentation for the system and its parts:

• development of working documentation containing all the necessary and sufficient information to ensure the implementation of work on the commissioning of the process control system and its operation, as well as to maintain the level of operational characteristics (quality) of the system in accordance with the adopted design decisions, its execution, coordination and approval.

6.2. Development or adaptation of programs:

• development of programs and software tools of the system;
• selection, adaptation and (or) binding of acquired software, development of program documentation.

7. Commissioning.

7.1. Preparation of the automation object for the commissioning of the process control system:

• work on the organizational preparation of the automation object for the commissioning of the process control system, including:
• implementation of design decisions on the organizational structure of process control systems;
• providing units of the control object with instructive and methodological materials;
• introduction of information classifiers.

7.2. Personnel training:

• personnel training and verification of their ability to ensure the functioning of the process control system.

7.3. The complete set of the AU supplied with products (software and hardware, software and hardware complexes, information products):

• obtaining component parts of serial and single production, materials and assembly products;
• conducting incoming quality control.

7.4. Construction and installation works:

• performance of works on the construction of specialized buildings (premises) for the placement of technical means and personnel of the process control system;
• construction of cable channels;
• performance of works on installation of technical means and communication lines;
• testing of installed technical means;
• delivery of technical means for commissioning.

7.5. Commissioning works:

• autonomous adjustment of hardware and software;
• loading information into the database and checking the system of its maintenance;
• complex adjustment of all means of the system.

7.6. Carrying out preliminary tests:

• tests of the AU for performance and compliance with the terms of reference in accordance with the program and methodology of preliminary tests;
• troubleshooting and making changes to the documentation for the process control system, including operational documentation in accordance with the test protocol;
• registration of the act of acceptance of the process control system for trial operation.

7.7. Conducting trial operation:

• carrying out trial operation of process control systems;
• analysis of the results of NPP trial operation;
• finalization (if necessary) of the software of the process control system;
• additional adjustment (if necessary) of technical means of process control systems;
• registration of the certificate of completion of trial operation.

7.8. Carrying out acceptance tests:

• tests for compliance with the terms of reference in accordance with the program and methodology of acceptance tests;
• analysis of the test results of the AU and the elimination of shortcomings identified during the tests;
• registration of the act of acceptance of the NPP into permanent operation.

8. Accompanying speakers.

8.1. Performance of work in accordance with warranty obligations:

• implementation of work to eliminate the shortcomings identified during the operation of the NPP within the established warranty periods, making the necessary changes to the documentation for the NPP.

8.2. Post-warranty service:

• analysis of system functioning;
• identification of deviations of the actual operational characteristics of the NPP from the design values;
• establishing the causes of these deviations;
• elimination of identified deficiencies and ensuring the stability of the operational characteristics of the NPP;
• making the necessary changes to the documentation for the AU.

Date of introduction 01.01.92

This standard applies to automated systems (AS) used in various activities (research, design, management, etc.), including their combinations created in organizations, associations and enterprises (hereinafter - organizations).

The standard establishes the stages and stages of creating an AS. Appendix 1 shows the content of the work at each stage.

1. General Provisions

2. Stages and stages of creating AS

Annex 1 (informative)

Annex 2 (informative)

1. GENERAL PROVISIONS

1.1. is a set of ordered in time, interconnected, united in stages and stages of work, the implementation of which is necessary and sufficient to create an AU that meets the specified requirements.

1.2. The stages and stages of the creation of AS are distinguished as parts of the creation process for reasons of rational planning and organization of work, ending with a given result.

1.3. Work on the development of the AU is carried out according to the stages and stages used to create the AU.

1.4. The composition and rules for performing work at the stages and stages established by this standard are determined in the relevant documentation of organizations involved in the creation of specific types of nuclear power plants.

The list of organizations involved in the creation of the AU is given in Appendix 2.

2. STAGES AND STAGES OF CREATING AS

2.1. The stages and stages of creating an AS in the general case are given in the table.

stages	Stages of work
1. Formation of requirements for the AU	1.1. Inspection of the object and justification for the need to create an AU
	1.2. Formation of user requirements for the AU
	1.3. Registration of a report on the work performed and an application for the development of an AU (tactical and technical specifications)
2. Development of the AU concept	2.1. Studying the object
	2.2. Carrying out the necessary research work
	2.3. Development of options for the concept of the AU and the choice of a variant of the concept of the AU that meets the requirements of the user
	2.4. Preparation of a report on the work performed
3. Terms of reference	3.1. Development and approval of terms of reference for the creation of the AU
4. Draft design	4.1. Development of preliminary design solutions for the system and its parts
	4.2. Development of documentation for the AU and its parts
5. Technical project	5.1. Development of design solutions for the system and its parts
	5.2. Development of documentation for the AU and its parts
	5.3. Development and execution of documentation for the supply of products for the acquisition of nuclear power plants and (or) technical requirements (technical specifications) for their development
	5.4. Development of design tasks in adjacent parts of the project of the automation object
6. Working documentation	6.1. Development of working documentation for the system and its parts
	6.2. Development or adaptation of programs
7. Input and action	7.1. Preparing the automation object for putting the AU into operation
	7.2. Staff training
	7.3. Completion of the AU with supplied products (software and hardware, software and hardware systems, information products)
	7.4. Construction and installation works
	7.5. Commissioning works
	7.6. Carrying out preliminary tests
	7.7. Conducting trial operation
	7.8. Conducting acceptance tests
8. Accompanying speakers	8.1. Performing work in accordance with warranty obligations
	8.2. Post-warranty service

2.2. Stages and stages performed by organizations - participants in the work on the creation of nuclear power plants are established in contracts and terms of reference based on this standard.

It is allowed to exclude the stage "Draft design" and separate stages of work at all stages, to combine the stages "Technical design" and "Detailed documentation" into one stage "Technical design". Depending on the specifics of the AS being created and the conditions for their creation, it is allowed to perform individual stages of work until the completion of the previous stages, the parallel execution of work stages in time, the inclusion of new stages of work.

APPENDIX 1. Reference

1. At stage 1.1 "Survey of the object and justification of the need to create an NPP" in the general case, the following is carried out:

• collection of data on the automation object and ongoing activities;
• assessment of the quality of the functioning of the object and the types of activities carried out, identification of problems that can be solved by means of automation;
• assessment (technical, economic, social, etc.) of the feasibility of creating a nuclear power plant.

2. At stage 1.2 "formation of user requirements for the AU" is carried out:

• preparation of initial data for the formation of requirements for the AU (characteristics of the automation object, description of the requirements for the system, limits on the allowable costs of development, commissioning and operation, the effect expected from the system, conditions for the creation and operation of the system);
• formulation and execution of user requirements for the AU.

3. At stage 1.3 "Filing up a report on the work performed and an application for the development of an AU (tactical and technical assignment)", a report on the work performed at this stage is drawn up and an application for the development of an AU (tactical and technical assignment) or another document replacing it with similar content.

4. At stages 2.1 "Studying the object" and 2.2 "Conducting the necessary research work", the developer organization conducts a detailed study of the automation object and the necessary research work (R&D) related to finding ways and assessing the possibility of implementing user requirements, draw up and approve research reports.

5. At stage 2.3 "Development of options for the concept of the AU and the choice of a variant of the concept of the AU that meets the requirements of the user", in the general case, alternative options for the concept of the created AU and plans for their implementation are developed; assessment of the necessary resources for their implementation and operation; an assessment of the advantages and disadvantages of each option; comparison of user requirements and characteristics of the proposed system and selection of the best option; determination of the procedure for assessing the quality and conditions for the acceptance of the system; assessment of the effects received from the system.

6. At stage 2.4 "Formulation of the report on the work performed" prepare and draw up a report containing a description of the work performed at the stage, a description and justification of the proposed version of the system concept.

7. At stage 3.1 "Development and approval of terms of reference for the creation of the NPP", the development, execution, coordination and approval of the terms of reference for the NPP and, if necessary, the terms of reference for parts of the NPP are carried out.

8. At stage 4.1 "Development of preliminary design solutions for the system and its parts" determine: the functions of the AU; functions of subsystems, their goals and effects; composition of task complexes and individual tasks; concepts of the information base, its enlarged structure; database management system functions; composition of the computer system; functions and parameters of the main software tools.

9. At stage 5.1 "Development of design solutions for the system and its parts", they provide the development of general solutions for the system and its parts, the functional and algorithmic structure of the system, the functions of personnel and the organizational structure, the structure of technical means, the algorithms for solving problems and the languages ​​used , on the organization and maintenance of the information base, the system of classification and coding of information, on software.

10. At stages 4.2 and 5.2 "Development of documentation for the NPP and its parts", the development, execution, coordination and approval of documentation is carried out in the amount necessary to describe the full set of design decisions made and sufficient for further work on the creation of the NPP. Types of documents - according to GOST 34.201.

11. At stage 5.3 "Development and execution of documentation for the supply of products for completing the NPP and (or) technical requirements (technical specifications) for their development", preparation and execution of documentation for the supply of products for completing the NPP; determination of technical requirements and preparation of technical specifications for the development of products that are not mass-produced.

12. At stage 5.4 "Development of design assignments in adjacent parts of the automation project", they develop, execute, agree and approve design assignments in adjacent parts of the automation object project for construction, electrical, sanitary and other preparatory work related to the creation AS.

13. At stage 6.1 "Development of working documentation for the system and its parts", they develop working documentation containing all the necessary and sufficient information to ensure the implementation of work on putting the NPP into operation and its operation, as well as to maintain the level of operational characteristics (quality) of the system in accordance with the adopted design decisions, its execution, coordination and approval. Types of documents - according to GOST 34.201.

14. At stage 6.2 "Development or adaptation of programs", the development of programs and software tools of the system, the selection, adaptation and (or) binding of purchased software tools, the development of software documentation in accordance with GOST 19.101 are carried out.

15. At stage 7.1 "Preparation of the automation object for putting the AU into operation", work is carried out on the organizational preparation of the automation object for putting the AU into operation, including: implementation of design decisions on the organizational structure of the AU; providing units of the control object with instructive and methodological materials; introduction of information classifiers.

16. At stage 7.2 "Personnel training", personnel are trained and their ability to ensure the functioning of the NPP is checked.

17. At the stage "Packing the NPP with supplied products" ensure the receipt of components of serial and single production, materials and assembly products. Carry out input quality control.

18. At stage 7.4 "Construction and installation work", the following is carried out: construction of specialized buildings (premises) for the placement of technical facilities and NPP personnel; construction of cable channels; performance of works on installation of technical means and communication lines; testing of installed technical means; delivery of technical means for commissioning.

19. At stage 7.5 "Commissioning" carry out offline adjustment of hardware and software, loading information into the database and checking the system of its maintenance; complex adjustment of all means of the system.

20. At stage 7.6 "Conducting preliminary tests" carry out:

• tests of the AU for performance and compliance with the terms of reference in accordance with the program and methodology of preliminary tests;
• troubleshooting and making changes to the documentation for the NPP, including operational documentation in accordance with the test protocol;
• registration of the act of acceptance of the NPP for trial operation.

21. At stage 7.7 "Conducting trial operation", the NPP trial operation is carried out; analysis of the results of NPP trial operation; finalization (if necessary) of the AS software; additional adjustment (if necessary) of technical means of the AU; registration of the certificate of completion of trial operation.

22. At stage 7.8 "Conducting acceptance tests" carry out:

• tests for compliance with the technical specifications in accordance with the program and methodology of acceptance tests;
• analysis of the test results of the AU and the elimination of shortcomings identified during the tests;
• registration of the act of acceptance of the NPP into permanent operation.

23. At stage 8.1 "Performance of work in accordance with warranty obligations", work is carried out to eliminate the shortcomings identified during the operation of the NPP within the established warranty periods, to make the necessary changes to the documentation for the NPP.

24. At stage 8.2 "Post-warranty service" work is carried out on:

• analysis of the functioning of the system;
• identification of deviations of the actual operational characteristics of the NPP from the design values;
• establishing the causes of these deviations;
• elimination of identified deficiencies and ensuring the stability of the operational characteristics of the NPP;
• making the necessary changes to the documentation for the AU.

APPENDIX 2. Reference

LIST OF ORGANIZATIONS PARTICIPATED IN THE CREATION OF THE AU

1. The customer organization (user) for which the AU will be created and which provides financing, acceptance of work and operation of the AU, as well as the performance of individual works to create the AU.

2. Organization-developer, which carries out work on the creation of the AU, presenting to the customer a set of scientific and technical services at different stages and stages of creation, as well as developing and supplying various software and hardware of the AU.

3. A supplier organization that manufactures and supplies software and hardware on the order of a developer or customer.

4. Organization-general designer of the automation object.

5. Organizations-designers of various parts of the automation object project for construction, electrical, sanitary and other preparatory work related to the creation of the AU.

6. Construction, installation, adjustment and other organizations.

Notes:

1. Depending on the conditions for the creation of the AU, various combinations of the functions of the customer, developer, supplier and other organizations involved in the creation of the AU are possible.

2. The stages and stages of their work on the creation of the AU are determined on the basis of this standard.

INFORMATION DATA

1. DEVELOPED AND INTRODUCED by the USSR State Committee for Product Quality Management and Standards

DEVELOPERS

Yu.Kh. Vermishev, Dr. tech. sciences; Ya.G. Vilenchik; IN AND. Voropaev, Dr. Sc. sciences; L.M. Seidenberg, Ph.D. tech. sciences; Yu.B. Irz, Ph.D. tech. sciences; V.D. Kostyukov, Ph.D. tech. sciences; M.A. Labutin, cond. tech. sciences; N.P. Leskovskaya; I.S. Mityaev; V.F. Popov (topic leader); S.V. Garshin; A.I. deaf believer; SOUTH. Zhukov, Ph.D. sciences; Z.P. Zadubovskaya; V.G. Ivanov; Yu.I. Karavanov, Ph.D. sciences; A.A. Klochkov; V.Yu. Korolev; IN AND. Makhnach, Ph.D. tech. sciences; S.B. Mikhalev, Dr. tech. sciences; V.N. Petrikevich; V.A. Rakhmanov, Ph.D. economy sciences; A.A. Ratkovich; R.S. Sedegov, Doctor of Economics. sciences; N.V. Stepanchikov; M.S. Surovets; A.V. Flegentov; L.O. Khvilevsky, Ph.D. tech. sciences; VK. Chistov, Ph.D. economy Sciences

2. APPROVED AND INTRODUCED BY Decree of the USSR State Committee for Product Quality Management and Standards dated December 29, 1990 No. 3469