Jeppesen logo The Jeppesen project personifies what we mean when we say “Nuxeo EP scales up, but it also scales lean and skinny.”

I had a chat about this with John Sims, Systems Architect at Jeppesen. Jeppesen is a Boeing subsidiary, involved in infrastructure to transmit navigation data to various end devices.

The Interview

Tell me about your project.

Basically it involves the evolution of a system to provide remote delivery of a database and content to end devices. The previous solution was coded in house.

The problems we are trying to solve are the same as those addressed by a content management system. We use Nuxeo EP to componentize our development so we can get out of the business of writing infrastructure code.

What Nuxeo products or components do you use?

We use Nuxeo EP for workflow, content management services, and notifications.

We plan to start using Nuxeo Studio, specifically for defining operations and automation chains in Nuxeo EP 5.3.2.

What type of solution were you looking for?

When we kicked off the project a couple of years ago, we wanted a content management system that was modular and flexible, based on industry standards, and priced right.

We wanted a master repository on the ground, and a slave repository on the end device that would be synchronizing to the master.

We needed a content management system that scales down as well as up.

Why did you choose the Nuxeo Enterprise Platform to build your application?

Nuxeo was the only company that readily grasped what we were trying to do. Eric (Barroca, Nuxeo CEO) understood the problem we were trying to solve, and told us that Nuxeo had a similar project already.

All of the other vendors talked about supporting a massive repository. They didn't get what we wanted.

Nuxeo EP scales down because of its modular architecture, and this is what we needed. The client software for our system must have a small footprint, because the end devices are not very powerful.

-- @JaneZupan