This article details the elements making up the screens you use for creating Inspections

Inspection Policies

A policy is used to define who the inspection applies to, the frequency of the inspection and how much notice is to be given before the inspection will occur. A single policy can apply to more than one inspection. 

  1. Inspection Policies – the name of the policy. This is used when establishing the inspection template to identify what policy will apply to the inspection.
  2. Business Unit – is used to qualify which jobs the inspection applies to. 
  3. Region – is used to further qualify which jobs the inspection applies to. 
  4. Cost Code – this is used to restrict the inspection to a particular supplier / trade. If used a frequency must be nominated. 
  5. Frequency – this is used to determine the frequency of the inspection.

Related to Frequency - Inspections will generate on Task Inspections, 7 days before the task they are linked to's Estimated Date. This means the inspection will be available in a timely manner.

Inspection Categories

The categories are used for grouping like questions for reporting purposes. Categories will be assigned to the Inspection questions.

  1. Category – the name given to enable the classification of questions for report grouping purposes.

Inspection Templates

The template describes the detail of the inspection. It identifies the policy that applies to the template, the details of the inspection and what to do if the inspection fails by not meeting the required standard.

  1. Inspection Group – the name of the inspection. 
  2. Business Unit – is used to qualify which business unit the inspection applies to. 
  3. Inspection Policy – the policy to be applied to this template therefore identifying the frequency and applicability of the inspection. 
  4. Fail Action – the action to be taken when an inspection fails. These can be individually or in combination. i.e. Place job on hold and Management Escalation. Options available are:
    1. Place job on hold - The jobs status is changed to On Hold. 
    2. Repeat the Inspection - The Inspection is scheduled again on the same task 
    3. Reschedule the task (that the inspection is associated with). - This is similar to a split task as a new task is created with the inspection attached. 
    4. Management Escalation. - A new task with the inspection attached is created with the supplier resource being the Construction Manager. 
    5. Notify Supplier - An email is sent to the Supplier notifying them of the failure. 
    6. Notify Client Liaison - An email is sent to the Client Liaison notifying them of the failure. 
    7. Notify Central Account - An email is sent to the Central Accounts notifying them of the failure. This requires the System Setting “ClickHome.Inspections.CentralEmailAccount” to have the email address for this notification. 
    8. Notify Construction Manager - An email is sent to the Construction Manager notifying them of the failure. 
    9. Mark Supplier Unavailable - The supplier on the task is made unavailable. If the supplier has already been allocated to a tasks or a purchase order is raised for the supplier it overrides the unavailable status 
    10. If you wish to set specific failure actions please check this link. Failure Actions

  5. Instructions – Instructions to the Supervisor about the inspection that appear on the mobile device. 
  6. Ad Hoc – specifies whether this inspection can be used in an Ad Hoc manner by the supervisor. Ad Hoc inspections are loaded to the Field device for selection.