Information system commissioning act. Information Technology Consulting (IT Consulting)

Resolution of the Government of the Russian Federation of July 6, 2015 N 676
"On the requirements for the procedure for the 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 of the Federal Law "On Information, Information Technologies and Information Protection" the Government Russian Federation decides:

1. To approve the attached requirements for the procedure for the creation, development, commissioning, operation and decommissioning of state information systems and further storage of information contained in their databases.

2. To establish that the measures provided for by the requirements approved by this resolution are carried out by the federal executive authorities within the budgetary allocations provided for by the federal law on the federal budget for the corresponding financial year and the planning period for leadership and management in the sphere of established functions.

3. Recommend that other state bodies, in addition to federal executive bodies and executive bodies of the constituent entities of the Russian Federation, as well as state non-budgetary funds management bodies, local self-government bodies, should be guided in their activities by the requirements approved by this resolution.

Requirements
to the procedure for the creation, development, commissioning, operation and decommissioning of state information systems and further storage of information contained in their databases
(approved by the decree of the Government of the Russian Federation of July 6, 2015 N 676)

With changes and additions from:

I. General Provisions

1. This document defines the requirements for the procedure for the implementation of measures for the creation, development, commissioning, operation and decommissioning of state information systems (hereinafter referred to as the system) and further storage of information contained in their databases, carried out by federal executive bodies and executive bodies. the authorities of the constituent entities of the Russian Federation (hereinafter referred to as the executive authorities) in order to increase the efficiency of the implementation of the powers of the executive authorities as a result of the use of information and communication technologies, either by executive authorities acting as public partners and private partners in accordance with agreements on public-private partnerships (hereinafter referred to as a private partner) in order to implement these agreements.

1.1. When the executive authorities or private partners implement measures for the creation, development, commissioning, operation and decommissioning of systems and further storage of information contained in their databases, the following should 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 of information, within the limits of their powers;

b) requirements for the organization and measures to protect the information contained in the system;

Information about changes:

Clause 1.1 is supplemented with sub-clause "c" from April 27, 2019 - Resolution

c) the 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:

Resolution of the Government of the Russian Federation of May 11, 2017 N 555 Requirements 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), the 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 illegal actions in relation to such information;

b) analysis of regulatory legal acts, methodological documents and national standards that the system must comply with;

c) classification of the system in accordance with the requirements for information protection;

d) identification of threats to information security, the implementation of which may lead to a breach of information security in the system, and the development of a model of threats to information security on their basis;

e) determining the requirements for the information system (subsystem) for protecting the information contained in the system.

II. Requirements for the procedure for creating a system

2. The basis for the creation of the system is:

a) the obligation of the executive authority to create the 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 sub-clause "c" from April 27, 2019 - Resolution of the Government of Russia of April 11, 2019 N 420

c) the decision of the Government of the Russian Federation on the implementation of a public-private partnership project;

Information about changes:

Clause 2 is supplemented with sub-clause "d" from April 27, 2019 - Resolution of the Government of Russia of April 11, 2019 N 420

d) the decision of the highest executive body of state power of the constituent entity of the Russian Federation, if the public partner is the constituent entity of the Russian Federation or a joint tender is planned with the participation of the constituent entity of the Russian Federation (except for cases of a joint tender 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 information security threats provided for in subparagraph "d" of paragraph 1.2 of this document, as well as the levels of protection of personal data during their processing in personal data information systems, depending on the threats to the security of these data and requirements of this document.

The model of threats to information security and (or) the terms of reference for the creation of the system are coordinated 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 the part related to the implementation of the established information protection requirements.

The terms of reference for the creation of the system must include the 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 a system and a 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 the system includes the following steps that are sequentially implemented:

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 software;

d) commissioning works;

e) conducting preliminary tests of the system;

f) conducting trial operation of the system;

g) conducting acceptance tests of the system.

