This chapter discusses:
JD Edwards EnterpriseOne Condition-Based Maintenance overview.
JD Edwards EnterpriseOne Condition-Based Maintenance integrations.
JD Edwards EnterpriseOne Condition-Based Maintenance implementation.
Unplanned downtime can create a huge dent in a company’s productivity and profitability. That is why it is so important to keep equipment in top working condition. Traditional maintenance programs are no longer sufficient; companies must be able to find and fix problems before they cause equipment breakdowns.
JD Edwards EnterpriseOne Condition-Based Maintenance (CBM) from Oracle enables you to make maintenance decisions based on actual condition, rather than time or usage interval. You can identify equipment problems early, when they are less costly to correct, and perform maintenance only when needed, thereby increasing asset utilization, extending equipment life, and reducing maintenance costs. JD Edwards EnterpriseOne CBM enables you to quickly respond to and resolve equipment issues instead of waiting for the equipment to fail. JD Edwards EnterpriseOne CBM:
Uses alerts generated from realtime equipment monitoring devices that assess equipment conditions against predefined, normal operation parameters.
Provides realtime alerts (using pager, email, or other messaging systems) when equipment is operating outside of normal bounds so appropriate maintenance action can be taken.
Automatically initiates appropriate maintenance action, including investigation, creation of a work order, and maintenance schedule updates.
The JD Edwards EnterpriseOne CBM system integrates with the JD Edwards EnterpriseOne Capital Asset Management (CAM) system from Oracle using these modules:
JD Edwards EnterpriseOne Work Order module.
JD Edwards EnterpriseOne Preventive Maintenance module.
The JD Edwards EnterpriseOne CBM system works with other JD Edwards EnterpriseOne systems to ensure that all information is fully integrated. We discuss integration considerations in the implementation chapters in this implementation guide. Supplemental information about third-party application integrations is located on the Customer Connection website.
JD Edwards EnterpriseOne CAM
The JD Edwards EnterpriseOne CAM system enables you to maintain and service equipment using the right mix of reactive, preventive, and predictive maintenance. This enables you to provide the required equipment reliability at the lowest possible cost.
This section provides an overview of the steps that are required to implement JD Edwards EnterpriseOne CBM.
In the planning phase of the implementation, take advantage of all JD Edwards EnterpriseOne sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface in About This Documentation with information about where to find the most current version of each.
When determining which electronic software updates (ESUs) for JD Edwards EnterpriseOne CBM, use the EnterpriseOne and World Change Assistant. EnterpriseOne and World Change Assistant, a Java-based tool, reduces the time required to search and download ESUs by 75 percent or more and enables you to install multiple ESUs at one time.
See JD Edwards EnterpriseOne Tools 8.98 Software Update Guide
This table lists the suggested global implementation steps for JD Edwards EnterpriseOne CBM:
Step |
Reference |
1. Set up companies, fiscal date patterns, and business units. |
|
2. Set up accounts, and the chart of accounts. |
See Setting Up Bank Accounts, Creating the Chart of Accounts. |
3. Enter address book records. |
This table lists the suggested application-specific implementation steps for JD Edwards EnterpriseOne CBM:
Step |
Reference |
1. Set up equipment master records. |
See Setting Up Equipment. |
2. Set up preventive maintenance schedules. |
|
3. Set up work orders. |
|
4. Set up sequences for notification and investigation messages. |
See Setting Up Sequences for Notification and Investigation Messages. |
5. Set up rules for notification and investigation messages. |
See Setting Up Rules for Notification and Investigation Messages. |
6. Set up sequences for alert action rules. |
|
7. Set up alert action rules. |