EAM Glossary of Terms

Equipment

Transactions: IE01, IE02, IE05, IE10

An equipment record is a physical object that is maintained as an autonomous unit and can be installed in a functional location.  Equipment is the lowest level in the technical structure where costs can be associated with an item.  Each piece of equipment has its own master record and a separate maintenance history.  Equipment records are not permanently fixed in a functional location and may be installed at various functional locations over time.  Multiple equipment records may be installed in one functional location.  Equipment records represent poles, switches, transformers, towers, circuit breakers, potheads, etc.

Maintenance Plan

Transactions: IP02

A Maintenance Plan is a master data record that contains a maintenance cycle (or cycles), the maintenance task lists (for tasks to be completed at each interval), and the technical object where/on which the work is performed. The technical object is a location or equipment number and appears on a maintenance item on the plan.

A plan may contain more than one maintenance item. A work order is generated for each maintenance item the plan has. Maintenance items are usually grouped together and put on the same plan if the objects which are to be inspected or maintained are in close proximity, or if it is important that the work on those items be consistently scheduled for the same timeframe.

When users Complete Inspection work orders, the completion information is updated against the Maintenance plan. This is known as PM Crediting.

Functional Location

Transactions: IL01, IL02, IL03

A functional location is part of a technical structure representing an area of responsibility. Functional location structure typically does not change over time.  At the higher levels, functional locations can be structured according to organizational hierarchy, infrastructure/ system functions, infrastructure/ system processes or physical locations.  Each functional location has its own master record and a separate maintenance history.

Compatible Units

Transactions: /CUM/DESIGN, /CUM/CM02

Compatible unit management is intended for industries that design their work using standard units. On completion of a design using compatible units, data from the design is translated to a structure that enables integration with work management, materials management, and finance via the work order. Compatible Unit Management in SAP makes use of standard Plant Maintenance functions, such as task lists and technical objects.

Tasks Lists

Transactions: IA09, IA13, IA07, IA*

Task Lists are used to describe a sequence of individual maintenance operations that must be performed at periodic intervals (as part of a maintenance plan/strategy), or to model work orders to provide a basic set of standardized operations that can then be modified to meet the specific resource (labor, material) requirements of the activity within a work order.

Task Lists are also used with Compatible Units. Using Compatible Units, units of work can be predefined, which can then be enhanced with the specific requirements for a particular job (job steps, duration, crew assignment, special tools, documents, accounting data, and so on).

Task lists contain information for the order operations such as work center, work, unit of work, duration, duration unit, number of capacities, etc. Task lists aid in the planning of work for work that typically does not go through a rigorous planning process.

Bill of Materials (BOMs)

Transactions: CS02

Bill of Materials (BOMs) are currently used by crews to determine what parts they need to accomplish a job. For example, if they are working on a transformer, rather than looking through a catalog for the correct part, the BOM is used to determine what parts are needed to perform the repair.


Measuring Points

Transactions: IK01, IK02, IK03

Measuring points are the physical and/or logical places at which a condition is described for a particular technical object. The readings at a measurement point are recorded as measurement documents in SAP.

Non-counter measuring points (both numeric and qualitative) can be used to represent a point-in-time condition of a technical object. This information can be used to create notifications and work orders when a threshold value for the technical object has been observed. These measuring points are frequently used to track the history of inspections.

Measurement points and documents streamline the process of inspection and repair to ensure proper functioning of technical objects to meet the maintenance requirements of the organization and regulatory bodies.

 

Classes and Characteristics

Transactions: CL02, CL04, CL20N

Class and Characteristic value assignments to Functional Locations and Equipment masters provide the ability to categorize Functional Locations and Equipment masters based on various physical properties of the object like color, type, length etc. The Characteristic value assignments in a Class can also describe usage properties, functional specifications, or other attributes.

The Class and Characteristic function in SAP also provides a ‘blank canvas’ which can be used to create any number of additional attribute fields to capture information that cannot be converted to a matching SAP target field on the standard Equipment or Functional Location master.

In SAP, the search for items with certain attributes (Characteristic Values) is done by first searching for items of a certain Class of the Equipment or Functional Location, and then further specifying the values of the Characteristic in the Class that are sought.

This will provide the users to search for a particular technical object based on any of its recorded properties.

For example, attributes like length and type can be maintained as characteristics for technical objects such as poles. These Characteristics can be grouped together to define a Class, which is then assigned to a technical object (such as Functional Location, Equipment or Compatible Unit). Once this Class assignment has been made, the technical object has access to all the Characteristics attached to that Class. Finally, actual values are assigned to the Characteristics for each technical object.

Leave a Reply

Your email address will not be published. Required fields are marked *