1C: Corporate Instrumental Packet (1S:KIP)

1C: A corporate Instrumental Packet (1S:KIP) - the tool intended for performance improvement, scalability and reliability of the information systems working at the 1C:Enterprise 8 platform.

According to the statement of developers, the product is most useful at implementation of rather large corporate information systems which are characterized by a heavy load on a system and a large number of jobs.

"The corporate instrumental packet" can be used as independently (for example, for assessment of applicability of any standard configuration for solving of tasks of the client), and as the additional tool promoting quality improvement of work of the implemented or operating system.

Screenshot of a window of a product, (2014)

The main objectives solved through "1C: Corporate instrumental packet 8":

• carrying out multi-user overload tests without participation of real users;
• assessment of applicability of a system in the set conditions;
• assessment of scalability of a system;
• choice of the server hardware and software;
• receiving objective (numerical) performance measures of a system during its overload tests or working operation;
• collecting and information storage about dynamics of system performance in time;
• search and analysis of bottlenecks and code optimization of a system:
  • collecting of the complete information about all performance concerns which are available in a multi-user system;
  • ranging of problems on extent of their influence on system performance in general;
  • providing a complete context of each problem at all levels of functioning of a system for the purposes of the further analysis and optimization;
  • ensuring timely and correct accomplishment of all necessary procedural procedures;

• the automated functional testing of configurations.

Structure of a product

• Command center performance;
• Test center;
• Standard load test;
• Quality supervisory center;
• Scenario testing.

Command center performance

"Command Center Performance" (CCP) – the instrument of monitoring and performance review of information systems on 1C: Enterprise platform 8.

TsUP is intended for assessment of system performance, the analysis of bottlenecks of a system and its optimization.

Main objectives:

• The analysis and integrated assessment of the current performance of the working multi-user information system:
  • As a system works?

• Whether * there Are performance concerns?
• Whether * It is possible to increase performance?
• Collecting and information storage about dynamics of system performance:
  • As system performance changed eventually?
  • As system performance at introduction of any changes changed?

• Search and the analysis of "bottlenecks" in the code of a configuration. Obtaining the detailed technical information about all performance concerns which are available in a system for the purpose of further optimization:
  • What performance concerns are available in a system and as far as they are serious?
  • What problems should be solved first of all?
  • B than specifically consists each problem?
  • What objects of metadata and code line of a configuration should be optimized to solve this problem?

These tasks can be solved as for model of an information system in which activity is emulated through the Test center, and for a system in which real users work.

Test center

The test center – the instrument of automation of multi-user overload tests of information systems on 1C: Enterprise platform 8. With its help it is possible to model work of the enterprise without participation of real users that allows to solve problems:

• Reveal problems of reliability and performance of an information system without participation of real users:
  • the problems of multi-user work connected with blocking;
  • problems of stability of system operation at a high load;

• Estimate performance of an information system or its separate parts at the set model parameters of the enterprise on purpose:
  • estimates of applicability of an information system in the set conditions;
  • formulations of operational requirements;

• Estimate scalability of an information system at change:
  • volume of information base;
  • the number of at the same time working users;
  • loads of a system;

• Estimate changes of performance measures at change:
  • functionality of a system (completion of a system or separate algorithms);
  • equipment configurations.

Standard load test

The standard load test is intended for assessment of performance of set of the server hardware and the software in "standard users of "1C: Enterprise". The main scope of this test – the choice of a configuration of a server part of a system for the purposes of specific implementation.

The standard load test represents information base "1C: Enterprise 8.2" with the configuration based on "Management of manufacturing enterprise". The configuration is merged into "Test center 2.0" which structure includes one test script.

The test script includes business process emulation of "sale in management of manufacturing plants", namely: creation of several different documents, report generation and other applied actions. The test works in the mode of complete parallelism, i.e. each user works with own unique data, and expectations on blocking do not arise. The user executes one full stroke of sale a minute.

The scenario automatically increases the number of at the same time working users until performance of their work does not become unsatisfactory. Performance is estimated by a technique of APDEX, proceeding from target time of T = 15 seconds on one full stroke of sale. System performance is considered satisfactory at APDEX values> = 0.85.

The maximum number of users at which system performance still was satisfactory is the end result of work of the test – system performance assessment in "conditional users of "1C: Enterprise". The standard load test estimates performance to within 10 standard users of "1C: Enterprise".

Quality supervisory center

The quality of system operation is its compliance to business requirements of the automated enterprise which consists of such indicators as system performance, its scalability and stability.

