How You Define Quality Inspection Plans

An inspection plan contains inspection elements that represent the specific data that you want to collect and report on for a maintenance work order. It also contains information about when and how often you collect that data. For a work order, ah-hoc inspection plans can be defined based on an asset's item, operation code, operation sequence, or both along with the dispatch status of the work order. Inspections will then be defined mandatory or optional.

Note:

To define and collect data for a quality inspection plan, you must have an Oracle Fusion Cloud Product Management subscription.

Define Inspection Characteristics

Use inspection characteristics to specify the range of acceptable values or specification limits for items and not items.

You use inspection characteristics to:

• Create inspection plans.

• Conduct ad-hoc inspections, where you can directly add the characteristics to result collections.

• Collect data

During inspections, you evaluate assets against inspection characteristics. The samples or serials that are within the conformance limits are accepted and the rest may be rejected and could either be scrapped or require additional repair.

You can define item-based and inspection characteristics and inspection characteristics not based on an item:

• Item-Based Inspection Characteristics: you can link item-based inspection characteristics with attribute values in an item class. This enables you to verify if an item meets the required product specifications. The item-based inspection characteristics generally have a range of acceptable values or specification limits, as well as target or optimal values.

  These are typically used for manufacturing but may be used for maintenance.

• Inspection Characteristics Not Based on Items: you can define inspection characteristics that aren't mapped to item attribute values. These inspection characteristics (not based on items) can be of these types: Number, Character, or Date. You must specify a target value for all of the types, and where applicable, a range or list of valid values as well as a unit of measure.

Note:

If an inspection characteristic not based on an item is of the Character type, you can choose not to specify a value set. This enables you to enter free-form text for that characteristic during an inspection. Any result entered for such a characteristic added directly to an inspection or as part of an inspection plan is accepted without an evaluation against specifications and is recorded for data collection purposes.

Create an Inspection Plan

After defining the inspection characteristics, you can create an inspection plan to capture them. New plans are created from the Overview landing page of the Quality Management work area. Click the + icon and select Inspection Plan to create a new plan.

Here are some suggested setups when you create a new plan:

• The plan name should be descriptive, as users search for and select the plan when entering the inspection results.

• The plan type must be Process Asset to be used for collection in the My Maintenance Work page. Work In Progress (WIP) plans are not supported for reporting in execution.

• The organization is generally a maintenance organization where maintenance work orders are created for an asset. These work orders can be generated manually or through a preventative maintenance program. You must have data access to each organization in which a plan is going to be defined.

• Set the Details attribute as Item and the value of attribute should be an Asset Item. This means that the inspection plan isn't set up against any specific asset, but an item. This is a required setup for the plan.

• Inspection Plan Optional check box is used to set the inspection as mandatory or optional during work order completion. If the check box is selected, then the inspection is optional during operation completion. If the check box is deselected, then the inspection is mandatory during work order completion.

• Characteristics should then be added to the plan. These are the quality attributes that you collect in the plan for the work order. Each characteristic is then ordered by a sequence number.

• Inspection criteria can be configured once characteristics have been saved to the plan. The criteria should be either set for Operation Sequence or Operation Code (recommended). This will help provide a match, along with item, for any work order created for a matching asset. The dispatch status should always be Ready.

• Finally, the inspection plan status must be set to Approved.

Note: Inspection plans applicable to a specific operation, whether mandatory or optional, are only validated for reporting during work order completion. Currently, individual operation completion isn't contingent on mandatory inspection plan reporting.

Enter The Results of an Inspection Plan

After a plan is defined and set to the approved status, any new work orders created for the matching asset item, operation sequence, or operation code enables the inspection plan for the work order. They can be viewed by a technician in the Report Work page or each work order and accessed from the My Maintenance Work page. Additional details are covered in the Using Maintenance guide.

Trigger Business Events

To create a new work order based off the results of an inspection plan, set up an inspection plan action rule that raises an inspection business event. Oracle Fusion Cloud Integration is the recommended way to listen to the business event and subscribe with some custom logic to call the Maintenance Work Order REST API and create a new maintenance work order. It's important to note that this suggested approach doesn't involve Application Composer, which isn't supported for the Quality Inspection objects.