Glossary - HxGN NetWorks - 11.01.2501 - Help - Hexagon

Work Template

A template used for creating an order.

Purpose: Work Template describes the operation to be performed. It contains information on which network object (object class) is to be processed, and how it is processed.

Work Template can specify:

• activities to be carried out

• required number of workers

• required qualifications

• necessary equipment (for example, material)

• time required for each task

Order

An order created from a work template.

Purpose: It describes the tasks to be carried out for a network object.

Besides the specifications from the work template, an order can also specify:

• specific equipment which is to be processed

• date when the order should be executed

• person who is responsible for the order

• person who executes the order

• current state of the request (new, released, published, in progress, and so on)

Task

One or more tasks included in an order.

Purpose: Each task describes a work step in connection with a network object.

Example:

An order of the Maintenance > Electricity systems > Transformer station > Standard - No pre-assignment (Station) type is assigned the following activities, among others:

• pumping out the cellar

• clean high-voltage insulators

• carrying out switchgear maintenance

• leaning/maintaining the transformer station

Task Attribute

One or more task attributes which can be assigned to each Task.

Purpose: In the task attributes, performing employees can add immediate confirmations about the task.

Example:

In the transformer station maintenance, for the task "Cleaning/Maintaining transformer station", the task attributes "Vegetation" and "Remark" are defined. In the "Vegetation" attribute, the executing employee reports the strength of the vegetation on the station. In the attribute "Remarks", the employee can make longer notes on the activity, for example, hints on the further state of the station or problems that have occurred.

The collected data in is then stored in the central database.

Collective Order

Several orders combined.

Purpose: Collective order identifies orders as belonging together, to facilitate special processing steps.

Example:

In the predefined data model of the MWF, collective orders are used to combine several orders from the electricity unit that require a switching operation on the same supply line. As a result, if the respective orders are executed within the shutdown period, this supply line needs to be switched off only once.

You can specify whether collective orders are to be created using a specific work template (marked with the "(S)" in the name of the template). Then, besides generating a (single) order for each selected network object, the system creates a collective order which includes every (individual) order created in this process.

Order Object

An asset or network object assigned to the Order.

Purpose: This is usually a superordinate object.

Example:

A transformer station, which is processed within the scope of the Order. The Order Object also indicates the location where the Order is executed. ,

Task Object

An asset or network object which is assigned to the Task.

Purpose: This can be the Order Object itself, or an object subordinate to the Order Object.

Example:

A transformer station is an Order Object with busbars and taps as subordinate objects.

MWF

Mobile Workforce