Condition Based Maintenance (CBM)

Conditioned based maintenance (CBM) is an OPC DA client service that connects to your Building Management System (BMS) for real-time equipment monitoring. This system can be simple to implement at your facility. It can provide several benefits with your maintenance plans for critical assets, enhanced alerts, work orders, instruction, integrate with your CMMS system, etc.

For more information email us at support@kinemics.com.

Go to your account

Item 1 of 24

Details

Connect to any BMS System or a stand alone OPC Server. Create maintenance rules and applied them as physical values changed. The basis of this application is simple. You create a plan for your system, each plan can monitor 5 tags and each plan can have multiple rules that can be implemented to generate predictive maintenance, compliance maintenance, alerts, work order, etc. The system can also command values to other tags registered within the application to control equipments based on actual system condition.

Integration

It can be easily integrated with any CMMS System on the market or just manage from its own dashboard.

Sample of a quick integration flow diagram

OPC UA suppor coming soon...

Predictive/Proactive Maintenance

Using an operating room as an example on controlling or monitoring humidity. Create a plan that can warn you that the operating room that's active the humidity is going up or dropping. Basically, you will monitor the humidity tag, setpoint tag, reheat tag, and CFM tag. With these tags as parameters, you can generate a successful plan.

Basic KPI tracked for you

The system is designed to track several KPIs to help you manage your system and your business with risk-based approach. Knowing when or how your system is performing over the years can help you make capital decisions for a better ROI.

System MTBF (Meantime Between Failure)
System MTTR (Meantime to Repair)
Tag ROC (Rate of Change of value against its setpoint)
Tag Slope (How fast is the value changing against time.)
And more.

Most CMMS systems and BMS systems don't provide this level of details. It is always left to the owner to do these calculations from a spreadsheet or hire several staff to perform this task.

Rule Logic for Humidity Control

Hum_High = (Humidity > setpoint) && (ReheatVlvPos < 10%) && (TempSetP < 65F);

Hum_Low = (Humidity < setpoint) && (ReheatPos > 25%) && (TempSetP > 70F);

Where setpoint is either the low limit or the high limit. To enhanced the above logic, you can add the outside temperature tag for summer/winter mode. This way, the system can decide which rule to apply.

For example:
Hum_High = (Humidity > setpoint) && (ReheatVlvPos < 10%) && (TempSetP < 65F) && (OutsideTemp > 55);

Sample Rule for Belt Inspection

Change_Belt = (FanStatic < 3.5) && (FanTorque < 60%) && (FanCmd > 95%)

Of course, before rules are implemented we need to know what are the best operating parameters for the equipment. Then we need to select when do we need to start alerting or sending our warning before actual failures occur. The customer will set the parameters before implementation. Premature failures are also recorded for future forecast calculation. Forecasting is not avaialble until 1st or 2nd year of data collection. Unless the customer has accurate data that we can analyze prior to incorporate in our system.

All maintenance plan are executed at a set interval set by the owner, for critical assets, the interval may be less than those non-critical. Activation proof timers are also set per plan basis to remove all possible noise to esnure the actual condition is filtered. However, this proof time would need to be monitor at first to ensure that the filtering effect does not mask the actual condition.

Auto Acknowledge use it to have the system acknowledge the event when it comes back to normal. Using this feature your system will reset itself allowing to track the actual repair time to improve the acurracy of the MTTR.

Visualize our Process

Maintenance Event Generators

Runtime
Condition comparison
Rate of change
Percent deviation
MTTF value
MTBF value
Reliability value
Availability value
Failure rate value
Expected failure rate (based on MTBF trend)

Reporting

Generate report that shows your team success on acknowledging activations, review equipment trends, meantime between failures, failures per quarter, and time series analysis to early forecasting.

Email Alerts and Customers Notifications

Don't you hate when you get an alarm when a system failed and then you have to first notify everyone affected before you run to take care the issue? Well, we know this very well... Being in the industry for so long, we have added a customer message specifically designed to email you the alert and the customer the notification. This allow you and your team to focus on the issue. With a built-in address book, it is easy to create groups to setup alert and notifications

System Activity Alerts

How many of you run reports and see, OMG where's the data or OMG this thing flat lined since last month... These types of behaviors are common and happens constantly, unfortunately you see them when you run a report or when you have someone dedicated to look for these things. I always say that if I'm reading it, most likely I'm already late... Our system is designed to alert you when anomalies like this occur.

These are some of the benefits

Alert users when sensors or tag data has not changed for 2 hours (boolean type is not processed)
Alert users when sensors or tag data have a bad quality
Alert users when sensors or tag is near its calibration date
Alert users when equipment is off for x hours to determined if its down for a reason or maintenance.
And more...

Allow for users to write values to the system

The system is designed to be flexible and allow users to expand their ideas to make their organization better without the need of hiring multiple vendors to create a single system.

Allow user(s) to write value to specific tags
This is ideal to allow patients and caregivers to change their room temperature when they need to and get confirmation after the change is applied. Able to have other systems connect to the system database and pull information about their rooms or system. i.e. query room temperature and display it in their patient monitor or hospital patient mobile device. How about when a VAV is controlling two or four rooms, no problem.
The system knows how many rooms are controlled by the system and basically splits the difference. If the command issued was to lower to 65 from 70, the system will split the difference and writes 70-65= 5, 5/2=2.5, 70-2.5= 67.5. So 67.5 will be written not the 65. A message is can be shown to the user or patient on how the change was managed. The same way when more rooms are involved. i.e using the same value as above and four rooms, 5/4=1.25, 70-1.25=68.8. and so on...
The posibiities are endless, what would you do??

Virtualization

Create virtual tags
Create virtual tags to create new tags. i.e. a virtual tag can take values from other tags to create a new value. This is ideal when you need to use system tags to create values such as Kwh, GPM, CFM, etc.
Supports expression with system functions and mathematics
Access other tags