GOST: automated control systems. Automated enterprise management systems (asup) and gost

GOST 24.103-84
AUTOMATED CONTROL SYSTEMS.
BASIC PROVISIONS

1. PURPOSE AND CLASSIFICATION FEATURES OF ACS TYPES

1.1. ACS is designed to ensure the effective functioning of the control object by automated execution of control functions.

The degree of automation of management functions is determined by production needs, the possibilities of formalizing the management process and must be economically and / or socially justified.

1.2. The main classification features that determine the type of ACS are:

the sphere of operation of the control object (industry, construction, transport, Agriculture, non-industrial sphere, etc.)
type of controlled process (technological, organizational, economic, etc.);
system level government controlled, enabling control national economy in accordance with the current management schemes for industries (for industry: industry (ministry), all-Union association, all-Union industrial association, research and production association, enterprise (organization), production, workshop, site, technological unit).

2. FUNCTIONS, COMPOSITION AND STRUCTURE OF ACS

2.1. The functions of the ACS are set in the terms of reference for the creation of a specific ACS based on the analysis of management goals, the assigned resources to achieve them, the expected effect of automation and in accordance with the standards applicable to this type of ACS.

2.2. Each function of the ACS is implemented by a set of task complexes, individual tasks and operations.

2.3. ACS functions generally include the following elements (actions):

planning and (or) forecasting;
accounting, control, analysis;
coordination and / or regulation.

The required composition of elements is selected depending on the type of a specific ACS.

2.4. ACS functions can be combined into subsystems according to functional and other characteristics.

GOST 24.104-85
Automated control systems control systems
General requirements

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 management personnel;
improving the quality of functioning of the control object;
improving the quality of management, etc.

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.5.2. ACS software must have the following properties:

functional sufficiency (completeness);
reliability (including recoverability, availability of error detection tools);
adaptability;
modifiability;
modularity and ease of use.

ADDITIONAL REQUIREMENTS FOR ACS FOR ENTERPRISES, PRODUCTION AND RESEARCH AND PRODUCTION ASSOCIATIONS

1. ACS should increase the efficiency of production and economic activities of enterprises, production or research and production association (hereinafter - enterprises).

2. The enterprise's automated control system (AMCS) should provide automated collection and processing of information with extensive use of optimization methods for the main tasks and control subsystems of the plant-wide and workshop level, including, if necessary, in real time in teleprocessing and dialogue mode.

3. ACS should be implemented as a set of jointly functioning subsystems, the interaction between which should take place through a common (single or distributed) database.

4. The 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 the automated control system.

GOST 34.003-90
Automated systems
Terms and Definitions

1. Automated systems. General concepts

1.1 automated system; AC: A system consisting of personnel and a complex of means for automating their activities, which implements information technology for performing established functions.	en automated system; AS
Notes:
1. Depending on the type of activity, there are, for example, the following types AS: automated control systems (ACS), computer-aided design systems (CAD), automated systems scientific research(ASNI) and others. 2. Depending on the type of controlled object (process), ACS is divided, for example, into process control systems (ACS TP), enterprise ACS (ACS), etc.
1.2 integrated automated system; IAS: A set of two or more interconnected AU, in which the functioning of one of them depends on the results of the functioning of the other (others) so that this set can be considered as a single AU	en integrated AS

General technical terms and explanations used in the field of automated systems

System:
A set of elements, united by connections between them and possessing a certain integrity.
Automated process:
A process carried out with the joint participation of humans and automation equipment.
Automatic process:
A process carried out without human intervention.
Information technology :
Techniques, methods and methods of using computer technology when performing the functions of collecting, storing, processing, transmitting and using data.
Purpose of activity:
The desired outcome of the activity process.
Performance criterion:
The ratio characterizing the degree of achievement of the goal of the activity and taking different numerical values depending on the used influences on the object of activity or specific results of the activity.
Activity object:
An object (process), the state of which is determined by the influences of a person (team) arriving at it and, possibly, external environment.
Algorithm:
A finite set of prescriptions for obtaining a solution to a problem through a finite number of operations.
Information model:
The object model, presented in the form of information describing the parameters and variable values of the object, which are essential for this consideration, the connections between them, the inputs and outputs of the object and which allows, by submitting information about changes in the input values to the model, to simulate the possible states of the object.
Control:
A set of targeted actions, including an assessment of the situation and state of the control object, the choice of control actions and their implementation.
Automated production complex:
An automated complex that consistently carries out automated preparation of production, production itself and its management.

