How You Create a Work Requirement in Redwood

Using the Redwood page, the work requirement header and its details are managed in different pages. Clicking the Create Requirement action from the Work Requirements tab will render the New Work Requirement page. On this page you will define the required fields for the requirement’s header, select its parent program, type, and forecast method(s). Once successfully submitted for creation, you will navigate to the Work Requirement details page.

On the Work Requirement details page, you will further define the forecast method, work definitions, assets, and requirement options on each corresponding tab. This new user experience replaces the single page design of the existing page to improve usability. It is expected that the status of a requirement will remain in Draft until you define the method, work definition and assets. It will then move to a status of Ready to Forecast, allowing you to optionally generate a forecast preview. Finally, you will promote a requirement to an Active status.

Comparison of the Existing and Redwood Pages

User Step	Existing Page	Redwood Page
View and Manage Work Requirements for a Program	Navigate to the Manage Maintenance Programs page: Search for the Program. Click the Program link to edit it. Navigate to the Program Details page. Click the Work Requirements tab. Search for the Requirement. Click the requirement link to navigate to the create/edit page.	Navigate to the Maintenance Programs page, you will start on the Work Requirements tab. Search for the Requirement. Click the requirement link to navigate to the Edit Work Requirement details page.
Create a Work Requirement for a Program	Navigate to the Manage Maintenance Programs page: Search for the Program. Click the Program link to edit it. Navigate to the Program Details page. Click the Work Requirements tab. Click the Add Requirement. Navigate to a Create/Edit page, define the minimum details, and click Save. The requirement will be saved in Draft status. You can optionally continue to define details on this page or return to the work Requirement list.	Navigate to the Maintenance Programs page, you will start on the Work Requirements tab. Click the Create Requirements button. Navigate to a Create/Edit page, define the minimum details, and click Save. The requirement will be saved in Draft status, and you will navigate to the Edit Details page. You can optionally continue to define details on this page or return to the Work Requirement search page.
Define Work Requirement header details	On the Create or Edit Work Requirement page, define the key details for the requirement: Name, Reference, and Start date. Select the Type (asset, item, or asset route). Based on the selected type, select the applicable Asset, Item or Asset Route Hierarchy Click Save The requirement is saved in the Draft status.	On the Create or Edit Work Requirement header page, define the key details for the requirement: Name, Reference, and Start date. Define the Program Details by select the Program by Organization. Define the Modeling Details by selecting the requirement Type (asset, item, mixed asset, or asset route) Based on the selected type, select the Asset, Item or Asset Route Hierarchy (Mixed assets are defined later in the process) Select the Forecast Method(s) (Calendar, Day, Meter and/or Condition Event) Click Save The requirement is saved in the Draft status.
Define Work Requirement Forecast Method(s)	On the Create/Edit Work Requirement page, in the Generate a Forecast region: Select the Forecast Method(s) (Calendar, Day, Meter and/or Condition Event) Then, for each forecast method, define its details in the Based on a Recurring Pattern by Date region: Day: Set the number of days and next due option. Calendar: Select the calendar pattern. Meter: Select the meter, due at value and next due option. Condition Event: Select one or more condition events.	On the Edit Work Requirement details page, start on the Pattern tab. Keep in mind that you have already selected the Forecast Method(s) when creating the requirement. For each selected forecast method, define its details: Day – set the number of days and next due option. Calendar – select the calendar pattern. Meter – select the meter, due at value and next due option. Condition Event – select one or more condition events.
Define Cycle Option and Work Definitions	On the Create or Edit Work Requirement page, in the Generate a Forecast region: Define if the forecast will use a cycle of intervals or not and select the forecast methods(s). Verify and update merge and suppress options. Then, define the work definition(s) in the To Perform This Work region: Add one or more work definitions. If cycle-based, set the due at interval and repeats flag option. Verify the merge and suppress across intervals, if defined.	Click on the Work Definition tab: Define if the forecast will use a cycle of intervals or not and select the forecast methods(s). Verify and update merge and suppress options. Then, define the work definition(s): Add one or more work definitions. If cycle-based, set the due at interval and repeats flag. Click the Preview Work Sequence action if a cycle of intervals is defined: Verify the merge and suppress across intervals for 2 cycles.
Define Asset and Initialization Options	Confirm the assets and initialization options by clicking the Affected Assets icon, navigating you to the Affected Assets page: For each row, confirm the included assets. Include or exclude Assets for item-based requirements. Review each asset’s initialization options: Optionally define historical last accomplished date/interval and future start date Update the work order creation method, automatic or manually. Optionally Generate a Forecast: Generate for a single asset. Generate for all included assets in the Work Requirement.	Click on the Asset tab: For each row, confirm the included assets. Include or exclude Assets for item-based requirements. Review each asset’s initialization options: Optionally define historical last accomplished date/interval and future start date Update the work order creation method, automatic or manually. Update its forecast status to remove or promote it to planning. Optionally Generate a Forecast: Generate for a single asset. Generate for all included assets in the Work Requirement.
Define Work Requirement Forecast and Work Order details	On the Create or Edit Work Requirement page, in the Generate a Forecast region: Optionally set forecast options Optionally set work order creation options	Click on the Options tab: Optionally set forecast options Optionally set work order creation options
Generate and verify a Forecast preview	Click the Calendar or Gantt chart tabs. Here, you can review the forecast due dates for the requirement and assets, but only for an active forecast. You can optionally update the modeling criteria, re-forecast and view the results.	Click the Forecast tab: Here, you can review the forecast lines by work definition for the requirement and assets, including both preview and active forecast dates. You can optionally update the modeling criteria, re-forecast and view the results.
Release a requirement to planning	Not available in this page. An Active status requirement is already in planning.	Once you have verified your modeling the Forecast preview, you can optionally release the requirement to planning status. This will update the requirement status from Ready to Forecast to Active.

