The music is called Drag Race from a group called TrackTribe.

Hello, and welcome back to Maximo Bite Size. A series of videos on the functional aspects of Maximo Manage.

Title

Good afternoon and welcome to the eighth episode in the series on Maintenance Planning and the first of three videos where we will explore the functionality of the Preventive Maintenance application. I’m Andrew Jeffery and today we will discuss time-based Preventive Maintenance and Inspections. Next week it will be meter-based and PM hierarchies, and the next video after that we will look at PM forecasting.

Please subscribe to this channel so that you don’t miss out on new episodes as they are published.  

Learning Objectives

The Preventive Maintenance application is widely used by Maximo clients, but many use it just for time-based maintenance and inspections which is today’s focus. There will be a certain amount of overlap with last week’s video on Master PMs, the template for these Preventive Maintenance records, so apologies if you have heard parts of this before.

I’ve split this video into three parts. In the first part we will look at the Preventive Maintenance header and discuss fixed and floating schedules. This is the minimum you need to get started with time-based PMs. In the second part we will look at Job Plan Sequences, Seasonal Dates and PM Work Generation, including considering Time Zones. In the final part we’ll look at the data that is copied to the work order from the PM and some other more advanced topics like Extended Dates, and PM Alerts. 

It could be one of those longer videos, so, let’s get started.

Preventive Maintenance Header

The Preventive Maintenance application is used for any requirement to generate work orders on a frequency basis, either time, meter or a combination of time and meter. The application is used for the generation of preventive maintenance (PM) and inspection work orders. The work that is performed is normally defined on a Job Plan, but PMs can generate work orders without a Job Plan and PMs need not have any frequency details, something I call an on-demand PM, we will find out about this when we discuss generating work orders.

PMs exist at the SiteA structural element of a Maximo database that is used for data separation. More level ; they are generating work orders which are site level records. A PM has a simple set of statuses Draft, Active or Inactive, and PMs need to be at ACTIVE state to generate work orders. A PM must reference either a location or asset, a route or a General Ledger (GL) account, something to charge the work order to. Without either of these you will receive the error message “BMXAA3204E – An asset, location, route or a GL account must be associated with the PM.” When you change the status of a location or asset to DECOMMISSIONED or a synonym then you will have an option ‘Change the Status of All Associated PMs to Inactive’. Changing the status of the PM to active or inactive does not make the record read-only, the PM is always editable.

Notice earlier that I said a PM needed a location or asset, these two fields are mutually exclusive, only one of them can have a value, not both. A Route is often used for inspections of multiple locationsA physical place where assets exist and where work can be performed. More and/or assets. A route can be referenced on a PM with or without a location or asset, although the combination of a location with a route is common. You might also notice that while a work order can reference a Configuration Item the PM does not reference a CI. This is because a configuration item can have an associated asset or associated location, and so will be pulled onto the work order if the PM references a location or asset that references a configuration item.

We saw last week that a PM record may be generated from a Master PM and when this is the case the Master PM field is populated. You can associate an existing PM with a Master PM so that you can receive updates from the Master PM. If you no longer want to receive updates from the Master PM, then you can either remove the reference to the Master PM or set the field ‘Override Updates from Master PM?’ . The later method is preferable because if you choose to remove the reference from the Master PM then you risk another record being generated from either the Master PM or Asset Template.

The Lead Time is the number of days prior to when the next work order will be required to start which provides time to prepare or plan the work order, including time required to purchase materials or services. Think of this as at least the amount of time you expect the work order to be in a Waiting for Material state (WMATL) is the status on a work order. The Lead Time (Days) field defaults to zero and can only be set if Lead Time Active is also set, but this is the default. If the Lead Time Active is toggled to off, then the Lead Time (Days) field will be made null. You can get into the Lead Time (Days) field and set a value if Lead Time Active is not set, but you will receive an error when trying to save the record.

The Counter field is important, and we will explain this in a while.