__________________

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 referred to as organizations).

The standard establishes the stages and stages of creating a speaker. Appendix 1 contains the content of work at each stage.

1. General Provisions

2. Stages and stages of creating a speaker

Appendix 1 (reference)

Appendix 2 (reference)

1. GENERAL PROVISIONS

1.1. is a set of time-ordered, 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. Stages and stages of creating an AU are distinguished as part of the creation process for reasons of rational planning and organization of work, ending with a given result.

1.3. The 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 the organizations involved in the creation of specific types of nuclear power plants.

The list of organizations participating in the work on the creation of the AU is given in Appendix 2.

2. STAGES AND STAGES OF CREATION OF AU

2.1. Stages and stages of creating an AU in the general case are shown in the table.

Stages	Stages of work
1. Formation of requirements for the AU	1.1. Site survey and justification of the need to create a nuclear power plant
	1.2. Formation of user requirements for the speaker
	1.3. Registration of a report on the work performed and an application for the development of the AU (tactical and technical assignment)
2. Development of the AU concept	2.1. Study of the object
	2.2. Carrying out the necessary research work
	2.3. Development of variants of the speaker concept and selection of a version of the speaker concept that satisfies the user's requirements
	2.4. Registration of a report on the work performed
3. Terms of reference	3.1. Development and approval of technical specifications for the creation of an AU
4. Draft project	4.1. Development of preliminary design solutions for the system and its parts
4. Draft project	4.2. Development of documentation for the NPP 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 NPP and its parts
	5.3. Development and execution of documentation for the supply of products for completing the AU and (or) technical requirements (technical specifications) for their development
	5.4. Development of design assignments in related parts of the automation object project
6. Working documentation	6.1. Development of working documentation on the system and its parts
6. Working documentation	6.2. Development or adaptation of programs
7. Putting into action	7.1. Preparation of the automation object for the NPP commissioning
	7.2. Staff training
	7.3. Complete set of speakers with supplied products (software and hardware, software and hardware complexes, information products)
	7.4. Construction and installation works
	7.5. Commissioning works
	7.6. Preliminary tests
	7.7. Trial operation
	7.8. Acceptance tests
8. Accompaniment of the AU	8.1. Performance of work in accordance with warranty obligations
8. Accompaniment of the AU	8.2. Post-warranty service

2.2. Stages and stages performed by organizations participating in the work on the creation of the AU 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 "Working documentation" into one stage "Technical work project". Depending on the specifics of the NPPs being created and the conditions for their creation, it is allowed to perform individual stages of work before the completion of the previous stages, parallel in time execution of stages of work, the inclusion of new stages of work.

APPENDIX 1 Reference

1. At stage 1.1 "Survey of the facility and justification of the need to create a nuclear power plant", in the general case, carry out:

collection of data about the automation object and the activities carried out;
assessment of the quality of the object and the activities carried out, identification of problems, the solution of which is possible by means of automation;
assessment (technical, economic, social, etc.) of the feasibility of creating an AU.

2. At stage 1.2 "formation of user requirements for the AU" carry 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, limiting the permissible 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 the AU.

3. At stage 1.3 "Execution of 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 is drawn up with similar content.

4. At stages 2.1 "Study of the object" and 2.2 "Carrying out the necessary research work", the organization-developer 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 reports on research.

5. At stage 2.3 "Development of options for the AU concept and the choice of a version of the AU concept that meets the user's requirements", in the general case, develop alternative options for the concept of the created AU and plans for their implementation; assessment of the necessary resources for their implementation and maintenance; 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 of system acceptance; assessment of the effects received from the system.

6. At stage 2.4 "Reporting 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 the 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 the NPP part are carried out.

8. At stage 4.1 "Development of preliminary design solutions for the system and its parts" determine: the functions of the nuclear power plant; functions of subsystems, their goals and effects; the composition of sets of tasks and individual tasks; the concept of the information base, its enlarged structure; database management system functions; the composition of the computing system; functions and parameters of the main software.

