Predictive Maintenance

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.

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 or Sub-Asset or Part that needs to be monitored.

For example, if you have 'Boiler' as an asset, you can create a custom field called 'Temperature'. You can continuously stream temperature data to SuperCMMS data warehouse using the API.

Asset
Field
Operator
Value

Boiler

Temperature

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'.

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.

Last updated

Was this helpful?