6. The stage of development of documentation for the system and its parts includes the development, coordination and approval of documentation in the amount necessary to describe the full set of design solutions (including information security) and sufficient for further work on the creation of 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 carry out work to maintain the level operational characteristics (quality) of the system (including information protection) established in the design solutions specified in paragraph 6 of this document, including:

a) a list of actions of employees when performing tasks for the operation of the system, including a 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 the operation of the system, and recommendations for actions when they occur;

d) a list of operating modes of the system 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 software development or adaptation includes the development of the system software, the selection and adaptation of the purchased software, as well as, in the established cases and procedure, the certification of the developed system software and information security tools in accordance with information security requirements.

9. The stage of commissioning includes autonomous adjustment of hardware and software parts of the system, loading information into its database, complex adjustment of hardware and software of the system, including information security.

10. The stage of preliminary testing 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 terms of reference for its creation;

b) checking the system for operability and compliance with the terms of reference for its creation;

c) elimination of faults identified during such tests and amendments 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 stage of the trial operation includes:

a) development of a program and methodology for trial operation;

b) trial operation of the system in accordance with the program and methodology of trial operation;

c) revision of the system software and additional adjustment of technical means in case of detection of deficiencies identified during the trial operation of the system;

d) registration of an act on the completion of trial operation, including a list of deficiencies that must be eliminated before starting the operation of the system.

12. The stage of acceptance tests includes:

a) testing the system for compliance with the terms of reference for its creation in accordance with the program and methods of acceptance tests;

b) analysis of the results of eliminating the deficiencies specified in the act on the completion of trial operation;

c) registration of an act of acceptance of the system into operation.

III. Requirements for the procedure for putting the system into operation

13. The basis for putting the system into operation is a legal act of the executive authority on putting the system into operation, which defines the list of measures to ensure the system is put into operation and sets the period for starting 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 the 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 protection of information, as well as national standards in the field of information protection;

b) measures for attestation of the system in accordance with information protection requirements, as a result of which, in the 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 on information protection is confirmed;

c) measures to prepare the executive authority, as well as a private partner in the event of an agreement on public-private partnership, to operate the system;

d) measures to train officials of the executive body, as well as employees of the private partner in the event of a public-private partnership agreement for the operation of the system, including those responsible for ensuring the protection of information.

15. Commissioning of the system 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 absence of a valid certificate of compliance with information security requirements;

b) the absence in the register of the territorial location of objects of control provided for by the Rules for exercising control over the placement of technical means of information systems used by state bodies, local self-government bodies, state and municipal unitary enterprises, state and municipal institutions, on the territory of the Russian Federation, approved by the decree of the Government of the Russian Federation of July 6, 2015 N 675 "On the procedure for monitoring compliance with the requirements provided for by 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 information system on the territory of the Russian Federation;

c) failure to comply with the requirements of this section, identified in the course of control in accordance with the Rules for exercising control over compliance with 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, approved Decree of the Government of the Russian Federation of 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 Protection of Information. "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, on exercising rights to the system software, dismantling and writing off the system hardware, ensuring storage and further use information resources systems;

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 for the protection of information, including archiving information contained in the system, destruction (erasure) of data and residual information from machine storage media and (or) destruction of machine storage media ...

24. Unless otherwise established by the regulatory legal acts of the Russian Federation, the storage periods for information contained in the databases of the system are determined by the executive authority and cannot be less than the storage periods for information that are established for storing paper documents containing such information.

25. The period for decommissioning the system cannot be earlier than the expiration date of the last measure provided for by the legal act on the decommissioning of the system.

3) a description of the operator's actions when working with programs (rules for launching programs, the sequence of work, actions in possible non-standard situations, etc.).

Test case description includes a description:

1) the functions and parameters of the software tested by the test case;

2) the composition of the technical means necessary for checking the software in this example;

3) input information;

4) the results of running programs against the test case data;

5) operator actions when checking the program using a test case;

6) test results (control standard) of programs on a test example.

Procedure for transferring software documentation

All programs and instructions, verified by the developer on a test case, are handed over to the customer according to an act certifying their acceptance into trial operation.

