User Defined Incident Data Fields

User Defined Incident data can be edited on either the Incidents Grid or the object Property Sheet.

To view and edit all user defined incident data, use the Property Sheet.

The following describes all the data which can be used to define a user defined incident.

User Defined Incident Data

Database Table Name for user-defined fields: networktype__objectname where:

networktype is the type of network and can take the following values:
- ams - Asset network
- cams - Collection network
- wams - Distribution network
"__" - double underscore
objectname - name of the asset as entered in the Database Name field of the User Defined Objects Dialog.

User defined objects are configured in the User Defined Object Grid. Please refer to the User Defined Object Grid topic for further details.

User defined objects may be assigned:

built-in fields. This is carried out behind the scenes by InfoAsset Manager at object creation or editing time. These default fields are related to the object type and geometry. Built-in fields are listed in the table below.
user defined fields. These user defined fields are specified by the user (this may be permissioned). See User Defined Field Grid for more information.

Show Columns	Database Names
	Size, Type and Units
	Defaults and Error Limits

Field Name

Help Text

Database Field

Data Type

Size

Units

Precision

Default

Error Lower Limit

Error Upper Limit

Warning Lower Limit

Warning Upper Limit

Incident ID

Unique identifier for the incident. The identifier depends on the geometry of the incident.

id for all incident types but points

node_id for points

ds_node_id and us_node_id for links

Text

Asset type

Type of asset associated with the incident.

(To associate the incident with a Collection Network pipe, use the US node ID, DS node ID and Link suffix fields.)

asset_type

Text

100

Asset ID

Asset ID of associated asset.

(To associate the incident with a Collection Network pipe, use the US node ID, DS node ID and Link suffix fields.)

asset_id

Text

US node ID

Applies to Collection Networks.

Upstream node ID of associated pipe.

(Used when incident is associated with a pipe.)

us_node_id

Text

DS node ID

Applies to Collection Networks.

Downstream node ID of associated pipe.

(Used when incident is associated with a pipe.)

ds_node_id

Text

Link suffix

Applies to Collection Networks.

Link suffix of associated pipe.

(Used when incident is associated with a pipe.)

link_suffix

Text

X coordinate

Applies to incidents that are points.

X coordinate of the incident

Double

Y coordinate

Applies to incidents that are points.

Y coordinate of the incident

Double

Elevation

Applies to incidents that are points.

Elevation above datum level (usually sea level) .

elevation

Double

Length

Applies to incidents that are polylines.

Link length

length

Double

Points

Applies to incidents that are polylines.

An array of X/Y values giving the geometry of a line feature.

point_array

Array

Area

Applies to incidents that are polygons.

Polygon area.

Default value is calculated from polygon geometry.

area

Double

Boundary Array

Applies to incidents that are polygons.

An array of X/Y values giving the geometry of a polygon feature.

boundary_array

Array

Location

Address or description of site at which asset is located.

location

Text

100

Team leader

Name or identifier of the team leader in charge of the task:

Database Value	Description
LEAD1	Team Leader 1
LEAD2	Team Leader 2

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

team_leader

Text

Contractor

Name of contractor responsible for carrying out task:

Database Value	Description
CONT1	Contractor 1
CONT2	Contractor 2

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

contractor

Text

Priority

Priority of incident with regards to resolution:

Database Value	Description
L	Low
M	Medium
H	High

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

priority

Text

100

Approval level

Approval level assigned to the scheduled task.

This dropdown list is populated with the Approval Level data entered in the Resource Grid.

approval_level

Text

Approval status

Task approval status:

Database Value	Description
Not required	Not required
Pending	Pending
Approved	Approved
Hold	Hold
Rejected	Rejected

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

approval_status

Text

Work package

Work package the incident is part of.

work_package

Text

Status

Status of incident with regards to resolution:

Database Value	Description
A	Active
V	Verified
R	Resolved
C	Closed

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

status

Text

100

Task phase

Stage of multi-step task:

Database Value	Description
PHASE 1	Phase 1
PHASE 2	Phase 2

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

task_phase

Text

Date reported

Date incident was reported.

date_reported

Date / Time

Report taken by

Database Value	Description
C	Call centre
O	Other

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

who_report_taken_by

Text

Date opened

Date/time when the incident record was created.

Automatically populated when object is created on the GeoPlan.

date_opened

Date / Time

Date inspected

Date incident was inspected.

date_inspected

Date / Time

Inspected by

Database Value	Description
C	Contractor
O	Other

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

