Initial system configuration is recommended according to the diagram and steps below.
We recommend the following steps for configuring MD Audit:
1 |
Division - the highest level of organizational structure in the system. There may be several divisions in the retail network, but there must be at least one. In a number of cases, the essence of the Division is used to divide the audited facilities by business types or other criteria. Division is a set of regions within it. When a Division level auditor is assigned to a certain division, he has access to all the stores that are part of the division's regions for inspection. |
|
2 |
Region is a set of stores included. If a Region level auditor is assigned to a certain region, all the stores included in the region become available for the audit. |
|
3 |
Store is the main object of the system used for the audit. |
|
4 |
Business directions 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 |
Groups - 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 |
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 |
Questions - the lower level of the checklist template structure. Questions are combined into processes for a community. The process is any area of the store, shop floor (women's area, men's area), a specific operating process (revaluation, work with personnel documentation). Processes are combined into sub-blocks, then into blocks. This hierarchy is used for reporting and analysis panels. |
|
8 |
Before creating checklists, you need to fill 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 |
When start working with a checklist template, you should assign it to a group of users or business areas that will use it during the audit. Configure the assignment of the checklist template in the "Checklists Configuration" block menu in the "Assign Recipients Group" tab. |
Comments