Fixed and Floating Schedules

On the Frequency tab there are two tabs towards the bottom of the screen for Time Based Frequency and Meter Based Frequency. We will discuss Time Based Frequency today.

The field ‘Use Last Work Order’s Start Date to Calculate Next Due Date?’ when set creates fixed schedules, if unset it is floating schedules. A Fixed Schedule is quite easy to understand. If the Target Start Date is 1-Jan and there is a 3-monthly PM then the next two Target Start Dates will be 1-Apr and 1-Jul. Maximo is using the Last Start Date of a generated work order to determine when to generate the next work order, the Last Start Date is shown on the main tab. With a fixed schedule it does not matter when you complete the work order. Each of the three work orders shown in the top left are completed after their Target Start date, two weeks late on 14th January, 6 days late on 6th April and 11 days late on 11th July, the inverted blue triangles represent the target start dates.

If ‘Use Last Work Order’s Start Date to Calculate Next Due Date?’ is not set, then a floating schedule is created. In the bottom left illustration, the first Target Start Date is 1-Jan, but Maximo uses the Actual Finish of the work order in this case 14-Jan to set the Target Start of the next work order 3 months later on 14-Apr, i.e., the next work order is due to start the time frequency after the last work order is completed. On the main tab the Last Completion Date is entered when a PM is completed or closed, and this is used to set the Earliest Next Due Date when a floating schedule is used. If the next work order is completed on 20-Apr then the next target start will be 20-Jul, 20 days later than what it would have been with a Fixed schedule.

As a floating schedule is waiting for the completion of the previous work order you cannot generate work orders into the future that is more than the frequency ahead of time now. While there is still an open work order for the PM you will receive an error message when attempting to generate a work order from the PM, the error is ‘BMXAA3191E – PM IC-11460 is not due yet, or it does not fall within the active season.’ For a fixed schedule you can generate work orders into the future, not that this is good practise.

In the Time Based Frequency tab a frequency must be entered, the Frequency Units will be DAYS, WEEKS, MONTHS or YEARS. The Frequency field must be a positive value, but it can also be zero, this is the default. A zero frequency PM can be used for on-demand generation of work orders, which we will review a little later. To be certain that no work order is generated, then do not enter an Estimated Next Due Date , if one exists then a work order will be generated when the Estimated Next Due Date is today or in the past, no further work order should be generated.

The Target Start Time will normally be the time of the first shift in the day, a later time might be used for the start of an afternoon or evening shift if this is the time you want to display on the generated work orders.

We’ll come back to the Extended Date and Alert Lead (Days) fields in the last section of this video.

Job Plan Sequence

Before we get to generating work orders, we would normally be associating the PM with one or more Job Plans . The Job Plans provide the information required for planning the tasks and resources needed to perform the work order. A PM does not require a Job Plan, work orders can be created without them. 

You can associate the Job Plan from the main tab and for a new PM when you do this Maximo will create a record in the Job Plan Sequence table window with a Sequence value of 1. In many cases there is just one Job Plan which is performed every time a work order is generated; however, Maximo supports sequencing of Job Plans where a different Job Plan may be attached to the work order depending on the nth occurrence of generating a work order.

In the example shown there are three Job Plans in the Job Plan Sequence table window. Note the Job Plan field above this is read-only and reflects the Job Plan (Breaker Inspection) performed where the Sequence is 1, when there are multiple records in the table window the field becomes read-only. This PM has a frequency of 1 MONTH and so, every 12th month the Operate Breaker (BREAKOP) Job Plan is performed, and every 48th month (4 years) the Overhaul Breaker (BREAKOVER) Job Plan is performed. The Breaker Inspection in this case only takes 30 minutes, the Operate Breaker takes 2 hours, and the Overhaul of the Breaker is given 8 hours to complete. Only one work order is generated at each frequency, you would not get three work orders on the 48th occurrence of generating a work order. If the Job Plan for the Breaker Inspection had multiple tasks, then the tasks of this job plan are often included in the other job plans so that in effect you are performing an inspection and additional activities for the Breaker Operate and Breaker Overhaul jobs.

