Customer Spotlight: Ryan O’Neal on Upgrading RFgen Without Starting Over
For more than fifteen years, Ryan O’Neal, Senior IT Manager of Enterprise Systems in the aerospace and defense manufacturing industry, has worked with RFgen across multiple manufacturing environments. From his early implementation of version 3.2 to his recent decision to upgrade, Ryan brings the perspective of someone who has built, maintained, and evolved RFgen solutions firsthand. In this conversation, he shares what informed his decision to modernize and what the upgrade experience looked like in practice.
Experience & Evolution
Q: You’ve been working with RFgen for over 15 years. How did you first get started?
When I first implemented RFgen, we were operating in a paper-based shop floor environment and needed real-time inventory visibility. I deployed version 3.2 and spent more than 1,000 hours designing and refining the solution to match how our operations actually functioned.
It was a hands-on effort. We built workflows that reflected the reality of the business, eliminated paper transactions, and significantly improved inventory accuracy. Over time, the system became something I understood deeply and maintained with confidence.
Q: After building and maintaining RFgen environments yourself for years, what made you consider upgrading?
The decision wasn’t driven by dissatisfaction. The system worked. What changed was the platform itself. RFgen has evolved significantly over the years, particularly in terms of user experience and architecture.
As someone who had invested a lot of time building strong workflows, I approached the upgrade carefully. I wanted to ensure that any change would preserve the integrity of what had already been built while improving usability and long-term maintainability.
The Modern Interface and Workforce Impact
Q: What stood out to you when you experienced the modern interface?
The updated interface introduced cleaner layouts and more logical page transitions, which made a real difference on scan guns and smaller devices. Instead of compressing everything onto one screen, transactions could follow a structured flow that improved readability and reduced friction.
It also aligned better with the expectations of today’s workforce. Maintaining familiar workflows while improving usability helped reduce resistance to change and made onboarding more efficient for new employees.
“You want that modern look and feel from an adoption perspective. That’s what people are excited to learn and excited to use. The modern UI really helps with that.” — Ryan O’Neal
Partnering for a Strong Upgrade
Q: You’ve built RFgen environments yourself in the past. Why did you choose to work with RFgen’s professional services team for the upgrade?
Even with my experience, I recognized that the platform had matured. Leveraging RFgen’s best practices and current field experience made strategic sense. The goal was to establish a strong modern foundation and then maintain and extend it internally over time.
It was a structured process, and that reduced risk significantly.
“The project was well managed from start to finish. Deliverables were on time, and the solution worked as expected right out of the gate, with very little rework. It was genuinely impressive and renewed my confidence that it’s possible to have strong external professional services teams.” — Ryan O’Neal
Q: Many long-time customers worry that upgrading means rebuilding everything. What was your experience?
That was a fair concern going into the project. In practice, the transition was far more manageable than I initially anticipated. Applications were not rebuilt from scratch; they were adapted to take advantage of the updated framework. After an initial learning curve, the process gained momentum.
The upgrade extended what had already been built rather than replacing it.
“The getting started kit was a huge advantage. It saves a lot of time and money, and the quality is strong right out of the gate.” — Ryan O’Neal
Advice to Long-Time RFgen Customers
Q: What would you say to other long-time RFgen customers who feel hesitant about upgrading?
If you’ve invested years building your RFgen environment, that work doesn’t disappear with an upgrade. The core logic and workflows can remain intact if that is what you want. What improves is how those workflows are delivered and maintained.
For me, upgrading was about reinforcing the foundation, not undoing it. With the right approach, the transition can be structured, predictable, and aligned with the way your operations already function.
Conclusion
Ryan’s experience reflects what many long-time RFgen customers discover when they take a closer look at upgrading their long-standing solution: modernization does not require starting over. With a structured approach and the right support, it is possible to extend the foundation you built and position it for what comes next. If you are evaluating an upgrade, our team is ready to help you assess what that transition could look like in your environment.
