Setting Up

This chapter covers the following topics:

Before You Begin

As you plan your implementation of Oracle Enterprise Asset Management (eAM), Oracle recommends that you consider the implementation issues discussed in this section. By carefully planning your implementation, you can save time and reduce errors.

Overview of Setting Up

This section lists the steps required to implement Oracle Enterprise Asset Management, along with advanced implementation topics for you to consider.

When installing Oracle Enterprise Asset Management, the installation process automatically creates five responsibilities: Oracle Enterprise Asset Management, Maintenance User Workbench, Maintenance Super User, Self-Service Work Requests, and Self Service Time and Expenses. The Oracle Enterprise Asset Management is a super user responsibility. It includes the necessary functions to set up and implement Oracle Enterprise Asset Management.

Before setting up Oracle Enterprise Asset Management, set up the users and assign their appropriate responsibilities for the implementation.

Related Product Setup Steps

Oracle Enterprise Asset Management setup includes various setup steps within Oracle Applications products. These steps are discussed in detail in the Overview of Setting Up sections of the respective Oracle Product users guides.

Setting Up Underlying Oracle Applications Technology

Ensure that you complete the following setup steps, including:

Oracle Enterprise Asset Management Setup Overview

Oracle Enterprise Asset Management (eAM) may have unique setups for each organization, including parameters, user defined lookups, and attributes. During the implementation process, the implementation team should discuss system and user options for Enterprise Asset Management. Users implementing Enterprise Asset Management should also have determined the structure of their organizations and user access through the Oracle System Administrator responsibility.

This chapter covers the following topics:

Organization Setup

Organization setup is required before you can set up any additional Enterprise Asset Management information. Tasks include:

Setting Up Organizations

A valid organization is a requirement for Enterprise Asset Management setup. Decisions are made during implementation as to which organizations are enabled for Enterprise Asset Management. If the organizations already exist, you can skip this section and proceed to Enabling Organizations for Enterprise Asset Management.

To set up organizations

  1. Navigate to the Organization window.

    Organization

    the picture is described in the document text

  2. Enter an organization Name, for example, Seattle Maintenance.

  3. Select an organization Type. For information on Type, Dates region fields, Location, Internal or External, Location Address, and Internal Address fields, see the Oracle Human Resources User's Guide.

  4. Save your work. A valid location must be set up before you can save.

  5. In the Organization Classifications region, establish this organization as an Inventory Organization.

    Select Inventory Organization from the Name list of values.

    Additional Information: An eAM organization must be classified as an Inventory Organization. You can also classify an eAM as other product organizations.

  6. Save your work.

Setting Up the Oracle Purchasing AutoCreate Process

Use the AutoCreate process to automatically create purchase orders from requisitions based on a specific operating unit. Follow these steps to set up the feature:

  1. Navigate to the Organizations window to search for the organization, such as Seattle Maintenance.

  2. In the Organization Classifications region, highlight the Inventory Organization value.

  3. Click the Others button, and the Additional Organization information window appears.

  4. Select Accounting Information.

  5. Click in the Accounting Information field, and the Accounting Information window appears.

    the picture is described in the document text

  6. Select a value for the Operating Unit field, and then click OK.

  7. Click OK.

  8. Save your work.

Enabling Organizations for Enterprise Asset Management

Before you begin implementing Enterprise Asset Management (eAM), decide which organizations are eAM enabled. A valid organization must exist before you can enable the organization for Enterprise Asset Management (See: Setting Up Organizations).

To define an Enterprise Asset Management enabled organization