9. At stage 5.1 "Development of design solutions for the system and its parts" 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 organizational structure, the structure of technical means, 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 the 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 to the extent necessary to describe the full set of adopted design solutions 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" prepare and execute 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" carry out the development, registration, approval and approval of design assignments in adjacent parts of the automation object for construction, electrical, sanitary and other preparatory work related to the creation AC.

13. At stage 6.1 "Development of working documentation for the system and its parts", the working documentation is developed, containing all the necessary and sufficient information to ensure the performance of work on the NPP commissioning 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 design, coordination and approval. Types of documents - according to GOST 34.201.

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

15. At stage 7.1 "Preparation of the automation object for the NPP commissioning" work is carried out on the organizational preparation of the automation object for the NPP commissioning, including: implementation of design solutions for the NPP organizational structure; providing subdivisions of the object of management with instructional and methodological materials; introduction of information classifiers.

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

17. At the stage "Completing the AU with the supplied products" ensure the receipt of components of serial and unit production, materials and assembly products. They carry out incoming quality control.

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

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

20. At stage 7.6 "Preliminary tests" carry out:

tests of the nuclear power plant for operability and compliance with the terms of reference in accordance with the program and methodology of preliminary tests;
elimination of malfunctions and amendments to the documentation for the NPP, including the operational one in accordance with the test report;
registration of the certificate of acceptance of the nuclear power plant for trial operation.

21. At stage 7.7 "Trial operation", trial operation of the NPP is carried out; analysis of the results of experimental operation of the nuclear power plant; revision (if necessary) of the AC software; additional adjustment (if necessary) of the technical means of the nuclear power plant; registration of an act of completion of trial operation.

22. At stage 7.8 "Acceptance tests" carry out:

tests for compliance with the terms of reference in accordance with the program and methods of acceptance tests;
analysis of the results of the AU tests and elimination of the shortcomings identified during the tests;
registration of the certificate of acceptance of the nuclear power plant for permanent operation.

23. At stage 8.1 "Performance of work in accordance with warranty obligations", work is carried out to eliminate the deficiencies identified during the operation of the NPP during 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 reasons for these deviations;
elimination of the identified deficiencies and ensuring the stability of the NPP operational characteristics;
making the necessary changes to the documentation for the AU.

APPENDIX 2. Reference

LIST OF ORGANIZATIONS PARTICIPATING IN THE CREATION OF THE AU

1. Organization-customer (user), for which the NPP will be created and which provides financing, acceptance of work and operation of the NPP, as well as the performance of individual works on the creation of the NPP.

2. The organization-developer, which carries out work on the creation of the AU, providing the customer with a set of scientific and technical services at different stages and stages of creation, as well as developing and supplying various software and hardware tools for the AU.

3. A supplier organization that manufactures and supplies software and hardware at the request of the developer or customer.

4. Organization-general designer of the automation object.

5. Organizations-designers of various parts of the project of the automation object for carrying out construction, electrical, sanitary and other preparatory work related to the creation of a nuclear power plant.

6. Organizations for construction, assembly, commissioning and others.

Notes:

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

2. 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. sciences; Ya.G. Vilenchik; IN AND. Voropaev, Dr. sciences; L.M. Seidenberg, Cand. tech. sciences; Yu.B. Irz, Cand. tech. sciences; V.D. Kostyukov, Cand. tech. sciences; M.A. Labutin, cond. tech. sciences; N.P. Leskovskaya; I.S. Mityaev; V.F. Popov (topic leader); S.V. Garshina; A.I. Deaf believing; SOUTH. Zhukov, Cand. Tech. sciences; Z.P. Zadubovskaya; V.G. Ivanov; Yu.I. Karavanov, Cand. Tech. sciences; A.A. Shreds; V.Yu. Korolev; IN AND. Makhnach, Cand. tech. sciences; S. B. Mikhalev, Dr. sciences; V.N. Petrikevich; V.A. Rakhmanov, Cand. econom. sciences; A.A. Ratkovich; R.S. Sedegov, Dr. sciences; N.V. Stepanchikova; M.S. Surovets; A.V. Fleents; L.O. Khvilevsky, Cand. tech. sciences; VK. Chistov, Cand. econom. sciences

