Inspections are built into the ClickHome Construction module and processes. It is used to guide the Supervisor or other personnel through specific areas and check for potential issues.
An inspection can be initiated in 4 different ways.
This is configured in the template for the callsheet and is used to conduct a specific type of inspection when certain work is completed in the construction process. eg a Frame inspection after the frame is installed, or a quality inspection after fixing carpenter has finished. This only needs the most simplistic policy, We always ignore resource code and frequency in the Policy.
When the task gets near to being scheduled, ClickHome will create one of these inspections automatically and link it to the task matching the callsheet template where you linked it. Task Inspections are generated and sent to field devices 7 days before the Estimated Date of the Task they are linked to. This ensures they are available in a timely manner.
This is designed to enforce WHS (OH&S) with your trades. Frequency set for this is usually a long one such as 3 months or 6 months. You need a resource code for this. Every time a resource (trade or supplier) for a task matching that resource code is scheduled or called up, the system checks to see when the last inspection for that resource was done and if it exceeds the frequency. Then a matching inspection is attached to this task. This is like Just in Time inspections for WHS. If you don't use a trade for 6 months due to workload, the supervisor will be prompted to conduct the inspection such as make sure his insurance and certificates are still current etc.
This is created by a supervisor on the iPad . So long as the inspection template is marked adhoc – we do it irrespective of supplier, resource code, business unit, region or even frequency.
Job or Safety Inspection
This requires a more detailed policy. The resource code in the policy can be blank, but the frequency needs to be populated. ClickHome evaluates all jobs and makes sure there is one of these inspections created every period determined by your frequency and it makes a new task on the callsheet to link to the inspection. For every (eg 2 weeks) new task that is added to the callsheet, the inspection is created and linked to the task. This is often used to conduct routine site safety inspections.
Designing an Inspection Process
The inspection process can be initiated in a number of ways as described above, but the questions and the types of valid answers are what the Supervisor sees, and what can be reported on.
Questions can be repeated for a number of areas, or can be configured to a single area such as Internal, External or simply Site. Areas must be setup separately. Each question can be configured to accept one of the following range values.
- Yes (1) , No (0)
- Zero to Ten (0 to 10)
- Zero to One Thousand (0 to 1000)
- Yes (1), No (0), NA (2)
- Fail Below - If the answer to the question is not sufficient, then the entire inspection fails
- Comment Below - If the answer to the question is not sufficient, then force the supervisor to enter comments.
- Photo Below - If the answer to the question is not sufficient, then force the supervisor to take a photo.