Work Requirement Header

Use the New Work Requirement page to define the key details to create a new Work Requirement. Once submitted for creation, you will navigate to the requirement details page.

Fields You Select When You Create Work Requirements

Field	Description
Name	Name of the work requirement. The name must be unique across all maintenance programs, regardless of maintenance organization.
Requirement Reference	Optional reference for a work requirement. For example, an OEM repair manual reference or a subscription line unique identifier.
Start Date	Date on which the work requirement becomes active. Forecasted due dates begin on this date and into the future. This value is required. The Start Date is used to determine when a work requirement is considered by the forecast program and will begin calculating from this date into the future. This date can be in the past, present or in the future and will control the first due date in the forecast, as well as its sequence of due dates into the future within the forecast horizon number of days window. Note: Setting the Start Date to the current date will begin forecasting on the next day in most cases. If the Start Date set to a value in the past, then the forecast will be calculated from that point in time based on the forecast method, generating the sequence of forecasted due dates. Care should be taken when defining a past date, as the forecast may include one or more overdue due dates, based on the interval period. Therefore, it is generally not recommended to set a past date that exceeds the next due interval, but to set the current date as the start date. The Start Date is optionally superseded in the forecast calculations by defining a Historical Start Date, Interval if applicable, and a Forecast Start Date in the Affected Assets page. This allows the forecast program to more accurately calculate the first due date based off asset’s maintenance history. For an item-based work requirement, it is recommended that you set a Forecast Start Date at the asset level, if the requirement’s start date is far into the past, as mentioned above. Else, the system will back calculate multiple due intervals and may produce overdue dates. If set to a date in the future, then the work requirement will not be considered by the forecast program until this date. As of this date, or the next time in the future in which the forecast is regenerated, the due dates will be created within the horizon time frame into the future. During setup and confirmation of your work requirement model, you can adjust the start date and regenerate the forecast. This will provide the ability to confirm the forecast method and most importantly confirm the first due date in the future in which you expect a work order to be created. When the first work order is created based off these dates, if you adjust the start date to another date in the past will not have any impact on your future forecast. The forecast will always stay on its original sequence based of the original Start Date. If you adjust the start date to a future value, then the work requirement will no longer be considered by the forecast. If you are using a cycle of intervals, then intervals that are due from the present to the future will be skipped when the forecast is regenerated. Therefore, it is generally recommended to End Date a requirement and create a new requirement to start again in the future. Note When using a calendar pattern and cycle of intervals, if the Start Date falls on the first iteration in the future of the calendar pattern, then it's considered as interval 1 of the cycle. However, for a day or meter-based forecast, interval 1 is calculated as due from the start date.
End Date	Date on which the work requirement becomes inactive. The work requirement will no longer be considered by the forecast program as of this date. The date is optional and should only be set to end date a work requirement.
Organization	Maintenance organization of the program in which you will create the requirement. Selecting a value is required and will filter the list of programs. Its value is set to your default organization but can be updated.
Program	Maintenance program name, required. The list is filtered by the selected Organization.
Program Code	Maintenance program code that is defaulted as read-only from the selected Program.
Program Description	Maintenance program description that is defaulted as read-only from the selected Program.
Allow assets from other organizations	Maintenance program option that is defaulted as read-only from the selected Program.
Type	Type of the work requirement, required. The valid values are Asset, Item, Mixed Asset or Asset Route.
Asset	If the selected work requirement type is Asset, you will select the Asset that will be forecasted by the work requirement. The Asset list of values will be governed by the maintenance program’s organization and if it is enabled for assets across organizations or not. Note The forecast and resulting preventative maintenance work orders is always for the selected asset and doesn’t apply to any parent or child assets in a physical hierarchy
Asset Description	Description of the asset that is defaulted as read-only from the selected Asset.
Asset Serial Number	Serial number of the asset that is defaulted as read-only from the selected Asset.
Operating Organization	Operating organization of the asset that is defaulted as read-only from the selected Asset.
Asset Route Name	If the selected work requirement type is Asset Route, this is the name of Asset Logical Hierarchy that is enabled as an Asset Route and is active. Note: The forecast and resulting preventative maintenance work orders is always for the selected asset and doesn’t apply to any parent or child assets in a physical hierarchy.
Asset Route Description	Description of the asset route that is defaulted as read-only from the selected Asset Route.
Asset	Asset Route Asset that is defaulted as read-only from the selected Asset Route. This is the Asset that will be forecasted by the work requirement.
Asset Description	Description of the asset that is defaulted as read-only from the selected Asset Route.
Asset Serial Number	Serial number of the asset that is defaulted as read-only from the selected Asset Route.
Operating Organization	Operating organization of the asset that is defaulted as read-only from the selected Asset Route.
Item Number	If the selected work requirement type is Item, this is the name of item that will be used to generate the list of affected assets that will be forecasted by the work requirement.
Item Description	Description of the item that is defaulted as read-only from the selected Item.
Include Assets	You must select if the Affected Assets will be Automatically or Manually included. The Default value is Automatically. Note: You can only update this value if assets have not been explicitly included or excluded. If you have defined initialization details, changing the method will delete them.
Calendar	Option to indicate whether a forecast is to be created based on a calendar pattern for both cycle and non-cycle based work requirements. If selected, you can optionally also select meter and a condition event; you can’t select a day. You must select at least one method to create a work requirement.
Day	Option to indicate whether a forecast is to be created based on a number of days interval for both cycle and non-cycle based work requirements. If selected, you can optionally also select meter and/or condition event. However, you can’t select calendar.
Meter	Option to indicate whether a forecast is to be created based on a meter interval for both cycle and non-cycle based work requirements.
Condition Event	Option to indicate if work orders can be created based on a condition event for non-cycle based work requirements. This check box is displayed only if the Forecast using a cycle check box is deselected, as condition event-only work requirements aren't forecasted. Note: It is recommended to only select this option if you are using the special action to create condition-based work orders, or you are using Connected Assets.