LEANTrak is a "multimeter for production performance" that can be configured in minutes without installation, wiring, programming, infrastructure changes, or production disruption to capture real-time production time and rate losses while selectively involving the line operators.

LEANTrak is built on TrakSYS technology but with a simplified configuration front-end that allows non-technical staff to participate in the configuration. If you are serious considering investing in a leading performance monitoring solution we urge you to consider a free TrakSYS pilot today. Pilot duration is normally a 2day period on a single line and picking the problem line is highly recommended. Following a trial we and our partner will discuss the result based on the information captured and our experience on your plant floor. You will see the OEE fluctuations, performance and availabilty losses and what the top reasons for losses on the line were.

Valuable knowledge of how production line performance can be increased using the existing equipment is gained within the first few hours. We believe in the "Try before Buying" approach so decision makers can be confident that the solution will work for your business. In every case production teams are excited about the results and the visibility of what is actually happening on the plant floor.

 

The response from operators is often surprising to production management; without exception they are willing to participate and assist in accurately capturing the reasons for downtime. For many paper solutions this level of operator involvement is still a major challenge.

It our expereience 10 to 40% of time lost is due to short stops which occur for less than 5 minutes and are not typically captured on paper. Lines that on paper are reporting an availability of 90% have been measured an average of 40% to 50% when using accurate, real-time monitoring that includes shots stops and other delays not previously captured. With LEANTrak the impact of short stops can more clearly be understand and which short stops to focus on in order to get the most impact. It's not possible to improve performance unless you have accurate current and historical visibility of the problem. Many manufacturers are understandably hesitant to put new solutions in place for fear they will add to the complexities inherent in the manufacturing process but seeing the results leaves no doubt.

Email This e-mail address is being protected from spambots. You need JavaScript enabled to view it to request an “Example LEANTrak Report” we have a number of manufacturing vertical examples. Trials have been done locally but the company name and details will not be divulged without their written permission.

 

Screenshots showing TrakSYS used for Real-time Performance Management (South African examples)	(Click to view)
This dashboard shows an overview of production KPI for a selected production period. The grey slice of the pie chart indicates the portion of time lost where line is being run under target performance rate. The Pareto highlights top losses and reasons; users can drill down for further information.
Using this dashboard a user can determine at what speed the production line is being run and what percentage of time the line / machine spends at each production rate. This together with the event chart and the trend can help us understand the relationship between downtime and the rate of the line. For example running a line faster line can result in bottles falling and as a result the whole line typically performances better at a slower rate.
A Pareto quickly highlights the losses having the largest impact on a machine or production line. This dashboard shows events by downtime reason, another view will show the events by system highlighting the machine where most losses are occuring.
Other than the dashboards, TrakSYS provides a number of standard reports based on MS Reporting services. These reports allow users to custom generate analytical views on the information captured. This helps answer questions like; What is the impact of different shifts, products, teams, etc. on the line performance? What are the details relating to a sequence of events resulting in lost production?

---