Aerospace · Program Leadership

Automating engine data uploads

Honeywell's engine data app set out to replace laptop downloads with automated cloud uploads for business jet maintainers. I led the program as technical product owner, directing the work of design, research, engineering and QA without managing the people.

My role
Technical Product Owner (directed the work; did not manage the people)
Timeline
Early 2019 to March 2020
Team
9 people: 6 core plus shared research, QA and data architecture
Budget
Managed to $1.3M, mostly staffing
  • 30–60 min → 1–10 min Engine data download became an automatic upload (self-timed by alpha maintainers)
  • 4 site visits To customer hangars, with engineering or QA whenever I could get them a slot
  • 5 customers Challenger 300 customers in alpha
The legacy e-Engine Interface chronology tab: a dense table of engine records with no visual separation between flights.
Before: the legacy chronology tab. Records ran together with no break between flights, making it hard to see a fault code recurring across multiple flights.
The redesigned Engine Data Viewer chronology screen, with records grouped by flight and subtle separation between each flight, plus added columns for altitude, ITT and fan speed.
After: the redesigned chronology view. A subtle separator marks each flight. Design mockup with placeholder data.

The problem

Maintainers spent 30 minutes to an hour sitting with each aircraft for manual engine downloads, and a competitor had already automated it.

This program covered software for Honeywell's HTF7000 and TFE731 engine families, which power business jets. To diagnose engine health, maintainers had to connect a laptop to each aircraft and download data one engine at a time, in hangars that could be freezing in winter and sweltering in summer.

The old download, step by step

  1. 1Carry a Windows 7 laptop and a kit of cables aboard
  2. 2Connect to ports inside the aircraft
  3. 3Download one engine at a time and stay with the aircraft for 30 minutes to an hour
  4. 4Move the data by USB stick and email

The tool ran only on Windows 7 laptops that were hard to get IT teams to support, and the laptop and cables had to be carried aboard, adding weight and taking cargo space on a small business jet.

A file could corrupt without the user finding out until the end of the process, and one user said a channel would not download about 1 in 3 times. A competitor had already moved to automated capture, and maintainers knew it.

"Requiring manual connection for engine downloads is obsolete."
A maintainer, early in our research

My role and the team

I led a nine-person program without managing anyone on it, while a designer and a researcher led their own disciplines.

I was responsible for getting the team access to customers, cross-functional alignment and delivery. I also managed to the $1.3M program budget. A dedicated designer led UX design and a researcher led the research. The researcher wrote the test scripts and ran the tests. I reviewed the designer's work and the researcher's test scripts, sat in on sessions with field service engineers, helped shape the research and assisted with the testing.

Three constraints shaped the work

  • Two groups in two cities: the hardware group in Phoenix and our software group in Atlanta

  • A highly regulated industry, where security concerns shaped the connection choice

  • A team that built machines, not software, so working in agile was new to many of them

Getting close to the problem

Getting engineers and QA into customer hangars, not just design and research, changed the decisions the team made.

Before we designed anything, we started internally with Honeywell's own field service engineers, learning the product and the domain so that customer time went to real questions. Then I partnered with our business contact at the Honeywell engines facility, who identified corporate jet fleet maintainers in the Atlanta area willing to talk with us.

I pushed to get engineers and QA into customer environments, which was not standard practice for this team. We made 4 customer site visits with a rotating team of 3 to 4 people, always UX design and research, plus engineering or QA whenever I could get them a slot. I also arranged a tour of Honeywell's engine manufacturing facility, which gave the team a feel for how many systems had to work together.

When the people building the software have watched a maintainer struggle in a cramped hangar, they make different decisions.

What we saw

Maintainers' main concern was fast access to fault codes and exceedance data. We saw downloads that could fail silently, constant monitoring of the connection and a work environment where maintainers moved between aircraft with phones and tablets and juggled several manufacturers' diagnostic tools.

Turning field findings into design

Two customer types used the product two ways, so we arranged the tabs to suit both and built the chronology screen from what maintainers asked for.

We visited two kinds of customer.

  • Corporate maintenance teams

    Used the application for basic diagnostics and to flag deeper issues.

  • A maintenance repair organization, or MRO

    Did far deeper diagnostics and relied on a different set of screens entirely.

The designer arranged the tabs around those two patterns. The first tabs were the ones corporate maintainers reached for in routine work, and the deeper-dive tabs came after, where the MRO would live.

A screen shaped by what maintainers asked for: the chronology view

The chronology screen shows everything that happened with an engine from takeoff to landing. On the legacy system it was a dense, undifferentiated list, and at a glance you could not tell where one flight ended and the next began. Maintainers told us they were bouncing between tabs to assemble a full picture and wanted the key data on this one screen. The designer worked to exactly that, and I worked with the designer and the data architect to make sure the database was structured so the screen could show it.

