Preventive maintenance is a proactive type of maintenance that is designed to prevent equipment failures and enhance its efficiency and lifespan. By using a regular preventive maintenance schedule, you can minimize asset downtime (and decrease work order costs) as you work to prevent and better prepare for unexpected failures.
Some tasks of preventive maintenance include, but are not limited to, regular:
- inspections
- cleaning & recalibration
- repairs
- software updates
- replacements
- monitoring
You may add multiple schedules if you require a job with multiple triggers or if you require the same job to multiple assets.
This article describes how to create a PM Schedule within the SOMAX system.
Creating a PM Schedule
The type of schedule you can create depends on the type of PM Job you selected. There are three options - Calendar, Meter, and On Demand - and they focus on what you want to trigger the maintenance. For more help differentiating between them, see About Preventive Maintenance. Once you have created your PM Schedule see Assigning a PM Schedule Record.
The first steps of adding the schedule are the same no matter what type of job you have.
- From the left sidebar, select Maintenance, then Preventive Maintenance, then Search.
- Select the ID of the job you would like to add a schedule to.
- Select + Add Schedule if there is no existing schedule. If there is, select ... under "Action" and select Add.
- The different schedule form fields should appear. These will vary based on the type of job. Descriptions for the form fields for each type should be shown below.
- Select Save.
Calendar Schedule
Field | Description |
---|---|
Charge To | Asset you would like to charge the job to. |
Charge To Name | Asset's name. Will fill out automatically based on the ID selected above. |
Schedule Method | Whether you would like to schedule the job based on when it was last due or last performed. |
Frequency Type | The unit of measurement you would like to count frequency in. Days or months. |
Perform Every | Value that determines how often you would like the job. Unit depends on frequency type above. |
Next Due Date | When the job is next due, so SOMAX knows when to "start" the calendar. |
Calendar Slack | The number of days after the job scheduled date that the maintenance personnel have, as leeway, to complete the job.(Job must be done by) |
Down Required | When this is Checked the Asset must be Down for the work to be completed |
Work Order Defaults | Information about the work, such as the preferred shift, priority, failure and action codes, and more. |
Meter Schedule
Field | Description |
---|---|
Charge To | Asset you would like to charge the job to. |
Charge To Name | Asset's name. Will fill out automatically based on the ID selected above. |
Meter ID | Meter you would like to use the readings from. |
Meter Interval | Value that the next meter reading must reach or exceed in order to trigger the PM into a work order. |
Meter Last Due | The last meter reading when the system generated a work order for the meter. |
Calendar Slack | The number of days after the job is due that the maintenance personnel have, as leeway, to complete the job. |
Down Required | When this is Checked the Asset must be Down for the work to be completed |
Work Order Defaults | Information about the work, such as the preferred shift, priority, failure and action codes, and more. |
On Demand Schedule
Field | Description |
---|---|
Charge To | Asset you would like to charge the job to. |
Charge To Name | Asset's name. Will fill out automatically based on the ID selected above. |
On Demand Group | User defined group responsible for the maintenance. See About PM On Demand Groups. Ex: Fall outage, Spring clean up |
Down Required | When this is Checked the Asset must be Down for the work to be completed |
Work Order Defaults | Information about the work, such as the preferred shift, priority, failure and action codes, and more. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article