The commissioning of the information system consists of the following stages:

• 1) putting into trial operation of technical means;
• 2) putting the software into trial operation;
• 3) training and certification of personnel;
• 4) conducting trial operation of all components and the system as a whole;
• 5) commissioning and signing of acceptance certificates.

The information system developed by us has the following minimum requirements for the technical characteristics of hardware and software:

• -Single-core processor with a frequency of 2 GHz;
• -Operative memory DDR - 512 MB;
• -video card - any modern one will do;
• -1 GB of hard disk space;
• -monitor, keyboard, mouse;
• -installed operating system Windows 98 / XP / Vista / Seven.

Since OJSC "Kirovenergosbyt" currently has similar databases (our database is a synthesis of 2 existing databases), no special training of personnel is required when introducing a new database.

After entering the enterprise database, it is completely ready for operation.

Operation of the information system

In this work, an attempt was made to simplify the work of users as much as possible with the help of the information system "Accounting for work with clients" of JSC "Kirovenergosbyt". Since the application is replete with tables, it was necessary to develop a convenient system for navigation, search, adding and deleting records, and reporting.

Despite the fact that the application does not require powerful technical characteristics from the computer on which it will be used, the application should not contain an abundance of side elements.

When you start the program "Accounting for work with clients", a form will appear that offers to start working with the data of JSC "Kirovenergosbyt".

If you need data on the debtors of JSC Kirovenergosbyt, then click on "Debtors". A new form "Debtors" will open, with which you can find, add, change or delete the required parameter.

When you click the "Change" button, after clicking on the required row in the table and changing its data, changes in the data of the specified row will be recorded in the table. If you want to add new data to the table, enter the new data in the indicated fields. Then click the "Add" button and the new information will appear in the database. In the "Search" field, you can find the information you need by one or several parameters by entering the data and clicking the "Search" button. Also, by highlighting a line in the table and pressing the "Delete" button from your list, the desired one and all data about it will be deleted. If you want to return to the original form, click "Exit".

On the main form, there are also buttons that open access to data about suppliers ("Suppliers"), about contracts ("Agreements"), about employees ("Employees"), about consumers ("Consumers"). All open forms also contain buttons "Add", "Modify", "Delete", "Search", "Report", "Exit".

If you want to exit the program, then on the main form, you must click the "Exit" button.

The program introduces restrictions on changing the interface, on user access to the buttons "Add", "Change", "Delete", check for compliance of the input data with the table parameters, check for the most complete data entry.

Prospects for the development of the information system

At this stage, the information system we have created is able to take into account the work with clients of OJSC Kirovenergosbyt, with its suppliers, to single out the debtors of the Company into a separate category, which simplifies the search for them. When creating this information system, an attempt was made to combine 2 currently existing databases, which separately take into account debtors and all consumers of the Company.

In the future, new possibilities for creating notifications and warnings for debtors, accounting for services provided in accordance with the contract, accounting elements, the ability to integrate data into 1C: Enterprise, etc. can be added to it.

GOST 24.208-80 Requirements for the content of documents of the "Commissioning" stage

By the decree of the USSR State Committee for Standards dated May 14, 1980 No. 2101, the introduction period 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 national), and sets requirements for the content of documents developed at the stage "Commissioning" in accordance with the requirements of GOST 24.101-80

1. GENERAL PROVISIONS

1.1. Documents developed at the “Commissioning” stage are referred to as acceptance documents for the automated control system.

1.2. When drawing up documents for a part of the ACS, the content of the documents is limited to the framework of the corresponding part of the ACS.

1.3. Depending on the purpose and specific features of the automated control systems being created, it is allowed to include in the documents additional information, the requirements for the content of which are not established by this standard.

2. REQUIREMENTS FOR ACCEPTANCE DOCUMENTATION

2.1. Completion certificate

2.1.1. The document is intended to record the fact of completion of a separate work when creating an ACS.

2.1.2. The document does not apply to construction and 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 have drawn up the act;
• completion date of work;
• name of the document (s) on the basis of which the work was carried out;
• the main results of the completed work;
• conclusion on the results of the completed work.

2.2. Test operation acceptance certificate

2.2.1. The document is intended to record the fact of 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:

• the name of the ACS (or its part) accepted for trial operation and the corresponding control object;
• the composition of the acceptance commission 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 ACS (or its part), accepted for trial operation;
• list of components of technical, software, informational and organizational support, checked during trial operation;
• main results of acceptance into trial operation;
• the decision of the commission on the acceptance of the automated control system for trial operation.