The redesigned Engine Data Viewer chronology screen, with records grouped by flight and subtle separation between each flight, plus added columns for altitude, ITT and fan speed.
The redesigned chronology view. Design mockup with placeholder data.
  • Flight separator

    A subtle visual separator between flight legs, so recurring fault codes became easy to pick out. In testing, maintainers singled it out as something they valued.

  • ITT and fan speed

    More granular insight at the moment of a fault.

  • MCID descriptions

    Shown alongside the fault codes to speed up troubleshooting.

  • Altitude

    Tells ground-related issues apart from airborne ones.

Before anything was built, we tested the designs with both customer types, because they used the product so differently.

What we built

Maintainers got a phone alert when an upload finished and could review engine health from anywhere, not just in the hangar.

The engines hardware team built a unit that sat on the aircraft, with a Wi-Fi radio and a Bluetooth radio, and we built the software around it. The unit was designed to replace the cables: when it attached to a Wi-Fi network it had credentials for, it started uploading engine data to the cloud on its own.

The Bluetooth mobile app configured the unit, including its Wi-Fi credentials, and gave maintainers a quick health check, flagging issues that needed further investigation. It also pushed the status of each upload to the maintainer, who could restart a failed upload or check the results of a successful one. The web application gave a deeper dive into the data.

The new upload, step by step

  1. 1After landing, the unit attaches to a Wi-Fi network it has credentials for
  2. 2Engine data uploads to the cloud on its own
  3. 3The maintainer gets a phone notification and can review engine health from anywhere

Leading the build across two sites

I kept a two-site program aligned through weekly cadence and logistics.

Keeping two cities aligned was a steady part of the job. I ran a weekly call with the engines team's leadership and filed a weekly program update, and people traveled in both directions. The engineers had sample units in Phoenix that we needed to test the software against, and on one of my trips I brought units back so the team could keep working.

One challenge was cultural. Agile development (build something, test it, learn, iterate) was not intuitive for engineers accustomed to fully documenting a design before building anything physical, and shifting that mindset took ongoing work throughout the project.

The hardest technical question was how the mobile app should connect to the unit on the aircraft.

The connection decision

Reliability favored Wi-Fi

The signal had to pass through the aircraft's metal skin, and our lead engineer made the case that Wi-Fi would hold up better.

Security favored Bluetooth

In a highly regulated industry, the engines hardware team, who owned the unit and the connection decision, chose Bluetooth for the local connection and kept Wi-Fi for the cloud upload once data had left the aircraft.

My job

To make sure both sides understood the tradeoff, including the reliability risk, before the call was made. Once it was made, we built around Bluetooth.

The alpha and the outcome

In the alpha, a 30 to 60 minute manual download became an automatic upload of 1 to 10 minutes, with a phone alert when it finished.

We tested internally first, deploying the software to Honeywell test aircraft. Then I ran a limited alpha in January 2020 with 5 Challenger 300 corporate customers. The alpha used corporate customers rather than the MRO, because it was too basic to be a fair test of the MRO's deeper diagnostic work.

Time to get engine data off the aircraft

Old manual download, with the maintainer sitting with the aircraft30 to 60 min
New upload, larger batches (about twice a month)5 to 10 min
New upload, fewer than 10 flights of data1 to 2 min

Bars are drawn to the top of each range. These are self-timed numbers from alpha users, not a controlled measurement.

Handing off

  1. Early 2019Program starts
  2. January 2020Limited alpha with 5 Challenger 300 customers
  3. March 2020I hand the program to the intern product owner
  4. August 2020The Phoenix team takes over
  5. 2024Connected Engine Data Service launches

In March 2020, I moved into a management role and handed the program to a product owner intern I was supervising, who had onboarded during the alpha. He ran it day to day under my guidance until he left in August 2020, when the Phoenix team took over. All the in-field design and testing had happened while I was leading.

The program became the foundation for Honeywell's Connected Engine Data Service, which launched in 2024. I had long since moved on by then, so that is lineage, not an outcome I delivered.

What I learned

Put the builders in front of the users, and know which decisions are yours to make.

  • Get the builders to the users

    The engineers who visited customer sites made better decisions than the ones who had not.

  • Earn trust with expert users

    The maintainers wanted us to get it right as much as we did. That kind of relationship is built on trust, preparation and respect for their time.

  • Stay close after a handoff

    Delegating a live program to a junior person, and staying close enough to support him without taking it back, was its own kind of leadership, different from running it myself and in some ways harder.

  • Know which calls you own

    Leading without authority means knowing the difference between the decisions you make and the ones you can only influence, and making sure the tradeoffs are understood either way.