LUBE-IT and CMMS Key Differences
LUBE-IT
CMMS
HIGH LEVEL ARCHITECTURE
Department by Department Hierarchical Structural View
Yes
Yes
Machine to Sub-Component Hierarchical Structural View
Yes
Yes
Sub-Component Care Requirement Hierarchical View
Yes
No
Ability to Use Tablets to Manage Work Orders (Routes related to weekly lubrication actions)
Yes
Yes
Ability to Assign Work Order Numbers for Labor Tracking Purposes
Yes
Yes
LUBRICATION PROGRAM SPECIFIC
Data Field for Each Sub-component Requiring Lubrication Care
Data Field
Text Field
Number of Locations Where a Lubricant Would be Placed
Data Field
Text Field
Lubricant Name
Data Field
Text Field
Lubricant Attributes (Viscosity at 40, 100°C)
Data Field
Text Field
Lubricant Volume (Sump Capacity, or Replenish Units)
Data Field
Text Field
Lubricant Consumption Tracking and Reporting
Yes
No
Lubricant Cost Tracking and Reporting by Route, by Employee, or by Machine
Yes
No
Definable Units of Volume Measurement (Ounces, Grams, Gallons, etc.)
Data Field
Text Field
Definable Type of Service Function (Clean, Regrease, Flush/Fill, Top-Up, etc.)
Data Field
Text Field
Definable Frequency of Service Function at the Component Level
Data Field
Text Field
Individual Scheduling of Task-Based Service Functions
Yes
No
Individual Completion Tracking of Task-Based Service Functions
Yes
No
Definable (Reasons We Skipped the Task) Function
Yes
No
Means to Track Reasons for Missed Tasks, by Each Scheduled Task
Yes
No
Auto-reschedule of Incomplete Task-Based Service Functions
Yes
No
Ability to Assign Criticality to an Asset
Yes
Yes
Ability to Prioritize Tasks based on Asset Criticality
Yes
No
Ability to Look Ahead at Future Route Schedules to Identify Labor Requirements
Yes
No
Ability to Rapidly Extract Future Outage Tasks from Existing Work Plans for Instant Access
Yes
No
Ability to Measure Labor for Any Given Week's Routes Based on Time Allocations Per Task
Yes
No
Ability to Generate and Track Completion of Thousands of Weekly Individual Tasks
Yes
No
Barcode/RFID Task Completion Tracking by Time of Day
Yes
No
Lubrication Engineering Calculations for Validating Lubricant is Appropriate for a Set of Component Conditions
Data Field
No
Lubrication Engineering Calculations for Selecting an Environment-Appropriate Service Frequency
Data Field
No
Lubrication Engineering Calculations for Adjusting Service Frequencies with Changes in Operating Conditions
Data Field
No
REPORT GENERATION
Phone App for use Identifying Which Lubricant is Used in a Given Machine Component
Yes
No
Complete List of All Lubricated Machine Parts by OEM
Yes
No
Complete List of All Lubricated Machine Parts by Lubricant In Use
Yes
No
Complete List of All Lubricated Machine Parts by Service Frequency
Yes
No
Complete List of All Lubricated Machine Parts by Technician Responsible for the Machine
Yes
No
Complete History of All Task Completion, Including the Number of Days that Tasks were Over-Due
Yes
No
History of Reasons for Why a Technician Failed to Complete Tasks (via configurable list, or notes)
Yes
No
Auto-Reporting of Scheduled and Completed Tasks
Yes
No
Auto-Reporting of Lubricant Consumed by Type or Machine
Yes
No
Auto-Reporting of Lubricant Cost by Type or Machine
Yes
No
Auto-Reporting of Labor Consumed by Route, Person, or Machine
Yes
No
Auto Reporting of Any Element of Lubrication Task Completion from Weekly Work Management
Yes
No