2.3. Industrial operation acceptance certificate

2.3.1. The document is intended to record the fact of putting the ACS (or its part) into industrial operation.

2.3.2. The document must contain:

• the name of the control object and the ACS (or its part) accepted for industrial operation;
• information on the status of the acceptance committee (state, interdepartmental, departmental), its composition and the basis for its work;
• time period of the commission's work;
• the name of the developer organization, the co-executing organization and the customer organization;
• name of the document on the basis of which the ACS was developed;
• the composition of the functions of the ACS (or its part), taken into commercial operation;
• list of components of technical, software, informational and organizational support accepted for industrial operation;
• list of documents submitted to the commission;
• conclusion on the results of trial operation of the automated control system;
• assessment of the conformity of the accepted ACS to the technical specifications for its creation;
• brief characteristics and main results of the work performed on the creation of an automated control system;
• assessment of the scientific and technical level of the ACS (according to design data) *;
• assessment of economic efficiency from the introduction of automated control systems (according to design data) *;
• decision of the commission;
• recommendations of the commission for the further development of the system *.

* Mandatory only upon acceptance of the ACS as a whole.

2.3.3. The program and test reports, minutes of the commission's meetings, acts of acceptance into industrial operation of previously accepted parts of the ACS, a list of technical means used by the commission when accepting the ACS are attached to the "Act of acceptance into industrial operation". 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 works related to the creation of works.

2.4.2. The document for each work included in the list must contain:

• job title;
• start and end date of work;
• the name of the unit participating in the work;
• the name and position of the executive in charge;
• the formula for presenting the results of work.

2.5. Work order

2.5.1. Depending on the stage of work on the creation of an automated control system, the following types of document are established:

• an order on the readiness of the control object for construction and installation work;
• an order on the readiness of the control object for commissioning;
• order to start trial operation of the automated control system (its parts);
• an order to put into commercial operation the automated control system (its parts).

2.5.2. The document "Order on the readiness of the control object for construction and installation works" must contain:

• message about the readiness of the control object to carry out construction and installation works;
• determination of the construction and installation area;
• the procedure for admission to work;
• a list of representatives of the customer organization responsible for the work and the safety of the mounted 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 for commissioning" must contain:

• message about the readiness of the control object for commissioning;
• list of technical means of ACS to be adjusted;
• an indication of the procedure for carrying out adjustment work;
• the procedure for admission to the commissioning;
• a list of representatives of the customer organization responsible for the commissioning;
• list of responsible representatives of organizations performing commissioning work;
• instructions on how to eliminate installation errors and the persons responsible for performing these works.

2.5.4. The document "Order on the start of trial operation of the ACS (its parts)" must contain:

• the name of the ACS as a whole or its parts undergoing trial operation;
• the timing of the trial operation;
• a list of officials of the contracting organization and the development organization responsible for the trial operation;
• list of divisions of the customer organization involved in the trial operation.

2.5.5. The document "Order on the commissioning of the automated control system (its parts)" must contain:

• the composition of the functions of the ACS or its parts, hardware and software, taken into industrial operation;
• a list of officials and a list of divisions of the customer organization responsible for the operation of the automated control system;
• the procedure and terms for the introduction of new forms of documents (if necessary);
• the procedure and terms for transferring the first person to work in the conditions of the functioning of the automated control system.

2.6. Order on the composition of the acceptance committee

The document must contain:

• the name of the accepted ACS as a whole or its parts;
• information on the composition of the commission;
• the basis for the organization of the commission;
• the name of the customer organization;
• name of the developer organization, co-executing organizations;
• the appointment and objectives of the commission;
• terms of commencement and completion of the work of the commission;
• instructions on the form of completion of 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;
• trial 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 to trial operation and acceptance tests when transferring the automated control system to industrial operation.

The document must contain:

• the composition of the functions of the ACS as a whole or its parts to be tested, with reference to the points of the "Terms of Reference" for the creation of the ACS;
• list of components of technical, software, informational and organizational support subject to testing;
• the procedure for testing individual components of the ACS support and individual ACS functions;
• conditions and terms of testing;
• the procedure for registering tests and identified deficiencies;
• the procedure for eliminating deficiencies and making the necessary changes to the technical documentation;
• indication of the form of presentation of test results.

2.7.2. The document "Trial operation program" is intended to determine the order and scope of the trial operation.

The document must contain:

