Creating a PM Schedule

Modified on Mon, Sep 16 at 3:16 PM

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.


The first steps of adding the schedule are the same no matter what type of job you have.


  1. From the left sidebar, select Maintenance, then Preventive Maintenance, then Search.
  2. Select the ID of the job you would like to add a schedule to.
  3. Select + Add Schedule if there is no existing schedule. If there is, select ... under "Action" and select Add.
  4. 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. 
  5. Select Save.



Calendar Schedule


FieldDescription
Charge ToAsset you would like to charge the job to.
Charge To NameAsset's name. Will fill out automatically based on the ID selected above.
Schedule MethodWhether you would like to schedule the job based on when it was last due or last performed.
Frequency TypeThe unit of measurement you would like to count frequency in. Days or months.
Perform EveryValue that determines how often you would like the job. Unit depends on frequency type above.
Next Due DateWhen the job is next due, so SOMAX knows when to "start" the calendar.
Calendar SlackThe 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 RequiredWhen this is Checked the Asset must be Down for the work to be completed
Work Order DefaultsInformation about the work, such as the preferred shift, priority, failure and action codes, and more.


Meter Schedule


FieldDescription
Charge ToAsset you would like to charge the job to.
Charge To NameAsset's name. Will fill out automatically based on the ID selected above.
Meter IDMeter you would like to use the readings from.
Meter IntervalValue that the next meter reading must reach or exceed in order to trigger the PM into a work order.
Meter Last DueThe last meter reading when the system generated a work order for the meter.
Calendar SlackThe number of days after the job is due that the maintenance personnel have, as leeway, to complete the job.
Down RequiredWhen this is Checked the Asset must be Down for the work to be completed
Work Order DefaultsInformation about the work, such as the preferred shift, priority, failure and action codes, and more.


On Demand Schedule


FieldDescription
Charge ToAsset you would like to charge the job to.
Charge To NameAsset's name. Will fill out automatically based on the ID selected above.
On Demand GroupUser defined group responsible for the maintenance. See About PM On Demand Groups. Ex: Fall outage, Spring clean up
Down RequiredWhen this is Checked the Asset must be Down for the work to be completed
Work Order DefaultsInformation 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

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article