2. APPROVED AND INTRODUCED BY Decree State Committee USSR on product quality management and standards dated December 29, 1990 No. 3469

Document's name:
Document Number:	24.104-85
Type of document:	GOST
Host body:	Gosstandart of the USSR
Status:	Document canceled in part Acting
Published:	official publication
Date of adoption:	December 20, 1985
Effective date:	01 January 1987
Revision date:	01 July 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

ISS 35.240
OKSTU 0024

Date of introduction 1987-01-01

By the decree of the USSR State Committee for Standards of 12/20/85 N 4632, the date of introduction was established 01/01/87

REPLACE GOST 17195-76, GOST 20912-75, GOST 24205-80

EDITION (July 2009) with Amendment (IUS 8-2003).

This standard applies to automated control systems (ACS) of all types (except national ones) and establishes General requirements to the automated control system as a whole, the functions of the automated control system, the preparedness of personnel and the types of maintenance of the automated control system, safety and ergonomics, the types and procedure for conducting tests during the commissioning of the automated control system, the completeness of the automated control system, guarantees.

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

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

Appendix 4 explains some of the terms used in the standard.

1. REQUIREMENTS FOR ACS

1.1. Requirements for ACS as a whole

1.1.1. ACS of any kind must comply with the requirements of this standard, the requirements of the technical specifications for its creation or development (hereinafter referred to as the TK for ACS), as well as the requirements of regulatory and technical documents in force in the department of the customer of the ACS.

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

- decrease in the number of management personnel;

- improving the quality of functioning of the control object;

- improving the quality of management, etc.

1.1.3. The specific content of the requirements in clauses 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 installed in the technical specification for the ACS.

1.1.4. The ACS should ensure the achievement of the goals of its creation (development), established in the technical specification for the ACS.

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 ACS or a set of ACS (AS) is created on the basis of a computer network, to ensure compatibility between the elements of such a network, systems of protocols of multi-level interaction must be applied.

1.1.6. ACS as a whole and all types of its support must be adapted to modernization, development and build-up within the requirements specified in the technical specification for ACS.

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

1.1.8. The adaptability of the ACS 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 ACS should provide for monitoring the correctness of the execution of automated functions and diagnostics, indicating the place, type and cause of violations of the correct functioning of the ACS.

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

1.1.11. The ACS should provide for measures of protection 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 with the help of one input channel, if this does not lead to non-fulfillment of the requirements established in the technical specification for the ACS (in terms of reliability, reliability, etc.).

1.1.13. The output information of the same semantic content should be generated in the ACS once, regardless of the number of addressees.

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

1.1.15. The ACS must be protected from information leakage, if it is stipulated in the technical specification for the ACS.

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

For example:

- Process control system for heating metal in a continuous furnace;

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

- Automated control system of the Hammer and Sickle 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 set in the technical specification for the ACS.

1.2.3. The composition of automated functions of ACS and the degree of their automation should 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.

1.3. Requirements for the training of ACS personnel

1.3.1. The qualifications of the ACS personnel must 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 for 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 used by him and the documentation that determines the order of his activities.

1.4. Requirements to technical support ACS

1.4.1. The set of technical means of the ACS should be sufficient to perform all the automated functions of the ACS.

1.4.2. The complex of technical means of ACS should mainly use technical means of serial production. If necessary, the use of technical means of a single production is allowed.

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

1.4.4. Technical means ACS should 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 ACS 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 visual information presentation means in accordance with GOST 21829-76, including for collective use boards made of digital sign-synthesizing electroluminescent indicators in accordance with GOST 29.05.002-82.

1.4.6. The technical means of the ACS used in the interaction of the ACS with other systems must be interface compatible with the corresponding technical means of these systems and the communication systems used.

1.4.7. In the ACS, technical means with a service life of at least ten years must be used. The use of technical means with a shorter service life is allowed only in justified cases and by 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 with a means of similar functional purpose without any design changes or adjustments in the remaining technical means of the automated control system (except for cases specifically stipulated in the technical documentation for the automated control system).

1.4.9. The technical means of ACS are allowed to 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 ACS from the influence of external influencing factors.