who_inspected_by

Text

Resolved

A checked field indicates that the incident has been resolved.

resolved

Boolean

Date resolved

Date incident was resolved.

date_resolved

Date / Time

Resolved by

Database Value	Description
C	Contractor
O	Other

who_resolved_by

Text

Closed

A checked field indicates that the incident has been closed.

closed

Boolean

Date closed

Date/time when the incident was closed.

date_closed

Date / Time

Cause

Description of cause of incident:

Database Value	Description
G	General

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

cause

Text

100

Effect

Description of effect of incident:

Database Value	Description
G	General

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

effect

Text

100

Action

Description of action to be taken:

Database Value	Description
G	General

The options available in the dropdown list depend on the choices defined in the Standards and Choice Lists dialog.

action

Text

100

Resource and Material details

The Resource Details editor is used to define :

Resources with breakdown by hours worked (normal, overtime and double time) showing an estimated and actual cost for carrying out maintenance work (user defined repairs, surveys or incidents) on a selected asset.

The editor can be used to perform resource management calculations.

Quantities and costs of materials required to carry out the related maintenance work, with breakdown by estimated and actual figures for each material.

Resource Details

Database Table Name: user_schedule_fields_cams for collection networks, user_schedule_fields_wams for distribution networks and user_schedule_fields_ams for asset networks

Show Columns	Database Names
	Size, Type and Units
	Defaults and Error Limits

Position in Data Structure	Field Name	Help Text	Database Field	Data Type	Size	Units	Precision	Error Lower Limit
1	Resource ID	Unique identifier for the resource. Any resources already defined are included in the dropdown list.	resource_id	Text	40		0	0
2	Estimated hours	Estimated time in terms of normal hours required to carry out the task.	estimated_hours	Double			2	0
3	Estimated overtime hours	Estimated time in terms of overtime hours required to carry out the task.	estimated_overtime_hours	Double			2	0
4	Estimated double time hours	Estimated time in terms of double time hours required to carry out the task.	estimated_double_time_hours	Double			2	0
5	Estimated cost	The estimated cost of carrying out the task.	estimated_cost	Double		WN_COST	2	0
6	Actual hours	Actual time in terms of normal hours taken to carry out the task.	actual_hours	Double			2	0
7	Actual overtime hours	Actual time in terms of overtime hours taken to carry out the task.	actual_overtime_hours	Double			2	0
8	Actual double time hours	Actual time in terms of double time hours taken to carry out the task.	actual_double_time_hours	Double			2	0
9	Actual cost	The actual cost of carrying out the task.	actual_cost	Double		WN_COST	2	0
10	Actual date	Actual date on which the resource was used.	actual_date	Date/Time			3

Material Details

Database Table Name: user_schedule_fields_cams for collection networks, user_schedule_fields_wams for distribution networks and user_schedule_fields_ams for asset networks

Show Columns	Database Names
	Size, Type and Units
	Defaults and Error Limits

Position in Data Structure	Field Name	Help Text	Database Field	Data Type	Size	Units	Precision	Error Lower Limit
1	Material ID	Unique identifier for the material. Any materials already defined are included in the dropdown list.	material_id	Text	40		0	0
2	Estimated number	Estimated number of items of this material required to perform the task.	estimated_number	Integer			0	0
3	Estimated cost	Estimated cost of the material required to carry out the task.	estimated_cost	Double		WN_COST	2	0
4	Actual number	Number of items of the material actually used to perform the task.	actual_number	Integer			0	0
5	Actual cost	Actual cost of the material used to carry out the task	actual_cost	Double		WN_COST	2	0
6	Actual date	Actual date on which the material was used.	actual_date	Date/Time			3

The Totals section is a container for calculated costs and durations. The fields which comprise this section are described below. See the Resource Management Calculations topic for details on how to perform the calculations.

resource_details

Array

Actual duration

Actual time taken to carry out the task.

May be calculated via the Resource Details editor.

actual_duration

Double

Actual cost

Actual cost of resolving incident.

May be calculated via the Resource Details editor.

actual_cost

Double

WN_COST

Estimated duration

Estimate of time required to carry out the task.

May be calculated via the Resource Details editor.

estimated_duration

Double

Estimated cost

Estimated cost of resolving incident.

May be calculated via the Resource Details editor.

estimated_cost

Double

WN_COST

Approval history

Notes containing the result of the task approval, the names of the approving officers, a user and date stamp as well as any comments that may have been added at approval time, all in read-only mode.

approval_history

Memo