Preventive Maintenance

Calendar Based Maintenance Schedules (CBMS).

You can create Daily, Weekly, Monthly, Yearly repeating maintenance schedules for your assets.

Form for Calendar Based Maintenance Schedule.

Here is a brief overview of each of the components of the CBMS. Refer to the number in the image above and read the explanation below.

1. New Work Order

Some times you might want the next work order to be generated only after the current one is closed. To do that you just need to toggle this switch.

2. High Risk

This is a flag you can use to indicate a work order that involves high risk - like when doing electrical work. A skull-and-crossbones ☠ icon appears in red beside a high risk work order.

3. Frequency

This is the number of Days/Weeks/Months/Years you want the next work order to be repeated. This is usually set as ‘ 1 ‘.

Examples ....

• 2 - Day : A work order is generated once every two days.

• 1 - Week : A work order is generated once every week.

• 6 - Month : A work order is generated once every six months.

How many future work orders are generated?

Depending on the maintenance schedule frequency (Day/Week/Month/Year), work orders are generated only upto a certain number of days into the future. This is by design so as not to overwhelm your calendar.

To illustrate, if you set a daily maintenance schedule from 1-Jan-2025 to 31-Jan-2025 (i.e. for 31 days), the initial set of work orders are created 14 days in to the future (i.e. from 1-Jan-2025 to 14-Jan-2025). Thereafter one new work order is created every day till the end date.

The below table illustrates further.

Maintenance Schedule Frequency	Work Orders are generated for next ....
Daily	14 Days
Weekly	28 Days
Monthly	90 Days
Yearly	365 Days

4. Title & Description

A short and long description about the work order.

5. Checklist

A Checklist is a collection of 'TO DO' items that need to be ticked off before a work order can be closed. You can attach one or more Checklists to a Calendar Based Maintenance Schedule. Just select an existing Checklist from the dropdown or click ➕ to create a new Checklist.

6. Assigned To

Teams members to who this work order will be assigned. These team members will receive email and push notifications whenever this work order is updated.

7. Priority

Choose between Normal or Urgent. If left blank a Normal priority is assigned.

8. Start Date

The date on which the first work order is generated.

9. End Date

The date after which no work orders will be generated. If you leave this blank, work orders will be generated forever.

NOTE: When you edit an existing Calendar Based Maintenance Schedule, the changes will reflect only in future work orders generated. Work orders already generated will not be affected. You can however edit individual work orders from the 'Work Order' module.

Event Based Maintenance Schedules (EBMS).

You can generate work orders when certain event conditions are met. Like when temperature exceeds 200°C or when a vehicle completes every 10000 kilometers, and so on.

EBMS requires integration of your IOT/Sensor/SCADA systems with the SuperCMMS API. You use this API to push data from your systems to SuperCMMS Data-Warehouse. SuperCMMS scans this data in near-real-time and generates work orders when pre-defined event conditions are met.

NOTE: Event based maintenance schedules are part of the paid plans.

Here is a brief overview of the components of EBMS. Refer to the number in the image above and read the explanation below.

1. Field

The 'Field' is an attribute of an asset/sub-asset/part that needs to be monitored. For example, if you have 'Boiler' as an asset, you can create a custom filed called 'Temperature'. You can continuously stream this temperature data to SuperCMMS data warehouse using the API.

2. Operator

This is the mathematical action (condition) that is applied to data associated with the 'Field'. The following operators are available.

• > Greater than

• >= Greater than or equal to

• < Less than

• <= Less than or equal to

• = Equal to

• != Not equal to

• %↑ percent increase

• %↓ percent decrease

• ↑ increases from previous value by

• ↓ decreases from previous value by

• ↑ counter value increases by

• ↓ counter value decreases by

Lets say you want to monitor if 'Boiler Temperature' meets or exceeds a certain value. You select the operator '>= Greater than or equal to'.

Continuing our example it's going to be --- Boiler : Temperature : >= Greater than or equal to

Asset	Field	Operator	Value
Boiler	Temperature	>= Greater than or equal to

3. Value

This is the numerical value that needs to be met for a work order to be generated.

Continuing our example it is now --- Boiler : Temperature : >= Greater than or equal to : 200°C

Asset	Field	Operator	Value
Boiler	Temperature	>= Greater than or equal to	200°C

4. Title

The title of the work order.

5. Description

A description of the work order. Descriptions are automatically generated EBMS.

6. Checklist

Select a checklist that needs to be attached to the work order.

7. Assigned to

Select a team member to whom the work order needs to be assigned.

8. Priority

Select 'Urgent' or 'Normal'.

IMPORTANT: Only one work order is generated when a condition is met. Subsequent work order is generated only after the current work order is closed.

Special Event Cases: Odometer / Meter / Counter

Let's consider the following cases ...

• a vehicle that need to be serviced every 10000 kilometers

• a bearing that needs to be greased after every 100000 rotations

In all such cases you must select the Operator "↑ increases from previous value by". EBMS remembers the last reading at which a work order was generated and generates the next work order whenever the Odometer / Meter / Counter value increments by your predefined value.