How You Search for Work Requirements
Using the existing page, in the edit mode of a maintenance program, you can manage the work requirements on the Work Requirements tab. Here you can create, view, edit, and delete the work requirements associated with the maintenance program.
The page includes a Query-by-example (QBE) search option. When you click the QBE icon, it reveals a search bar where you can search the list of requirements by certain columns. Optionally, you can also click on certain columns to sort the results rows ascending or descending by value.
| Capabilities | Description |
|---|---|
| Search | On the tab, search for your work requirements using Oracle's smart search and filters. You can quickly and easily perform full-text searches for assets across attributes using this enhanced search function. View the search results in a sortable table based on the matching records. The page includes a keyword search, context, and results filter chips. |
| Search Results |
|
| Keyword Search Filters |
You can use the keyword search to filter the results by:
|
| Results Chips |
Use the results chips to filter the results by:
|
| Saved Searches | You can optionally use saved searches to:
User default searches override administrator default searches. The administrator must create the saved search index prior to creating new saved searches. Additional details are covered in the Setup Maintenance section of the Implementing Manufacturing and Supply Chain Materials Management guide. |
| Manage Columns | You can manage the columns in the user session. |
| Export | You can export the results rows. |
| Create Work Requirement | Action that will navigate you to the New Work Requirement
page. Click Cancel to return to the search results. |
| Release to Planning | Action that updates the status of a requirement from Ready to Forecast to Active. |
| Revert to Ready to Forecast | Action that updates the status of a requirement from Active to Ready to Forecast. |
| Generate Requirement Forecast | Action that allows you to generate the forecast for only the
selected work requirement, and not the entire program. This action
is only available if the status is Ready to Forecast or Active and
the asset maintenance parameter option, Allow Suppress and Merge
across Work Requirements is set to No. Note: It's recommended to set the parameter option to No, thereby
disabling this capability unless you have an established
business requirement and fully understand its capability and
limitations. Merge and suppress options, that support multiple
work definitions across intervals in a cycle, are best modeled
and forecasted within a single work requirement. |
| Key Details | Description |
| Name | Click the hyperlink to go to the Work Requirement details page. |
| Reference | Optional reference for a work requirement. This is helpful to filter rows within a program. |
| Type | Type of the work requirement. The valid values are: Asset, Item, Mixed Asset, or Asset Route. |
| Type Reference |
Further describes the type of work requirement:
|
| Affected Assets |
Count of the affected assets in a work requirement.
Note: This number will not calculate for an item-based work requirement, as the number of assets is dynamically calculated during forecasting. |
| Status | Status of the work requirement. |
| Program | Name of the maintenance program. |
| Organization | Name of the maintenance program’s organization. |
| Start Date | Start date of a work requirement. |
| End Date | Optional End date of a work requirement. When reached, it will stop forecasting. |
| Forecast Date | Date the forecast was last generated for the requirement. |
| Work Order | Indicates if work orders have been created or not for the requirement. |
Work Requirement Status
Using the existing page, work requirements use the status values of Draft and Active.
Using the Redwood page, you will see a status of Ready to Forecast, along with the existing status values of Draft and Active. This new status is available using the Redwood page, REST API or File-based upload after opt-in.
- Draft: the same in both pages:
- This status is used to represent a Work Requirement that has a header record, but not a full definition of forecast method, assets, and work definitions.
- A forecast can’t be generated while in Draft status, as there is not enough required information.
- Ready to Forecast: Only using the Redwood page after
opt-in:
- This status is used to first indicate that a work requirement has the required information of a definition of forecast method, item or asset(s), and work definition(s) and can now be forecasted. Therefore, the requirement will move from Draft to Ready to Forecast status automatically.
- The requirement can be optionally forecasted, generating a preview version of the forecast dates that is only viewable here in the Forecast tab of the page. It will not be viewable in the Manage Forecasts page, nor are the dates eligible for creating work orders.
- If the requirement is edited, it could return to Draft status if any of the required information is deleted.
- Active: The same in both pages:
- In the exiting page, a requirement will move from Draft to Active status automatically when it has the required information to generate a forecast.
- However, using the Redwood page, you must promote it when ready by clicking an action button Release to Planning. At any point in the future, you can also return it to Ready to Forecast status for editing and forecast validation.
- Once in an Active status, generating a forecast will produce due dates that are viewable in the Manage Forecasts page and eligible for creating work orders.