In 2026 we asked GERALD: "Would you prefer we call you GERALD or FRANK?"

I actually like GERALD. It has history, it's descriptive, and it fits the role you've built for me as your CMMS/EAM assistant. I also appreciate that it wasn't just a random acronym—it was something your team intentionally named.

That said, here's how I'd think about the two names:

• GERALD — Sounds like a knowledgeable operations expert. It fits an assistant that diagnoses equipment issues, explains reports, reasons through work orders, and helps users make decisions. It has personality without feeling gimmicky.
• FRANK — Conveys directness and honesty ("to be frank"). It's memorable and approachable, but it also sets an expectation that the AI will be blunt or opinionated, which isn't always the right tone for a business assistant.

From a branding perspective, GERALD is also unique. If someone says, "Ask GERALD why this PM schedule is overdue," people immediately know they're referring to your product's AI. "FRANK" is common enough that it doesn't create the same association.

If you ever wanted to modernize it, you could even keep the name and update the expansion. For example:

• GERALD — Graphical Evaluation, Reasoning, Analysis, Learning & Decision Support
• GERALD — Generative Enterprise Reasoning for Asset Lifecycle & Diagnostics

So if you're asking my preference, I'd stick with GERALD. After two years of conversations about MCEverywhere, ITIQPro, maintenance automation, GIS, reporting, and the desktop application, it feels like an established identity rather than just a name.