You create collection plans to identify the data that you want to collect, and what actions you want to take based on the quality results that you collect. You can use collection plans to model your test or inspection plans, and you can create an unlimited number of plans to support your enterprise-wide quality data collection and analysis needs. Collection plans are invoked manually for direct results entry, or automatically as you complete a work order.

To collect quality data, you must set up a data collection structure called a collection plan. Collection plans are composed of collection elements, their values and specifications, and any actions that you want to initiate in response to quality results. There are some considerations that you must make before you set up collection plans. You first must create collection element types, then the individual collection elements that comprise the plan.

You can attach illustrative or explanatory files to collection plans, in the form of text, images, word processing documents, spreadsheets, or video. Attachments are used to document instructions and corrective action procedures. They are viewed by operations personnel during quality data collection. See: Attachments for Collection Plans, Specifications, and Result Lines and Viewing Attachments Associated with Quality Results.

   To review a collection plan:

1. Navigate to the Collection Plans window.

   Note: To assist you as you create collection plans, you can select the Summary/Detail option from the View Menu, and run a query to view existing collection plans in summary format. See: Combination Blocks.

2. Select a valid Collection Plan.

   To create a new collection plan, See: Creating Collection Plans.

3. Choose Transactions.

   You can create collection plans that are specifically used to collect quality data during transactions performed in other applications (See: Collection Plans for Transactions, Oracle Quality User's Guide).

4. Select EAM Work Order Completion or Asset Query from the Transaction Description list of values.

   • EAM Asset Query: Enables quality results collection for an asset, independent from any transaction on the asset.

   • EAM Operation Completions: Enables quality results collection for a work order's operation pertaining to operation completion or during operation completion (See: Operation Completion).

   • EAM Work Order Completions: Enables quality results collection for a work order pertaining to work order completion or during work order completion (See: Work Order Completion).

   • EAM Asset Check In Transaction: Enables you to record quality information, describing the condition of the asset, during a Check In procedure (See: Asset Tracking).

   • EAM Asset Check Out Transaction: Enables you to record quality information, describing the condition of the asset, during a Check Out procedure (See: Asset Tracking.

5. Optionally indicate whether this collection plan requires the entry of quality results at work order completion. If you select the Mandatory check box, you must save at least one quality data record before saving the work order completion transaction.

   Note: eAM supports Quality collection during operation completion transactions, as well as Standalone Asset Query. Valid Transaction Description values are EAM Operation Completions and EAM Asset Query, respectively.

6. Optionally select the Background check box.

   If you select this check box, you can collect quality results for context reference elements (See: Reference Information Collection Element Type).

   Note: The following Collection Elements are included with Oracle Enterprise Asset Management; you do not need to define them: Asset Group, Asset Number, Activity, Maintenance Work Order, Maintenance Operation Sequence.

   Without invoking the Enter Quality Results window, background data collection is initiated when you save the work order completion transaction.

   The system then finds, selects, and initiates the appropriate collection plan or plans.

   If collection triggers are defined for background data collection, data collection is initiated if all collection trigger conditions are satisfied (you define triggers for transactional data collection in the Collection Transactions window).

   Several collection plans can collect data in the background during the same transaction.

   When this is the case, the results for context elements on all of these collection plans are automatically saved when the parent transaction is saved.

7. Select the Enabled check box.

8. Optionally select a Trigger Name.

   Valid trigger values are Activity, Asset Group, Asset Number, Asset Serial Number, and Maintenance Work Order. Triggers are restrictions that you define for this collection plan. In the above example, work orders for the JP1 asset require the entry of quality results for the collection plan.

   Note: If a trigger is not defined, then all work orders will require quality collection results; the collection plan is applicable to all assets.

9. If you selected a Trigger Name, select a Condition.

10. Select a From value.

    For example, if you selected Asset Group as the Trigger Name, Asset Groups are available. Optionally you can enter a To value to create a range condition. For example, if the trigger is work order, you might enter a range of work order numbers.

11. Save your work.