The software, instructions and descriptions of algorithms handed over to the customer must comply with the requirements for the composition and content of the working project of the information system. The customer receives programs recorded on magnetic media. The customer provides the developer with magnetic media and machine time necessary for putting the programs into trial operation and duplicating them (if necessary).

Acceptance of a set of tasks (subsystems) for trial operation consists in solving a test case by specially trained customer personnel in the presence of developer representatives, followed by an 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 results of acceptance, a software acceptance certificate for trial operation is signed. Discovered

developer errors in programs and technical documentation are eliminated in the process of putting into trial operation.

Organizational and administrative documentation

The following organizational and administrative documentation is drawn up for the main work carried out at the stage of "Working design":

1) order to carry out work at the stage in accordance with the schedule organizational and technical measures;

2) the schedule of joint work of the contractor and the customer;

3) act of verification on test cases and acceptance into trial operation of work programs;

4) the act of readiness of normative and reference documentation;

5) the act of performing organizational and technical measures to prepare the enterprise for the implementation of the information system.

5.5. Commissioning the information system

Commissioning of the information system and its individual elements is a process of gradual transitions from existing methods control to methods of automated control.

The commissioning of the information system is organized and carried out by the customer with the participation of the developer and the executing organizations. The interaction of the organizations of the customer, developer and co-executors is carried out on the basis of the contractual conditions and the schedule for the delivery of the information system in industrial exploitation.

Commissioning is carried out in stages, starting from the stage of development of a technical design as soon as the working documentation is ready and the commissioning of technical means ensuring the introduction of queues or objects of the information system capable of independent functioning.

You should start 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 the dedicated queue of the information system;

4) the technical means of the information system that were put into operation to ensure the functioning of the implemented task complexes.

Organization of work

Carried out:

1) trial operation of individual tasks and their complexes;

2) acceptance of task complexes for industrial operation;

3) carrying out acceptance tests;

4) acceptance of the system into industrial operation.

The composition and sequence of work are determined by the agreed commissioning schedules, which indicate the composition and timing of the following works:

1) for the construction, installation, commissioning and testing of information system objects from the moment of receipt of working documentation to the commissioning of objects for industrial operation;

2) for trial operation and acceptance tests of task complexes;

3) to ensure the transition from existing management methods

To methods provided by the project of the information system.

At the stage "Putting the information system into operation"

the customer is obliged:

1) end 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 personnel of the enterprise comply with official and technological instructions;

3) put into operation the technical means necessary for the implemented technological process of data processing;

4) issue an order with a schedule for the trial operation of the information system and analyze, together with the developer, the results of trial operation;

5) to complete the trial operation of the complexes of tasks that are part of the information system, and their acceptance into industrial operation;

6) make changes to the organizational structure of the enterprise in accordance with the project of the information system;

7) develop a draft order on the composition of the acceptance committee;

8) develop and agree with the developer of the 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 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) correct technical documentation based on the results of experimental operation of the information system;

2) take part in the development of a draft program for acceptance tests of the information system;

3) carry out methodological guidance and take part in the delivery of tasks (sets of tasks) for industrial operation;

4) participate in the work of the commission for the acceptance of the information system into industrial operation.

Test operation procedure

The beginning of the trial operation of tasks (task complexes), 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. The order is accompanied by the agreement with

the developer is a program of trial operation, which determines the conditions for checking the complexes of tasks, the procedure for checking technical means when solving complexes of tasks (subsystems) and the procedure for eliminating the shortcomings identified during trial operation.

Additional customer requirements arising in the process of trial operation, which are not provided for in the terms of reference and technical design, are not grounds for a negative assessment of the results of trial operation and can be satisfied according to additional agreement within the agreed time frame.

At positive results experimental operation of tasks (subsystems), a bilateral act on their acceptance into industrial operation is drawn up.

After the acceptance of the information system into industrial operation, the customer bears responsibility for its functioning within the scope of the accepted complexes of tasks and means.