1.4.10. In the ACS, computer facilities must be used that satisfy the general technical requirements according to GOST 21552-84.

1.4.11. In the ACS, technical means must be used that correspond to:

- for 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 factors of the external environment, GOST 21552-84
________________
GOST R 52931-2008.

- according to power parameters - GOST 12997-84 for industrial devices and automation equipment of GSP, GOST 21552-84 for computer equipment;

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

1.4.12. The protection of the technical means of the automated control system from the effects of external electric and magnetic fields, as well as noise in the power supply circuits, should be sufficient for the effective implementation of the technical means of the automated control system for its purpose during the functioning of the automated control system.

1.4.13. In the ACS, in accordance with the requirements provided for by the "All-Union Standards of Permitted Industrial Interference" 1-72 - 9-72 and GOST 23450-79 *, measures must be taken to protect the external environment from industrial radio interference emitted by the technical means of the ACS during operation, as well as at the moment of switching on and off.
_________________
* Within the territory of Russian Federation GOST R 51318.11-2006 is in force.

1.4.14. General ergonomic requirements for mnemonic circuits - in accordance with GOST 21480-76, for calculating 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-ray tubes for visual display information - in accordance with GOST 29.05.006-85.

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

1.4.16. General ergonomic requirements for signaling devices of audio primary messages - in accordance with GOST 21786-76.

1.4.17. General ergonomic requirements governing the organization of the workplace, the mutual arrangement of information display means, controls and communication facilities within the workplace - in accordance with GOST 22269-76, including consoles - in accordance with GOST 23000-78.

1.4.18. General ergonomic requirements for operator's seats are in accordance with GOST 21889-76.

1.4.19. General ergonomic requirements for the hall, operator's cabins and the mutual arrangement of workplaces are in accordance with GOST 21958-76.

1.5. Requirements for ACS software

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

1.5.2. ACS software must 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 predominantly built on the basis of existing software packages and other programs borrowed from government, 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. In the ACS should be mainly used database management systems (DBMS), registered in the prescribed manner.

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

1.5.6. The ACS software must have diagnostic tools for the ACS hardware and control the accuracy of the input information.

1.5.7. IN software ACS should be implemented measures to protect against errors in the input and processing of information, ensuring the specified quality of performance of ACS functions.

1.5.8. The general software of the ACS should allow the adjustment of the components of the special software and the further development of the software of the ACS without interrupting the process of its functioning. The already generated and loaded piece of software must be protected from accidental changes.

1.5.9. All programs of special software of a specific ACS must be compatible both with each other and with its general software.

1.5.10. Operational software documentation for the ACS must comply with the ESPD standards and contain all the information necessary for staff ACS for using the ACS software, for its initial loading and (or) generation, loading information from the in-machine information base, launching ACS programs, checking their functioning using appropriate tests.

1.5.11. Newly developed software products during the creation of a specific ACS, 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 ACS

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

1.6.2. To encode information used only in this ACS, classifiers adopted by the customer of the ACS must be used.

1.6.3. For coding in the ACS of the output information used at a higher level, classifiers of higher control systems must 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 ACS for communication between devices of a complex of technical means, the following should be used:

- input and output signals:

Electric - current and voltage in accordance with GOST 26.011-80, with discrete change of parameters in accordance with GOST 26.013-81, coded in accordance with GOST 26.014-81,

- hydraulic in accordance with GOST 26.012-94,

- pneumatic in accordance with GOST 26.015-81;

- character sets alphanumeric in accordance with GOST 27465-87;

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

1.6.6. The information support of the ACS should 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 ACS.

1.6.7. Forms of documents created by the ACS must comply with the requirements of the DCS standards or the regulatory and technical documents of the department of the ACS customer.

1.6.8. Forms of documents and video frames input, output or corrected through the terminals of the automated control system must be agreed with the relevant technical characteristics terminals.

1.6.9. The set of information arrays of the ACS should be organized in the form of databases on computer media.

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

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

1.6.12. The ACS should provide for 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 organizational support of ACS

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

1.7.2. Organizational structure ACS should allow performing all the functions of ACS, taking into account their distribution by control levels.

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

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

________________