On the main PM tab there is a field called Counter which defaults to zero and increments by one every time a work order is generated from the PM. Therefore, in our example the Breaker Operate Job Plan (BREAKOP) is selected after the Counter is incremented to eleven and will be the next Job Plan that is associated when the 12th work order for the PM is generated.

When you first set up a PM you may have been performing work manually or in another system and you may need to adjust the counter which you can do using the action Set PM Counter. The dialog that opens can be seen in the bottom of the slide and it shows the current Counter and allows you to enter the New PM Counter . You can move the New PM Counter field forward or backwards. If we are in the middle of September, the 9th month, and the Breaker Operate Job Plan is to be performed in December the 12th month, then the New PM Counter should be set to the number of work orders that might have been generated by today, i.e., it should be set to 9 if the work orders are generated on the 1st day of the month. It will be incremented to 10 at beginning of October and 11 at the beginning of November. On the other hand, if the work orders are generated on the 25th of the month then you would set the counter to 8 because you have three more work orders to generate before you get to perform the Breaker Operate Job Plan. 

The setting of the PM Counter does take a little getting used to. The action View Sequence can help when you download the results to a spreadsheet and add a column to generate dates when the work orders are expected to be generated. It can help to check that the Job Plans with larger Sequence numbers occur when you expect them.

Below the Counter field on the main PM tab is a read-only indicator of whether there is a Job Plan Sequence containing multiple Job Plans. If it unset there is either no Job Plans or just one.

The Total Work Units field is used with Dynamic Job Plans functionality which I aim to cover in the set of videos associated with Work Management.

Seasonal Dates

Also, before we get to generating the work orders we ought to consider when they can be generated. The Seasonal Dates tab is quite quick to explain.

The Active Days are the days of the week in which you are happy for a work order to be generated. In our example it looks as if we are happy for the work to be performed on any day of the week, which would be sensible for a 24×7 operation. If you normally only work Monday to Friday, then you should only select those days of the week and deselect Saturday and Sunday. If a work order falls due on a Saturday or Sunday then the Target Start Date will occur on the following Monday, unless the field ‘Schedule Early on Frequency Conflict?’ is set, in which case it will be the Friday. 

A little further down, the PM will also allow you to set an Active Time , which would normally be the start time of the shift when the work order will be scheduled and assigned. In our case it looks as if the teams may be working 7 days a week with a day shift that starts at 08:00.

The Active Dates table window below this allows you to build multiple periods using the Start Day, Start Month and End Day, End Month fields, you can just see the column headings. The two fields Start Day and End Day are values between 1 and 31 but Maximo does validate the day number in the chosen month. An active period is the time at which you accept a work order to be generated, if it falls outside of the period, then Maximo will generate the work order to start on the first day of the next active period. For example, some PM work cannot be performed during wintertime, so you may set the active period from 1-Mar to 30-Nov, leaving the three winter months of December, January, and February when the work order will not be generated during this time. A work order that does fall due in these months will have a Target Start date of 1-Apr.

Generate Work Orders

Finally, we come to the manual action Generate Work Orders. To generate work orders the PM must be in an ACTIVE state and the referenced location or asset must also be in an OPERATING status (or a synonym). You will receive an error message if the location or asset is in a NOT READY state, and you can’t add a DECOMMISSIONED asset or location to a PM. 

Generate Work Orders is a simple enough dialog with four fields, some of the defaults are found in the OrganizationsA structural element of a Maximo database which is used for data sharing and is often aligned to a legal entity of an organisation. More application and the dialog for PM Options, these are Site specific settings, you do need to select the appropriate site first, something which I often forget to do. 

