Set Up Maintenance

Maintenance Management is an optional functional area in the Manufacturing and Supply Chain Materials Management Offering that you must select for implementing Oracle Maintenance. In the Offerings work area, enable the Maintenance Management functional area at the offering level to make available the tasks for setting up some of these components.

You may refer to this information in the Get Started with Your Implementation section of the Getting Started with Your Maintenance Implementation guide.

After you enable the Maintenance Management functional area, follow these steps to set up and define master data for maintenance:

• Set up one or more maintenance-enabled inventory organizations. You will then need to perform the following setup tasks for each organization

  • Set up plant parameters

  • Set up work areas

  • Set up work centers

  • Set up resources

  • Define resource instances (optional)

• Review these optional areas to determine if additional setup is required:

  • Define maintenance lookups

  • Define maintenance descriptive flexfields (DFFs)

  • Define common descriptive flexfields (DFFs)
  • Define and configure the asset object using application composer

  • Define custom work orders statuses

  • Define custom work orders subtypes
  • Define Suppliers to allow the purchasing of Items (Assets)
  • Define Suppliers for reference as a Warranty Provider in Supplier Warranty (optional)
  • Define Manufacturers for reference in Supplier Warranty (optional)
  • Define Costing for Items, Resources and Equipment for Maintenance Work Orders

  • Set up maintenance organization relationships

  • Set up electronic signatures

  • Set the profile for the Manage Maintenance Work Orders page search criteria
  • Define Quality Inspection plans
  • Enable the Smart Search for Assets
  • Set up work requests using the Help Desk offering

You may want to consider licensing these additional offerings that complement Maintenance:

• License, enable, and setup the Help Desk offering to manage work requests
  • Define custom internal work order statuses (optional)
  • Review the Maintenance user guide for additional details
• License, enable, and setup the integration for IoT Asset Monitoring offering
  • Set up IOT integration for asset monitoring in FSM

After you complete the setup and define the master data, complete these additional steps to begin using the application. These steps are further covered in the Using Maintenance guide:

• Define inventory items in the Product Information Management work area for each of your inventory organizations:

  • Assets that are maintained require an inventory item that's asset-tracked and serial controlled.
  • Assets that are stocked in inventory require an inventory item that may be serial or lot controlled.
  • Assets that aren't maintained or stocked in inventory can be optionally based on an inventory item. These are considered descriptive assets.
  • Inventory Items that are defined as parts list items in an asset should also be defined. These items are used during the repair of an asset and can be purchased, received, stocked, issued, and returned from a maintenance work order

  • Enable each item for your inventory stock, manufacturing, and maintenance-enabled organizations. Items must be enabled for all maintenance locations in which you could create and execute work orders for a repair of an asset.

  • Define a default repair transaction code for each item, using a condition event code, that describes the item’s reference by system, assembly, and component (optional).
• Define condition event codes for use in IOT asset monitoring, maintenance programs, standard operations, supplier warranty, quality inspection, and failure capture (optional).

• Define standard operations (optional but recommended):

  • Within a standard operation, define condition event codes for use in supplier warranty (optional).

• Define maintenance work definitions (with and without standard operation references).

  • If you enable maintenance programs for assets across organizations, then you must have work definitions with the same code value in each organization where the work requirement may be used to create work orders.

• Set up one or more utilization meter template definitions:

  • Define item applicability in the meter templates definitions (optional). This must be defined prior to asset creation if you expect asset meters to be automatically created (recommended).
• Define supplier warranty coverage template definitions.
  • Reference covered items, meters, and repair transactions codes (optional).

• Create asset group rules, asset groups, and associate assets to groups (optional).

• Create customers with location details such as site, site use, and address
• Create trading community locations, which can be used as an external location address for an asset
• Create internal addresses in HCM, which can be used as an internal location address for an asset

• Create new enterprise assets and, if needed, customer assets.

• Create historical or initial meter readings for each asset (optional).

• Create preventative maintenance programs for assets (optional).

  • Define the historical last accomplished date and interval prior to cutover (optional).

• Define material availability rules (optional).

• Define asset and maintenance work order attachment categories (optional).

