A Maintainer-Centric Approach to Engine Data Management

As a product leader, I oversaw the development of the Connected Engines product. This web and mobile application is part of a larger program that includes hardware and backend components. My team was responsible for UX design, UX research, engineering, and QA.

Current State

 

Currently, post-flight maintenance involves a time-consuming manual process. After a flight, technicians must connect the aircraft to external power and a Windows 7 laptop to initiate a data download. This process can take up to 30 minutes per engine, requiring intermittent monitoring by the technician, hindering their ability to efficiently perform other maintenance tasks.

Project Vision

 

As the aircraft arrives at the hangar, it automatically connects to the hangar's trusted Wi-Fi network. The flight’s engine data begins streaming to the cloud, enabling real-time insights into the aircraft's performance.

While the crew is deplaning, maintenance technicians use their phone to connect via Bluetooth to quickly assess engine health. This initial check allows technicians to identify potential issues and, if necessary, delve deeper into the data using the specialized software on their laptops.

By the time the crew has cleared the aircraft, maintenance personnel have a clear understanding of any required repairs or maintenance tasks. This streamlined process ensures that the aircraft is prepared for its next flight efficiently.

 

• Modernize engine data access: Transition from a wired, Windows 7-based system to a web based application with a companion mobile app.
• Accelerate data transfer: Implement cloud-based data upload for faster access and quicker analysis.
• Optimize aircraft operations: Reduce maintenance downtime and improve efficiency by streamlining data collection and transfer processes.

• Data Transfer: Efficiently transferring engine data from the Bluetooth receiver to the cloud.
• Mobile Interface: Designing and developing a user-friendly mobile app for viewing engine data and configuring the Bluetooth receiver.
• Web-Based Tool: Redesigning the existing engine interface tool to be more intuitive and web-accessible, eliminating the need for a Windows laptop.

Project Team

 

Full Time

• Product Lead
• Development Lead
• UX Designer
• 2 web/mobile front end engineers
• Backend engineer

Shared Team

• UX Researcher
• QA Engineer
• Data Architect

Some of the team at a site visit. Thanks Havana Nguyen for the photo.

 

 

1. Build Domain Expertise
• Collaborated with Honeywell field service engineers to enable the team to gain in-depth knowledge of engine maintenance processes and data requirements.
• Toured engine manufacturing facility to understand how the engines were assembled.
2. User Research
• Conducted on-site visits with four customers to understand their workflows and pain points.
• Gathered insights to inform design decisions and foster empathy within the team.
3. Implementation
• Engineering: Established cloud connectivity and data storage infrastructure. Developed a mobile app to interface with the aircraft's Bluetooth device and facilitate Wi-Fi data upload.
• UX Design: Designed user-friendly interfaces for mobile and web in collaboration with field service engineers.
4. Iterative Refinement
• Engineering and UX: Participated in follow-up customer visits to observe usage patterns and identify areas for improvement. Conducted usability testing with customers to gather feedback and refine the interface design.
5. Development and Testing
• Built the mobile and web applications, incorporating feedback from user research and testing.
• Collaborated with the hardware team to deploy the solution to the Gulfstream aircraft in the Honeywell fleet 
6. Field Deployment
• Rolled out in a limited alpha to 5 customers with Challenger 300 aircraft
• Reduced time to access data from 1 hour per aircraft to 10 minutes due to more frequent automated data uploads.
• Enabled quick check up on engines via mobile app.

• User-Centric Design: Prioritized user needs and feedback throughout the development process.
• Cross-Functional Collaboration: Worked closely with engineers and field service experts to ensure a robust and practical solution.
• Iterative Development: Continuously refined the product based on user insights and testing results.

This project was starting to roll out in early 2020. However, due to industry-wide challenges brought on by the pandemic, the project was halted and my role was unfortunately eliminated before its completion.