Java Interface for Maintenance Record and OEE

During my tenure at Lear Corporation, my primary role was to sustain production equipment. This involved leading a team of qualified technicians, tracking maintenance events, and compiling key maintenance metrics such as MTTR, MTTB, and OEE at the end of each month to drive improvement initiatives.

Our daily operations were fairly standard—when a machine failed, various departments (production, quality, etc.) would call us in for repairs. Every failure caused downtime, which had to be assigned to a specific department and documented through printed work orders. At the end of each shift, these work orders were manually recorded —a tedious and time-consuming process.

To streamline this, I developed a Java-based interface that automated much of the data entry process. Operators only needed to focus on recording their actions, significantly reducing the time required for documentation to a quarter of what it used to be. More importantly, this structured the data automatically, allowing me to build a real-time tracking system for maintenance metrics, eliminating the need to compile them manually at the end of the month.

I expanded the system further by adding a searchable database of past interventions, enabling maintenance operators to quickly review previous solutions to recurring problems. This feature alone reduced intervention time by 10% overall.

This project was well received by management and even competed in internal Kaizen events. Implementing such solutions back then was not easy—AI wasn’t as accessible, and automation required extensive manual programming. Looking back, I can only imagine how much faster and more advanced the system could have been with the aid of AI and LLMs today.