• Define work order custom work order subtypes (optional). Additional details are covered in the How You Manage Lookups for Maintenance section.
• Define supplier warranty provider labor rates using REST API or manage page (optional).
• Define supplier warranty standard repairs using REST API or manage page (optional).
• Define work order supplier warranty repair defaulting options by work order type and subtype (optional).
• Define asset maintenance parameters (covered in the section below).
• Enable the Oracle Search for the Assigned To field in a warranty claim (covered in the section below).

Here's a comparison of the available methods for creating the master data, definition, and execution objects required to use Maintenance:

Object	Manual Setup	REST API	File-Based Data Import Upload
Work area	Yes	Yes, using the Manufacturing Work Area REST API.	Not available
Work center	Yes	Yes, using the Manufacturing Work Area REST API.	Not available
Resources	Yes	Yes, using the Production Resources REST API.	Not available
Resource Instances	Yes	Yes, using the Production Resources REST API.	Not available
Standard Operations	Yes	Yes, using the Manufacturing Standard Operations REST API.	Not available. Note: You can mass create and update the standard operations and resources by using the Oracle Application Development Framework Desktop Integration (ADFdi). Find additional details in the Using Maintenance guide
Work Definitions	Yes	Yes, using the Manufacturing Work Definitions REST APIs: Create, update, and delete using the Work Definition Requests REST API. View using the Work Definitions REST API.	Yes, using the Maintenance Work Definition Import.
Item	Yes	Yes, using the Items REST API in Product Lifecycle Management	Yes, using the Item Import in Product Master Data Management
Meter Template	Yes, in the context of an asset or the Meter Template task flow	Yes, using the Meter Templates REST API	Not available
Meter Template: item applicability	Yes, in the Meter Template task flow	Yes, using the Meter Templates REST API	Not available
Asset Meter Association	Yes, you can manually associate a meter in the context of an asset	Not directly available through REST API; however, if item applicability is defined for a meter template by an item, asset meters can be automatically created during asset creation through the Installed Base Asset REST API	Not directly available through REST API; however, if item applicability is defined for a meter template by an item, asset meters can be automatically created during asset creation through the Installed Base Asset import process
Meter Readings	Yes, in the context of an asset or using the Complete with Details option in the Dispatch List for an operation	Yes, using the Meter Readings REST API	Yes, using the Meter Readings Import
Assets	Yes	Yes, using the Asset REST API	Yes, using the Asset Import
Condition Event Codes	Yes	Not available	Not available
Warranty Repair Codes	Yes, using the Condition Event Codes REST
Failure Codes	Yes, using the Condition Event Codes REST
Supplier Warranty Coverages	Yes	Yes	Yes, using the Warranty Coverages Import
Supplier Warranty Contracts	Yes	Yes	Not available
Supplier Warranty Entitlements	Yes, using the Manage Claims task flow	Yes	Not available
Supplier Warranty Claims	Yes, using the Manage Claims task flow	Yes	Not available
Supplier Warranty Provider Labor Rates	Not available	Yes	Not available
Supplier Warranty Provider Standard Repair Times	Not available	Yes	Not available
Work order warranty repair defaulting options by work order type and subtype	Yes	Not available	Not available
Work Requests (Internal Service Requests)	Yes	Yes	Not available
Preventative Maintenance Programs	Yes	Yes, using the Maintenance Programs REST API	Yes
Preventative Maintenance Programs History	Yes	Yes, using the Maintenance Programs REST API. You can define the historical last completed date and interval to initialize the forecast for an asset.	Not available
Asset Rules and Group Definitions	Yes	Yes, using the Asset Groups REST API	Not available
Asset Assignments to Groups	Yes, in the context of an asset or group	Yes, using the Asset Groups REST API	Yes, using the Asset Import for active groups
Customer	Yes, customer, account, and site details	See Oracle Customer Data Management and Purchasing documentation	See Oracle Customer Data Management and Purchasing documentation
External Address	Not available	External addresses are setup using a SOAP service. For more details about setting up a trading community location, refer to the Business Object Services chapter of the SOAP Web Services for CX Sales and B2B Service guide.	Not available
Internal Address	Yes, locations are defined in HCM	See HCM documentation	See HCM documentation
Attachment Categories	Yes, using the setup task Manage Attachment Categories for an Asset or Work Order object	Not applicable	Not applicable

