November 2004 A set of standards for automated systems GOST TYPES, COMPLETENESS AND DESIGNATION OF DOCUMENTS WHEN CREATION OF AUTOMATED SYSTEMS. GOST GOST AUTOMATED SYSTEMS. STAGES OF CREATION. GOST TECHNICAL TASK FOR THE CREATION OF AN AUTOMATED SYSTEM. GOST TYPES OF TESTS OF AUTOMATED SYSTEMS
If all team members need to have unrestricted access to information in a joint document, since they are For example, if you work in different areas of analysis, then you have the ability to clone and consolidate. In this case, any number of special copies are generated from the original document and passed on to the team members, who can then process them independently of each other. From time to time, the state of the clones is automatically compared to the state of the original document, and the changes are consolidated by consolidation, so that all team members are returned to the same level.
November 2004 GOST STATE STANDARD OF THE UNION SSR GOST AUTOMATED SYSTEMS. STAGES OF CREATION. The standard establishes the stages and stages of creating a speaker. Stages Stages of work 1. Formation of requirements for the AU 1.1. Inspection of the facility and justification of the need to create an AU Formation of user requirements for the AU Preparation of a report on the work performed and an application for the development of an AU (tactical and technical task)
This tried and tested method offers the greatest possible flexibility to all participants with the least administrator effort. A simple script should be used as an example. The company develops a product that consists of complex substructures. At the desired time, individual clones can be automatically merged with the original document again, so that all changes and extensions are included in the resulting document.
The original document will be processed by two teams in parallel. 
Work continues in the original document on the Signal Cable Complete structure element. 
The clone document continues to work on the external systems framework element. 
The result document then merges the changes from the clone with the changes from the main document.
November Development of the NPP concept Object study Carrying out the necessary research and development work Development of options for the NPP concept that meets the user's requirements Registration of the report on the work performed. 3. Terms of reference Development and approval of terms of reference for the creation of a nuclear power plant. 4. Draft design Development of preliminary design solutions for the system and its parts Development of documentation for the NPP and its parts. GOST
This umbrella term refers to various application-specific capabilities, of which two are currently being implemented and more are planned. A typical situation might be that a company produces components that are built into another company's product. Therefore, the first company works as a supplier for the second company. An additional processed interface can also be returned to the supplier.
Product features Interfaces
With product characteristics interfaces, product characteristics can be transferred from source document to target document. The function information can be updated as often as required in this direction, i.e. if new sources are found in the source document, they can be sent to the owner of the target document. New results are automatically entered into the target document.
November Technical project Development of design solutions for the system and its parts Development of documentation for the NPP and its parts Development and execution of documentation for the supply of products for completing the NPP and (or) technical requirements (technical specifications) for their development Development of design assignments in adjacent parts of the facility project automation. 6. Working documentation Development of working documentation for the system and its parts Development or adaptation of programs. GOST
Terminological control during data entry
Reuse of information requires that the same concepts be called the same. To avoid such terms when entering names, users can use an optional collective directory entry. At the bottom of the collective entry, all designations already entered are listed in this document.
If a suitable term already exists in the list, you can drag it to the upper list with the mouse and select. To prevent re-entering a term already entered a second time, the user can be assisted in entering a similarity search. 
This type of input is available for a wide variety of label types: functions, failures, actions, etc.
November Commissioning Preparing the automation object for commissioning the NPP Personnel training Completing the NPP with the supplied products (software and hardware, software and hardware complexes, information products) Construction and installation works Commissioning works Preliminary tests Trial operation Acceptance tests. 8. Maintenance of the AU 8.1. Performance of work in accordance with warranty obligations Post-warranty service. GOST
There are various ways to connect external directories to use terminology control across multiple documents. 
In the term and translation editor, labels and translations can be maintained with minimal effort. The changes affect all places where the term has been used. This reduces translation efforts to a minimum.
In the catalog editor, you can also save conditions for labels. To facilitate navigation through often extensive catalogs, these terms can also be categorized into user-defined categories. 
The same function occurs several times in the document at different bearing functions and in other places, since new faults are found, so new faults can be inherited upon request to other occurrences of the function. Figure 8: Inheritance Step 1.
November 2004 Stages The stages carried out by organizations participating in the work on the creation of the AU are established in contracts and technical specifications. 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" in one stage Technological project ". It is allowed to perform separate 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 GOST
Concentration on core business
Figure 9: Inheritance Step 2. The adaptability provided by the software management system. To simplify the update process softwareThe program components can be stored in a central location on the network. However, as you will soon see, this is not enough for a reasonable risk analysis. For example, there is no built-in ability to evaluate correlations or get statistics or take action. The word processor knows only the text and elements and functions of the structure, the spreadsheet has no idea about errors, measures, deadlines, etc.
November 2004 GOST STATE STANDARD OF THE UNION SSR GOST TYPES, COMPLETENESS AND DESIGNATION OF DOCUMENTS WHEN CREATING AUTOMATED SYSTEMS The list of names of documents being developed for the system and its parts must be defined in the terms of reference for the creation of an automated system (subsystem) in accordance with GOST, which is being developed
And so it happens all too often that the actually required activity of risk analysis is increasingly invading the background due to excessive macro programming in the respective office tools. We know the demands of the international market and ensure that the product always meets them.
Documents have the advantage that their access can be centrally managed, easily exchanged, easily integrated with document management systems, etc. Experience has shown that document oriented software is adequate for the vast majority of use cases. Even if it requires multiple users working together over one document, without getting each other, this approach provides a convenient and pragmatic solution with simultaneous development.
November 2004 GOST The following organizational and administrative documents are developed at the “Putting into operation” stage: 1) an act of completion of work; 2) the act of acceptance for trial operation; 3) the act of acceptance into industrial operation; 4) work schedule; 5) order on the composition of the acceptance committee; 6) order to carry out work; 7) work program; 8) test report; 9) agreement protocol.
The server software always relies on the results of the client software: it consolidates and centralizes the information contained in the documents and then provides them different ways for different purposes. Maintenance efforts are limited by differences between individual options.
For each system and each process, any number of variants can be defined based on the so-called basic structure. The main structure contains all the information that applies to all variants. Variants are derived from the main structure, excluding objects that are not relevant to the variant from that variant, or by adding attributes that apply only to the variant. The following figure shows the basic structure of the connector, which can be realized in two versions: with solder joint and with screw joint.
November 2004 GOST STATE STANDARD OF THE UNION SSR GOST TYPES OF TESTING OF AUTOMATED SYSTEMS AU tests are carried out at the stage of Commissioning in accordance with GOST in order to verify the compliance of the created AU with the requirements of the technical assignment (TZ). The types of tests and the status of the acceptance committee are established in the contract and (or) TK. To plan the conduct of all types of tests, the document Program and test methods are developed. The developer of the document is established in the contract or TK.
Both versions can be seen in the master structure. 
Now, if the solder connection option is activated, this structure looks like this. 
In contrast, the structure in the variant clamping connection is as follows. 
Next more detailed example shows that not only these structures can be variant-dependent, but also separate attributes of objects.
November 2004 GOST STATE STANDARD OF THE UNION SSR GOST TECHNICAL TASK FOR THE CREATION OF AN AUTOMATED SYSTEM. GENERAL PROVISIONS The technical specification for the NPP is the main document that defines the requirements and procedure for creating an automated system, in accordance with which the NPP is developed and accepted upon commissioning. Changes to the technical specification for the NPP are drawn up by an addition or a protocol signed by the customer and the developer. The supplement or the specified protocol is an integral part of the technical specification for the NPP. On the title page of the TK on the AU there should be an entry Valid from ....
An example is a manufacturing process that is reviewed once and without rework. In this case, depending on the variant, not only the finalization step is available, but also the processing status of the measures. 
An overview of all object-specific object values \u200b\u200bcan be found in the Object inspector.
The following table provides an overview of the most important variant-dependent attributes. The headquarters of this organization is located in Geneva. The focus of standardization activities is on technical standards. They have a high economic and social status. They also aim to streamline and simplify trade between different countries and give governments a technical basis for legislation.
November 2004 GOST COMPOSITION AND CONTENT TK for NPP contains the following sections, which can be divided into subsections: general information; purpose and goals of creating (developing) the system; characteristics of automation objects; system requirements; composition and content of work on the creation of the system; the procedure for control and acceptance of the system; requirements for the composition and content of work on the preparation of the automation object for putting the system into operation; documentation requirements; development sources. The TK for the AU can include applications, it is allowed to introduce additional, exclude or combine subsections.
November 2004 GOST Section General information indicate: the full name of the system and its symbol; subject code or contract code (number); the name of the enterprises (associations) of the developer and customer (user) of the system and their details; a list of documents on the basis of which the system is created, by whom and when these documents were approved; planned start and end dates for the creation of the system; information about the sources and procedure for financing the work; the procedure for registration and presentation to the customer of the results of work on the creation of the system (its parts), on the manufacture and adjustment of individual means (hardware, software, information).
November 2004 GOST Section Requirements for the system consists of the following subsections: requirements for the system as a whole; requirements for functions (tasks) performed by the system; requirements for the types of security. The section Composition and content of work on the creation (development) of the system should contain a list of stages and stages of work on the creation of the system in accordance with GOST, the timing of their implementation, a list of organizations of performers of work, links to documents confirming the consent of these organizations to participate in the creation of the system, or a record identifying the person responsible (customer or developer) for carrying out these works. This section also provides: a list of documents according to GOST, presented at the end of the corresponding stages and stages of work; type and procedure for the examination of technical documentation (stage, stage, volume of the checked "documentation, organization-expert);
November 2004 GOST In the Documentation Requirements section, the following is given: a list of sets and types of documents to be developed that meet the requirements of GOST agreed by the system developer and the Customer; In the presence of approved methods, the TOR for NPPs includes applications containing: calculation of the expected efficiency of the system; assessment of the scientific and technical level of the system. THE RULES FOR REGISTRATION OF TK at the NPP are drawn up in accordance with the requirements of GOST on A4 sheets. The values \u200b\u200bof indicators, norms and requirements are indicated, as a rule, with maximum deviations or maximum and minimum values.
November 2004 GOST PROCEDURE FOR DEVELOPING AGREEMENT AND APPROVAL OF TOR FOR NPP The project TK for the NPP is developed by the organization-developer of the system with the participation of the customer on the basis of technical requirements. The term for approval of the draft TK for the NPP in each organization should not exceed 15 days from the date of its receipt. It is recommended to send copies of the draft TK to the AC (copies) simultaneously to all organizations (departments) for approval.
November 2004 GOST Approval of the technical specification for the NPP is carried out by the heads of enterprises (organizations) of the developer and customer of the system. Comments on the draft TOR for the NPP should be submitted with a technical justification. If, when agreeing on the draft TK for the NPP, disagreements arose between the developer and the customer (or other interested organizations), then a protocol of disagreements is drawn up. November 20, 2004 Comparative analysis of the RUP and GOST stages The regulation of project activities is based on standards and methodologies, among which the most popular at present are both the GOST 34 and 19 series standards, which determine the requirements for the developed documentation, and the new GOST R ISO standards / IEC and GOST R ISO / IEC, defining the processes of the life cycle of software. One of the most developed and popular methodologies describing the life cycle processes of the PS is the Rational Unified Process (RUP), developed by Rational Software and corresponding to GOST R ISO / IEC RUP stages GOST stages Inception Requirements formation Concept development Terms of reference Elaboration Draft design Technical design Construction design Working documentation Transition Commissioning Maintenance
"INFORMATION TECHNOLOGY COMPLEX OF STANDARDS FOR AUTOMATED SYSTEMS ..."
STATE STANDARD OF THE UNION OF SSR
INFORMATION TECHNOLOGY
COMPLEX OF STANDARDS FOR AUTOMATED
SYSTEMS
AUTOMATED SYSTEMS
STAGES OF CREATION
GOST 34.601-90
IPK PUBLISHING STANDARDS
STATE STANDARD OF THE UNION OF SSR
Information technology Set of standards for automated systemsAUTOMATED GOST SYSTEMS
STAGES OF CREATION 34.601-90 Information technology. Set of standards for automated systems. Automated systems. Stages of development Date of introduction 01.01.92 This standard applies to automated systems (AS) used in different types 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 a speaker. Appendix 1 contains the content of work at each stage.
1. GENERAL PROVISIONS
1.1. The process of creating an AU 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 technical assignment)
2. Development of the AU concept 2.1. Object study
2.2. Carrying out the necessary research work
- & nbsp– & nbsp–
2.2. Stages and stages performed by organizations - participants 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 design". 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, conducting:
Collection of data about the automation object and the activities carried out;
Assessment of the quality of the object and the activities carried out, identifying problems that can be solved by means of automation;
Assessment (technical and 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 speaker.
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 task)", a report on the work performed at this stage is drawn up and an application for the development of an AU (tactical and technical task) 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 R&D reports.
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 the best option; determination of the procedure for assessing the quality and conditions of system acceptance; evaluating the effects of 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;
composition of task complexes 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"
ensure the development common solutions by the system and its parts, the functional and algorithmic structure of the system, by the functions of personnel and organizational structure, by the structure of technical means, by algorithms for solving problems and used languages, by the organization and maintenance of the information base, the system of classification and coding of information, by software.
10. At stages 4.2 and 5.2 "Development of documentation for the NPP and its parts"
carry out the development, execution, coordination and approval of documentation in the amount necessary to describe the full set of adopted design solutions and sufficient for further work on the creation of the nuclear power plant.
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 project of the automation object for construction, electrical, sanitary and other preparatory workassociated with the creation of the AU.
13. At stage 6.1 "Development of working documentation for the system and its parts"
carry out the development of working documentation 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 execution, coordination and approval.
Types of documents - according to GOST 34.201.
14. At stage 6.2 "Development or adaptation of programs", programs and software for 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"
carry out work 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 tested.
17. At the stage "Completing the AU with the supplied products" ensure the receipt of components of serial and unit production, materials and installation 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 equipment 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 tools.
20. At stage 7.6 "Preliminary tests" carry out:
Speaker performance tests and compliance terms of reference in accordance with the program and method of preliminary tests;
Eliminating malfunctions and making changes to the documentation for the NPP, including the operational one in accordance with the test report;
Execution 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 NPP; revision (if necessary) of the AC software; additional adjustment (if necessary) of the NPP hardware; registration of an act of completion of trial operation.
22. At stage 7.8 "Acceptance tests" carry out:
Tests for compliance with technical specifications in accordance with the program and methodology of acceptance tests;
Analysis of the test results of the AU and elimination of the shortcomings identified during the tests;
Execution of the certificate 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 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:
System functioning analysis;
Revealing deviations of the actual operating 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 WORK TO CREATE AU
1. Organization-customer (user), for which the NPP will be created and which provides financing, acceptance of works 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 for the AU.
3. A supplier organization that manufactures and delivers 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 construction, electrical, sanitary and other preparatory work related to the creation of the nuclear power plant.
6. Organizations for construction, assembly, commissioning and others.
Notes:
1. Depending on the conditions for creating an AU, various combinations of functions of a customer, developer, supplier and other organizations involved in the creation of 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, Ph.D. 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.
Klochkov; 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; VC. Chistov, Cand. econom. sciences
2. APPROVED AND PUT INTO EFFECT by the Decree of the USSR State Committee on Product Quality Management and Standards dated December 29, 1990 No. 3469
3. REPLACE GOST 24.601-86, GOST 24.602-86
4. REFERENCE REGULATORY AND TECHNICAL DOCUMENTS
Designation NTD referenced Application number GOST 19.101-77 1 GOST 34.201-89 15. REPUBLICATION. June 1997, Princess Chulabhorn Mahidol, daughter of King Rama IX, grandson of the great King of Siam Rama V Chulalongkorn, came. So great is the respect for the personality of Chulalongkorn that, according to the established tradition, high-ranking guests from the Kingdom of Thailand must visit our museum (and the Hermitage), and this visit has an almost ritual meaning for them, since ... "
«1 Table of Contents Information about the Report Chapter 1. Strategic overview 1.1. Rosatom today 1.2. Main results of activities in 2014 1.3. Mission and strategy of ROSATOM 1.4. Value creation, business model and markets of presence Chapter 2. One step ahead in 2014 2.1. International business 2.2. International cooperation 2.3. Innovative development 2.4. Business diversification Chapter 3. Main results 3.1. Financial and economic results 3.2. Mining Division 3.3. Fuel ... "
“Topic 1. Financial environment of entrepreneurship: concept, essence and types 1. Financial environment of entrepreneurship: concept and essence, structure. The financial environment of entrepreneurship is a set of economic entities operating outside the given enterprise and affecting its ability to carry out entrepreneurial activities and receive income. Or the financial environment of entrepreneurship can be viewed as a combination of various conditions and factors that affect the results ... "
“S.N. Terekhin (St. Petersburg University of the State Fire Service of the Ministry of Emergency Situations of Russia; e-mail: [email protected]) USE OF THE PRINCIPLES OF SATELLITE COMMUNICATION SIGNAL BROADCASTING TO SOLVE THE POSITIONING PROBLEMS OF THE FIRE SECURITY UNITS The analysis of the characteristics of the navigation field of global navigation satellite systems is carried out. A solution to the problem of positioning the fire protection units of the EMERCOM of Russia by creating ground-based equipment for navigation signals is proposed. Key words: radio navigation, ... "
2016 www.site - "Free e-library - Scientific publications"
The materials on this site are posted for review, all rights belong to their authors.
If you do not agree that your material is posted on this site, please write to us, we will delete it within 1-2 business days.