Inspections, control works

The document describes, in the form of examples, the management of the periodic inspection process within a given enterprise. Depending on the requirements, the machine park and fixed equipment require periodic inspections and inspections. The system makes it easy to schedule the execution of such activities, keeps track of performance periods and reminds you of deadlines. It also monitors device parameters, e.g. operating hours, and generates inspections based on them. Templates of such performances may contain a series of questions, measurements and tasks to be performed on individual devices. All operations are performed fully digitally on mobile devices, whether by plant employees or external subcontractors

This tutorial requires you to have properly prepared starting data. Inspections are performed on specific resources (devices, machines) or by selecting locations (for virtual inspections). All this data should have been created or imported beforehand. This tutorial does not cover this information and you should refer to the user documentation or other tutorials.

Inspections in the main system are available in a separate section that includes four views related to inspections:

The imported resource structure data contains information about all resources. Here, after selecting the appropriate filters, we get one resource for which we can generate an inspection.

Each resource can have definable parameters. In this case, this resource has several parameters related to the electrical parameters of the device. These parameters can be used during inspections as data to verify the measured measurements. This will be explained with examples in a later step.

In the case of inspections, the measurement device and calibration information are often required in addition to the measurements. We can achieve this by defining a new resource and in its settings specify that it is a measuring device and indicate the date of calibration and other parameters of such a device.

We specify it in the edition of the resource in the "Equipment" tab, indicating that the given resource is equipment and specifying the validation parameters.

After this introduction, we have all the data and facilities available to plan and perform inspections.

First, we define the inspection template. A template is a set of rules and actions to be performed as one set of operations. These elements may result either from normative requirements (national or international standards) or from internal arrangements.

The template is defined in the template view. We create a new template. The template definition window appears. It is divided into several parts separated by tabs.

General information:

Inspection sections allow you to divide questions/measurements into sections, e.g. question/measurement areas.

Questions

A list of questions is a list that builds a checklist consisting of actions that require an answer to a specific question. As in the given example, these can be questions such as "Checking the history of events" with a yes/no answer, but also questions such as "Is the device working properly?" or "Indicate the operating mode of the device", which will contain more than two "yes/no" answers.

The question editor allows you to specify this element. It contains the following fields:

Measurement

The second list of action items in an inspection is a set of measurements. Measurements are clearly elements that must have a numerical answer, i.e. a specific information value. The system allows you to define any number of measurements and then helps in their acquisition during the inspection. We can add/edit/remove measurements from the list and change their display order.

The editor of a particular measurement consists of two sections. General measurement information such as:

The second section contains information that allows you to verify the correctness of the measurement. While entering the measurement during the inspection, the system can verify the correctness of this measurement, additionally facilitating the work of the persons performing the inspection. This allows you to avoid simple errors and mistakes, but it can also indicate a potential problem with the device being inspected.

This section allows you to define and verify check equations.

Tasks

Tasks allow you to define additional activities to be performed during the inspection. Sometimes the employee is expected to perform additional activities during the inspection. These additional steps will be part of the inspection. These can be:

Editing the task template allows you to specify these types of tasks. We can add/edit/delete tasks or change their order.

The task editor allows you to specify the fields and values of a given task. Available properties:

In the case of code scanning, we can additionally specify the type of required identifier. This allows you to force a specific type of identifier even if the device has two types of identifiers - RFID and a printed QR code.

In the case of a photo task, we specify the number of photos and we can mark the flag that at least the given number of photos must be taken. Otherwise, the number will only be a suggestion.

For the Upload files task, we define the same parameters as for photos.

Other

In addition to the inspection template, we can add documentation of the inspection in the form of an editor or a list of attachments, e.g. device manuals with a section on performing this type of inspection.

Summary

After saving the inspection template, we can proceed to the stage of their use. We can do this in two ways. To explicitly and explicitly trigger the execution of a given inspection for specific resources/locations or to specify the rules according to which these inspections should be performed.

The schedule/inspection plan allows you to define rules that will allow you to periodically perform and remind you to perform such activities. Using inspection templates, we defined what should be done. We will use inspection plans to determine when this should be done.

