Understand the frequently used terms

AVEVA Mobile Operator uses several terms specific to the app and the software. The frequently used terms are as follows:

Asset

Asset is equipment and location at a given base. Static asset, or asset selected at design time, is asset selected by a procedure designer while building the procedure. Dynamic asset, or asset selected at run time, is asset selected by a user while running a procedure.

Asset Type

Asset type is used to classify assets into user-defined categories, for example, Pumps, in order to aid in their location and identification, and inclusion in or exclusion from reports and audits.

Base

Base is a process area or unit within a manufacturing facility. However, a base can also be a logical entity associated with a group of assets and procedures within AVEVA Mobile Operator for a specific discipline or craft, regardless of unit or equipment boundaries.

For example, a Water Treatment Base can be one of many bases within a facility; a Safety Department can also be a base that covers the entire facility.

Condition

Condition is a procedure component which uses a calculation to evaluate a value, acting upon that value if it meets the condition’s calculation expression. A task response may, via a condition, trigger any of a number of actions as per the procedure’s configuration.

For example, if the task response exceeds a numeric constraint, or an appropriate list item is selected, the user may be presented with a focused advice message, prompted to enter a note, write a work order request, or execute a jump step to another task.

Data Filter

Data filter aids in classifying a reading a user has taken for a task. The classification used is entirely at the discretion of the creator of the data filter, and only has bearing in reports and audits configured to take data filters into consideration. Likely candidates for data filters are safety, mechanical, operations, environmental audit, and so on.

Decision

Decision is similar to task group, except that decisions become available only once a condition has been satisfied. Decisions do not possess the versatility of task groups; they cannot be assigned to an asset, so they cannot require scan for status or access to their tasks. They also cannot bear attachments such as documents and trends.

An example of a decision is a new group of tasks that become available due to a reading the user took previously in the procedure.

Default Note

The default note list is a collection of pre-configured text entries made available to users when they need or wish to type notes for a task or task group, or make an entry in the log. This saves time and effort in the field, where a user would otherwise have to type the entire note manually.

For example, with the note "__ quarts of oil added" the user would simply select this note and type a number, rather than having to type the entire sentence.

Management Center

Management Center consolidates various desktop components of the Work Management system in one place.

Mobile Attachments

Mobile attachments provide a method to include additional information with a procedure as an attachment from the mobile device. The information is usually reference material in the form of a PDF, graphic, or spreadsheet.

Node

A node is a task group or task within the procedure.

Plants

Plants are sub-unit of Tenant or Organizations in the hierarchical structure. It is a collection of Bases.

Procedure

Procedure is a collection of tasks and actions in task groups that may or may not be associated with one or more assets. The procedure is available on the mobile device based on a predetermined schedule and field job responsibility. Each task group has a set of tasks that involve data collection. Each task can have a set of actions that prompt the user to take a specific action given an observed result. This facilitates having the correct response options made available for all users. Other terms used for procedure include rounds, surveillance, routes, and electronic log sheets.

Response

Response is group of responses that users use when encountering a task whose data type is set to list. During rounds, a user chooses one of the pre-defined responses and records it as the value for a task.

Examples of response lists include Low/Med/High and On/Off.

Role

Role is used to segregate the view of the procedures that are transferred by job assignment. Since transfer of procedures to the mobile device is by base, role allows a user to see only those procedures that are applicable to the user’s job or craft.

Server Attachments

Server attachments provide a method to include additional information with a procedure as an attachment from the Server. The information is usually reference material in the form of a PDF, graphic, or spreadsheet.

Severity Level

Severity level is used to represent the urgency of user-supplied data according to a numerical scale of the user’s definition. This aids the location of equipment that may urgently be in need of attention.

An example of a typical severity level scale is as follows.

  0 - Normal

10 - Alert

20 - Warning

30 - Critical

40 - Danger

50 - Shut Down

Status List

Status list is used to indicate the status of the equipment. Based on user selection, tasks and task groups associated to the equipment may be enabled or disabled.

Task

Task is the primary instruction provided to the user within a procedure. Tasks can be configured to accept different types of data such as numerical, text, list, date, calculation, and data entered through execution of custom functions that call external systems.

Task Group

Task Group is a group of tasks, or other task groups, which are usually associated with an asset. Examples of task groups include grouping observations or measurements for equipment such as a flare stack, tank, or pump, and grouping multiple sets of observations or measurements.

For example, a compressor train may have sub-groups defined for the driver, the compressor case and a lube oil skid with each task group able to have its own status assigned.

Trend

Trend provides a method to include historical task values with a procedure. The user can then view the values as a graph while working with the procedure in the field.

User

User is a field user using the AVEVA Mobile Operator app.

User Group

User group is a collection of users that share a common set of permissions.

WOR

WOR or Work Order Request is an entry as configured in the System Configuration module of the Management Center for the installed Work Order Request module in the Server.