* Document not provided. Per additional information refer to the link. - Note from the manufacturer of the database.

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 should be interconnected for all modes of performance of this function and contain instructions on personnel actions in case of failures of the technical means of the automated control system.

1.8. Requirements for linguistic support of ACS

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 the means of automation of the ACS and for the implementation of transformation procedures and machine representation of information processed in the ACS.

1.8.2. The linguistic support of ACS should include:

foreseen language means to describe any information used in the ACS;

- the used language means are unified;

- the descriptions of the same type of information elements and the recording of syntactic constructions have been standardized;

- the convenience, uniqueness and stability of communication between users and the means of automation of the ACS are provided;

- means are provided for correcting errors that arise when users communicate with the technical means of the ACS.

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

1.9. Requirements to legal support ACS

Legal support of ACS should include a set of legal norms:

Determining the legal force of information on data carriers and documents used in the operation of the ACS and created by the system;

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

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

1.10. Requirements for operational documentation for ACS

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 ACS should:

- contain information necessary for quick and high-quality development and correct operation of automated control systems;

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

- not contain provisions that are open to 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 are in accordance with GOST 12.2.007.0-75.

2.3. Safety requirements for computer equipment used in automated control systems are in accordance with GOST 25861-83.

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

2.5. The technical means of ACS placed at explosion and fire hazardous installations must meet the requirements of the "Rules for the Installation of Electrical Installations".

2.6. The technical means of the ACS must be installed in such a way as to ensure their safe operation and maintenance.

2.7. Safety requirements should be established by a special section job descriptions and (or) instructions for the operation of ACS and have links to instructions for the operation of technical means.

2.8. General ergonomic requirements for workplaces of ACS personnel - in accordance with GOST 22269-76.

2.9. Comfortable living conditions for ACS personnel must comply with the current sanitary standards, the maximum permissible living conditions are 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 rooms of the ACS personnel are in accordance with GOST 12.1.005-88.

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

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

2.13. General ergonomic requirements for vibration of equipment at workplaces of ACS personnel are in accordance with GOST 12.1.012-2004.

2.14. Signal colors and safety signs - in accordance with GOST 12.4.026-76 *.
__________________
* On the territory of the Russian Federation, GOST R 12.4.026-2001 is in force.

3. TYPES AND PROCEDURE FOR CONDUCTING TESTS DURING THE COMMISSIONING OF THE ACS IN ACTION - according to GOST 34.603-92

3.1-3.7.13 (Deleted, Amendment).

4. COMPLETE SET OF ACS COMMITTED INTO OPERATION

4.1. The ACS should include:

- technical means of ACS in the form of a set of technical means of ACS, prepared for operation;

- spare products and devices (spare parts), devices and devices for performance testing, adjustment of technical means and control of the metrological characteristics of the measuring channels of the automated control system in the amount provided for by the order project documentation, agreed with the customer of the ACS and the user's metrology service in terms of the calibration equipment;

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

- at least two copies of programs on data carriers and operational documentation for them in accordance with GOST 19.101-77, taking into account the 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 - in accordance with GOST 19.501-78;

- two copies of the operational documentation for the ACS in accordance with GOST 34.201-89, including the necessary documentation for the information support of the ACS (ACS form in one copy).

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

4.2. ACS staff must be staffed with personnel who meet the requirements of clause 1.3.

4.3. To complete the created ACS, the following products supplied as production and technical purpose can be used:

- 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 the development, putting into production and testing of the supplied components used in the ACS must comply with State standards systems for the development and launch of products.

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

5. WARRANTY

5.1. The developer of the ACS guarantees the compliance of the ACS with the requirements of this standard and the technical specification for the ACS, provided that the user observes the conditions and rules of operation.

5.2. The conformity of the hardware, software and automation systems used in the ACS and supplied as products for industrial and technical purposes to the requirements of standards and technical specifications for them is guaranteed by the manufacturers of these types of products, provided that the user observes the conditions and rules of operation.

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 ACS must be set in the TK for the ACS and cannot be less than 18 months.

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

ANNEX 1
Mandatory

1. APCS in industry and non-industrial sphere should control 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 object of control (TOC).

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

3. APCS should perform control, information and auxiliary functions.

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

