Two sub-groups of editable data.
Identity
|
Field |
Description |
|
Defect Description |
A concise description of the problem, which can be left as per the Standard Defect it was created from, or can be modified for more accuracy. |
|
Standard Defect |
The Standard Defect that the Defect was created from. When not editing, click to open the Standard Defect. In Edit Mode is a picklist to select a Standard Defect from. |
|
Severity |
In Edit Mode is a picklist to select a Severity from the Standard Defect that the Defect is based on, and the Asset’s Priority. |
|
Severity Score |
From the selected Severity |
|
Asset Priority |
From the Asset. |
|
Due date |
Calculated, based on the selected Severity for the Asset’s Priority. |
Details
|
Field |
Description |
|
Action Category |
A picklist of Action Categories to assign one of, to the Defect, so helping with its categorization for assessment. |
|
Work Required / Monitor |
Check boxes, to determine whether an Action should be created for the Defect now, or whether it can be monitored for deterioration. Due to other work priorities and budget constraints it may not be possible to repair all Defects immediately, so these flags provide a way to filter Defects to a more manageable list. On the next Inspection it may be found that the Defect is worse, so it might then be marked as Work Required. |
|
Element (name of an Element List) |
This picklist provides selection of the part of the Asset, where the Defect is. This picklist is created in the Code Editor in the Elements section, with its Caption appearing as the picklist name e.g. Footpaths, set in the Asset Type Attributes. It means that you can record Defects on different parts of an Asset. |
|
Defect Condition |
A System List used in conjunction with the above checkboxes to help prioritise Defects. |
|
Defect Priority |
A System List to highlight the priority of the Defect. It has been superseded by the Priority functionality of Standard Defects but can still be used, if so desired. |
|
Cost Estimate |
An estimate of the repair cost, to help determine, which defects are repaired first. |
|
Material required |
To record the primary material needed to repair the Defect. |
|
Completion Date |
If the System Option, 'Use latest Completion Date of related Actions for Defect' is ticked, the Defect gets Completion Date from the latest Action Completion Date, when all Actions for it are Complete. If the System Option is not ticked, the Defect gets the earliest Action Completion Date, when all Actions for it are Complete. |
All Defect User Fields, configured in a Defect Attribute Set, are available here.
Used to record any additional information regarding a Defect.
Creating Defects is best done in the field by an Inspector:
•Download an Inspection Program of Assets and existing Inspection records
•During the Asset Inspection process, record Defects, or if there are no Defects, record a “Tag” Inspection on the Asset
•After the Inspection Program is complete, upload it to Conquest
•In Conquest, use a View that displays the newly recorded Defects, to
assess the information from each and establish the priority of work to be done.
Determine the Defects to be repaired, select the Create Action Task for each
Defect to establish the required Actions to complete repairs, or
alternatively, relate the Defect to an existing Action.
Note: The new
Action will be assigned to the lowest level common parent in the Asset
Hierarchy
•Issue the necessary Actions to contractors or works crews for the repairs to be conducted. When finished, return to each Action in Conquest and select the Complete Action Task. All Defects that have been related to that Action will be marked as Complete
When you create a Defect from a Standard Defect, the Defect Description is based on the combined Asset and Standard Defect descriptions. The Standard Defect data is copied to the new Defect, leaving unfilled fields for you to do.
You can create an Ad Hoc Defect, where you do all of the data entry including changing the description from New Defect.