Preventive maintenance is a discipline involving planned maintenance jobs, for example, regular service, calibration, and inspections. In Enterprise Asset Management, you can create maintenance sequences and set them up on objects or functional locations. You can also set up rounds on functional locations. Maintenance sequences on objects are active regardless of where the object is installed. Maintenance sequences and rounds on functional location are active for the objects currently installed at the location. Instead of setting up maintenance sequences on objects, or setting up rounds on functional locations, you can create rounds that include multiple objects on which you need to perform related types of maintenance jobs in the same work routine. Rounds created from objects - instead of created on functional locations - means that you can select a number of objects for one round that are not depending on being installed on the same functional location.
Maintenance sequences are used for preventive and reactive maintenance on individual objects. Rounds are used for preventive maintenance on a group or a set of objects. Maintenance sequences and rounds are used for generating work order proposals. The work order proposals are saved as object calendar lines, which can be bundled and converted into work orders.
The figure below provides an overview of the work flow from creating maintenance sequences and rounds to creating work orders for objects, based on those sequences and rounds.
A maintenance sequence defines when a pre-planned preventive maintenance job is to be carried out on an object. Maintenance sequences can be related to objects, object types, functional locations, or functional location types, but first you create the maintenance sequences to be used in your company.
A maintenance sequence can have multiple maintenance sequence lines. Job type and interval are specified on the maintenance sequence line. There are two types of maintenance sequence lines:
Maintenance sequence lines of type "Time" are used for recurring planned maintenance based on a fixed time interval. Maintenance sequence lines of type "Counter" are used for planned maintenance or reactive maintenance based on object counter registrations. A maintenance sequence may include several maintenance sequence lines of both types.
Note
If no counter values have been registered for a counter type on an object, the maintenance sequence lines are omitted.
First, you create the maintenance sequences you require for your preventive maintenance jobs and select the object types, objects, functional location types, and functional locations that should be related to each maintenance sequence. Afterwards, if required, you can also add maintenance sequences to an object or a functional location, which is done in All objects > select object > Preventive maintenance FastTab, or All functional locations > select functional location > Preventive maintenance FastTab.
If you add a maintenance sequence to object types or functional location types, it means that when you create new objects or functional locations with those object types or location types, the object or functional location will automatically be added to the maintenance sequence. The start date of the relation to a maintenance sequence will be the current date, which may need to be adjusted.
This section describes how to set up maintenance sequence lines and provides examples of how they can be used.
Note
If you deactivate a maintenance sequence, no calendar posts will be created in the object calendar when you run a schedule maintenance sequence job.
Note
The example described in this and the previous step means that if several maintenance sequence lines overlap, and Omit overlap is selected for one or more lines, the period of omitting object calendar lines is extended to a total of five days (the expected start date on the object calendar line and two days before and two days after that date).
Note
The example described in this step shows that the most comprehensive job, which contains the largest number of tasks, and which is not done so often, should always be inserted as the first line. The more frequent jobs are then inserted as separate lines in the order of frequency, placing the most frequent job at the bottom of the list.
Note
When work orders are manually created on objects that are covered by a vendor warranty, a dialog box is shown to make the user aware of the warranty. The creation of the work order can then be canceled. The check for a warranty relation is omitted for work orders that are automatically created.
Interval type and Description |
Line Type: Time |
Line Type: Counter |
Interval type: Repeated from plan date The count starts from the plan date used, and when you schedule maintenance sequences, object calendar lines are created for when the interval is expected to be reached. |
The Plan date on the maintenance sequence line is used. If no plan date is selected on the line, the Plan date for the maintenance sequence is used. Example: If the number "3" is inserted in the Interval field, and "Year" is selected in the Period field, a new object calendar line will be created once every 3 years. |
The Plan date for the maintenance sequence is used. If the counter has been replaced, the latest replacement date is used as the plan date. |
Interval type: Repeated from start date The count starts from the start date on the object relation. The date is selected in the Object form > Preventive maintenance FastTab > Start date field, or in the Functional location form > Preventive maintenance FastTab > Start date field. When you schedule maintenance sequences, an object calendar line is created when the interval is reached. |
The start date of the maintenance sequence line on object or functional location is used. If that field is blank, the Plan date for the maintenance sequence is used. |
The start date of the maintenance sequence line on object or functional location is used. If that field is blank, the Plan date for the maintenance sequence is used. |
Interval type: Repeated from last work order The count starts from the actual end date and time of the latest work order that was completed on the object and the job type / variant / trade combination. That date and time is shown in the Actual end field in the Work order form. |
The actual end date and time of the work order completed on the object and the job type / variant / trade combination. is used. If no completed work order is found, one of the dates used in the "Repeated from start date" interval type described above is used instead. |
The actual end date and time of the work order completed on the object and the job type / variant / trade combination. is used. If the end date and time was left blank on the work order, one of the dates used in the "Repeated from start date" interval type described above is used instead. |
Interval type: Once from plan date See description for the "Repeated from plan date" interval type above. Only difference is that this interval type is to be used only once. |
See description for "Repeated from plan date" interval type above. This interval is typically used for a one-time maintenance or service job. |
See description for "Repeated from plan date" interval type above. This interval is typically used for a one-time maintenance or service job. Note 1: This interval type is only relevant if the counter is replaced every time you carry out a maintenance or service job. If, for some reason, a counter has been replaced before the end of the planned interval, a new time is calculated for the job from the time of the counter replacement. Note 2: If the counter is replaced when completing the maintenance or service job, this interval type functions as the "Repeated from plan date" interval type above. |
Interval type: Once from start date See description for the "Repeated from start date" interval type above. Only difference is that this interval type is to be used only once. |
See description for "Repeated from start date" interval type above. This interval is typically used for a one-time maintenance or service job. |
See description for "Repeated from start date" interval type above. This interval is typically used for a one-time maintenance or service job. Note 1 above also applies to this interval type. Note 3: If the counter is replaced when completing the maintenance or service job, this interval type functions as the "Repeated from start date" interval type above. |
Interval type: Once from last work order See description for the "Repeated from last work order" interval type above. Only difference is that this interval type is to be used only once. |
See description for "Repeated from last work order" interval type above. This interval is typically used for a one-time maintenance or service job. |
See description for "Repeated from last work order" interval type above. This interval is typically used for a one-time maintenance or service job. Note 1 above also applies to this interval type. Note 4: If the counter is replaced when completing the maintenance or service job, this interval type functions as the "Repeated from last work order" interval type above. |
Interval type: Once reached above This interval type only relates to counters and is used for indicating an upper limit set up on the maintenance sequence line. Object calendar entries will have the expected start date and time of the counter registration meaning that these entries will be created with an expected start date equal to or earlier than the system date. |
N/A |
The counter interval indicates an upper limit. If that limit is exceeded when you create a counter registration, an object calendar line is created when you schedule preventive maintenance. |
Interval type: Once reached below This interval type only relates to counters and is used for indicating a lower limit set up on the maintenance sequence line. Object calendar entries will have the expected start date and time of the counter registration meaning that these entries will be created with an expected start date equal to or earlier than the system date. |
N/A |
The counter interval indicates a lower limit. If that limit is passed when you create a counter registration, an object calendar line is created when you schedule preventive maintenance. |
Interval type: Linked from start date A maintenance sequence can contain more lines using this interval type, and those lines are linked. Typically, you will create a maintenance sequence that contains lines of only this interval type. Object calendar lines are created by identifying the maintenance sequence line that has the first expected start date and time. |
See description for "Once from start date" above. Example: You create two lines in a maintenance sequence for a service job on a car: one time-based line with a 1-year period, and one counter-based line with a 25,000 km limit. An object calendar line is created for the limit that is reached first. For this line type you create the line with the 1-year period. |
See description for "Once from start date" above. Example: You create two lines in a maintenance sequence for a service job on a car: one time-based line with a 1-year period, and one counter-based line with a 25,000 km limit. An object calendar line is created for the limit that is reached first. For this line type you create the line with the 25,000 km limit. Example creating two counter lines: You can also set up a maintenance sequence with two linked, counter-based lines in which the first line has a limit of 10,000 items quantity produced, and the second line relates to the machine or work center requiring service after running 3,000 hours. |
Interval type: Linked from last work order A maintenance sequence can contain more lines using this interval type, and those lines are linked. Typically, you will create a maintenance sequence that contains lines of only this interval type. Object calendar lines are created by identifying the maintenance sequence line that has the first expected start date and time. |
This interval type basically works as "Linked from start date" described above. Only difference is the date on which the interval type is based. The date used is the actual date and time on the latest work order completed on the object and the job type / variant / trade combination. |
This interval type basically works as "Linked from start date" described above. Only difference is the date on which the interval type is based. The date used is the actual date and time on the latest work order completed on the object and the job type / variant / trade combination. |
Note
When object calendar lines are created for time-based maintenance sequence lines, expected time is always at the start of the day. For counter-based maintenance sequence lines, expected time can be anytime during the day.
Below you will find examples of the setup of time-based and counter-based maintenance sequence lines:
Example 1 - Time-based maintenance sequence line: A lubrication job may be set up in a fixed interval, occurring once a week. For that purpose, select "Repeated from plan date" in the Interval type field.
Example 2 - Time-based maintenance sequence line: An inspection job may be set up to be carried out approximately once a week. For that purpose, select "Repeated from last work order" in the Interval type field.
Example 3 - Counter-based maintenance sequence line: A graphical illustration of an hour counter for which a new object calendar line is created each time 250 hours have passed. The interval type for this counter-based line is "Repeated from start date". The start date is the start date of the related objects in the Object detail view > Preventive maintenance FastTab > Start date field, or in the Functional location form > Preventive maintenance FastTab > Start date field. This is an example of a preventive maintenance sequence because the object calendar line is automatically created each time the threshold (+ 250) is reached.
Example 4 - Counter-based maintenance sequence line: A graphical illustration of a decrease in counter value, measuring brake pad wear. An object calendar line is created when a counter registration below 20 mm is created on the brake pad. The interval type for this counter-based line is "Once reached below" or "Once from last start date". This is an example of a reactive maintenance sequence because the object calendar line is not created until a measurement below 20 mm is registered.
Example 5 - Counter-based maintenance sequence line: A graphical illustration of a counter with a threshold of -18° Celsius. An object calendar line is created when a counter registration above -18° Celsius is made. The interval type for this counter-based line is "Once reached above". This is an example of a reactive maintenance sequence because the object calendar line is not created until a measurement higher than -18° Celsius is registered.
Note
When you create a new object, and that object uses an object type related to a maintenance sequence, the maintenance sequence is automatically inserted in All objects > Preventive maintenance FastTab. Also, in the Object types setup, on the Maintenance sequences FastTab, the related maintenance sequences will automatically be inserted.
If you add or remove object types or functional location types in Maintenance sequences, that change will only reflect on new objects created after you made the change.
If you add or remove objects or functional locations in Maintenance sequences, that change will automatically be updated in All objects > Preventive maintenance FastTab, or in All functional locations > Preventive maintenance FastTab.
Preventive maintenance scheduling generates calendar entries on objects, based on the maintenance sequences set up on the objects. You can schedule calendar entries based on selected maintenance sequences, object types, and objects.
Note
The Period and Interval fields indicate how far ahead in time you want object calendar lines to be created, based on the maintenance sequences that you have created (time-based or counter-based). In the first figure below, object calendar lines (= work order proposals) are created from the current date and three months onwards.
Note
If this toggle button is set to "Yes", and the Auto create toggle button is also set to "Yes" on maintenance sequence lines in Maintenance sequences, work orders are created based on the maintenance sequence lines, and object calendar lines with status "Work order created" are also created. If only one of the Auto create toggle buttons is set to "Yes", in this form or in Maintenance sequences, only object calendar lines are created with status "Created". In that case, no work orders are created.
Note
Regarding scheduling of maintenance sequences on functional locations: If you update the setup of object types, products, and models on maintenance sequences in All functional locations > Maintenance sequences FastTab after you have scheduled maintenance sequences, existing object calendar entries related to that functional location are automatically deleted. In order to create new calendar entries, which correspond with the updated maintenance sequence setup on the functional location, you must run a new maintenance sequence schedule for that functional location. Read more about the setup of object types, products, and models on functional locations in the Create Functional Locations section.
Example: You want to create a maintenance sequence for a specific functional location, meaning all objects set up on that functional location at any given time will be included when you run the sequence. In that case, you create a maintenance sequence and select the specific functional location, but you do NOT add any objects in the maintenance sequence. The result is that when you run that maintenance sequence, object calendar lines will be created for all the objects related to the functional location at that time.
If you make changes to object types, products and models in Object types, those changes only affect new objects that use the updated object type. Read more about object type setup in the Object Types section.
Note
In Schedule maintenance sequences, you can set up batch jobs on the Run in the background FastTab to automatically generate calendar entries at regular intervals.
When you schedule preventive maintenance, object calendar lines with expected start date and time earlier than the system date and time will not be created.
The second figure at the end of this article provides a graphic illustration of a time-based maintenance sequence calculation.
Regarding counter-based maintenance sequences: In the last two figures below, two different counter registration cycles are shown. They are based on a maintenance sequence set up for object "V0001", expecting the object (a car) to run approx. 2,000 km every month.
In the first example, the expected 2,000 km are not reached every month. According to the counter-based maintenance sequence, the threshold is 2,000 km, meaning when you run a maintenance sequence scheduling, an object calendar line should be created each time the 2,000-kilometer threshold is reached. In example 1, there are 4 registration lines, but the 2,000-kilometer threshold is only reached once. This means that when you run schedule maintenance sequences for this object, for example for a 3-month period, only one object calendar line will be created.
In next figure "Object counters example (> 2.000 km)", 2,000 km or more are registered every month. Therefore, three object calendar lines would be created if you schedule maintenance sequences for this object for a 3-month period.
The examples described here show that all counter registrations made on an object show a trend describing wear and tear on the object. That trend is used as calculation basis at the time of maintenance sequence scheduling.
In Enterprise Asset Management, you can create rounds for various objects, on which you need to carry out a similar task at regular intervals. For example, lubrication jobs or safety inspection jobs that need to be carried out on a number of machines within the same intervals.
Rounds can be set up on objects and/or functional locations. If you add a functional location to a round, all objects installed on the location at the time of scheduling are included in the round.
First step is to create a round, including objects and/or functional locations, that require the same form of maintenance job. Next, you schedule the rounds. When you have completed the rounds schedule, you can see object calendar lines created from the rounds in the All object calendars, Open object calendars, or Open object calendar pools grid views.
Note
Refer to the Create an object section for information on the setup of rounds on objects. Refer to the Create Functional Locations section for information on the setup of rounds on functional locations.
Note
You can edit line numbers to create your preferred object sequence. When you schedule a round, object calendar lines are scheduled in the order they are shown on this tab.
Note
You can edit line numbers to create your preferred functional location sequence. When you schedule a round, object calendar lines are scheduled in the order in which functional locations are shown on this tab. Each functional location may have several objects installed. The sequence in which objects are scheduled on a functional location is determined by the object ID.
Note
If you set up objects on the Object lines FastTab, and functional locations on the Functional location lines FastTab, on the same round, the sequence of scheduling object calendar lines is that first, the objects selected separately on the Object lines FastTab are generated as object calendar lines. Next, object calendar lines are generated from the objects installed on the functional locations set up on the Functional location lines FastTab.
The Objects and Lines fields located in the Details section at the top of the form show summarized information from the Object lines FastTab regarding the number of objects and object lines set up on the selected round.
Example with a setup of objects as well as functional locations on a round: You have set up two functional locations on which you know that all objects must undergo the same inspection at regular intervals. You have also added two spare parts/replacement objects that are installed on a spare parts location. Those two replacement objects must undergo the same inspection within the same intervals..
When you have set up a round, you run a schedule job to schedule all the jobs related to the round.
Note
If this toggle button is set to "Yes", and the Auto create toggle button is also set to "Yes" on maintenance sequence lines in Maintenance sequences, work orders are created based on the maintenance sequence lines, and object calendar lines with status "Work order created" are also created. If only one of the Auto create toggle buttons is set to "Yes", in this drop-down or in Maintenance sequences, only object calendar lines are created with status "Created". In that case, no work orders are created.
Note
When work orders are manually created on objects that are covered by a vendor warranty, a dialog box is shown to make the user aware of the warranty. The creation of the work order can then be canceled. The check for a warranty relation is omitted for work orders that are automatically created.
You can set up a batch job on the Run in the background FastTab to schedule rounds at regular intervals.
If a round is included in several work order pools (refer to the Work Order Pools section), one record is shown for each pool in Open object calendar pools. This is done to optimize the filtering options on work order pools
Maintenance stops are used to get an overview of the capacity required to carry out maintenance jobs on specific objects during a specific period. For example, you can create a maintenance stop for Production line 10 in Production Hall 29-A on production site 02. The maintenance stop has a start and end time indicating the period in which the objects related to the maintenance stop are not available for production.
The maintenance stop is an overview of object calendar lines and work orders on related objects during a specified period. The lines related to work orders all have an expected start date within the maintenance stop period. You can extract useful information and make adjustments to planned maintenance jobs:
When objects have been selected on a maintenance stop, all open object calendar lines and work order lines relating to active work orders are included in the maintenance stop.
Click Enterprise asset management > Common > Maintenance stops > All Maintenance stops to open the list. All maintenance stops contains a list of all maintenance stop records and displays some of the information related to the maintenance stops.
Note
You can copy objects from one maintenance stop to another. In All maintenance stops, select the Copy maintenance stop button, and make your selections in the From maintenance stop and To maintenance stop fields, and click OK.
In All maintenance stops, click the Object calendar lines button or the Active work orders button to open the related lists and view the lines related to the selected maintenance stop.
Note
The object calendar lines and work order lines related to the selected objects are automatically updated if new work orders or object calendar lines have been created after you created the maintenance stop. For example, if you schedule maintenance sequences or rounds on the related objects two days after the maintenance stop was created, new object calendar lines are automatically added to the maintenance stop record.
Copyright Dynaway A/S