The work order is the foundation for all maintenance organizations. Work orders define the resources and items that are needed to conduct work. They can automatically generate through the use of Preventive Maintenance Schedules, the issue of an inventoried rebuildable, breach of quality results, or manually generated as a routine work order. These work orders are then reviewed and shared with Operations to produce an estimated schedule.
Oracle Enterprise Asset Management integrates with Oracle Quality. Use Quality collection plans to predefine required feedback information that must be entered into Oracle Enterprise Asset Management, upon a work order's completion. For example, data to collect may include inspection points for asset number and downtime variables. If a variance is recorded to the quality plan, a work request or work order is created. You can define quality collection plans directly on the work order, or define them as attributes of an activity to ultimately default into future work orders that are generated for specific asset number and activity combinations.
For each work order, the estimated costs aggregate, from the associated BOM and resources, to develop a costing profile for the current work order. You can use Costing Profiles for future Budgeting and Forecasting.
For each work order, the actual costs aggregate during the work order's lifecycle. These costs roll up, based on the hierarchy of the current work order's associated asset number. View these actual costs by period at a transaction level or at a summary level. Costs can roll up, based on the hierarchy of work orders. You can view the costs (both actual and estimates) by period, at a transaction or summary level.
This chapter is divided into the following sections: