3) a description of the operator’s actions when working with programs (rules for launching programs, work order, actions in possible non-standard situations, etc.).
Test case description includes description:
1) functions and parameters of the software tested by the test case;
2) composition technical means necessary to test the software using this example;
3) input information;
4) results of running programs based on test case data;
5) operator actions when checking the program on a test example;
6) test results (control standard) of programs using a test example.
Procedure for transferring software documentation
All programs and instructions, tested by the developer on a test example, are handed over to the customer under a certificate certifying their acceptance for trial operation.
Delivered to the customer software, instructions and descriptions of algorithms must meet the requirements for the composition and content of the working design of the information system. Programs recorded on magnetic media are transferred to the customer. The customer provides the developer with magnetic media and computer time necessary for putting programs into trial operation and duplicating them (if necessary).
Acceptance of a set of tasks (subsystems) for trial operation involves solving a test case by specially trained customer personnel in the presence of developer representatives, followed by analysis of the results. By mutual agreement, the test case can be performed by the developer in the presence of the customer.
Based on the acceptance results, a software acceptance certificate for trial operation is signed. Discovered
Developer errors in programs and technical documentation are eliminated during the commissioning process.
Organizational and administrative documentation
For the main work carried out at the “Detailed Design” stage, the following organizational and administrative documentation is drawn up:
1) order to carry out work at the stage in accordance with the schedule organizational and technical measures;
2) schedule of joint work between the contractor and the customer;
3) act of verification on test examples and acceptance of work programs into trial operation;
4) act of readiness of regulatory and reference documentation;
5) the act of carrying out organizational and technical measures to prepare the enterprise for the implementation of the information system.
5.5. Putting the information system into operation
Commissioning of an information system and its individual elements is a process of gradual transition from existing management methods to automated management methods.
Commissioning of the information system is organized and carried out by the customer with the participation of the developer and co-executing organizations. Interaction between customer organizations, developers and co-executors is carried out on the basis of contractual terms and a schedule for putting the information system into commercial operation.
Commissioning is carried out in stages, starting from the stage of development of the technical project, as the working documentation is ready and the technical means are put into operation, ensuring the implementation of queues or information system objects capable of independent functioning.
You should begin putting the information system into operation if you have:
1) executed documents on the implementation of the action plan for the preparation of the facility;
2) working documentation for the implementation of a dedicated queue or information system as a whole;
3) trained personnel providing preparation for commissioning
operation and operation of a dedicated information system queue;
4) technical means of the information system accepted for operation, ensuring the functioning of the implemented sets of tasks.
Organization of work
Implemented:
1) trial operation of individual tasks and their complexes;
2) acceptance of task complexes for commercial operation;
3) carrying out acceptance tests;
4) acceptance of the system for commercial operation.
The composition and order of work are determined by the agreed commissioning schedules, which indicate the composition and timing of the following work:
1) for the construction, installation, commissioning and testing of information system objects from the moment of receipt of working documentation until the objects are put into commercial operation;
2) for carrying out trial operation and acceptance testing of task sets;
3) to ensure the transition from existing management methods
To methods provided for by the information system design.
At the stage “Putting the information system into operation”
the customer is obliged:
1) terminate execution organizational and technical measures to prepare the enterprise for the implementation of the information system and formalize them with acts;
2) ensure that the enterprise personnel comply with job and technological instructions;
3) put into operation the technical means necessary for the implemented technological process data processing;
4) issue an order with a schedule for conducting trial operation of the information system and analyze, together with the developer, the results of trial operation;
5) complete the trial operation of the complexes of tasks included in the information system and their acceptance for commercial operation;
6) make changes to the organizational structure of the enterprise in accordance with the information system project;
7) develop a draft order on the composition of the acceptance committee;
8) develop and coordinate with the developer a draft program acceptance tests;
9) organize the work of the acceptance committee, provide it with the required documentation and test the information system;
10) check the effectiveness of the implemented solutions in industrial operation conditions and, based on the results of the analysis of the functioning of the system, develop recommendations for its further development.
At the stage “Putting the information system into operation”
the developer is obliged:
1) adjust technical documentation based on the results of trial operation of the information system;
2) take part in the development of a draft program for acceptance testing of the information system;
3) provide methodological guidance and take part in putting tasks (sets of tasks) into commercial operation;
4) participate in the work of the commission for acceptance of the information system into commercial operation.
The procedure for conducting trial operation
The beginning of trial operation of tasks (sets of tasks), the terms of operation and the composition of the commission for the acceptance of a specific task or subsystem are determined by an order issued by the customer and agreed with the developer. Attached to the order is the agreement agreed with
the developer has a trial operation program, which defines the conditions for testing sets of tasks, the procedure for checking technical means when solving sets of problems (subsystems) and the procedure for eliminating deficiencies identified during trial operation.
Additional customer requirements that arise during trial operation and are not provided for in the technical specifications and technical design do not constitute grounds for a negative assessment of the results of trial operation and can be satisfied by additional agreement within the agreed time frame.
If the results of the trial operation of the tasks (subsystems) are positive, a bilateral act on their acceptance for commercial operation is drawn up.
After the information system has been accepted for commercial operation, the customer bears responsibility for its functioning within the scope of the accepted sets of tasks and tools.
Initial and reporting documents for testing information system software
Joint tests are carried out by a customer commission, which includes the development manager and some leading developers. The testing commission is guided by the following documents:
1) technical specifications for the creation of an information system approved by the customer and agreed with the developer;
2) current state and industry standards for software design and testing and technical documentation;
3) test program for all technical requirements
4) test methods for each section of the requirements of the technical specifications.
Test program, methods of their conduct and evaluation
The results are developed jointly by the customer and the developer and must be agreed upon and approved. They contain clarifications of the requirements of the technical specifications for a given system and must guarantee their correct verification. System documentation should
fully comply with the programs being tested, ensure that the system is understandable by maintenance personnel, and also provide the ability to develop and modernize programs to increase the duration of their life cycle.
Test program is a plan for conducting a series of experiments. It is developed from the position of minimizing the amount of testing while ensuring the reliability of the results obtained is specified and agreed upon with the customer. To do this, the sequence and scope of each testing during the testing process are determined to verify compliance with the requirements of the technical specifications when minimum costs. It can be especially difficult to select a set of stressful system operating situations under which testing should be carried out. Test program should contain the following clearly defined sections:
1) test object, its purpose and a list of the main documents that determined its development;
2) the purpose of the tests, indicating the main requirements of the technical specifications to be verified, and restrictions on testing;
3) actually test program, containing a check of the completeness of the developed system in accordance with the technical specifications and a test plan for checking the functioning of programs for all sections of the technical specifications and additional requirements formalized by separate solutions;
4) test methods, unambiguously defining all the concepts of the characteristics being tested, testing conditions, tools used for testing, methods for processing and evaluating test results for each section of the test program.
Large volume of heterogeneous data obtained during testing
software, and variety possible ways their processing, interpretation and evaluation lead to the fact that the most important factors for processing test results become methods for processing and evaluating results. In accordance with test methods, automation equipment must ensure completeness of characteristics checks for each section of methods and development
inspection protocols for items of the test program. The complexity of software and the close relationship between its various characteristics lead to the need for careful formulation of all test conditions and parameter values at which the test must be performed.
Test results are recorded in protocols , which usually contain the following sections:
1) the purpose of testing and the section of the requirements of the technical specifications according to which the test is carried out;
2) indication of the methods in accordance with which the tests were carried out, processing and evaluation of the results;
3) testing conditions and characteristics of the initial
4) generalized test results with their assessment for compliance with the requirements of the technical specifications and other governing documents;
5) conclusions about the test results and the degree of compliance of the created software with a certain section of the requirements of the technical specifications.
The protocols for the entire program are summarized in an act, resulting in
a conclusion is made about the system’s compliance with the customer’s requirements and whether the work is completed with a positive or negative result. If all requirements of the technical specification are fully met, the customer is obliged to accept the system and the work is considered completed.
However, as already noted, for complex software packages it is difficult to foresee and correctly formulate all the requirements of the technical specifications at the initial stages of design. Therefore, during debugging and testing, it is often revealed that some requirements of the technical specifications are not met and sometimes even fundamentally cannot be fulfilled even with the most conscientious attitude to this on the part of the developer. In this case, it is necessary to work together between the customer and the developer to find a compromise solution when completing tests and drawing up a conclusion. Some shortcomings of the program complex during the testing process are only registered and recorded in terms of eliminating the commission’s comments,
who carried out the tests. This plan is an annex to the test results report and allows you to separate subsequent improvements from direct tests.
The procedure for carrying out acceptance tests
The customer is responsible for organizing and conducting acceptance into commercial operation. Acceptance of the information system for commercial operation is carried out upon completion of the customer's acceptance of all sets of tasks (subsystems) for commercial operation.
Tasks, sets of tasks (subsystems) and technical means of the information system that are not provided for in the technical specifications, but implemented by the customer independently, can be included in the complex of the information system being delivered only in agreement with the developer and after appropriate changes have been made to the technical specifications for the creation of the information system.
At the request of the customer or developer, representatives of subcontractors may be involved in the acceptance of the information system.
The customer presents the information system to the acceptance committee. In addition to the members of the commission, experts on certain issues of creation may be involved in the acceptance process with the right of an advisory vote. information systems. The customer is obliged to ensure normal working conditions for the commission in accordance with the adopted information system acceptance program. For prompt solution organizational issues arising during the acceptance of the information system, by order of the head of the developer organization, a responsible representative from the developer organization is allocated.
The customer, together with the developer, prepares a draft program for testing and acceptance of the information system and submits it to the acceptance committee for review and approval. The program indicates: the name of the information system being submitted, the directive documents on the basis of which the system was developed (if any), the composition of the acceptance committee and the number of the order for its appointment, purpose, objects, volume, location and
sequence of tests, methods of testing and evaluation of results.
The customer prepares together with the developer and transfers the following documents for temporary use to the commission:
1) orders, instructions, plans, contracts providing for the creation of an information system;
2) technical and economic justification, terms of reference, technical design, detailed design of the information system;
3) acts of consideration and approval of the technical design;
4) bilateral acts of the customer and the developer on the delivery of tasks, sets of tasks (subsystems), devices and their complexes into commercial operation in accordance with the approved technical specifications.
The acceptance committee provides:
1) checking documentation and functioning of the information system;
2) organizing working groups and distributing responsibilities among commission members to check individual subsystems;
3) checking the calculation of the economic efficiency of the created information system;
4) organizing workshops and preparing information system acceptance certificates.
Checking operating conditions and operating modes of technical
information system tools is carried out simultaneously with checking the functioning of complexes of tasks (subsystems). The preparedness of the personnel responsible for the operation of the information system is determined in accordance with the training program and job descriptions included in the working project. The results of the inspection are discussed at work meetings and documented in minutes.
The final stage of the commission’s work is the drawing up of an act, which indicates:
1) composition of the commission, positions and places of work of commission members;
2) term (date) of system acceptance;
3) the composition of performers (organizations, enterprises) who took part in the creation of the information system;
4) grounds for acceptance (orders, instructions and
5) list of presented information system documentation
And assessment of its compliance with current regulatory and technical documents;
6) compliance of actually completed and implemented work with technical specifications;
7) readiness of all types of support and structural divisions of the customer for the implementation and operation of the information system;
8) information about the effectiveness of the information system (comparison of existing or expected actual data on the volume and sources of savings obtained with calculated data);
9) conclusions of the commission on the possibility of accepting the information system;
The acceptance certificate in five copies is signed by the chairman and all members of the commission. The date of putting the information system into operation is the date of signing the act by the commission.
6. Information systems development team
Since the creation of a modern information system is a complex process that requires joint efforts large number various specialists, the formation of a team engaged in the design, development and implementation of an information system, in modern conditions becomes very important.
Organization of a team and distribution of work among specialists can be carried out according to several principles:
1) based on the distribution of system analysis (algorithmization) and program development among different teams;
Home / Wires and cablesGOST 34.601-90
Group P87
INTERSTATE STANDARD
INFORMATION TECHNOLOGY
AUTOMATED SYSTEMS
STAGES OF CREATION
Information technology. Set of standards for automated systems. Automated systems. Stages of development
MKS 35.080
OKSTU 0034
Date of introduction 1992-01-01
INFORMATION DATA
1. DEVELOPED AND INTRODUCED by the USSR State Committee for Product Quality Management and Standards
2. APPROVED AND ENTERED INTO EFFECT by Resolution of the USSR State Committee for Product Quality Management and Standards dated December 29, 1990 N 3469
3. INSTEAD GOST 24.601-86, GOST 24.602-86
4. REFERENCE REGULATIVE AND TECHNICAL DOCUMENTS
Item number, application |
|
GOST 19.101-77 | Annex 1 |
GOST 34.201-89 | Annex 1 |
6*. REISSUE. July 2009
________________
*Numbering corresponds to the original. - Database manufacturer's note.
This standard applies to automated systems(AS) used in various types of 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 an AS.
Appendix 1 shows the content of work at each stage.
1. GENERAL PROVISIONS
1. GENERAL PROVISIONS
1.1. The process of creating an AS is a set of works ordered in time, interconnected, combined into stages and phases, the implementation of which is necessary and sufficient to create an AS that meets the specified requirements.
1.2. The stages and phases of creating an AS are distinguished as parts of the creation process for reasons of rational planning and organization of work ending with a given result.
1.3. Work on the development of the AS is carried out according to the stages and steps used to create the AS.
1.4. The composition and rules for performing work at the stages and stages established by this standard are determined in the relevant documentation of organizations involved in the creation of specific types of nuclear power plants.
The list of organizations involved in the creation of nuclear power plants is given in Appendix 2.
2. STAGES AND STAGES OF CREATION OF AS
2.1. Stages and stages of creating an AS in general case are given in the table.
Stages of work |
|
1.1. Inspection of the facility and justification for the need to create a nuclear power plant |
|
1.2. Formation of user requirements for speakers |
|
1.3. Preparation of a report on the work performed and an application for the development of an AS (tactical and technical specifications) |
|
2. Development of the AC concept | 2.1. Studying the object |
2.2. Carrying out the necessary research work |
|
2.3. Development of AC concept options and selection of an AC concept option that meets user requirements |
|
2.4. Drawing up a report on the work performed |
|
3. Terms of reference | 3.1. Development and approval of technical specifications for the creation of nuclear power plants |
4. Draft design | 4.1. Development of preliminary design solutions for the system and its parts |
4.2. Development of documentation for the speaker system and its parts |
|
5.1. Development of design solutions for the system and its parts |
|
5.2. Development of documentation for the speaker system and its parts |
|
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 |
|
5.4. Development of design tasks in adjacent parts of the automation facility project |
|
6. Working documentation | 6.1. Development of working documentation for the system and its parts |
6.2. Development or adaptation of programs |
|
7. Commissioning | 7.1. Preparing the automation object for putting the NPP into operation |
7.2. Personnel training |
|
7.3. Complete set of speakers supplied with products (software and hardware, software and hardware complexes, information products) |
|
7.4. Construction and installation works |
|
7.6. Carrying out preliminary tests |
|
7.7. Conducting trial operation |
|
7.8. Carrying out acceptance tests |
|
8. AC support | 8.1. Carrying out work in accordance with warranty obligations |
8.2. Post-warranty service |
2.2. The stages and milestones performed by organizations participating in the creation of nuclear power plants are established in contracts and technical specifications based on this standard.
It is allowed to exclude the “Sketch Design” stage and individual stages of work at all stages, to combine the “Technical Design” and “Working Documentation” stages into one “Technical Detailed Design” stage. Depending on the specifics of the AS being created and the conditions for their creation, it is allowed to carry out individual stages of work before the completion of previous stages, parallel execution of work stages, or the inclusion of new stages of work.
APPENDIX 1 (for reference). CONTENT OF WORK
ANNEX 1
Information
1. At stage 1.1 “Inspection of the facility and justification of the need to create an NPP”, in the general case, the following is carried out:
Collection of data about the automation object and the types of activities carried out;
Assessing the quality of functioning of the facility and the types of activities carried out, identifying problems that can be solved using automation tools;
Assessment (technical, economic, social, etc.) of the feasibility of creating an NPP.
2. At stage 1.2 “Formation of user requirements for speakers” the following is carried out:
Preparation of initial data for the formation of requirements for the automated system (characteristics of the automation object, description of the requirements for the system, limitations on acceptable costs for development, commissioning and operation, the effect expected from the system, conditions for the creation and operation of the system);
Formulation and registration of user requirements for speakers.
3. At stage 1.3 “Completing a report on the work performed and an application for the development of an AS (tactical and technical specifications)”, a report on the work performed at this stage and an application for the development of an AS (tactical and technical specifications) or another document replacing it are completed with similar content.
4. At stages 2.1 “Study of the object” and 2.2 “Carrying out the necessary research work,” the development organization conducts a detailed study of the automation object and the necessary research work (R&D) related to finding ways and assessing the possibility of implementing user requirements, draws up and approve research reports.
5. At stage 2.3 “Development of options for the AS concept and selection of an option for the AS concept that meets the user’s requirements”, in the general case, alternative options for the concept of the AS being created and plans for their implementation are developed; assessment of the necessary resources for their implementation and maintenance; assessing the advantages and disadvantages of each option; comparison of user requirements and characteristics of the proposed system and selection of the optimal option; determining the procedure for assessing the quality and conditions for accepting the system; assessment of the effects obtained from the system.
6. At stage 2.4 “Preparing a report on the work performed”, prepare and draw up a report containing a description of the work performed at the stage, a description and justification of the proposed version of the system concept.
7. At stage 3.1 “Development and approval of technical specifications for the creation of a nuclear power plant,” the development, execution, coordination and approval of technical specifications for the nuclear power plant and, if necessary, technical specifications for parts of the nuclear power plant are carried out.
8. At stage 4.1 “Development of preliminary design solutions for the system and its parts” the following are determined: the functions of the AS; functions of subsystems, their goals and effects; composition of task complexes and individual tasks; concepts of the information base, its enlarged structure; database management system functions; composition of the computer system; functions and parameters of the main software.
9. At stage 5.1 “Development of design solutions for the system and its parts”, they ensure the development of general solutions for the system and its parts, the functional-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 organizing and maintaining an information base, a system of classification and coding of information, on software.
10. At stages 4.2 and 5.2 “Development of documentation for the NPP and its parts”, the development, execution, coordination and approval of documentation is carried out to the extent necessary to describe the full set of design decisions taken and sufficient for the further implementation of 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 NPPs and (or) technical requirements (technical specifications) for their development” the following is carried out: preparation and execution of documentation for the supply of products for completing NPPs; determination of technical requirements and drawing up 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 facility project,” the development, execution, coordination and approval of design assignments in adjacent parts of the automation facility project are carried out for construction, electrical, sanitary and other preparatory work related to creation of AS.
13. At stage 6.1 “Development of working documentation for the system and its parts,” working documentation is developed containing all the necessary and sufficient information to ensure the implementation of work on putting the NPP into operation and its operation, as well as to maintain the level of operational characteristics (quality) of the system in accordance with the adopted design decisions, its execution, coordination and approval. Types of documents - according to GOST 34.201.
14. At stage 6.2 “Development or adaptation of programs”, programs and software of the system are developed, selection, adaptation and (or) linking of purchased software, development of program documentation in accordance with GOST 19.101.
15. At stage 7.1 “Preparation of the automation object for putting the plant into operation”, work is carried out on the organizational preparation of the automation object for putting the plant into operation, including: implementation of design solutions for the organizational structure of the plant; providing departments of the management facility with instructional and methodological materials; implementation of information classifiers.
16. At stage 7.2 “Personnel training”, personnel are trained and their ability to ensure the functioning of the plant is checked.
17. At the stage “Completing the speakers with supplied products”, they ensure the receipt of serial and individual production components, materials and installation products. Incoming quality control is carried out.
18. At stage 7.4 “Construction and installation work” the following is carried out: work on the construction of specialized buildings (premises) to accommodate technical equipment and NPP personnel; construction cable channels; performing work on the installation of technical equipment and communication lines; testing of installed technical equipment; delivery of technical equipment for commissioning.
19. At stage 7.5 “Commissioning”, they carry out autonomous adjustment of hardware and software, loading information into the database and checking the system for maintaining it; comprehensive setup of all system tools.
20. At stage 7.6 “Conducting preliminary tests” the following is carried out:
Testing the speakers for operability and compliance with technical specifications in accordance with the program and methodology of preliminary tests;
Troubleshooting and making changes to the NPP documentation, including operational documentation in accordance with the test report;
Drawing up a certificate of acceptance of the NPP for trial operation.
21. At stage 7.7 “Conducting trial operation” the following is carried out: trial operation of the NPP; analysis of the results of trial operation of the NPP; modification (if necessary) of the AS software; additional adjustment (if necessary) of NPP technical equipment; execution of a certificate of completion of trial operation.
22. At stage 7.8 “Conducting acceptance tests” the following is carried out:
Tests for compliance with technical specifications in accordance with the acceptance testing program and methodology;
Analysis of AS test results and elimination of deficiencies identified during testing;
Drawing up an act of acceptance of the AS for permanent operation.
23. At stage 8.1 “Performing work in accordance with warranty obligations”, work is carried out to eliminate deficiencies identified during the operation of the NPP during the established warranty periods, and 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;
Determining the reasons for these deviations;
Eliminate identified deficiencies and ensure stability of NPP operational characteristics;
Making the necessary changes to the documentation for the speakers.
APPENDIX 2 (for reference). LIST OF ORGANIZATIONS PARTICIPATING IN THE CREATION OF AU
APPENDIX 2
Information
1. The customer organization (user) for which the NPP is being created and which provides financing, acceptance of work and operation of the NPP, as well as the execution of individual work on the creation of the NPP;
2. A development organization that carries out work on the creation of the AS, 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 AS;
3. A supplier organization that manufactures and supplies software and hardware to the order of the developer or customer;
4. Organization-general designer of the automation facility;
5. Design organizations of various parts of the automation facility project for construction, electrical, sanitary and other preparatory work related to the creation of AS;
6. Construction, installation, commissioning and other organizations.
Notes:
1. Depending on the conditions for creating the NPP, various combinations of functions of the customer, developer, supplier and other organizations involved in the creation of the NPP are possible.
2. The stages and phases of the work they perform to create the AS are determined on the basis of this standard.
Electronic document text
prepared by Kodeks JSC and verified against:
official publication
M.: Standartinform, 2009
Why, in principle, are they needed when designing?
It turns out that GOSTs help the designer himself.
The main problem with design is the lack of design itself. There are certain scraps of thoughts and desires, but without forming them into some kind of holistic picture. This is typical for both beginners and system administrators and beginning systems engineers. There is a certain spontaneity of thinking. By the way, this is also typical for many customers. But they are in a slightly more advantageous position than the performers.
An interesting question arises: who needs all these explanatory notes, technical specifications, etc.? And here’s an interesting answer we get: 85% of documentation is necessary for the performer. The remaining 15% is needed by the customer for some general understanding of what is happening. But the contractor must clearly define both the boundaries of the project and the signs of its implementation. The contractor must be able to protect himself from the chaotic thinking of the customer.
So, let's turn to the developer's GOSTs. We have two main ones: GOST 34th series and GOST 19th series. The 34th series relates to the development of automated systems, and the 19th to software development.
We will talk about GOST 34th series.
There are many different GOSTs in the 34th series. We will be interested in only a few of them. Namely:
1. GOST 34.003-90 Information technology. Set of standards for automated systems. Terms and Definitions
2. GOST 34.601-90 Information technology. Set of standards for automated systems. Automated systems. Stages of creation
3. GOST 34.602-89 Information technology. Set of standards for automated systems. Terms of reference for the creation of an automated system
4. GOST 34.603-92 Information technology. Types of testing of automated systems
5. GOST 34.201-89 Information technology. Set of standards for automated systems. Types, completeness and designation of documents when creating automated systems
6. RD 50-34.698-90 Automated systems. Requirements for the content of documents.
GOSTs are somewhat similar in their hierarchical structure to a catalog. For example, like this Active Directory. It is likely that if you write documentation strictly following GOSTs, then cross-references will allow you to familiarize yourself with a huge number of documents. But what is most important in GOSTs is a clear model “from the general to the specific”. Starting with general phrases, we will get to the very last RJ45 in the system.
And now in more detail. The main GOST, around which there is the so-called. dance is GOST 34.601-90 (Stages of creation). Let's take a closer look at this document.
This is the structure that greets us in this document. What's so great about this? The wonderful thing about this is that we see almost the full life cycle of an automated system. Why almost? Because there is no such stage as decommissioning and disposal. But we don’t really need this. For now, the existing stages are more than enough. Moreover, the recycling stage is considered in one of the other GOSTs, but this is beyond the scope of this article.
As I said above, GOSTs contain cross-references. And to go further in our reasoning, we will take a little look at GOST 34.003-90 (Terms and definitions). It is interested in the definition of an automated system. This is important because we still need to have an idea of what we are going to create.
GOST 34.003-90 in the definition of an automated system tells us the following: automated system; AS: A system consisting of personnel and a set of automation tools for their activities, implementing information technology to perform established functions. Those. in other words, the AC consists of
1. Personnel
2. complex of funds
3. some activity to be automated.
We will also check with GOST 34.003-90
1. a set of automation tools for an automated system; KSA AS: The totality of all components of the AS, with the exception of people
2. user of the automated system; AC user: A person participating in the functioning of the AC or using the results of its functioning
3. operating personnel of the automated system; NPP operating personnel
4. automated system component; component AC: Part of the AC, identified by a certain characteristic or set of characteristics and considered as a whole
So what do we get? But it turns out that we felt some foundation under our feet on which we will rely. We know what the automated system consists of and have clarified that there are two types of personnel: user and operational. And we logically deduce that the component AC, selected according to a certain characteristic, will be t.s. “hardware” and “software”, to put it simply. And the combination of software + hardware will be a complex of automation equipment.
This means that if a customer, for example, says “Install Exchange for me,” then this will not be an AS for one simple reason: at least in such a task there is no type of automated activity. Or maybe the customer doesn’t need Exchange at all. Or maybe he doesn’t need Exchange at all. This means that an inspection of the automation object is required. This means the first stage of GOST 34.601-90 begins (Stages of creation). “Formation of requirements for speakers”
At this stage, GOST requires us to complete several steps. If we translate this into human language, then we must determine whether it is necessary to develop anything at all. Is it advisable from different points of view. In general, assess the need to begin work. The result of the work at this stage is a report that records the result.
Once we have decided with the customer that there are sufficient grounds for development, we can move on to the next stage, “Development of the AC concept.”
In the concept, we need to study the object where implementation is required. If in the first stage we were looking for the reason for creating the speaker system in general (based only on business goals, GOST was simply written when such words were not used), then at the second stage we need to find possible options that meet the customer’s requirements. For example, if the customer wants postal system, then this can be implemented both on Exchange and on Postfix or on anything else. With its pros, cons and development options. A general examination of the facility is carried out and labor costs are preliminarily estimated. We, as performers, are also looking for the most optimal option for ourselves.
After we come to a certain consensus with the customer about which solution option suits him in general terms the most, we move on to, dare I say it, the most important point of the project “Technical Specifications”
The technical specification, if you look at the definition of GOST 34.602-89, is the main document that defines the requirements and procedure for creating (development or modernization - then creation) of an automated system, in accordance with which the development of the AS is carried out and its acceptance upon commissioning.
The technical specification is such an important document that a personal GOST is dedicated to it. Now we will not dwell on this in detail. I will only note that for the correct formation of technical specifications, it is necessary that the stages of GOST 34.601-90 “Formation of requirements for NPP” and “Development of the NPP concept” be completed. The accuracy and correctness of the creation of technical specifications depends on the quality of execution of these stages.
Date of introduction from 01.07.1987
This standard applies to automated systems (AS) used in various types of activities (research, design, management), including their combinations (research - design - management, design - management), created in organizations, associations and enterprises (hereinafter referred to as organizations ).
The standard establishes the stages and stages of the creation and development of AS and the main results of work at each stage.
The standard does not apply to the procedure for developing components used in nuclear power plants.
The procedure for developing supplied systems of automation equipment, hardware, software, etc. is determined by the standards of the system for the development and supply of products and equipment for production, operating in the department of the customer.
The reference book annex provides explanations and some terms used in the standard.
1. GENERAL PROVISIONS
1.1. The creation (development) of an AS is a set of works, ordered in time, mutually related, combined into stages and stages, the implementation of which is necessary and sufficient to create an AS that meets the specified requirements.
1.2. The composition, content and procedure for performing work at the stages and phases established by this standard are determined in the normative and technical documentation for the creation of an NPP of the corresponding type.
2. STAGES AND STAGES OF CREATION OF AUTOMATED SYSTEMS
2.1. The stages and stages of work are shown in the table.
| Stages | Stages of work |
|---|---|
| 1. Research and justification for the creation of the AS | 1.1. Inspection (data collection and analysis) of an automated object, including collection of information about foreign and domestic analogues |
| 1.2. Development and registration of requirements for the system (feasibility study, tactical and technical specifications, application) | |
| 2. Terms of reference | 2.1. Research work* |
| 2.2. Development of preliminary design | |
| 2.3. Development of technical specifications for the NPP as a whole and, if necessary, specific technical specifications for NPP subsystems | |
| 3. Draft design | 3.1. Development of preliminary decisions on the selected AS option and individual types of support |
| 4. Technical design | 4.1. Development of final decisions on system-wide issues, including on AS structures (functional, organizational); procedures (tasks) implemented by the system; process of system operation and, if necessary, issuing specific technical specifications for the development of types of NPP support or types of NPP subsystem support |
| 4.2. Development of solutions for organizational support, including the development of an action plan to prepare for the implementation of AS | |
| 4.3. Development of solutions for technical support | |
| 4.4. Development or selection of algorithms for automated activities | |
| 4.5. Development of solutions for information support | |
| 4.6. Development of solutions for linguistic support | |
| 4.7. Development of software solutions | |
| 4.8. Development of solutions for methodological support | |
| 4.9. Development of design and estimate construction documentation | |
| 4.10. Coordination of decisions on connections between types of support and development of system-wide documentation for the AS as a whole | |
| 4.11. Drawing up custom documentation for supplied components and automation equipment systems or technical specifications for their development | |
| 5. Working documentation | 5.1. Development of working documentation for information support |
| 5.2. Development of working documentation for organizational support | |
| 5.3. Development of working documentation for methodological support | |
| 5.4. Development of working documentation for linguistic support | |
| 5.5. Development or adaptation of programs and program documentation | |
| 5.6. Development of documentation for technical means of one-time production | |
| 5.7. Development of design and estimate construction documentation | |
| 6. Manufacturing of non-serial components of a complex of automation equipment (CAS) | 6.1. Manufacturing of KSA components |
| 6.2. Autonomous debugging and testing of KSA components | |
| 7. Commissioning | 7.1. Preparing the organization for putting the system into operation, training user personnel * |
| 7.2. Construction and installation work * | |
| 7.3. Complete set of speakers * supplied automation equipment complexes, hardware, software, etc. | |
| 7.4. Commissioning * (comprehensive debugging of automated control systems) | |
| 7.5. Conducting trial operation of the NPP | |
| 7.6. Conducting acceptance tests (state, interdepartmental or departmental) | |
| 7.7. Elimination of comments identified during testing of speakers | |
| 7.8. Acceptance of NPPs for commercial operation (introduction of NPPs) |
*Stages may be performed at previous stages depending on the specific development conditions.
2.2. The composition, sequence and timing of the implementation of the stages and stages of work performed during the creation (development) of the AS are established in the technical specifications for the creation (development) of the system from the number of stages and stages given in the table.
2.3. The application of the put into operation AS at similar facilities is carried out by using ready-made design solutions of the developed system and mass-produced components (complexes of automation equipment, software, hardware, etc.) products.
The decision on the possibility of using the AS is made by the commission during acceptance tests of the system.
2.4. When creating (developing) a nuclear power plant, the mandatory stages are: “Technical specifications”, “Technical design”, “Detailed documentation” and “Put into operation”.
For simple systems and systems developed using standard design solutions, combine the “Technical Design” and “Detailed Documentation” stages into one.
2.5. The required steps when creating an AS are: 1.2; 2.3; 4.1-4.5; 4.7; 4.9 - 4.11; 5.1; 5.2; 5.5; 7.1; 7.3 - 7.5; 7.6 and 7.8.
2.6. It is allowed to carry out research work (stage 2.1) at the stage “Research and justification for the creation of nuclear power plants”, and, if necessary, at other stages.
3. RESULTS OF WORK BY STAGE
3.1. The result of the stage “Research and justification for the creation of a nuclear power plant” is a scientific and technical report, tactical and technical specifications, a feasibility study or an application for the creation of a nuclear power plant.
3.2. The result of completing the “Technical specifications” stage is the technical specifications for the creation of the AS.
3.3. The result of the “Sketch Design” stage is a preliminary design.
3.4. The result of work performed at the “Technical Design” stage is a technical design.
3.5. The result of the work performed at the “Working documentation” stage is a set of working documentation for the plant.
3.6. The result of the work performed at the stage “Manufacture of non-serial components of the automated control system” are components of the automated control system that have passed tests in the prescribed manner.
3.7. The result of the work at the “Commissioning” stage is the acceptance of the NPP for commercial operation.
3.9. Development (modernization) or decommissioning of the system is carried out on the basis of decisions made based on the results of an operational analysis.
APPLICATION
InformationTERMS USED IN THE STANDARD AND THEIR EXPLANATIONS
| Term | Explanation |
|---|---|
| Automated system | A system consisting of an interconnected set of organizational units (or a team of specialists) and a set of activity automation tools that implement automated functions for individual types of activities - research, management, testing, etc., or their combinations. |
| Components for speakers | The supplied part of the NPP, which is a component or an interconnected set of components (complex) of one or more types of support, developed in accordance with current regulatory and technical documents, passed state, interdepartmental or departmental tests, accepted for production, manufactured according to duly approved technology, accepted by the technical control (standard control) service of the manufacturer's (supplier's) organization. AC components are products for industrial and technical purposes. |
| Methodological support for AS | Documents that reflect the user’s interaction with a set of automation tools, including a description of the system and subsystems, methodology (technology) for performing automated activities, user instructions |
| Organizational support for the AS | Documents (regulations, job descriptions, staffing schedules, qualification requirements, etc.), establishing the organizational structure, functions and procedure for the interaction of departments with each other during the operation of the plant, including instructions to personnel |
| AC component | An element of one of the types of support (technical, software, information, etc.) that performs a specific function in the AS subsystem and ensures its operation |
The process of creating an AS is a set of works ordered in time, interconnected, combined into stages and phases, the implementation of which is necessary and sufficient to create an AS that meets the specified requirements.
The stages and phases of creating an AS are distinguished as parts of the creation process for reasons of rational planning and organization of work ending with a given result.
Work on the development of the AS is carried out according to the stages and steps used to create the AS.
The composition and rules for performing work at the stages and stages established by this standard are determined in the relevant documentation of organizations involved in the creation of specific types of nuclear power plants.
Stages and stages of work
1. Formation of requirements for speakers
1.1. Inspection of the facility and justification of the need to create an NPP.
1.2. Formation of user requirements for speakers.
1.3. Preparation of a report on the work performed and an application for the development of an AS (tactical and technical specifications)
2. Development of the AC concept.
2.1. Studying the object.
2.2. Carrying out the necessary research work.
2.3. Development of variants of the speaker concept that meets user requirements.
2.4. Drawing up a report on the work performed.
3. Technical specifications.
Development and approval of technical specifications for the creation of nuclear power plants.
4. Draft design.
4.1. Development of preliminary design solutions for the system and its parts.
4.2. Development of documentation for the speaker system and its parts.
5. Technical design.
5.1. Development of design solutions for the system and its parts.
5.2. Development of documentation for the speaker system and its parts.
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.
5.4. Development of design tasks in adjacent parts of the automation facility project.
6. Working documentation.
6.1. Development of working documentation for the system and its parts.
6.2. Development or adaptation of programs.
7. Commissioning.
7.1. Preparing the automation facility for putting the plant into operation.
7.2. Personnel training.
7.3. Complete set of speakers with supplied products (software and hardware, software and hardware systems, information products).
7.4. Construction and installation works.
7.5. Commissioning works.
7.6. Conducting preliminary tests.
7.7. Conducting trial operation.
7.8. Conducting acceptance tests.
8. AC support
8.1. Carrying out work in accordance with warranty obligations.
8.2. Post-warranty service.
GOST 34.602-89 "Technical specifications for the creation of an automated system"
1. GENERAL PROVISIONS
1.1. The technical specification for a nuclear power plant is the main document that defines the requirements and procedure for creating (development or modernization - then creation) of an automated system, in accordance with which the development of the nuclear power plant is carried out and its acceptance upon commissioning.
1.2. Specifications for the NPP are developed for the system as a whole, intended to operate independently or as part of another system.
1.3. Requirements for AS in the scope established by this standard can be included in the design assignment for a newly created automation facility. In this case, technical specifications for the nuclear power plant are not developed.
1.4. The requirements included in the technical specifications for nuclear power plants must correspond to the current level of development of science and technology and not be inferior to similar requirements imposed on the best modern domestic and foreign analogues. The requirements specified in the technical specifications for the NPP should not limit the system developer in the search and implementation of the most effective technical, technical, economic and other solutions.
1.5. Technical specifications for nuclear power plants are developed on the basis of initial data, including those contained in the final documentation of the stage “Research and justification for the creation of nuclear power plants”, established by GOST 24.601.
1.6. The technical specifications for the AS include only those requirements that complement the requirements for systems of this type (ACS, CAD, ASNI, etc.) contained in the current normative and technical documentation, and are determined by the specifics of the specific object for which the system is being created.
1.7. Changes to the technical specifications for the NPP are formalized by an addition or a protocol signed by the customer and developer. The addition or the specified protocol is an integral part of the technical specifications for the NPP. On the title page of the technical specification for the speaker there should be the entry “Valid from...”.
2. COMPOSITION AND CONTENTS
2.1. The technical specification for the NPP contains the following sections, which can be divided into subsections:
2) the purpose and goals of the creation (development) of the system;
3) characteristics of automation objects;
4) system requirements;
5) composition and content of work to create the system;
6) the procedure for control and acceptance of the system;
7) requirements for the composition and content of work to prepare the automation object for putting the system into operation;
8) documentation requirements;
9) sources of development.
Applications may be included in the technical specifications for the speakers.
GOST 34.603-92 "Types of tests"
1. GENERAL PROVISIONS
1.1. Testing of the NPP is carried out at the “Commissioning” stage in accordance with GOST 34.601 in order to verify compliance of the NPP being created with the requirements of the technical specifications (TOR).
1.2. AS testing is a process of checking the performance of specified system functions, determining and verifying compliance with the requirements of technical specifications for the quantitative and (or) qualitative characteristics of the system, identifying and eliminating deficiencies in the system’s operations and in the developed documentation.
1.3. The following main types of tests are established for AS:
a) preliminary;
1) autonomous;
2) complex.
b) trial operation;
Trial operation is carried out in accordance with the program, which indicates:
1) conditions and procedure for the functioning of parts of the NPP and the NPP as a whole;
2) the duration of trial operation, sufficient to verify the correct functioning of the NPP when performing each function of the system and the readiness of personnel to work under the operating conditions of the NPP;
3) the procedure for eliminating deficiencies identified during trial operation.
c) acceptance.
Acceptance tests are carried out in accordance with the program, which indicates:
1) a list of objects allocated in the system for testing and a list of requirements that the objects must meet (with reference to the points of the technical specifications);
2) acceptance criteria for the system and its parts;
3) conditions and timing of testing;
4) means for testing;
5) names of persons responsible for testing;
6) testing methods and processing of their results;
7) list of documentation to be drawn up.
http://www.franklin-grant.ru/ru/technologies/gost.asp
Features of NGOs. Characteristics of control objects.
NGO structure. Levels and management systems of NGOs.
Features of VT in NGOs:
1) Territorial distribution of NGO, VT and NPP facilities.
2) Continuous or discrete-continuous nature of technological processes.
3) Difficult climatic operating conditions and high fire hazard.
4) Low-skilled service personnel.
5) Enterprises in the industry are city-forming.
Enlarged diagram of the relationship between technological complexes of oil and gas production facilities:
Stages of development. Sequence of metasystem transitions:
70s - centralized systems for collecting and processing information based on ES-computers: KIVC\RIVC.
80s - microprocessor technology, new tools (decentralized) appear: SM-computer, TECHNIK, MicroDat.
90s – cluster system, many relatively autonomous subsystems: PC.
2000 – client-server technologies, artificial intelligence technologies, foreign technical solutions.
Nowadays NGOs high level development.
Proprietary concepts and solutions for NGO automation:
1) ERP (Enterprise Resource Planning) – automated control system, automated enterprise resource management system.
2) EAM (Enterprise Asset Management) – AS for managing production capacities and assets.
3) MES (Manufacturing Execution System) – automated control system, operational production management system.
4) SCADA – automated process control system, automated process control system.
PLC – program logic controllers.
DCS – distributed control systems.
The AS is implemented as a sequence of information-related functions, tasks or procedures performed in an automated (interactive) or automatic mode.
Automated technological complexes- a set of technological and software tools necessary for a certain type of production and production processes.
4) development of optimal technological modes;
5) calculation of the necessary material resources and their optimal distribution - equipment;
6) maintaining the maximum balance and analyzing unit costs;
7) analysis of downtime of technological equipment and accounting of losses;
8) automated processing of research results and technological information;
9) maintenance and repair management technological equipment.
At the top level, problem solving is aimed at supporting decision-making by specialists in the changing operating conditions of the enterprise.
Solving these problems is aimed at supporting decision-making at the enterprise (Medium level).
Functionality at the workshop level:
1) collection of information by automation systems of technological objects;
2) creation and maintenance of a database;
3) generation and transmission of information at the enterprise level;
4) monitoring the condition of equipment in technological modes;
5) operational calculations of the effectiveness of the event;
6) diagnostics of the operation of technological equipment and technical automation equipment;
7) maintaining reporting and planning documents.
Solving these problems is aimed at implementing decisions made in the changing operating conditions of the enterprise workshops.
Requirements for self-propelled guns different levels NGO. (drawing)
Technology object level:
(Lower level)
1) collection of information from sensors and automation systems according to regulations;
2) automatic processing and storage of primary information;
3) automatic control and regulation of technical objects (setting regulations);
4) dialogue with the operator technologist;
5) ensuring control of security parameters.
Basic principles for building AS at different levels of the enterprise:
1) Invariance of the performance of functions at each level of control in relation to the number and types of technological objects: the system can be adjusted to specific technical objects, open and supplemented by new functions. Tree of object types => tree of specific objects.
2) Intellectualization of technical and software programs through automation of personnel.
3) Standardization, guaranteed compatibility of the device and software programs and, as a result, reduction in the costs of their operation.
4) The architecture of the complex of those means should ensure the implementation of various configuration systems managed with radial, ring and mixed communication channels, including via wired and radio channel.
Types of AS support. Problems, models and means of integrating automated control systems into NGOs
In general, automated systems consist of software and hardware complexes (PTK), software and methodological complexes (PMK) and technical components. Software and information support.
AS is a set of mutually agreed components and complexes of software, hardware and information support, developed, manufactured and supplied as products for industrial and technical purposes. The joint functioning and interaction of the complexes is carried out on the basis of computer networks.
AS software is a set of programs on storage media with program documentation in accordance with GOST 19.101.
Technical support AS is a set of means for implementing control actions, means for receiving, inputting, preparing, converting, processing, storing registration, displaying, using and transmitting data with design documentation in accordance with GOST 2.102 and operational documentation in accordance with GOST 2.601.
Information Support of AS is a set of system-oriented data describing the dictionary of basic descriptions adopted in the system (classifiers, standard models, automation elements, documentation formats) and updated data on the state of the information model of automation objects (control object, design) at all stages of the life cycle.
Organizational and methodological support for the AS is a set of documents that define the organizational structure of the facility and the automation system, activities under the operating conditions of the system, and forms for presenting the results of activities.
AS software is a set of mathematical methods, models and information processing algorithms used in the operation of the system.
Linguistic support is a set of language tools for constructing and combining information units of KSA.
Decree of the Government of the Russian Federation of July 6, 2015 N 676
"On the requirements for the procedure for creation, development, commissioning, operation and decommissioning of state information systems and further storage of information contained in their databases"
In accordance with Part 6 of Article 14 Federal Law"On information, information technologies and information protection" Government Russian Federation decides:
1. Approve the attached requirements for the procedure for creation, development, commissioning, operation and decommissioning of state information systems and further storage of information contained in their databases.
2. Establish that the activities provided for by the requirements approved by this resolution are carried out by federal executive authorities within the limits of budgetary allocations provided for by the federal law on the federal budget for the corresponding financial year and planning period for leadership and management in the field installed functions.
3. Recommend that other government bodies, in addition to federal executive bodies and executive bodies of constituent entities of the Russian Federation, as well as management bodies of state extra-budgetary funds, local governments, should be guided in their activities by the requirements approved by this resolution.
Requirements
to the procedure for creation, development, commissioning, operation and decommissioning of state information systems and further storage of information contained in their databases
(approved by Decree of the Government of the Russian Federation dated July 6, 2015 N 676)
With changes and additions from:
I. General provisions
1. This document defines the requirements for the procedure for implementing measures for the creation, development, commissioning, operation and decommissioning of state information systems (hereinafter referred to as the system) and the further storage of information contained in their databases, carried out by federal executive authorities and executive authorities authorities of the constituent entities of the Russian Federation (hereinafter referred to as executive authorities) in order to increase the efficiency of the implementation of the powers of executive authorities as a result of the use of information and communication technologies, or executive authorities acting as public partners, and private partners in accordance with public-private partnership agreements (hereinafter referred to as the private partner) in order to implement these agreements.
1.1. When executive authorities or private partners implement measures for the creation, development, commissioning, operation and decommissioning of systems and the further storage of information contained in their databases, the following must be performed:
a) requirements for the protection of information contained in systems established by the federal executive body in the field of security and the federal executive body authorized in the field of countering technical intelligence and technical protection information within the limits of their authority;
b) requirements for the organization and measures to protect information contained in the system;
Information about changes:
Clause 1.1 was supplemented with subclause “c” from April 27, 2019 - Resolution
c) requirements for the protection of personal data provided for in Part 3 of Article 19 of the Federal Law “On Personal Data” (if there is personal data in the system).
Information about changes:
By Decree of the Government of the Russian Federation of May 11, 2017 N 555, the requirements were supplemented with clause 1.2
1.2. In order to fulfill the requirements for the protection of information provided for in paragraph 1.1 of this document (hereinafter referred to as the requirements for the protection of information), executive authorities determine the requirements for the protection of information contained in the system of the executive authority, for which they carry out:
a) determination of information to be protected from unauthorized access, destruction, modification, blocking, copying, provision, distribution, as well as other unlawful actions in relation to such information;
b) analysis of regulations, methodological documents and national standards that the system must comply with;
c) classification of the system in accordance with information security requirements;
d) identification of threats to information security, the implementation of which may lead to a violation of information security in the system, and development on their basis of a model of threats to information security;
e) determination of requirements for the information system (subsystem) for the protection of information contained in the system.
II. Requirements for the procedure for creating a system
2. The basis for creating the system is:
a) the duty of the executive authority to create a system provided for by regulatory legal acts;
b) the decision of the executive authority to create a system in order to ensure the implementation of the powers assigned to it;
Information about changes:
Clause 2 was supplemented with subparagraph “c” from April 27, 2019 - Decree of the Government of Russia of April 11, 2019 N 420
c) decision of the Government of the Russian Federation on the implementation of a public-private partnership project;
Information about changes:
Clause 2 was supplemented with subclause “d” from April 27, 2019 - Decree of the Government of Russia of April 11, 2019 N 420
d) decision of the highest executive body of state power of a constituent entity of the Russian Federation, if the public partner is a constituent entity of the Russian Federation or it is planned to hold a joint competition with the participation of a constituent entity of the Russian Federation (except for cases of holding a joint competition with the participation of the Russian Federation).
3. The creation of the system is carried out in accordance with the terms of reference, taking into account the model of threats to the security of information provided for in subparagraph "d" of paragraph 1.2 of this document, as well as the levels of security of personal data during their processing in personal data information systems, depending on the threats to the security of this data and requirements of this document.
The model of threats to information security and (or) the terms of reference for the creation of a system are agreed upon with the federal executive body in the field of security and the federal executive body authorized in the field of countering technical intelligence and technical protection of information, within the limits of their powers in relation to the implementation of established information protection requirements.
The terms of reference for the creation of the system must include requirements for the protection of information contained in the system, formed in accordance with subparagraphs “a” and “c” of paragraph 1.1 of this document.
4. The terms of reference for the creation of the system and the model of threats to information security are approved by an official of the executive authority who is entrusted with the appropriate powers.
5. The procedure for creating a system includes the following sequentially implemented stages:
a) development of documentation for the system and its parts;
b) development of working documentation for the system and its parts;
c) development or adaptation of software;
d) commissioning works;
e) conducting preliminary tests of the system;
f) conducting trial operation of the system;
g) conducting system acceptance tests.
6. The stage of developing documentation for the system and its parts includes the development, coordination and approval of documentation to the extent necessary to describe the full set of design solutions (including information security) and sufficient for further work on creating the system.
7. The stage of development of working documentation for the system and its parts includes the development, coordination and approval of documentation containing information necessary to carry out work on putting the system into operation and its operation, and the procedure for operating the system containing information necessary to perform work to maintain the level operational characteristics (quality) of the system (including information security) established in the design solutions specified in paragraph 6 of this document, including:
a) a list of actions of employees when performing tasks to operate the system, including the list, types, volumes and frequency of work to ensure the functioning of the system;
b) monitoring the performance of the system and components that ensure information protection;
c) a list of malfunctions that may arise during operation of the system, and recommendations regarding actions when they occur;
d) a list of system operating modes and their characteristics, as well as the procedure and rules for transferring the system from one operating mode to another, indicating the time required for this.
8. The stage of development or adaptation of software includes the development of system software, selection and adaptation of purchased software, as well as, in established cases and procedures, certification of the developed system software and information security tools according to information security requirements.
9. The commissioning stage includes autonomous adjustment of hardware and software of parts of the system, loading information into its database, comprehensive adjustment of hardware and software of the system, including information security tools.
10. The preliminary testing stage includes:
a) development of a program and methodology for preliminary tests, in accordance with which the system is checked for operability and compliance with the technical specifications for its creation;
b) checking the system for operability and compliance with the technical specifications for its creation;
c) eliminating faults identified during such tests and making changes to the documentation and working documentation for the system;
d) drawing up a test report and a certificate of acceptance of the system for trial operation.
11. The trial operation stage includes:
a) development of a program and methodology for trial operation;
b) trial operation of the system in accordance with the program and methodology for trial operation;
c) refinement of the system software and additional adjustment of technical means in case of detection of deficiencies identified during trial operation of the system;
d) execution of a certificate of completion of trial operation, including a list of deficiencies that must be eliminated before the start of operation of the system.
12. The acceptance testing stage includes:
a) testing the system for compliance with the technical specifications for its creation in accordance with the acceptance testing program and methodology;
b) analysis of the results of eliminating the deficiencies specified in the certificate of completion of trial operation;
c) drawing up an act of acceptance of the system into operation.
III. Requirements for the procedure for commissioning the system
13. The basis for putting the system into operation is a legal act of the executive authority on putting the system into operation, defining a list of measures to ensure the putting of the system into operation and establishing a date for the start of operation.
14. The legal act of the executive authority on putting the system into operation includes:
a) measures for the development and approval of organizational and administrative documents defining measures to protect information during operation of the system, the development of which is provided for by regulatory legal acts and methodological documents of the federal executive body in the field of security and the federal executive body authorized in the field of countering technical intelligence and technical information protection, as well as national standards in the field of information security;
b) measures to certify the system according to information protection requirements, as a result of which, in cases established by the legislation of the Russian Federation, the compliance of the protection of information contained in the system with the requirements provided for by the legislation of the Russian Federation on information, information technologies and information protection is confirmed;
c) measures to prepare the executive authority, as well as the private partner in the event of concluding an agreement on public-private partnership, to operate the system;
d) measures to prepare officials of the executive authority, as well as employees of the private partner in the event of concluding a public-private partnership agreement, to operate the system, including persons responsible for ensuring information security.
15. Putting the system into operation is not allowed in the following cases:
a) failure to comply with the information protection requirements established by the legislation of the Russian Federation, including the lack of a valid certificate of compliance with information security requirements;
b) absence in the register of territorial location of control objects, provided for by the Rules for monitoring the placement of technical means of information systems used by state bodies, local governments, state and municipal unitary enterprises, state and municipal institutions, on the territory of the Russian Federation, approved by a resolution of the Government of the Russian Federation dated July 6, 2015 N 675 “On the procedure for monitoring compliance with the requirements provided for in Part 2.1 of Article 13 and Part 6 of Article 14 of the Federal Law “On Information, Information Technologies and Information Protection”, information on the placement of technical means of the information system on the territory Russian Federation;
c) failure to comply with the requirements of this section, identified during the implementation of control in accordance with the Rules for monitoring compliance with the requirements for the procedure for the creation, development, commissioning, operation and decommissioning of state information systems and the further storage of information contained in their databases, approved Decree of the Government of the Russian Federation dated July 6, 2015 N 675 “On the procedure for monitoring compliance with the requirements provided for in Part 2.1 of Article 13 and Part 6 of Article 14 of the Federal Law “On Information, Information Technologies and Information Protection.” of this document. legal act a) preparation of legal acts related to the decommissioning of the system;
b) work on decommissioning the system, including work on uninstalling the system software, exercising rights to the system software, dismantling and decommissioning the system’s hardware, ensuring storage and further use of the system’s information resources;
Information about changes:
By Decree of the Government of the Russian Federation of May 11, 2017 N 555, paragraph 23 was supplemented with subparagraph “c”
c) ensuring the protection of information in accordance with the documentation for the system and organizational and administrative documents on information protection, including archiving of information contained in the system, destruction (erasure) of data and residual information from computer storage media and (or) destruction of computer storage media .
24. Unless otherwise established by regulatory legal acts of the Russian Federation, the storage periods for information contained in the system databases are determined by the executive authority and cannot be less than the storage periods for information that are established for the storage of paper documents containing such information.
25. The deadline for decommissioning the system cannot be earlier than the completion date of the last event provided for by the legal act on decommissioning the system.
THE GOVERNMENT OF MOSCOW
ORDER
On the requirements for commissioning information systems created in the city of Moscow *
Document with changes made:
(Bulletin of the Mayor and Government of Moscow, N 37 (Volume 2), 07/07/2015);
(Bulletin of the Mayor and Government of Moscow, N 57, 10/13/2015);
dated December 5, 2017 N 694-RP (Official website of the Mayor and Government of Moscow www.mos.ru. 12/06/2017);
(Official website of the Mayor and Government of Moscow www.mos.ru, 12/20/2018).
____________________________________________________________________
________________
* Title as amended, put into effect by order of the Moscow Government dated June 30, 2015 N 370-RP..
In order to increase the efficiency of operation of information systems in the city of Moscow:
1. Establish that:
1.1. Executive authorities of the city of Moscow, ensuring the creation of information systems at the expense of the budget of the city of Moscow, organizations subordinate to such executive authorities of the city of Moscow, which, in accordance with legal acts of the city of Moscow, are entrusted with the powers to ensure the creation of information systems (hereinafter also referred to as executive authorities of the city Moscow and organizations providing the creation of information systems), carry out the commissioning of the specified information systems after carrying out acceptance tests confirming the readiness of the information system for commissioning, approval of the information security threat model, as well as the implementation of the necessary measures to protect the information contained in the information system , by drawing up legal acts (local regulations) of the executive authorities of the city of Moscow or organizations ensuring the creation of information systems, respectively (hereinafter referred to as legal acts on the commissioning of information systems) in the form according to the appendix to this order.
by order of the Moscow Government of December 19, 2018 N 891-RP.
1.2. Legal acts on the commissioning of information systems, the creation of which is not provided by the Department information technologies of the city of Moscow, are subject to agreement with the Department of Information Technologies of the city of Moscow. In the course of approval by the Department of Information Technologies of the city of Moscow, additional information about this information system, containing its description and (or) confirming the grounds for its creation, as well as the compliance of the costs of creation, may be requested from the executive authorities of the city of Moscow and organizations providing the creation of information systems information system of the planned cost of work on the development of information systems created in the city of Moscow, determined in accordance with the Methodology for calculating the planned cost of work on the creation, development and modernization of information systems of the city of Moscow, approved by a joint order of the Department of Economic Policy and Development of the City of Moscow and the Department of Information Technologies of the city Moscow.
(Clause as amended, put into effect by order of the Moscow Government dated December 19, 2018 N 891-RP.
1.3. In the event that the use of the information system will be carried out by several executive authorities of the city of Moscow or when using the information system it is planned to interact with residents of the city of Moscow and/or legal entities, an executive body of the city of Moscow that ensures the creation of an information system or carries out the functions and powers of the founder subordinate organization ensuring the creation of an information system, in agreement with the Department of Information Technologies of the city of Moscow, submits in the prescribed manner for consideration by the Moscow Government a draft legal act of the Moscow Government containing regulations on the specified information system, which, among other things, reflects the definition of the information system, its tasks and functions, as well as a list of participants information interaction using the information system and their powers, including the powers to process personal data contained in the information system.
by order of the Moscow Government of December 19, 2018 N 891-RP.
If a legal act of the Moscow Government defines the executive authority of the city of Moscow responsible for organizing the information content of the information system, the powers to organize the processing of personal data contained in the information system, determining the purposes of processing such personal data, as well as the powers of the owner of the information contained in the information system are assigned to the specified executive authority of the city of Moscow. At the same time, the authority to apply technical measures to ensure the security of personal data during their processing in the information system, necessary to fulfill the requirements for the protection of personal data established by the Government of the Russian Federation, is assigned to the operator of the information system.
(Paragraph as amended, put into effect by order of the Moscow Government dated October 6, 2015 N 563-RP.
(Clause 1.3 as amended, put into effect by order of the Moscow Government dated June 30, 2015 N 370-RP.
1.3(1). Measures to protect information contained in information systems implemented by the executive authority of the city of Moscow responsible for organizing the information content of the information system include:
The paragraph is no longer valid - .;
The paragraph has lost force - order of the Moscow Government dated December 19, 2018 N 891-RP.;
The paragraph has lost force - order of the Moscow Government dated December 19, 2018 N 891-RP.;
The paragraph has lost force - order of the Moscow Government dated December 19, 2018 N 891-RP.;
- determination of the degree of possible damage (possible negative consequences) from violation of confidentiality, integrity or availability of information for each type of information;
(Paragraph additionally included by order of the Moscow Government dated December 19, 2018 N 891-RP)
- assessment of the harm that may be caused to subjects of personal data in case of violation of the requirements of the legislation of the Russian Federation in the field of personal data;
(Paragraph additionally included by order of the Moscow Government dated December 19, 2018 N 891-RP)
Determination of requirements for the information system (subsystem) for protecting information contained in the information system.
(Item additionally included)
1.4. If there are no grounds for the adoption of a legal act of the Moscow Government containing a regulation on the information system, the legal act on the commissioning of the information system must be agreed upon with the executive authority of the city of Moscow that ensures the operation of the information system at the expense of the budget of the city of Moscow, or with one subordinate to such to the executive authority of the city of Moscow by the organization (if it is entrusted with the appropriate powers).
(Clause 1.4 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP, by order of the Moscow Government dated October 6, 2015 N 563-RP; as amended by order of the Moscow Government dated December 19, 2018 N 891-RP.
1.5. Access to the information contained in the information system is provided after the information system is put into operation by the information system operator or the organization authorized by it to perform the functions of the information system operator, by:
Free receipt of information not related to restricted access information, unless otherwise established in the regulations on the information system;
Receipt of information by executive authorities of the city of Moscow, organizations subordinate to them, and other organizations, individuals in accordance with the information system regulations;
Obtaining information on the basis of agreements for the use of information resources of the information system, concluded by the operator of the information system or the organization authorized by him to perform the functions of the operator of the information system, with business entities (hereinafter referred to as the agreement for the use of information resources).
(Clause 1.5 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)
1.6. The agreement for the use of information resources is an adhesion agreement and must, among other things, provide for:
List of information systems, information from which must be provided;
Composition of information to which access is provided;
Purposes of providing access to information;
The amount of the fee for providing access to information if the information system operator has not established that access to it is provided free of charge;
Requirements and restrictions on the use of information, including when carrying out activities by an economic entity.
(Clause 1.6 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)
1.7. The information system operator ensures approval of forms of agreements for the use of information resources and their placement on the official website of the information system operator on the information and telecommunications network Internet, conclusion of agreements for the use of information resources and control of their implementation. The specified powers are exercised by the operator of the information system, regardless of whether the legal act of the Moscow Government containing the regulation on the information system specifies an executive authority of the city of Moscow, different from the operator of the information system, responsible for organizing the information content of the information system.
(Clause 1.7 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)
1.8. Under an agreement for the use of information resources, personal data and other information of limited access are not provided, except in cases where such provision is agreed with the subject of personal data or the owner of the information of limited access.
(Clause 1.8 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)
1.9. The legal act of the Moscow Government containing regulations on the information system may establish other features of providing access to information contained in the information system.
(Clause 1.9 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)
2. Entrust control over the implementation of this order to the Minister of the Moscow Government, Head of the Moscow Department of Information Technologies E.A. Lysenko.
(Clause as amended, put into effect by order of the Moscow Government dated December 19, 2018 N 891-RP.
Mayor of Moscow
S.S. Sobyanin
Application. About commissioning
Application
to the order of the Moscow Government
dated July 3, 2012 N 342-RP
(As amended as put into effect
by order of the Moscow Government
dated December 5, 2017 N 694-RP;
in the version put into effect
by order of the Moscow Government
dated December 19, 2018 N 891-RP. -
See previous edition)
About commissioning |
|||||||||||||||
In accordance with | |||||||||||||||
(indicates the legal act of the Moscow Government in accordance with which the information system was created) |
|||||||||||||||
and for the purpose of implementation | |||||||||||||||
(if a legal act of the Moscow Government is adopted containing a regulation on the information system, the name of the corresponding legal act is indicated) |
|||||||||||||||
taking into account the results accepted in the prescribed manner | |||||||||||||||
(the name of the work is indicated - the subject of the contract (agreement) in accordance with which the information system was created) |
|||||||||||||||
produced under the contract (agreement) from | |||||||||||||||
which is confirmed | |||||||||||||||
(indicate the acceptance test report) | |||||||||||||||
1. Accept with | into operation |
||||||||||||||
(indicate the date of commencement of operation of the information system) | |||||||||||||||
(indicate the name of the information system) |
|||||||||||||||
create an information system passport. | |||||||||||||||
(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow) |
|||||||||||||||
based on the information contained in the information system passport, register the information system in the Unified Register of Information Systems and Resources of the City of Moscow. |
|||||||||||||||
(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow) |
|||||||||||||||
ensure the adoption of a legal act of the Moscow Government approving the regulations on the information system. |
|||||||||||||||
5. Establish that the operation of the information system |
|||||||||||||||
provides | |||||||||||||||
(indicate the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow that exercises these powers) | |||||||||||||||
(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow) |
|||||||||||||||
ensure the development and approval of organizational and administrative documents of the executive authorities of the city of Moscow, ensuring the creation of information systems that define measures to protect information during the operation of the information system, the development of which is provided for by regulatory legal acts and methodological documents of the federal executive body in the field of security and the federal body executive power, authorized in the field of countering technical intelligence and technical protection of information, as well as national standards in the field of information protection. |
|||||||||||||||
(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow) |
|||||||||||||||
ensure certification of the information system according to information protection requirements, as a result of which, in cases established by the legislation of the Russian Federation, the compliance of the protection of information contained in the information system with the requirements provided for by the legislation of the Russian Federation on information, information technology and information protection is confirmed. |
|||||||||||||||
(indicate the position, surname and initials of the person who is responsible for preparing officials and workers for operating the information system) |
|||||||||||||||
ensure the training of officials of the executive authority of the city of Moscow (employees of an organization subordinate to the executive authority of the city of Moscow), ensuring the creation of an information system, for the operation of the information system, including persons responsible for ensuring the security of information. |
|||||||||||||||
(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow) |
|||||||||||||||
ensure the preparation of the executive authority of the city of Moscow (an organization subordinate to the executive authority of the city of Moscow), ensuring the creation of the information system, for the operation of the information system. |
|||||||||||||||
10. Monitoring the implementation of this legal act (local normative act) |
|||||||||||||||
assign to | |||||||||||||||
(indicate the position, surname and initials of the person who is entrusted with control over the implementation of the legal act (local normative act) |
|||||||||||||||
Position of the head of the executive authority the city of Moscow or a subordinate authority executive power of the city of Moscow organization | Surname and initials |
||||||||||||||
________________ If the registration of an information system passport and the registration of an information system in the Unified Register of Information Systems and Resources of the City of Moscow is carried out by the same structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow, paragraphs 2 and 3 of this appendix can be combined . |
|||||||||||||||
The clause is included if, on the date of adoption of a legal act of the executive authority of the city of Moscow or a local regulatory act of an organization subordinate to the executive authority of the city of Moscow on the commissioning of an information system, a legal act of the Moscow Government containing a regulation on the information system has not been adopted. The clause is included if there are no grounds for the adoption of a legal act of the Moscow Government containing a provision on the information system. |
|||||||||||||||
Revision of the document taking into account
changes and additions prepared
CJSC "Kodeks"
By Decree of the USSR State Committee on Standards dated May 14, 1980 No. 2101, the introduction date was established
from 01/01/1981
This standard applies to technical documentation for automated control systems (ACS) of all types, developed for all levels of management (except for national ones), and establishes requirements for the content of documents developed at the “Commissioning” stage in accordance with the requirements of GOST 24.101-80
1. GENERAL PROVISIONS
1.1. Documents developed at the “Commissioning” stage are classified as acceptance documentation for the automated control system.
1.2. When drawing up documents for parts of the automated control system, the content of the documents is limited to the framework of the corresponding part of the automated control system.
1.3. Depending on the purpose and specific features of the created automated control systems, it is allowed to include additional information in documents, the content requirements for which are not established by this standard.
2. REQUIREMENTS FOR ACCEPTANCE DOCUMENTATION
2.1. Certificate of completion of work
2.1.1. The document is intended to record the fact of completion of a separate work when creating an automated control system.
2.1.2. The document does not apply to construction, installation and commissioning works.
2.1.3. The document must contain:
- name of the completed work(s);
- a list of representatives of the developer organization and the customer organization who drew up the act;
- date of completion of work;
- name of the document(s) on the basis of which the work was carried out;
- main results of the completed work;
- conclusion about the results of the completed work.
2.2. Certificate of acceptance for trial operation
2.2.1. The document is intended to record the completion of the commissioning of the automated control system as a whole or its parts into trial operation.
2.2.2. The document must contain:
- name of the automated control system (or part thereof) accepted for trial operation and the corresponding control object;
- the composition of the acceptance committee and the basis for its work (name, number and date of approval of the document on the basis of which the commission was created);
- the composition of the functions of the automated control system (or its part) accepted for trial operation;
- a list of components of technical, software, information and organizational support tested during trial operation;
- main results of acceptance into trial operation;
- decision of the commission to accept the automated control system for trial operation.
2.3. Certificate of acceptance for industrial operation
2.3.1. The document is intended to record the fact of putting the automated control system (or part thereof) into commercial operation.
2.3.2. The document must contain:
- name of the control object and the automated control system (or part thereof) accepted for commercial operation;
- information about the status of the acceptance committee (state, interdepartmental, departmental), its composition and the basis for its work;
- period of the commission's work;
- name of the developer organization, co-executing organization and customer organization;
- name of the document on the basis of which the automated control system was developed;
- the composition of the functions of the automated control system (or its part) accepted for commercial operation;
- a list of components of technical, software, information and organizational support accepted for commercial operation;
- list of documents presented to the commission;
- conclusion on the results of trial operation of the automated control system;
- assessment of compliance of the adopted automated control system with the technical specifications for its creation;
- brief characteristics and the main results of the work performed to create an automated control system;
- assessment of the scientific and technical level of the automated control system (based on design data) * ;
- assessment of economic efficiency from the implementation of automated control systems (based on design data) * ;
- decision of the commission;
- recommendations of the commission for further development of the system *.
2.3.3. The “Certificate of Acceptance for Industrial Operation” is accompanied by a program and test reports, minutes of commission meetings, certificates of acceptance into industrial operation of previously accepted parts of the automated control system, and a list of technical means that the commission used when accepting the automated control system. At the discretion of the commission, it is allowed to include additional documents in the application.
2.4. Work schedule
2.4.1. The document establishes a list of works, deadlines and performers of work related to the creation of works.
2.4.2. The document for each work included in the list must contain:
- title of work;
- start and end date of work;
- name of the unit participating in the work;
- name and position of the responsible executor;
- formula for presenting work results.
2.5. Work order
2.5.1. Depending on the stage of work on creating an automated control system, the following types of documents have been established:
- order on the readiness of the management facility for construction and installation work;
- order on the readiness of the control facility to carry out adjustment work;
- order to begin trial operation of the automated control system (its parts);
- order to put into commercial operation the automated control system (its parts).
2.5.2. The document “Order on the readiness of the management facility for construction and installation work” must contain:
- message about the readiness of the management facility to carry out construction and installation work;
- determination of the construction and installation zone;
- procedure for admission to work;
- a list of representatives of the customer organization responsible for the work and safety of the installed equipment;
- list of responsible representatives of construction and installation organizations performing the work.
2.5.3. The document “Order on the readiness of the control object to carry out adjustment work” must contain:
- message about the readiness of the control object to carry out adjustment work;
- list of technical equipment of the automated control system to be adjusted;
- instructions on the procedure for carrying out adjustment work;
- procedure for admission to commissioning work;
- a list of representatives of the customer organization responsible for the commissioning work;
- list of responsible representatives of organizations performing commissioning work;
- instructions on the procedure for eliminating installation errors and the persons responsible for performing this work.
2.5.4. The document “Order on the start of trial operation of the automated control system (its parts)” must contain:
- name of the automated control system as a whole or its parts undergoing trial operation;
- timing of trial operation;
- a list of officials of the customer organization and the developer organization responsible for conducting trial operation;
- list of departments of the customer organization participating in the trial operation.
2.5.5. The document “Order on putting into commercial operation the automated control system (its parts)” must contain:
- the composition of the functions of the automated control system or its parts, hardware and software accepted for commercial operation;
- a list of officials and a list of departments of the customer organization responsible for the operation of the automated control system;
- procedure and timing for introducing new forms of documents (if necessary);
- the procedure and timing for transferring first-time employees to work under the operating conditions of the automated control system.
2.6. Order on the composition of the acceptance committee
The document must contain:
- name of the adopted automated control system as a whole or its parts;
- information about the composition of the commission;
- basis for organizing the commission;
- name of the customer organization;
- name of the developer organization, co-executing organizations;
- purpose and goals of the commission;
- start and end dates of the commission's work;
- instructions on the form for completing the work of the commission.
2.7. Work program
2.7.1. Depending on the content of the work, the following types of documents are established:
- test program;
- pilot operation program;
- work program of the acceptance committee.
2.7.2. The document “Test Program” is intended to determine the procedure and scope of preliminary tests when transferring into trial operation and acceptance tests when transferring automated control systems into commercial operation.
The document must contain:
- the composition of the functions of the automated control system as a whole or its parts to be tested, with reference to the paragraphs of the “Terms of Reference” for the creation of the automatic control system;
- a list of components of technical, software, information and organizational support that are subject to testing;
- procedure for testing individual components of the automated control system and individual functions of the automated control system;
- conditions and timing of testing;
- the procedure for registering tests and identified deficiencies;
- the procedure for eliminating deficiencies and making necessary changes to the technical documentation;
- instructions on the form of presentation of test results.
2.7.2. The document “Trial Operation Program” is intended to determine the procedure and scope of trial operation.
The document must contain:
- the composition of the functions of the automated control system and its parts subject to trial operation, with reference to the clauses of the technical specifications for the creation of the automatic control system;
- a list of components of technical, software, information and organizational support that are subject to trial operation;
- procedure for personnel actions during trial operation of automated control system elements and individual functional subsystems;
- conditions and timing of trial operation;
- the procedure for recording the results of trial operation and identified deficiencies;
- the procedure for eliminating identified deficiencies and making changes to technical documentation;
- instructions on the form for presenting the results of trial operation.
2.7.2. The document “Work Program of the Acceptance Committee” is intended to determine the procedure for accepting the automated control system for commercial operation. The composition and content of the document are determined according to regulatory and technical documents approved in the given industry.
2.8. Test report
2.8.1. The document is intended to record the results of preliminary tests when transferring the automated control system as a whole or its parts into trial or industrial operation.
2.8.2. The document must contain:
- name of the test object;
- list of officials who conducted the test;
- purpose of testing;
- information about the duration of the tests;
- a list of items of the technical specifications for the creation of an automated control system, for compliance with which tests were carried out;
- a list of items of the “Test Program” for which tests were carried out;
- information on the results of observations of the correct functioning of the automated control system;
- information about failures, malfunctions and emergency situations that arose during testing;
- information about adjustments to the parameters of the test object and technical documentation.
2.9. Agreement protocol
2.9.1. The document is intended to coordinate deviations from previously adopted and approved design decisions, when during the trial operation of the automated control system as a whole or its parts, the need for their adjustment was revealed.
2.9.2. The document must contain:
- a list of considered deviations indicating the document, deviations from the requirements of which are subject to approval;
- list of officials who compiled the protocol;
- justification of accepted deviations from design decisions;
- a list of agreed deviations and deadlines for making necessary changes to the technical documentation.
Reissue. May 1986