The ‘Generate WOs Due Today Plus This Number of Days’ field is a look ahead period from today, it may be referenced as the “slack” time. With a default of zero there is no look ahead and Maximo will only generate work orders where the Target Start Date would be today. To have the work orders generated for next week you would set this value to 7, for the next month then set it to either 28 or 30. There is no setting which will allow you to say generate all the work orders due in the next calendar month because the number of days in each month fluctuates. It is quite common to see people use the value of 7, 14, or a multiple of 7 depending on how frequently they generate the next set of PM work orders.

The Generate Work Orders action also works from the List tab against a selected set of PMs. If you have selected many PMs and you use this action and there are a lot of work orders to generate then it will tie-up your PC unless you select ‘Run Work Order Generation in the Background’ . If you do opt for this, then you can be notified when the last work order is generated by providing your email address in the field ‘Notification E-mail for Work Order Generation’ .

Most often the setting for Use Frequency Criteria is set and it remains that way. However, if you want to generate a work order and you receive the error message ‘BMXAA3191E – PM 1010 is not due yet, or it does not fall within the active season.’ then you can still generate the work order by deselecting Use Frequency Criteria. This will always increment the Counter and if it is a fixed schedule and ‘Use Last Work Order’s Start Date to Calculate Next Due Date?’ is set it will add the frequency to the Last Start Date to derive an Estimated Next Due Date. If it is a floating schedule, then the new work order’s target start date will be the same as the Last Start Date.

I deselect the field Use Frequency Criteria frequently when I’m doing testing of PM based work orders where the dates don’t matter. If you are using On Demand PMs with a zero frequency, then you need to deselect Use Frequency Criteria in order to generate the work orders for the shutdown or outage or other reason for using PMs with a zero frequency.

When you go to Generate Work Orders and the PM has a forecast then you will receive the message ‘BMXAT0231E – A forecast exists for this PM. Generating a work order from this PM will delete the forecast. Select OK to create the work order and generate the forecast later using the cron task.’ As you generate PMs frequently, then if you are starting to use PM Forecasts you do need to consider implementing both the PM Work Order Generation and PM Forecast Generation as background Cron Tasks. We will discuss PM Forecasts in an upcoming video.

The Cron Task called PMWoGenCronTask will allow a schedule to be created when work order generation occurs as a background activity. There may be an active existing Cron Task Instance called TBPUMP with only a parameter for a logfile. This is linked to an extra set of settings in the Organizations application and PM Options. In this dialog there is a section called ‘Stand-alone PM Work Order Generation Process Settings’ where you can opt for Automatic PM WO Generation. There are two other fields in this section ‘WO Generation Where Clause’ and ‘E-mail Address Notification’. The first field allows you to filter the PMs which you wish to consider for work order generation. In a MAXDEMO database this is ‘status = ‘ACTIVE’’. You should configure this field to reduce the PM records that can be generated depending on your circumstances, to avoid Maximo from performing unnecessary work and to avoid a lot of error messages of the type BMXAA3191E which alerts you to a PM which is not due yet. The other field will provide you with an email when the automatic work order generation has completed.

You can have multiple instances of the Cron Task which does give you a greater amount of flexibility than just using the settings in PM Options. For example, a utility company may have one site with many regions and areas, you can be more granular using multiple Cron Task Instances, spreading the load on the Maximo system when work orders are being generated, each area may have its work orders generated at a different time of the night. Each Cron Task Instance takes three parameters, a SiteID (or a comma separated list), a SQLWhere clause which helps to filter the PMs, and a log file directory and filename.

Time Zone Rules

Before we finish this section on Generating Work Orders, we should discuss the Time Zone Rules application which will be found in the Administration module. The purpose of this application is to allow you to perform processes that will derive a date in a different time zone to the user performing the process. There is only one process currently, it is called PMWOGEN for the generation of work orders from PMs. What we want is to generate a PM based work order that will have a target start time which is in the time zone of where the work is performed, this would normally be the time zone of the asset or location. If a user from the time zone is looking at the work order it must be a time that makes sense to them.

