Report "Performance Evaluation" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. A service (technical) report for analyzing the performance of the information base. It calculates the integral indicator APDEX (Application Performance Index) based on key operations using accumulated measurements of their execution time. It is used by information base administrators, technical support specialists, and maintenance personnel to identify bottlenecks, monitor degradation after updates to the configuration/platform, and justify optimization regulations.

This is not an accounting report: it does not refer to the chart of accounts, accounting registers, and does not operate with amounts of economic transactions. Tax and accounting parameters of the RK (VAT 16%, MRP 4,325 ₸, accounts 1210/3130/6010, etc.) do not apply to this object — they relate to the applied part of the configuration, not to the performance measurement mechanism.

Where to find in 1C: section “Administration” → “Performance Evaluation” (with the corresponding functional option enabled), or directly via the navigation link e1cib/list/Report.PerformanceEvaluation.

2. Attributes, Table Parts, and Settings

2.1 Header Attributes

There are no explicit header attributes in the report's metadata. All user input is implemented through parameters and selections of DCS, stored in the object SettingsComposer. Typical parameters of the composition scheme:

2.2 Table Parts

Static table parts are absent. The output data is dynamically generated by the composition scheme: the result is a table “Key Operation → Measurements → APDEX → Evaluation” with possible grouping by dates/operations.

2.3 Main Layout

The report is based on the main data composition scheme (MainDataCompositionScheme) with pre-configured options (settings) — at least an option for calculating APDEX by key operations and an option for the dynamics of the indicator over time.

3. Forms

No custom forms are defined in the metadata — the report uses the automatically generated report form of DCS of the 1C:Enterprise 8.3 platform:

Working with variants is provided by the “Report Variants” subsystem of LSS (if activated in the configuration), so the list of saved settings is accessible from the report form.

4. Key Module Procedures

The attached evidence does not include the source code (BSL) of the modules. Below are typical handlers for the report in DCS as part of LSS (verify actual signatures with the specific build 3.0.74.2).

Report Object Module:

• ReportSettings(Parameters, ReportSettings) — registration of the report in the “Report Variants” subsystem: description, placement, specific variants, availability of quick selection. Standard integration point of LSS.
• OnResultComposition(DocumentResult, DataDecoding, StandardProcessing) — if custom composition is needed: programmatic refilling of parameters (target time, period), post-processing of the result, calculation/highlighting of the APDEX evaluation. If the procedure is empty — the composition is performed by the platform.

Form Module (if overridden):

• OnCreateOnServer — initialization of default period, target time value T, visibility restriction for users without administration rights.
• OnResultCompositionOnServer / decoding handlers — transition to the detail of measurements of a specific key operation.

APDEX Calculation Logic (implemented in the DCS scheme or in an external module of the subsystem): for each key operation, measurements are classified relative to the threshold T — “satisfied” (time ≤ T), “tolerable” (T < time ≤ 4·T), “unsatisfied” (time > 4·T). Index: APDEX = (N_satisfied + N_tolerable / 2) / N_total. The obtained value (0…1) is compared with the rating: up to 0.5 — unacceptable; 0.5–0.7 — poor; 0.7–0.85 — satisfactory; 0.85–0.94 — good; above 0.94 — excellent.

5. Data Sources, Posting, and Movements

The report is not posted and does not generate movements — like any object of the type “Report”, it does not create entries in the accounting register and records in accumulation/information registers. It works only in read mode.

Data sources (registers/references of the “Performance Evaluation” subsystem of LSS):

Since the report does not relate to the accounting circuit, the standard chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010) and tax parameters (VAT 16%, PIT, social tax, etc.) are not involved here. These attributes appear in applied documents and registers of the configuration, but not in the performance measurement mechanism.

6. Related Objects and Input Based On

• Input based on is not applicable for reports (the “input based on” mechanism is available for documents/references, but not for reports).
• Related objects: reference KeyOperations, information registers TimeMeasurements / TechnologicalTimeMeasurements, common modules of the “Performance Evaluation” subsystem (collection and storage of measurements), “Report Variants” subsystem of LSS (storage and selection of settings).
• Connection with the measurement mechanism: data is filled by the subsystem automatically when the time measurement functional option is enabled; the report only visualizes the accumulated data.

7. Extension Points

• Configuration extension: adding handlers OnResultComposition/OnCreateOnServer through an extension without removing the object from support — for custom visualization, additional groupings, or highlighting critical operations.
• Report variants (DCS): creating custom user/predetermined variants with different groupings, selections by specific key operations and thresholds T without changing the code.
• Composition scheme: extending the scheme with additional fields/calculated resources (for example, percentiles of time, APDEX trend).
• Access rights: restricting the visibility of the report by administration roles — a typical practice for service tools.
• Threshold values T: maintaining the reference KeyOperations (setting target time) — the main “configurable” parameter affecting the result.

Requires verification in the specific build 3.0.74.2: the exact set of predefined report variants and module procedure signatures (they are version-dependent in LSS).