Virtual inspections

The document shows how to perform virtual inspections that group multiple resources within a selected location tree. These inspections can be initiated and performed by employees directly from the mobile interface and then completed with the devices being inspected. The document shows how such an inspection can be prepared and executed with minimal preparation.

In the AMAGE system, we have the ability to create inspections that are related to a specific resource. In the case of construction, these may be devices installed during its implementation, inspection works in accordance with the normative requirements regarding, for example, electrical works, piping works.

However, sometimes there is a need to perform an inspection, acceptance or other checking activity that is not directly related to one specific resource or grouping several resources. An example are partial acceptances in construction works, where they are carried out at stages related to the construction of e.g. a certain level and specific elements of a given type, e.g. window frames, masonry works, etc. such operations.

In this tutorial, we will show you how to perform a partial acceptance of construction work along with recording some key information about this task.

First, we go to the list of inspection executions. There we have a list of all the inspections currently being performed and completed.

We can use the To do and To check buttons to display inspections that are assigned to a given user and require given actions.

However, we want to create a new inspection which will carry out partial acceptance of construction works. Select the (+) Virtual button, which allows you to perform this type of inspection.

A location selection window appears. We select those locations that the given inspection type applies to.

Then the inspection scheduling window appears.

We select an inspection template (previously prepared template), describe the scope, select a responsible and inspector. If we have a work orders module, we can assign an inspection to a given order (groups activities).

After creating an inspection and going into details, we have a view with information about pre-assigned people and the scope of activities - tasks, questions and measurements. Importantly, the inspection statuses are incomplete, i.e. "Completed" - NO, "Checked" - NO, "Report generated" - NO.

If we are talking about a virtual inspection, an additional Resources tab appears for it, in which we can indicate a list of resources that participated/were checked during it.

We can add resources (existing ones only) using the Select button, and exclude resources from inspection with the Disconnect button.

We move on to the execution of the given reception. We do this using a mobile device.

We execute the inspection as a standard solution. We answer questions and take measurements.

Then we move on to the inspection summary. Here we enter general information about the status of the inspection (acceptance) whether it was received without comments or whether there are any necessary works. We can include information about this in the comment. If we want (we have a specific requirement), we fill in electronic signatures.

The result of execution in the main system is as follows. Acceptance is made, measurements completed and photo documentation added.

We can proceed to check and verify this inspection.

If we have designated a reviewer, that reviewer can perform the validation check. This is useful when the actual execution is carried out by a team, subcontractor or other persons. The verifying person is then from the team of the general contractor (system operator). After calling the check option, we fill in the information allowing for further operations on the inspection.

We fill in the protocol number, correct the note, approve and generate our signature. Everything done electronically. IF we mark the check as rejected, this inspection will go to be performed again (with data preservation).

Once approved, we can generate a report. We will use the default report appearance and general view. After selecting the report generation, a window appears that allows you to hide some sections of the report (if they were unused, e.g. measurements). The configuration can be saved for reuse.

The default appearance report generates information and all inspection parameters.

This is a report with a basic look. Job, inspection, contract data is retrieved from the related work order. To customize the look of your report, see the main documentation or report tutorials and report fields documentation.

We can view all the acceptance and activities on the dashboard, which is available directly in the system or provided as a view on the synoptic panel on the site.

During the inspection/acceptance, we can use the service request module to store information about all irregularities and defects.

In the inspection view, the Add button with the service request icon appears. After selecting it, the report form opens and you can add a new report to the list of bugs.

Up to this point, all defects are associated with a specific inspection and are included in the details of that inspection.

Ready. We performed a virtual inspection, i.e. partial acceptance of construction works. We checked the correctness of the implementation and generated final reports. During commissioning, we created several non-conformance reports, which will then be resolved by the responsible teams. Inspection reports were generated with signatures and execution details.