When you generate a work order from a PM the time element of the Target Start date of a work order defaults to 00:00 (12:00a.m.) but you can modify this by using the Target Start Time field on the Time Based Frequency tab. If you modify this field to 08:00 then the work order’s Target Start Date will be 08:00 if the profile of the user generating the work orders has a time zone of Europe/London (UTC+0). If the profile of the user has a time zone of Europe/Athens (UTC+2) then the Target Start Date will show as having a start time of 10:00. If you move the user back to a time zone of Europe/London (UTC+0) the same work order will show as having a Target Start Date of 08:00, i.e., the Target Start Date is being displayed in the time zone of the user.

If you use the Associate Time Zone action on the PM and gave a time zone of America/New_York (UTC-5) and generated a new work order there will be no difference in the time element of the Target Start Date, it was still 08:00. If you go to the Assets application and use the Associate Time Zone action for the asset and set the time zone to America/Chicago (UTC-6) then the Target Start Date will still show as 08:00. There is currently no Time Zone Rule, so without a Time Zone Rule it doesn’t matter what time zone the PM or asset exists in, those time zones you have entered are not being used.

If we create a Time Zone Rule for the PMWOGEN process and use a Process Rule of ASSET which will look for the asset’s time zone, then the Target Start Date of a newly generated work order from the PM will be 14:00. When I first saw this, I did wonder whether the calculations were correct, but you need to log on with someone with that time zone to see that when they look at the same work order the time is 08:00, i.e., the same time you entered on the PM record for the Target Start Time field.

The Process Rule field tells Maximo the order of fields to search to derive a time zone to use. For example ASSET,LOCATIONS,ROUTES says look first to the Asset’s record, then the Location’s record and finally to the Time Zone on the referenced Route. Dot notation can be used. The places where Time Zones can be entered are on the Asset, Location, Route, Site, Organization, and PM, except none of the 17 supplied Process Rules reference the PM object. Therefore, without adding a new set of rules in the PROCRULE object, then while the PM application has an Associate Time Zone action, what you enter here will not get used.

To create new process rules, you need to use a SQL insert statement for the PROCRULE table. If you do have PMs which are not based on asset, location, or route but GL Account, then you will need to do this in order to be able to use the time zone associated with the PM.

Work Order Data

When the work order is generated, data is copied from the PM or the Job Plan which is next due according to the Job Plan Sequence. If a PM references a Route with multiple route stops, then you will either get multiple child work orders, tasks, or records in the Multiple Assets, Locations and CIs table.

The main PM tab has a couple of sections where data is copied to the work order, we’ll start with the section called Work Order Information. It will be considered good practise to always populate the Work Type , Work Order Status and Priority fields. The default for the Work Order Status is WSCH – Waiting to be Scheduled. It would be common to use PM as a default for the Work Type, these are the work types defined against the WORKORDER class, work types are often configured to a different set of values from those you receive as standard in Maximo. The Priority is a value in range 0-999 where 999 is high, but better to limit this to a smaller range of 0-10 and provide a description to each value via a Numeric Domain.

The Priority field also exists on the Job Plan as do many of the fields we will discuss. The Priority on the PM takes precedence over that on the Priority on the Job Plan. However, there is an Organizations – PM Options setting called ‘Use Priority from Job Plans on Sequenced PMs?’ that will reverse that. You don’t need to have multiple Job Plans on the PM for the priority to be derived from the Job Plan.

The Interruptible field is used to indicate whether the work order can be interrupted once it has started, i.e., whether the next shift should continue with the work if it is unfinished by the shift that started the work order. The Interruptible field is copied from the PM to the work order, even if the Job Plan says that it is interruptible. If the PM indicates it is uninterruptible, then that will be the same setting on the work order, the PM takes preference over the Job Plan.

