The On-Site Lube-Test module adds functionality to LUBE-IT that is of value to any organization performing on-premise testing or analysis of lubricants. This includes lubricant viability tests performed at the machine using test kits such as Kittiwake™ or handheld devices such as Ruler™ and OilCheck™ -- as well as on-premise bench analysis using a CSI™ or similar mini-lab.

Incorporating on-premise lube testing into the system means lube-test related tasks will receive the control and oversight of LUBE-IT. This includes the clear documentation of the work to be done, ultra-flexible routing, Planner-Less™ scheduling, automatic backlog management, along with detailed history for every lube point. This serves to ensure responsibilities for all lubrication testing tasks are clear and known, work is performed on-time and according to procedure, and both detailed status of individual tasks and management overviews are always right at hand.

The On-Site Lube-Test Advanced Feature extends LUBE-IT with the ability to:

• Document all on-premise lubrication testing tasks needing to be performed
• Define a follow-on task to perform (i.e., change the oil) when a lubricant fails its test
• Include these on-premise tests in existing Routes, or create new lube-test specific Routes
• Have LUBE-IT automatically schedule, track and manage these tests along with your other lube tasks
• Record "Pass / Fail" test results -- with the option to perform the follow-on task right-now
• Collect a "Result Comment" from the person performing the test
• View detailed history of all Lube-Tests performed at the individual lube-point level

For added efficiencies and productivity gains, this feature is best in conjunction with the Handheld Routes Advanced Feature. Full integration of these two features not only eliminates printing hassles and post-route data entry, it also enables Lube-Test specific actions right on the handheld unit. Integrated functionality includes:

• Check-out to Handheld of routes which include Lube-Test tasks
• Lube-Test tasks clearly displayed and identified on the handheld unit
• One-touch "Pass / Fail" results indication of Lube-Test tasks
• At-the-moment collection of the Results Comment
• Automatic display of the follow-on task, with full tracking if completed right-now
• Check-in from Handheld eliminates data-entry, including all automatic update of Lube-Test data

TIP: On-premise testing of lubricants is an excellent way to identify the lubricant change-outs required in advance of a shutdown. Because LUBE-IT automatically releases the follow-on task (i.e., change lube) for each failed test, as the shutdown approaches, there's no guessing as to the workload or lubricant products required.

NOTE: The Lube-Test Advanced Feature is not a replacement for used oil analysis software used to trend results of laboratory samples.

The Lube-Test Task Type

At the core of this Power Feature is an additional Task Type called "Lube-Test", which was created specifically for on-premise lubrication testing. In various places, LUBE-IT will respond with additional features when it encounters Lube-Test tasks. For example, when an Lube-Test task is marked as completed the Pass/Fail results feature is enabled.

Results Comments

Result Comments are collected for each Lube-Test task given a result of FAIL. These comments serve to provide additional information regarding the condition of the lubricant or the reason it was deemed to have failed. This is especially useful, if in the process of performing the test, the Lube Technician observes lubricant issues of interest (i.e., water in the lube, burnt smell, gritty texture, etc.).

Linked Tasks

Another feature enabled for Lube-Test tasks is the option of defining a linked task. Each Lube-Task task can be linked to one other task, which will become due if the Lube-Test task is given a result of FAIL. For example, a gearbox with a Lube-Test task done every 6 months could be linked to the gearbox's change task. Over time, when the gearbox's lubricant fails the Lube-Test, the linked change task will automatically become due. Another example might link a Lube-Test tasks to a Sample task so important condition monitoring information can be collected via used oil analysis at a laboratory.