This chapter covers the following topics:
Oracle Enterprise Asset Management (Oracle eAM) supports sophisticated, condition-based maintenance strategies for property, plants, and public infrastructure. Oracle eAM's single instance design ensures best practices and quality compliance globally, eliminates excess and obsolete spare parts inventories, promotes environmental, health and safety policies, ensures smooth coordination of production and maintenance schedules, and improves both, the responsiveness and accuracy of contracted maintenance.
This section provides information on the common prerequisites, profile options, and data setups required for executing the Oracle Enterprise Asset Management flows. Flow specific requirements are documented along with each flow in the subsequent sections.
The following are the prerequisites for executing the Oracle Enterprise Asset Management flows:
Inventory accounting period is open for the current date
GL periods are open for the current date
The EAM field is enabled in the Organization Parameters form
Parameters for Oracle eAM are defined in the eAM Parameters window
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| EAM: Maintenance Supervisor | Yes | Site |
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| User | User Name | mnt |
| User | password | welcome |
| Responsibility | Responsibility Name | Enterprise Asset Management Maintenance Super User, Vision Operations |
| Item Template | Item Template |
|
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | V1 – Vision Operations |
| Organization | Inventory Organization |
|
| Create Asset groups | Use Item Template | Asset Group |
| Create Asset groups | Use Item Template | (Select Transactable in INV tab. Assign to organization EM1 and M1) |
| Create Asset No | Use Asset Group | (A user defined value. In case, the user has not defined a value, the system automatically generates a number) |
| Create Activities with BOM & Routing | Item Template | Activity |
| Create Activities with BOM & Routing | Item Template | Purchased Item |
| Defining Departments and Resources | Department and Resource | (A user defined value) |
| Define WIP Accounting Class | WIP Accounting Class | (A user defined value) |
Oracle eAM supports multiple asset locations: organization area, internal inventory location and external physical location.
A user can move or transfer an asset to another organization without losing the integrity of its attributes, maintenance strategies or work history, using the Asset Move Workbench.
The Move Asset and its Child from Production Organization to Maintenance Organization from Asset Move Workbench flow demonstrates Oracle eAM’s capability to move an asset and its child from production organization to maintenance organization using the Asset Move Workbench.
This section provides information on prerequisites, profile options, and data setups required to execute the Move Asset and its Child from Production Organization to Maintenance Organization from Asset Move Workbench flow.
Asset_Move_Workbench_InTransit_W_Child_Prod_Maint
The following are the prerequisites for executing this flow:
The asset group is assigned to the production and maintenance organizations
A shipping network is defined between the two organizations
Not applicable.
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Inventory Organization |
|
| Subinventory | Subinventory | (A user defined value) |
This flow demonstrates Oracle eAM’s capability to move an asset without its child from the production organization to the maintenance organization using the Asset Move Workbench.
This section provides information on prerequisites, profile options, and data setups required to execute the Move Asset without Child from Maintenance Organization to Production Organization from Asset Move Workbench flow.
Asset_Move_Workbench_Direct_WO_Child_Maint_Prod
The following are the prerequisites for executing this flow:
The asset group is assigned to the production and maintenance organizations
A shipping network is defined between the two organizations
Not applicable.
Not applicable.
Not applicable.
The asset operations log tracks all user-selected maintenance events of a critical asset, which enables equipment operators to document problems identified during asset usage so that these can be addressed during the next scheduled maintenance.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Asset Operations Log for System Events flow.
Validate_Asset_Operations_Log_For_System_Events
None.
Not applicable.
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| eAM Parameters | Control Log Events | (Select events that you want to track) |
Oracle eAM enables organizations to set up assets in a hierarchical structure. The hierarchical structure makes it easier to find and group assets and roll up asset costs. For example, a company’s office building is defined as a top-level asset. Each individual floor of the building is defined as a child asset. This structure can be further defined by establishing a relationship between offices and floors.
This section provides information on prerequisites, profile options, and data setups required to execute the Asset Rebuild Genealogy flow.
Asset_Rebuild_Genealogy
None.
Not applicable.
Not applicable.
The following data must be set up:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| Create Rebuildable Item | Use Item Template | Rebuildable Item |
| Create Rebuild No | Rebuild No | (System defined value or a user defined value. If value is not defined, then the system automatically generates a rebuild number) |
| Rebuild No | Parent Asset | (associate parent asset number) |
To improve user ability to forecast maintenance costs, Oracle eAM’s budgeting and forecasting tool is used to generate cost forecasts based on preventive maintenance schedules or historical work order costs. Generated costs are grouped into financial periods, and can be aggregated by accounts or work orders. These costs can be exported in a standard file format (Excel, HTML, PDF) for further analysis and subsequently imported into user preferred budgeting tools. The budgeting and forecasting process increases efficiency of user budget analysis.
The Manage Budget Forecast for all Historical Work flow creates budget forecasts based on all historical work orders and verifies the projected budget.
This section provides information on prerequisites, profile options, and data setups required to execute the Manage Budget Forecast for all Historical Work flow.
Creation_Update_Budget_Forecast
The following is a prerequisite for executing this flow:
Historical work order is available
Not applicable.
Not applicable.
Not applicable.
This flow creates a construction estimate using a new or existing construction unit having an activity assigned to it. It further groups all activities using the Group by Single WO option.
This section provides information on prerequisites, profile options, and data setups required to execute the Create Construction Estimate and Group by Single Work Order flow.
Create_Update_BOM_Explosion_Groupby_Estimate_CU_CE
The following is a prerequisite for executing this flow:
A construction unit is defined and activities, operations, and resources are associated with it
Not applicable.
Not applicable.
Not applicable.
Work executed using a construction unit results in creation of new assets or adds value to existing assets. This feature enables you to collect costs on the work orders and post them for capitalization in the Fixed Asset (FA) module through mass update. If the eAM asset numbers are not associated with FA serial numbers until work order completion, then the asset numbers are generated in the FA module and used during capitalization.
The Work Order Capitalization process is used to capitalize costs associated with an asset.
This section provides information on prerequisites, profile options, and data setups required to execute the Depreciable Asset Creation through Capitalization of Construction Estimate Work Order flow.
Depreciable_AssetCreation_Capitalization_CU_CE
The following are the prerequisites for executing this flow:
FA book is created in the current period
The periods for Oracle Inventory, PO, Oracle General Ledger, and Oracle Payables are open
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| EAM: FA Book Type Code | (A user defined value) | Site |
| CSE: FA Book Type Code | (A user defined value) | Site |
Not applicable.
Not applicable.
Oracle eAM integrates with Oracle Projects to provide a complete, seamlessly integrated business solution for project maintenance. The project and task for maintenance work order details are specified, and transaction costs are collected in Oracle eAM and passed to Oracle Projects for subsequent project cost analysis and management.
The Construction Estimate and Project Integration flow demonstrates integration of Oracle Projects with construction estimate and work order created in this process.
This section provides information on prerequisites, profile options, and data setups required to execute the Construction Estimate and Project Integration flow.
CE_Project_Integration
The following are the prerequisites for executing this flow:
A valid project and project task are available
The Projects (PA) periods are open
Not applicable.
Not applicable.
Not applicable.
Employee scheduling enables searching for available employees by skill sets and competencies. The department resource availability and an employee’s current workload facilitate assignments and resource reshuffling, if needed.
This section provides information on prerequisites, profile options, and data setups required to execute the Crew Schedule flow.
Crew_Schedule
The following is a prerequisite for executing this flow:
An open work order with a resource or employee assigned to it
Not applicable.
Not applicable.
Not applicable.
A supplier reports work completion and any required collection data and meter readings using the iSupplier portal. Oracle eAM integrates with the Oracle iSupplier portal to provide the capability for web-based collaboration with suppliers or subcontractors and improve accuracy and timing of suppliers’ reporting.
This section provides information on prerequisites, profile options, and data setups required to execute the Oracle eAM Integration with Oracle iSupplier flow.
EAM_iSupplier_Integration
None.
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| PO: Enable Direct Delivery To Shop Floor | Yes | Site |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Create Work Order | Work Order | (Create WO with operation) |
Oracle eAM integrates with Oracle iProcurement to provide an intuitive, web-shopping interface to directly order items for maintenance work orders. Oracle iProcurement has a powerful search engine and multiple supplier self-guiding catalog capabilities for item selection.
This section provides information on prerequisites, profile options, and data setups required to execute the Oracle eAM Integration with Oracle iProcurement flow.
EAM_IProcurement_Integration
None.
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| PO: Enable Direct Delivery To Shop Floor | Yes | Site |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Create Work Order | Work Order | (Create WO with operation) |
Oracle eAM integrates with Oracle Service for logging and resolving maintenance service requests. This enables the maintenance planner or supervisor to view the service requests logged against the department’s asset, and helps them in work assignment.
This section provides information on prerequisites, profile options, and data setups required to execute the Oracle eAM Integration with Oracle Service flow.
EAM_Service_Integration
The following are the prerequisites for executing this flow:
Oracle Service is installed to utilize the service request functionality
Maintenance service request types are created
Service requests for assets and rebuildables are enabled
Not applicable.
Not applicable.
The following data must be set up:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| Create Work Order | Work Order | (Create WO with activity) |
Oracle eAM integrates with Oracle Time and Labor (OTL) where employees can enter the hours they have worked on each work order on a self-service timecard. Once the timecard is submitted, Oracle eAM charges the time to the work order resource and assigned employee.
This section provides information on prerequisites, profile options, and data setups required to execute the Oracle eAM Integration with Oracle Time and Labor flow.
EAM_OTL_Integration
The following are the prerequisites for executing this flow:
Employees are set up as Persons in Oracle Human Resource Management System
Preference values are defined and linked to the eligibility criteria
Note: Preferences are predefined, but these must be assigned to the user
Not applicable.
The following predefined data must be used:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| Retrieve Time card data from OTL to EAM | Organization | EAM Organization |
| Asset Serial No | (asset serial number) |
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Create Work Order | Work Order | (Create WO with activity) |
This flow creates on-hand stock through purchase order receipts and account purchase invoices. It verifies distributions in an encumbrance enabled, average costing organization.
This section provides information on prerequisites, profile options, and data setups required to execute the Encumbrance Accounting for Shop Floor Destination flow.
EAM_Encumberance_Shop_Floor
The following are the prerequisites for executing this flow:
Organization is an average costing-enabled organization
Sub-inventory is Asset Subinventory
Tax setup is disabled
Not applicable.
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization Parameters | Costing Method | Average |
| Purchase Order | Type | Standard Purchase Order |
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | EN1 |
| Master Items | Template | Purchased Item Template |
| Define Budget | Budget | ENC Budget |
| Page Name | Field Name | Field Value |
|---|---|---|
| Create Work Order | Work Order | (Create WO with activity) |
| Supplier | Supplier Name | Office Supplies, Inc (to create purchase order) |
| Define Budget | Site | New York |
The Maintenance User Workbench enables technicians to view their work, request material, charge time, and hand over the work and all other activities required to complete the work. .
This section provides information on prerequisites, profile options, and data setups required to execute the Mass Time Entry Using Maintenance User Workbench flow.
EAM_MSU_MUWB_OTL_ChargeTime_MassTimeEntry
The following are the prerequisites for executing this flow:
Employees are set up as Persons in Oracle Human Resources Management System
Profile Options An employee is assigned
Not applicable.
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Create Work Order | Work Order | (Create WO with activity) |
| Assign Employee to WO operations | (employee name) |
An Express Work Order provides users with a quick way to report work that has been completed without any planning, often referred as “after-the-fact” reporting. The Debrief Work Order feature enables users to report labor, charge time, issue stocked items and complete the work from a single page.
Oracle eAM integrates with Oracle Quality to define flexible and configurable data collection requirements. Data collection results can trigger powerful automated response and follow up actions. If the collected data results in a condition outside the acceptable limits defined in the collection plan, a work request or work order can be created.
Oracle eAM enables you to define failure codes and organize them into hierarchical groupings called Failure Sets. Failure Sets are associated with asset groups and inherited by all assets in the group.
This section provides information on prerequisites, profile options, and data setups required to execute the Create and Complete Express Work Order with Failure Data and QP wherein QP Results Trigger Creation of Work Request flow.
Express_WO_Create_Complete_FailureData_QP_Create_WorkRequest
The following is a prerequisite for executing this flow:
An active employee is defined in Oracle Human Resources Management System
Not applicable.
Not applicable.
Not applicable.
An Express Work Order is used to capture completed work. It can be accessed through the Maintenance Super User responsibility.
The Create and Complete Express WO with Resource Charging, Operation Completion and Quality Plan Results flow captures completed work and records the quality results.
This section provides information on prerequisites, profile options, and data setups required to execute the Create and Complete Express WO with Resource Charging, Operation Completion and Quality Plan Results flow.
Express_WO_Create_Complete_OP_COMP_Res_Charge_QP
The following is a prerequisite for executing this flow:
An active employee is defined in Oracle Human Resources Management System
Not applicable.
Not applicable.
Not applicable.
Failure data can be entered while completing the work order using the Maintenance User Workbench responsibility. This data is used in evaluating the performance of an asset.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Failure Data Entry from Maintenance User Workbench flow.
Validate_Failure_Entry_Maintenance_Workbench
None.
Not applicable.
Not applicable.
Not applicable.
The Failure Analysis feature shows an asset’s failure history and computed metrics, such as mean time between failure, mean time to repair and mean cost to repair, and failure frequency, based on the failure data captured during work order completion. Various aggregation levels enable you to evaluate the comparative reliability, maintainability, and performance between assets, asset groups, and asset categories.
This section provides information on prerequisites, profile options, and data setups required to execute the Failure Analysis flow.
Validate_Failure_Analysis_FreqCount_MTBF_MTTR_WO_Create_Update
None.
Not applicable.
Not applicable.
Not applicable.
The Mass Meter Readings page enables you to enter readings for multiple meters. Oracle eAM offers unique capabilities to define multiple meters for assets and enables multiple assets to share these meters. Readings for a meter are immediately updated to all associated assets. An associated target meter (current meter) readings are automatically updated when the source meter’s readings are updated.
Organizations can associate a source meter to an asset number or meter association. The source meter reading subsequently feeds corresponding meters that are associated with assets within the Meter Hierarchy, at a predefined factor.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Mass Meter Reading for Source Meter flow.
Validate_Mass_Readings_For_Source_Meters
None.
Not applicable
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Meter Definition | Create Source and target Meters | (A user defined value) |
| Meter Association | Associate Source and target Meters to Asset Number | (A user defined value) |
This flow demonstrates the target meter reading captured during work order completion. Target meter reading is automatically updated based on the source meter's readings. The source meter reading feeds corresponding target meters that are associated with assets within the Meter Hierarchy.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Target Meter Reading when Source Meter Reading is Captured at Work Order Completion flow.
Validate_MeterReadings_Source_Target_WO_Completion
None.
Not applicable.
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Meter Definition | Create Source and target Meters | (A user defined value) |
| Meter Association | Associate Source and target Meters to Asset Number | (A user defined value) |
This flow is used to suppress other activities with the current activity in the Preventive Maintenance Schedule Definition page. A user can enter suppression activities for a combination of an asset number or activity.
This section provides information on prerequisites, profile options, and data setups required to execute the Creation of Fixed Asset for a Normal Nonserial Control Item through PO Receipt flow.
Validate_Suppression_Logic_PM_WO
None.
Not applicable.
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Activity Association | Associate Activities to Asset Number | (A user defined value) |
| PM Schedule Definition | Create PM Schedule with Multiple Activities | (A user defined value) |
Oracle eAM tracks the performance of assets using meters, quality plans, and condition monitoring systems. When a failure is reported, each work order represents one single failure occurrence (event) for the asset specified on the work order. A user can then take necessary steps to eliminate the event.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Workflow for WO Completion with Mandatory Failure Set, Quality Plan, and Meter flow.
Validate_WO_Comp_FailureData_QualityPlan_MeterReadings_WF_1
Validate_WO_Comp_FailureData_QualityPlan_MeterReadings_WF_2
The following is a prerequisite for executing this flow:
Business events and event subscriptions are enabled for Oracle eAM workflow
Not applicable.
The following predefined data must be used:
| window Name | Field Name | Field Value |
|---|---|---|
| AME Transaction Type | EAM Work Order Completion | (A user defined rule) |
| AME Transaction Type | EAM Work Order Release Approval | (Item and organization used in the flow ) |
The following data must be set up:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| Parameters | Workflow for Work Orders | (Select the check box) |
| Collection Plan |
|
(A user defined value) |
| Meter Association | Associate Meter to Asset Number | (A user defined value) |
Rebuildable work orders are created as child work orders. A user can repair and reinstall a rebuildable item, or replace it by issuing a new rebuildable item from inventory. If the user chooses to repair and then reinstall the problematic rebuildable item, then the child rebuild work order is manually created for the old rebuildable item.
The Validate Work Order Completion for Rebuildable Serial Number flow enables a user to create a rebuild work order without issuing new material. The rebuildable item is replaced and is not included in a subinventory when the work order is completed. In this case, the asset number genealogy is not updated.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Work Order Completion for Rebuildable Serial Number flow.
Validate_WO_Completion_Serial_Rebuildable
None.
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| EDR: E-records and E-signatures | Yes | User |
The following predefined data must be used:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| AME Transaction Type | EAM Work Order Completion | (A user defined rule) |
| AME Transaction Type | EAM Work Order Release Approval | (A user defined rule) |
Not applicable.
A user may require electronic signatures and electronic records during work order completion. These are provided using the Oracle Electronic Records and Electronic Signatures (ERES) framework. Electronic signatures require user identification and password during the transaction. Electronic records provide a permanent snapshot of the transaction data that the user is verifying.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate E-record with Oracle eAM Search Options flow.
Validate_Erecord_With_EAM_Search_Options
The following is a prerequisite for executing this flow:
Transaction event oracle.apps.eam.wo.comp.ss is enabled
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| EDR: E-records and E-signatures | Yes | Site |
The following predefined data must be used:
| Page Name | Field Name | Field Value |
|---|---|---|
| AME Transaction Type | EAM Work Order Completion - SSWA | A user defined rule) |
The following data must be set up:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| Parameters | Workflow for Work Orders | (Select the check box) |
Person type resources are employees grouped together based on their capabilities. After defining the resource type employee details that are associated to a resource can be attached. When the work order is created, these employees are assigned based on the department or resource mapping, after which the assigned resource is charged.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Employee Assignment in Work Order Operations flow.
Validate_Assignment_Of_EMP
The following is a prerequisite for executing this flow:
An active employee is defined in Oracle Human Resources Management System
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| BOM: Hour UOM | UOM | Site |
Not applicable
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| People | People | (A user defined value using Person type employee) |
This flow demonstrates the maintenance process flow of capital assets from creation of work order, material issue, resource charging, work order completion and closure to work order capitalization. A user can capitalize part or all of the costs incurred, while maintaining a capital asset. The capitalized cost gets added to the asset's book value within Oracle Fixed Assets.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Asset Work Order Flow from Creation to Capitalization flow.
Create_Asset_WO_ResCharge_MatlIssue_Estimate_EmpAssign_OPComp_WOComp_Close_Captilize
The following is a prerequisite for executing this flow:
Item cost is defined for the materials used in the work order
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| EAM: FA Book Type Code | (A user defined value) | Site |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Resources | Employee Assignment | (A user defined value) |
This flow demonstrates the maintenance process flow for a rebuildable item from creation of work order, material issue, resource charging, work order completion and closure to finally work order capitalization. A user can capitalize part or all of the costs incurred, while maintaining a rebuildable item. The capitalized cost gets added to the asset's book value within Oracle Fixed Assets.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Rebuildable Work Order Flow from Creation to Capitalization flow.
Create_Rebuildable_WO_ResCharge_MatlIssue_Estimate_EmpAssign_OPComp_WOComp_Close_Captilize
The following is a prerequisite for executing this flow:
Item cost is defined for the materials used in the work order
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| EAM: FA Book Type Code | (A user defined value) | Site |
Not applicable.
The following data must be set up:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| Resources | Employee Assignment | (A user defined value) |
An Enterprise Asset Management work order may progress through several statuses through its life cycle. The work orders may start with a Draft status, and then move to Released, Complete, and finally to Closed status. These statuses may vary depending on the type of work order that is created. A user defined work order status provides flexibility in tracking and managing work orders.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Work Order Status Change while Using User Defined Statuses flow.
Validate_WO_Status_Change_UserDefined
None.
Not applicable.
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| WO Statuses | WO Status | (A user defined value) |
| AME Transaction Type | EAM Work Order Release Approval | (A user defined rule) |
This flow enables a user to create work permits mandated by regulatory agencies to be used by operations, maintenance and safety personnel during repair of some assets. A user can capture additional information by attaching documents, a URL, or include short text as attachments to the work permit.
The flow demonstrates the workflow functionality for a work permit wherein the workflow notification is approved. This changes the work permit status to Released from Release-pending.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Approve Workflow Functionality for Work Permit with Attachments flow.
Create_Complete_WorkPermit_With_Attachments_WorkFlow_With_Approve
The following is a prerequisite for executing this flow:
Validate Approve workflow is enabled for the work order
Not applicable.
The following predefined data must be used:
| Window Name | Field Name | Fields Value |
|---|---|---|
| AME Transaction Type | EAM Permit Release Approval | (A user defined rule) |
Not applicable.
This flow enables a user to create work permits mandated by regulatory agencies to be used by operations, maintenance and safety personnel during repair of some assets.
The flow demonstrates the workflow functionality for a work permit wherein the workflow notification is rejected. This changes the work permit status to Cancelled from Release-pending.
This section provides information on prerequisites, profile options, and data setups required to execute the Create Work Permit and Validate Reject Workflow Functionality for Work Permit flow.
Create_WorkPermit_WorkFlow_Reject
The following is a prerequisite for executing this flow:
The Create Work Permit and Validate Reject workflow is enabled for the work order
Not applicable.
The following predefined data must be used:
| Page Name | Field Name | Field Value |
|---|---|---|
| AME Transaction Type | EAM Permit Release Approval | (A user defined rule) |
| Create Assets Interface Inventory Transaction to Oracle Assets | Item and Inventory Organization | (Item and organization used in the flow ) |
| FA Book | FA Book | (A valid book) |
Not applicable.
This flow enables creation of work order and associate a work permits by creating a new permit from Work Order page. An existing work permit can also be associated to the work order and any safety additional information for the Work Order – Permit association is captured using descriptive flexfields.
This section provides information on prerequisites, profile options, and data setups required to execute the Create and Update Work Order with New and Existing Work Permit and Capture Safety Association Descriptive Flexfield flow.
Create_Update_WO_With_New_Existing_WP_SafetyAssociation_DFF
None.
Not applicable.
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Descriptive Flex field Segments | Safety Association | (A user defined rule) |
The following data must be set up:
| Page Name | Field Name | Field Value |
|---|---|---|
| Safety | Create Permits | (A user defined rule) |
This flow enables users to create work permits mandated by regulatory agencies to be followed by operations, maintenance and safety personnel during maintenance of assets. Work permits are created and are associated to existing work order and any additional information on the permit is captured using descriptive flexfields
Multiple work orders can be associated with permits using the Permit page.
This section provides information on prerequisites, profile options, and data setups required to execute the Create and Update Work Permit with Work Order and Capture Descriptive Flexfield flow.
Create_Update_WP_With_WO_Association_WorkPermit_DFF
None.
Not applicable.
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Descriptive Flex field Segments | Safety Association | (A user defined rule) |
The following data must be set up:
| Page Name | Field Name | Field Value |
|---|---|---|
| Work Orders | Create Work Order | (A user defined rule) |
This flow enables creation of work permits mandated by regulatory agencies to be followed by operations, maintenance, and safety personnel during maintenance of assets, through the Maintenance User Workbench.
This section provides information on prerequisites, profile options, and data setups required to execute the Create Permit Using Maintenance User Workbench Responsibility flow.
Create_Permit_Maintenance_User_WorkBench
None.
Not applicable.
Not applicable.
Not applicable.
This flow creates work orders and associates existing work permits with the work order. Work permits are required before assets can be repaired.
This section provides information on prerequisites, profile options, and data setups required to execute the Create Work Order and Associate Existing Work Permit with the Work Order flow.
Create_WO_With_Existing_WorkPermit
None.
Not applicable.
Not applicable.
Not applicable.
This flow automatically generates work request and work orders based on quality plans associated with an asset. Based on the actions and transactions defined in the Quality Collection Plan, the system triggers a proposed action and prompts the user to take immediate action or follow up.
This section provides information on prerequisites, profile options, and data setups required to execute the Asset Checkin and Checkout Transaction with Quality Plan Enabled flow.
Create_WO_WR_Through_QualityPlan_Trigger_Asset_CheckIn_CheckOut
None.
Not applicable.
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Collection Plan | Define Actions, Transactions | (A user defined rule) |
This flow demonstrates the security access control at the Responsibility level as per the profile EAM: Maintenance Work Request. When this profile is set as View and Update All Work Requests, a user with the Maintenance Super User Responsibility has access to view and update work requests created by all users.
This section provides information on prerequisites, profile options, and data setups required to execute the Validate Options for the Profile EAM: Maintenance Work Request Options flow.
Validate_View_Add_and_Update_delete_WR_Atta_with_Profile_Option
None.
The following profile option must be set:
| Profile Option Name | Profile Option Value | Level |
|---|---|---|
| EAM: Maintenance Work Request Options | View and Update All Work Requests | Responsibility |
Not applicable.
The following data must be set up:
| Concurrent Request Name | Parameter Name | Parameter Value |
|---|---|---|
| Collection Plan | Define Actions, Transactions | (A user defined rule) |