The field Requires Asset Downtime will rarely be used on a PM because as soon as you enter a Job Plan it will be blanked and made read-only. The Job Plan also has fields for both Requires Asset Downtime and Requires Location Downtime, both fields being copied through to the work order.

The Start and Finish Constraint Offsets create a time window around the Target Start date on the work order. The Start Constraint Offset is the number of hours earlier than the Target Start date used to create the Start No Earlier Than date. The Finish Constraint Offset is the number of hours later than the Target Finish date used to create the Finish Not Later Than date. These constraint offsets will be found on both the PM and the Job Plan, Maximo will use the one which creates the larger time window.

There are seven fields in the Responsibility section. The Owner and Owner Group fields are mutually exclusive, only one of the fields can have a value. Work Group and Lead are also mutually exclusive. The Crew Work Group and Crew can both have a value, but you should make sure that a Crew belongs to the Crew Work Group otherwise you will receive an error message when you try to generate a work order ‘BMXAA4191E – The value BOSOHLNW is not valid for Crew. Specify a valid value for Crew.’ The other Responsibility field is Supervisor.

It is easiest to use the Responsibility section on a PM and to leave the Responsibility section fields on Job Plans blank when the Job Plans are used with PMs. The Job Plan Responsibility fields can be used for Job Plans that are not used on PMs. This is because when they combine onto a work order the validations will occur. For example, if you had Owner on PM and Owner Group on Job Plan then both cannot exist on the work order. When the responsibility fields exist on both a PM and a Job Plan the PM takes precedence. When the Work Group is copied to the work order from either the PM or Job Plan the Lead is derived from the Group Default on the associated Person Group, trying to understand where the Lead has been derived from is not obvious. 

A little further down in the Resource Information section there are fields for GL Account and Storeroom. If GL validation is enabled for the Organization in the Chart of Accounts application – Validation Options and the field Validate GL Component Combinations? then if the status on the PM is at APPR (approved) or later, which is highly likely, then a full GL will be required on the work order that is being generated, if it is incomplete, you will get an error message. The GL Account on the work order is derived from the GL Accounts on the PM, Asset and Location in that order. The PM GL Account is often a partial GL Account providing only one or two of the segment values being derived, others segment values being derived from the partial GL Accounts on the Asset or Location. By the time the partial GL Accounts have merged all the mandatory GL segments need to have a value, and the code combination of this needs to exist in the Chart of Accounts table.

The Storeroom and Storeroom Site fields should be populated especially if Job Plans are shared across multiple sites. If it is left empty, then it is filled by the Default Storeroom of the user that generates the work order. This can be set on the PMWoGenCronTask instance, but it is often set as the user MAXADMIN, and MAXADMIN can’t have multiple default storerooms. As PM based work orders are often generated after the state of approval you do need to get this right so that the storeroom reservation is made on the storeroom that makes sense to the PM. It is possible to reference a Storeroom from a different site to the PM, but this would be a little unusual.

Extended Date

The Extended Date is used with fixed and floating schedule PMs, but not with a zero frequency on-demand PM. It allows you to give an extension to the PM, for example if resources are short or there is other priority work taking place, for example a shutdown. If you set the Extended Date more than the frequency in front of the Estimated Next Due Date you will receive the warning ‘BMXAA3227W – The extended date entered will cause at least one cycle to be skipped. This may cause a disruption with job plan sequencing.’. What this means is that you need to consider whether the counter should be incremented (or not) and this depends on the Job Plan Sequencing. For example, if the next job plan to perform is the normal job plan, then you might consider skipping it by incrementing the counter, if on the other hand the next job plan is a special one with additional steps you will probably not wish to skip it. 

