How You Create a Maintenance Program
You can create a maintenance program on the Create Maintenance Program page.
The following are the steps to create a maintenance program:
-
On the Tasks pane, click the Manage Maintenance Programs link.
-
On the Maintenance Programs page, click the Create Program button.
-
On the Create Maintenance Program page, select from or enter value the following fields:
Field Description Name The name of the maintenance program. Code The code of the maintenance program. Concurrent Requirements The option to determine how are concurrent work requirements used when creating the forecast and work orders. The valid values are: - Suppress: The work requirement with the highest cycle interval is included when creating the forecast and work order. In other words, the work requirement with a lower cycle interval is suppressed by a work requirement with a higher cycle interval.
- Merge: The work requirements are merged when creating the forecast and work order.
The Merge and Suppress options will default to each work requirement. Optionally, you can choose to override the option at the requirement level
Note: It's recommended for an administrator to set the Allow Suppress and Merge Across Work Requirements in a Maintenance Program parameter to No on the Manage Asset Maintenance Parameters page located within the Setup and Maintenance work area. Otherwise, certain work requirement definitions for the same asset may consider the option to merge and suppress across work requirements making it difficult to model, manage, and recognize in a forecast. Merge and Suppress is recommended to only be setup within a work requirement.Start Date The start date of the maintenance program. End Date The end date of the maintenance program. Program Type Option used to identify the type of program used to forecast due dates for Maintenance (default) or Subscription assets. This field is for reference only. Program Subtype Optional field used to identify the subtype of program. The values are user-defined in the lookup ORA_MNT_MX_PROGRAM_SUB_TYPE. Allow assets from other organizations Option that enables assets in other organizations, within the same master organization, to be considered in a work requirement and maintenance forecast. - By default, this option is selected. This means that only assets operating in the same maintenance organization as the program are considered.
- Select to let a work requirement consider assets from other organizations.
Note: The option can only be set and updated until the first work order is created for a program. Therefore, existing programs that have work orders already created can’t be enabled or disabled from allowing assets from other organizations.Program Reference Optional reference for a program. An example could be an OEM repair manual reference or a unique subscription identifier. Forecast Window in Days Optional value that represents the number of days into the future the maintenance forecast will be created for all work requirements in the program. If not defined, then either the number of days value at a work requirement or the organization parameter is used. The lowest level of definition takes precedence. It is recommended to define a value at the program header for visibility or if the expected forecast horizon is different than the default number of days value defined in the organization parameters. Set a value that generally considers all or most work requirements in the program, providing a consistent baseline expectation for the forecast horizon of the program. Optionally, you can define different forecast windows at the work requirement level if they require a forecast for a shorter but generally longer horizon.
Work Order Window in Days Optional value that represents the number of days into the future that work orders will be created for all work requirements in the program. If not defined, then either the number of days value at a work requirement or the organization parameter will be used. The lowest level of definition will take precedence. It is recommended to define a value at the program header for visibility or if the expected work order horizon is different than the default number of days value defined in the organization parameters. Set a value that generally considers all or most work requirements in the program, providing a consistent baseline expectation for the work order horizon of the program. Optionally, you can define different work order windows at the work requirement level if they require a forecast for a shorter but generally longer horizon.
Work Order Start Time Option to set the start time of a work order that is created for a due date: - The date you set is considered when the work order scheduler is created.
- If a date is not set, default value of 8:00 AM is used.
Note: Define a start time if you have shifts that begin before 8:00AM daily. Shift definitions and setup affects the start time of a work order. See Work Order Scheduling in the Using Manufacturing guide.Work Order Time Zone Option to set the time zone of a work order that is created for a due date. For newly created programs, the time zone will default from your user preferences but can be edited. For existing programs, the time zone will default to UTC if not defined. It is recommended to set a time zone that matches where the affected assets operate and are maintained. If they are centrally managed or maintained outside of operating organizations, it is recommended to set this value to UTC. Care should be taken before setting this value if you have operations that span time zones for assets within the same program or have users that are viewing due dates across time zones.
Note: In general, your user preferences determines the time zone to be considered when viewing dates and times in the user interface. Therefore, when viewing forecast and work orders dates and times, the user interface adjusts the values to match your preferences.Attachments The attachments in the maintenance program. It can be of file, text, or URL type. Description The description of the maintenance program. -
Click the Save and Continue button or Save and Close button.
Managing Organizational Relationships for Programs
Relationships aren't required to maintain an asset that operates in a same maintenance-enabled organization. However, relationships may be required if you wish to maintain the asset in other maintenance organizations using a maintenance program. Therefore, you should consider how you will model programs as the basis for setting the value of the asset maintenance parameter, Consider Organization Relationships When Creating Maintenance Work Orders Program.
- For assets operating in a maintenance-enabled organization, work orders can be
created:
- In its operating organization without defining any relationships (default capability).
- Only in those maintenance-enabled organizations where a reciprocal relationship is defined.
- For assets operating in a non-maintenance-organization, work orders can be
created:
- Only in those maintenance-enabled organizations where a supports or supports as primary relationship is defined.
- For assets operating in a maintenance-enabled organization, work orders can be
created:
- In its operating organization without defining any relationships (default capability).
- In any other maintenance-enabled organization under the same master organization.
- For assets operating in a non-maintenance-organization, work orders can be
created:
- In any other maintenance-enabled organization under the same master organization.
- Optionally, you can define a supports as primary relationship if you wish for an asset to always be maintained in a specific maintenance organization. If not defined, then these assets can be forecasted and maintained within the program’s contextual organization, without the need to define a relationship.