• the composition of the functions of the ACS and its parts subject to trial operation, with reference to the points of the terms of reference for the creation of the ACS;
• list of components of technical, software, informational and organizational support subject to trial operation;
• the procedure for personnel actions during the trial operation of the ACS elements and individual functional subsystems;
• conditions and terms of the trial operation;
• the procedure for registering the results of trial operation and identified deficiencies;
• the procedure for eliminating the identified deficiencies and making changes to the technical documentation;
• an indication of the form of presentation of the results of trial operation.

2.7.2. The document "Program of work of the acceptance committee" is intended to determine the procedure for the acceptance of the automated control system into industrial operation. The composition and content of the document is determined by the regulatory and technical documents approved in this industry.

2.8. Test report

2.8.1. The document is intended to record the results of preliminary tests during the transfer of the ACS as a whole or its parts for trial or industrial operation.

2.8.2. The document must contain:

• name of the test object;
• list of officials who conducted the test;
• the purpose of the tests;
• information about the duration of the tests;
• a list of points of the technical assignment for the creation of an automated control system, for compliance with which the tests were carried out;
• the list of items of the "Test Program" for which the tests were carried out;
• information on the results of monitoring the correct functioning of the ACS;
• information about failures, failures and emergencies that occurred during testing;
• information on adjustments to the parameters of the test object and technical documentation.

2.9. Negotiation protocol

2.9.1. The document is intended to agree on deviations from previously adopted and approved design solutions, when, in the process of experimental operation of the ACS as a whole or its parts, the need for their correction was revealed.

2.9.2. The document must contain:

• a list of considered deviations with an indication of the document, deviations from the requirements of which are subject to approval;
• a list of officials who drew up the protocol;
• justification of accepted deviations from design solutions;
• a list of agreed deviations and the time frame for making the necessary changes to the technical documentation.

Reissue. May 1986

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 NPP tests "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 batch and unit production components, materials and assembly products, 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, the construction of cable channels, the installation of technical equipment and communication lines, the testing of the assembled technical equipment, the delivery of technical equipment for commissioning;

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 of 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 operational 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 an act of completion of 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 the EIS represents a gradual transition from the existing control system to an automated one. 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 system life cycle, 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 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. In 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, in order to check the correctness of all the laid down solutions, the commissioning of a new system is carried out gradually during trial operation by 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 work of the new system on the full volume of real data and in real terms in a control mode, when the results obtained are not used for management, but are compared with the results obtained in the previous system and analyzed.

3. Transition to management based on the results of the new system while keeping the old system in operation 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 successful the development and debugging of the system is. 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 trial 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 the period accumulation of information the largest number of mistakes made when creating an information system will appear. 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 the high cost of automation tools for testing the information system under conditions of multiuser access. Some errors will be difficult to fix as they are design errors. None of the best projects is 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 DBMS technical support service. 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 for restoring 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.

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 on a test case;

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

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 computer 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 draft":

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

2) a 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

The commissioning of an information system and its individual elements is a process of gradual transition from existing management methods to automated management methods.

The commissioning of the information system is organized and carried out by the customer with the participation of the developer and 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 putting the information system into commercial operation.

Commissioning is carried out in stages, starting from the stage of development of the 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 priority of the 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 issue 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 conduct tests of 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 requirements of the customer that have arisen 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 by an additional agreement within the agreed time frame.

With positive results of the trial 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 tests are carried out by a commission of the customer, which includes the development manager and some of the leading developers. 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 task.

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 cognizability of the system by the service personnel, as well as provide the possibility of developing and modernizing programs to increase the duration of their 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. For this, the sequence and scope of each testing in the process of testing is determined to verify the fulfillment of the requirements of the technical task at a minimum 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 specifications to be verified, and the restrictions on the 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 to check 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 concepts of the tested 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 the variety of possible ways of processing, interpreting and evaluating them lead to the fact that the most important factors for processing test results become methods of processing and evaluating results... In accordance with the test methods, automation tools must ensure the completeness of 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) 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 specific 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 design stages to foresee and correctly formulate all the requirements of the technical task. 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 to work together between 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.

The procedure for conducting acceptance tests

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, complexes of tasks (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 members of the commission, experts on specific issues of creating information systems may be involved in acceptance with 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 the prompt solution of organizational issues arising in the process of accepting 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 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 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 that are part of the working project. 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) 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 about 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;

Test operation acceptance certificate is formed according to 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

In this section of the acceptance certificate, the start and end dates 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.

Name of the customer organization, the executing organization and the co-executing organization

The name 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 is 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.

In the process of 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.

The decision of the commission on the acceptance of the AIS into trial operation

The decision of the commission on the possibility or impossibility of accepting the information system for trial operation is presented.

M. V. Kovtun October 2010.