5. Control actions in the APCS should be generated automatically or formed by its operational personnel using a set of automation tools included in the system.

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

7. The APCS should carry out the function of monitoring the execution of control actions on the TOU and signal the exit executive bodies into the maximum permissible positions.

8. When implementing the function of automatic emergency shutdown of equipment in the APCS, an alarm should be provided to operating personnel about this by means of light and, if necessary, sound signals with automatic recording of the shutdown time.

9. Products should be used as the main technical means of APCS. State system industrial devices and automation equipment (GSP), other products that meet the requirements of ESSP standards, and computer equipment that meet GOST 21552-84.

10. The technical means of the APCS placed on the technological equipment must comply with the requirements imposed on them by the operating conditions.

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

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

- the permissible level of psychophysiological and emotional load of operators established by the industry normative 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 actions (interactions) included in the corresponding automated and interconnected non-automated functions of the APCS, as well as to make the right decisions in emergency situations or in case of other violations of normal operation;

- proven skills that allow performing all actions and interactions with the specified accuracy and speed.

13. The software of the ACS TP should provide for, and the organizational support reflects the language means for communication of the operating personnel with the CCS of the ACS TP, convenient and accessible for persons who do not have the qualifications of a programmer.

14. Codes and symbols used in APCS should be close to the terms and concepts used technological staff control object, and should not cause difficulties in their perception.

15. The measuring channels of the APCS must have metrological characteristics that ensure the performance of its information functions with the indicators specified in the technical specification for the APCS.

16. Requirements for testing ACS TP

16.1. Preliminary tests of the APCS are carried out at the operating TOU.

16.2. Preliminary tests of the APCS functions required for start-up and running-in technological equipment, is allowed to be carried out at the facility using simulators.

16.3. Determination of the actual values of the indicators of technical and economic efficiency and reliability of the APCS is carried out after its commissioning. The duration of the operating time of the APCS, 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 FOR ENTERPRISES, PRODUCTION AND RESEARCH AND PRODUCTION ASSOCIATIONS

APPENDIX 2
Mandatory

1. ACS should increase the efficiency of production and economic activities of an enterprise, production or research and production association (hereinafter - the enterprise).

3. ACS should be implemented as a set of jointly functioning subsystems, the interaction between which should take place through a common (single or distributed) database.

APPENDIX 3 (mandatory). ADDITIONAL REQUIREMENTS FOR INDUSTRIAL AUTOMATED CONTROL SYSTEMS (AMS)

APPENDIX 3
Mandatory

1. OASU should provide:

- improving the characteristics of the object of management (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 the initial data, increasing the accuracy and efficiency of calculations);

- improving the organization of the performance of management functions (in particular, the rational distribution of work between the divisions of the management apparatus, computing centers and research organizations and enterprises).

2. The OASU should have automated industry management functions, for example:

- forecasting and planning of production and industry resources;

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

- management labor resources industry;

- management material resources industry;

- management capital construction in branch;

- management financial resources industry;

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

3. OASU should be implemented in the form of a set of jointly functioning subsystems, the interaction between which should take place through common databases.

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

5. OASU should provide an interactive mode of work with the databases of the system.

6. The creation of an OASU should lead to the improvement of the methods and structure of management of the industry.

7. The duration of the trial operation of parts of the OAMS 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 OASU is established by agreement between the developer and the customer.

APPENDIX 4 (reference). EXPLANATION OF CERTAIN TERMS USED IN THIS STANDARD

APPENDIX 4
Reference

Automation complex (KSA)- the supplied set of mutually agreed complexes of hardware and software (products), developed and manufactured as products for industrial and technical purposes. The composition of the KSA may also include other products and (or) documents that are part of the information, organizational or other types of support for automated systems.

Building up the 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 a cathode-ray tube of a document of a drawing or a text of a message used in an automated control system.

Measuring channel of ACS- a functionally combined set of technical and (if necessary) software tools, designed to implement one simple measurement function of the ACS.

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

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

State tests- ACS acceptance tests conducted by the state commission.

Interdepartmental tests of ACS- Acceptance tests of ACS, carried out by a commission of representatives of several interested ministries and (or) departments.