Initial and reporting documents during testing of information system software

Joint testing is carried out by a commission of the customer, in which the development manager and some of the leading developers participate. The test commission is guided by the following documents:

1) by the approved customer and agreed with the developer terms of reference for the creation of an information system;

2) current state and industry standards for the design and testing of software and technical documentation;

3) test program for all the requirements of technical

4) test methods for each section of the requirements of the technical assignment.

Test program, methods of their implementation and evaluation

results are developed jointly by the customer and the developer and must be agreed and approved. They contain clarifications of the requirements of the technical specifications for a given system and must ensure their correct verification. System documentation should

fully comply with the tested programs, ensure the system's cognizability by the service personnel, as well as provide the possibility of development and modernization of programs to increase their duration life cycle.

Test program Is a plan for a series of experiments. It is developed from the standpoint of minimizing the amount of testing given the reliability of the results obtained and agreed with the customer. To do this, the sequence and scope of each testing in the testing process is determined to verify the fulfillment of the requirements of the technical task at minimal cost. It is especially difficult to choose a set of stressful situations in the functioning of the system, in which the tests should be carried out. Test program should contain the following clearly formulated 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 basic requirements of the technical assignment to be verified, and the restrictions on testing;

3) actually test program containing a check of the completeness of the developed system in accordance with the terms of reference and a test plan for checking the functioning of programs in all sections of the terms of reference and additional requirements formalized by separate solutions;

4) test procedures, unambiguously defining all the concepts of verified characteristics, testing conditions, means used for testing, methods of processing and evaluating test results for each section of the test program.

Large amount of heterogeneous test data

software, and variety possible ways their processing, interpretation and evaluation lead to the fact that critical factors to process test results become methods of processing and evaluating the results... In accordance with the test methods, automation tools must ensure the completeness of the performance checks for each section of the methods and the development

verification protocols according to the points of the test program. The complexity of the software and the close relationship between its various characteristics lead to the need for a careful formulation of all testing conditions and the values of the parameters under which the verification should 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 assignment, according to which the test is carried out;

2) an indication of the methods in accordance with which the tests were carried out, processing and evaluation of the results;

3) test conditions and characteristics of the original

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 task.

The protocols for the entire program are summarized in an act, resulting in

a conclusion is made on the compliance of the system with the customer's requirements and on the completion of the work with a positive or negative result. If all the requirements of the technical assignment 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 at the initial stages of design to foresee and correctly formulate all the requirements of the technical assignment. Therefore, during debugging and testing, it is often revealed that some requirements of the technical assignment are not fulfilled and sometimes even fundamentally cannot be fulfilled with the most conscientious attitude to this on the part of the developer. In this case, it is necessary joint work the customer and the developer in search of a compromise solution when completing tests and drawing up a conclusion. Some shortcomings of the complex of programs during the testing process are only registered and recorded in the plan for eliminating the comments of the commission,

who conducted the tests. This plan is an annex to the test results act and allows you to separate subsequent modifications from direct tests.

Acceptance test procedure

The customer is responsible for organizing and carrying out acceptance into industrial operation. The acceptance of the information system for industrial operation is carried out upon completion of the acceptance by the customer of all complexes of tasks (subsystems) for industrial operation.

Tasks, task complexes (subsystems) and technical means of the information system that are not provided for in the terms of reference, but implemented by the customer independently, can be included in the complex of the information system being handed over only by agreement with the developer and after making appropriate changes to the terms of reference 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 creating information systems can be involved in acceptance with the right of an advisory vote. The customer is obliged to ensure the normal working conditions of the commission in accordance with the accepted acceptance program of the information system. For prompt decision organizational issues arising in the process of accepting the information system, by order of the head of the developer organization, a responsible representative is allocated from the developer organization.

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 consideration and approval. The program indicates: the name of the information system being handed over, 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 on its appointment, purpose, objects, volume, location and

sequence of tests, test procedure and evaluation of results.

The customer prepares together with the developer and transfers the following documents for temporary use to the commission:

1) orders, orders, plans, contracts providing for the creation of an information system;

2) technical and economic justification, terms of reference, technical design, working design of the information system;

3) acts of consideration and approval of the technical project;

4) bilateral acts of the customer and the developer on the delivery of tasks, task complexes (subsystems), devices and their complexes for industrial operation in accordance with the approved terms of reference.

The acceptance committee provides:

1) checking the documentation and the functioning of the information system;

2) organization of working groups and distribution of responsibilities among members of the commission to check individual subsystems;

3) checking the calculation of the economic efficiency of the created information system;

4) organization of workshops and preparation of acceptance certificates for the information system.

Checking the operating conditions and operating mode of technical

means of the information system is carried out simultaneously with checking the functioning of the task complexes (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 draft. The results of the check are discussed at workshops and documented in minutes.

The final stage of the commission's work is the drawing up of an act, which indicates:

1) the composition of the commission, positions and places of work of the members of the commission;

2) the term (date) of acceptance of the system;

3) the composition of the executors (organizations, enterprises) who took part in the creation of the information system;

4) grounds for acceptance (orders, instructions and

5) list of submitted documentation of the information system

and assessment of its compliance with current regulatory and technical documents;

6) compliance of the actually performed and implemented works with the terms of reference;

7) readiness of all types of support and structural divisions of the customer for the implementation and operation of the information system;

8) information on the effectiveness of the information system (comparison of the available or expected actual data on the volume and sources of the resulting savings with the 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. Team of developers of information systems

Since the creation of a modern information system is a complex process that requires the joint efforts of a large number of different specialists, the formation of a team engaged in the design, development and implementation of an information system becomes very important in modern conditions.

The organization of the team and the distribution of work by specialists can be carried out according to several principles:

1) based on the distribution of system analysis (algorithmization) and the development of programs for different teams;

APPROVED

Deputy Director of the Department of State Regulation in the Economy

Ministry of Economic Development of the Russian Federation
______________ V.N. Rudenko
« 09 » _ November __ 2011

PUTTING INTO EXPERIMENTAL OPERATION

Automated information system for project management, developed under the state contract dated November 7, 2011 No. GK-158-OF / D01.
In accordance with the joint decision of the Customer (Ministry of Economic Development of Russia) and the Contractor (OTR 2000 LLC) to put it into trial operation.

Commission consisting of:

Chairman of the Commission:

Deputy Director of the Department of State Regulation in the Economy V.N. Rudenko,

Commission members:

S.V. Pushhakov, Acting Head of the Electronic Society Development Division of the Department of State Regulation in the Economy,

Department Advisor methodological support organization of interdepartmental interaction of the Department of State Regulation in the Economy A.V. Matveenko,

Leading consultant of the e-society development department of the Department of State Regulation in Economy N.N. Kirsanova,

Head of the direction of LLC "OTR 2000" A.I. Kuleshova,

O.V., Project Manager of OTR 2000 LLC Strakhova,

Leading analyst of OTR 2000 LLC Yu.M. Gudkova,

Researcher of the "Real Sector" direction of the IEP named after E.T. Gaidar E.R. Batarshin.
since "_ 08 _" November 2011 by "_ 09 _" November 2011 conducted preliminary tests of the applied software of the automated information system "Project Management Portal" (AIS PPU), installed in the Ministry of Economic Development of Russia.

The preliminary tests were found to have been successfully completed.

The main stages of development were carried out in accordance with the Terms of Reference.
Developed by the documentation meets the requirements exploitation software tools.
The software is prepared for trial operation.

The list of functions accepted for trial operation (section "Requirements for functions performed by the system" of the technical task):
1. Maintaining a list of projects.
2. Working with design entities.
3. Working with indicators to assess the state of work on the project.
4. Analytical module.
5. Document library.