The quality of system operation depends on a set of factors behind which constant control is a difficult task. In other words, to provide high quality of system operation, it is necessary to execute (or periodically to perform) some difficult enrollment of operations, each of which has the specifics. For example, operation can be performed with a certain frequency, consist of the difficult sequence of transactions, demand use of special tools or a certain qualification from responsible and so on.

Each of such actions in terms of Supervisory center of quality is called the procedural procedure. Respectively, the Supervisory center of quality is intended for quality improvement of system operation due to ensuring timely and correct maintenance of a system – i.e., behind accomplishment of all procedural procedures.

The supervisory center of quality solves problems:

• allows to store the detailed description of all program and hardware components of a system (destination objects of procedural procedures);
• automatically provides the list of all procedural procedures which it is necessary to perform works of each destination object for high-quality providing;
• provides detailed recommendations about the current actions which are necessary for system operation quality improvement;
• allows to distribute responsibility for accomplishment of separate tasks within each procedural procedure between users of a system;
• automatically notifies users of a system on need of accomplishment of tasks within the procedural procedures;
• provides detailed information on techniques of accomplishment of each procedural procedure;
• displays quality of system operation at each its level, proceeding from information obtained at accomplishment of procedural procedures.

Scenario testing

The tool is intended for automation of scenario testing of any system configurations 1C: Enterprise.

The scenario of the test describes an operations procedure of the user with data in the program. The purpose of such testing – to check whether the program correctly works at input in it the user of different economic transactions. So the logic of the test is described by rules of reflection of economic transactions in the program according to the user documentation. For example, it is possible to write the test for correctness of reflection of transactions of wholesale, the chain of documents in this case should include goods receipt on a warehouse, registration of the invoice, sales of goods to the buyer, the statement of accompanying documents.

The tool can be used also for functional testing, i.e. check of separate functions of the program. Printing of the goods issue slip, substitution of the basic agreement after input of the partner, calculation of the amount according to the price and quantity, filling of a table part of the document by the Fill button and others can be examples of such functions.

Use of "Corporate instrumental packet"

"1C: The corporate instrumental packet 8" can be used at all stages of a system lifecycle:

• design;
• system development or its completion in use;
• implementation, working operation and technical support;

Design

If the implemented system is under construction on the basis of standard configuration 1C (for example, "Management of manufacturing enterprise"), then by means of "A corporate instrumental packet" at a design stage it is possible to solve problems:

• Search of possible "bottlenecks" and their optimization. Detect and analyze bottlenecks in a configuration which can lead to the fact that system performance will be below necessary level. For the solution of this task the Test center, standard test scripts and Command center are used by performance.
• Equipment selection. What equipment is necessary to provide sufficient system performance at the set loading parameters? For the solution of this task the Standard load test is used.
• Assessment of applicability of a standard configuration under the set conditions. Whether there will be a solution to work in the conditions of this enterprise (with these business processes given by parameters of loading and on this equipment) with an acceptable performance? For the solution of this task the Test center and standard test scripts is used.
• Assessment of scalability of a system based on a standard configuration. As system performance with growth of loading (connected, for example, with business growth) will change. What ultimate load at which performance measures will remain primlemy. For the solution of this task the Test center and standard test scripts is also used.

System development or its completion in use

At a development stage (or completions) the Corporate Instrumental Packet systems can be used for quality control of the developed source code. Control should be exercised in two independent directions:

• Control of functional correctness of the developed code. It is necessary to provide high stability and correctness of work of the source code, i.e. absence in it functional errors. For the solution of this task it is necessary to execute regular functional testing by means of the Scenario Testing tool in development process. The test set should be replenished in process of expansion of functionality of the solution.
• Control of optimality of the code in terms of system performance. It is necessary to guarantee the set performance of system operation which is in development process or making changes. For the solution of this task it is necessary to organize regular stress testing with change control of performance (through the Test center), and also the analysis of the arising problems and code optimization (by means of Command center performance).

Implementation, working operation and technical support

During working operation of the Corporate Instrumental Packet system it can be used for solving of tasks:

• Obtaining the objective information about system performance. What objective system performance in each timepoint? Whether exist in the system of a performance concern? This problem is solved by means of Command center by performance.
• Analysis of bottlenecks of a system and its optimization. Analysis of problems of insufficient system performance. These problems are also solved by means of Command center by performance.
• Ensuring timely and correct system maintenance by means of "Quality supervisory center".
• Assessment of effect of change of any operating conditions of a system. As system performance at change of any operating conditions will change: configuration changes of the equipment, transition to the new version of DBMS or 1C: Enterprise, etc. This problem is solved through the Test center and standard test scripts.