Initial system setup

Initial system configuration is recommended according to the diagram and steps below.

mceclip2.png

We recommend the following steps to configure QVALON:

1

Create a division

A division is the highest level of organizational structure in the system. Depending on the size of your company, there may be several divisions, but one division will suffice to start using the system.

In a number of cases, the essence of the Division is used to divide the audited facilities by business types or other criteria.

A division consists of several regions. When a division-level auditor is assigned to a certain division, he can create inspections in any store from any region within that division.

2

Create regions

Region is a set of stores included. If a region-level auditor is assigned to a certain region, he can create inspections in any store within that region.

3

Create stores

Store is the object where inspections take place.

4

Create departments

Departments reflect the organizational structure of the company. It is possible to draw an analogy between the system's business areas and the company's departments. For example: HR Department = HR business area, Logistics Department = Logistics business area. Business areas are used to define user permissions. To start working, add users to the existing "Operations" business area (created in the system by default).

5

Create user groups

Groups are unions of selected users that have access to audits and analysis of audit results within the special checklist templates created for each particular group. For example: only users of the "Share Control" group can conduct audits using the "Share Control" checklist template and receive notifications of the audit results. Users that are not added to the corresponding group will not be able to see the assigned checklist template for the group.

6

Create users

User - an employee registered in the system with a certain set of options. Their type and number are set depending on the position and level of the user in the system hierarchy. The user level is set on the "Users" tab and defines the scope of interaction with stores.

7

Create blocks, sub-blocks, processes and questions

Questions are the lower level of the checklist template structure. Questions are combined into processes for a community. The process may be an area of the store, shop floor (women's area, men's area), or a specific operating process (re-evaluation, work with personnel documentation). Processes are combined into sub-blocks, then into blocks. This hierarchy is used in reports and analytics.

8

Create checklist

Before creating checklists, you need to fill in the system library: create a hierarchy of thematic blocks, sub-blocks, processes and questions. Then create a checklist template selecting items from the library. The structure of the checklist template is formed on the "process - question" hierarchy principle. Process sequence in the template structure is determined at your discretion. In the new checklist template, you can add questions from different processes, blocks that are present in the system library. In the checklist template properties, it is necessary to specify the rules of evaluation and sending of notifications about the fact and result of the audit according to the template.

9

Assign the checklist template to a group or department

Before users can work with a checklist template, you should assign it to a group of users or business departments that will be using it. Configure the assignment of checklist templates in the "Inspections -> Checklists Registry" tab by clicking on the desired template and listing groups/departments in the "Assign group of recipients" section.