The list of documents provided to the commission required for the trial operation:
1. "Description of AIS" Project Management Portal "" (Passport of the system);
2. "Instructions for the administrator of the AIS PPU";
3. "User manual for AIS PPU";
4. "Program and methodology for testing AIS PPU";
5. "Test tasks for AIS PPU";
6. "A role-based instruction describing the procedure for working with AIS PPU as a project management tool" Interdepartmental interaction "".
Commission decision: To accept the software for trial operation from November 9, 2011.

APPLICATIONS:

Preliminary test report No. 1
Preliminary test report No. 2

Commission members:

V.N. Rudenko

S.V. Pushchakov

A.V. Matveenko

N.N. Kirsanova

A.I. Kuleshov

O.V. Strakhova

Yu.M. Gudkova

E.R. Batarshin

The procedure for putting the EIS into operation.

TYPICAL AUTOMATED DESIGN. STAGE OF COMMISSIONING.

LECTURE 10.

According to GOST 34.601-90 “AS. Stages of creation "and GOST 34.603-92" Types of tests of the AU "As part of the stage of putting the system into operation, the following works are carried out:

1) organizational preparation of the automation object for putting the IS into operation - implementation of design solutions for the organizational structure, provision of subdivisions of the object of management with instructional and methodological materials, introduction of information classifiers;

2) staff training - training of personnel and verification of their ability to ensure the functioning of the IS;

3) IC equipment with supplied products (in the case of the need for such a delivery described in the TOR) - receipt of serial and single-production components, materials and assembly products, conducting incoming quality control;

4) construction and installation work - carrying out work on the construction of specialized premises for the placement of technical equipment and IS personnel, construction cable channels, installation of technical means and communication lines, testing of installed technical means, delivery of technical means for carrying out commissioning works;

5) commissioning works - autonomous adjustment of hardware and software, loading information into the database and checking its maintenance, complex adjustment of all system facilities;

6) preliminary tests - testing the IS for operability and compliance with the terms of reference in accordance with the program and methodology of preliminary tests; elimination of malfunctions and amendments to the documentation on the IC, including the operational one in accordance with the test report; registration of the certificate of acceptance of the IS for trial operation;

7) trial operation - trial operation of IS; analysis of its results; completion of the IS software; additional adjustment of technical means of IS; registration of the certificate of completion of the trial operation.

8) acceptance tests - tests for compliance with the technical specifications in accordance with the program and methodology of acceptance tests; analysis of IC test results and elimination of deficiencies identified during testing; registration of an act of acceptance of IP into permanent operation.

The commissioning of an EIS represents a gradual transition from the existing system management to automated. At the same time, not only the degree of use of technical means for data processing increases, but also the management methods themselves change accordingly.

In accordance with the spiral model of the life cycle of a system starting from the stage of technical design, EIS subsystems, task complexes or individual components, capable of independent functioning, are put into operation in stages, as soon as the working documentation and technical means are ready.

The commissioning stage includes pilot operation of task complexes and their acceptance into industrial operation after acceptance tests. The entire system is taken into commercial operation after the completion of the acceptance into operation of all complexes of tasks.

One of the important features of putting the system into operation is the presence of a certain period during which the parallel operation of the existing system and the new EIS is carried out. V technical systems one device is replaced by another most often sequentially in time. Sometimes a new machine is installed in place of the old one - in this case, neither the new nor the old equipment works for some time. If the new comes into operation before the old stops working, then they work independently of each other. When commissioning an EIS of an organizational type, it is fundamentally impossible for a situation in which neither the old nor the new system worked for at least a short time. Moreover, to check the correctness of all the laid down solutions, commissioning new system is carried out gradually during trial operation in the following steps:

1. Checking a subsystem or a complex of tasks on the full volume of real data, but not in the real time required for control.

2. The operation of the new system on the full volume of real data and in real terms in the control mode, when the results obtained are not used for management, but are compared with the results obtained in the old system, and are analyzed.

3. Transition to management based on the results of the new system while keeping in work old system in case of possible failures and unforeseen situations.

4. Final transition to the work of the new system.