Schedules are defined in the section called Schedules in the main menu. After displaying it, we get a view with several tabs and main actions to be performed.

Importantly, AMAGE/AMAGE24 distinguishes between two types of schedules. Depending on the scope of the review, we use one of them. However, in the end, we perform inspections for a specific device.

Schedule types:

To enable filtering, of course, an additional, detailed filter is available, with which we can additionally filter plans.

For each schedule (after its creation) we also have a context menu available that allows you to perform basic operations.

The inspection plan view is additionally divided into several tabs.

Inspection plan definition

After invoking the action to create an inspection plan, in the first step we indicate which resource or type will be covered by this inspection plan. Next, the plan definition window is displayed, divided into three parts.

The first part is basic data about the plan

The next tab is the definition of the schedule for calling this plan based either on the calendar or on the selected parameter of the resource, e.g. motor hours.

Format parameters:

The last section of the plan definition is identifying those responsible for its implementation.

After defining the template and the plan, we can visualize the deadlines and manage the inspection. We can do this in two ways:

After preparing the plans, we can see the scheduled inspections on the calendars. In the form of a monthly or yearly view.

When you select any day or range of days, a window appears that displays all scheduled inspections for that day. We can perform specific operations on each inspection.

The Execution Schedule shows the audit plan divided into date ranges. Dates are shown - this week, next week, end of month, next month. Inspections according to parameters are grouped separately, e.g. after exceeding the defined operating hours. We can also manually change the date range and display planned (and historical) inspection plans according to the selected range.

We can perform specific operations for each entry.

manual order

We can do it directly from the plan view. We can also trigger the inspection manually. Each of these operations will bring up the inspection execution definition window.

To invoke (add) an inspection execution manually, we can go to the execution view and select one of the inspection invocation actions:

If we choose a virtual type, we must additionally select locations (many) for which inspection plans will be created.

Determination of execution

Whether we call the inspection determination directly from the plans view or manually in the execution view, a window appears in which we can determine who will be responsible.

Here we add:

After determining the execution, the system generates a task in the inspection list assigned to a specific person to perform it. In the plans view, we can view whether a given inspection has been planned and whether it has been performed in accordance with the order.

To perform the inspection, the employee launches the mobile version via the AMAGE Shell application. The app can be configured to use a launchpad with quick action buttons. An example view is shown below.

We go to the inspection list. The view is divided into tabs showing inspections assigned to the logged in person.

Pressing the Filter button displays additional filtering options.

Selecting any inspection will take us to the execution view. In it, we have tabs for questions, measurements, tasks to be performed. Shortcuts allow us to go to attachments, manuals or related service requests (if the module is active).

The view of measuring devices allows you to select equipment defined in the system that will be used for measurements (multimeters, etc.). It will then be displayed in detailed reports.

The summary view allows you to determine the execution status - after that, you can quickly filter out inspections in the main system, which, despite the fact that they are done correctly, have some remarks about devices. Then we add a comment and we can set the next inspection date.

Contractor/contractor signatures allow you to save signatures and include them in reports.

The attachment view allows you to add photos or other files during the inspection.

After inspection, we can view them in the desktop view. Each inspection shows its status, description and execution information. Filters allow you to additionally filter the view.

We can also perform inspections directly from this view. By invoking the Execute action from the pop-up menu, we display a window with the inspection execution, as if we were performing it on a mobile device.

Inspections are carried out completely electronically.

If we have appointed a person responsible for checking the inspection, then that person can perform the check. A window is displayed in which you can accept or reject the execution, modify the comment, enter your signature and protocol number.

Inspection Execution Views allows you to view all inspections with statuses and background information.

By selecting details, we go to the view of detailed data and answers to all checklists and attachments.

To generate a report, we can use a general template and specify which sections should be hidden because, for example, they are not used.

You can customize the report to suit your needs in terms of data and appearance. Refer to other tutorials to do this.

The generated report contains all information as well as captions and photo documentation.

Inspections can be outsourced to third parties. They gain access through a unique token and can perform a given inspection without the need for an account in the system. Refer to the portals user guide for more information.

In this tutorial, we have shown most of the features of the inspection system and how to use them. We obtain fully electronic information flows.