Once you have added an Extended Date you can choose whether to use the Adjust Next Due Date field. If you had a 3-monthly PM set up to create a fixed schedule 1-Jan, 1-Apr, 1-Jul, and the Estimated Next Due Date is 1-Apr, then if an Extended Date was added one month later as 1-May and Adjust Next Due Date is not set, then the Earliest Next Due Date after generating a work order would be 1-Jul, i.e. it would continue with the schedule as previously set, this can be seen in the top illustration on the left. If the Adjust Next Due Date field is set, then work orders would be generated three months after the Extended Date of 1-May i.e., the 1-Aug, as seen in the bottom illustration on the left, for fixed schedule PMs this is irrespective of when the last work order generated from the PM is completed.

When you use an Extended Date, the dialog Extend Date Comment opens for you to enter a reason for the extension. This used to be a part of Maximo Calibration but as calibration is now part of Maximo Application Suite the dialog will now open. The Estimated Next Due Date shown in the Time Based Frequency tab shows when the PM is next due without considering the extended date, in our example this will be 1-Apr. The Earliest Next Due Date on the main PM tab does consider the Extended Date and will show 1-May. 

You might notice after entering an Extended Date and entering the reason for the extension that the Extended Date has now become read-only. This is due to a setting in the Organizations application and action Calibration Options – Work Order – Other Organization Settings. There is a field called ‘Default Amount Allocated to Extend Date in PM Application’ which defaults to 1, this allows you to change the Extended Date once only. If it was a setting of 2, then you could change the Extension Date twice before it becomes read-only.

The Override Extend Date action is an action provided by Maximo Calibration which gives a person with access to this option the ability to override the Extended Date, except with fixed schedules it is likely that you will receive the error message ‘BMXAA9140E – The extend date cannot be overwritten because a work order is generated or because the PM counter is greater than zero.’. The dialog only opens for a new PM or a PM where the counter has been reset back to zero. I’ve raised a case with IBM Support as I cannot understand why it would be restricted in this way. If I get an answer after the video is published, I’ll write a comment on the YouTube video. For floating schedules, the Override Extend Date dialog opens. 

When the work order is generated, the Extended Date is blanked and the Estimated Next Due Date and the Earliest Next Due Date on the main PM tab should now align.

Incidentally if the PMs are associated with a Master PM, then the Extended Dates can be viewed from the Master PM application using the action View PM Extend Dates. The history of extension dates on the PM is found in the action Override Extend Date, which currently requires the counter to be at zero.

PM Alerts

The Alert Lead (Days) field is the number of days prior to the next due date when a Corrective Maintenance work order, a work order with work type of ‘CM’, reaches a certain status change, at which point the user will be prompted to generate the next PM work order early if they wish the PM work order to be performed at the same time as the corrective work.

The status change is defined by a setting in the Organizations application and PM Options called ‘Generate PM Alerts for Assets When Corrective Maintenance Work Order Status is’. When the View PM Alert Information dialog is triggered (as seen in the bottom left of this slide) you will be shown the PMs which have the same location or asset as the CM work order, you select the PM(s) you wish to be performed at the same time and then press OK. You’ll receive an information message like ‘BMXAA3208I – PM 1062 created work order 1397’ and if you look at the Plans tab of the CM work order you’ll find a new child work order, the one generated from the PM and referenced in the message.

The date of the status change on the CM work order must be within the alert period of the PM, this is the Earliest Next Due Date – Alert Lead (Days). The Alert Lead (Days) must be a value less than or equal to the frequency on the PM. The work order generated from the PM will have a Target Start Date of today, it does not have a target start of when the PM was next due or any extension date it had.

Thank you for watching

I hope you have enjoyed this video on Time-Based Preventive Maintenance, I hope you found it useful, and thank you for watching. We would like to see you back in our next episode when we will review meter-based Preventive Maintenance as well as PM Hierarchies. Don’t forget to hit the Subscribe button, and if you enjoyed this video, please give it a thumbs up.

The music is called Drag Race from the group called TrackTribe, do check them out on track tribe .com, all one word (tracktribe.com). 

Until another time, Goodbye.