The parallel operation of the system is extremely unfavorable for employees. They have to do double work with increased stress. System developers should strive to reduce the period of parallel work, which essentially depends on how successfully the development and debugging of the system is carried out. It is unacceptable to transfer at least part of the debugging and debugging of the system for the period of trial operation. Changes during this period are inevitable, however, one should strive to ensure that only those remain that could not have been foreseen before the start of experimental operation.

The trial operation overlaps the testing process. As a rule, the system is not fully commissioned, gradually. Therefore, from the point of view of the content of the system, commissioning goes through at least three phases:

2) accumulation of information;

3) reaching the design capacity.

initiates a rather narrow range of errors - mainly data mismatch problems during loading and loaders' own errors, that is, something that was not tracked on the test data. If debugging "on live" data is impossible, then you will have to simulate the situation, and quickly. This requires very qualified testers.

During accumulation of information will manifest the largest number mistakes made when creating an information system. As a rule, these are errors related to multiuser access. Such errors are often overlooked during the testing phase. This is apparently due to the complexity of modeling, as well as to the high cost of automation tools for testing information systems under conditions of multiuser access. Some errors will be difficult to fix as they are design errors. None of the most good project not immune from them. This means that, just in case, you need to reserve time for localization and correction of such errors.

During the period of information accumulation, one may encounter the famous "base fell". In the worst case scenario, it turns out that the DBMS cannot withstand the flow of information. If it is good, the configuration parameters are simply incorrect. The first case is dangerous, since it is quite difficult to influence the manufacturer of the DBMS, and the customer really does not like links to the service technical support DBMS. It is not the manufacturer who will have to solve the problem of DBMS failure, but you - to change the scheme, reduce the flow of requests, change the requests themselves; in general, there are many options. It is good if the time to restore the database fits into the planned time of the project.

The system reaches its design capacity at successful coincidence of circumstances - this is the correction of a number of minor mistakes, and occasionally - serious mistakes.

Acceptance certificate for trial operation is formed based on the results of preliminary tests and includes: conclusions drawn from the results of complex tests; assignments for trial operation.

The time period of the commission

V this section of the acceptance certificate, the dates of the beginning and end of the work of the acceptance committee for conducting preliminary tests are given.

The beginning of the tests - November 01, 2010.
End of testing - December 31, 2010.
The total duration of the tests is 44 working days.

The name of the contracting authority, the executing organization and the co-executing organization

The names of the organizations of the participants in the tests and those who made up the certificate of acceptance of the information system into trial operation are given.

Organization-customer - JSC "Customer".
Executing organization - JSC "Executor".
Organization-co-executor - LLC "Co-executor" (if any).

The composition of the AIS functions accepted for trial operation

The list of the AIS functions accepted for trial operation is listed. Functions can be transferred both system-wide and by subsystems. The functions are taken from the section "Requirements for the functions performed by the system" of the technical assignment for the creation of an information system.

List of components of technical, software, informational and organizational support checked during trial operation

This section of the acceptance certificate provides a list of tests carried out during trial operation. The list of tests is taken from the "Scope of tests" section of the Test Program.

During trial operation, the tests presented in the table below should be carried out.

List of documents to be submitted to the commission

This section of the acceptance certificate provides a list of the documents provided to the commission, necessary for the trial operation.

Instructions for the formation and maintenance of a database (data set), version 1 of 12.09.2010.
- User manual, version 1 dated 09/14/2010.
- ...

Assessment of the conformity of the accepted AIS to the technical specifications

An assessment of the compliance of the accepted AIS with the technical specifications is given.

Based on the results of preliminary tests, the System meets the requirements presented in the document: "". Version 1.0.

The main results of acceptance into trial operation

This section of the acceptance certificate lists the main results obtained from the results of the experimental operation of the information system.

Based on the results of the trial operation, the following main results should be obtained:
- The system is operational;
- Subsystems of the System - interact;
- The system meets the requirements of the document "Terms of reference for the creation of an automated system." Version 1.0 .;
- All characteristics to be assessed are within acceptable limits.