You can create a new Enterprise Asset Management enabled organization, or convert an existing organization to an Enterprise Asset Management enabled organization. Oracle recommends that you keep Enterprise Asset Management organizations separate from production organizations. Enterprise Asset Management parameters are on the Inventory Parameters tab, within the Organization Parameters window.

  1. Navigate to the Organization Parameters window.

    Organization Parameters

    the picture is described in the document text

  2. Enter a valid organization code. For information on how to create an organization, See: Setting Up Organizations.

  3. Select the Approve automatically value in the Move Order Time Out Action field.

    Move orders are created with a status of Incomplete if the planner is defined in the Organization Items - General Planning tab.

    Set up the Move Order parameters for Move Order Time Out and Move Order Time Out Action as required. See Overview of Move Orders, Oracle Inventory User's Guide.

    If the planner is not defined, move orders are created with a status of Pre-approved.

    Approval action is required to change the status of the move order to Approved. After approval, the material allocation will occur.

    For more information regarding planner definition, see Defining Planners, Setting Up, Oracle MRP User's Guide.

  4. Select the EAM Enabled check box to enable Enterprise Asset Management for this organization.

    You cannot clear this check box after Enterprise Asset Management items or Enterprise Asset Management parameters are defined in the current organization.

  5. If Enterprise Asset Management is enabled for the current organization, the EAM Organization value defaults and is disabled; the current organization code defaults.

    For organizations that are not Enterprise Asset Management enabled, you can populate the EAM Organization field with an Enterprise Asset Management enabled organization code. The designated eAM organization maintains equipment items for the designated production organization. For example, if the current organization is a production organization, this is how you would identify a maintenance organization that is associated with the production organization (See: Overview of the Process and Discrete Manufacturing Integration, Oracle Enterprise Asset Management User's Guide). You can update this field, if asset equipment association does not exist in this organization.

  6. Select the LCM Enabled check box to enable the ability to capture landed costs during asset capitalization.

    For more information regarding landed costs, see Including Landed Cost for Asset Capitalization Value, Understanding the Fixed Asset Architecture in Oracle Asset Tracking User's Guide.

  7. If you are using encumbrance accounting, you must enable this feature.

    Navigate to the Costing Information page.

    Costing Information

    the picture is described in the document text

  8. Select the Reverse Encumbrance option.

  9. Save your work.

Related Topics

Oracle Inventory User's Guide

Setting Up Installed Base Parameters

Oracle Enterprise Asset Management is integrated with Oracle Installed Base. Therefore, the Installed Base parameters must be set up to ensure that assets are created correctly in eAM.

Creating an Internal Party

You must perform the following steps in Oracle Installed Base:

  1. Navigate to the Installed Base Administrator responsibility.

  2. Under the Setups menu, click the Install Parameters link.

  3. Set up the Install Parameters for Installed Base.

    See Set Up Installation Parameters, Setup Steps within Oracle Installed Base, Oracle Installed Base Implementation Guide.

  4. Verify that the Freeze check box has been selected.

    If it is unchecked, then select the check box.

  5. Save your work.

Setting Up Services Fulfillment Manager Parameters

Several transactions originating from Inventory and Order Management are processed in Installed Base, and these transactions must be serialized.

To guarantee the serialization of the transactions, you must perform the following steps to ensure that asset transfers are performed correctly in eAM:

  1. Navigate to the SFM System Administrator responsibility.

  2. Navigate to Administration, and then click the Queue Console link.

  3. Click the Services button.

  4. Select the SFM Event Manager Queue Service value.

  5. Enter a value of 1 for both the Actual and Target to ensure that the Services Fulfillment Manager is up and running.

  6. Save your work.

Related Topics

See Ensure the Serializability of Transactions Processed in Oracle Installed Base, Implementation and Setup for New Users, Oracle Installed Base Implementation Guide.

Defining eAM Parameters

After you have established an eAM-enabled organization, set up specific eAM parameters that determine the organization level defaults for individual transactions. Set up information such as asset number defaults, cost defaults, work request information, and work order defaults.

Important: Before creating eAM parameters, first create an asset subinventory in the current eAM-enabled organization (Inventory > Setup > Organizations > Subinventories). See: Creating Subinventories, Oracle Inventory User's Guide.

To define Enterprise Asset Management parameters

  1. Navigate to the Enterprise Asset Management Parameters window.

    Enterprise Asset Management Parameters

    the picture is described in the document text

  2. Optionally indicate whether this organization has system generated asset numbers within individual asset groups. See: Defining Asset Groups.

    You can specify the starting serial number within the Organization Parameters window or the Master Item window, when defining asset groups. If the starting serial number is defined for the asset group, this definition overwrites the starting serial number within the Organization Parameters.

  3. Optionally choose Event Log Controls to enable system events that are logged within the current organization.

    You can select the Log Enabled check box next to the events that you want logged for your assets. See: Asset Operational Logging, Oracle Enterprise Asset Management User's Guide.

  4. The Cost Defaults region represents default cost information for future work orders, without defined cost elements within the work order.

    Select an Enterprise Asset Management Cost Element to indicate how to capture cost overheads and any miscellaneous resource costs. Valid values are Equipment, Labor, and Material. See: Overview of eAM Cost Management, Oracle Enterprise Asset Management User's Guide.

  5. Select a Cost Category to use as the default for departments that do not have a cost category defined.

    Department costs are then posted to the appropriate cost elements. Values are Maintenance, Operations, Contract, and any other values that you may have added within the extensible lookup table.

  6. In the Preventive Maintenance region, optionally select the Implement From Horizon Start Date check box to bypass past due work order suggestions when executing the Preventive Maintenance process.

    If this check box is selected, suggested work orders from the Horizon Start Date forward are executed.

  7. Indicate whether work requests are automatically approved upon creation, or if every user, with the responsibility assigned to the asset's current owning department, receives a notification through workflow (See: Oracle Applications Workflow and Defining Department Approvers).

    This notification appears within self service, within the responsibility you use to log in.

    If the Auto Approve check box is selected, work requests are created with an Awaiting Work Order status. If the check box is not selected, work requests are created with an Open status.

    Note: A work request status must be Awaiting Work Order before you can associate it with a work order. The Awaiting Work Order status indicates that the work request is approved.

  8. Optionally select the Enable AME Approval Workflow to trigger the work request approval process to follow the AME Rules.

    Important: The Enable AME Approval Workflow check box can be selected as Yes only if the Auto Approve parameter is set as No.

  9. Optionally select the Default Asset from Employee Location check box to indicate the default asset information when creating a work request.

    If this check box is selected, the Asset Number information defaults as the Location number exported from Oracle Property Manager. Oracle Property Manager is a separate product.

  10. Optionally enter values in the Work Request Prefix field (up to 3 characters) and the Work Request Sequence field (up to 6 characters). A prefix enables your organization to identify work requests.

  11. If you choose the Extended Log check box, the system keeps an audit trail of records when defining or updating work requests.

  12. Optionally select the Asset Number Mandatory check box to indicate that the Asset Number field is mandatory when creating a work request.

  13. Click the Request by Dates Setup button to manage the setup for work requests by Request by Start and Request by Completion date tolerances. These dates appear in the Work Request UI (Maintenance Super Use > Home > Work Requests).

    This information provides the ability to prioritize and complete work more efficiently.

  14. Select Yes or No in the Include Inactive Setups drop-down. If you select No, only the Active setups will appear.

    The Request by Dates Setup page appears.

    the picture is described in the document text

  15. Use this page to create, update, and delete work request information based on Work Request Priority and Work Request Type.

    1. Click the Add Row button.

    2. Enter values for the following fields:

      • Work Request Priority (required)

      • Work Request Type

      • Request by Start Date from System Date (Hrs): Enter a positive numeric value or decimal; negative values are not allowed.

      • Request by Completion Days Tolerance (Hrs): Enter a positive numeric value or decimal; negative values are not allowed.

      • Effective Start Date

      • Effective End Date

      Note: Oracle Quality will make changes to the default request by date based on existing rules for Quality triggered work requests. This feature works with WR Priority based rules only.

    3. Save your work.

  16. Click the Request Types Mapping button to create associations between work requests and work orders. If you create the mapping association, the default value for the work order type is automatically linked for the work request type.

    Work Request to Work Order Types Mapping

    the picture is described in the document text

    1. Enter values for one of the work request types:

      1. Work Order Type

      2. End Date

    2. Click Save.

  17. Select the WIP Accounting Class default to ensure that work orders generated within Enterprise Asset Management have an established account code structure assigned to accept charges incurred by that work order.

    The WIP accounting class codes available are of type, Maintenance. If a Maintenance type WIP accounting class does not exist, you can define a new one. If you are using encumbrance accounting, you must include a budget account to capture encumbrance amounts. (See: Defining WIP Accounting Classes, Oracle Work in Process User's Guide).

    Note: Cost Management handles maintenance work orders as nonstandard expense jobs.

  18. Optionally enter a Work Order Prefix.

    A prefix enables your organization to identify routine work orders.

    Important: Do not use 'BFWO' (Budget Forecast Work Order) as a work order prefix as the system uses this prefix for work order numbers that are generated in a budget forecast.

  19. Optionally select a Default Department.

    Oracle recommends that you select a default department. This department defaults to maintenance work orders as they are entered. If a department does not exist on a work order, you cannot release it.

  20. Optionally enter a PM Work Order Prefix.

    This prefix enables your organization to identify Preventive Maintenance work orders. There is a limit of 30 characters.

  21. Select the Enable Workflow for Work Orders check box to initiate approval processes for work orders and work permits.

    Work orders and work permits might require approvals or notifications at different stages in their lifecycles. Workflow automates this process. You can set up business events and event subscriptions (or use seeded events and subscriptions) within Oracle Workflow to indicate what events trigger Workflow. Seeded events that you can enable to trigger workflow are: Work Order creation, Work Order release approval, Work Order completion, Work Order status change, Operation completion, Work Permit release approval, Work Permit status update. See: Setting Up Oracle Workflow, Oracle Workflow User's Guide and Setting Up the Business Event System, Oracle Workflow User's Guide.

  22. Optionally select the Enable Workflow for Safety check box to initiate the workflow processes for isolations, work clearances, and work permits used in safety management.

    See Safety Management, Oracle Enterprise Asset Management User's Guide.

  23. Indicate whether Material Issue Requests are enabled.

    If this check box is selected, the Enable Material Issue Requests check box on eAM Work Orders defaults as selected.

  24. Within the Work Order Defaults region, select the Value Rebuildables at Zero Cost to indicate that rebuildable components charge at zero cost.

    I this check box is selected, rebuildable items issued out of the subinventory expense account are issued at zero cost. See Setting Up Zero Cost Rebuild Item Issue).

  25. Indicate whether only billable items are invoiceable.

    If the Invoice Billable Items Only check box is selected, only billable items can invoice; however, the item needs to be invoiceable (Invoiceable Item and Invoice Enabled check boxes selected within the Master Item window. For more information regarding invoicing attribute groups, see the Oracle Inventory User's Guide. In addition, the Billing Type check box should be selected (See: Work Order Billing Setup).

    If the Invoice Billable Items Only check box is not selected, any item can be invoiced if it is invoiceable within the Master Item window (Invoiceable Item and Invoice Enabled check boxes selected within the Master Item window). See Oracle Inventory User's Guide for additional information.

  26. If you select the Auto Firm on Release check box, the dates on the work order cannot automatically reschedule, after the work order is at Released or On Hold statuses.

    You can still manually reschedule a resource on the work order, thereby updating the dates on its corresponding operation and work order.

  27. If you select the Auto Firm on Create check box, the dates on the work order cannot automatically reschedule, even in Draft and Unreleased statuses.

    You can still manually reschedule a resource on the work order, thereby updating the dates on its corresponding operation and work order.

  28. Select the Enable Target Dates for Work Orders check box if you want users to enter target dates for work orders.

    The default value is cleared. If enabled, the target date fields appear on the Work Order pages.

    If the work order is created manually or through PM forecasting, the default date values are the same as the Scheduled Start and Completion Dates. The target dates can be changed if the status of the work order is not Cancelled or Closed.

    Note: Target dates are not mandatory.

    Considerations

    • The target start date can be later or earlier than the schedule start date.

    • The target completion date can be later or earlier than the scheduled completion date.

    • Target Completion Date should be greater than Target Start Date.

    For more information, see Work Orders, Oracle Enterprise Asset Management User's Guide.

  29. Within the Account Defaults region, select a Maintenance Offset account.

    You can create or break a parent and child (hierarchy) relationship that exists between an asset number and a rebuildable serial number, manually using the Configuration History page. This account records what is sent to Inventory when a Rebuildable is removed from an Asset, and then transferred into inventory.

    For example, if the relationship is broken, the Asset or Rebuildable is sent to either Scrap or Inventory. If the Rebuildable is sent to Inventory, the accounting is as follows:

    • Debit Inventory

    • Credit Maintenance Offset

  30. Within the Asset Move Defaults region, select a default Intermediate Subinventory and Intermediate Locator value.

    Only the expense subinventories associated with your organization are available for selection.

    This intermediate subinventory is the default subinventory to which all the assets undergoing miscellaneous receipt transactions are received while performing the Asset Move transfer. The Intermediate Locator value indicates the number assigned to the expense intermediate inventory.

    See Using the Asset Move Workbench, Oracle Enterprise Asset Management User's Guide.

  31. Save your work.

General eAM Setup

General Enterprise Asset Management Setup tasks include the following:

Setting Up Areas

Use areas to logically sort assets by the zones in which they reside. Areas divide the maintenance plant or facility into zones, which help to track and account for assets. Areas are later associated with assets.

To set up areas

  1. Navigate to the Area window.

    Area

    the picture is described in the document text

  2. Using the Add icon on the tool bar, add an area.

  3. Enter a Description for this location.

  4. The Effective From Date defaults as the system date, but you can optionally update it. Optionally select an Effective To Date to indicate an expiration of the area.

  5. Save your work.

Defining Work Order Statuses at the Organization Level

You can define work order statuses and apply them for use by specific organizations.

User-defined work order statuses are defined upon system statuses and are assigned to organizations. For example, you can define a work order status of "Ready to Start" based on the Released system status. You can also have a work order status of Ready to Start based on the system status of Draft. Both statuses can then be assigned to your organization for use.

User-defined work order statuses are available in the (work order) Status field in the UIs, Forms and APIs for Enterprise Asset Management.

To define work order statuses at the Organization level:

  1. Navigate to the Define Statuses form (Enterprise Asset Management > Setup > Work Order Statuses).

    The Define Statuses page appears.

  2. Click the Add Row button.

    the picture is described in the document text

  3. Enter values for the following fields:

    1. Status (name)

      The Unreleased by Approver status is automatically assigned to approvers of work orders. This status enables an approver to update the work order, make required changes, and then approve the work order to be released.

    2. Status

    3. Enabled check box: the default value is selected. If the check box is unselected, the status will not be available for use.

    4. Global check box: This option will be read only indicating the status is applicable to all organizations.

      The default value is selected for the status, if the status is selected for all organizations. However, if at least one organization is unselected from the Work Order Statuses page, then this check box will also be unselected.

      Note: You can select a different status value to update the organization access.

    5. Save your work.

  4. Click the Organization Assignment button, and the Work Order Statuses page appears.

  5. Select a work order Status.

    The default status value from the Work Order Status forms page appears, but you can select a different value in the Status field to update the organization access.

  6. View the organizations to which the status is available in the Organization Status Assignment Table on the page.

    the picture is described in the document text

  7. Select the Enabled check box for organizations who can use this status.

    Unselect the check box if you do not want an organization to use this status.

    Note: If there are work orders and active PM schedules while performing the Unselect action, the following error message appears:

    Status cannot be unassigned as there are either work orders or PM schedules associated with this status.

  8. Click Save.

Defining Departments and Resources

A department represents a crew within your organization. A crew may include people, machines, or suppliers. Departments are also used to collect costs, apply overhead, and compare load to capacity. Assign a department to each operation of a routing and assign resources that are available for that department. The department assigned to each operation of a routing also becomes the assigned department of the corresponding operation within the work order, if the work order is using the routing.

Resources are defined before departments. For information on defining resources, See: Defining a Resource, Oracle Bills of Material User's Guide. When you define a department, you specify available resources. A resource represents a craft. You can enter multiple resources for each department. For each resource, you can specify the shifts that the resource is available. For each resource shift, you can specify capacity modifications that change the available hours per day, units per day, or workdays.

To define departments (crews) and resources (crafts)

  1. Navigate to the Departments window.

    Departments

    the picture is described in the document text

  2. Enter the Department name, unique to the organization.

  3. Optionally select a department Class (See: Creating Department Classes, Oracle Bills of Material User's Guide).

  4. Select a Location.

    Enter a location for a department if it is the receiving department following outside processing (See: Overview of eAM Contractor Services, Oracle Enterprise Asset Management User's Guide and Outside Processing, Oracle Work in Process User's Guide).

  5. Enter a Project Expenditure Organization.

  6. Optionally enter an Inactive On date on which you can no longer assign this department to routing operations.

    For instructions on all remaining fields, See: Defining a Department, Oracle Bills of Material User's Guide (Bills of Material, Routings, Departments).

  7. Click the Resources button to add resources or crafts to the current department.

    Resources

    the picture is described in the document text

  8. Enter the Resource to assign to the current department.

  9. Optionally, for owned resources, indicate whether the resource is available 24 hours per day.

    You cannot assign shifts to a resource that is available 24 hours per day.

  10. For owned resources, indicate whether this department can share the resource and capacity with other departments.

  11. Enter the number of capacity Units (resource units) available for this department, for example, the number of machines for a machine resource.

    Each resource can assign to any number of departments; multiple resources can be assigned to each department.

  12. Optionally select the Check CTP check box to indicate that this resource is used in a Capable to Promise (CTP) check See: Capable to Promise, Oracle Master Scheduling/MRP and Supply Chain Planning User's Guide.

  13. Optionally enter a resource Group for the resource in this department.

  14. Optionally select the Schedule by Instance check box to indicate whether the department resource should be scheduled at the instance level (specific person or piece of equipment).

  15. For borrowed resources, enter the Owning Department.

  16. Select the Planning tab.

    Optionally enter an Exception Set. The exception sets that you assign help to identify capacity problems (See: Planning Exception Sets, Oracle Capacity User's Guide).

  17. Choose Instances to add persons (including contingent workers) or equipment to the current resource. See Implementing Oracle HRMS.

    Instances

    the picture is described in the document text

  18. Choose Shifts for owned resources that are not available 24 hours per day.

    This enables you to assign and update shift information for the resource and define capacity changes for a shift.

    Shifts

    the picture is described in the document text

    1. Select a Shift Number.

      The shifts available are those assigned to the workday calendar and assigned to the current organization.

    2. Choose Capacity Changes to define capacity changes for a shift.

    For more information, See: Assigning Resources to a Department, Oracle Bills of Material User's Guide (Bills of Material, Routings, Departments).

Defining Department Approvers

With a responsibility assigned to the current asset's owning department, you can set up department approvers so that work request notifications are sent to each approver, using Oracle Workflow (See: Defining Departments and Resources and Defining Asset Numbers, and Oracle Applications Workflow). Approvers can view these notifications on the Enterprise Asset Management Self Service Maintenance Home page (See: Maintenance Home, Oracle Enterprise Asset Management User's Guide). Everyone who receives the notification can access the work request to change its status, or add additional information to the Work Request log. After one user approves the work request, the notification is removed from the users' notification lists, and the work request status transitions from Open to Awaiting Work Order.

A work request can be rejected. If an approver rejects a work request, the notification is removed from that approver's notification list. You can re-assign a notification to another user for approval or additional information; for example, the originator might need to provide additional information on the work request.

To define Department Approvers

  1. Navigate to the Department Approvers window.

  2. Select a Responsibility Name. A department is assigned to one responsibility.

    Department Approvers

    the picture is described in the document text

  3. In the Departments region, select a Department. You can select an unlimited number of departments.

  4. Optionally select a Primary Approver for the department from the Name list of values.

    The list of values contains all users within the current responsibility. If the Primary Approver is not specified, the notification is sent to all users with the particular responsibility.

  5. Save your work.

Related Topics

Work Requests, Oracle Enterprise Asset Management User's Guide

Maintenance Home, Oracle Enterprise Asset Management User's Guide

Defining Miscellaneous Documents

You can create text and files, such as spreadsheets, graphics, and OLE objects. You can attach these documents to a maintenance work order, asset, or operation.

To define miscellaneous documents

  1. Navigate to the Miscellaneous Documents window.

    Miscellaneous Documents

    the picture is described in the document text

  2. Select a Data Type:

    • File: Attach the appropriate file.

    • Web Page: Enter the relevant URL.

    • Short Text: Insert the text in the Text field.

    For information on all fields, See: Working With Attachments, Oracle Applications User's Guide.

Setting Up Electronic Records and Signatures

During work order completion, you can require electronic signatures and electronic records. These are provided using the Oracle ERES framework. Electronic signatures require a User Identification and password during the transaction. Electronic records provide a permanent snapshot of the transaction data that the user is verifying.

For more information regarding setting up electronic records and signatures, see the Oracle E-Records Implementation Guide.

To set up electronic records and signatures

  1. Navigate to the Electronic Records page (ERES Administrator > Administration Tasks > Setup > Configuration Variables).

    Electronic Records

    the picture is described in the document text

  2. Select EAM Work Order Completion - SSWA from the Transaction Name list of values.

  3. Optionally select a rule name.

  4. Choose Create to create variable names.

    • Select E-record Required from the Transaction Name list of values. Set this value to Y.

    • Select E-signature Required from the Transaction Name list of values. Set this value to Y.

  5. Choose Apply.

Creating XML Elements for EAM Work Order Completions

All e-records are XML documents consisting of many XML elements. An XML element which is indexed and used for special purposes such as querying or creating security rules is called an Indexed XML Element.

You must set up XML elements to be used for EAM work order completions.

Use the following steps to create and index the XML elements for use in an Advanced Search.

  1. Create the XML elements.

  2. Run the E-record Indexed XML Element Maintenance concurrent program.

  3. Run the Oracle E-Records XML Element Synchronization Program.

Creating XML elements for EAM work order completions

  1. Navigate to the XML Elements page (ERES Administrator > Administration Tasks > Setup > XML Elements).

  2. Click the Create Element button and the Create Element page appears.

  3. Enter EAM as the Owner Application.

  4. Enter the XML Element name, for example, ASSET_ACTIVITY.

  5. Enter the Display Name, for example, Activity.

  6. Select the Query Element check box.

  7. Click the Apply button.

    the picture is described in the document text

  8. You will receive a confirmation message indicating that the specific XML element has been created.

EAM XML Elements

The following table includes the EAM XML elements to be defined.

Important: Use EAM as the Owner Application for each XML element.

Work Order Header XML Elements
XML Element Display Name
ORGANIZATION_CODE Organization Code
WORK_ORDER Work Order Number
WO_DESC Work Order Description
ASSET_GROUP Asset Group
ASSET_GROUP_DESC Asset Group Description
ASSET_NUMBER Asset Number
ASSET_SERIAL_NUMBER Asset Serial Number
ASSET_NUM_DESC Asset Number Description
AREA Area
LOCATION_CODE PN Location Code
LOCATION_NAME PN Location Name
ASSET_ACTIVITY Activity
ASSET_ACTIVITY_DESC Activity Description
CLASS_CODE Accounting Class Code
ACTIVITY_TYPE Activity Type
ACTIVITY_CAUSE Activity Cause
ACTIVITY_SOURCE Activity Source
SCHEDULED_START_DATE Scheduled Start Date
SCHEDULED_END_DATE Scheduled End Date
PM_SUGGESTED_START_DATE PM Suggested Start Date
PM_SUGGESTED_END_DATE PM Suggested End Date
DATE_RELEASED Date Released
DATE_COMPLETED Date Completed
PROJECT_NUMBER Project Number
PROJECT_NAME Project Name
TASK_NUMBER Task Number
TASK_NAME Task Name
PRIORITY Priority
FIRM Firm
WO_TYPE Work Order Type
WO_DEPARTMENT Work Order Department
SHUTDOWN_TYPE Shutdown Type
SHUTDOWN_START_DATE Shutdown Start Date
SHUTDOWN_END_DATE Shutdown End Date
Completions XML Elements
XML Element Display Name
ACTUAL_START_DATE Actual Start Date
ACTUAL_DURATION Actual Duration
ACTUAL_END_DATE Actual End Date
RECONCILIATION_CODE Reconciliation Code
SUB_INVENTORY Completion Sub-Inventory
LOCATION Location
LOT_NUMBER Lot Number

Running the E-records Indexed SML Element Maintenance Concurrent Program

You must run a concurrent program to index the XML elements that you created. The job of the concurrent program is to index all the non-indexed elements. The indexing consists of changing the status field in the table EDR_IDX_XML_ELEMENT_B and creating a section in the interMedia text index for the indexed XML element.

Important: After creating or updating an indexed XML element, you must run this program again in order to index the element.

Follow these steps to submit the program:

  1. Navigate to the Submit Requests page (ERES Administrator > Requests > Run).

  2. Enter the E-record Indexed XML Element Maintenance value in the Name field.

  3. Click the Submit button.

    the picture is described in the document text

Running the Oracle E-Records XML Element Synchronization Program

When new, deleted, or changed XML elements are synchronized into the system, they are available for query on all existing records in the system. To make them available for query on new elements, the Oracle E-records XML Element Synchronization Program must be run. This program is run in the background as a cron job. It is run as often as necessary, based on the amount of querying done in your system. For example, if your system has several hundred records entered every day, and there is a need to have the ability to query these records immediately, then have this program run every hour.

After you have run the indexing concurrent program, submit the Oracle E-Records XML Element Synchronization Program.

Note: Oracle recommends that you schedule this program to run multiple times to pick up newly processed E-records.

Follow these steps to submit the program:

  1. Navigate to the Submit Requests page (ERES Administrator > Requests > Run).

  2. Enter the Oracle E-Records XML Element Synchronization Program value in the Name field.

  3. Click the Submit button.

Related Topics

For more information regarding setting up XML elements, see the Oracle E-Records Implementation Guide.

Defining Lookups

Lookup codes must be decided upon and defined during the implementation process. Lookup codes fall within three categories:

You must define Asset Lookups, Work Request Lookups, and Work Order Lookups.

This section includes the following topics:

Activity Types

Activity types are used to describe the type of maintenance work that is performed on an asset (See: Defining Activities, Oracle Enterprise Asset Management User's Guide). For example, Inspections, Lubrications, Overhauls, Calibration, and Repetitive work. Activity types are extensible (See Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define activity types

  1. Navigate to the Oracle Manufacturing Lookups window.

    Oracle Manufacturing Lookups

    the picture is described in the document text

  2. Click the Find icon.

  3. Select MTL_EAM_ACTIVITY_TYPE from the Type list of values.

  4. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  5. Enter the Meaning of the code, for example, Lubrication.

  6. Enter a Description for the code.

  7. Optionally enter a Tag to categorize lookup values. This field is for informational purposes.

  8. The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration of the code.

  9. Select the Enabled check box to enable this code for Enterprise Asset Management.

  10. Save your work.

Activity Causes

Activity cause codes are reasons for an asset failure. For example, Preventive, Normal Wear, Rework, and Breakdown. This information enables you to understand the dynamics that affect an asset's ability to perform. They establish critical data that is used for reporting and analysis of asset failure causes and the frequency of such conditions. Asset cause codes are referenced when setting up an activity (See: Defining Activities, Oracle Enterprise Asset Management User's Guide). Activity cause codes are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define activity cause codes

  1. Navigate to the Oracle Manufacturing Lookups window.

    Activity Cause Codes

    the picture is described in the document text

  2. Select MTL_EAM_ACTIVITY_CAUSE from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, Breakdown.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values. This field is for information purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date of the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Activity Sources

Activity source codes are the reasons why activities are executed. For example, warranty compliance, OSHA compliance, or military specification requirements. Activity source codes are referenced when setting up an activity (See: Defining Activities, Oracle Enterprise Asset Management User's Guide). Activity source codes are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define activity source codes

  1. Navigate to the Oracle Manufacturing Lookups window.

    Activity Source Codes

    the picture is described in the document text

  2. Select MTL_EAM_ACTIVITY_SOURCE from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering of alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, Breakdown.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration of the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Asset Activity Priorities

Activity priority codes indicate asset activity priority levels, for example, Low, Medium, and High. Activity priorities are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define activity priorities

  1. Navigate to the Oracle Manufacturing Lookups window.

    Activity Priorities

    the picture is described in the document text

  2. Select WIP_EAM_ACTIVITY_PRIORITY from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering of alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, High.

  5. Enter a Description.

  6. Optionally enter a Tag to categorize lookup values. This field is for information purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Asset Failure Source Types

Failure is reported on a work order. Each work order represents one single failure occurrence (event) for the asset specified on the work order (See: Failure Analysis Overview, Oracle Enterprise Asset Management User's Guide). You can optionally add more codes, specifying different source types. For example, you may specify different types of work orders with different source types. Asset failure source types are user-defined (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define asset failure source types

  1. Navigate to the Oracle Manufacturing Lookups window.

    Asset Failure Source Types

    the picture is described in the document text

  2. Select EAM_ASSET_FAIL_SRC_TYPE from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning, for example, Preventive Maintenance Work Order.

  5. Enter a Description.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Asset Import Scope Codes

The eAM Asset Number Open Interface enables you to import asset numbers into eAM, using a batch process. You can optionally import asset number attributes. You can create asset numbers and attributes, or update existing asset numbers and attributes. See eAM Asset Number Open Interface, Oracle Enterprise Asset Management Implementation Guide. Define the process' parameter scope codes. Asset Import Scope codes are user-defined (See: Defining Lookups).

To define Asset Import Scope codes

  1. Navigate to the Oracle Manufacturing Lookups window.

    Asset Import Scope Codes

    the picture is described in the document text

  2. Select EAM_ASSET_IMPORT_SCOPE from the Type list of values.

  3. Enter a numeric code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the meaning, for example, With Attributes.

  5. Enter a description.

  6. Optionally enter a tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date default value appears as the system date, but you can update this field.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Asset Import Statuses

The eAM Asset Number Open Interface enables you to import asset numbers into eAM, using a batch process. You can optionally import asset number attributes. You can create new asset numbers and attributes, or update existing asset numbers and attributes. See eAM Asset Number Open Interface, Oracle Enterprise Asset Management Implementation Guide. Define the process' import statuses. Asset import statuses are user defined (See: Defining Lookups).

To define asset import statuses

  1. Navigate to the Oracle Manufacturing Lookups window.

    Asset Import Statuses

    the picture is described in the document text

  2. Select EAM_ASSET_IMPORT_STATUS from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning, for example, Success.

  5. Enter a Description.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Asset Log User-Defined Events

Asset log events are user-defined (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define asset log user-defined events

  1. Navigate to the Oracle Manufacturing Lookups window.

    Asset Log User-Defined Events

    the picture is described in the document text

  2. Select EAM_USER_EVENTS from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code.

  5. Enter a Description.

  6. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  7. Select the Enabled check box to enable this code for Enterprise Asset Management.

  8. Save your work.

Contact Preferences

You can set up contact preferences. Contact preferences are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define contact preferences codes

  1. Navigate to the Oracle Manufacturing Lookups window.

    Contact Preferences

    the picture is described in the document text

  2. Select WIP_EAM_CONTACT_PREFERENCE from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code.

  5. Enter a Description.

  6. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  7. Select the Enabled check box to enable this code for Enterprise Asset Management.

  8. Save your work.

Cost Category Codes

Cost category codes are used as the default for departments that do not have a cost category defined. Department costs are then posted to the appropriate cost elements. Valid values are Maintenance, Operations, Contract, and any other values that you might add within this extensible lookup table. See: Overview of eAM Cost Management, Oracle Enterprise Asset Management User's Guide.

To define cost category codes

  1. Navigate to the Oracle Manufacturing Lookups window.

    BOM Cost Category Codes

    the picture is described in the document text

  2. Select BOM_EAM_COST_CATEGORY from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, High.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Criticality Codes

Criticality codes suggest the importance of an asset to an organization, for example, High and Low. An asset that has a direct impact on production or that is difficult to replace may be considered a critical asset. Asset criticality codes help you to determine the urgency of requested work. Asset criticality codes are referenced when defining an asset (See: Defining Asset Numbers, Oracle Enterprise Asset Management User's Guide). Asset Criticality Codes are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define asset criticality codes

  1. Navigate to the Oracle Manufacturing Lookups window.

    Asset Criticality Codes

    the picture is described in the document text

  2. Select MTL_EAM_ASSET_CRITICALITY from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

    Warning: Oracle recommends that you do not create more than 250 asset criticality codes in order to avoid performance issues.

  4. Enter the Meaning of the code, for example, High.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Failure Code Types

Failure, cause, and resolution codes are organized into multiple tree structures called failure code sets, which are then assigned to asset groups. Each set provides asset group-specific information on the possible failures of an asset group, the possible causes of each failure, and the possible resolutions for each cause. Assets within an asset group inherit the assigned failure code set. At the work order level, failure tracking codes are entered to report a failure, its cause, and resolution. (See: Failure Analysis Overview, Oracle Enterprise Asset Management User's Guide). You can optionally update the meaning for the failure code types.

To define failure code types

  1. Navigate to the Oracle Manufacturing Lookups window.

    Failure Code Types

    the picture is described in the document text

  2. Select EAM_FAILURE_CODE_TYPE from the Type list of values.

  3. Optionally update the Meaning, for example, Failure Code.

  4. Enter a Description.

  5. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  6. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  7. Select the Enabled check box to enable this code for Enterprise Asset Management.

  8. Save your work.

Functional Hierarchy Types

Functional hierarchy types are used to define location hierarchies for assets. There are several seeded lookup types and they are extensible.

For more information about location hierarchies, see Defining Location Hierarchies and Using Location Hierarchies.

To define functional hierarchy types

  1. Navigate to the Oracle Manufacturing Lookups window.

  2. Select EAM_FUNC_HIER_TYPE from the Type list of values.

    Functional Hierarchy Types

    the picture is described in the document text

  3. Optionally add codes to the pre-existing list of codes.

    The codes that are pre-existing cannot be deleted; however, the meaning can be modified.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Work Request Statuses

The Work Request Approval is the process of changing a work request status from Open to Awaiting Work Order. Maintenance work orders are linked to work requests with a status of Awaiting Work Order. If the Auto Approve check box is selected on the eAM Parameters page (See: Defining eAM Parameters, Oracle Enterprise Asset Management User's Guide) then work requests for that organization are created with an automatic status of Awaiting Work Order. If the check box is not selected, work requests are created with a status of Open. Any user who receives the notification (See: Defining Department Approvers, Oracle Enterprise Asset Management User's Guide) can change the work request status to Awaiting Work Order.

A plant or facility may need to include additional statuses. Currently, the workflow cannot be customized to work with user-defined work request statuses. However, work request approval statuses are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define work request statuses

  1. Navigate to the Oracle Manufacturing Lookups window.

    Work Request Statuses

    the picture is described in the document text

  2. Select WIP_EAM_WORK_REQ_STATUS from the Type list of values.

  3. Optionally add codes to the pre-existing list of codes. The codes that are pre-existing cannot be deleted; however the meaning can be modified.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, Open.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values. This field is for information purposes.

  7. Optionally enter Effective From and To Dates to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Work Request Types

Work request types describe and categorize work requests, for example, Manual, System, Routine, Capital, and Furniture. Work request types are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define a work request type

  1. Navigate to the Oracle Manufacturing Lookups window.

    Work Request Types

    the picture is described in the document text

  2. Select WIP_EAM_WORK_REQ_TYPE from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, Manual.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values. This field is for informational purposes only.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Work Order and Work Request Priority Codes

Work order priority codes contribute to the organization and execution of work orders. For example, High, Medium, and Low, or 1,2, and 3, respectively. Typically, a priority is assigned by the people entering work requests and work orders. The planner or supervisor compares this priority to the asset criticality (See: Asset Criticality Codes, Oracle Enterprise Asset Management User's Guide). These codes are entered when creating activity associations, work orders, and work requests. Typically, a priority is assigned by the person that enters the work request and its related work order. Priority specified during activity association becomes the work order priority when a work order is created, using the activity association (See: Routine Work Orders, Oracle Enterprise Asset Management User's Guide and Work Requests, Oracle Enterprise Asset Management User's Guide). Work order priority codes are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To create work order priority codes

  1. Navigate to the Oracle Manufacturing Lookups window.

    Priority Codes

    the picture is described in the document text

  2. Select WIP_EAM_ACTIVITY_PRIORITY from the Type list of values.

  3. Optionally add additional codes to the pre-existing list of codes.

    The codes that are pre-existing cannot be deleted; however, the Meaning can be modified.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, High.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values. This field is for informational purposes only.

  7. The Effective From Date defaults as the system date, but you can update this value.

    Optionally enter a Effective To Date to indicate an expiration code for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Work Order Reconciliation Codes

Reconciliation codes detail how work orders and operations were completed. These codes usually fall within two categories: Completed as Planned or Partial Completion. You can further define the condition within these two types of completion statuses. These codes enable you to evaluate work orders by percentage completed or delayed, and if they were delayed, the reason for the delay. Reconciliation codes are extensible (See: Defining Lookups, Oracle Enterprise Asset Management User's Guide).

To define work order reconciliation codes

  1. Navigate to the window.

    Work Order Reconciliation Codes

    the picture is described in the document text

  2. Select WIP_EAM_RECONCILIATION_CODE from the Type list of values.

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, Fixed Completely.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Work Order Types

Work order types enable you to differentiate work orders. For example, Routine, and Rebuild. Maintenance management can use this information to sort and monitor work activity for reporting and budgeting. Work order types are referenced in the activity and work order.

Work order types are created manually or automatically. For example, rebuildable work orders are created automatically or manually (See: Rebuild Work Orders, Oracle Enterprise Asset Management User's Guide). Preventive maintenance work orders are created automatically, based on meter readings (See: Preventive Maintenance Work Orders, Oracle Enterprise Asset Management User's Guide).

Work order types are extensible (See: Defining Lookups).

To define work order types

  1. Navigate to the Oracle Manufacturing Lookups window.

    Work Order Types

    the picture is described in the document text

  2. Select WIP_EAM_WORK_ORDER_TYPE from the Type list of values.

  3. Enter a numeric code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. The use of alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, Routine.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date default value is the system date, but you can update this field.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Asset Setup

This section includes the following asset setup tasks:

Setting Up Category Codes

Category codes are used as naming conventions for assets by creating classes and subclasses. Category codes are user defined, and used to logically group assets, simplifying the search for asset numbers.

For example, Cranes are classified by several different types, such as Overhead Cranes, Jib Cranes, and Mobile Cranes. You can query using the class CRANE, which displays all assets defined as Cranes within that organization. If you enter CRANES.JIB, the system would then narrow the results to just those assets defined as Jib Cranes. With both queries, you can identify assets based on familiar names rather than numbers.

Process to use category codes:

  1. Define category codes.

  2. Add the category code to a category set.

  3. Associate the category set to asset groups, which are tied to individual assets.

See also: Defining Categories and Defining Category Sets, Oracle Inventory User's Guide.

To set up category codes

  1. Navigate to the Find Categories window.

    You can find existing category codes, or create new ones.

  2. Choose New.

    Categories

    the picture is described in the document text

  3. Select the Asset Management category to create a new Class.Subclass from the Structure Name list of values.

  4. Enter in a new Category, for example TRUCK.FRKLFT.

  5. Add a long Description for this category.

  6. Optionally select the Enabled check box to indicate that this category is enabled.

  7. Optionally enter an Inactive On date.

  8. Optionally select the Enabled for iProcurement check box to indicate that this category is enabled for iProcurement.

  9. Optionally select the Viewable by Supplier check box to indicate that this category is viewed by the supplier.

  10. Save your work.

To set up category sets

To associate category codes (TRUCK.FRKLFT) with an asset group, first define the item category relationship using the Category Sets menu option.

  1. Navigate to the Category Sets window.

    Category Sets

    the picture is described in the document text

  2. Click the Find button, and then select Enterprise Asset Management.

  3. A default value appears in the Description field, but you can change it.

  4. Select Asset Management from the Flex Structure list of values.

  5. Indicate the Controlled At level. Values are Master Level and Organization Level.

  6. Enter a Default Category code for the category set.

  7. If you select Allow Multiple Item Category Assignments, you can define a series of categories, such as Crane.Jib, and Crane.Overhead that are associated to a single asset group.

  8. If you select Enforce List of Valid Categories, you are preventing users from entering incorrect categories that are not associated with the asset group associated with the asset being created.

  9. Enter the Category Codes that you want to associate with this category set.

  10. Select Assign to display a table enabling you to associate the categories with an asset group.

  11. Save your work.

Defining Asset Groups

During implementation, Asset Group (Asset Group or Rebuildable Item) names should be established. Asset groups represent groups of assets that are virtually identical. Generally, an asset group is defined for each Manufacturer and Model Number combination (Make, Model, and Year). Examples include Acme Model 123 Pump and Ford F150 2002 Truck.

Note: If you have assets in your organization that are virtually identical (for example, the same manufacturer and model), consider creating an asset group for those assets.

Note: The Asset Groups page does not support electronic signatures. If you create an asset group, the record does not contain your electronic signature.

To set up asset groups

  1. Navigate to the Asset Groups page.

    Asset Groups

    the picture is described in the document text

  2. Enter the name of the asset group.

  3. Enter a Description for this asset group, up to 240 characters.

  4. Select the @Asset Group Template to quickly apply attribute values, and to ensure that the appropriate attributes are applied.

    Note: You can create asset groups using the template described above, or you can copy an asset group from an existing asset group (See: Defining Items, Oracle Inventory User's Guide).

    The following table presents the required attribute values that are applied automatically to the asset group when using the template.

    Asset Group Attributes
    Attribute Value
    User Item Type Asset Group
    Item Status Active
    Inventory Item Enabled
    Transactable Disabled
    Serial Number Generation Predefined
    Effectivity Control Model/Unit Number
    EAM Item Type Asset Group

  5. In the Serial Generation region, select Predefined for the Generation value.

  6. Define a Starting Prefix and Starting Number for this asset group.

    If Serial Generation is set at Item Level for the Organization, the system populates the prefix, along with the starting number sequence, when a new asset number is created for this asset group.

  7. Save your work.

To view failure analysis information

You can access the Failure Set page to view failure tracking codes that are assigned to the current asset group.

  1. From the Asset Groups page, select Maintain Failure Set from the Tools menu.

    If the asset group does not have an associated failure set, this menu option is disabled. See: Defining Failure Codes and Sets, Oracle Enterprise Asset Management User's Guide and Failure Analysis Overview, Oracle Enterprise Asset Management User's Guide.

    the picture is described in the document text

  2. Close the page.

To associate asset groups with multiple organizations

  1. From the Asset Groups page, select Item Details from the Tools menu.

  2. Select the Organization Assignment tab.

  3. Select additional organizations in the available table.

  4. After saving your work, you can create assets for this asset group.

Defining Activities

Activities provide you with a standard template of jobs, which are applied to work orders, such as Routine or Preventive Maintenance. After these activity templates are created, they are associated with one or more asset numbers or rebuildables. They are also associated to a maintenance BOM and routing containing the materials and resources needed for operations, respectively. When work orders are created for assets associated to the activity, the material and resources associated with the current activity automatically copy to the work orders created.

There are three methods you can use to create an activity. You can create an activity within the Master Activity (Master Item) window, using the Activity Workbench, or from within a Maintenance work order.

To set up activities within the Master Activity window

  1. Navigate to the Activity (Master Item) window.

    The Master Item window is used to create asset groups, activities, and rebuildables.

    Master Item

    the picture is described in the document text

  2. Enter the name of the activity in the Item field.

  3. Enter a Description for this activity, up to 240 characters.

  4. Use the @Activity template to quickly apply attribute values, and to ensure that the appropriate attributes are applied.

    1. Select Copy From located under the Tools menu.

    2. Select the @Activity template.

      Note: You can create activities using the template described above, or you can copy an activity from an existing activity (See: Defining Items, Oracle Inventory User's Guide).

    The following table presents the necessary attribute values that are applied automatically to the activity, when using the template:

    Activity Attributes
    Attribute Value
    User Item Type Activity
    Item Status Active
    Inventory Item Enabled
    EAM Item Type Activity

  5. Select the Asset Management tab.

    In the Activity Property region, optionally enter an Activity Type to indicate the type of maintenance for this activity. It is used when defining a work order. It should remain generic, and should not describe the job in detail. For example, Inspection, Overhaul, Lubrication, Repair, Servicing, or Cleaning.

  6. Optionally select an Activity Cause to specify what situation caused this work to generate; for example, Breakdown, Vandalism, Normal Wear, or Settings.

  7. Optionally select an Activity Source.

    Activity Source codes are reasons activities are executed.

    For example, Warranty Compliance, OSHA Compliance, or Military Specification Requirements. See: Activity Sources.

  8. Optionally select a Shutdown Type.

    This indicates whether a shutdown is necessary to perform this maintenance activity. For example Required, and Not Required. This field is for information purposes.

  9. Optionally select an Activity Notification Required value to indicate whether the asset requiring work is mobile, and should be brought into the shop for repairs.

    This field is for informational purposes.

  10. Save your work.

    After saving your work, this activity can be associated with an asset.

To associate activities to multiple organizations

  1. Navigate to the Master Item window, and select an activity.

  2. Select the Tools menu and click Organization Assignment.

  3. Select additional organizations.

  4. Save your work.

To associate assets with activities

After you have defined asset groups, assets, and activities, you can associate the activities with assets and rebuildables. However, you can streamline the creation of activities and associations using an Activity Association Template. Assets are associated with activities before entering the activity into a preventive maintenance schedule.

Note: The Activity Workbench is generally used to streamline your activity setups, including asset number and activity associations. Also, you can streamline the creation of activity associations using an activity association template. For example, when you create an asset group and the asset numbers within that group, you do not need to utilize the Association window to associate those asset numbers with an activity. If you create an Activity Association Template, the activity that you associate with the current asset number's asset group automatically determines the activity that is associated with the current asset number.

You can also use Oracle Web Services to automatically create, update and search for asset activity associations. These public interfaces enable you to more easily convert data from another instance or another system. These web services are annotated and available in the I-Repository along with other public Oracle APIs.

  1. Navigate to the Activity Association window.

    Activity Association

    the picture is described in the document text

  2. Select an activity.

  3. Within the Main tab, select Asset or Rebuildable from the Item Type list of values.

    This field works directly with the Asset Group and Asset Item fields.

    If the Asset value is selected, then the Asset Group field refers to the asset group, and the Asset Number value refers to the asset number. If the Rebuildable value is selected, the Asset Group field refers to the rebuildable item, and the Asset Number field refers to the specific serial numbers for the current rebuildable item.

  4. Select an asset group.

    If the Asset field is populated in the Item Type field, your asset groups are available for selection.

  5. Select an asset number.

    Asset numbers associated with the previously selected asset group are available. Asset numbers are always serial controlled. If you select a non-serialized rebuildable in the Asset Group field, then an asset number value is not required.

  6. Optionally select a priority code.

    This field is for informational purposes.

  7. Optionally enter Effective Dates.

    If the Effective From field is left blank, it defaults to the system date. If the Effective To field is left blank, it defaults to NULL.

  8. Click the Work Order Defaults tab.

    Use this tab to optionally define default information that will appear for work orders such as:

    • Activity Cause: Default value comes from the Activity definition, specifying what situation caused this work to generate. For example, Breakdown, Vandalism, Normal Wear, or Settings.

    • Activity Type: Default value comes from the Activity definition, indicating the type of maintenance activity to perform for this activity, and is used during job definition.

      This code should remain generic, and should not describe the job in detail. For example, Inspection, Overhaul, Lubrication, Repair, Servicing, or Cleaning. Optionally, you can select an activity type.

    • Tagging Required: Select this check box to indicate whether tag out procedures are required.

      This indicates that the area may need securing to perform operations for a work order. Tags are generally printed and placed on an asset, warning the plant that the asset is shutdown, and should not be started. This check box helps the planner isolate those jobs that require a tagout. This is for informational purposes.

    • Owning Department: Default value comes from the asset number definition and indicates a planner or supervisor who is responsible for the activity or asset.

    • Shutdown Type: This value defaults from the Master Activity information that was created within the Master Item window.

      This option indicates whether a shutdown is necessary to perform this maintenance activity, for example, Required or Not Required. This field is for informational purposes.

    • WIP Accounting Class: Defaults from the eAM Parameters information for the current organization; you can update this value.

    • Activity Source: This value defaults from the Master Activity information created in the Master Item window.

      Activity source codes are the reasons why activities are executed, for example, Warranty Compliance, OSHA Compliance, or Military Specification Requirements.

    • Work Order Type: Select a value to differentiate work orders. For example, Routine, and Rebuild. Maintenance management can use this information to sort and monitor work activity for reporting and budgeting.

    • Planner: Select a planner to be assigned to the work order.

    • Firm: Select to indicate the work order is to be firmed and planning and scheduling will not automatically adjust the schedule, regardless of material or resource availability.

    • Planned: Select to indicate that this is a planned order.

    • Notification: Select if a notification is to be generated.

  9. Save your work.

Reapplying an Activity Template

You can reapply an activity template to an entire asset group or to specific asset numbers or serialized rebuildables within an asset group. The activity template can only be applied to those assets whose activity template has not been previously applied.

Important: The concurrent program applies to asset groups that have existing activity templates associated.

  1. Navigate to the Reapply Asset Template form (Enterprise Asset Management > Assets > Reapply Asset Template).

  2. Select the Asset Type (required). Values are Capital or Rebuildable.

  3. Enter the Asset Group (required).

  4. (Optional) Select the Activity Template to be reapplied.

    If the Activity Template field is blank, the concurrent program reapplies all activity templates to the entire asset group.

  5. (Optional) Enter values in these fields to reapply the Activity template to a range of asset numbers within the asset group:

    • Asset Status

    • Asset Number From: Enter the beginning asset number value if you want to apply the activity template to a range of asset numbers in the asset group.

    • Asset Number To: Enter the ending asset number value if you want to apply the activity template to a range of asset numbers in the asset group.

    If you enter a value in the Asset Number From field but leave the Asset Number To field blank, the concurrent program will apply the activity template to a specific asset number.

  6. Optionally select Yes in the View Only field if you do not want the system to apply the templates.

    A log is generated but the templates are not reapplied to the assets. The default value is No.

    the picture is described in the document text

  7. Click OK to run the concurrent program.

Activity Association Templates

Activities provide you with a standard template of jobs, which are applied to work orders, such as Routine or Preventive Maintenance. After the activity templates are created, they are associated with one or more asset numbers or rebuildables (See: Defining Asset Numbers and Rebuildable Item/Activity Association). They are also associated to a maintenance BOM (See: Setting Up Activity Bills of Material) and activity routing (See: Defining Asset Routes), containing the materials and resources needed for operations, respectively. When work orders are created for assets associated to the activity, the material and resources associated with the current activity automatically copy to the work orders created.

You can streamline the creation of activity associations using an Activity Association Template. For example, when you create an asset group, and then asset numbers within that group, you do not need to utilize the Association window to associate those asset numbers with an activity. If you create an Activity Association Template, the activity that you associate with the asset group for the current asset number automatically determines the activity that is associated with the current asset number.

Note: The Activity Workbench is generally used to streamline your activity setups, including Activity Association Templates (See: Using the Activity Workbench).

To create activity association templates

  1. Navigate to the Activity Association Template window.

    Activity Association Template

    the picture is described in the document text

  2. Select an activity. The activity is created using the Master Item window.

  3. Within the Main tab, select an Item Type of Asset or Rebuildable.

  4. Select an asset group.

    After this record is saved, this asset group is associated with the current activity. Each asset number created within the current asset group is automatically associated with the current activity.

  5. Optionally select a Priority code.

    This default value comes from the Master Activity information created using the Master Item window.

  6. Optionally enter Effectivity Dates for this Activity Template.

  7. Click the Work Order Defaults tab.

    Use this tab to optionally define default information that will appear for work order such as:

    • Activity Cause: Defaults from the Activity definition, specifying what situation caused this work to generate. For example, Breakdown, Vandalism, Normal Wear, or Settings.

    • Activity Type: Defaults from the Activity definition, indicating the type of maintenance activity to perform for this activity, and is used during job definition.

      This code should remain generic, and should not describe the job in detail. For example, Inspection, Overhaul, Lubrication, Repair, Servicing, or Cleaning. Optionally, you can select an activity type.

      See Defining Activities.

    • Tagging Required: Select this check box to indicate whether tag out procedures are required.

      The area may need securing for operations required for carrying out a work order. Tags are generally printed and placed on an asset, warning the plant that the asset is shutdown, and should not be started. This check box helps the planner isolate those jobs that require a tagout. This is for informational purposes.

    • Owning Department: Defaults from the asset number definition and indicates a planner or supervisor who is responsible for the activity or asset.

    • Shutdown Type: This value defaults from the Master Activity information that was created within the Master Item window.

      This option indicates whether a shutdown is necessary to perform this maintenance activity, for example, Required or Not Required. This field is for informational purposes.

    • WIP Accounting Class: Default values come from the eAM Parameters information for the current organization, but you can update this value.

    • Activity Source: This value defaults from the Master Activity information created in the Master Item window.

      Activity source codes are the reasons why activities are executed, for example, Warranty Compliance, OSHA Compliance, or Military Specification Requirements. Activity Sources.

    • Work Order Type: Select a value to differentiate work orders. For example, Routine, and Rebuild. Maintenance management can use this information to sort and monitor work activity for reporting and budgeting.

    • Planner: Select a planner to be assigned to the work order.

    • Firm: Select to indicate the work order is to be firmed and planning and scheduling will not automatically adjust the schedule, regardless of material or resource availability.

    • Planned: Select to indicate that this is a planned order.

    • Notification: Select if a notification is to be generated.

  8. Save your work.

Setting Up Attributes

You can define common characteristics data specific to asset groups, such as Facility Information, Engineering Specifications, Regulation Requirements, Horsepower, Voltage, and Square Footage, by creating attribute groups using descriptive flexfields. After the attribute group is created, you can then assign it to an asset group. This enables you to define additional characteristics data when defining an asset associated with the asset group. This provides extensive query capabilities. Attribute groups are descriptive flexfields, defined by segments and values.

For example, you can define an Attribute Group, Front Loader Nameplate data. This group can then be associated with the CARS Asset Group. When defining an asset within the CARS Asset Group, you can optionally utilize the attributes to specify nameplate data (specified data such as make, year, and model) for the asset. This creates a simplified way of entering specified data (See: Defining Asset Numbers) related to a specific Asset Group.

To set up attributes

  1. Navigate to the Descriptive Flexfield Segments window.

    Descriptive Flexfield Segments

    the picture is described in the document text

  2. Select the Search icon from the tool bar, and then select the Oracle Inventory Application with the Title, Asset Attributes.

  3. Unfreeze the Flexfield Definition by clearing the Freeze Flexfield Definition check box.

  4. In the Context Field Values region, select a row, then click the New icon. A blank row is added for you to create an attribute group.

  5. Enter the attribute group name in the Code field.

  6. Optionally enter a Description for this attribute group.

  7. Select Segments to add attributes to the attribute group you just created.

    Segments Summary

    the picture is described in the document text

  8. Enter a Number to sequence the data.

  9. Define the Name of the specific attribute. The Window Prompt defaults to this name.

  10. Select a Column value.

  11. Select a Value Set, or optionally choose Value Set to create a new one.

  12. If the Displayed check box is selected, this attribute appears for you when defining data for an asset within the asset group (for example, Fork Lift Classifications) associated with the attribute group in which this attribute (for example, Make) resides.

  13. Optionally select the Enabled check box to enable the attribute for availability when defining assets (See: Defining Asset Numbers, Oracle Enterprise Asset Management User's Guide).

  14. Save your work, and return to the Descriptive Flexfield Segments window.

  15. Select the Freeze Flexfield Definition check box. Failure to do this prevents you from querying the segments from the Attribute window.

  16. Save your work.

To associate the attribute group with an asset group

  1. Navigate to the Attributes Assignment window.

    In the following example, any asset created within the Fork Lifts asset group has the Fork Lift Classifications attribute group available as an option for data entry.

    Attributes Assignment

    the picture is described in the document text

  2. Select an Asset Group. See Defining Asset Groups.

  3. Select an Attribute Group Code.

    You can have an unlimited number of attribute groups associated with an asset group.

  4. Save your work.

Defining Asset Documents

You can attach existing documents to an asset, and create text to associate with an asset. You can attach text, URLs, or files, such as spreadsheets, graphics, and OLE objects. When creating a work order for an asset with attachments, you can attach the asset's attachments to the work order. For this to function, the appropriate attachment category, Asset Attachments (1), must be associated with the attachment function, EAMWOMDF (See: Working With Attachments, Oracle Applications User's Guide.

To define asset documents

  1. Navigate to the EAM Asset Documents window.

    EAM Asset Documents

    the picture is described in the document text

  2. Select a Data Type.

  3. If the Data Type is File, attach the appropriate File. If the Data Type is Web Page, enter the relevant URL. If the Data Type is Short Text, insert the text in the text field.

    For information on all fields, See: Working With Attachments, Oracle Applications User's Guide.

  4. Save your work.

Defining Asset Statuses

Use the Create Status page to define asset statuses. The status value appears for selection in the Asset Status field in the Define Asset Number, Define Rebuildable Serial Number and Define Asset Route forms, and can be used by discrete and GIS assets.

  1. Navigate to the Create Status page (Maintenance Super User > Assets > Asset Setups > Asset Statuses > Create Status or Maintenance Super User > Assets > GIS Assets > Asset Statuses > Create Status).

    Create Status - GIS Assets tab

    the picture is described in the document text

  2. Enter a Name for the asset status (required).

  3. Select the check box for any of the following statuses:

    • Terminated

    • Status Change Allowed

    • Service Allowed

    • Request Allowed

    • Updateable

    • EAM Asset Status

  4. Optionally enter an Active Start Date.

  5. Optionally enter an Active End Date.

  6. Optionally enter a Description.

  7. Click Save or Apply.

Updating Asset Statuses

  1. Navigate to the Update Asset Statuses page (Maintenance Super User > Assets > Asset Statuses or Maintenance Super User > Assets > GIS Assets > Asset Statuses > Create Status).

    You cannot modify an asset status if there are existing assets using the asset status.

    The Update Asset Status page appears.

    the picture is described in the document text

  2. Search for an asset status and click the Update icon in the search results table.

    Note: Only assets with a status of Updateable are available for selection.

  3. Select the check box for any of the available statuses such as:

    • Terminated

    • Status Change Allowed

    • Service Allowed

    • Request Allowed

    • Updateable

    • Pre-Defined

    • EAM Status Change

  4. Optionally enter an Active Start Date.

  5. Optionally enter an Active End Date.

  6. Optionally enter a Description.

  7. Click Save or Apply.

Defining Asset Numbers

Oracle Enterprise Asset Management provides several methods in which you can define a new asset. You can create them individually, copy information from an existing asset, utilize the multiple asset entry method, use the Import Asset Number interface, or use the Asset Number WebADI and Asset Attribute WebADI.

See Creating and Updating Asset Numbers Using the Asset Number WebADI Feature, Oracle Enterprise Asset Management User's Guide and Creating and Updating Asset Attributes Using the Attribute WebADI Feature, Oracle Enterprise Asset Management User's Guide.

You can also use Oracle Web Services to automatically create, update and search for asset numbers. These public interfaces enable you to more easily convert data from another instance or another system. These web services are annotated and available in the I-Repository along with other public Oracle APIs.

Warning: You cannot use “_” or “%” when creating an asset number using Oracle EAM.

In addition, when an asset is received and delivered to inventory, an asset number is created automatically.

Prerequisites

You must set up the following task prior to defining asset numbers in Oracle eAM:

To define assets individually using the EAM responsibility

  1. Navigate to the Define Asset Number window.

    You can also create assets using the Create Asset page located in the Maintenance Super User responsibility (Maintenance Super User > Home > Assets > Create button). See Creating Capital or Rebuildable Assets, Oracle Enterprise Asset Management User's Guide for more information.

    the picture is described in the document text

  2. Enter an asset number or accept or modify the default, if you have automatic number generation enabled (See Defining eAM Parameters).

    After an asset is saved, it cannot be deleted. The asset can be deactivated if there are no open work orders or work requests for the asset, and if the asset is not part of an asset hierarchy.

  3. Optionally enter an Asset Description, up to 240 characters.

  4. Select an asset group. This asset group is associated with this asset.

    Note: After an asset group is associated with an asset and then saved, it can be changed under certain conditions. See Updating Asset Groups for Asset Numbers.

  5. Enter a value in the Asset Serial Number field, or accept the default value that appears if automatic number generation is enabled.

    Note: The Asset Serial Number can be modified to be identical to the asset number.

    The Asset Serial Number might have a non-unique value across organizations, but the asset number must be globally unique, regardless of the defaulting value. When an asset number generates automatically at receipt by the Deliver to Inventory transaction, it defaults to the Item Instance number. You can change it, as long as it is a globally unique number.

  6. Optionally associate this asset to an Asset Category. This is the Class and Subclass code, such as CRANE.OVERHEAD or BUILDING.FLOOR. See Setting Up Category Codes and Sets.

  7. Optionally, change the default value in the Organization field.

    This organization may be different than the eAM-enabled organization that maintains the asset. You can define an asset group and asset number directly in the production organization.

    You can define an asset group in an organization that is not eAM-enabled, if it is associated with an eAM-enabled organization in its Organization parameters.

    In this Define Asset Number window, you can define an asset number for asset groups defined in the eAM-enabled organization itself, and also for asset groups that are defined in organizations that are maintained by the eAM organization, by specifying the organization is this field.

    The list of values includes the eAM-enabled organization, as well as all organizations that are not eAM-enabled but are associated with the eAM-enabled organization in their Organization Parameters.

  8. Within the Main tab, optionally select an owning Department for this asset to represent the crew responsible for the asset.

    Notifications regarding work requests are sent to the Primary Approver of the work request's associated asset's current owning department (See Defining Department Approvers.

  9. Optionally select a Criticality code to indicate the importance of the asset to the organization. This field is for informational purposes.

  10. Optionally select a WIP Accounting Class to identify the Expense cost elements associated with the work performed, such as materials, labor, and resources.

  11. Select an Asset Status to indicate the status of the asset; CREATED is the default value.

  12. Optionally enter the Area where this asset resides.

    This is a user-defined listing of logical areas of work. For example, North Plant, East Wing, or Area 1 (See Setting Up Areas).

  13. Indicate whether this asset is maintainable. If the Maintainable check box is selected, you can create work requests and work orders for this asset.

    For example, you can create an asset for cost-tracking purposes. For example, you might want to view the cost for all top level assets in an asset hierarchy, but you do not want to maintain those assets. In this situation, do not select this check box.

    Note: After work orders are created for this asset, you cannot clear this check box unless those work orders are at Complete, Canceled or Closed statuses.

  14. Optionally select the Active check box to indicate that the asset is functioning, for example, maintenance work orders can be created for this asset.

    This check box changes when you activate or deactivate an asset from the Tools menu.

  15. Select the GIS Assets check box if you want to define the asset as a linear or area asset.

    This field is also available on the Define Rebuildable Serial Number page.

    See Defining GIS Asset Numbers, Oracle Enterprise Asset Management User's Guide or Defining Rebuildable Serial Numbers for more information.

  16. Indicate whether Asset Operational Logging is enabled for this asset.

    If you select the Operation Log Enabled check box, you can view all current and past asset operational information such as Check Out, Check In, associated work requests and work orders. You can remove or add a child asset, remove a parent asset, activate or deactivate the asset, transfer the asset to another location, and receive or issue the asset into and from Inventory. By default, logging is turned off for an asset. See Asset Operational Logging, Oracle Enterprise Asset Management User's Guide.

  17. Within the Parent region, optionally select a parent asset number to establish asset hierarchy information.

    Work order costs roll up through the parent and child hierarchies defined, and can roll up to any level within an asset hierarchy. This enables you to review all cost associated with an asset or asset hierarchal view.

    Note: When a child asset is transferred to another eAM organization, it is still included in the parent hierarchy. The organization that the asset currently resides in appears in parentheses. Transferring the asset does not remove the asset from the asset hierarchy. You must remove the asset manually, to remove the asset from its hierarchy.

  18. The Checked Out check box indicates whether the current asset is checked in or out.

    You can check out an asset to view asset details, enter collection plan data, enter meter information, and optionally create a work request, within Maintenance Super User. This check box is protected against update. See Asset Operational Logging, Oracle Enterprise Asset Management User's Guide.

  19. Within the Location tab, the Subinventory and Locator fields are view-only, displaying the subinventory location of this asset within Inventory and its Locator segments.

    If this asset if received into Inventory, these fields are populated.

  20. Optionally select a Location Code to specify a physical location for this asset.

    The Address field simultaneously populates with the selected Location Code's associated Address. The previously defined area is organization-specific and not associated with a physical location.

    If your asset does not reside in a subinventory, you can specify an external location for it. You can only select an external location that is defined as a HZ location. You may optionally define external locations with a location code.

    Valid Location Codes are defined within Oracle Installed Base.

  21. The Address defaults as the populated Location Code's associated address.

    You can optionally select a different address. If the current asset is in stores, the address of the Location's organization appears (See Stores, Oracle Enterprise Asset Management User's Guide).

  22. Optionally select a Production Organization.

    The list of values displays the production inventory organizations maintained by the current asset's organization. See: Enabling Organizations for Enterprise Asset Management for information on designating eAM organizations to maintain equipment items for designated production organizations.

  23. Select an Equipment Item.

    This is mandatory if you populated the Production Organization field. Items that were defined with an equipment template (See: Item Templates, Oracle Inventory User's Guide ), or with the Equipment item attribute enabled (See: Physical Attributes, Oracle Inventory User's Guide ), are available.

  24. Enter an Equipment Serial Number.

    This is mandatory if you populated the Production Organization field. This is the specific name of the component within the Equipment Type, if an asset resides directly in the Production Organization, and its asset group is defined directly in the Production Organization as Equipment. You can view the Production Organization and the Asset Serial Number fields, but you cannot update them.

  25. Use the Location tab to specify the geocode information with details of latitude, longitude, direction, and ESRI reference details for the asset.

    This information is used to display the assets in the chosen map viewer. If both longitude and latitude and ESRI references are provided, the ESRI Feature and Feature ID would be used to plot the asset on the map, and the latitude and longitude fields would be ignored.

    If you are using the ESRI integration, you can alternatively enter values in the following fields rather than enter Latitude and Longitude to display assets on a map.

    • ESRI Feature: These values are defined on the ESRI Map Manager page.

      This value is referenced to a published Feature table which has a Point shape from the ESRI system.

    • ESRI Feature ID: The specific ESRI reference identifier from the selected ESRI Feature table which has a corresponding Point geometry.

      If the Latitude, Longitude and ESRI fields are entered, then the ESRI related fields take priority and are used to display assets on a map.

    Note: Geocode entry and ESRI Feature associations are enabled for point assets only and are not applicable for GIS assets.

    See Using Map Manager, Oracle Enterprise Asset Management Implementation Guide for more information regarding the ESRI Map Manager fields.

    the picture is described in the document text

  26. Optionally enter the Number if Oracle Fixed Assets is installed.

    This represents a fixed asset number that belongs to a fixed asset category, associated with the asset.

  27. The Property Management fields, Location Name and Location Code default values come from a Property Manager export process (Export Locations to Enterprise Asset Management), if Oracle Property Management is installed.

    These fields are display only and cannot be changed.

    Important: Asset groups must be defined before information is passed from Property Manager into Enterprise Asset Management. See Defining Asset Groups.

  28. Optionally choose Location Details to view or update Property Manager field information.

  29. You can indicate if an asset is a positional asset or a lockout device.

    Note: You can leave the field blank (no value) or indicate if the asset is a positional asset or a lockout device, but not both.

    Click the Safety tab to enter values for the positional asset or to indicate if the asset will be associated with a lockout device used during isolation. See Defining Positional Assets, Oracle Enterprise Asset Management User's Guide.

  30. Optionally click the Attributes button to enter attribute values for the asset (See: Setting Up Attributes).

    Existing, enabled attribute groups appear. These attribute groups are optional. You do not need to enter values for all existing attribute groups. From this window, you cannot generate attribute groups.

    Asset Attributes

    the picture is described in the document text

  31. You can choose Resource Usage if the fields in the Production Equipment region are populated.

    This enables you to view production work orders using the equipment that corresponds with this asset number as a resource.

    Resource Usage

    the picture is described in the document text

  32. Click the GIS Asset Workbench to enter GIS (linear and area) asset details.

    See Using the GIS Asset Workbench, Oracle Enterprise Asset Management User's Guide for more information.

  33. Optionally select Associate Activity to directly associate this asset with an asset group. See Activity Association Templates.

    Activity Association

    the picture is described in the document text

  34. Optionally enter file, URL, or text attachments to this asset by choosing the paperclip Attachments icon.

    You can then choose Document Catalog to add asset specific documents. See Defining Asset Documents.

  35. Save your work.

To copy assets from existing assets

You can copy asset information from existing assets.

When using this method, everything copies to the new asset, including attributes and attachments. Equipment serial numbers are not copied. You are prompted to enter the Equipment Serial Number, when saving.

  1. Navigate to the Define Asset Number window.

  2. Select an asset group. This asset group is associated with this asset.

  3. Enter an asset number if you do not have them automatically generated, or accept or modify the default, if you have automatic generation enabled. (See: Defining eAM Parameters).

    After an asset has been saved, it cannot be deleted. The asset can be deactivated if there are no open work orders or work requests for the asset, and if the asset is not part of an asset hierarchy.

  4. Optionally enter an Asset Description up to 240 characters.

  5. From the Tools menu, select Copy Asset Number from.

  6. Select the asset.

  7. Optionally associate this Asset to an Asset Category. This is the Class and Subclass code, such as CRANE.OVERHEAD, or BUILDING.FLOOR. See: Setting Up Category Codes and Sets.

  8. Select an owning Department for this asset.

    Email notifications regarding work requests are sent to the Primary Approver of the owning department for the associated asset (See: Defining Department Approvers.

  9. Save your work.

To access failure analysis information

You can access the Failure Set page to view failure tracking codes that are assigned to the current asset number.

  1. From the Define Asset Number window, select Maintain Failure Set from the Tools menu.

    If the asset number does not have an associated Failure Set, this menu option is disabled. See: Defining Failure Codes and Sets, Oracle Enterprise Asset Management User's Guide and Failure Analysis Overview, Oracle Enterprise Asset Management User's Guide.

  2. Close the window.

To deactivate an asset

  1. Navigate to the Define Asset Number window.

  2. Select the flashlight Find icon to display the Find Asset Number window.

  3. Select an asset number to deactivate.

  4. From the Tools menu, select De-Activate Asset Number.

  5. Save your work.

Important: An asset cannot be updated unless it is in an Active state. Therefore, any simultaneous updates to the asset will reactivate the asset.

To activate an asset

  1. Navigate to the Define Asset Number window.

  2. Select the flashlight Find icon to display the Find Asset Number window.

  3. Select a Deactivated Asset Number to activate.

  4. From the Tools menu, select Re-Activate Asset.

  5. Save your work.

Defining Location Hierarchies for Assets

A functional location is an organizational unit that structures the maintenance objects of an organization to functional, process-related or spatial criteria. In Oracle Enterprise Asset Management, a functional location represents the place at which a maintenance task is to be performed. The functional location hierarchy represents the list of assets that are impacted by the maintenance tasks based on a physical location.

Follow these steps to define information used with location hierarchies:

1. Define the lookups for functional location hierarchy types

  1. Navigate to the Manufacturing Lookups page (Enterprise Asset Management > Setups > Lookups).

  2. Review the seeded values; you cannot delete these values, but you can change the description and effective dates.

  3. Enter values for additional lookups to be used by your organization.

    the picture is described in the document text

  4. Click Save.

2. Define the functional hierarchy positions

After you have defined the hierarchical lookup values, you will define the position codes for the hierarchy.

  1. Navigate to the Functional Hierarchy page (Maintenance Super User > Assets > Asset Setups > Functional Hierarchy).

  2. Click the Define Functional Hierarchy button.

  3. Enter values on the page:

    1. Hierarchy Type (required)

    2. Hierarchy Description (optional)

    3. Position Code (required)

    4. Description (optional)

    5. Parent Position Code and Parent Code Description (optional)

    the picture is described in the document text

  4. Click Apply.

3. Associate asset numbers to the functional hierarchy

The final setup step is to associate the asset numbers to the functional hierarchy. You can perform this association when you create or update the asset number.

  1. Navigate to the Asset Numbers page (Maintenance Super User > Assets > Asset Numbers).

  2. Search for an asset number.

  3. Click the Update Asset icon for the asset number.

  4. Select values in the fields for Hierarchy Type and Position Code in the Functional Hierarchy region of the page.

    the picture is described in the document text

  5. Click Apply.

For more information about viewing functional location hierarchies, see To view a functional location hierarchy for an asset, Oracle Enterprise Asset Management User's Guide.

Updating Asset Groups for Asset Numbers

You can update the asset group for an asset number after it has been created and saved. This update can be performed using the Define Asset Number form and Update Asset Number HTML page.

You can update an asset group even if the following setups or associations exist for the asset number:

However, you cannot update the asset group if:

Note: You cannot update an asset group for an asset route.

For Assets With Work History - Special Considerations

  1. Navigate to the Define Asset Number page (Enterprise Asset Management > Assets > Asset Numbers).

  2. Search for the asset number that you want to update.

  3. Click the search button next to the Asset Group field.

    The Asset Group page appears.

  4. Search for the new asset group using the % wildcard to view all valid asset groups associated with the organization, or enter a specific asset group value.

    Select the new asset group. The new asset group name and description appear.

  5. Click the Save button.

  6. Upon save, the following occurs:

    • If the asset is serial controlled, the original asset serial number does not change.

    • A new item instance is created in Oracle Installed Base.

Transaction History in Oracle Installed Base

The transaction history will capture the asset group updates performed on the asset number.

Defining Asset Routes

You might need to perform an activity on multiple asset numbers. To eliminate the possibility of creating multiple work orders for the same activity, you can define asset routes. You can define a Preventive Maintenance schedule for your asset route to specify when an activity should be scheduled for the asset route. You can define day interval rules for asset routes.

To define asset routes

  1. Navigate to the Define Asset Route window.

    Define Asset Route

    the picture is described in the document text

  2. Enter the name of the asset route in the Asset Number field.

  3. Select an Asset Group.

  4. The Asset Serial Number defaults to the asset number.

    You can optionally select the next serial number for the current organization. The Asset Serial Number might have a non-unique value across organizations, but the asset number must be globally unique, regardless of the defaulting value.

  5. Optionally associate this asset route to an Asset Category.

    This is the Class and Subclass code, such as CRANE.OVERHEAD or BUILDING.FLOOR. See Setting Up Category Codes and Sets.

  6. Within the Main tab, optionally select an owning Department for this asset route.

    This represents the crew responsible for the asset. Notifications, regarding work requests, are sent to the Primary Approver of the work request's associated asset's current owning department (See Defining Department Approvers and Defining Asset Numbers).

  7. Optionally select a Criticality code to indicate the importance of the asset route to the organization.

    This field is for information purposes.

  8. Optionally select a WIP Accounting Class to identify the Expense cost elements associated with the work performed, such as materials, labor, and resources.

  9. Select an Asset Status.

    This field represents the current status of the asset route.

  10. Optionally enter the Area where this asset route resides.

    This is a user defined listing of logical areas of work, for example, North Plant, East Wing, or Area 1. (See Setting Up Areas).

  11. Indicate whether this asset route is maintainable.

    If the Maintainable check box is selected, you can create work requests and work orders for this asset route.

  12. Optionally select the Active check box to indicate that the asset route is functioning.

    This check box changes when you activate or deactivate an asset route from the Tools menu.

  13. The GIS Asset option is unavailable.

    Note: You cannot define an asset route as a GIS asset.

  14. Choose Asset Route to display the Asset Route window.

    Asset Route

    the picture is described in the document text

  15. In the Associated Asset Numbers region, select an Asset Group.

  16. Select an asset number.

    Asset numbers associated with the previously selected asset group are available. You can associate an unlimited number of asset numbers.

  17. Optionally enter vales for the Effective Dates fields.

    If the Effective Date From field is left blank, the system date defaults.

  18. Save your work.

    Note: Asset numbers can be associated with asset routes. An asset route cannot be associated with another asset route.

Setting Up Asset Bills of Material

You can identify and select the required items that make up an asset. A bill of material (BOM) is used to list all items and components that make up a particular asset, and is defined for each asset group. The items defined on an asset BOM are standard inventory components (See: Defining Items, Oracle Inventory User's Guide).

Note: Even if you are not using Project Manufacturing applications, Project Parameters are defined for your eAM enabled organization to successfully create asset groups. This is required because an Asset BOM is of type Model/Unit Effective and this BOM type is currently allowed if PJM organization parameters are set up for the eAM enabled organization to which the asset group has been assigned. To define Project Parameters, open the Project Parameters window using Project Manufacturing Super User responsibility and without entering any data in the window, save the record. If you plan to use Project Manufacturing, see: Project Manufacturing Integration Setup for information on defining Project Parameters.

To set up an Asset BOM

  1. Navigate to the Bills of Material window.

    Bills of Material

    the picture is described in the document text

  2. Select an asset group from the Item list of values.

  3. Within the Main tab, the Item Sequence and an Operation Sequence values default.

  4. Enter the inventory Component to make up the asset number.

  5. Enter the Quantity of that component necessary for the asset.

  6. Select the Serial Effectivity tab.

    Bills of Material - Serial Effectivity

    the picture is described in the document text

  7. Select the asset number (asset numbers are always serialized) that the inventory items are associated with, in the From and To fields.

    Asset numbers associated with the current asset group are available.

    If the component is installed in all asset numbers within the asset group, enter 0 in the From field, and leave the To field blank.

  8. Optionally select the Material Control tab, and enter a subinventory location or source locator for this asset BOM.

    If the Auto Request Material option is selected at the BOM level, material allocation will be initiated when the work order is released, and the source subinventory and source locator values you enter will override these values in the Inventory sourcing rules. If the Auto Request Material option is not selected, you can specify a source subinventory and source locator for your material when you perform a material request or a One-Step Material Issue transaction.

    Material Control

    the picture is described in the document text

  9. Save your work.

    For information on all remaining fields, See: Creating a Bill of Material, Oracle Bills of Material User's Guide.

Reapplying Activity, Meter and PM Templates Simultaneously

You can reapply all activity, meter and PM templates for assets that do not have existing templates attached. You can perform the reapplication using a concurrent program.

To apply activity, meter and PM templates simultaneously

  1. Navigate to the Apply Asset Template form (Enterprise Asset Management > Assets > Reapply Asset Template).

  2. Enter values in the following required fields:

    1. Asset Type: Capital or Rebuildable

    2. Asset Group: Select an asset group to which you want to apply all templates.

    3. Template Type: All

    Reapply Asset Template - All

    the picture is described in the document text

  3. Optionally select Yes in the View Only field if you do not want the system to apply the templates; a log is generated but the templates are not reapplied to the assets. The default value is No.

  4. Click the OK button.

To reapply meter templates only, see Reapplying a Meter Template to an Asset Group.

Related Topics

Defining Activities, Oracle Enterprise Asset Management User's Guide

Using the Activity Workbench, Oracle Enterprise Asset Management User's Guide

Rebuildable/Activity Association, Oracle Enterprise Asset Management User's Guide

GIS Asset Setup

The following setup steps must be performed to use the GIS assets feature:

  1. Enable the EAM: Enable GIS asset functionality profile option. See Profile Option Details.

  2. Define GIS asset reference UOM and UOM Classes. See Defining GIS Asset Reference UOM and UOM Classes.

  3. Define GIS asset reference methods. See Defining Reference Methods.

The following setups are optional:

Defining GIS Asset Reference UOM and UOM Classes

Define reference UOM and UOM classes for GIS assets:

See Defining Units of Measure, Oracle Inventory User's Guide for more information.

Defining Reference Methods

Reference methods indicate the manner in which GI assets are identified in the system using criteria such as X and Z references, and offset units of measure.

Use the Create Reference Method page to create reference methods.

  1. Navigate to the Create Reference Method page (Maintenance Super User > Maintenance Home > Assets > GIS Assets > Reference Methods > Create Reference Method).

    Create Reference Method page

    the picture is described in the document text

  2. Enter or select values in the following fields:

    • Reference Method Code (required)

    • Reference Method Name (required)

    • Reference UOM (required)

    • Active Start Date (required)

    • Active End Date (optional)

    • Y references (optional)

    • Z references (optional)

    • X Offset UOM (optional)

    • Y Offset UOM (optional)

    • Z Offset UOM (optional)

    • Description (optional)

    • Context Value (optional)

  3. Click Save or Apply.

Defining Y References

GIS asset Y references describe the vertical (up-down or North-South) reference point for the GIS asset. GIS asset Y references are user-defined.

To define Y references for GIS assets

  1. Navigate to the Manufacturing Lookups page (Enterprise Asset Management > Setup > Lookups).

  2. Click the Find icon.

  3. Select EAM_LAM_Y_REFERENCE from the Type list of values.

    GIS Asset Y References

    the picture is described in the document text

  4. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

  5. Enter the Meaning.

  6. Enter a Description.

  7. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  8. The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration date for the code.

  9. Select the Enabled check box to enable this code for Enterprise Asset Management.

  10. Save your work.

Defining Z References

GIS asset Z references describe the location (above or below) the GIS asset. GIS asset Z references are user-defined.

To define Z references for GIS assets

  1. Navigate to the Manufacturing Lookups page (Enterprise Asset Management > Setup > Lookups).

  2. Click the Find icon.

  3. Select EAM_LAM_Z_REFERENCE from the Type list of values.

    GIS Asset Z References

    the picture is described in the document text

  4. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

  5. Enter the Meaning.

  6. Enter a Description.

  7. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  8. The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration date for the code.

  9. Select the Enabled check box to enable this code for Enterprise Asset Management.

  10. Save your work.

Defining X, Y, and Z Offset Units of Measure

The GIS asset feature of Oracle Enterprise Asset Management uses units of measure for the following offsets:

Define X, Y and Z offset UOMs using the Units of Measure page (Inventory > Setup > Units of Measure > Units of Measure).

See Defining Units of Measure, Oracle Inventory User's Guide for more information.

Defining Direction Types

Direction types are used to identify the location of the GIS asset in relationship to the GIS asset reference method. You can define directions such as Same, Opposite, North, South, and so on. For example, using the Pipe Line Reference method, Asset XYZ-Pipeline has a direction of South, indicating that the GIS asset is south of the Pipe Line Reference. Direction types are user defined.

To define GIS asset direction types

  1. Navigate to the Oracle Manufacturing Lookups window.

  2. Click the Find icon.

    GIS Asset Direction Types

    the picture is described in the document text

  3. Select EAM_LAM_DIRECTION_TYPE from the Type list of values.

  4. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  5. Enter the Meaning, for example, Opposite.

  6. Enter a Description.

  7. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  8. The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration date for the code.

  9. Select the Enabled check box to enable this code for Enterprise Asset Management.

  10. Save your work.

Defining GIS Asset Map Entity Event Types

Map Entity Event Types are user-defined.

To define map entity event types

  1. Navigate to the Oracle Manufacturing Lookups window.

  2. Select EAM_LAM_MAP_ENTITY_EVENT_TYPE from the Type list of values.

    GIS Assets Map Entity Event Types

    the picture is described in the document text

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning, for example, Properties.

  5. Enter a Description.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Defining GIS Assets Map Entity Types

Map Entity Types are user-defined.

To define map entity event types

  1. Navigate to the Oracle Manufacturing Lookups window.

  2. Select EAM_LAM_MAP_ENTITY_TYPE from the Type list of values.

    GIS Assets Map Entity Types

    the picture is described in the document text

  3. Enter a numeric Code.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning, for example, Organization and Site.

  5. Enter a Description.

  6. Optionally enter a Tag to categorize lookup values.

    This field is for informational purposes.

  7. The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Defining Map Visualization Entities

Assets, work orders and GIS asset attributes can be visualized on a map. GIS geometric shape entities such as GIS asset and GIS asset attributes require a line style; point geometry entities such as discrete asset require icons to be visualized on a map.

These map visualizations are user-defined, and can have specific line styles and icons defined for various entities. Related line styles or icons are used to display the entities on a map depending on whether they are linear or point.

You can define visualization entities for:

Defining Map Visualizations for Assets

Follow these steps to define line styles and icons for assets and asset groups to be displayed on a map:

To define map visualizations for assets and asset groups

  1. Navigate to the Define Map Visualization for Asset page (Maintenance Super User > Home > Assets > GIS Assets > Map Visualization Setup > Assets).

    The Map Visualization for Asset page appears.

  2. Click the Define Map Visualization button.

  3. Enter values in the following fields:

    • Asset Group (required)

    • Asset Number (optional): If this field is left blank, then the map visualization setup applies to all assets in the asset group.

      You can define map visualization for an asset group and a specific asset number.

      Note: Map visualization defined for a specific asset number takes priority over map visualization defined at the Asset Group level.

    • Icon Code

    • Line Style Code

    • Active Start Date

    • Active End Date (optional)

  4. Click Save or Apply.

Defining Map Visualizations for Asset Status

  1. Navigate to the Define Map Visualization for Asset Statuses page (Maintenance Super User > Home > Assets > GIS Assets > Map Visualization Setup > Asset Status).

  2. Enter values in any of the following fields:

    • Asset Status (required)

    • Icon Code

    • Line Style Code

    • Active Start Date

    Important: Map visualization defined for the Asset Status would be used even if map visualization is defined at the Asset Number or Asset Group level.

    Asset Status map visualization is the highest priority when displaying assets.

  3. Click Save or Apply.

Defining Map Visualizations for Work Order Status

  1. Navigate to the Define Map Visualization for Work Order Statuses page (Maintenance Super User > Home > Assets > GIS Assets > Map Visualization Setup > Work Order Status).

  2. Enter values in any of the following fields:

    • Work Order Status (required)

    • Icon Code

    • Line Style Code

    • Active Start Date

  3. Click Save or Apply.

Defining Map Visualizations for Element Types

  1. Navigate to the Define Map Visualization for Elements page (Maintenance Super User > Home > Assets > GIS Assets > Map Visualization Setup > Element Type).

  2. Enter values in any of the following fields:

    • Element Type (required)

    • Icon Code

    • Line Style Code

    • Active Start Date

  3. Click Save or Apply.

Defining Map Visualizations for Property Types

  1. Navigate to the Define Map Visualization for Properties page (Maintenance Super User > Home > Assets > GIS Assets > Map Visualization Setup > Property).

  2. Enter values in any of the following fields:

    • Property (required)

    • Property From Value

    • Property To Value

    • Icon Code

    • Line Style Code

    • Active Start Date

  3. Click Save or Apply.

GIS Assets Map Visualization Setup: Integration Options

GIS assets are defined as:

Important: Entering the length and measure while associating GIS geometry to EAM asset segments is optional. Currently, this feature is enabled for ESRI integration.

The geometric shape of GIS assets can be visualized on a map. The geometry must be mapped to GIS asset using the GIS Asset Workbench to enable the visualization of the assets on a map. The mapping of the geometry profile associated to the GIS assets details by mapping integration option that you choose to implement.

You can use one of the following integration options:

Prerequisites

Related Topics

Profile Option Details

GIS Assets Map Integration, Oracle Enterprise Asset Management User's Guide

Enabling the Indoor Map Workbench Menu

Oracle EAM provides you the ability to visualize indoor GIS assets on a map workbench. Before you can use this feature, the page must be enabled.

To enable the Indoor Map Workbench

  1. Navigate to the Menus window (System Administrator > Application > Menu).

  2. Click in the User Menu Name field, and click the Find button (flashlight).

  3. Enter EAM Maintenance Unit Search in the Find User Menu Name window, and click Find.

  4. Select the value, and then click OK.

    The system populates the window.

  5. Scroll to the Indoor Map Workbench value, and select the Grant check box.

  6. Click the Save button.

The Indoor Map Workbench link appears on the Assets tab (Maintenance Super User > Maintenance Home > Assets). See Using the Indoor Map Workbench, Oracle Enterprise Asset Management User's Guide.

Using the Activity Workbench

You can use a central workbench to manage your organization's activity functions. Using the Activity Workbench, you can view, create (See: Defining Activities), query, and manage all of your activities. From this central workbench, you can view, create, and update maintenance routes, maintenance BOMs, Preventive Maintenance schedules, and suppressions associated with your activities. You can create various copy functions within a single activity, across multiple Activities, as well as between work orders and activities or asset activity associations. You can view or update Last Service for the asset activity association, as well as view cost estimates for the activity. These copy functions save time and standardize processes across your organization.

This section includes the following topics:

Defining Activities

There are three methods you can use to create an activity:

To set up activities using the Activity Workbench

  1. Navigate to the Activity Workbench window.

  2. Click the Launch button.

    Activity Association

    the picture is described in the document text

  3. To create an activity, select New.

    Create Activity

    the picture is described in the document text

  4. Enter an Activity Name.

  5. Enter an Activity Description.

  6. Choose an activity Template. This automatically links the properties associated with an activity. The @Activity template is created for you. You can create your own Activity Templates, as well.

  7. Within the Activity Properties region, optionally select an Activity Type (See: Activity Types). The value defaults from the Template properties above.

  8. Within the Activity Properties region, optionally select an Shutdown Type. The Shutdown Type is user defined, and indicates whether an activity shutdown is required. For example, the Shutdown Type can refer to whether the Asset Activity association shutdown is required before the activity is performed. The value defaults from the Template properties above. This field is for information purposes.

  9. Within the Activity Properties region, optionally select an Activity Cause (See: Activity Causes). The value defaults from the Template properties above.

  10. Within the Activity Properties region, optionally select an Activity Source (See: Activity Sources). The value defaults from the Template properties above.

  11. The Activity Notification check box is informational until a future release.

  12. You can optionally create an activity by copying it from another activity or a work order. Within the Copy Options region, select the entity to copy information from. Valid values are Activity and Work Order. If you select Activity, the values within the Activity region are relevant, and the values within the Work Order region are irrelevant. If you select Work Order, the values within the Work Order region are relevant, and the values within the Activity region are irrelevant.

  13. Within the Activity region, if Activity is populated in the Copy From field, optionally select an Activity name. This is the activity from which you are copying.

  14. Within the Activity region, if Activity is populated in the Copy From field, optionally select the BOM check box to indicate that the Maintenance Bill of Material, associated with the current activity within the Activity region, copies to the new Activity Name.

    For example, in the screen shot, the Maintenance Bill of Material, associated with the 3000 Mile Truck Maint, copies to Oil Change.

  15. Within the Activity region, if Activity is populated in the Copy From field, optionally select the Routing check box to indicate that the routings associated with the current activity within the Activity region copies to the new Activity Name.

    For example, in the screen shot, routings that are associated with the 3000 Mile Truck Maint copy to Oil Change.

  16. Within the Activity region, if Activity is populated in the Copy From field, select All or None from the Association list of values.

    • All: All asset and rebuildable associations related to the current activity within the Activity region copy to the new activity.

    • None: No asset and rebuildable associations related to the current activity within the Activity region copy to the new activity.

  17. Within the Work Order region, if the work order number is populated in the Copy From field, select an existing maintenance work order.

  18. Within the Work Order region, if the work order number is populated in the Copy From field, select All or None from the Operation list of values.

    • All: All operations associated with the current work order, populated in the Work Order field, copy to the new activity.

    • None: No operations associated with the current work order, populated in the Work Order field, copy to the new activity.

  19. Within the Work Order region, if the work order number is populated in the Copy From field, select All, Issued, or None from the Material list of values.

    • All: All material associated with the current work order, populated in the Work Order field, copies to the new activity.

    • Issued: Material issued to the current work order, populated in the Work Order field, copies to the new activity.

    • None: No material associated with the current work order, populated in the Work Order field, copies to the new activity.

  20. Within the Work Order region, if the work order number is populated in the Copy From field, select All, Issued, or None from the Resource list of values.

    • All: All resources associated with the current work order copy to the new activity.

    • Issued: Resources issued to the current work order copy to the new activity.

    • None: No resources associated with the current work order copy to the new activity.

  21. Within the Work Order region, if Work Order is populated in the Copy From field, select None, Current, or All from the Association list of values.

    • None: No Assets and Rebuildables, associated with the current work order, associate with the new activity.

    • Current: An Asset and/or Rebuildable, associated with the current work order, associates with the new activity.

    • All: All Assets and/or Rebuildables, associated with the current work order's activity, associate with the new activity.

  22. Save your work.

    After saving, the new activity is automatically assigned to the current organization.

Navigating the Activity Workbench

The Activity Workbench enables you to manage all of your organization's activity functions. Before launching the Activity Workbench, you can narrow your data selection; the Activity Workbench provides a query capability as you enter the Activity Workbench. The top portion of the window enables you to query by Asset Type, Asset Number, Asset Group, Area, Asset Category, Owning Department, and provides you the choice of including child assets within asset hierarchies. The bottom portion of the window enables you to query by activity, Activity Type, Activity Source, Shutdown Type, and Activity Cause. You can also select data that is between specified effective dates.

To navigate the Activity Workbench

  1. Navigate to the Activity Workbench window.

  2. Optionally narrow your data selection by selecting criteria within the Activity Workbench window.

    If you make selections, you can view those selections after you launch the Activity Workbench.

  3. Choose Launch.

  4. Optionally select the Results (Capital) tab.

  5. Optionally expand the Results (Capital) folder.

    • Optionally expand the All Assets folder to display all asset number, based on your chosen selection criteria.

      You can select an asset and view related activity information within the corresponding Activity Associations window. Within the corresponding Activity Associations window, you can associate activities with the current asset.

    • Optionally expand the Assets with Activities folder to display all asset number that are currently associated with one or more activities, based on your chosen selection criteria.

      You can select an asset and view its related activity information within the corresponding Activity Associations window. Within the corresponding Activity Associations window, you can view, create, or update preventive maintenance schedule definitions, create or update Suppression definitions, view or update last service information, view the parts list, and view or update the maintenance routing.

      You can also view Work Order Default information such as:

      • Activity Cause: Defaults from the Activity definition, specifying what situation caused this work to generate. For example, Breakdown, Vandalism, Normal Wear, or Settings.

      • Activity Type: Defaults from the Activity definition, indicating the type of maintenance activity to perform for this activity, and is used during job definition.

        This code should remain generic, and should not describe the job in detail. For example, Inspection, Overhaul, Lubrication, Repair, Servicing, or Cleaning. Optionally, you can select an activity type.

      • Tagging Required: Select this check box to indicate whether tagout procedures are required.

        The area may need securing for operations required for carrying out a work order. Tags are generally printed and placed on an asset, warning the plant that the asset is shutdown, and should not be started. This check box helps the planner isolate those jobs that require a tagout. This is for informational purposes.

      • Owning Department: Defaults from the asset number definition and indicates a planner or supervisor who is responsible for the activity or asset.

      • Shutdown Type: This value defaults from the Master Activity information that was created within the Master Item window.

        This option indicates whether a shutdown is necessary to perform this maintenance activity, for example, Required or Not Required. This field is for informational purposes.

      • WIP Accounting Class: Defaults from the eAM Parameters information for the current organization; you can update this value.

      • Activity Source: This value defaults from the Master Activity information created in the Master Item window.

        Activity source codes are the reasons why activities are executed, for example, Warranty Compliance, OSHA Compliance, or Military Specification Requirements.

      • Work Order Type: Select a value to differentiate work orders. For example, Routine, and Rebuild. Maintenance management can use this information to sort and monitor work activity for reporting and budgeting.

      • Planner: Select a planner to be assigned to the work order.

      • Firm: Select to indicate the work order is to be firmed and planning and scheduling will not automatically adjust the schedule, regardless of material or resource availability.

      • Planned: Select to indicate that this is a planned order.

      • Notification: Select if a notification is to be generated.

    • Optionally expand the Routes folder to display all asset routes that are currently associated with one or more activities, based on your chosen selection criteria.

      You can select an asset route and view related activity information within the corresponding Activity Associations window.

  6. Optionally select the Results (Rebuildable Inventory) tab.

  7. Optionally expand the Results (Rebuildable Inventory) folder.

  8. Optionally expand the All Rebuildables folder.

    • Optionally expand the Serialized folder to display all Rebuildable Serial Numbers, based on your chosen selection criteria, within the Activity Workbench window.

      You can select a Rebuildable Serial Number and view related activity information within the corresponding Activity Associations window. Within the corresponding Activity Associations window, you can associate activities to the current Rebuildable Serial Number.

    • Optionally expand the Non-serialized folder to display all Non-serialized Rebuildables, based on your chosen selection criteria, within the Activity Workbench window.

      You can select a Non-serialized Rebuildable and view related activity information within the corresponding Activity Associations window. Within the corresponding Activity Associations window, you can associate activities to the current Serialized Non-rebuildable.

  9. Optionally select the Rebuildables with Activities folder.

    • Optionally expand the Serialized with Activities folder to display all Rebuildable Serial Numbers that are currently associated with one or more activities, based on your chosen selection criteria, within the Activity Workbench window.

      You can select a rebuildable serial number and view related activity information within the corresponding Activity Associations window. Within the corresponding Activity Associations window, you can create or update preventive maintenance schedule definitions, create or update Suppression definitions, view or update last service information, view the parts list, view or update the maintenance routing, and view cost estimations for a rebuildable serial number and activity combination.

    • Optionally expand the Non-serialized with Activities folder to display all non-serialized rebuildables that are currently associated with one or more activities, based on your chosen selection criteria, within the Activity Workbench window.

      You can select a non-serialized rebuildable and view related activity information within the corresponding Activity Associations window. Within the corresponding Activity Associations window, you can create or update preventive maintenance schedule definitions, create or update Suppression definitions, view or update last service information, view the parts list, view or update the maintenance routing, and view cost estimations for a non-serialized rebuildable and activity combination.

  10. Optionally select the Results (Activities) tab.

  11. Optionally expand the All Activities folder to display all valid activities, based on your chosen selection criteria, within the Activity Workbench window.

    You can select an activity and view its related activity information within the corresponding Activity Associations window, if an association exists. You can associate an asset number with the current, selected activity using the corresponding Activity Associations window. You can select an activity within the Activity Workbench pane, and then view its related information within the corresponding Activity Associations window. For a selected activity, you can create a new activity, create or update its associated Maintenance Routing, create or update the associated maintenance BOM, and view cost estimations.

  12. Optionally expand the Activities with Association folder to display all activities that are associated with an asset number, based on your chosen selection criteria, within the Activity Workbench window.

    You can select an activity within the Activity Workbench pane, and then view its related information within the corresponding Activity Associations window. For a selected activity, you can create a new activity, create or update its associated maintenance routing, create or update the associated maintenance BOM, and view cost estimations.

To create or update a PM schedule definition

You can view, create or update a Preventive Maintenance (PM) Schedule definition for activity and asset number, and activity and asset route combinations.

  1. Within the Activity Workbench pane, select any one of the three tabs: Results (Capital), Results (Rebuildable Inventory), or Results (Activities).

  2. If you selected Results (Capital), expand either the Assets with Activities or Routes folders, then select an asset number or route, respectively.

    You cannot create or update a PM Schedule definition for an asset number that is not associated with an activity.

    If you selected Results (Rebuildable Inventory), expand the Rebuildables with Activities folder, expand either the Serialized with Activities or Non-serialized with Activities folder, then select a serialized or non-serialized rebuildable, respectively.

    You cannot create or update a PM Schedule definition for an asset number that is not associated with an activity.

    If you selected Results (Activities), expand the Activities with Association folder, then select an activity.

  3. Select Preventive Maintenance.

    The PM Schedules window displays all PM Schedule definitions for the current activity and asset number, or activity and asset route combination.

    1. Optionally choose New to create a new PM Schedule definition.

      the picture is described in the document text

    2. Optionally choose Last Service Information to create or update Last Service Information.

    3. Optionally choose Suppression to create or update a suppression definition, associated with the current activity and asset number, or activity and asset route combination.

    4. Optionally select a PM Schedule definition, and then choose Open to view its details.

  4. Close the window.

  5. Save your work.

To create or update an activity suppression

You can view, create, or update suppression definitions for activity and asset number, or activity and asset route combinations.

  1. Within the Activity Workbench pane, select any one of the three tabs: Results (Assets), Results (Rebuildables), or Results (Activities).

  2. If you selected Results (Assets), expand either the Assets with Activities or Routes folders, then select the asset number or route, respectively.

    You cannot create or update a suppression definition for a asset number that is not associated with an activity.

    If you selected Results (Rebuildables), expand the Rebuildables with Activities folder, expand either the Serialized with Activities or Non-serialized with Activities folder, then select a serialized or non-serialized rebuildable, respectively. You cannot create or update a suppression definition for a asset number that is not associated with an activity.

    If you selected Results (Activities), expand the Activities with Association folder, then select an activity.

  3. Choose Suppression.

  4. Add or update the Suppression Activity associated with the current activity.

    the picture is described in the document text

  5. Save your work.

To view or update last service information

You can view or update last service information for activity and asset number, or activity and asset route combinations.

  1. Within the Activity Workbench pane, select any one of the three tabs: Results (Assets), Results (Rebuildables), or Results (Activities).

  2. If you selected Results (Assets), expand either the Assets with Activities or Routes folders, then select the asset number or route, respectively.

    If you selected Results (Rebuildables), expand the Rebuildables with Activities folder, then expand either the Serialized with Activities or Non-serialized with Activities folder, and finally select a Serialized or Non-serialized Rebuildable, respectively.

    If you selected Results (Activities), expand the Activities with Association folder, then select an activity.

  3. Choose Last Service to view or update last service information.

    the picture is described in the document text

  4. Save your work.

To view estimated cost information

You can view estimated cost information for an activity. Estimating activity costs is often necessary for planning and budgeting purposes.

  1. Within the Activity Workbench pane, select any one of the three tabs: Results (Assets), Results (Rebuildables), or Results (Activities).

  2. If you selected Results (Assets), expand either the Assets with Activities or Routes folders, then select the asset number or route, respectively.

    If you selected Results (Rebuildables), expand the Rebuildables with Activities folder, then expand either the Serialized with Activities or Non-serialized with Activities folder, and finally select a Serialized or Non-serialized Rebuildable, respectively.

    If you selected Results (Activities), expand the Activities with Association folder, then select an activity.

  3. Choose Cost Estimate to view the activity's cost estimation information.

    the picture is described in the document text

Setting Up Maintenance Bills of Material

You can identify and select the required items used by an activity. A bill of material (BOM) is used to list all inventoried or Direct Items needed to perform a particular activity, and is defined for each activity. For example, you might have an activity titled, Fork Lift Daily Maintenance. The items necessary to perform this activity include water, fork lift lubrication oil, filled propane tanks, and shop rags. As maintenance BOMs are created, they are associated to an activity.

When a work order is created for an activity, the Maintenance BOM corresponding to the activity explodes to the work order all components specified in the maintenance BOM are copied to the work order as material requirements.

To set up a maintenance BOM

  1. Navigate to the Activity Workbench window.

  2. Choose Launch.

  3. Within the Activity Workbench pane, select the activity for which you wish to define the Bill of Material.

  4. Choose BOM.

    the picture is described in the document text

  5. Select an activity from the Item field list of values.

  6. Select the Main tab. The Item Sequence defaults.

  7. Enter the Operation Sequence that this Component (material item necessary for the operation sequence, NOT rebuildable item) is needed for (See: Defining Maintenance Routes).

  8. Enter necessary Components and their Quantities that are required to perform the activity. You can enter an unlimited number of inventory and non-inventory, direct items.

    Note: The Purchasing tab is enabled for Maintenance and Asset Bills of Material, and contains attributes specific to non-stockable, inventory items.

  9. Optionally select the Auto Request Material check box to indicate that requisitions and purchase orders are created automatically, for the current component or Direct Item, when the work order is released.

  10. Optionally select the Date Effectivity tab to specify effectivity dates per component.

  11. Save your work.

    For information on all remaining fields, See: Creating a Bill of Material, Oracle Bills of Material User's Guide

    For information on defining activities using the Activity Workbench, See: Defining Activities.

Associating Asset Numbers with Activities

After you have defined asset groups, asset numbers, and activities, you can associate the activities with assets and rebuildables. However, you can streamline the creation of activities and associations using an activity association template. Assets are associated with activities before entering the activity into a preventive maintenance schedule (See: Entering Preventive Maintenance Schedule Definitions.

Note: You can streamline the creation of activity associations using an Activity Association Template. For example, when you create an asset group, and then asset numbers within that group, you do not need to utilize the Association window to associate those asset numbers with an activity. If you create an Activity Association Template, the activity that you associate with the current asset number's asset group automatically determines the activity that is associated with the current asset number .

To associate asset numbers (capital or rebuildable inventory) with activities using the Activity Workbench

  1. Navigate to the Activity Workbench window.

    Activity Workbench

    the picture is described in the document text

  2. Select Asset or Rebuildable from the Item Type list of values.

    The item type determines the type of asset number you are associating with the activity.

  3. Optionally narrow your data selection by selecting the asset number you intend to associate with an activity.

  4. Optionally narrow your data selection by selecting an activity.

  5. Choose Launch.

    Activity Workbench and Activity Associations

    the picture is described in the document text

  6. Depending on the Item Type chosen while performing step 2, select the corresponding tab within the Activity Workbench pane.

    For example, if you selected an Item Type of Asset, select the Results (Assets) tab. If you selected an Item Type of Rebuildable, select the Results (Rebuildables) tab.

  7. Expand the All Assets (within the Results (Assets) tab) or All Rebuildables (within the Results (Rebuildables) tab) folder.

    If you specified an asset number while performing step 3, that asset number appears.

  8. Select an asset number by highlighting it.

    The Activity Associations window appears. If the asset number is already associated with one or more Activities, those rows display within the window.

  9. Select the next available row and then select an asset group.

  10. Select an asset number.

    Asset numbers associated with the previously selected asset group are available. Asset numbers are always serial controlled. If you had selected a Non-serialized Rebuildable in the Asset Group field, then the Asset Number field is not required.

  11. Select an activity.

  12. When an asset is transferred from one organization to another, its maintenance may be handled by a new eAM organization. Any activities that are assigned to the asset are visible in the Activity Workbench, within the new eAM organization. Activities that are not currently assigned to the new organization are displayed in blue.

    Choose Assign to Org to assign the selected activities to the new organization.

  13. Save your work.

Defining Maintenance Routes

Operations are the instructions or tasks to perform a repair. Because each operation is associated with a department, each operation contains assigned resources, for example, trades people, outside service providers, and equipment (See: Defining Departments and Resources). A maintenance route is the set of operations or jobs necessary to perform an activity. When a work order is created for an activity, the maintenance route corresponding to the activity explodes to the work order (See: Defining Activities); all operations specified in the maintenance route are copied to the work order as its operations.

Maintenance routes are not asset routes. For information on asset routes, See: Defining Asset Routes.

Enterprise Asset Management operations differ from manufacturing operations because manufacturing operations are performed sequentially, whereas eAM operations may not be performed sequentially. You can specify that one operation is dependent on another, and one operation can depend on multiple operations. Also, two unrelated operations can occur concurrently. Multiple operations can depend on one operation. The dependency may not be totally connected.

To define a maintenance route

  1. Navigate to the Activity Workbench window.

  2. Click the Launch button.

  3. Within the Activity Workbench pane, select the Activity for which you wish to create the routing.

  4. Click the Routings button.

    the picture is described in the document text

  5. Select an Activity from the Item list of values.

  6. Within the Main tab, enter an operation Sequence, or let the system automatically generate it for you, according to your profile setup (See: Item and Operation Sequence, Oracle Bills of Material User's Guide).

  7. To copy or reference standard operations into a routing, use the operation Code list of values. You can define a new standard operation by selecting Standard Operations from the Tools menu.

    If you use a standard operation code, the operation information for that code is copied into the current operation. You can then update that information as desired (See: Creating a Standard Operation, Oracle Bills of Material User's Guide).

  8. Select a Department where the operation is performed.

  9. Select the Referenced check box to indicate that any changes to standard operations are reflected in the routing. If the standard operation is selected, this check box is selected by default.

  10. The Effective date defaults to the system date, but you can optionally change this (See: Effective Date Fields, Oracle Bills of Material User's Guide).

  11. Optionally enter a Disabled date to indicate the current operation's expiration.

  12. Select the Description tab. Enter a Description for the current operation.

  13. Optionally choose Routing Network to view the operation dependencies for the current asset route.

    the picture is described in the document text

    You can schedule operations to execute in parallel, sequence, or through dependent steps. In the screen shot above, for example, Operations 20, 30, 40, and 50 are dependent on Operation 10, since there is a line connecting the operations. These operations also run in parallel to each other. The operation numbers identify the sequence that they are performed (See: Preparing Work Order Operations, Oracle Enterprise Asset Management User's Guide).

  14. Optionally select an operation, then choose Operation Resources to view the resources associated with the current department attached to this operation (See: Defining Departments and Resources). Optionally you can modify the resources listed (See: Assigning Operation Resources, Oracle Bills of Material User's Guide).

    the picture is described in the document text

  15. Save your work.

    For information on all remaining fields, See: Creating a Routing, Oracle Bills of Material User's Guide

    For information on defining Activities using the Activity Workbench, See: Defining Activities.

Creating Activity Templates

You can streamline the creation of activity associations using an Activity Association Template. For example, when you create an asset group, and then asset numbers within that group, you do not need to use the Association window to associate those asset numbers with an activity. If you create an Activity Association Template, the activity that you associate with the asset group for the current asset number automatically determines the activity that is associated with the current asset number.

You can also create an activity template during an asset activity association.

To create an activity template

  1. Navigate to the Activity Workbench page.

  2. Click the Launch button.

  3. Select the Results (Activities) tab.

  4. Select the Activities with Associations directory.

    Select the appropriate activity.

  5. Select Yes from the Template Flag list of values to indicate that this activity and asset association is also an Activity Association Template.

    If you select No, an asset and activity association is created.

  6. For information on all remaining fields within the Activity Associations window, See: Associating Asset Numbers with Activities.

  7. Save your work.

Related Topics

Defining Activities

Preventive Maintenance Setup

eAM Cost Estimation, Oracle Enterprise Asset Management User's Guide

Activity Association Templates

Rebuildable Item Setup

Rebuildable Item Setup tasks include:

Defining Rebuildable Items

Items that are installed, removed, and refurbished are referred to as rebuildable items. Examples of rebuildable items include motors, control boxes, and computer boards. Rebuildable items might need to be removed or refurbished while a parent asset is maintained. Rebuildable items are inventory items; you have the option to serialize them.

To set up rebuild items

  1. Navigate to the Rebuild Items window.

    Rebuild Items

    the picture is described in the document text

  2. Enter the name of the Rebuild Item.

  3. Enter a Description for this Rebuild Item, up to 240 characters.

  4. Select the @Rebuildable Template to quickly apply attribute values, and to ensure that the appropriate attributes are applied.

    Note: You can create rebuildable items using the template described above, or you can copy a Rebuild Item from an existing Rebuild Item (See: Defining Items, Oracle Inventory User's Guide).

  5. In the Serial Generation region, select Predefined for the Generation value.

  6. Define a Starting Prefix and Starting Number for this Rebuild Item. If Serial Generation is set at Item Level for the Organization, the system defaults the prefix, along with the starting number sequence, when a new Serialized Rebuild is created for this Rebuild Item.

  7. Save your work.

To access failure analysis information

You can access the Failure Set page to view failure tracking codes that are assigned to the current Rebuild Item.

  1. From the Rebuild Items window, select Maintain Failure Set from the Tools menu. If the Rebuild Item does not have an associated Failure Set, this menu option is disabled. See: Defining Failure Codes and Sets, Oracle Enterprise Asset Management User's Guide and Failure Analysis Overview, Oracle Enterprise Asset Management User's Guide.

  2. Close the window.

To associate rebuildable items to multiple organizations

  1. From the Rebuild Items window, select Item Details from the Tools menu.

  2. Select the Organization Assignment tab.

  3. Enter additional organizations in the available table.

  4. After saving your work, you can associate this Rebuildable Item with an Activity (See: Rebuildable Item/Activity Association).

Defining Rebuildable Serial Numbers

To set up rebuildable serial numbers individually

  1. Navigate to the Define Rebuildable Serial Number page.

    You can also create rebuildable assets using the Create Asset page located in the Maintenance Super User responsibility (Maintenance Super User > Home > Assets > Create button). See Creating Capital or Rebuildable Assets, Oracle Enterprise Asset Management User's Guide for more information.

    the picture is described in the document text

  2. Enter an asset number (Rebuildable Serial Number) if you do not have them automatically generated.

    Accept or modify the default asset number, if you have automatic generation enabled (See: Defining eAM Parameters).

  3. Select an asset group. This is the asset group (Rebuildable Item) you are associating with the Rebuildable Serial Number you are currently creating.

    Note: After an asset group (Rebuildable Item) is associated with a Rebuildable Serial Number and then saved, you cannot change it.

  4. The Asset Serial Number (Rebuildable Serial Number) defaults to the asset number. You can optionally select the next serial number for the current organization.

    The Asset Serial Number might have a non-unique value across organizations, but the asset number must be globally unique, regardless of the defaulting value.

  5. Optionally associate this Rebuildable Serial Number to an Asset Category. This is the Class and Subclass code, such as CRANE.OVERHEAD or BUILDING.FLOOR. See: Setting Up Category Codes and Sets.

  6. Optionally enter a description for the Rebuildable Serial Number of up to 240 characters.

  7. Within the Main tab, optionally select an owning Department for this Rebuildable Serial Number. This represents the crew responsible for the Rebuildable Serial Number. Notifications, regarding work requests, are sent to the Primary Approver of the work request's associated asset number's current owning department (See: Defining Department Approvers and Defining Asset Numbers).

  8. Optionally select a Criticality code to indicate the importance of the asset number to the organization. This field is for information purposes.

  9. Optionally select a WIP Accounting Class to identify the Expense cost elements associated with the work performed, such as materials, labor, and resources.

  10. Select the GIS Assets check box if you want to define the asset as a linear or area asset.

    This field can be updated on this page or the Define Asset Numbers page.

    See Defining GIS Asset Numbers, Oracle Enterprise Asset Management User's Guide for more information.

  11. Optionally enter the Area where this asset number resides. This is a user defined listing of logical areas of work. For example, North Plant, East Wing, or Area 1 (See: Setting Up Areas).

  12. Indicate whether this asset is maintainable. If the Maintainable check box is selected, you can create work requests and work orders for this asset.

    For example, you can create an asset for cost-tracking purposes. We may want to see the cost for all top level assets in an asset hierarchy, but we do not want to maintain those assets. In this situation, do not select this check box.

    Note: After work orders are created for this asset, you cannot clear this check box unless those work orders are at Complete, Canceled or Closed statuses.

  13. Select an Asset Status. This field represents the current status associated with the rebuildable asset.

  14. Optionally select the Active check box to indicate that the asset is functioning, for example, maintenance work orders can be created for this asset. This check box change when you activate or deactivate an asset from the Tools menu.

  15. Indicate whether Asset Operational Logging is enabled for this asset. If you select the Operation Log Enabled check box, you can view all current and past asset operational information, such as Check Out, Check In, associated work requests and work orders. You can remove or add a child asset, remove a parent asset, activate or deactivate the asset, transfer the asset to another location, and receive or issue the asset into/from Inventory. By default, logging is turned off for an asset. See: Asset Operational Logging, Oracle Enterprise Asset Management User's Guide.

  16. You can optionally associate the current Rebuildable Serial Number with a parent capital asset or parent rebuildable.

    1. Select an Asset Type. Valid values are Capital and Rebuildable Inventory.

    2. If you selected a Capital Asset Type, optionally select a parent asset number. If you previously selected a Rebuildable Inventory Asset Type, optionally select a Rebuildable Serial Number from the asset number list of values.

    3. If you selected a Capital Asset Type, optionally select a parent asset group. If you previously selected a Rebuildable Inventory Asset Type, optionally select a Rebuildable Item from the Asset Group list of values.

  17. The Checked Out check box indicates whether the current asset is checked in or out. You can check out an asset to view asset details, enter collection plan data, enter meter information, and optionally create a work request, within Maintenance Super User. This check box is protected against update. See: Asset Operational Logging, Oracle Enterprise Asset Management User's Guide.

  18. Within the Location tab, the Subinventory and Locator fields are view-only, displaying the subinventory location of this asset within Inventory and its Locator segments. If this asset if received into Inventory, these fields are populated.

  19. Optionally select a Location Code to specify a physical location for this asset. The Address field simultaneously populates with the selected Location Code's associated Address. The previously defined Area is organization-specific and not associated to a physical location.

    Valid Location Codes are defined within Oracle Installed Base.

  20. Use the Location tab to specify the geocode information with details of latitude, longitude and direction for the asset. This information is used to display the assets in the chosen map viewer.

    If you are using the ESRI feature, you can enter values in these fields to display assets on an ESRI map rather than entering values in the Latitude and Longitude fields:

    • ESRI Feature: The reference to a published Feature table from the ESRI System which has a Point shape. These values are defined on the ESRI Map Manager page.

    • ESRI Feature ID: The specific ESRI reference identifier from the selected ESRI Feature table which has a corresponding Point geometry.

      If both longitude and latitude and ESRI references are provided, the ESRI Feature and Feature ID would be used to plot the asset on the map.

      Note: Geocode entry and ESRI Feature associations are enabled only for point assets and are not applicable for GIS assets.

    See Using Map Manager, Oracle Enterprise Asset Management Implementation Guide for more information regarding the ESRI Map Manager fields.

  21. The Address defaults as the populated Location Code's associated address. You can optionally select a different address. If the current asset is in stores, the address of the Location's organization appears (See: Stores, Oracle Enterprise Asset Management User's Guide).

  22. Optionally select a Production Organization. The list of values displays the production inventory organizations maintained by the current asset's organization. See: Enabling Organizations for Enterprise Asset Management for information on designating eAM organizations to maintain equipment items for designated production organizations.

  23. Select an Equipment Item. This is mandatory if you populated the Production Organization field. Items that were defined with an equipment template (See: Item Templates, Oracle Inventory User's Guide ), or with the Equipment item attribute enabled (See: Physical Attributes, Oracle Inventory User's Guide ), are available.

  24. Enter an Equipment Serial Number. This is mandatory if you populated the Production Organization field. This is the specific name of the component within the Equipment Type, defined above.

  25. Select the Safety tab to enter safety information. See Defining Positional Assets, Oracle Enterprise Asset Management User's Guide.

  26. Select the Others tab to optionally enter the Fixed Asset region information, if Oracle Fixed Assets is installed. This is Enterprise Asset Management's integration with Fixed Assets. Enter a Category, which is a grouping of fixed assets, defined within Oracle Fixed Assets. This category is tied to a set of books, and must be the same set of books that is assigned to the current Enterprise Asset Management organization. See: Setting Up Asset Categories, Oracle Fixed Assets User's Guide.

  27. Optionally enter the Number if Oracle Fixed Assets is installed. This represents a fixed asset number that belongs to a fixed asset category, associated with the asset.

  28. The Property Management fields, Location Name and Location Code, default from a Property Manager export process (Export Locations to Enterprise Asset Management), if Oracle Property Management is installed. These fields are disabled, and the values cannot be changed.

  29. Before the above information is passed from Property Manager into Oracle Enterprise Asset Management, asset groups (rebuildable items) need to first be established. See: Defining Rebuildable Items.

  30. Optionally choose Location Details to view or update the Property Manager field information.

  31. Optionally select Attributes to enter attribute values for the asset .

    Existing, enabled attribute groups appear. These attribute groups are optional. You do not need to enter values for all existing attribute groups. From this window, you cannot generate attribute groups. (See: Setting Up Attributes).

  32. When you select the GIS Asset check box, the GIS Workbench button becomes available.

    Use the GIS Asset Workbench to enter details for the GIS asset. See Using the GIS Asset Workbench, Oracle Enterprise Asset Management User's Guide for more information.

  33. Optionally choose Meters to associate the current rebuildable serial number to one or more meters.

  34. Optionally choose Associate Activity to associate the current rebuildable serial number to an activity.

    Additional Information: To establish this Rebuildable Serial Number in Inventory, you must execute any receipt transaction, such as a Miscellaneous Receipt or a Purchase Order Receipt.

  35. Save your work.

Rebuildable Item and Activity Association

After you have defined rebuildable items and activities, you can associate activities to the rebuildable items. For example, you may have a Rebuild Engine Activity, and an Engine Rebuildable Item. After you create a rebuild work order for the engine, the associated Rebuild Engine Activity attaches its associated maintenance BOM (material) and maintenance routing (resources) to the work order.

Note: Activity association for Rebuildable Serial Numbers are streamlined by using Activity Association Templates. If an Activity Template is defined for a Rebuildable Item, the activity association automatically creates when a new serial number is created for that item, within the maintenance organization.

To associate rebuildable items with activities

  1. Navigate to the Activity Association window.

    Activity Association

    the picture is described in the document text

  2. Select an Activity.

  3. Within the Main tab, select Rebuildable from the Item Type list of values.

  4. Select a Rebuildable Item from the Asset Group list of values.

  5. If the Rebuildable Item is serial number controlled (See: Defining Rebuildable Items), select a Rebuildable Serial Number from the Asset Number list of values.

  6. Optionally select a Priority Code.

    This field is for informational purposes.

  7. Optionally enter Effective Dates.

    If the Effective From field is left blank, the system date defaults. If the Effective To field is left blank, it defaults as NULL.

  8. Within the Activity tab, the Activity Cause defaults from the Activity definition, specifying what situation caused this work to be generated.

    For example, Breakdown, Vandalism, Normal Wear, or Settings. Optionally you can select an Activity Cause.

  9. The Activity Type defaults from the Activity definition (See: Defining Activities, Oracle Enterprise Asset Management User's Guide).

    This code indicates the type of maintenance activity needed to perform for this Activity. It is used when defining a job or a standard job. It should remain generic, and should not describe the job in detail. For example, Inspection, Overhaul, Lubrication, Repair, Servicing or Cleaning. Optionally select an Activity Type.

  10. Optionally select the Tagging Required check box to indicate whether tag out procedures are required.

  11. The Owning Department field is used when associating asset numbers to activities (See: Activity Association Templates).

  12. Save your work.

Defining Rebuildable Bills of Material

You can identify and select the required items that make up a Rebuildable Serial Number. A bill of material (BOM) is used to list all items and components that make up a particular asset or rebuildable, and is defined for each Rebuildable Item. The items defined on a Rebuildable BOM are standard inventory components or non-inventory, direct items (See: Defining Items, Oracle Inventory User's Guide).

Note: If you are not using Project Manufacturing applications, Project Parameters are defined for your eAM enabled organization to successfully create Rebuildable Items. This is required because a Rebuildable BOM is of type Model/Unit Effective and this BOM type is currently allowed if PJM organization parameters are set up for the eAM enabled organization to which the Rebuildable Item has been assigned. To define Project Parameters, open the Project Parameters window using Project Manufacturing Super User responsibility and without entering any data in the window, save the record. If you plan to use Project Manufacturing, see: Project Manufacturing Integration Setup for information on defining Project Parameters.

To set up a rebuildable BOM

  1. Navigate to the Bills of Material window.

  2. Select a Rebuildable Item from the Item list of values.

  3. Within the Main tab, the Item Sequence and Operation Sequence values default.

  4. Enter the inventory or non-inventory Component to make up the Rebuildable Serial Number.

  5. Enter the component Quantity for the Rebuildable Serial Number.

  6. Save your work.

Related Topics

Defining Items, Oracle Inventory User's Guide

Associating Asset Numbers with Activities, Oracle Enterprise Asset Management User's Guide

Defining Subinventories, Oracle Inventory User's Guide

Defining Stock Locators, Oracle Inventory User's Guide

Creating a Bill of Material, Oracle Bills of Material User's Guide

Non-Stock Direct Item Setup

Non-stock direct items can represent items that are not stocked in inventory, such as services that are purchased from a supplier. Non-stock direct items are not stocked in inventory; they are defined in the Item Master as an inventory item, Purchased, Purchasable, and the Stockable check box is not selected. See: Purchasing Attribute Group, Oracle Inventory User's Guide. These items are contrived as "one off", bought directly from a vendor for a specific work order and operation. These items are delivered directly to the Shop Floor for maintenance work order execution.

You can add only coded items (for example, Inventory Stockable and Non-Stockable-Direct items) to the maintenance BOMs. (See: Defining Direct Item Material Requirements, Oracle Enterprise Asset Management User's Guide).

To set up non-stock direct items, access the Master Item window within Oracle Inventory, and apply the @Non Stocked Item template. See: Defining Items, Oracle Inventory User's Guide. Description based direct items are not set up within Oracle Inventory.

If direct items exist on a BOM, they default as material requirements when creating a work order for that asset; however, you can add direct item material requirements to an existing work order.

To set up a non-stock direct item

  1. Navigate to the Master Item window.

  2. Enter the non-stock direct Item name.

  3. Enter a Description.

  4. From the Tools menu, select Copy From.

  5. Select the @Non-Stocked Item Template.

  6. Choose Apply.

  7. Choose Done.

    Master Item

    the picture is described in the document text

  8. Save your work.

    The Stockable check box is clear, and the Purchased and Purchasable check boxes are selected.

Related Topics

Defining Rebuildable Bills of Material

Setting Up Maintenance Bills of Material

Setting Up Asset Bills of Material

Defining Items, Oracle Inventory User's Guide

Preventive Maintenance Setup

eAM can generate work orders automatically based on meter readings, runtime or calendar days. An example of meter-based preventive maintenance is an oil change for a car. Most car manufacturers recommend that you change your engine oil every 3,000 miles or six months, whichever comes first.

This section includes the following topics:

Project and Task Setup

Work orders can be associated with a Project, Task or Seiban number at the time of implementing PM suggestions to work orders. The Forecast Work Order window can be configured.

Defining Meter Templates

There are two ways to create meters:

If you create meters using the Meter window (See: Defining Meters), associate that meter definition with individual asset numbers manually.

If you utilize the meter template definition functionality, you can associate that meter template with asset groups. After the association is created, when an asset number (asset numbers or serialized rebuilds) is created within that asset group (Asset Group or Rebuildable Item), the system automatically creates a new instance of the meter, associated with the specific asset number. This enables you to streamline your meter setup. However, the meters are not created retroactively; it applies to asset numbers created after the meter template was created.

Defining Meter Templates

  1. Navigate to the Meter Template window.

    Meter Template

    the picture is described in the document text

  2. Enter a Name for the meter template.

  3. Enter the Description for the template.

  4. Enter a Value or Change Reading value for new meter readings, depending on the meter type.

    Note: If the meter is a Change type, the Value field indicates the difference between the last reading and the current reading. The Change value is used to calculate the Life To Date Reading, within the Latest tabbed region.

  5. Optionally change the Date, if required.

  6. Optionally enter an Initial Reading.

    This is automatically used as the first meter reading entered, or each new instance of the meter that is created and associated with an asset number (or Serialized Rebuild) using the Meter Template.

  7. If you select the Used in Scheduling check box, the meter is used in Preventive Maintenance Scheduling.

    If there are any scheduling rules associated with this meter, you cannot deselect this check box. If this is a fluctuating meter, this check box is disabled. If the Used in Scheduling check box is selected, the Usage Rate (per day) and Number of Past Reading fields are mandatory.

  8. Optionally select the Required check box.

    Warning: PM work orders cannot be completed unless a meter reading is entered when the meter is considered in the Meter rules section of the PM Schedule definition, even if the Required check box is not selected.

    You can select or clear this check box at any time; it impacts only future meter readings. However, if the meter is a Primary Failure Meter for any current asset/meter association, you cannot deselect the check box.

  9. Enter a usage Rate (per day).

    This field works in conjunction with the Number of Past Readings field to provide daily meter usage estimates, based on historical readings. It supplies the system benchmark data that is used to set the occurrence of scheduled PMs. Rate per day is referred to in the absence of a sufficient value in the Number of Past Readings field.

    This field is mandatory if you have selected the Used in Scheduling check box.

  10. Enter a value for the Number of Past Readings.

    This value designates how many readings prior the scheduler should go to for calculating the usage rate. If there is an insufficient number of readings (for example four, instead of the required five), the system continues the calculation based on the usage Rate per day.

    This field is mandatory if you have selected the Used in Scheduling check box.

  11. Select the meter template effective dates.

    If left blank, the meter is effective all of the time. You can disable a meter effective on a specific date by selecting a To date.

  12. Save your work.

To associate meter templates with asset groups

If you use the Meter Template definition functionality (See: Defining Meter Templates), you can associate that Meter Template with asset groups, within the same Meter Template window. After you create the association, when a new asset number (Asset Numbers or Rebuildable Serial Numbers) is created within that asset group (Asset Group or Rebuildable Item) a new instance of the corresponding meter is automatically created. This enables you to streamline your Meter setup.

  1. Select an Item Type.

    Valid values are Capital or Rebuildable.

  2. Select an asset group.

    If you previously selected Capital, asset groups are available for selection. If you previously selected Rebuildable, Rebuildable Items are available for selection.

  3. Save your work.

    After saving, each asset number defined as part of the current asset group is automatically associated with the meter template.

Reapplying a Meter Template to an Asset Group

You can reapply a meter template to asset group after the asset has been created. Meter templates can be applied to an entire asset group or a range of asset numbers or serialized rebuildables.

Note: You can apply meter templates to only those assets to which a meter template has not been previously (applied) associated.

  1. Navigate to the Reapply Asset Template form (Enterprise Asset Management > Assets > Reapply Asset Template).

  2. Select values for the following required fields:

    1. Asset Type: Select Capital or Rebuildable.

    2. Asset Group: Select the asset group. You can apply the meter template to an entire asset group or to specific asset numbers within an asset group.

    3. Template Type: Select Meter Template.

  3. Optionally select values for these fields:

    • Asset Status

    • Meter Template: Select the meter template that you want to reapply to the asset.

    • Asset Number From: Enter the beginning asset number value if you want to apply the meter template to a range of asset numbers in the asset group.

    • Asset Number To: Enter the ending asset number value if you want to apply the meter template to a range of asset numbers in the asset group.

    If you enter a value in the Asset Number From field but leave the Asset Number To field blank, the concurrent program will apply the meter template to a specific asset number.

  4. Optionally select Yes in the View Only field if you do not want the system to apply the templates; a log is generated but the templates are not reapplied to the assets. The default value is No.

    the picture is described in the document text

  5. Click the OK button.

Defining Meters

Alternatively, you can create Meters using the Meter window. Manually associate the meter definition with individual asset numbers. If you utilize the Meter Template definition functionality, you can associate that Meter Template with Asset Groups (See: Defining Meter Templates).

To define a meter:

  1. Navigate to the Meter page.

    Meter

    the picture is described in the document text

  2. Enter a unique meter Name.

  3. Enter a Description for this meter.

  4. Optionally select a Source Meter from the list of values.

    As the readings for the source meter are updated, the associated target meter (current meter) is updated automatically. Companies can associate a source meter to an asset number and meter association. The source meter reading subsequently feeds corresponding meters that are associated with assets within the meter hierarchy.

    For example, some companies must track units, using a meter to a parent asset (truck). These units should then trickle down to all child components of that parent asset (transmission, tires, belts). Each child component has different meters to track the units and history on the individual components. If the transmission is replaced, the Rebuild Replacement process enables you to remove the replaced transmission from the meter hierarchy and add the new transmission to the hierarchy. From that point, meter readings logged to the truck should also update the transmission child meter with those units. When a reading is logged to the truck, it will update the transmission child meter with those units.

  5. Select the meter Type of Absolute or Change.

  6. Select a unit of measure (UOM), associated with this meter. After the meter is created, this field is disabled.

  7. Select Ascending, Descending, or Fluctuating in the Value Change field.

    A fluctuating meter reading is one that can go up and down, for example, a temperature gauge. As production units pass through meters, meter readings increment. Another example of an ascending meter is a car odometer. Some liquid dispensers start full and record decreasing readings as material is used.

    Note: Fluctuating meters are not used in Preventive Maintenance scheduling.

    After the meter is created, this field is disabled.

  8. Enter an Initial Reading.

    This value is automatically used as the first meter reading entered, or each new instance of the meter that is created and associated to a asset number via the Meter Template.

  9. If you select the Used in Scheduling check box, the meter is used in Preventive Maintenance Scheduling.

    If there are any scheduling rules associated with this meter, you cannot clear this check box. If this is a fluctuating meter, this check box is disabled. If the Used in Scheduling check box is selected, the Usage Rate (per day) and Use Past Reading fields become mandatory.

  10. Optionally select the Required check box.

    Warning: PM work orders cannot be completed unless a meter reading is entered when the meter is considered in the Meter rules section of the PM Schedule definition, even if the Required check box is not selected.

    You can select or clear this check box at any time; it impacts only future meter readings. However, if the meter is a Primary Failure Meter for any current asset/meter association, you cannot deselect the check box.

  11. Enter a usage Rate (per day).

    This field works in conjunction with the Number of Past Readings field to provide daily meter usage estimates, based on historical readings. It supplies the system benchmark data that is used to set the occurrence of scheduled preventive maintenance. Rate per day is referred to in the absence of a sufficient value in the Number of Past Readings field.

    This field is mandatory if you have selected the Used in Scheduling check box.

  12. Enter a value for the Number of Past Readings.

    This value designates how many readings prior the scheduler should go to for calculating the usage rate. If there is an insufficient number of readings (for example four, instead of the required five), the system continues the calculation based on the usage Rate per day entered.

    This field is mandatory if you have selected the Used in Scheduling check box.

    Note: If you enter a value of 1, the system perpetually calculates at the usage Rate per day.

  13. Select the meter Effective Dates.

    If left blank, the meter is effective all of the time, after it is created. If you select a future date, the meter is disabled until that date. You can disable a meter effective on a specific date by selecting a To date.

  14. Save your work.

To associate meters with capital assets or serialized rebuilds

Meter association creates the relationship between the meter definition and the capital asset number or Serialized Rebuild.

  1. Select an Item Type of Capital, if you are going to associate the current meter with an asset number. Select Rebuildable if you are associating the current meter with a Serialized Rebuild.

  2. Select an asset number (or Serialized Rebuild). The Asset Group (or Rebuildable Item) default value appears.

  3. Optionally select a Primary Failure Meter to indicate the default meter that is used for failure analysis. These readings are used to calculate meter-based MTBF and MTTR. See: Failure Analysis Overview, Oracle Enterprise Asset Management User's Guide.

    You can select a Primary Failure Meter for any meter with the Required option selected. Only one meter can be selected at a time, for an asset.

  4. Save your work.

Defining Set Names

A PM schedule for an activity and an asset number or asset group must uniquely belong to a set name. Multiple PM schedules for the same asset number or asset group and activity combination are created across sets. However, out of those PM schedules, one can be identified as the Default and used for generating work orders. Other schedules in other sets can be used for simulation purposes. All set names have an end date. Each PM schedule that belongs to the set name must have its effective-to date before the end date of the PM schedule set name. Before assigning a set name to a PM schedule, you must define set names within the Set Name Definition window. If you do not want to create set names, you can assign PM schedules to the predefined MAIN set.

PM schedules might contain assets that transferred from one organization to another. The destination organization for the asset can update and use the PM schedules that are assigned to a global PM set. However, you can only view the PM schedules within the destination organization that are assigned to the local PM sets for the originating asset organization.

Defining Set Names

  1. Navigate to the Set Name window.

    Set Name

    the picture is described in the document text

  2. Enter the Set Name.

  3. Optionally enter an End Date.

    Every PM schedule that belongs to the set name must have its effective-to date before the End Date of the set name for the PM schedule. If you leave this field blank, the current set name does not expire.

  4. Optionally enter a Description for this set name.

  5. Optionally select the Global check box to indicate that the set is visible globally.

    If this check box is clear, the set is confined to the current organization.

    Note: You can change this setting from Global to local, if the set is not used in an PM schedules of assets associated with another organization.

  6. Optionally choose Templates to add, change, delete, or view Preventive Maintenance Schedule Templates, associated with the current set name (See: Preventive Maintenance Schedule Templates).

  7. Optionally choose Schedules to create PM schedule definitions associated with the current set name (See: Defining a Preventive Maintenance Template).

  8. Optionally choose Set Default to identify all schedules within this set as the default value.

    Default-identified PM schedules automatically generate work orders during the PM Scheduler process. PM schedules that are not identified as a default value can generate work order suggestions during the PM Scheduler process. The generated suggestions cannot be converted into work orders. You can create an unlimited number of Set Names within this window.

  9. Save your work.

Defining a Preventive Maintenance Template

An activity and asset number combination can be associated with Runtime, Day Interval Rules, or a list of dates, defining when an activity should be scheduled for an Asset, Serialized and Non-Serialized Rebuildables, or an Asset Route. Day Interval rules and List of Dates rules are supported for Non-Serialized Rebuildables and Asset Routes. The Preventive Maintenance (PM) Scheduler process creates suggested work order dates based on these rules. A planner can then view these forecasted work orders, and generate them as necessary.

There are two ways to create PM schedule definitions for Rebuildable Serial Numbers and Assets. You can create them individually within the Preventive Maintenance Schedules window (See: Entering Preventive Maintenance Schedule Definitions, Oracle Enterprise Asset Management User's Guide), or streamline the process of creating them using a PM Template. A PM Template is a schedule, defined for an asset group (Asset Group or Rebuildable Item)/Activity association. If you utilize the PM Template functionality, a new PM Schedule is automatically created for a newly created asset number (asset or rebuildable) for the asset group. All PM Template attributes are copied over to the PM Schedule for the Instance. You can optionally modify the values of the PM Instances created.

Before a PM Template is created, the following prerequisites must exist:

Creating Preventive Maintenance (PM) Templates

  1. Navigate to the Find Preventive Maintenance Schedules window.

    This window enables you to enter information to narrow your search for query mode.

    Select Yes in the Next WO only field if you want the PM Scheduler to be able to create the next work order only if the previous work order has been completed for this work order completion date.

    To define a new PM Template, select the New button.

  2. Enter a PM Template name in the Schedule Name field.

  3. Enter a Set Name. A PM schedule for an activity and asset group must uniquely belong to a set name (See: Defining Set Names).

    Each Set Name has an end date. The PM schedule that belongs to the Set Name must have its Effective To date before the end date of the PM Set Name. Before assigning a Set Name to a PM schedule, define Set Names within the Set Name Definition window. If you do not want to create Set Names, you can assign PM schedules to the predefined set, MAIN.

    PM schedules might contain assets that transferred from one organization to another. The destination organization for the asset can update and use the PM schedules that are assigned to a global PM set. However, you can only view PM schedules within the destination organization that are assigned to the local PM sets for the originating asset organization. You can copy these PM schedules to a global, local set or to the local set for the organization.

  4. Select an Asset Type.

    Valid values are Capital and Rebuildable Inventory. If Capital is selected, the Asset Group fields refer to the asset group. If you select Rebuildable Inventory, the Asset Group fields refer to the Rebuildable Item.

  5. Select an asset group.

  6. Select a Schedule Type.

    Valid values are Rule Based and List Dates. If you select Rule Based, the Day Interval Rules and Runtime Rules tabs are enabled to enter information. If you select List Dates, you can define information within the List Dates tab.

  7. The Effective dates default from the current activity association, if they exist. Optionally select or update the Effective From and Effective To dates.

  8. Optionally enter a Lead Time In Days.

    Lead time in a Preventive Maintenance Schedule is different than lead time associated with work order creation. The Preventive Maintenance process suggests work orders to be created or scheduled, starting from the last service day of the Asset to the cutoff day you specified while running the process. If a Lead Time In Days is specified, the Preventive Maintenance process predicts work for those extra days beyond the cutoff date. This provides the maintenance department advanced visibility for maintenance work that is typically predicted in the next planning process. The maintenance department can prepare for such work in the current planning period.

  9. Optionally select a Work Order Status that best fits your business process.

    When PM work orders are generated, (See: Generating Work Orders, Oracle Enterprise Asset Management User's Guide) they are created with this specified status. You can optionally update this status within the Maintenance Workbench (See: Using the Maintenance Workbench, Oracle Enterprise Asset Management User's Guide).

  10. Optionally select Yes in the Next WO only field if you want to enable the scheduler to create the next work order only if the previous work order has been completed for the work order completion date.

  11. Optionally select the Default check box to indicate that the current PM schedule definition generates work orders. If this check box is not selected, work order suggestions will not generate. You can have only one Default PM for an asset item and activity combination.

  12. Optionally select the Automatic Instantiation check box. If this check box is selected, a new instance of the current PM schedule template is created for each new asset (Asset Number or Rebuildable Serial Number).

  13. Optionally select the Reschedule Manual Work Orders check box. If this check box is selected, non-firm, unreleased manual work orders are considered during PM scheduling.

  14. If the Run To Failure check box is selected, the Preventive Maintenance Scheduler does not automatically schedule asset numbers within this asset group and activity association, although you can create manual work orders. This is relevant for asset numbers that cost more to maintain than the asset number itself. You might also check this box for forecasting and budgeting reasons. For example, your asset is a conveyor belt. It is common in maintenance environments to let this asset wear out completely before replacing it. You estimated that the life of this asset is 18 months, and have set up a schedule for a replacement work order every 18 months. In reality, you found that the belts have ended up wearing out every 12 months, affecting your cost budget.

    You may select this check box and clear it later. For example, you might associate an asset number to an activity, but maybe you cannot currently maintain or schedule this asset number. You may have future plans to maintain this asset number.

    If this check box is selected, PMs created as a copy of this PM Template generate work orders for the corresponding asset in the Maintenance Workbench (See: Using the Maintenance Workbench, Oracle Enterprise Asset Management User's Guide).

  15. In the Scheduling Options region, indicate how the PM Scheduler process calculates work order dates.

    The Use field works in conjunction with the to suggest Next Service field. The date field indicates the Last Service date

    • Actual Start Date to Start Date: The PM Scheduler process uses the Last Service Actual Start Date, and calculates scheduled start dates.

      This is a forward scheduling method.

    • Actual Start Date to End Date: The PM Scheduler process uses the Last Service Actual Start Date, and calculates the scheduled end dates.

      This is a backward scheduling method.

    • Actual End Date to Start Date: The PM Scheduler process uses the Last Service Actual End Date, and calculates the scheduled start dates.

      This is a forward scheduling method.

    • Actual End Date to End Date: The PM Scheduler process uses the Last Service Actual End Date, and schedules the scheduled end dates.

      This is a backward scheduling method.

    • Scheduled Start Date to Start Date: The PM Scheduler process uses the Last Service Scheduled Start Date, and calculates scheduled start dates.

      This is a forward scheduling method.

    • Scheduled Start Date to End Date: The PM Scheduler process uses the Last Service Scheduled Start Date, and calculates the scheduled end dates.

      This is a backward scheduling method.

    • Scheduled End Date to Start Date: The PM Scheduler process uses the Last Service Scheduled End Date, and calculates the scheduled start dates.

      This is a forward scheduling method.

    • Scheduled End Date to End Date: The PM Scheduler process uses the Last Service Scheduled End Date, and schedules the scheduled end dates.

      This is a backward scheduling method.

    • Base Date: You must enter a date as the basis for the PM calculation.

      As your intervals change, you might want to update the Base Date so that your PM work orders are generated at your choice intervals. It is recommended that you change the Base Date to the Last Service Date if your scheduling interval changes, to ensure that the new scheduling is impacted only from that point and forward. Actual and scheduled work order dates are not considered when you use the Base Date or Base Meter options.

    • Base Meter: You must enter a meter, as well as the initial interval.

      The PM engine uses that initial reading as the anchor for its calculation. Actual and scheduled work order dates are not considered when you use the Base Date or Base Meter options.

  16. In the Multiple Rules region, indicate how the predicted due dates are determined for multiple rules.

    • First: The due date is set to the first due date of all rules.

    • Last: The due date is set to the last due date of all rules.

    For example, below is a Runtime Rule that includes two meters, Meter1 and Meter2

    Schedule Based On Example
    Interval Effective From Effective To Meter
    100 0 10,000 Meter1
    50 0 2,500 Meter2

    If you specify First Due Date in the Scheduling Based On region of the PM Template, between the two meters, the first meter that hits the due reading triggers the service. In this case, if Meter1's reading reaches the interval of 100 first, the service happens before Meter2's reading reaches its interval of 50. Conversely, you can choose Last Due Date in the Scheduling Based On region. In this case, even if Meter1 reaches its due reading, the service is not scheduled until Meter2 has also reached its due reading.

    This region is disabled if the current PM schedule definition's Scheduling Type field is populated with List Dates.

  17. In the Activity region, select one or multiple activities.

    Activities associated with asset groups are eligible for use in a schedule template definition. A maintenance planner can create a single PM schedule for multiple activities on an asset template. You can list multiple activities to perform on an asset that share a common base interval of either a date, meter, or both. Each maintenance activity on the schedule generates work orders, based on a multiple of the base interval occurring. The group of maintenance activities on one PM schedule represents a cycle of activities. Base Interval refers to the minimum of a space of time (such as 90 days), or meter reading (such as 7,500 miles) between when PM activities included in one PM schedule should be performed. It can be considered a common denominator among the multiple activities included in one PM Schedule that share a common base interval. A cycle is a complete round of maintenance activities performed on an asset that share a common base interval of a meter or time period, or both, or a multiple of the shared intervals.

    After the cycle of activities completes, the cycle restarts. For example, you can define a PM schedule for two activities that have a common Base Interval of 7,500 miles. The first activity is an oil change, and is scheduled every 7,500 miles. The second activity, a tune-up, is scheduled for every fourth interval or 30,000 miles. The work order for the oil change generates on each occurrence of the 7,500 mile interval and the work order for the tune-up generates on the fourth interval occurrence.

    When an asset transfers to another organization, the schedule that is associated with the local PM Set is viewable within the new organization. For example, the PM Set Name, Local, is created in organization, EM1. A PM schedule is defined in EM1 for asset number, #1554877, and is associated with Local (Set Name). asset number #1554877 is transferred to another eAM-enabled organization, EM2. A planner in this new organization (EM2) can view the PM schedule that is associated with the Local PM set. However, it is view-only; it cannot be updated. The associated activity appears in blue, to indicate that the activity definition has not yet been assigned to EM2. In this scenario, to use the PM schedule, the planner must either assign the activity for the PM schedule to the current organization, EM2, or update the PM schedule Set Name from Local to a global set or a local PM set that was defined in EM2.

    Note: You can define an unlimited number of activities, however, it is recommended that you keep it simple.

  18. Optionally indicate the Interval Multiple of the Base Interval.

    This field works with the Repeat in Cycle field to determine how many intervals for an activity to repeat.

  19. Optionally select the Repeat in Cycle value to determine if the activity interval repeats in the cycle.

    If you select Yes, the Interval Multiple field determines how many times the activity interval repeats. If you select No, the activity is scheduled once for each cycle.

  20. Optionally enter a value in the Tolerance In Days field to indicate a minimum interval in days between the suppressed activity and actual activity suppressing it.

  21. Within the Date Rules tab, optionally enter Effective From and To dates to specify the rule's expiration.

  22. Enter a Base Interval In Days.

    For example, if you enter the number three, a work order suggestion is created every three days. You can optionally create variable Date Rules. For example, you would like work order suggestions created every three days in January, and every four days in February. The window below illustrates this example:

  23. Within the Meter Rules tab, optionally select a Meter Name to indicate that Preventive Maintenance scheduling is based on a meter rule.

    If you have previously set up a Date Rule, you can base the scheduling on a Runtime Rule, as well. Meter Templates associated with this asset group (See: Associating Meter Templates with Asset Groups), and with the Used in Scheduling check box selected in the meter template definition are available.

    For example, trucks of a specific Make and Model need to be scheduled for an oil change every 30 days, or every 1000 miles.

    Date Rule
    Field Value
    Last Service Start/End Date December 26, 2001
    Interval In Days 30
    Meter Rule
    Field Value
    Last Service Reading 3000
    Interval 1000
    Latest Meter Reading 3100 (found within meter reading history)
    Latest Meter Reading Date January 1, 2002 (this can be found via meter reading history)
    Usage Rate 25 miles per day (calculated, based on Linear Regression's Least Square formula. In a least-squares model, the best-fitting line for the observed data is calculated by minimizing the sum of the squares of the vertical deviations from each data point to the line. For example, if a point lies on the fitted line exactly, then its vertical deviation is zero.)

    If the Meter Rule is taken into account, the next due date is February 6, 2002 (January 1 2002 + [(3000 + 1000 - 3100)/25 = January 1, 2002] +36 days), and every 40 days after that. This is calculated as the interval (1000 miles) divided by the usage rate (25 miles per day).

    The PM Scheduler process compares the above suggested dates from the runtime interval rule, to those of the date rule: Base Date of December 26, 2001 + every 30 days.

    The work orders ultimately created by the PM Scheduler process are those of the earliest or latest dates, depending on how the Schedule Based On region is populated. If you selected First Due, the earliest suggestion is used for work order creation. The opposite is also true.

  24. The Interval and UOM fields work together.

    For example, for every 2000 miles, this asset number needs an oil change.The UOM defaults from the Meter Template definition of the current Meter Template. You can optionally create multiple Runtime Rules. For example, from zero to 10,000 miles, you would like your asset serviced every 3,000 miles. From 10,000 to 50,000 miles, you would like your asset serviced every 2,000 miles.

  25. Optionally enter the Last Service Reading in the Last Service Information window.

    This field is also automatically updated with the meter reading information recorded at work order completion (See: Work Order Completion, Oracle Enterprise Asset Management User's Guide).

    Note: The Preventive Maintenance Scheduler (See: Generating Work Orders, Oracle Enterprise Asset Management User's Guide) automatically calculates the meter usage rate, based on historical data, which is then used to predict the next meter due date. Refer to the example below.

  26. If you populated List Dates within the Schedule Type field, select the List Dates tab to define the specific due dates that work orders should transpire.

    For example, you want asset, Car1, serviced on May 1 and November 1 every year for the next three years. In this case, you would create a List Dates type schedule definition, and list all the due dates within this tab. The PM Scheduler process creates suggested work order dates on those specified dates.

  27. Save your work.

Reapplying a PM Template to an Asset Group

You can reapply an PM template to an entire asset group or to specific asset numbers or serialized rebuildables within an asset group. If there are any associated suppression templates, they are also reapplied.

Note: The concurrent program applies to asset groups that have an existing activity template applied.

To reapply a PM template to an asset group:

  1. Navigate to the Reapply Asset Template page (Enterprise Asset Management > Assets > Reapply Asset Template).

  2. Select the Asset Type (required). Values are Capital or Rebuildable.

  3. Enter the Asset Group (required).

  4. Select PM Template for the Template Type to be reapplied (required).

  5. (Optional) Enter values in these fields to reapply the PM template to specific assets within the asset group:

    • Asset Status

    • Asset Number From: Enter the beginning asset number value if you want to apply the PM template to a specific asset number in the asset group.

    • Asset Number To: Enter the ending asset number value if you want to apply the PM template to a specific asset number in the asset group.

  6. Optionally select Yes in the View Only field if you not want the system to apply the templates; a log is generated but the templates are not reapplied to the assets. The default value is No.

    Reapply Asset Template - PM Template

    the picture is described in the document text

  7. Click OK to run the concurrent program to reapply the PM template.

Entering Preventive Maintenance Schedule Definitions

Schedule definitions are implemented to create scheduled work orders, based on Day Interval rules, Runtime rules, or Calendar Based schedules. Schedules can also be based on a list of specific dates by using List Date rules. List Date rule based PM schedules cannot have Runtime or Day interval rules. Runtime or Day Interval Rule based PM schedules cannot have List Date rules. You can create a Preventive Maintenance Schedule Definition for an asset group (serialized rebuildable and activity combination, asset number/activity combination, or an asset route and activity combination).

Calendar Based Scheduling

This option enables users to define recurring calendar setups that can be defined in PM rules. Calendar based schedule options are Weekly, Monthly and Yearly.

Note: Multiple calendar rules are allowed but cannot overlap in one PM schedule.

Calendar Based Schedules - Setup Information for Weekly Option

Field Values/Meaning
Interval Enter the value for the interval such as enter 2 to repeat once every 2 weeks.
Day of Week Sunday to Saturday
Day Num Display only, values of 1 to 7 are displayed based on Day of Week value. For example, Day Num for Sunday is 1; sequence continues to Day Num as 7 for Saturday.
Weekly Example
Field Values/Meaning
Interval 3
Day of Week Monday
Day Num 2

In this example, the activity should occur once every 3 weeks and is always scheduled to run on a Monday.

Calendar Based Schedules - Setup Information for Monthly Option

Field Values/Meaning
Interval Enter the value for the interval such as enter 2 to repeat the activity once every 2 months
Repeat First/Second/Third/Fourth/Last/Day of Month
Day of Week Sunday to Saturday and Day option applicable for First and Last Day of the month selection.
Day Num Display only field. Values 1 to 8 are associated with Day of Week value, or values of 1 to 31 are applicable to Repeat option for Day of Month.
Monthly Example
Field Values/Meaning
Interval 2
Repeat Last
Day of Week Sunday
Day Num 1

In this example the activity should occur once every 2 months on the last Sunday of the month.

Calendar Based Schedules - Setup Information for Yearly Option

Field Values/Meaning
Interval Enter the value for the interval such as every 2 years.
Repeat First/Second/Third/Fourth/Last/Day of Month
Day of Week Sunday to Saturday and Day option applicable for First and Last Day of the month selection.
Month January to December
Day Num Display only field. Values 1 to 8 are associated with Day of Week value, or values of 1 to 31 are applicable to Repeat option for Day of Month.
Yearly Example
Frequency Values/Meaning
Interval 2
Repeat Last
Day of Week Day
Day Num 8
Month December

In this example, the activity should occur once every two years and is scheduled on the last day of December.

If a meter is entered in a runtime interval rule, the following prerequisites must exist before creating a Preventive Maintenance schedule:

Defining Preventive Maintenance (PM) Schedules

  1. Navigate to the Find Preventive Maintenance Schedules window.

    This window enables you to enter information such as a Planner, to narrow your search for query mode.

    Select Yes in the Next WO Only field if you want the PM Scheduler to be able to create the next work order only if the previous work order has been completed for this work order completion date.

    To define a new schedule, click New.

    Preventive Maintenance (Schedule Definition)

    the picture is described in the document text

  2. Enter a Schedule Name.

    Important: If your PM schedule requires more than one activity and if the activities use different cycles, we recommend that you create separate PM schedules.

  3. Enter a Set Name.

    A PM schedule for an activity and an asset number or asset group must uniquely belong to a Set Name (See: Defining Set Names). Every Set Name has an end date. Every PM schedule that belongs to the Set Name must have its Effective To date before the end date of the PM Set Name. Before assigning a Set Name to a PM schedule, define Set Names within the Set Name Definition window. If you do not want to create Set Names, you can assign PM schedules to set, MAIN; it already exists.

    PM schedules might contain assets that transferred from one organization to another. The asset's destination organization can update and use the PM schedules that are assigned to a global PM set. However, you can only view, within the destination organization, PM schedules that are assigned to the asset's originating organization's local PM sets. You can copy these PM schedules to a global, local set or to your organization's local set.

  4. Select an Asset Type.

    Valid values are Capital and Rebuildable Inventory. If Capital is selected, the Asset Number and Asset Group fields refer to the asset number and asset group, respectively. If Rebuildable Inventory is selected, the Asset Number and Asset Group fields refer to the Rebuildable Serial Number and Rebuildable Item, respectively. If a Non-Serialized Rebuildable Item is entered in the Asset Group field, the Asset Number field is not required.

  5. Select an asset number.

    Assets that are maintainable and associated with activities are available. The Asset Group field populates with the asset group associated with the current asset number. If you wish to define a PM Schedule for a Non-serialized Rebuildable, enter the asset group; the Asset Number field does not apply.

    For assets that transferred from one organization to another, PM schedules that are defined for assets within their originating organizations are also visible within their destination organizations.

  6. Select a Schedule Type.

    Valid values are Rule Based and List Dates. If you select Rule Based, the Day Interval Rules and Runtime Rules tabs are enabled to enter information. If you select List Dates, you can define information within the List Dates tab.

  7. The Effective dates default from the current Asset activity association, if they exist. Optionally select or update the Effective From and Effective To dates.

  8. Optionally enter a Lead Time In Days.

    Lead time in a Preventive Maintenance Schedule is different than lead time associated with work order creation. Lead time within a Preventive Maintenance Schedule covers the time between the end date of the first execution of the Preventive Maintenance Schedule process, and the start date (system date) of the second execution of the Preventive Maintenance Schedule process. For example, a department executes the Preventive Maintenance Scheduler process every two months; the end date of each Preventive Maintenance Scheduler process is the end of every other month. However, due to circumstance, the meter data is not ready until the middle of the month. Therefore, the Preventive Maintenance Scheduler process starts in the middle of the month, instead of at the beginning, creating a lapse between the first and second Preventive Maintenance Scheduler executions. Lead time is used to cover this lapse.

  9. Optionally select Yes in the Generate Next WO field if you want to enable the scheduler to create the next work order only if the previous work order has been completed for the work order completion date.

  10. Optionally select a Work Order Status that best fits your business process.

    User-defined work order statuses for your organization are available for selection.

    Note: User-defined work order statuses are based upon system statuses and are assigned to organizations. For example, you can define a work order status of "Ready to Start" based on the Released system status. You can also have a work order status of Ready to Start based on the system status of Draft. Both statuses can then be assigned to your organization for use.

    When Preventive Maintenance work orders are generated, (See: Generating Work Orders, Oracle Enterprise Asset Management User's Guide) they are created with this specified status. You can optionally specify a different status for each PM schedule. You can also update this status, using the Maintenance Workbench (See: Using the Maintenance Workbench, Oracle Enterprise Asset Management User's Guide).

  11. Optionally select the Default check box to indicate that the current PM schedule definition generates work orders.

    If this check box is not selected, work order suggestions will not generate. You can have only one Default PM for an asset item and activity combination.

  12. Optionally select the Reschedule Manual Work Orders check box.

    If this check box is selected, non-firm, unreleased manual work orders are considered during PM scheduling.

  13. Optionally select a Planner to assign to this work order.

  14. If the Run To Failure check box is selected, the Preventive Maintenance Scheduler does not automatically schedule this asset number and activity association, although you can create manual work orders.

    This is relevant for asset numbers that cost more to maintain than the asset number itself. You might also check this box for forecasting and budgeting reasons. For example, your asset is a conveyor belt. It is common in maintenance environments to let this asset wear out completely before replacing it. You estimated that the life of this asset is 18 months, and have set up a schedule for a replacement work order every 18 months. In reality, you found that the belts have worn out every 12 months, affecting your cost budget.

    You can select this check box and clear it later. For example, you might associate a non-maintainable asset to an activity, but maybe you cannot currently maintain or schedule this asset. You might have future plans to maintain this asset number.

    If this check box is selected, the work orders for this asset do not appear in the Maintenance Workbench at the time of PM Scheduling (See: Using the Maintenance Workbench, Oracle Enterprise Asset Management User's Guide).

  15. For new PM schedule definitions, the default value for the Reviewer is based on the user login information, and the Review Date field defaults to the current system date.

    If you are updating a PM schedule definition, the Reviewer field indicates the last reviewer of the PM Schedule, and the Review Date field indicates the date on which the last review occurred. When updating the schedule definition, the Reviewed Date can be changed.

  16. In the Scheduling Options region, indicate how the PM Scheduler process calculates work order dates (see PM Scheduling Options).

  17. In the For Multiple Rules region, indicate how the predicted due dates are determined for multiple rules.

    • First: The due date is set to the first due date of all rules.

    • Last: The due date is set to the last due date of all rules.

    For example, below is a Runtime Rule that includes two meters, Meter1 and Meter2.

    Schedule Based On Example
    Interval Effective From Effective To Meter
    100 0 10,000 Meter1
    50 0 2,500 Meter2

    If you specify First in the Multiple Rules region of the PM schedule definition, between the two meters, the first meter that hits the due reading triggers the service. In this case, if Meter1's reading reaches the interval of 100 first, the service happens before Meter2's reading reaches its interval of 50. Conversely, you can choose Last in the Multiple Rules region. In this case, even if Meter1 reaches its due reading, the service is not scheduled until Meter2 has also reached its due reading.

    This region is disabled if the current PM schedule definition's Scheduling Type field is populated with List Dates.

  18. Optionally enter a value for the Intervals Per Cycle field. This field represents the number of base intervals that comprise the complete cycle. For example, 12 monthly intervals would comprise a 1-year cycle, and four 7,500 miles base intervals would comprise a 30,000-mile cycle.

    The system automatically updates these fields:

    • Current Cycle: The current execution cycle of a Preventive Maintenance cycle for an asset. This field is automatically updated by the system when preventive maintenance work orders generated out of a given schedule are completed.

    • Current Interval Cycle: The current execution interval within a current running cycle. This field is automatically updated by the system when preventive maintenance work orders generated out of a given schedule are completed. It is advisable not to change the current cycle and current interval count after initial definition, unless really required to do so. These fields can be disabled for edit by users through function based menu exclusions.

  19. Within the Activity region, select one or multiple Activities. Activities associated with asset numbers or non-serialized rebuilds are eligible for scheduling.

    A Maintenance Planner can create a single PM schedule for multiple activities on an Asset. You can list multiple activities to perform on an asset that share a common base interval of either a date, meter, or both. Each maintenance activity on the schedule generates work orders, based on a multiple of the base interval occurring. The group of maintenance activities on one PM schedule represents a cycle of activities. After the cycle of activities completes, the cycle restarts. For example, you can define a PM schedule for two activities that have a common Base Interval of 7,500 miles. The first activity is an oil change, and is scheduled every 7,500 miles. The second activity, a tune-up, is scheduled for every fourth interval or 30,000 miles. The work order for the oil change generates on each occurrence of the 7,500 mile interval and the work order for the tune-up generates on the fourth interval occurrence.

    When an asset transfers to another organization, the schedule that is associated with the local PM Set is viewable within the new organization. For example, the PM Set Name, Local, is created in organization, EM1. A PM schedule is defined in EM1 for Asset Number, #1554877, and is associated with Local (Set Name). Asset Number #1554877 is transferred to another eAM-enabled organization, EM2. A planner in this new organization (EM2) can view the PM schedule that is associated with the Local PM set. However, it is view-only; it cannot be updated. The associated activity appears in blue, to indicate that the activity definition has not yet been assigned to EM2. In this scenario, to use the PM schedule, the planner must either assign the schedule's activity to the current organization, EM2, or update the schedule's PM Set Name from Local to a global set or a local PM set that was defined in EM2.

    Note: You can define an unlimited number of activities, however, it is recommended that you keep it simple.

  20. Optionally indicate the Interval Multiple of the Base Interval. This field works with the Repeat in Cycle field to determine how many intervals for an activity to repeat.

  21. Optionally select the Repeat in Cycle value to determine if the activity interval repeats in the cycle. If you select Yes, the Interval Multiple field determines how many times the activity interval repeats. If you select No, the activity is scheduled once for each cycle.

  22. Optionally enter a Tolerance In Days to indicate a minimum interval in days between the suppressed activity and activity suppressing it.

  23. Optionally choose Last Service Info to enter the last service information for the current asset number and activity association.

    Enter Last Service start and end dates. These dates are used by the Preventive Maintenance Scheduler as a starting point for calculating the next due date for a suggested work order. After the Preventive Maintenance Scheduler suggests a work order, and that work order is completed, this date resets to the completion date. Last service information is always regarding the asset number and activity association, and independent of the association's PM schedule definition.

    The Last Service Reading cannot be greater than the last meter (if the meter is ascending), or less than the last meter reading (if the meter is descending).

    Last Service Information

    the picture is described in the document text

  24. Within the Date Rules tab, optionally enter Effective From and To dates to specify the rule's expiration.

    This tab is enabled if Rule Based is populated in the Schedule Type field.

  25. Enter a Base Interval In Days. For example, if you enter the number three, a work order suggestion is created every three days.

    You can optionally create variable Date Rules. For example, you would like work order suggestions created every three days in January, and every four days in February.

  26. Optionally within the Meter Rules tab, select a Meter Name to indicate that Preventive Maintenance scheduling is based on a Meter Rule.

    If you have previously set up a Date Rule, you can base the scheduling on a Meter Rule, as well. Meters associated with this asset number (See: Associating Meters with Asset Numbers), and with the Used in Scheduling check box selected in the meter definition, are available.

    For example, a Truck 01 Asset Number is scheduled for an oil change every 30 days, or every 1000 miles.

    Date Rule
    Field Value
    Last Service Date December 26, 2001
    Interval In Days 30
    Meter Rule
    Field Value
    Last Service Reading 3000
    Interval 1000
    Last Service Reading Date January 1, 2002 (this can be found via meter reading history)
    Usage Rate 25 miles per day (calculated as the total of the meter readings value changes, divided by the total of the meter reading date intervals)

    If the Meter Rule is taken into account, the next due date is February 10, 2002 (January 1 2002 + 40 days), and every 40 days after that. This is calculated as the interval (1000 miles) divided by the usage rate (25 miles per day).

    The PM Scheduler process compares the above suggested dates from the meter rule, to those of the date rule: Base Date of December 26, 2001 + every 30 days.

    The work orders ultimately created by the PM Scheduler process are those of the shortest interval and earliest dates: December 26, 2002 + every 30 days.

    Note: Meter Rules are not applicable for Non-Serialized Rebuildables.

  27. The Interval and UOM fields work together. For example, for every 2000 miles, this asset number needs an oil change.

    The UOM defaults from the meter definition of the current meter.

    You can optionally create multiple Meter Rules. For example, from zero to 10,000 miles, you would like your asset serviced every 3,000 miles. From 10,000 to 50,000 miles, you would like your asset serviced every 2,000 miles.

  28. You cannot enter the Last Service Reading. This field is automatically updated with the meter reading information recorded at work order completion (See: Work Order Completion, Oracle Enterprise Asset Management User's Guide).

    Note: The Preventive Maintenance Scheduler (See: Generating Work Orders, Oracle Enterprise Asset Management User's Guide) automatically calculates the meter usage rate, based on historical data, which is then used to predict the next meter due date. Refer to the example below.

  29. If you populated List Dates within the Schedule Type field, select the List Dates tab to define the specific due dates that work orders should transpire.

    For example, you want asset, Car1, serviced on May 1 and November 1 every year for the next three years. In this case, you would create a List Dates type schedule definition, and list all the due dates within this tab. The PM Scheduler process creates suggested work order dates on those specified dates.

  30. Save your work.

Multiple Activity PM Schedule Definition - Fixed Meter Example

Parameters for Conveyor PM Schedule

The following are the steps you will perform:

  1. Enter the meter name and define the scheduling starting point to the right of the meter.

    The system will define default values for the following:

    • Intervals per Cycle

    • Current Cycle

    • Current Interval Count

  2. Enter the required activities, taking the following into consideration:

    • The activity “Inspection” is scheduled after 100 hours of operation: (Interval Multiple (1) x Base Interval (100)).

    • The activity “Minor PM” is scheduled after 200 hours of operation.

    • The activity “Major PM” is scheduled after 400 hours of operation.

    • Repeat in Cycle determines if an activity can occur multiple times during a cycle, in this example the Inspection can occur multiple times within the cycle, the Minor PM will not be planned at the 400 hour interval.

  3. Enter the meter name with a base interval of 100.

  4. Save your work.

    the picture is described in the document text

Analysis of Example

The program will update Current Cycle and Current Interval Count when PM work orders are completed. For example at 210 hours of operation, two Inspection work orders and one Minor PM work order have been generated and completed. The Current Interval Count has been updated to (2). The Current Interval Count provides a count within the Current Cycle, the Current Interval Count is updated to (1) with the start of each new cycle.

The Current Cycle provides a count of the number of times a PM Set (Inspection, Minor PM and Major PM) has been completed. In this example, the Current Cycle remains (1), the Current Cycle will be updated to (2) with the completion of the PM Set and the start of a new cycle.

When forecasting work orders for the next 30 days, note that the activity “Minor PM” is not included in the forecast but the activity “Inspection” is included, the “Repeat in Cycle” controls if an activity will occur within a Cycle. For the activity “Inspection” the Repeat in Cycle is “Yes”, for the activity “Minor PM” the Repeat in Cycle is “No”, the “Minor PM” will be generated once per cycle.

the picture is described in the document text

To define a Preventive Maintenance schedule for an asset route

Preventive Maintenance Schedules can be defined based on Asset Routes. See: Setting Up Asset Routes.

  1. Navigate to the Preventive Maintenance Schedules window.

  2. Select Asset from the Item Type list of values.

  3. Select an Asset Route from the asset number list of values.

  4. See: Preventive Maintenance Scheduling, for instructions on the remaining fields.

    Note: You can define Date Rules and List Dates for asset routes. You cannot define Meter Rules.

To create a suppression activity

You can suppress other activities with the current activity in the scheduling definition. You can enter suppression activities for an asset number and activity combination.

For example, there are two activities associated with a Truck 01 asset: Oil Chafnge (to be performed every five months), and Major Service (to be performed every 12 months). A major service on a Truck 01 includes an Oil Change. Therefore, a suppression definition needs to be defined; the activity, Major Service, suppresses the child activity, Oil Change.

  1. From the Preventive Maintenance Schedules window, choose Suppression.

    Suppression

    the picture is described in the document text

  2. Choose a Suppressed Activity. Activities associated with the asset numbers are available.

  3. Optionally enter a Description for this suppression.

  4. Optionally enter a numerical value in the Tolerance in Days field to indicate a minimum interval in days between the actual suppressed activity and the activity that suppresses it.

  5. Save your work.

    Note: Suppression is applicable to an activity association and can also be defined from the Activity Workbench and Suppression windows.

Creating PM Schedules for Multiple Assets Using Web ADI

You can create and update PM schedules for multiple assets using the PM Schedules Web ADI option from the Schedule Definition form.

Key features of the PM Web ADI Template:

The PM schedule header contains the schedule header information is used to load the schedule information and its related child data information.

To create PM schedules for multiple assets using Web ADI:

  1. Navigate to the Schedule Definition form (Enterprise Asset Management, Preventive Maintenance, Schedule Definition).

  2. Click New.

  3. Click Tools, and select the PM Schedules Web ADI option.

    The Create Document page appears.

    the picture is described in the document text

  4. Select the Viewer to be used for the template, for example, Excel 2007. This is a required step.

  5. Click Create, and the following message appears:

    the picture is described in the document text

  6. Click Open with or Save the file to a desktop folder.

  7. Open the file.

  8. Click the Enable Macros button.

  9. Update the spreadsheet and save your changes.

  10. Select Oracle, Upload from the Microsoft Excel toolbar to upload the new instance.

    This process synchronizes the data in the Excel spreadsheet with the live data in Web ADI. For more information, see Oracle Web Applications Desktop Integrator Implementation and Administration Guide.

Navigating to the Maintenance Workbench

You can access the Maintenance Workbench from the PM Schedule Definition window.

  1. Search for a specific PM schedule definition.

  2. Click Tools from the menubar.

    the picture is described in the document text

  3. Select Maintenance Workbench, and the Maintenance Workbench page appears.

    For more information, see Using the Maintenance Workbench, Oracle Enterprise Asset Management User's Guide.

Navigating to the Forecast Work Orders Page

You can access the Forecast Work Orders page from the PM Schedule Definition window.

  1. Search for a specific PM schedule definition, and click Launch.

    The Preventive Maintenance (Schedule Definition) page appears.

  2. Click Tools from the menubar.

  3. Select Forecast Work Orders.

    The Forecast Work Orders page appears. The default values for the schedule are populated on the page.

    the picture is described in the document text

  4. Enter a numerical value in the Horizon field, or select a date in the Cutoff Date field.

    The horizon indicates a specific number of days into the future that you want to forecast. The Cutoff Date can be a specific calendar date.

  5. Click Simulate to generate a 'what if' scenario. If you select Simulate, then you cannot implement work orders.

  6. View the forecasted work order result such as:

    • Action

    • Type

    • Asset Number

    • Activity information

    • Work Order information

    • PM Name

    the picture is described in the document text

  7. Click Run to implement work orders for forecasted work orders only based on the horizon or cutoff date.

    the picture is described in the document text

  8. Click the Select check box for each forecasted work order that you would like to implement.

    Note: You must select all activities that are associated with a work order.

  9. Optionally click Show Implement Additional Fields to enter values for the following:

    • Project

    • Task

    • Parent Work Order

  10. Click Implement, and the system completes the process.

    The following confirmation message appears:

    Your selected work orders have been implemented.

Related Topics

Entering Meter Readings, Oracle Enterprise Asset Management User's Guide

Generating Work Orders, Oracle Enterprise Asset Management User's Guide

Using the Maintenance Workbench, Oracle Enterprise Asset Management User's Guide)

eAM Planning and Scheduling

Oracle eAM uses work orders to create demand for asset maintenance. Operations within work orders are completed using the work orders' associated material and resource requirements (See: Overview eAM Work Management, Oracle Enterprise Asset Management User's Guide). Cost savings and work management efficiencies can be achieved by generating predictive work activities, and then using a planning process to balance the work load for resource management.

The process is as follows:

  1. A Master Demand Schedule is created.

  2. This Master Demand Schedule is attached to Material Requirements Planning (MRP) options.

  3. MRP is launched, creating planned work order suggestions.

    You can use the Planner Workbench to implement the suggestions into purchase requisitions or manufacturing orders.

  4. Using the Purchasing AutoCreate feature, purchase orders are created from the requisitions.

  5. After the purchase orders are received into inventory, you can issue material into a maintenance work order.

This section includes the following topics:

eAM Planning

Oracle eAM uses Material Requirements Planning (MRP) to calculate net material requirements from gross material requirements, by evaluating:

MRP then plans material replenishment by creating a set of recommendations to release or reschedule orders for material, based on net material requirements. MRP assumes infinite capacity is available to meet the material requirements plan.

The following illustration depicts how eAM uses MRP.

eAM Material Requirements Planning

the picture is described in the document text

This section includes the following topics:

eAM Scheduling

Oracle Enterprise Asset Management (eAM) uses the Oracle Production Scheduling application to schedule work orders and operations. The scheduling process calculates work order and operations scheduled duration and dates, based on the forward or backward scheduling goal (See: Routine Work Orders, Oracle Enterprise Asset Management User's Guide), and Work in Process parameters. The concurrent program is triggered after a work order is released (See: eAM Work Order Statuses, Oracle Enterprise Asset Management User's Guide). The work order is automatically moved to a Pending Scheduling status, until the concurrent program finishes scheduling. At that time, the work order is moved back to a Released status.

The Scheduler Workbench enables a planner to graphically view and reschedule single work orders and operations. It provides you with a visual display of work orders. You can interactively reschedule work orders, operations, and resources.

Important: You have the eAM Scheduler (infinite scheduler) available to you; this scheduler is not constraint-based.

Additional Information: Oracle eAM uses the Infinite Scheduler for automatic scheduling. The Infinite Scheduler considers only the calendar and shift setups for scheduling. It does not consider shift exceptions or take the resource loads and availability into consideration. The Resource Availability form is a view to display information on the availability and considers exceptions so that you can perform manual scheduling accordingly.

Defining a Master Demand Schedule Name

Before you define a master schedule manually or load a schedule from another source, you must first define a master demand schedule name. You can also set several options for each name.

To define a Master Demand Schedule name

  1. Navigate to the MDS Names window.

    Master Demand Schedules

    the picture is described in the document text

  2. Enter a Name and Description for the schedule.

  3. Save your work.

Related Topics

Defining a Schedule Name, Oracle Master Demand Scheduling/MRP and Oracle Supply Chain Planning User's Guide

Defining a Material Requirements Plan Name

The Master Demand Schedule names trigger the material requirements planning process. A master demand schedule name must be created to perform material requirement planning for maintenance work orders.

To define a MRP name

  1. Navigate to the MRP Names window.

    MRP Names

    the picture is described in the document text

  2. Enter an alphanumeric Name to identify a unique material requirements.

  3. Optionally enter a Description of the MRP name.

  4. Optionally select the Feedback check box to monitor the quantity of the planned order that has been implemented as maintenance work orders, purchase orders, or purchase requisitions.

    This provides the planner visibility of the plan's status at any point in time.

  5. Optionally select the Production check box to enable a plan to automatically release planned orders.

  6. Optionally enter an Inactive On date on which to disable the plan.

    As of this date, you can no longer update the plan or use the plan name in the planning process. You can still view information and run reports for disabled names.

  7. Save your work.

Related Topics

Overview of Planning Logic, Oracle Master Demand Scheduling/MRP and Oracle Supply Chain Planning User's Guide

See: Auto-release Planned Orders, Oracle Master Demand Scheduling/MRP and Oracle Supply Chain Planning User's Guide

Defining MRP Names, Oracle Master Demand Scheduling/MRP and Oracle Supply Chain Planning User's Guide

Defining Plan Options

You can enter plan options for any plan. If you are launching the planning process for this plan name for the first time, the plan options you defined in the setup parameters are displayed. Otherwise, the plan options you chose, for the last launch of the planning process, are displayed.

Supply Chain Planning users can also launch a DRP and supply chain MRP and master production schedule (MPS) plan (See also: Reviewing or Adding Plan Options, Oracle Master Demand Scheduling/MRP and Oracle Supply Chain Planning User's Guide).

To enter plan options

  1. Navigate to the Plan Options window.

    Plan Options

    the picture is described in the document text

  2. Select a material requirements Plan.

  3. Select a master demand Schedule.

  4. Select MRP from the Type list of values.

  5. Select an Overwrite option:

    All: For a master production schedule (MPS) plan, overwrite all entries and regenerate new MPS entries based on the source master demand schedule.

    For an MRP, overwrite all MRP firm planned orders for MRP items. This option is displayed when you generate a plan for the first time.

    Outside planning time fence: For a master production schedule (MPS) plan, overwrite all MPS entries outside the planning time fence. For an MRP, overwrite all planned orders and firm planned orders outside the planning time fence.

    None: Do not overwrite any firm planned order for MPS or MRP plans.

  6. Select the Append Planned Orders check box to append new planned orders.

    For information regarding situations that cause new planned orders to append, see: Reviewing or Adding Plan Options, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide.

  7. Select the Net WIP check box to indicate that the planning process considers standard discrete jobs, nonstandard discrete jobs, or repetitive schedules when planning items during the last plan execution.

  8. Select Net Reservations to indicate that the planning process considers stock designated for a specific work order when planning the items during the last execution of the plan.

  9. Select Net Purchases to indicate that the planning process considers approved purchase requisitions when planning the items during the last execution of the plan.

  10. Select Plan Capacity to indicate whether the planning process calculates safety stock for each item during the last plan execution.

    • Specify the Bill of Resource (for MPS plans) and optionally a Simulation Set.

      See: Capacity Modifications and Simulation, Oracle Capacity User's Guide and Overview of Bills of Resources, Oracle Capacity User's Guide.

  11. Select Pegging to calculate graphical pegging information.

    The planning process then traces supply information for an item to its corresponding end demand details, which you then can view in a graphical display. See: Overview of Graphical Pegging, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide.

    • If you are working in a project environment, set a Reservation Level and, Optionally a Hard Pegging Level. See: Reviewing or Adding Project MRP Plan Options, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide.

  12. Select a Material Scheduling Method:

    • Operation Start Date: Schedule material to arrive in inventory for availability on the start date of a specific operation.

    • Order Start Date: Schedule material to arrive in Inventory for availability on maintenance work order start date.

  13. Specify which planned items you want included.

    • All planned items: Include all planned items in the planning process.

      You would choose this option to be certain that all items are planned, including those you add to a work order or schedule, that are not components on any bill of material. Use this option to avoid missing items you want to plan. For items you do not want to plan, define them with an MRP planning method of Not Planned when defining an item in Inventory.

    • Demand schedule items only

    • Supply schedule items only

    • Demand and supply schedule items

  14. Save your work.

Related Topics

Launching the Planning Process, Oracle Enterprise Asset Management User's Guide

Viewing Suggested Demand, Oracle Enterprise Asset Management User's Guide

Reviewing or Adding Supply Chain Plan Options, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide

Quality Integration Setup

A maintenance work order goes through various steps in its lifecycle (See: eAM Work Order Statuses, Oracle Enterprise Asset Management User's Guide). One of the steps in the lifecycle is Completion. When completing a maintenance work order, if the asset number has associated, mandatory quality collection plans, you need to enter quality results for the work order. A list of quality collection plans associated with the completion transaction appears during the completion process.

While creating a collection plan, you have the option of adding collection triggers to the plan. Triggers are restrictions that you define for a collection plan. For example, work orders for assets that belong to the TRUCK Asset Group require the entry of quality results for the collection plan. Data collection is initiated if all collection trigger conditions are satisfied.

You can use EAM quality plans for assets, work orders, and work order operations.

You can associate electronic reporting and electronic signatures (ERES) enabled transaction events such as Quality Result Creation or Update and enforce signature flows when you add and update quality results for Asset Query quality collection transactions in the Quality Workbench. For the list of Oracle Quality events seeded in Oracle E-Records, see E-records and E-signatures for Oracle Quality in the Oracle Quality User's Guide.

Quality setup tasks for EAM include the following:

Creating Collection Elements

Collection elements are the basic building blocks of collection plans, the data structures that you use to collect Quality results. Before you can collect quality data, you must first create a collection plan. Begin by creating collection elements, which define the characteristics of the product or process that you want to monitor, record, and analyze. See: Overview of Collection Elements, Oracle Quality User's Guide.

You can associate electronic reporting and electronic signatures (ERES) enabled transaction events such as Quality Result Creation or Update and enforce signature flows when you add and update quality results for Asset Query quality collection transactions in the Quality Workbench. For the list of Oracle Quality events seeded in Oracle E-Records, see E-records and E-signatures for Oracle Quality in the Oracle Quality User's Guide.

When you define collection elements, you are creating data fields that you can use in collection plans to collect quality results. After you create a collection element, it is available as a selection on a list of values that you can choose from when you set up collection plans. You can create an unlimited number of user-defined collection elements, or you can use any of Quality's predefined collection elements (See: Predefined Collection Elements, Oracle Quality User's Guide) in your collection plans; for example, Asset Num, Asset Serial Number, Asset Group, Activity, Work Order, and Maintenance WorkOrder. The Maintenance WorkOrder collection element must be used when you define a parent-child collection plan relationship to track the relationship between the source work order and the quality action triggered work order or work request. See Creating Parent-Child Collection Plans for more information.

You can also create collection elements by copying them from one collection plan to another.

To define collection elements

  1. Navigate to the Collection Elements window.

    Collection Elements

    the picture is described in the document text

    Note: The steps listed below describe how to define collection elements one-at-a-time in the Collection Elements window. You can also define several collection elements simultaneously using the Collection Elements Summary window. See: Combination Blocks, Oracle Applications User's Guide.

    Note: The following Collection Elements are included with Oracle Enterprise Asset Management; you do not need to define them: Asset Group, Asset Num, Asset Serial Number (the asset's Inventory Serial Number), Activity, Maintenance Work Order, Maintenance Operation Sequence.

  2. Select the Collection Element name.

    The collection element can contain alphanumeric characters, spaces, underscores, and single quotation marks. You cannot use words that are reserved for column names, such as NAME, OCCURRENCE, and ORGANIZATION_ID. See: Reserved Words, Oracle Quality User's Guide.

  3. Select the Enabled check box to enable the collection element. You can add enabled collection elements to collection plans.

  4. Select its collection Element Type. See: Collection Element Types, Oracle Quality User's Guide.

  5. Enter text for the data entry Prompt. The prompt is the label for the collection element field displayed in the Results region of the Enter Quality Results window. Prompts also become the column headings on reports and online inquiries. The default prompt is the name of the collection element, but you can overwrite it.

  6. Optionally enter a Hint.

    Hints are additional text that appears in the message line, as you enter quality results, to guide you during data entry. See: Message Line, Oracle Applications User's Guide.

  7. Select the collection element's Data Type.

    You can select any data type, however, you cannot change it after you define the collection element. The available data types are Character, Number, Date, Comment, and Sequence.

    Important: Oracle eAM Self-Service Applications do not support the use of sequence data type collection elements.

  8. Optionally select the Mandatory check box to indicate that a value must always be entered for this collection element, when entering quality results. A mandatory collection element can be redefined as non-mandatory when added to a collection plan.

  9. Enter the Reporting Length.

    The reporting length specifies how much space is allocated for this collection element's quality results values on reports, inquiries, and in the Enter Quality Results window.

    Note: The reporting length does not determine the amount of space used to store quality results values in the quality data repository. Results values can be up to 150 characters in length.

  10. If the Data Type is Number, enter the Decimal Precision.

    If you define specification limits for this collection element, entering the decimal precision (refers to the number of places after the decimal point) here controls the decimal precision of the specification limit values that you can define.

  11. Optionally select a UOM. See: Overview of Units of Measure, Oracle Inventory User's Guide. Units of measure can be entered for any collection element, regardless of data type.

  12. Optionally enter a Default Value for the collection element.

    When you set a default value for the collection element (generally, the most commonly used value for the collection element), it is automatically entered when you enter quality results. You can overwrite this value. See: Default Value Assignment Rules, Oracle Quality User's Guide.

  13. Optionally enter the SQL Validation Statement.

    This statement is used for validation when you enter quality data. You can base a collection element's data validation on any table in the Oracle database. To do this, you can define a SQL validation statement that Quality uses for validation when you collect quality data. This SQL statement must be a SELECT statement in which you select two columns. For example, if you have entered machine numbers in the database table, you can cross-validate machine numbers entered as you collect quality results against the numbers. See: SQL*Plus User's Guide and Reference.

    For example, to validate machine numbers from a table called 'machine_numbers' stored in the database, enter the following SQL validation statement:

    SELECT machine_number, machine_description

    FROM machine_numbers

    WHERE NVL(disable_date, SYSDATE+1) > SYSDATE

    AND organization_id=:parameter.org_id

    ORDER BY custom_machine_number

    Note: To constrain the SQL Statement to the current organization, you can use the variable, ':parameter.org_id' for the current organization id. To constrain the SQL Statement to the current user's id, you can use the variable, ':parameter.user_id' for the current user's id.

    If you define both a SQL validation statement and a list of collection element values, the list of values is used for validation; the SQL validation statement is ignored.

Related Topics

Overview of Collection Elements, Oracle Quality User's Guide

Collection Element Types, Oracle Quality User's Guide

Predefined Collection Elements, Oracle Quality User's Guide

Collection Element Values, Oracle Quality User's Guide

Defining Collection Element Actions, Oracle Quality User's Guide

Defining Collection Element Alert Actions, Oracle Quality User's Guide

Viewing Collection Elements, Oracle Quality User's Guide

Creating eAM Quality Collection Plans

You create collection plans to identify the data that you want to collect, and what actions you want to take based on the quality results that you collect. You can use collection plans to model your test or inspection plans, and you can create an unlimited number of plans to support your enterprise-wide quality data collection and analysis needs. Collection plans are invoked manually for direct results entry, or automatically as you complete a work order.

To collect quality data, you must set up a data collection structure called a collection plan. Collection plans are composed of collection elements, their values and specifications, and any actions that you want to initiate in response to quality results. There are some considerations that you must make before you set up collection plans. You first must create collection element types, then the individual collection elements that comprise the plan.

You can attach illustrative or explanatory files to collection plans, in the form of text, images, word processing documents, spreadsheets, or video. Attachments are used to document instructions and corrective action procedures. They are viewed by operations personnel during quality data collection. See: Attachments for Collection Plans, Specifications, and Result Lines, Oracle Quality User's Guide and Viewing Attachments Associated with Quality Results, Oracle Quality User's Guide.

To review a collection plan

  1. Navigate to the Collection Plans window.

    Collection Plans

    the picture is described in the document text

    Note: To assist you as you create collection plans, you can select the Summary/Detail option from the View Menu, and run a query to view existing collection plans in summary format. See: Combination Blocks, Oracle Applications User's Guide.

  2. Select a valid Collection Plan.

    To create a new collection plan, See: Creating Collection Plans, Oracle Quality User's Guide.

  3. Choose Transactions.

    You can create collection plans that are specifically used to collect quality data during transactions performed in other applications (See: Collection Plans for Transactions, Oracle Quality User's Guide).

    Collection Transactions

    the picture is described in the document text

  4. Select EAM Work Order Completion or Asset Query from the Transaction Description list of values.

    • EAM Asset Query: Enables quality results collection for an asset, independent from any transaction on the asset.

    • EAM Operation Completions: Enables quality results collection for a work order's operation pertaining to operation completion or during operation completion (See: Operation Completion, Oracle Enterprise Asset Management User's Guide).

    • EAM Work Order Completions: Enables quality results collection for a work order pertaining to work order completion or during work order completion (See: Work Order Completion, Oracle Enterprise Asset Management User's Guide).

    • EAM Asset Check In Transaction: Enables you to record quality information, describing the condition of the asset, during a Check In procedure (See: Asset Tracking, Oracle Enterprise Asset Management User's Guide).

    • EAM Asset Check Out Transaction: Enables you to record quality information, describing the condition of the asset, during a Check Out procedure (See: Asset Tracking, Oracle Enterprise Asset Management User's Guide.

  5. Select a Workbench Layout. You can choose Single Row or Multiple Row. The Multiple Row option enables you to set up data entry for multiple rows of results. The default value is Single Row.

  6. Optionally indicate whether this collection plan requires the entry of quality results at work order completion. If you select the Mandatory check box, you must save at least one quality data record before saving the work order completion transaction.

    Note: eAM supports Quality collection during operation completion transactions, as w ell as Standalone Asset Query. Valid Transaction Description values are EAM Operation Completions and EAM Asset Query, respectively.

  7. Optionally select the Background check box.

    If you select this check box, you can collect quality results for context reference elements (See: Reference Information Collection Element Type, Oracle Quality User's Guide).

    Note: The following Collection Elements are included with Oracle Enterprise Asset Management; you do not need to define them: Asset Group, Asset Number, Activity, Maintenance Work Order, Maintenance Operation Sequence.

    Without invoking the Enter Quality Results window, background data collection is initiated when you save the work order completion transaction.

    The system then finds, selects, and initiates the appropriate collection plan or plans.

    If collection triggers are defined for background data collection, data collection is initiated if all collection trigger conditions are satisfied (you define triggers for transactional data collection in the Collection Transactions window).

    Several collection plans can collect data in the background during the same transaction.

    When this is the case, the results for context elements on all of these collection plans are automatically saved when the parent transaction is saved.

  8. Select the Enabled check box.

  9. Optionally select a Trigger Name. Values are Activity, Asset Group, Asset Number, Asset Serial Number, Work Order, and Maintenance WorkOrder. Triggers are restrictions that you define for this collection plan. In the above example, work orders for the JP1 asset require the entry of quality results for the collection plan.

    Note: If a trigger is not defined, then all work orders will require quality collection results; the collection plan is applicable to all assets.

  10. If you selected a Trigger Name, select a Condition.

  11. Select a From value.

    For example, if you selected Asset Group as the Trigger Name, Asset Groups are available. Optionally you can enter a To value to create a range condition. For example, if the trigger is work order, you might enter a range of work order numbers.

  12. Save your work.

Creating EAM Parent-Child Collection Plans

You can create child collection plans in EAM to capture quality information.

Important: Creating a parent-child relationship does not automatically establish a relationship between collection plans for existing data.

Prerequisites

  1. Set up a collection plan relationship indicating whether the child data entry will be immediate, automatic, historical, or delayed. See Defining Parent-Child Collection Plans, Oracle Quality User's Guide for more information.

  2. Add the Maintenance WorkOrder collection element to the EAM child quality collection plan.

    This step ensures that the source work order name is passed down from the parent collection plan to the child collection plan so that you can use EAM parent-child collection plans (Enterprise Asset Management, Quality, Setup, Define Parent Child Plan Relationship).

To set up and use EAM parent-child collection plans, see Parent-Child Collection Plans in the Oracle Quality User's Guide for information regarding the following:

Related Topics

Adding Collection Plan Attachments, Oracle Enterprise Asset Management User's Guide

Triggering a Work Request, Oracle Enterprise Asset Management User's Guide

Collection Plans for Transactions, Oracle Quality User's Guide

Overview of Collection Plans, Oracle Quality User's Guide

Overview of Quality Self-Service, Oracle Quality User's Guide

Collection Plan Types, Oracle Quality User's Guide

Collection Plan and Import Results Database Views, Oracle Quality User's Guide

Collection Elements in Collection Plans, Oracle Quality User's Guide

Defining Collection Plan Element Values, Oracle Quality User's Guide

Associating Specification Types with Collection Plans, Oracle Quality User's Guide

Defining Collection Plan Element Actions, Oracle Quality User's Guide

Updating and Deleting Collection Plans, Oracle Quality User's Guide

Viewing Collection Plans, Oracle Quality User's Guide

Creating eAM Quality Collection Plans for a Supplier

eAM enables you to create Quality collection plans that are optionally mandatory for a supplier to enter crucial Quality data, via iSupplier Portal, before the supplier can complete an Outside Service Processing operation.

To create and eAM quality collection plan for a supplier

  1. Navigate to the Collection Plans window.

    Collection Plans

    the picture is described in the document text

    Note: To assist you as you create collection plans, you can select the Summary/Detail option from the View Menu, and run a query to view existing collection plans in summary format. See: Combination Blocks, Oracle Applications User's Guide.

  2. Select a valid Collection Plan.

    To create a new collection plan, See: Creating Collection Plans, Oracle Quality User's Guide.

  3. Choose Transactions.

    You can create collection plans that are specifically used to collect quality data during transactions performed in other applications (See: Collection Plans for Transactions, Oracle Quality User's Guide).

    Collection Transactions

    the picture is described in the document text

  4. Select EAM Operation Completions from the Transaction Description list of values.

  5. Optionally select the Mandatory check box to indicate that this collection plan requires the entry of quality results at the operation completion.

    If this check box is selected, the supplier must enter quality data before completing the Outside Services operation.

  6. Save your work.

Related Topics

Creating eAM Quality Collection Plans

Adding Collection Plan Attachments, Oracle Enterprise Asset Management User's Guide

Triggering a Work Request, Oracle Enterprise Asset Management User's Guide

Overview of Collection Plans, Oracle Quality User's Guide

Overview of Quality Self-Service, Oracle Quality User's Guide

Collection Plan Types, Oracle Quality User's Guide

Collection Plan and Import Results Database Views, Oracle Quality User's Guide

Collection Elements in Collection Plans, Oracle Quality User's Guide

Defining Collection Plan Element Values, Oracle Quality User's Guide

Associating Specification Types with Collection Plans, Oracle Quality User's Guide

Defining Collection Plan Element Actions, Oracle Quality User's Guide

Updating and Deleting Collection Plans, Oracle Quality User's Guide

Viewing Collection Plans, Oracle Quality User's Guide

Outside Processing Integration Setup

Contractor services are defined as work services provided by an organization or person who is not an employee of your company. Contractors are paid for their work based on an agreed upon contract or agreement. For example, a contractor service is a painting service. It is also important to associate the purchasing transactions, such as the requisition and purchase order, to the work order. In order for this to execute, you must complete the appropriate steps in Purchasing and Enterprise Asset Management.

Outside Service Processing provides the functionality to create items that are contractor services, such as landscaping, include these items on a work order, and execute the related purchasing transactions as the work order is released. By creating a contract service as an Outside Service Processing item, the purchasing requisition is created when the work order is Released. The additional purchasing transaction, including the creation of the purchase order, the approval, and invoicing process, are then managed by Purchasing. This optional process ensures that the actual charges are applied to the work order. The supplier accesses the purchase order and maintenance work order via iSupplier Portal. Within iSupplier Portal, the supplier can view all open and closed outside service operations and their associated maintenance work orders. The supplier can enter mandatory collection plan results, before completing the outside operation (See: Oracle iSupplier Portal, Oracle iSupplier Portal User's Guide).

The other option is to enable Standard Rate. This applies predetermined standard rates, for contractor services, to the work order.

Outside Processing Setup tasks for Enterprise Asset Management include the following:

Setting Up Outside Service Processing

Purchasing recognizes items, while eAM recognizes resources. As a result, you must link the contractor service item to a resource, for the purchase order to link to the work order. This is associated via the Resources window. Additionally, the resource must associate with a department. The department must specify the location where the services are to deliver. This must be a valid location for the organization.

For each contractor service resource, you can determine whether the rate charged to the work order is a standard rate or the actual amount, based on the purchase order price. This is set up within the Resources window, and may vary for each resource.

To set up purchasing information

  1. Navigate to the Financials Options page.

  2. Select the Supplier-Purchasing tab.

    the picture is described in the document text

  3. The options you define in this region, except for Inventory organization, are used as default values for the Purchasing region of the Suppliers window (See: Suppliers, Oracle Payables User's Guide).

    The supplier values default to new supplier sites for the supplier, which default to new purchasing documents for the supplier site.

  4. Select Ship-To and Bill-To Locations.

    These are the names of the ship-to/bill-to location for the system default values. If the name you want is not available, use the Location window to select a new location (See: Setting Up Locations, Using Oracle HRMS - The Fundamentals).

  5. Select an Inventory Organization.

    You can associate each of your purchasing operating units with one inventory item master organization. Your eAM Organization (See: Enabling Organizations for Enterprise Asset Management) should point to this item master. When you associate your purchasing operating unit with an inventory organization, items you define in this organization become available in Purchasing. You can choose an inventory organization that uses the same set of books as your Purchasing operating unit. Do not change the inventory organization after you have already assigned on to Purchasing.

  6. Optionally select a Ship Via code.

    This is the freight carrier you use with suppliers. If the type of freight carrier you want is not available, use the Freight Carriers window to define a new shipping method. The value you enter here is the value in the Description field of the Freight Carriers window in Purchasing.

  7. Select a FOB.

    If the type of FOB you want is not available, use the Oracle Purchasing Lookups window to define a new FOB.

  8. Select a Freight Terms code.

    The fright terms for a supplier identify whether you or your supplier pays for freight charges on goods you receive. You can define new freight terms in the Oracle Purchasing Lookups window.

  9. Save your work.

To set up outside services as items

Create an item for each outside service such as landscaping services.

  1. Navigate to the Master Item window.

    Master Item

    the picture is described in the document text

  2. Enter the item Name for the contractor service. For example, Landscape Service.

  3. Select Copy From within the Tools menu.

  4. Select @Outside Processing Item from the Template list of values.

  5. Choose Apply.

  6. Choose Done.

  7. Within the Purchasing tab, ensure that the Outside Processing Item check box is selected.

  8. Select the Resource Unit Type.

    Resource costs are based on the resource standard rate.

  9. Select a Default Buyer.

  10. Enter a List Price for this contractor service.

  11. Select Each for the Unit of Issue.

    This is the unit of measure you use to issue the item from inventory.

  12. Within the Receiving tab, select Direct from the Receipt Routing list of values.

  13. Save your work.

  14. Select the Organization Assignment tab on the left side of the window, then assign this item to the eAM organization.

  15. Save your work.

To link outside service items to resources

You must define outside resources and link them to outside items in order to automatically generate purchase requisitions for outside services. When you assign outside resources to a department, you also specify a usage rate or amount that determines the quantity you are requisitioning and/or charging to work orders.

  1. Navigate to the Resources page.

    Resources

    the picture is described in the document text

  2. Select a unit of measure (UOM).

    This value is the default unit of measure for all transactions, for the current resource.

  3. Verify that the Enabled check box is enabled for outside processing.

  4. Enter the outside services Item that was entered in Inventory and associate it with the eAM resource.

  5. Select the Costed check box to include this outside resource in your work order cost.

    When you define a resource with a charge type of PO Receipt, Cost Management automatically defaults Outside Processing as the cost element.

  6. Enter an Absorption Account.

    You must define an absorption account for each outside resource. The absorption account defaults from the organization's receiving account, which is debited when an outside processing item is received and is subsequently credited when the item is delivered to eAM. The debit goes to the outside processing account associated with the accounting class of the work order when the item is delivered to eAM.

  7. Optionally enter a Variance Account.

    You must define a purchase price variance account for each outside resource you define. This account defaults from the organization's purchase price variance account. If you select the Standard Rate check box while performing the next step, the Variance Account is mandatory.

  8. Optionally select the Standard Rate check box to charge the standard, non-purchase order amount to the work order.

    Clear the Standard Rate check box to charge the work order with the actual purchase order amount.

    1. If you selected the Standard Rate check box, choose Rates to enter your standard rates.

      Resource Costs

      the picture is described in the document text

    2. Enter a Cost Type of Value. This is dependent on the costing method defined for your eAM organization.

    3. Enter a Resource Unit Cost.

    4. Save your work and close the window.

To link the outside service resource to a department

  1. Navigate to the Departments window.

    Departments

    the picture is described in the document text

  2. Select the Department to associate with the outside service resource.

  3. Select a Cost Category for this department.

    If this is left blank, then the costs related to this department are charged, based on the eAM parameter settings (See: Defining eAM Parameters).

  4. Select a valid Location. This is mandatory.

  5. Choose Resources.

    Department Resources

    the picture is described in the document text

  6. Select the outside service Resource.

  7. Optionally indicate whether this resource is Available 24 Hours a day.

    You cannot assign shifts to a resource that is available 24 hours a day.

  8. Optionally indicate whether this department can share this resource and capacity with other departments.

  9. Enter the number of capacity Units (resource units) available for this department.

  10. Save your work.

    For information on all remaining fields, See: Defining a Resource, Oracle Bills of Material User's Guide.

To define WIP parameters

  1. Navigate to the Work in Process Parameters page.

    Work in Process Parameters

    the picture is described in the document text

  2. Select the Outside Processing tab.

  3. Select a value for Requisition Creation Time.

    • At Job/Schedule Release - This enables automatic creation of a purchase order requisition, for contractor services, when the work order is Released.

    • Manual - Choose Manual to manually create requisitions.

      With this selection, requisitions are not automatically created.

    • At Operation - Oracle recommends that you do not select At Operation.

      Within eAM, At Operation is equivalent to selecting Manual.

  4. Save your work.

Related Topics

Supplier - Purchasing Financials Options, Oracle Payables User's Guide

Setting Up Direct Items

You can add direct items to a maintenance BOM (See: Setting Up Maintenance Bills of Material). When the maintenance BOM is associated with a work order, you can add more direct items to its material requirements list before it is released (See: Defining Inventory Material Requirements, Oracle Enterprise Asset Management User's Guide). The system automatically creates requisitions and purchase orders (if the Auto Request Material check box is selected within the maintenance BOM), for the associated direct items, when the work order is released for execution. The supplier can view the maintenance work order detail information within Work Order Details page through the iSupplier Portal.

To set up purchasing information

  1. Navigate to the Financials Options window.

  2. Select the Supplier-Purchasing tab.

    Financials Options

    the picture is described in the document text

    The options you define in this region, except for Inventory organization, are used as default values for the Purchasing region of the Suppliers window (See: Suppliers, Oracle Payables User's Guide).

    The supplier values default to new supplier sites for the supplier, which default to new purchasing documents for the supplier site.

  3. Select Ship-To and Bill-To Locations.

    These are the names of the ship-to and bill-to location for the system default values. If the name you want is not available, use the Location window to select a new location (See: Setting Up Locations, Using Oracle HRMS - The Fundamentals).

  4. Select an Inventory Organization.

    You can associate each of your purchasing operating units with one inventory item master organization. Your eAM Organization (See: Enabling Organizations for Enterprise Asset Management) should point to this item master. When you associate your purchasing operating unit with an inventory organization, items you define in this organization become available in Purchasing. You can choose an inventory organization that uses the same set of books as your Purchasing operating unit. Do not change the inventory organization after you have already assigned it within Purchasing.

  5. Optionally select a Ship Via code.

    This is the freight carrier you use with suppliers. If the type of freight carrier you want is not available, use the Freight Carriers window to define a new shipping method. This value is used as the default value for the Description field in the Freight Carriers window in Purchasing.

  6. Select a FOB.

    If the type of FOB you want is not available, use the Oracle Purchasing Lookups window to define a new FOB.

  7. Select a Freight Terms code.

    The fright terms for a supplier identify whether you or your supplier pays for freight charges on goods you receive. You can define new freight terms in the Oracle Purchasing Lookups window.

  8. Save your work.

Related Topics

Non-Stock Direct Item Setup

Setting Up Asset Bills of Material

Setting Up Maintenance Bills of Material

Defining Rebuildable Bills of Material

Supplier - Purchasing Financials Options, Oracle Payables User's Guide

iSupplier Portal User's Guide

Cost Management Integration Setup

Costs are generated as maintenance work is executed and completed. These costs roll up through the parent and child hierarchies defined within Enterprise Asset Management, and can roll up to any level within an asset hierarchy. Labor, Material, and Equipment charges can further classify into several maintenance cost categories.

All work is captured and retained by Enterprise Asset Management. You can reference work that has been completed to review operations, resources, and costs. This information can help you understand the scope of work and the process by which it is completed.

This section includes the following topics:

eAM Costing Methods and Mappings

eAM supports four perpetual costing methods: standard, average, FIFO, and LIFO. As a foundation, eAM uses the following five basic cost elements provided by Cost Management (See: Cost Elements, Oracle Cost Management User's Guide):

Asset management requires different cost classifications. eAM provides these cost classifications, while maintaining the integrity of the basic costing rules. The five cost elements above are translated into cost elements that are familiar to maintenance managers.

eAM classifies work done on maintenance work orders into cost categories. By default, eAM has defined three cost categories: Contract, Operations, and Maintenance.

You can define additional cost categories, if needed. Each cost category is further classified into three cost elements: Equipment, Labor, and Material.

Material charges are classified as Material cost elements. Resource charge of type person is classified as a Labor cost element. Resource charge of type machine is classified as Equipment cost element. All other resource types are classified by the default cost element in the eAM Parameters (See: Defining eAM Parameters).

For each department, a maintenance cost classification is identified to reflect the above breakdown. The cost category for the Material cost element is the cost category of the department assigned to the routing of the operation. For the Labor cost element, it is the cost category of the resource's owning department. For the Equipment cost element, it is the cost category of the asset's owning department.

eAM Mappings

The three cost elements (Material, Labor, and Equipment) are mapped to the five basic cost elements (Material, Material Overhead, Resource, Resource Overhead, and Outside Processing) provided by Cost Management.

The following diagram illustrates that the eAM Material cost classifications are mapped to Material, Material Overhead, and Outside Processing. Labor and Equipment cost classifications are mapped to Resource, Resource Overhead, and Outside Processing.

Cost Element Mappings

the picture is described in the document text

Setting Up Cost Categories

Cost category codes are used as the default for departments that do not have a cost category defined. Department costs are then posted to the appropriate cost elements. Values include Maintenance, Operations, Contract, and any other values that you might have added within this extensible lookup table. See: Overview of eAM Cost Management, Oracle Enterprise Asset Management User's Guide.

By default, eAM has defined three cost categories: Contract, Operations, and Maintenance. However, you can define additional cost categories, if needed. After you have added the cost categories, they are available in the Cost Category list of values, within the Enterprise Asset Management Parameters window (See: Defining eAM Parameters, Oracle Enterprise Asset Management User's Guide).

To define additional cost categories

  1. Navigate to the Oracle Manufacturing Lookups window.

    Cost Category Lookups

    the picture is described in the document text

  2. Select BOM_EAM_COST_CATEGORY from the Type list of values.

  3. Enter a numeric value in the Code field.

    Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.

    Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.

  4. Enter the Meaning of the code, for example, High.

  5. Enter a Description for the code.

  6. Optionally enter a Tag to categorize lookup values. This field is informational.

  7. The Effective From Date defaults as the system date, but you can update this.

    Optionally enter a Effective To Date to indicate an expiration date for the code.

  8. Select the Enabled check box to enable this code for Enterprise Asset Management.

  9. Save your work.

Setting Up Purchase Order Category Associations for Direct Items

You can specify whether direct items are material, labor, or equipment charges on a work order, based on the user-specified Purchasing Category on the requisition or purchasing line. Purchasing Categories are associated with a maintenance cost element and its respective valuation account. If an association is not set up, direct items are charged as material on the work order.

Direct items may be Non-Stock or Description-based. Non-Stock Direct Items are defined within Oracle Inventory (See: Non-Stock Direct Item Setup, Oracle Enterprise Asset Management User's Guide), and the Purchasing Category for this type of direct item defaults from the Purchasing category set's item assignments.

For projects, you can assign direct items to a Direct Item Expenditure Type, other than the one assigned at the organization level. This is performed based on the Direct Item Expenditure Type associated with the Purchasing Categories used on the requisition or purchasing line.

To set up associations for purchasing categories used for direct items

  1. Navigate to the Find Category Associations page.

  2. Choose New.

    Category Associations

    the picture is described in the document text

  3. Select a Purchasing Category.

  4. Select a Maintenance Cost Element.

  5. Select a Valuation Account.

    If the Maintenance Cost Element is Material, you can choose the Material Valuation Account. If the Maintenance Cost Element is Labor or Equipment, you can select the Resource or Outside Processing Valuation Accounts.

  6. Select a Start Date.

  7. Optionally select an End Date.

    A Purchasing Category may have one existing association at a time. If you want to assign a different association for a category, select an End Date.

  8. Select a Direct Item Expenditure Type if your organization uses Oracle Projects.

    This is a required step.

  9. Save your work.

Related Topics

Defining Items, Oracle Inventory User's Guide

Defining Categories, Oracle Inventory User's Guide

Defining Category Sets, Oracle Inventory User's Guide

Setting Up eAM Cost Management

You can reference work that has been completed to review operations, resources, and costs. This information can help you understand the scope of work and the process by which it is completed. To capture costs for all work within eAM, some key setups must be in place:

  1. Define a default cost element.

  2. Define a default cost category.

Follow these steps to define these key setups.

  1. Define a default cost element (Material, Labor, or Equipment) when setting up the eAM parameters. See: Defining eAM Parameters. This is used when no predefined mapping exists to the cost elements in eAM. For example, department overheads are not linked to a particular eAM cost element for cost analysis. Therefore, the default cost element carries the cost for analysis. Also, outside processing types of Currency, Amount, and Miscellaneous are not linked to a particular eAM cost element. When one of these types is used in outside processing, the costs are allocated to the default cost element (See: eAM Costing Methods and Mappings).

  2. Define a default cost category when setting up the eAM Parameters. This defaulted cost category is used if there is no cost category defined for the departments.

To define a default cost element and cost category

  1. Navigate to the Enterprise Asset Management Parameters page.

    Enterprise Asset Management Parameters

    the picture is described in the document text

  2. In the Cost Defaults region, select an eAM Cost Element to indicate how to capture cost overheads, and any miscellaneous resource costs.

    Values are Equipment, Labor, and Material.

  3. Select a Cost Category to use as the default for departments that do not have a cost category defined.

    Department costs are then posted to the appropriate cost classification.

To define a cost category by department

  1. Navigate to the Departments page.

    Departments

    the picture is described in the document text

  2. Select a Cost Category.

    Note: It is not required to provide a cost category for a department (crew). However, if you do not provide a cost category for a department (crew), costs for that crew are allocated to the defaulted cost category specified in the eAM parameters (See: Defining eAM Parameters). Each time costs for that element are charged to a work order, this default cost category is used for reporting and analysis.

Related Topics

Defining Departments and Resources

eAM Cost Estimation, Oracle Enterprise Asset Management User's Guide

Viewing Cost Information, Oracle Enterprise Asset Management User's Guide

Transferring Invoice Variances, Oracle Enterprise Asset Management User's Guide

Setting Up Zero Cost Rebuild Item Issue

Oracle EAM work order costing supports both WIP component issues and the return of rebuildables from and to expense subinventories at their current or zero cost. You can issue rebuildable components from the Expense Subinventory to the maintenance work order at zero cost and/or return rebuildable components to the Expense Subinventory at zero cost.

Oracle EAM parameters determine organization level defaults for individual transactions. Set up work order default information to establish how rebuildables are valued in the current organization.

To set up zero cost rebuild item issue

  1. Navigate to the Enterprise Asset Management Parameters page.

    Enterprise Asset Management Parameters

    the picture is described in the document text

  2. Within the Work Order Defaults region, select the Value Rebuildables at Zero Cost to indicate that rebuildable components charge at zero cost.

  3. Save your work.

Related Topics

Defining eAM Parameters

Process and Discrete Manufacturing Integration Setup

Oracle Enterprise Asset Management integrates with Process and Discrete Manufacturing, enabling your maintenance environment to identify eAM asset relationships with production equipment. This feature associates assets to the production equipment located in a discrete or process manufacturing organization. After establishing, you can view the resource usage (maintenance work orders, batches, or FPOs) originating from production, associated with a maintainable asset. In discrete manufacturing organizations, you can view maintenance equipment downtime requirements and their affect on capacity during production planning and scheduling.

This section includes the following topics:

Process or Discrete Organization Setup

To integrate eAM with process or discrete manufacturing, determine which process or discrete manufacturing organization is associated with your eAM organization.

Process Manufacturing organizations are never the same as eAM organizations; they are mutually exclusive. Although it is possible, Oracle does not recommend commingling eAM and discrete manufacturing organizations. They should have separate organization codes.

To associate a process or discrete manufacturing organization with an eAM organization

  1. Navigate to the Organization Parameters page, and select a valid process enabled or discrete manufacturing organization from the Organization Code list of values.

    Organization Parameters

    the picture is described in the document text

  2. Enter an EAM organization to associate with the current organization code.

    This eAM organization is now linked to the organization code you selected.

Related Topics

Creating an Organization, Oracle Human Resources User's Guide

Associating Assets with Production Equipment

You can link an asset to production equipment defined within a process or discrete organization, as well as asset equipment defined within an eAM organization. This relationship is defined while defining or updating assets within eAM.

To associate an asset with production equipment

  1. Navigate to the Define Asset Number page.

    Define Asset Number

    the picture is described in the document text

  2. Select an Asset Number that you want to link to production equipment.

  3. In the Production tab, select a valid Production Organization.

    The list of values displays those process and discrete organizations that have the current eAM organization selected as their maintenance organization (See: Organization Setup).

  4. Select an Equipment Item.

    This is mandatory if you populated the Production Organization field. Items that were defined with an equipment template (See: Item Templates, Oracle Inventory User's Guide), or with the Equipment item attribute enabled (See: Physical Attributes, Oracle Inventory User's Guide), are available.

  5. Enter an Equipment Serial Number. This is mandatory if you populated the Production Organization field. This is the specific name of the component within the Equipment Type, defined above.

Related Topics

Defining Asset Numbers

Viewing Resource Usage, Oracle Enterprise Asset Management User's Guide

Encumbrance Accounting

Enterprise Asset Management enables you to use encumbrance accounting for purchase requisitions and purchase orders associated with work orders with a destination type of shop floor.

Prerequisites

You must perform the following setup tasks before you can use encumbrance accounting:

  1. Ensure that your eAM organization is associated with an operating unit that allows encumbrance accounting.

  2. Select the Reverse Encumbrance option on the Organization Parameters - Costing Information tab.

  3. Include a budget account in the maintenance WIP accounting class for encumbrance accounting.

Related Topics

See Encumbrance Accounting

Project Manufacturing Integration Setup

Enterprise Asset Management supports a variety of ways to define work breakdown structures. The methods include, using third party project management systems (with on-line integration), project templates, Seiban number wizard, copy, and manual entry. Work breakdown structures are commonly needed for program management. To support financial project management an reporting, the combination of Oracle Projects and Oracle Project Manufacturing enables budgeting, project costing and tracking, project billing, project revenue recognition, project cash forecasting, and project cost collection, including multi-currency and tax regulations.

To support project supply chain management and execution, Project Manufacturing provides functionality for project sales management, project advanced supply chain planning, project procurement, project execution, and project quality management.

The following diagram illustrates the eAM Project Manufacturing process:

  1. A maintenance work order is linked to a project or task.

    If a requisition or purchase order is created for that work order, the work order commitments for the associated project or tasks are updated.

  2. The Project Cost Collector process (See: Project Cost Collector, Oracle Cost Management User's Guide) passes the costs to the work order associated project WIP accounting class accounts, rather than the WIP accounting class associated with the eAM asset or eAM organization.

  3. Resources and material are charged against a work order.

  4. The work order is associated with a project.

    The charges are transferred to the project expenditures using the Cost Collector process.

eAM Project Manufacturing

the picture is described in the document text

This section includes the following topics:

Project Definition

You can inquire on an existing, or copy a new project from a template or existing project. To create a new project, See: Project Definition (Assigning Project Parameters), Oracle Project Manufacturing User's Guide. Associate this project number with a planning group, a cost group, and a default WIP accounting class.

To inquire on an existing project

  1. Navigate to the Find Projects page.

    Find Projects

    the picture is described in the document text

  2. Select a project Number.

  3. Choose Find.

  4. Choose Open.

    Projects, Templates

    the picture is described in the document text

  5. Optionally you can view detailed task information by choosing Detail (See: Viewing Project Details, Oracle Project Manufacturing User's Guide).

To assign project parameters

  1. Navigate to the Project Parameters page.

    Project Parameters

    the picture is described in the document text

  2. Select a valid Project Number.

  3. Optionally select a Planning Group.

  4. Select a Cost Group.

    If the current organization has selected Average as its primary costing method in the Organization Parameters window, the Cost Group field is required. The list of values includes the Common Cost Group and the user defined cost groups. The list of user defined cost groups includes those cost groups with valid accounts and with Project selected in the Cost Group window (See: Project Cost Groups, Oracle Cost Management User's Guide). You must assign the project to its own Cost Group to keep weighted average costing at the project level.

    Associate a Maintenance type WIP Accounting Class to this Cost Group. See: Project Cost Groups, Oracle Cost Management User's Guide.

  5. Optionally assign a Maintenance WIP Accounting Class to the current project.

    You can select any Maintenance type WIP Accounting Class that is associated with the selected Cost Group.

  6. Optionally select the name of the Planning Group with which you want to associate your project.

    If you plan material requirements by a group of projects, rather than by each individual project, you need to define a planning group and to assign all the projects to this planning group. If you plan material requirements by a single project, you do not need to associate the project with any planning group (See: Defining Planning Group Lookups, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide).

  7. Select the Other tab.

  8. Select Maintenance from the Direct Item Expenditure Type list of values.

    This expenditure type enables the Cost Collector process to pass costs for direct items to project maintenance work orders. This is a required step.

  9. Save your work.

Related Topics

Associating a Work Order with a Project, Oracle Enterprise Asset Management User's Guide

Creating Purchase Orders from Requisitions, Oracle Enterprise Asset Management User's Guide

Updating the Commitments for a Project, Oracle Enterprise Asset Management User's Guide

Viewing Commitments, Oracle Enterprise Asset Management User's Guide

Project Definition, Oracle Project Manufacturing User's Guide

Assigning Project Parameters, Oracle Project Manufacturing User's Guide

Project Cost Groups, Oracle Cost Management User's Guide

Defining Project Cost Groups, Oracle Cost Management User's Guide

WIP Accounting Classes, Oracle Work in Process User's Guide

Project Manufacturing Parameters, Oracle Project Manufacturing User's Guide

Property Manager Integration Setup

The eAM and Property Manager integration enables eAM assets to correspond with locations defined in Property Manager. The information transferred from Property Manager are the three-level land or building hierarchies, and the associated Location Codes within Property Manager. eAM also provides user-defined Area codes, enabling you to logically sort assets by where they are physically located. However, Area codes in eAM do not equal locations in Property Manager. See: Setting Up Areas.

This section includes the following topics:

Setting Up eAM Prerequisites

The following must be defined within eAM before the Export Locations to Enterprise Asset Management concurrent request process can export locations into eAM:

Executing the Export Process

Locations from Property Manager are always exported as a hierarchy. The first time that you execute the process, the starting node of the hierarchy is specified as the top level of building or land hierarchies. Thereafter, any level within the building or land hierarchy is specified.

After the process has executed, any changes within Property Manager's building or land hierarchies are automatically changed within eAM's corresponding asset hierarchies.

The Export Locations to Enterprise Asset Management process executes from the Property Manager responsibility. This process can execute in both create and update modes.

To execute the Export Locations to Enterprise Asset Management process

  1. Navigate to the Submit Request page.

    Submit Request

    the picture is described in the document text

  2. Select Export Locations to Enterprise Asset Management.

  3. Enter the following parameters:

    • Batch Name: The Batch Name identifies each export process by name.

    • Location Code Low: This code, defined in Property Manager, is the starting node of the building or land hierarchies. This code reflects the Enterprise Asset Management Asset, and is normally entered into one Enterprise Asset Management Asset Group per transfer.

    • Location Code High: This code, defined in Property Manager, is the ending node of the building or land hierarchies. This code reflects the Enterprise Asset Management Asset, and is entered into one eAM Asset Group per transfer.

    • Default Organization: Select the eAM enabled organization. This code is defined within eAM. See: Organization Setup, Oracle Enterprise Asset Management Implementation Guide.

    • Default Asset Group Item: Select the asset group (defined within eAM). The eAM assets are created in this asset group. See: Defining Asset Groups, Oracle Enterprise Asset Management Implementation Guide.

    • Owning Default Owning Department: This is the designated maintenance department to associate with the exported asset/location within eAM.

    • Maintainable: Select whether the asset/location is maintainable within eAM.

  4. Choose OK.

  5. Choose Submit.

Related Topics

Property Manager Integration, Oracle Enterprise Asset Management User's Guide

Submitting a Request, Oracle Applications User's Guide

Executing the Asset Number Interface

Locations are set up in Property and are exported to Enterprise Asset Management (eAM) with a two-step process. This allows you the opportunity to modify data before it is exported to eAM. First, push the location records from Property Management to eAM (See: Executing the Export Process). After submission of the concurrent process, the Property Management Location information are entered into the EAM Asset Interface table and are accessed via the Pending Asset Number window within eAM. You can update all relevant information, including Asset Group, Asset Number, Owning Department, and WIP Accounting Class, for this information, before submitting the interface process.

To view pending asset numbers

  1. Navigate to the Pending Asset Number page.

    Pending Asset Number

    the picture is described in the document text

  2. Update the information, as necessary.

  3. Choose Submit to update your changes.

Related Topics

Executing the Export Process, Oracle Enterprise Asset Management Implementation Guide

Service Integration Setup

Use service requests to report and request maintenance service for unplanned maintenance demand on internal assets and rebuildable items. Service requests that are classified as type Maintenance are used to identify requests for eAM maintenance. For example, when personnel notice that a printer is broken, the person can create a service request, even though a technician is scheduled to regularly check the printer monthly. You can create both service and work requests for capital assets and rebuildables, simultaneously, within one eAM organization.

If a valid asset or rebuildable serial number is entered on the service request, the owning department for the serial number defaults. (See: Defining Asset Numbers, Oracle Enterprise Asset Management Implementation Guide), and the service request is visible within the eAM Maintenance Workbench. The Owning Department can then approve the service request and create a work order, or reject the service request and notify the service request owner to cancel it. However, customers or persons who report problems are often not aware of the asset or rebuildable's serial number requiring maintenance. In this situation, a default department is used as the Owning Department. You may customize an eAM Workflow process to identify appropriate default owning departments and department approvers. Within Oracle Service, an agent can create a request for maintenance, provide a problem summary, and provide any additional information, such as an incident address or notes.

A planner creates a work order and then releases it to execute. The planner can choose to create one or multiple work orders for a single service request. When a work order is complete, the service request owner updates the service request status to Closed.

A support agent can view all work order information for each work order created for a service request. You can create eAM work orders for service and work requests, or associate requests to existing work orders.

You can customize a workflow process that creates notifications to eAM personnel that indicate service requests requiring work and approval.

Note: Oracle Service must be installed to utilize service request functionality.

This section includes the following topics:

Creating Maintenance Service Request Types

Within Oracle Service, create at least one Maintenance Service Request Type. You can define multiple Service Request Types, if necessary.

To create a Maintenance service request type

  1. Navigate to the Service Request Type window.

    Service Request Types

    the picture is described in the document text

  2. Enter the name of the Service Request Type.

  3. Select Customer Support, from the Business Process list of values.

  4. Optionally select effective dates for this request type.

  5. Select the Asset Maintenance check box to indicate that this Service Request Type is of type Maintenance (viewable in eAM). Maintenance Type Service Requests are viewable in eAM.

  6. Save your work.

Enabling Service Requests for Assets and Rebuildables

To set up Service Request functionality for Asset and Rebuildable Serial Numbers, enable Asset Groups and Rebuildable Items for Service Requests, respectively.

To enable Service Requests for asset groups and rebuildable items

  1. Navigate to the Master Item window.

    Master Item

    the picture is described in the document text

  2. Select an Asset Group or Rebuildable Item.

  3. Select the Service tab.

  4. Select Enabled from the Service Request list of values.

  5. Save your work.

Enabling eAM Specific Fields

The Service Request page enables a customer support agent to view pertinent information for an entered service request, such as associated work orders and their statuses. It is necessary to have this important information visible at all times within the Service Request page. You can customize which fields and records appear (See: Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide).

Use Oracle's folders functionality to ensure that key eAM-specific fields are visible for maintenance service requests. By default, eAM specific fields are hidden. This folders feature provides you a user-defined display of retrieved information, such as:

You can prevent users from creating or modifying folders with profile option, FLEXVIEW: ALLOW_CUSTOMIZATION.

To display eAM-specific fields in the Service Request page

  1. Navigate to the Service Request page from the Create Service Request or Find Service Request pages. (Service > Service Requests).

    Service Request

    the picture is described in the document text

  2. From the Folder menu, select an existing, or create a new Folder definition.

    the picture is described in the document text

  3. Save your work.

Related Topics

Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide

Oracle Applications 12 Workflow

Oracle Time and Labor Integration Setup

Oracle Time and Labor (OTL) is the repository in which time is entered by personnel, including contingent workers, working in a particular organization. Personnel working on Oracle Enterprise Asset Management (eAM) work orders enter their time using OTL Self-Service. Information collected is stored in OTL Time Store, and is composed of a series of business rules and processes. eAM extracts information from the Time Store and charges eAM work orders for the time spent by personnel that work on them.

There are multiple steps within the integration flow:

  1. Timecard information is entered for a specific work order, within Oracle Time Store (part of Oracle Time and Labor).

  2. Information is then extracted from Oracle Time Store to Oracle Enterprise Asset Management. This extraction dynamically creates a resource transaction within Oracle Enterprise Asset Management.

  3. The Cost Manager process is executed, and the resource transactions are charged.

  4. View the actual costs within the work order for the period that you charged.

The process is as follows:

OTL Process Flow

the picture is described in the document text

This section contains the following topics:

Setting Up Overview

There are two required setup procedures for this integration:

  1. Establish personnel needing to use this functionality as Pe9rsons within Oracle Human Resources (See: People Management, Oracle HRMS Workforce Sourcing, Deployment, and Talent Management Guide.).

    After established, those persons are assigned to respective users within Enterprise Asset Management.

  2. Create Preference Values, and then link those values to eligibility criteria.

    Preferences provide you the opportunity to assign rules and options to your workers. It also lists the values that are predefined as default preferences. You can override the defaults by creating new preferences hierarchies. In the Preferences window, you can view the Default Preferences by expanding the Preference Tree node.

    See Enterprise Asset Management Preferences in Oracle Time & Labor in the Oracle Time and Labor Implementation and User Guide for more information regarding the preference values.

This section contains the following topics:

Defining Persons as Users

Establish personnel needing to use this functionality as Persons within Oracle Human Resources (See: Oracle Human Resources User's Guide). After established, those Persons must be assigned to the respective users, within Oracle Enterprise Asset Management (eAM).

To define Persons as Users within eAM

  1. Navigate to the Users window.

    Users

    the picture is described in the document text

  2. Enter a User Name.

  3. Select the Person that was created in Oracle Human Resources.

  4. Enter a Password.

  5. Within the Responsibilities tab, select the appropriate Responsibilities to assign to this User.

    The responsibilities, US OTL Administrator and Self Service Time and Expenses, are seeded but the Administrator must manually assign them to the person/user.

  6. Save your work.

Creating Eligibility Criteria

You must create Preference Values, and then link those values to eligibility criteria.

Note: Preferences are seeded, but the preferences must be assigned to the user.

To create eligibility criteria

  1. Navigate to the Preferences page.

    Preferences

    the picture is described in the document text

  2. Select the Preference Tree node, then choose New.

  3. Enter the name of your tree.

  4. Select the Self-Service timecard, review and confirmation layout pages Preference.

  5. Within the OTL Preferences window, select EAM Timecard Layout from the Timecard Layout list of values.

    OTL Preferences

    the picture is described in the document text

  6. Select EAM Review Layout from the Review Layout list of values.

  7. Select EAM Confirmation Layout from the Confirmation Layout list of values.

  8. Choose OK.

  9. Save your work.

    After saved, you have created a new node on the Preference Tree. Expand this new node, and select EAM Self-Service Timecard.

  10. To create eligibility criteria for timecard entry, select the Eligibility Criteria tab.

  11. Enter the Name of the rule.

    You can have one rule for everyone, or multiple rules to create different eligibility criteria for different groups.

  12. Select EAM Self-Service Timecard from the Name of Branch list of values.

  13. Select Person, Organization, or All People from the Link by list of values.

    If you are creating one rule for all users, select All People.

  14. Enter a Precedence value.

    Values are all positive numbers. If you have multiple rules, the rule with the highest precedence is displayed first, and so on. For example, an employee can view the time card with a rule precedence value of 95, versus the timecard with a rule precedence value of 94.

  15. Save your work.

Related Topics

Time and Expenses, Oracle Enterprise Asset Management User's Guide

Work Order Billing Setup

While maintaining an asset or servicing a customer request, you can bill a third party customer for the work that they performed. The cost of the work performed is based on the material and resource requirements (bill of material) of the work order, or the cost of the activity associated with the work order.

This section includes the following topics:

Setting Up Item Costs and Prices

The Billing Basis is either Cost Plus or Price List. The Billing Basis affects your item setup procedures. If you want the flexibility of using both billing basis types for an item, you need to set up both costs and prices for that item. An item is an Activity, Material, or Resource.

This section includes the following topics:

Setting Up Parameters

You can optionally create the ability to change the billable material on a work order at the time a bill is created.

To enable the change of billable material functionality

  1. Navigate to the Enterprise Asset Management Parameters window.

    Enterprise Asset Management Parameters

    the picture is described in the document text

  2. Optionally select the Invoice Billable Items Only check box. If selected, you can change the billable material at the time the bill is created.

    If selected, this check box indicates that you want to invoice only billable items. Billable items are those that have a populated value within the Billing Type field, within the Service Tab, of the Master Item window. Billing Type is relevant only if you have this check box selected. Also, selecting this check box means that you can choose a different item to bill. See: Service Attribute Setup, Oracle Enterprise Asset Management Implementation Guide.

  3. Save your work.

Setting Up Costs for the Cost Plus Billing Basis

The cost plus method utilizes costs associated with an item. The item should have a cost defined for it. First, you need to ensure that the appropriate item attributes are set up correctly for the item.

To set up an item's attributes

  1. Navigate to the Master Item page.

    Master Item

    the picture is described in the document text

  2. Optionally select the Costing Enabled check box to report, value, and account for any item costs.

    You must select this check box if you are using the Cost Plus Billing method.

  3. Optionally select the Inventory Asset Value check box.

    You must select this check box if you are using the Cost Plus Billing method.

  4. Save your work.

To set up costs for an item

  1. Navigate to the Item Costs Summary page.

  2. Choose Costs.

  3. Enter cost information for your item.

  4. Save your work.

Related Topics

Costing Attribute Group, Oracle Inventory User's Guide

Defining Item Costs, Oracle Cost Management User's Guide

Setting Up Prices for the Price List Billing Basis

The Price List method uses a specified price list. The specified item should have at least one entry in the price list. You must begin by setting up the appropriate item attributes.

To set up an item's attributes

  1. Navigate to the Master Item window.

  2. Select an existing item or create a new one.

  3. Select the Order Management tab.

    Master Item - Order Management tab

    the picture is described in the document text

  4. Optionally select the Customer Ordered check box to create a price within the price list.

    You must select this check box if you are using the Price List billing method.

  5. Save your work.

To set up prices for an item

  1. Navigate to the Advanced Pricing - Price Lists window (Order Management > Pricing > Price Lists > Price List Setup).

    Advanced Pricing - Price Lists

    the picture is described in the document text

  2. Enter price information for your item.

    The same item can repeat multiple times in the price list, with varying values for Start Date, End Date, and Precedence. For example, it is invalid to have overlapping date ranges, if the Precedence is the same.

  3. Save your work.

Related Topics

Order Entry Attribute Group, Oracle Inventory User's Guide

Service Attribute Setup

Set the Billing Type for each item that you want billable. The Billing Type field within the Master Item window must be populated if you have selected the Invoice Billable Items Only check box, within the Enterprise Asset Management Parameters window. See: Setting Up Parameters, Oracle Enterprise Asset Management User's Guide.

To set up the Billing Type attribute

  1. Navigate to the Master Item window.

  2. Select the Service tab.

  3. Optionally select a Billing Type of Expense, Labor, or Material. This field must be populated if you have selected the Invoice Billable Items Only check box, within the Enterprise Asset Management Parameters window. See: Setting Up Parameters, Oracle Enterprise Asset Management User's Guide.

  4. Save your work.

Setting Up Billable Material

To create billable material:

  1. Set specific attributes within the Master Item window.

  2. Assign the resource item to your organization.

  3. Decide whether you are pricing this item using the Cost Plus or Price List method, or both, and perform the additional setup for those methods (See: Setting Up Item Costs and Prices, Oracle Enterprise Asset Management User's Guide

  4. Define costs and prices for your item.

To set up billable material

  1. Navigate to the Master Item window.

  2. Select the Invoicing tab.

  3. Optionally select the Invoiceable Item check box to indicate that the current material item can invoice.

    You can select this attribute at the Master Organization level.

  4. Optionally select the Invoice Enabled check box to indicate that invoices are enabled for the current material item.

    Note: For the current material item, you need to ensure the Billing Type is populated with Material, within the Service tab. See: Service Attribute Setup, Oracle Enterprise Asset Management User's Guide.

  5. Assign the current item to your organization.

  6. Save your work.

Setting Up a Billable Resource

To create a billable resource:

  1. Create a resource item by setting specific attributes within the Master Item page.

  2. Assign the resource item to your organization.

  3. Decide whether you are pricing this item using the Cost Plus or Price List method, or both, and perform the additional setup for those methods (See: Setting Up Item Costs and Prices, Oracle Enterprise Asset Management User's Guide).

  4. Define a resource and associate the resource item to the resource.

  5. Assign the resource to a department.

To set up a billable resource

  1. Navigate to the Master Item page.

    Master Item

    the picture is described in the document text

  2. Select the Invoicing tab.

  3. Optionally select the Invoiceable Item check box to indicate that the current resource item can invoice.

    You can select this attribute at the Master Organization level.

  4. Optionally select the Invoice Enabled check box to indicate that invoices are enabled for the current resource item.

    Note: For the current resource item, you need to ensure the Billing Type is populated with Labor, within the Service tab. See: Service Attribute Setup, Oracle Enterprise Asset Management User's Guide.

  5. Assign the current item to your organization.

  6. Save your work and close the window.

  7. Navigate to the Resources window.

    Resources

    the picture is described in the document text

  8. Enter the name of the Resource within the Resource field.

  9. Within the Billing region, select the resource item you created within the Master Item window to ensure that the resource is available for billing.

    Note: Rates defined in the Resources window are not used for billing. For billing rates for the resource item, See: Setting Up Item Costs and Prices, Oracle Enterprise Asset Management User's Guide.

  10. Save your work.

  11. Assign the current resource to a department. See: Defining Departments and Resources, Oracle Enterprise Asset Management User's Guide.

  12. Save your work.

Setting Up a Billable Activity

To create a billable activity, first set specific attributes within the Master Item window. Next, decide whether you are pricing this item using the Cost Plus or Price List method, or both, and perform the additional setup for those methods. (See: Setting Up Item Costs and Prices, Oracle Enterprise Asset Management User's Guide). Finally, associate the activity to the asset group or asset number that is used to create the work order.

To set up a billable activity

  1. Navigate to the Master Item window.

  2. Select the Invoicing tab.

  3. Optionally select the Invoiceable Item check box to indicate that the current activity item can be invoiced. You can select this attribute at the Master Organization level.

  4. Optionally select the Invoice Enabled check box to indicate that invoices are enabled for the current activity item.

  5. Assign the current item to your organization.

  6. Save your work.

Related Topics

Initiating Billing, Oracle Enterprise Asset Management User's Guide

Enterprise Asset Management Command Center Configuration

Setting Up Enterprise Asset Management Command Center

The Enterprise Asset Management Command Center configuration setup must be completed after the installation and common configurations are completed as described in My Oracle Support Knowledge Document 2495053.1, Installing Oracle Enterprise Command Center Framework, 12.2.

Setup and Configuration Steps

To complete setup of the Oracle Enterprise Asset Management Command Center, you must perform the following:

  1. Enterprise Asset Management Profile Options

  2. Configuring Descriptive Flexfields for Search

  3. Loading Enterprise Asset Management Data

Enterprise Asset Management Profile Options

You must set the following profile option for calculating work order schedule delays:

Profile Option Name Description
EAM: ECC WO Schedule Delay Alert The EAM: ECC WO Schedule Delay Alert profile option calculates the schedule delay of work orders that are in Open status with schedule delays. Values for this profile option include Yes, No, or Blank (null). This calculation and the resulting update to ECC occurs once each day to ensure the schedule delay is updated accurately. If the user chooses not to have the details updated during incremental load, then the profile option value should be updated to No.
EAM: ECC Is Employee Assigment Enabled The EAM: ECC Is Employee Assigment Enabled profile option captures information on whether or not the Employee Assignment page is enabled for a user. Values for this profile option include Yes, No, or Blank (null). A Blank or Yes value opens the Employee Assignment page for customers on release 12.2.10 and above. For customers below release 12.2.10, a Yes value navigates the user to the Employee Assignment menu but does not display any information. A No value opens the Crew Schedule page for customers on release 12.2.4 and above.
EAM: ECC Enable WO Dashboard Deeplink The EAM: ECC Enable WO Dashboard Deeplink profile option allows users to enable or disable the deeplink filter Last 21 to Next 21 Days in the Open Work Orders dashboard. Values for this profile option include Yes, No, or Blank (null). A Blank or Yes value enables deeplink for Last 21 to Next 21 Days in the Open Work Orders Dashboard. A No value disables deeplink Last 21 to Next 21 Days in the Open Work Orders Dashboard.
EAM: ECC Debug Profile Option The EAM: ECC Debug Profile Option enables data load logging. Select Yes to enable data load logging, and select No to disable data load logging.

Configuring Descriptive Flexfields for Search

Enterprise command centers support Descriptive Flexfields (DFFs) that enable you to search on DFF attributes. After you configure DFFs, you must run the data load process, which ensures that the DFF attributes are available in the command center.

Note: You must initially run the Metadata Load concurrent program to load the DFF setup information to Enterprise Command Center. After the DFF setup is initially loaded, running Incremental or Full Load concurrent programs on a regular basis will maintain the DFF attributes.

For additional information on configuring and customizing flexfields, see the Oracle E-Business Suite Flexfields Guide and My Oracle Support Knowledge Document 2495053.1, Installing Oracle Enterprise Command Center Framework, Release 12.2.

The following table describes the DFFs available in the Enterprise Asset Management dashboards:

Dashboard Data Set DFF Title DFF Name DFF Attribute Group Name
Open Work Orders Dashboard eam-wo Discrete Job Operation Information WIP_DISCRETE_JOBS Additional Details
Open Work Orders Dashboard eam-wo-op Work Order Operations OPERATIONS Additional Operation Details
Open Work Orders Dashboard eam-wo-op Work Order Resources OPERATION_RESOURCES Additional Resource Details
Assets Dashboard eam-asset-attrs Asset Attributes MTL_EAM_ASSET_ATTR_VALUES Asset Attributes (Asset Attribute Dataset)
Assets Dashboard eam-asset-details Item Instance Flexfield Details CSI_ITEM_INSTANCES Additional Details
Materials Dashboard eam-store-wo Component Information BOM_INVENTORY_COMPONENTS Additional Details

Loading Enterprise Asset Management Data

Run the concurrent program Enterprise Asset Management Command Center Data Load to load Oracle E-Business Suite data into the Enterprise Asset Management Command Center. You can find this concurrent program from the Reports tab in the Asset Management page.

Note: Before you load data from Oracle E-Business Suite into the Enterprise Asset Management Command Center, ensure that your EBS data is accurate and current by running any concurrent programs that impact attributes used in the command center.

To load Enterprise Asset Management data

  1. Select the Reports tab in the Asset Management page. The Request Submission page appears.

  2. In the Program Name field, enter Enterprise Asset Management Command Center Data Load.

    the picture is described in the document text

  3. Select the Parameters tab and then select the appropriate load type:

    • Full Load: Loads all eAM data and is required to be run for the first data load. If you select and run full load for subsequent requests, then this program clears all eAM from ECC and loads fresh data.

    • Incremental Load: Loads the data modified and updated from the previous load only. Incremental load should be scheduled to run as often as required to keep the ECC dashboard current.

    • Metadata Load: You must initially run the Metadata Load concurrent program to load Descriptive Flexfield (DFF) setup information to Enterprise Command Center. After the DFF setup is initially loaded, running Incremental or Full Load concurrent programs on a regular basis will maintain the DFF attributes. In this process, the application waits for other tasks such as consolidation, data entry, or other load processes to finish before proceeding to load the files.

    the picture is described in the document text

    the picture is described in the document text

  4. Select the Dashboards for loading full load or incremental load data. Data loading will be processed for the selected dashboard only. To load all dashboard data, select the All option.

    the picture is described in the document text

  5. Enter one or more language codes in the Languages field for the output. For multiple language codes, use the format AA,BB,NN. For example, enter US,AR,KO. If the field is blank, then the data will be loaded for the base language only (usually US).

  6. Enter the Organization Code. You can specify one or multiple organizations for sequential data loading. Full and incremental data loading can be sequentially scheduled by organization.

  7. Select the Log Level that you want the program to report. The default value is Error.

  8. Reset Dataset is applicable only for Full Load when ran sequentially for organization code(s). When set to True, data in all datasets related to that dashboard is cleared. Fresh data related only to the organization code(s) is loaded into the dataset and is visible on the dashboard.

  9. Select True to enable SQL trace. Otherwise, select False.

    the picture is described in the document text

  10. Select Continue. The Schedule Request: Review page appears.

  11. Submit the concurrent request.

To review request details

  1. From the Reports tab (Schedule Request: Define page), select the View Requests sub tab. The Requests page appears and displays all of your requests.

  2. In the row that contains your request, click the Details icon. The Request Details page appears and displays the ECC- Run Data Load information.

Enabling Data Load for Work Order Operation Data Set

An optional eam-wo-op data set loads work order operation data to ECC. If you require work order operational data to be loaded, then add this data set name to the lookup types EAM_ECC_DATA_SET_KEYS and EAM_ECC_WO_DATASET_KEYS.

If the eam-wo-op data set is added to the lookup EAM_ECC_DATA_SET_KEYS, then the eam-wo-op data load will run if the data load is submitted for All dashboards.

Additional Information: For adding a lookup to a lookup type details, refer to the section Application Utilities Lookups and Oracle Application Object Library Lookups in the Oracle E-Business Suite Developer's Guide.

Debugging Data Loads

You can enable debug logging of all data loading. The process creates log files for all data loads that can be used to help in debugging issues with data loading. In order to generate the log files, the following settings are required:

  1. The following profile option enables debug logging for all eAM Enterprise Command Center data load packages:

    • EAM: ECC Debug Profile Option - This profile option enables data load logging if the value is Yes, and disables data load logging if the value is No.

  2. A writable directory in v$parameter. These log files will be generated in the first writable directory specified in v$parameter. Run the following query to determine the path:

    select value from v$parameter where name='utl_file_dir';

Once data load logging is enabled, the application generates a log file in the first writable directory specified in v$parameter using the file name:

EAMECC<Dataset_Short_Code><DDMMYYYYHH24MISS>.log

Publishing Quality Collection Metadata to Enterprise Command Center

To publish EBS data to the Enterprise Command Center, run the Publish Quality Collection Metadata to Enterprise Command Center concurrent program. You can find this concurrent program under Reports in the Oracle Quality application.

Note: The Publish Quality Collection Metadata to Enterprise Command Center program should be run only after the patching window is complete. Avoid running the program during patching windows to ensure that the Publish Quality Collection Metadata to Enterprise Command Center program completes successfully and without errors.

Run the concurrent program from the Submit Requests window.

(N) Quality > Reports > Submit Requests

To publish quality collection metadata

  1. Choose Single Request and click OK.

  2. In the Name field on the Submit Requests window, select Publish Quality Collection Metadata to Enterprise Command Center.

  3. Use the Parameters window to enter the parameters information.

  4. In the Plans List field, select the default value ALL, or enter a list of plan names, separated by commas, upto a maximum of 150 characters.

  5. In the Create Plan Attribute Groups field, you can select the default value No, or select Yes to create plan attribute groups.

  6. In Publish/Reset field, you can select the default value Publish, or select Reset.

  7. In the Publish Quality Data From Date field, enter a valid date in the DD-MON-YYYY format.

    the picture is described in the document text

  8. Click OK on the Parameters window.

  9. Click Submit.

  10. Review your request using the Requests page.

  11. Run the full data load.

    See: Loading Oracle Quality Data.

Loading Inventory Management Data - Inventory On-Hand

The Materials dashboard displays on-hand inventory information in the Material Details table using the inv-onhand data set from the Inventory Management Enterprise Command Center application. To process and load on-hand inventory data from Oracle E-Business Suite (EBS) to the Materials dashboard, you must run the Inventory On Hand Data Load concurrent program. Run this program from the Submit Request window.

(N) Manufacturing and Distribution Manager > Material Planning > Others > Request

the picture is described in the document text

To run the Inventory On Hand Data Load:

  1. In the Name field, select Inventory On Hand Data Load.

  2. Select Full Load as the load type to load all on-hand data from EBS.

  3. In the Languages field, enter one or more language codes for the output. For multiple language codes, use the format AA,BB,NN. If the field is blank, then the data will be loaded for the base language only (usually US).

  4. Select the log level that you want the program to report. The default value is ERROR.

  5. Select TRUE to enable SQL trace. Otherwise, select FALSE.

  6. Submit the concurrent request.

  7. Review your request using the Requests page.

  8. Monitor data loading using the Data Load Tracking page of the ECC Developer responsibility.

    Note: Running the Enterprise Asset Management Command Center Data Load does not load on-hand inventory information in the Material Details table in the Materials Dashboard.

Loading Oracle Quality Data

To load Oracle E-Business Suite Quality data into the Enterprise Asset Management Command Center, run the concurrent program Quality Command Center Data Load. You can find this concurrent program under Reports in the Oracle Quality application.

Note: The Quality Command Center Data Load program should be run only after the patching window is complete. Avoid running this program for any of the available data load types during patching windows to ensure that the Quality Command Center Data Load program completes successfully and without errors.

Run the concurrent program from the Submit Request window.

(N) Quality > Reports > Submit Requests

To load Oracle Quality data

  1. Choose Single Request and click OK.

  2. In the Name field on the Submit Request window, select Quality Command Center Data Load.

  3. Use the Parameters window to enter the parameters information.

  4. The System Name field defaults to EBS.

  5. Select the appropriate load type:

    • Full data load - This process loads all Oracle Quality data and is required to be run for the first data load. The full data load process also includes metadata load. If you select and run full load for subsequent requests, then this program clears all Oracle Quality data from ECC and loads fresh data.

    • Incremental data load - This process loads the data modified and updated from the previous load only. Incremental load should be scheduled to run as often as required to keep the ECC dashboard current.

    • Metadata load - This process ensures the application waits for other tasks such as consolidation, data entry, or other load processes to finish before it loads the files. Note that the full data load process includes metadata load.

  6. Enter one or more language codes in the Languages field for the output. For multiple language codes, use the format AA,BB,NN. For example, enter US,AR,KO. If the field is blank, then the data will be loaded for the base language only (usually US).

  7. In the Enable SQL Trace field, select True to enable the SQL trace. Otherwise, select False.

  8. In the Log Level field, select the program you want to report. The default value is Error.

    the picture is described in the document text

  9. Click OK on the Parameters window.

  10. Click Submit.

  11. Review your request using the Requests page.

  12. Monitor data loading using the Data Load Tracking page of the ECC Developer responsibility.

To review request details

  1. From the menu, click Requests. The Find Requests window appears.

  2. Select the All My Requests radio button and click Find. The Requests window appears and displays all of your requests.

  3. In the Requests window, select the row that contains your request and then click View Details. The Request Detail window appears and displays the ECC- Run Data Load information.

  4. Click OK to exit and close the window.

Concurrent Program Scheduling

You can schedule the Enterprise Asset Management Command Center Data Load and Quality Command Center Data Load concurrent programs as you can with any other concurrent program in the standard Oracle E-Business Suite.

To schedule the Enterprise Asset Management Command Center Data Load concurrent program

  1. Navigate to the Schedule window:

    (N) Enterprise Asset Management responsibility > Reports

  2. Search or enter Enterprise Asset Management Command Center Data Load concurrent program in the Name field.

  3. Enter the report Parameters.

  4. Click the Schedule button. The Schedule window appears.

    the picture is described in the document text

  5. Enter your preferred schedule parameters.

  6. Click OK to save the schedule.

Results Tables Actions

Assets Dashboard Actions:

Results Table Name Results Table Action Page Navigation Actions Performed
Assets Update Update Asset Allows asset update actions such as adding and updating asset attributes, DFF updates, and so on.
Assets Create Work Order Create Work Order Asset number defaults to the Create Work Order page.
Assets Create Work Request Create Work Request Asset number defaults to the Create Work Request page.
Work Orders Update Update Work Order Allows work order update actions for selected records.
Work Orders Update Maintenance Routing Maintenance Routing Update Maintenance Routing form for the activity appears and allows updates.
(Suggested use-case: Identify activities with the highest deviation by using the Schedule Delay by Activity chart refinement. Review the schedule deviation hours from the results table and update the Maintenance Routing From form to optimize planned hours.)
Work Orders Create Activity Create New Asset Activity The Create Activity form appears with work order requirements defaults.
(Suggested use-case: Identify recurring failures using the Failures chart. Select a suitable work order from the results table and convert it into an activity from the Create New Asset Activity page.)
Work Orders Export Parameters selection Exports selected work orders from the results table to a csv file.
Work Orders Print Work Order Report Work Order Report Runs the Work Order Report for selected work orders in the results table.
Work Orders Export Work Orders Export Work Orders Generates a xml file for selected work orders in the result table.

Open Work Orders Dashboard Actions:

Results Table Name Results Table Action Page Navigation Actions Performed
Work Orders Update Update Work Order Resolve work order alerts. You can review and update work order schedule dates, resource assignments to resolve schedule delay alert, or review failure alert and plan the appropriate resources for work orders with issues.
Work Orders Quick Update Pop-up Updates the work order in real time for the following key attributes:

  • Work Order Type

  • Work Order Status

  • Work Order Priority

  • Work Order Scheduled Start Date

  • Work Order Scheduled Completion Date
Work Order Cost Estimate Details Update Update Work Order Review and update the resource and material information for high-cost work orders.
Work Orders and Work Order Cost Estimate Details Export Parameters Selected work orders from the result table are exported to a csv file.
Work Orders and Work Order Cost Estimate Details Print Work Order Report Work Order Report Runs the Work Order Report for selected work orders in the results table.
Work Orders and Work Order Cost Estimate Details Export Work Orders Export Work Orders Generates a xml file for selected work orders in the result table.
Work Requests Create Work Order Create Work Order A new work order is created with defaults from work request details. Clicking on Apply navigates back to the Open Work Order dashboard.
Work Requests Assign Work Order Assign Work Order A Work Request will be assigned to the work order.

Materials Dashboard Actions:

Note: The Materials Details results table and refinements data is available only when 'inv_ecc.zip' Inventory Management Command Center is imported into the ECC framework.

Results Table Name Results Table Action Page Navigation Actions Performed
Work Orders Materials Update Update Work Order Resolve work order alerts. You can review and update material requirements by adding new materials, or increasing and decreasing required quantity to the existing materials in the work order.
Work Orders Materials Delete Material Allocation Material Issue Refines data with the material shortage alert. The result table is refined with work orders containing material shortage.
Verify if the shortage material is allocated to other work orders that can be prioritized for later dates (By Schedule Date or Work Order Priority).
The Delete Material Allocation action is enabled for material lines containing allocated quantity of the shortage material. Select this action to navigate to the Material Issue page, Update Material Allocation to resolve the shortage for work orders with critical and immediate requirements.
Run the Component Pick Release concurrent program to allocate the materials to the priority work order.
Work Orders Materials Copy to Asset BOM Work Order Details When reviewing the unplanned material usage alert, the result table data is refined to display work orders containing more quantity issued than quantity required.
The Copy to Asset BOM action opens the Work Order page and defaults to Copy to Asset BOM under the Materials tab.
Use work order standard action to add the material to the Asset BOM.
Work Orders Materials Update Activity BOM n/a Review unplanned material usage for work orders and verify the material usage pattern to check if it is asset related or activity related. Use the Update Activity BOM action that is enabled for the work orders with activity association. The Maintenance BOM page appears for the selected activity to update the material required quantity.
Work Orders and Work Order Cost Estimate Details Export Parameters selection Exports selected work orders from the results table to a csv file.
Work Orders and Work Order Cost Estimate Details Print Work Order Report Work Order Report Runs the Work Order Report for selected work orders in the results table.
Work Orders and Work Order Cost Estimate Details Export Work Orders Export Work Orders Generates a xml file for selected work orders in the result table.