When a program needs senior technical judgment but not another permanent position, Caldridge can take on a focused assignment without adding another management layer.
The name Caldridge Partners connects where we started, what we've learned and how we approach technology challenges today.
CAL stands for Computer-Assisted Learning, a nod to the technology that helped inspire our original consulting practice in 1991. It was a time when computers were opening new possibilities for how people learned, worked and accessed information.
RIDGE represents perspective. From a ridge, you can see the broader landscape, understand how things connect and make better decisions about the path ahead. It's a fitting metaphor for our approach to technology strategy, enterprise architecture and modernization.
PARTNERS reflects how we do business. We work alongside our clients, bringing experience, independent judgment and practical solutions without adding unnecessary complexity.
Together, the name bridges more than three decades of technological change, from the early days of computer-assisted learning to today's advances in artificial intelligence, automation and enterprise modernization.
Caldridge Partners was established in 2026, carrying forward the experience and entrepreneurial spirit of a consulting practice that began in 1991.
The technology has changed dramatically. The purpose remains the same: helping people and organizations put technology to work in meaningful ways.
Before a government award
A credible technical approach starts with understanding the mission behind a requirement. Kenyon helps capture teams at federal primes with solution concepts, requirements, Statements of Work, teaming input and proposal sections. For FAA opportunities, his familiarity with the agency's Acquisition Management System helps when an RFP needs reading between the lines.
After a government award
Sometimes a delivery team needs senior judgment on one workstream, not another permanent position. Kenyon takes a defined role, such as an assessment, an architecture, an integration plan or technical reviews, and works inside your structure and reporting lines.
For companies and institutions
Commercial and institutional organizations face the same questions about aging systems, integration and where AI fits. Kenyon provides direct technology advisory work, from IT assessments like the one he did for the University of Oklahoma to ongoing AI and analytics support like Caldridge's work with Performance Dashboard.
Federal program experience
Experience across FAA technology programs
32 yearsSupporting FAA programs
The FAA runs one of the largest, most safety-critical technology operations in government. The problems Kenyon worked on there, including legacy systems, shared services, security mandates and governance across organizations, show up in every large agency and in many companies. His FAA work spanned enterprise technology strategy, NAS mission-support architecture and integration, modernization planning, technical governance and industry engagement. Based in Oklahoma City, home of the FAA's Mike Monroney Aeronautical Center, with extensive on-site FAA work in Washington, D.C., and at the William J. Hughes Technical Center in Atlantic City.
01Strategy and governance
At the FAA, technology decisions run through governance, standards and asset management. Kenyon worked where those meet, including governance for the SWIM Web Services Registry and work on the FAA STD 063 and STD 064 service standards.
02Mission-critical architecture
In the NAS, an interface failure has operational consequences. Kenyon's architecture work covered flight inspection, aeronautical data and airborne systems, along with Common Security Services infrastructure supporting HSPD-12 and enterprise security integration.
03Industry engagement
Knowing how a federal agency weighs its own priorities against what industry can offer helps any contractor frame an opportunity. Kenyon worked on the agency side of FAA industry engagement and, more recently, with FAA enterprise teams exploring early adoption of AI language models.
Success stories
Real technical challenges and how they were addressed
Large organizations, public or private, run into the same few problems: systems that don't talk to each other, security rules that move faster than the software, and old platforms nobody wants to touch. Here's how some of those got solved at the FAA.
01Flight operations and mission-critical systemsSupporting Flight Operations Through Mission-Critical System Modernization
Problem
FAA Flight Inspection Central Operations needed centralized scheduling and tracking of aircraft operations.
Challenge
Integrate aircraft scheduling, aeronautical databases, geodetic calculations and operational requirements into a dependable system.
Solution
Kenyon developed the system specifications, aeronautical relational databases, geodetic calculation scripts and scheduling interfaces, along with project, integration and test plans.
Outcome
The operational system supported the FAA’s initial Part 135 certification effort, received NAS mission-critical designation and remained in service beyond its originally planned 18-month life cycle.
02Security integration and modernizationModernizing Security While Preserving Existing Systems
Problem
Evolving security requirements were creating integration challenges for multiple ATO application teams.
Challenge
Improve shared security capabilities without forcing disruptive replacement of functioning systems or duplicating investment.
Solution
Kenyon advocated a leave-and-leverage architecture and, with a technical colleague, mentored project teams on applying Spring Security to isolate application-specific changes while strengthening integrated security.
Outcome
The approach gave teams a practical path to adapt existing applications to changing security needs while supporting system reuse and cost-conscious modernization.
03Enterprise architecture and information deliveryModernizing FAA Information Delivery Through Enterprise Architecture
Problem
FAA aviation information was maintained across separate organizational websites, complicating content management, integration and compliance with federal accessibility requirements.
Challenge
Bring together teams in Oklahoma City and Silver Spring around a common architecture, publishing process and Section 508 accessible information delivery.
Solution
Kenyon established and led the Public Web Initiative, developed the XML-based information architecture, coordinated the cross-organizational web team and established technical standards, integration plans and testing procedures.
Outcome
The integrated infrastructure was deployed successfully, separating content from presentation and enabling future website redesign work to be completed in hours rather than months.
04Enterprise service integrationLaying the Foundation for Enterprise Service Integration in the National Airspace System
Problem
FAA automation systems needed a more coordinated way to identify and integrate shared services across organizational boundaries.
Challenge
Establish an approach to registering and discovering services that could support wider adoption of Service-Oriented Architecture (SOA).
Solution
Kenyon helped initiate the NAS Web Services Registry effort by organizing stakeholders, defining technical direction and registration criteria, and coordinating with the FAA organization responsible for the NAS Federal Data Registry. He later served as technical architect for the ATO UDDI Web Services Registry and directed cross-agency registry collaboration.
Outcome
This work established early technical and governance foundations for enterprise service discovery and contributed to the FAA’s progression toward shared services and the later NAS Service Registry and Repository (NSRR).
05Process improvement and governanceEstablishing Consistent IT Processes Across the Air Traffic Organization
Problem
Newly formed ATO IT organizations needed consistent development, configuration management and governance practices.
Challenge
Establish repeatable processes and documentation to support organizational maturity and preparation for FAA iCMM Level 2 accreditation.
Solution
Kenyon helped develop and establish the Aviation System Standards Integrated System Methodology (AVNiSM), guided teams applying the Rational Unified Process (RUP), and led the iCMM Configuration Management Process Area implementation for ATO-W.
Outcome
The work strengthened formal process improvement practices and supported organizational readiness for maturity assessment. The FAA recognition narrative credits Kenyon with contributions to long-term process improvement and financial discipline.