1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | KeyOperationProfiles |
| Full Name | Catalog.KeyOperationProfiles |
| Synonym | not set (—) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Subsystem | “Performance Management”, supplied as part of BSP |
| Hierarchy | none |
| Owner | none |
Purpose. The catalog stores sets (profiles) of key operations of the system with specified target (normative) execution times and priorities for each operation. It is used by the performance management subsystem to monitor the speed of critical operations performed by users. The administrator or performance manager creates profiles that include typical operations (document processing, report generation, etc.) and sets standards for them. The catalog is not used frequently — mainly during system setup and when reviewing target indicators. This is a service (technological) catalog, which has no relation to accounting and taxation.
Where to find. Section “Administration” → “Performance Management” → “Key Operation Profiles”.
Navigation link: e1cib/list/Catalog.KeyOperationProfiles
2. Header Attributes and Table Parts
2.1 Header Attributes
The catalog does not contain its own header attributes, apart from standard system ones.
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Name | String | Mandatory | Profile name (for example, “Accountant Profile”, “Standard Warehouse Operations”) |
| Code | String | Optional | Unique profile code for identification |
2.2 Table Part “KeyOperationsProfile”
The only table part. Contains a list of key operations included in the profile, with standards.
| Name | Type | Purpose |
|---|---|---|
| KeyOperation | Catalog.KeyOperations |
Reference to a specific key operation of the system (for example, “Document Processing Sale of Goods”, “Report Generation Turnover Balance Sheet”) |
| TargetTime | Number (xs:decimal) | Target (normative) time for operation execution in seconds. If the actual time exceeds the target, the operation is considered ineffective |
| Priority | Number (xs:decimal) | Priority of the operation in the profile (the higher the value, the more important the operation). Used for calculating integral performance indicators of the profile |
3. Forms
The catalog contains three forms.
| Form | Purpose |
|---|---|
| ElementForm | Main form for editing the profile. Contains a name field and a table part with a list of operations. Has commands for loading/saving the profile from/to a file, auto-filling, and sorting operations |
| ListForm | Form for viewing and selecting profiles. Standard table form with search |
| SelectForm | Form for selecting a profile when picking from other objects. Similar to the list form, optimized for selection mode |
4. Key Module Procedures
BSL-evidence for this object is not attached. Below are typical handlers characteristic of the catalog of the “Performance Management” subsystem. Specific names/signatures should be clarified according to version code 3.0.74.2.
Form Module ElementForm
OnCreateOnServer— initial setup of the form, availability of load/save profile commands, visibility settings for table part columns.LoadProfileFromFile/SaveProfileToFile— import/export commands for the profile composition to a file (usually XML/JSON) for transferring between databases.AutoFillOperations— command to fill the table part with key operations (for example, all registered in the system or by template).SortOperations— ordering of table part rows by priority/name of operation.- Table part event handlers (
KeyOperationsProfileOnChange, checking for duplicates of operations within the profile).
Object Module / Manager Module
CheckFillingHandler— control of filling the name and correctness of valuesTargetTime/Priority(non-negative numbers), absence of duplicates of key operations.- Procedures/functions of the manager module for obtaining the default profile and reading standards, used by the subsystem when analyzing time measurements.
5. Processing and Movements
The catalog is not a document and does not participate in processing: it does not generate accounting entries and does not make movements in accounting, accumulation, or calculation registers. This is normal for a service catalog of the performance subsystem.
Accordingly, the accounts of the typical chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010), VAT/ESF/SNT registers, as well as tax norms of 2026 (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, basic deduction for PIT 30 MRP/month, etc.) have no relation to this object and are not used by it.
The data of the catalog is used only for reading: the performance management subsystem compares actual time measurements of operations (information register of measurements) with target time from the active profile and calculates performance indicators. The catalog itself does not generate any register records when an element is recorded (except for the standard record of the catalog element itself).
6. Related Objects and Input Based On
| Object | Relation |
|---|---|
Catalog.KeyOperations |
Source of values for the KeyOperation attribute of the table part |
| Information register of time measurements of key operations | Stores actual measurements; compared with profile standards during analysis |
| Reports/processings of the “Performance Management” subsystem | Consumers of profile data for calculating integral indicators and generating reports |
| Constant/setting of the active profile | Determines which profile is used as a benchmark during evaluation |
Input based on for this catalog is not provided (it is neither a source nor a receiver of the “Input Based On” mechanism). The exchange of profile composition is performed through load/save commands in the element form.
7. Extension Points
- Configuration Extension. Adding header attributes (for example, “Responsible”, “Effective From”) or columns to the table part (comment, operation category) without removing the object from support.
- Form Handlers. Redefining/extending
OnCreateOnServerand auto-fill/sort commands in the extension of theElementFormfor custom logic of filling the profile. - Filling Check. Adding
CheckFillingHandlerwith custom rules (ranges of target time, mandatory priority). - Programming Interface. Wrappers in common modules for reading profile standards from external code (integration with custom performance analytics).
- Event Subscriptions.
OnRecord/BeforeRecordof the catalog element for logging changes in standards.