Anomaly Actions¶
An anomaly may have one or more anomaly actions associated with it. Anomaly actions can be assigned to individuals or teams or departments and may have a “due by” date.
Anomaly actions are not necessarily inspection type actions (e.g. Confirm WT reading). The Anomaly actions functionality can be used as a reminder to initiate a study with a vendor, or to have a discussion with an OIE about access.
Properties of an Anomaly Action¶
| Field Name | Description |
|---|---|
| Anomaly | This is the name of the anomaly that this action belongs to. To change the anomaly that the action is assigned to, click on the  button to the right. |
| Name | A short (50 character limit) name for the anomaly action. |
| Status | Optionally select a status for the anomaly action. This list is user-definable and you can add/edit/delete statuses by clicking on the button on the right hand side of the Status input control. |
| Reference No. | Used to reference (or cross reference) number. The number may relate to a Work Order number in your Planned Maintenance System. |
| Action Type | Choose from a list of pre-defined action types. Typical action types may include “[EVENT] - UT Reading”, “[ENGINEERING ASSESSMENT]”, or “[TEMPORARY REPAIR]”, however this list is user-definable and you can add/edit/delete action types by clicking on the button on the right hand side of the Action Type input control. |
| Created At | Enter the date that the anomaly action is created. This will default to today’s date, but is editable thereafter. |
| Created By | Select the name of the person creating the anomaly action. This will default to the currently logged in user, but is changeable thereafter. |
| Action Before | Enter a date that the anomaly action should be completed by. |
| Assigned To | Select the name of an individual or department that is responsible for progressing or completing the Anomaly Action. |
| Completed At | Enter the date that the anomaly action was completed. Please note that an anomaly action is not deemed “completed” until there is a valid date entered in this field. |
| Percent Complete | Enter a value between 0 and 100. This is for reporting and information purposes only. |
| Comments | A large free text field to retain additional information about the Anomaly Action which may not already be captured in the properties of the anomaly action. |
| Is Tasked? | This field shows whether this action has had a task assigned to it. |
| Is Due | This will display whether the action’s due status is Completed, Overdue, or No due date set. |
When you edit an Anomaly Action, you will also see Tasks and Planning Tasks associated with it. To link a task to an Anomaly Action, edit the Anomaly Action and navigate to the Tasks list. Here you can click Add to create a new task and associate it with the Anomaly Action.
Alternatively, go to the Tasks tab on the WORKPACKS screen. Add or edit a task, and set its Anomaly Action to match the desired anomaly action. Note that the task’s asset and the anomaly action’s asset must match.
Report Table Sources¶
To extract anomaly action data into a report template, use the System Table titled Action as the primary Table Source. For more information see Report Templates.
The Grid¶
The Actions grid lists all anomaly actions for the currently selected anomaly (or anomalies).
The Actions Toolbar¶
- , , :
- Add / Edit / Delete Anomaly Action(s).
Tip
To bulk update (or delete) Anomaly Actions, use the Multi-Edit functionality available from the Actions grid.
- See Import for full description of the Import menu item.
- See Export for full description of the Export menu item.
- See Customise for full description of the Customise menu item.
- See Connections for information about the Connections toolbar option.
- See Navigate to Anomaly for information about the Navigate to Anomaly toolbar option.
- You can assign one or more tasks to an action of an anomaly. By clicking on this button the Select Task dialog will be displayed, you can select the task from the existing tasks or you can add a new task. (If you add a new task, it will have its Asset automatically populated from the anomaly.) The action must have Action Type to be able to assign tasks.