Common Tasks That You Perform for Maintenance Management

Some tasks that are included in the Maintenance Management functional area will also apply to Manufacturing, as both offerings share many objects in the work setup and execution. For details about how to perform them, see the Oracle Applications Cloud: Using Functional Setup Manager guide.

Task	Required or Optional	Description
Manage Maintenance Value Sets	Optional	Create and maintain maintenance value sets
Manage Maintenance Descriptive Flexfields	Optional	Create attributes for the maintenance entities, define related validation, and display properties of descriptive flexfields maintenance work orders.
Manage work order subtypes	Optional	Create and maintain custom work order subtypes
Manage Search Indexes	Optional	Maintain attributes for entities that are searchable using the Oracle Search Extension Framework.

Site Profile for The Manage Maintenance Work Orders Search Page

The keyword search looks across work order records using a contains search criteria. For example, if you were searching for all work orders for assets that would be included an asset number range of Truck_ModelB_Version1 to Truck_ModelB_Version10, you can search by ModelB, Version, or Truck. However, if you have an extremely large volume of work orders, then you may find the time required to search to be inefficient and perhaps even timeout in the page. Therefore, you can optionally change the search to use a starts with method to improve performance. If set, the same search would require you to search by Truck or Truck_ModelB. The search method is set by a system administrator by changing the profile option ORA_MNT_ALLOW_CONTAINS_OP_IN_KEYWORD_SEARCH from Yes to No.

Define Asset Maintenance Parameters

There are several parameters that should be considered during maintenance implementation. You can access them using the Mange Asset Maintenance Parameters page in the Setup and Maintenance work area using the tab entitled Additional Parameters. These parameters are used by maintenance programs, supplier warranty, fault analysis, and for managing customer assets.

• The Default Master Organization for Maintenance Management parameter should be defined using your main master organization. The value can then be used for defaulting in the Manage Meter Templates and Fault Analysis Setup task flows. If not defined, then in these flows the user must manually enter the Master Organization Code value. The organization must be enabled for inventory.
• The Validation Organization for Customer Assets must be defined to create customer assets. The value is used as the Item Validation Organization to validate the properties of the item for which the customer asset is being created or updated. If the value isn't defined, you will be presented an error during asset creation. The organization can be an item or inventory organization.
• The Allow Suppress and Merge across Work Requirements in a Maintenance Program parameter defaults to a value of Yes. If set to Yes, then forecasts may merge or suppress across work requirements for matching assets and due dates in some scenarios, making it hard to understand the forecast output. Therefore, it is recommended to set this parameter to a value of No if you don’t wish for merge and suppress to be considered across work requirements. Generally, merge and suppress should only be modeled within a work requirement and not across work requirements.
• The Consider Organization Relationships When Creating Maintenance Work Orders Program parameter defaults to a value of Yes. When set to Yes, you must define organization relationships to create work orders across organizations. When set to No, you will only need to define organization relationships to support assets that operate in a non-maintenance organization by a maintenance program. Additional details are in the section below entitled Set Up Maintenance Organization Relationships.
  Note: If you intend for assets to routinely require maintenance across organizations, it is recommended to set the parameter Consider Organization Relationships When Creating Maintenance Work Orders Program to a value of No. Only if you wish to control which organizations can support each other should relationships be defined, and the value of the parameter be set to Yes.

Enable the Oracle Search for the Assigned To field in a Warranty Claim

The warranty claim has an optional field for assigning a primary contact for a claim. The Assigned To field allows you to search and select a worker’s name from the HCM workers list of values. Be default, the Assigned To list of values will not use Oracle Search. If you wish to enable it, then you can follow the guidance in the Using Common Features for HCM guide.

Additionally, ensure your users have this privilege to search and select values in the Assigned To field:

• Use REST Service - Workers List of Values(PER_REST_SERVICE_ACCESS_WORKERS_LOV_PRIV)