Navigation:  Management > Maintenance route > Maintenance route plan >

Editing a maintenance route plan

Previous  Top  Next

To edit the data in a maintenance route plan, first locate the desired plan. After that, with the plan selected on the main screen, click on the edit button. At this point the maintenance route plan data screen will be displayed for editing.

 

General data

The General data section provides general information about the maintenance route plan, divided into the following subsections:

 

General data

In this section, complete or edit the following fields:

ID #: Enter an ID # for the maintenance route plan.

Name: Enter a name for the maintenance route plan.

Plan type: This field will be filled with the plan type in question which in this case is Maintenance route.

Responsible team for route: Select the team responsible for the maintenance route. Users of this team will receive the Maintenance route task as soon as the planning is saved for each of the routes defined in this plan.

Date-based frequency: Check this option to enable the execution frequency of the asset maintenance by means of the Maintenance route task. Remember that this frequency may be pre-configured if this plan standard activity was configured with that frequency. After checking this option, also fill in the following fields:

Frequency type: Select the frequency type for the maintenance execution of the asset:

oExecution date: The maintenance route will be executed on a specific date.

oFirst use: The maintenance route will be executed at the determined frequency after the first use of the asset.

oUsage time: The maintenance route will be executed at the frequency determined by the usage time of the asset.

Frequency: Enter the frequency with which maintenance routes will be carried out. In the Unit field, define if the frequency will be calculated in days, weeks, months or years. For example: every 3 days, every 2 months, every year, among others. Remember that, in addition to the option configured in this field, the system will take into consideration the frequency type selected before.

Date visualization: Set how the deadline will appear on the system screens: day/month/year, month/year or week/year. If the selected template is "month/year", the system will generate the task in the last day of the month. If the selected template is "day/month/year", the system will validate whether the maintenance route execution date is a working day according to the defined calendar; if it is not, it will move the execution to the last business day.

Next execution: Select the date on which the maintenance route will be executed. When the maintenance route plan is scheduled, the dates of the next executions will be calculated according to the frequency defined in the previous field. If the execution does not occur after that date, the system will generate the Plan due date task.

Calendar: Select the calendar which the maintenance route execution dates will be based on. This field may be filled in if there is a calendar configured in the general parameters of SE Asset. This field will only be displayed if the user selected the "Inherit activity data" option when creating the maintenance route plan.

Create activity automatically: Check this option to have the maintenance route created automatically. Configure also the following information:

Create ___ days before the next execution: Enter how many days before the next execution the new activity will be created.

Create activities even if pending activities already exist: If this option is checked, new activities will be created, regardless of the existence of pending maintenance route activities.

Generate activities in the step of: Define if the maintenance route activities will be created in the planning or the execution (To be started) step.

 

Maintenance route

In the Maintenance route subsection, the configuration of the related activities and assets/equipment shall be carried out at each step of the maintenance route contained in this plan. Use the buttons in this section to add, edit, or delete the items that make up the route of this plan:

1.1_auxnmbTo add a new step to the maintenance route, click on the new toolbar button in this section. At this point, the system will display the maintenance route item data screen:

 

dados_item_rota_manutencao

 

2.Fill in the following fields:

Order: Execution order of the activity in the maintenance route. This field is automatically filled in by the system, but it is possible to change the order.

Activity: Select the standard activity that will be associated with the asset maintenance.

 

3.In the Step object, define how the activities to be executed in this step of the maintenance route will be created:

Specify assets: Check this option to define the assets related to the route step. The system will require the association of at least one asset, but it is possible to add multiple records.

All assets that have a specific user: Check this option to define a Responsible user. That way, the route will be related to all the assets that are under the selected user responsibility, regardless of the location associated with the asset. This user is defined in the storage place creation.

All assets that are in a specific location: Check this option to define a Location of the system, that way, the route will be related to all assets that are in the selected location.

All assets that are in a specific location and have a specific user: This option limits both a Location and a Responsible user. That way, the route is related to all assets that are with the user and the selected location associated with the asset.

 

4.In the Activity execution, define the configuration of the activity execution:

Generate one WO for each asset: By selecting this option, when executing the Maintenance route task, the system will create a maintenance activity (Work order) for each asset in the route step. For example, if the selected configuration was Location and that location has 100 assets, the system will generate 100 WO records.

Generate one WO associating all assets: By selecting this option, when executing the Maintenance route task, the system will create a maintenance activity (Work order) for all asset selected in this step. For example, if the selected configuration was Location and that location has 100 assets, the system will generate one WO with 100 related assets.

 

5.Save the maintenance route step data. Repeat the procedure in this section for all items/steps that will make up the maintenance route plan.

 

For each step in the route sequence, it is possible to define different configurations.

 

History

In the History section, the system will display the route execution history and maintenance route activities in question:

Activities history: This section displays the history of the activities (work order) of the route.

Route executions history: This section displays the history of all executions of the route.

 

Notification

In the Notification section, it is possible to schedule notifications that will be sent via e-mail the day before and/or after the maintenance route expires. For that, fill in the following fields:

Notify before due date: Check this field so that the notification is sent before the maintenance route expires. In that case, in the Notify before field, select the number of days that the notification will be sent before the route maintenance expires.

Notify on due date: Check this field to have the notification sent on the due date of the maintenance route.

Notify after due date: Check this field so that the notification is sent after the maintenance route expires. In this case, in the Notify after field, select the number of days that the notification will be sent after the maintenance route expires. Also, set the Frequency with which notifications will be sent after the maintenance route expires.

Subordinates' tasks: Check this field to enable tracking notifications for maintenance route tasks.

Notify leader of responsible user: The notification will be sent to the responsible user leader through maintenance route.

Specific user: The notification will be sent to a specific user. Select the user in the respective field.

Go up __ level(s): Enter how many levels above is the leader who will receive the maintenance route notifications.

Frequency: Enter the frequency, after the delay, that maintenance route notifications will be sent.

 

After making any changes to the maintenance route plan data, save the record.