Departmental tests of ACS- Acceptance tests of ACS, conducted by a commission of representatives of the interested ministry or department.

Electronic text of the document
prepared by JSC "Kodeks" and verified by:
official publication
Information technology.
Automated systems.
Key points:
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
Type of document:	GOST
Host body:	Gosstandart of the USSR
Status:	Document canceled in part Acting
Published:	official publication Information technology. Automated systems. Key points: Sat. GOSTs. - M .: Standartinform, 2009
Date of adoption:	December 20, 1985
Effective date:	01 January 1987
Revision date:	01 July 2009

Name (eng.): 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 required to describe the scope of data exchange between application systems and information requirements for 3D designs (designs) of mechanical parts and assembly units. Configuration in this context only covers data and processes that drive 3D product design data. The notion of exchange is used to extend the scope of the standard only to data used as part of a 3D product definition. Organizations exchanging data in accordance with this standard may be bound by contractual relationships that are not addressed in the standard.
The scope of this standard covers:
a) products consisting of mechanical parts and assembly units;
b) product defining and configuration management data relevant to the product design phase;
c) design (construction) change and data associated with documenting the change process;
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 different rules (disciplines) at the design stage in the product life cycle;
f) designation of government, industry, brand or other specifications for the project (structure), process, surface treatment and materials that are determined by the designer for the product being constructed;
g) government, industry, brand or other designation of standard parts in order to include them in the design (project) of the product;
h) data required to monitor the progress of the project;
i) data needed to control design approval, specific aspects of a project, or product configuration management;
j) data identifying the supplier of the product or its design and, if necessary, specific information about the supplier;
k) designation of the contract and reference to it, if the part is designed according to the contract;
l) designation of the level of classification of protection (confidentiality) of an individual part or part that is a component assembly unit;
m) data used in the analysis of the design, or the results of its verification, used to justify changes to the design.
The scope of this standard does not cover:
a) the data used in the analysis of the project, or the results of its verification, which are not used to justify the changes made to the project;
b) data on changes in the project from the results of the initial analysis to the end of this project;
c) data defining the product and its configuration management related to any stage life cycle creating a product in addition to its design;
d) business data for structural design management;
f) alternative representations of data according to different rules (disciplines), except for the design stage (for example, at the production stage);
f) the use of 3D Boolean geometry to represent design items;
g) data related to the visual representation of any form of product or the management of its configuration

Photosensitivity of photographic materials (films and photographic papers) and matrices digital cameras is determined in accordance with the sensitivity scale.

Previously, photosensitivity standards were used that were in use in different countries.

For example, ASA - American Standards Association; DIN - Deutsche Indastrienormen.

Recently, manufacturers have agreed to unified system determination of photosensitivity.

ISO / ISO ° values are used in a single scale of light sensitivity

A comparison of the light sensitivity scales is made in Table 1.

Light sensitivity scales ISO / ISO °, ASA, DIN, GOST

Table 1

ISO°	GOSTnew	GOSTold

Sensitivity value, expressed in ISO units, consists of two numbers separated by a forward slash.

A number of first numbers coincide with the light sensitivity scales of the new GOST and ASA, a number of second numbers (called ISO degrees) coincide with the light sensitivity scale, expressed in DIN degrees.

Manufacturers of cameras and exposure meters sometimes limit themselves to only the first ISO sensitivities. This is due to the fact that the scale of ISO sensitivity units is an arithmetic progression with the module 1.26. The rows of shutter speeds and apertures of the camera are arranged in a similar way.

The sensitivity scale, expressed in ISO degrees, is a logarithmic scale with a difference of one.

For practice, it is enough to remember that a twofold change in photosensitivity according to GOST, ISO, ASA corresponds to a change of three degrees DIN and ISO ° see Table 2

The most common range of photosensitivity

table 2

In practice digital photography the minimum value for the sensitivity of the camera sensor is 100 or 200 units. Smaller values of the minimum sensitivity are achieved, as a rule, by software methods.

The high maximum sensitivity of the matrix is not always used. This is due to the fact that with increasing sensitivity, the matrix noise increases and the image quality decreases.

Modern algorithms embedded in digital cameras allow using high sensor sensitivity values, but require extremely accurate exposure determination and accurate post-processing.