Q&A With Aaron.

Introduction:

In the latest instalment of our “A Day in the Life” series, we sit down with Aaron, a highly experienced Level 4 Technician at Morris Vermaport. Aaron specialises in diagnosing and resolving complex lift faults—often stepping in when others have tried and failed. In this in-depth Q&A, Aaron shares the technical thought processes, tools, and experiences that shape his day-to-day role and offers valuable insights for both aspiring and established engineers in the lift industry.

Q&A With Aaron – Senior Lift Technician, Morris Vermaport

1. When you’re called to a site where others have already attempted a fix, what’s your first move?
The first step is always to start with the basics, reviewing the job report, checking the fault log, confirming safety circuits, and ensuring the fundamentals are sound before diving deeper. As a Level 4 technician, I’m often called in after others have been unable to resolve the issue, and occasionally faults are unintentionally introduced during earlier attempts. That said, sometimes a methodical reset and sequence check is all it takes to get the lift operational again.

2. What’s the strangest fault callout you’ve experienced?
The most memorable, and messiest, involved a through-car hydraulic lift needing door shoe replacements on both sides. While manually raising the cabin with a hand pump, the ram seal failed explosively. We later found that only one of the two required seals had been installed originally. As pressure built, it was only a matter of time before failure. The lift collapsed, and we were left ankle-deep in hydraulic oil.

3. Can you share an example of a particularly complex fault you resolved?
A previous engineer misdiagnosed a drive failure. A subcontractor installed a new drive but couldn’t configure it correctly. When I was brought in, I traced the issue to a fault with the encoder offset via the movement control board. Replacing the board didn’t solve it, which pointed back to the drive. Although hesitant to blame the new part, replacing it a second time resolved the issue instantly. A valuable lesson: new parts can still be faulty, trust your diagnosis.

4. What tools or software do you rely on most when fault-finding?
My go-to tool is the multimeter, it’s absolutely essential. After that, it’s the manufacturer-specific software and diagnostic interfaces that allow me to retrieve error codes and interrogate system logic across different panels and drives.

5. What are the most common mistakes made in early-stage fault assessments?
The biggest issue is self-doubt. Engineers often have the capability but second-guess themselves. Many faults can be resolved over the phone with the right mindset and information. Also, some engineers stop just short of the root cause; taking the diagnostic process a step or two further could save a return visit.

6. How do you balance hands-on work with supporting other engineers?
It depends on who’s calling. If an engineer genuinely wants to learn, I’ll often send technical manuals from my shared Dropbox. I also take calls on the road when possible. However, if I’m already on-site and deep into a job, I have to prioritise that. I always follow up when I can, it’s about balance and availability.

7. What’s the most technically demanding system you’ve worked on?
I wouldn’t say any system is more difficult than another, it’s all about familiarity. Once you’ve worked regularly on Orona, Otis, or Schindler systems, for example, they become straightforward. It’s not about complexity, just exposure.

8. How do you keep your knowledge current in such a fast-evolving field?
Networking is key. I stay in touch with a wide circle of highly skilled engineers across the country. If we’re working in the same area, we’ll meet up, exchange insights, and sometimes troubleshoot together. OEM techs from Otis, KONE, and Schindler are a great resource, especially for new systems. In this industry, you’re only as good as your phonebook.

9. What role do senior technicians play in developing future engineers?
Our role is to pass on experience, resources, and confidence. Whether it’s sending wiring diagrams or explaining logic sequences, we’re there to help build knowledge and reduce trial-and-error. If we invest time in sharing what we know, the whole industry benefits.

10. Walk us through a typical day in your role.
It usually starts with a few calls during the drive to site—helping others where I can. I’ll check in with the office for updates or collect parts, although they’re often sent directly to site. Once on-site, I’ll speak with the client to provide a clear update, resolve the issue if possible, and send a full report to the office. Then it’s straight on to the next job—every day is different.

11. What do you enjoy most about working at Morris Vermaport?
What sets MV apart is that the operations team is made up of former engineers—they get it. When I send a detailed report, they understand the context straight away. I also love the variety, different locations, panels, and environments. One day I’m in Stratford and Reading, the next in High Wycombe or even Wales. I rack up over 1,500 miles a week, but I wouldn’t trade it for anything else.

Conclusion:

Aaron exemplifies what it means to be a high-level lift technician: methodical, technically sharp, and always willing to support others in the field. His approach to diagnostics, mentoring, and continuous learning underscores the vital role experienced engineers play in keeping the lift industry safe, efficient, and moving forward.

Follow us to stay tuned for more real-world insights from the MV Lifts team in our Day in the Life series