• Flitestar For Macbook
• Flitestar For Macbook Air
• Flitestar For Macbook Pro
• Flitestar For Mac Os

We are excited to release our first online, interactive, self-paced training course, ePairing I. This course will introduce and guide you through concepts and best practices for production planning in Jeppesen Crew Pairing (JCP). Private Flying - Running JEPP Flitestar/Flitemap on a MAC. Hello Done my homework, searched PPRuNe archives on the subject but all. My 1998 model Flitestar opened part way and died. No motion, (remote or wall switch) no light, no hum, no safety beams, no nuthin. Acts like a dead circuit but the wall socket is good. Troubleshooting guide in the manual says replace the board (P/N 6080362). RORTOS calls itself maker of the most advanced flight sims for mobile, and they're pretty snazzy on the Mac too. More than thirty missions along with a half-dozen training missions and free flight so you can buzz around on your own with no agenda. $5.99 - Download now Heads up, virtual pilots — what'd I.

This portfolio is a summary of the products and projects myself and my team were responsible for designing, developing, deploying, and maintaining over the past from 2001-2015. The majority of these products have been developed under my leadership, however a few were launched previously and I was responsible for their maintenance.
These products have been developed by a very lean team, with total team sizes of between 4-15 people covering all the development functions/disciplines. These small, lean, agile teams accomplished so much because of the high caliber of people who are experts in their functional area yet able to contribute at a high level in other areas to fill all the roles needed on the development team.
My team was responsible for the product development (from concept, through development, launch, and ongoing improvement) for a large number of products, which will become clear by exploring this portfolio of projects and products. Many of these products are consumer (COTS) products that include supporting systems built by my teams. Those systems included installers, security, electronic application updates, data updating, weather delivery, and more.
I have written a page with some basic Aviation/Jeppesen terms and concepts that might help with some terminology. Although there are links included with most of the products, almost all of these products can be Googled to find even more information about them.p>

The messages I hope you to take from this portfolio are:

• I know how to lead the successful execution and delivery of software products and projects, and more importantly have demonstrated it repeatedly - which will be clear by exploring this portfolio.
• I have demonstrated the ability to establish and lead high caliber, cross-functional development teams - it's all about hiring extremely talented people and enabling them to do their job.
• I have a broad and deep set of experience in software development.
• My experience isn't just leading software engineering projects, it's leading product development - there is so much more involved in successfully designing, developing, delivering, and maintaining/enhancing a product than writing code.

Although I do have a significant depth and breadth of knowledge and experience in Aviation, across markets segments, domains, and with the data and the supporting systems that make these products possible, I believe my success is based on the knowledge and ability to execute in the discipline of software development not just the domain.

Summary of Products covered in this portfolio and were developed/maintained by my team:

Jeppesen and Aviation Background

Enroute Charts

Enroute Charts are the charts used to navigate from one airport to another. Think of them as a 'road map' with highways in the air. Pilots today still generally carry paper versions of Enroute charts. One of the core components you will read about in this portfolio is the Enroute Charting engine, which is a component of many of our applications. The Enroute charting engine provides an electronic display of these Enroute charts.

Terminal Charts

Terminal charts are the charts that defined the procedures for departing and arriving at airports. Airports have a number of defined approaches depending on runway, wind direction, etc. When you see pilots at the airport carrying around a brown leather case (between 40-50#), those are Jeppesen paper charts. Pilots are required to carry (and update every 14 days) the charts for the airports they fly in and out of as well as airports they may get diverted to in an emergency. Obviously carrying an iPad instead of a 40# leather case is much preferred by many pilots.

General Aviation (GA) Market Segment

General aviation (GA) includes all flying that is not military or commercial in nature. General aviation flights range from gliders to private jets. The majority of the world's air traffic falls into this category, and most of the world's airports serve general aviation exclusively. General aviation covers a large range of activities including flying clubs, flight training, agricultural aviation, and people that fly as a hobby (own or rent aircraft).

Business Aviation Market Segment

Business Aviation is made up primarily of two core groups, corporate flight departments and fractional owners (such as NetJets).
Business Aviation operators often fly jets or turboprops with more passengers. They are covered by more FAA regulations than the General Aviation market, but not as stringent as Airlines. Smaller cargo carriers are often considered part of this segment.

Commercial Aviation (CA) Market Segment

The CA market is primarily made up of scheduled Airlines like United or Alaska, as well as charter airlines. CA operators generally have passengers and on some kind of regular schedule. Large cargo carriers are often considered part of this market (there are some blurry lines here). The Airlines are much more regulated than cargo or business operations, however.

Military Aviation Market Segment

In the context of this portfolio, military aviation is really focused on cargo/transport, tanker and VIP aircraft. Basically, these aircraft are similar to commercial aircraft and fly much of their mission(s) in commercial airspace and in/out of commercial airports. Many of our products fit this market well with some adaptations to address the specific needs of the military pilot.

Electronic Flight Bag (EFB)

From the NBAA website: 'An Electronic Flight Bag (EFB) is a device that allows flight crews to perform a variety of functions that were traditionally accomplished by using paper references. In its simplest form, an EFB can perform basic flight planning calculations and display a variety of digital documentation, including navigational charts, operations manuals, and aircraft checklists. The most advanced EFBs are fully certified as part of the aircraft avionics system and are integrated with aircraft systems such as the FMS. These advanced systems are also able to display an aircraft's position on navigational charts, depict real-time weather, and perform many complex flight planning tasks.'
The EFB is often implemented as an 'application manager' that runs on hardware in the cockpit (either portable or fixed mounted). The application manager provides a framework to launch and manage applications used in a pilot workflow and provides some common services to the applications launched within the EFB. Applications can be either tightly or loosely integrated depending on the particular EFB. There are two different EFBs that we have built applications for; Jeppesen's EFB and Boeing's EFB. There are several 'classes' of EFBs (1-3) based on whether the hardware is fix mounted and/or whether the EFB connects to the aircraft systems or not.

NavData

NavData refers to Jeppesen's aviation data that drives the display in our Enroute chart rendering engines as well as aircraft Avionics.

Electronic Updates

We built our own application and data delivery system many years ago. When I refer to electronic updates, it's referring to that system that determines what application and data needs to be delivered to a particular customer/application, authenticates they have rights to the data, and does the updates - including delta/incremental updates. Data is updated every 14 or 28 days depending on the type of data. The system serves over a dozen applications and many tens of thousands of customers.

Background

In early 2010, my team built a prototype application to display Jeppesen Terminal Charts on an iPad in order to demonstrate the value of this new (iPad) platform for our market. It was this prototype that spurred interest in 'mobile' development by Jeppesen and has led to the the flagship mobile FD product. This prototype was the basis for the first Jeppesen iPad application (Mobile TC) and has since lead to the Mobile FD application, one of the company's flagship products. This is one of many examples of innovation that my team has brought to Jeppesen and the industry.

Jeppesen Mobile TC

The first Jeppesen iPad application (extended from the prototype mentioned above) was Jeppesen Mobile TC. This product took Jeppesen Terminal charts to the iPad for the first time. Although we already had windows applications onboard displaying Terminal Charts, the EFB hardware is extremely expensive. Several things happened in large part due to the launch of Mobile TC. Airlines quickly began evaluating iPads (due to the cost and ease of deployment) as an option to replace paper charts and traditional EFBs, and all the interest brought the FAA into the mix. The FAA pretty quickly approved the use of iPads, specifically Mobile TC, to replace paper charts in the cockpit. This one application FUNDAMENTALLY changed the aviation charting industry.
Mobile TC, the product of this team's innovation, changed the industry. You can see some of the stories in the links below which also demonstrate the significant value to our airline customers in cost savings.
The team also received a Commercial Aviation Services (CAS) Service Excellence Award for this product and its impact on the aviation community!

Mobile TC Highlights

• Launched: 7/2010
• Type: iPad App
• Market: Business/General Aviation
• Languages: Objective C
• Distribution: Apple Store
• # of Releases: 5
• Team Size: < 5
• 2010 Flying Magazine Editor's Choice Award

Product Information

iTunes Mobile TC Page
Jeppesen Mobile TC Page
Jeppesen Mobile TC Fact Sheet
FAA Approval for use in flight
EASA Approval for use in flight

Reviews/Customers

Flying Magazine Mobile TC Review
American Airlines approved for use in all phases of flight
Executive Jet Management (EJM) receives approval
Mobile TC saving on pilot injuries

Jeppesen Mobile FD

For the most part the Mobile TC product line has been replaced by the Jeppesen Mobile FliteDeck and Mobile FliteDeck Pro applications, which have a much more robust feature set including Enroute Charting while also providing all the functionality of the Mobile TC application.

Mobile FD Highlights

• Launched: 7/2011
• Type: iPad App
• Market: Business/General Aviation
• Languages: Objective C
• Distribution: Apple Store
• # of Releases: 10
• Team Size: < 6

Jeppesen Mobile FD Page
Jeppesen Mobile FD Pro Page
Flying Magazine Review of Mobile FD
Article on United Airlines use of iPads and Mobile FD

Jeppesen Mobile FD Pro

While Jeppesen Mobile FD is primarily targeted at the General Aviation and Business Aviation customers, the Mobile FD Pro application is targeted at the commercial airline market to replace paper in the cockpit.
The primary difference in the Pro version is the ability to utilize the customized chart services and data used by most airlines, and integrate with Jeppesen Distribution Manager Pro (JDM Pro) to deliver and track the delivery of that data.

Mobile FD Pro Highlights

• Launched: 8/2012
• Type: iPad App
• Market: Commercial/Airlines & Military
• Languages: Objective C
• Distribution: VPP and Enterprise
• # of Releases: 8
• Team Size: < 6

Product Information

iTunes Mobile FD Pro Page
Jeppesen Mobile FD Pro Page

Jeppesen Mobile TC Pro

Mobile TC Pro Highlights

• Launched: 2/2012
• Type: iPad App
• Market: Commercial/Airlines & Military
• Languages: Objective C
• Distribution: VPP and Enterprise
• # of Releases: 4
• Team Size: < 5

While Jeppesen Mobile TC was primarily targeted at General Aviation and Business Aviation customers, the next iOS product we built was Mobile TC Pro. This product was targeted at the Commercial Airline market to replace paper charts in the cockpit. The major addition with this version was the ability to download our commercial customer's unique charts to their iPads on a customer by customer basis. There are only a couple customers still using Mobile FD Pro, the vast majority migrated to Mobile FD Pro shortly after it was launched.

Wireless Data Delivery Application (INDS)

INDS Highlights

• Launched: 9/2013
• Type: iPad App
• Market: Business & General Aviation
• Languages: Objective C
• Distribution: Apple Store
• # of Releases: 1
• Team Size: < 5

The Integrated Navigation Data Service (INDS) is a wireless data delivery application for the iPad. This product was developed as a joint project with Honeywell, Pilatus, and Jeppesen to provide an iPad application that can wirelessly deliver Jeppesen data to the avionics onboard the aircraft, saving the pilot from having to download the data to a computer then write it to a card that gets inserted into a slot on the avionics, which is how JSUM and JDM work and how data has traditionally been delivered. My team builds the iPad application portion of the system that connects to the hardware on the Pilatus Aircraft.

Media Articles on our INDS Application

Wall Street Journal article on Jeppesen's INDS Application
Aviation Today's Article on our iPad INDS Application
Press Release on Wireless INDS Application Launch
iTunes INDS page

Background

All of the products on this page I have been responsible for the development of from concept to deployment and since then their incremental improvement, except FliteStar. Although I was involved in development of the current version of FliteStar (at the time we moved the product from a 16 bit to 32 bit application), I wasn't responsible for its development.

Jetplanner

JetPlanner is a Windows Desktop application that is primarily used by Business Aviation customers and Airline Dispatchers for creating and managing the flight plans for their flights.
I lead the initial design and development of JetPlanner in 2001, with a team of basically three. JetPlanner was the first aviation development project I was responsible for. I have played many roles on this project beyond managing the development including project manager, tester, technical writer, requirements analyst, etc. JetPlanner replaced a 16 bit application with no graphical capabilities as the front-end client to Jeppesen's JetPlan flight planning engine and was initially developed in a very 'start-up' environment. The size of the team has varied over the years, but currently JetPlanner has the biggest team it has ever had working on it (approximately 16 people) and is moving to a new architecture. Although the team size has increased since it's initial development days, the team remains very agile, innovative, flexible, and most important productive - more like a start-up mentality. The launch customer for this new version of JetPlanner is TUI Airlines TUI Airlines Press Release.

JetPlanner Highlights

• Launched: 2001
• Type: Windows Desktop
• Market: Commercial/Airlines
• Languages: C++/MFC/ & C#/WPF
• Distribution: DVD & Electronic Updates
• # of Releases: 30+
• Avg Team Size: < 7

Product Information

JetPlanner's initial launch announcement in 2002
JetPlanner Product Page
JetPlanner Fact Sheet
More JetPlanner Information

MilPlanner

MilPlanner is a derivative of JetPlanner targeted at the Military Flight Planning Market. The primary users are tanker, airlift, VIP, etc. who fly aircraft similar to commercial aircraft. MilPlanner has features specific to the Military users, however the way the application is built MilPlanner takes advantage of all the changes to the commercial JetPlanner product as well.

MilPlanner Highlights

• Launched: 2003
• Type: Windows Desktop
• Market: Military
• Languages: C++/MFC/ & C#/WPF
• Distribution: DVD & Electronic Updates
• # of Releases: 15+
• Avg Team Size: < 3

MilPlanner is used by many of the largest air forces around the world. One challenge with MilPlanner, that I have gained a lot of experience with, is International Traffic and Arms Regulations (ITAR) and the extra precautions that come with it. Although MilPlanner is a COTS product (sold only to the military, of course), we have also been a subcontractor on several major programs providing mission planning as part of an overall program.
MilPlanner is unique in that although it's a COTS product, some of the releases have been done in conjunction with a larger program where enhancements to the application were part of a contract to offer MilPlanner as the flight planning component of a mission planning system (see links below).
MilPlanner is another product/project that I managed from the very beginning to present. MilPlanner is currently actively being developed with ongoing releases.

Product Information

MilPlanner Flyer
MilPlanner Product Page
MilPlanner Fact Sheet
MilPlanner in Boeing Mission Planning Literature
UAE MilPlanner Customer
MilPlanner is a key component to the Royal Australian Air Force's AEW&C Mission Planning

Advanced Air Refueling Module

My team designed, developed, and deployed this Windows application from the initial concept. Today, AARM is being used in real mission planning by air force customers. The application provides air refueling mission optimization that can plan complex missions in a few minutes that historically would take hours to plan. This application was built using the application framework my team designed and developed, significantly speeding up the development process.

AARM Highlights

• Launched: 4/2008
• Type: Windows Desktop
• Market: Military
• Languages: C++/MFC
• Distribution: DVD & Electronic Updates
• # of Releases: 4
• Avg Team Size: < 4

This project was originally started as a Internal Research and Development (IRAD) project funded by Boeing Mission Planning, eventually becoming an active new product development effort, resulting in a released product used in active service for real air refueling missions.

Product Information

My FlitePlan Online (My FPO)

In 2012 I wrote a proposal around Jeppesen utilizing many of the components my team has built over the years to quickly develop a web-based flight planning application for the General Aviation market that could be accessed from the Jeppesen website. After presenting the proposal, our product portfolio team gave the go ahead to develop and launch the product for our Fall NBAA trade show.
This is a free flight planning application for anyone who is a Jeppesen chart subscription customer or can be purchased as a stand-alone subscription. My FPO has a free trial period form the Jeppesen website, so anyone can try it out.

My FPO Highlights

• Launched: 10/2012
• Type: Web Application
• Market: General Aviation
• Languages: Javascript/GWT
• Distribution: Web
• # of Releases: 3
• Avg Team Size: < 4

We designed, developed, and launched the new flight planning application in a matter of several months - introducing a beta at the 2012 NBAA Aviation Conference/Show and going to production two months later.
You can check out the application yourself by going to the My Jeppesen.com website, creating an account (it's free), and clicking on the My FlitePlan Online link. Another note is that the graphic weather display on that website is also using the web chart rendering services my team developed.

Product Information

FliteStar/FliteMap

FliteStar Highlights

• Launched: 1999
• Type: Windows Desktop
• Market: Business & General Aviation
• Languages: C++/MFC
• Distribution: DVD and Electronic Updates
• # of Releases: 20+
• Avg Team Size: < 6

FliteStar was the main product built by MentorPlus Software purchased by Jeppesen in 1996, which was the foundation for the Wilsonville office. The flight planning product, targeted at the Business and General Aviation market, was the market leader in PC flight planning. My team is still responsible for maintenance of the application.
I was involved somewhat in the re-development of FliteStar in 1999 to a new (32 bit) codebase that later became the base for numerous Jeppesen products. In fact, MarineMap was actually the first product launched in the new codebase.

Product Information

Background

These products are all Jeppesen charting products, most of which my team has designed, developed and deployed from the very beginning. There are different products to serve either different markets (Business and General Aviation, Military, or Commercial) or delivery mechanism (web or desktop). JeppView, e-Link, and eCharts are all Windows Desktop applications while Online ChartViewer is a web-based application.
FliteDeck3 as well as the Mobile TC and Mobile FD applications are also charting applications, but designed for use in the cockpit of an aircraft vs the ground-based chart management and printing function that these products serve.

JeppView

JeppView is our desktop charting application for the general aviation market.
My team recently launched version 4.0, however, in our application framework, which also included some new significant features that had previously been developed for the commercial and military markets in e-Link and eCharts. E-Link and eCharts were brought into our application framework several years earlier.

JeppView Highlights

• Launched: 2000
• Launched in new codebase: 2012
• Type: Windows Desktop
• Market: Business & General Aviation
• Languages: C++/MFC
• Distribution: DVD and Electronic Updates
• # of Releases: 10+
• Avg Team Size: < 5

Product Information

JeppView 3 Information
JeppView 4 Information

e-Link for Windows

My team developed e-Link for Windows as a variant of the JeppView product targeted at the Commercial Aviation market. E-link was later migrated to our new application framework and released as version 3.0 with significant enhancements to the functionality. This was pretty much a complete rewrite of the e-Link application within the new application framework, however that effort has now been deployed in multiple applications including Jeppview and eCharts.

Product Information

e-Link Product Page

e-Link Highlights

• Launched: 9/2006
• Launched in new codebase: 5/2009
• Type: Windows Desktop
• Market: Commercial/Airline
• Languages: C++/MFC
• Distribution: DVD and Electronic Updates
• # of Releases: 8+
• Avg Team Size: < 4

eCharts

eCharts Highlights

• Launched: 9/2006
• Launched in new codebase: 5/2009
• Type: Windows Desktop
• Market: Military
• Languages: C++/MFC
• Distribution: DVD and Electronic Updates
• # of Releases: 8+
• Avg Team Size: < 3

My team developed eCharts for Windows as a variant of JeppView for the Military market and later migrated the application to our new application framework and released version 3.0 with significant enhancements to the functionality. eCharts has additional functionality for the military market above and beyond JeppView and e-Link.

Online ChartViewer

Online ChartViewer is accessed from e-Link Online. Online ChartViewer is our web-based charting application that provides access to Jeppesen's charts on the web for our Commercial, Military, and large Business Aviation customers. The largest airlines in the world have access to the Online ChartViewer, which allows pilots, dispatchers, and operations personnel to print Jeppesen charts and text data required to legally and safely fly aircraft.

Product Information

Online ChartViewer Information
Avantair Press Release
Singapore Airlines Customer

ChartViewer Highlights

• Launched:2008
• Type: Web
• Market: Airline/Military/Business
• Languages: Javascript/Java/YUI/Open Layers
• Distribution: Web
• # of Releases: 12+
• Avg Team Size: < 4

FliteDeck3 (FD3)

FliteDeck3 is a Windows-based moving map application (EFB) for the Business and General Aviation Market. It was the original Electronic Flight Bag (EFB) application launched by Jeppesen, long before the Windows-based FliteDeck Pro launched in 2010. Although we had a moving map desktop application (a derivative of FliteStar called FliteMap) prior to FD3, FliteDeck3 has an optimized interface to run in a cockpit environment. Although I wasn't responsible for the development of FliteDeck3, my team is currently responsible for any maintenance.

FliteDeck3 Highlights

• Launched:
• Type: Windows Airborne
• Market: Business & General Aviation
• Languages: C++/MFC
• Distribution: DVD and Electronic Updates
• # of Releases: 8+
• Avg Team Size: < 4

Other

See the iOS and Android sections for the Mobile charting applications.

PDF Chart Viewer (FLIP Viewer)

The PDF ChartViewer application was built and released by my team as a product targeted at the military market to allow them to manage and display their own country charts within the Jeppesen EFB.
Jeppesen's EFB had an application that ran within its framework to view Jeppesen charts, but not the ability to integrate in Military customers own charts (which were available in PDF format). We built the application from concept to delivery.

PDF ChartViewer Highlights

• Launched: 3/2006
• Type: Windows Airborne
• Market: Military
• Languages: Aircraft 'parts'
• # of Releases: 3
• Avg Team Size: < 3

Product Information

Flip Chart Viewer Info Page

Background

My team built the first Android application launched by Jeppesen. The application is built as a native Android application, offering the rich user experience consistent with other applications on the platform. The feature set, however, was based on the second release of the iOS Mobile TC application to maintain consistency between our mobile applications. Currently the 'Pro' version is in development.

Mobile TC Android

Product Information

Mobile TC Android Page
Mobile TC Android Press Release
Google Play Application Page
Android Informer Profile of Mobile TC Android

Background

Although I can't provide too much information on this project, I can say my team began building a version of Mobile FD and Mobile FD Pro for the WinRT Platform in 2013. The intial target platform is on the Surface and Surface Pro tablets. It will have a feature set equivalent to the Mobile FD iOS application.

Product Information

Background

The products on this page were built by to deliver avionics data to Business and General Aviation pilots to load into their Flight Management Computers (FMCs) onboard the aircraft. This system delivers the data based on customer subscriptions and writes it to the appropriate media for the customer's aircraft avionics. It is an extremely complex system that delivers and writes the data to cards for many different avionics systems and services a significant customer base.

Jeppesen Service Update Manager (JSUM)

JSUM Highlights

• Launched: 2002
• Type: Windows Desktop
• Market: Business and General Aviation
• Languages: C++/MFC
• Distribution: DVD & Electronic Updates
• # of Releases: 15+
• Avg Team Size: < 5

JSUM is the original Windows client built to deliver avionics data (NavData and more).

Jeppesen Distribution Manager (JDM) for the Macintosh

JDM is the next generation version, replacing JSUM for segments of the market (eventually expanding to all customers with JSUM). The new version of JDM is built fundamentally as a cross-platform application, so although the initial version was on OS X targeted at the Mac community, the Windows version will ultimately be released from the same codebase.

JDM Mac Highlights

• Launched: 2013
• Type: Macintosh
• Market: Business and General Aviation
• Languages: Javascript/C++
• Distribution: DVD & Electronic Updates
• # of Releases: 1
• Avg Team Size: < 5

My team did an outstanding job of rolling out the new version in a closely managed beta release that had supported avionics rolled out in stages.

Product Information

JDM for Mac Press Release

Flitestar For Macbook

Jeppesen Distribution Manager (JDM) for Windows

JDM Windows is currently being completed as an extension of the JDM for Mac and will be released in the near future, ultimately replacing the older JSUM application.

Application Framework

My team, with hands on leadership by myself and one of my lead developer/architects, designed and built an application framework that is the core of many of our newer products (as well as the basis for the redevelopment and launch of numerous applications such as e-Link, eCharts, JeppView, and soon to be JetPlanner and MilPlanner).
The framework consists of a 'core' that provides common functionality to applications built in the framework (a chart display, undo functionality, configurable UI, common Options settings, ability to detach - or float - panes/views and move to another monitor, searching, ability to 'Skin' an application for optimization in an airborne environment, security/authentication capability, application and data updates, etc.) as well as an extensive 'plug-in' interface providing the ability to take a modular approach to building new functionality, extending the existing functionality, or building new products. The interfaces provide the ability to build plug-ins that load at runtime and add/modify/extend dialogs, add toolbars or toolbar buttons to existing toolbars, add new 'panes', add drawing layers to the chart display, launch dialogs or extend existing dialogs, facilitate one plug-in providing data or computations to another, etc.
The framework was built with a few key goals in mind:

• Maximize the reuse of code (most plug-ins are plug and play with no additional work)
• Reduce Maintenance Costs
• Reduce Testing Costs
• Simplify our codebase and make products more extensible with a modular approach
• Easily address International Traffic and Arms Regulations (ITAR) requirements
• Easier to add developers to a particular product with a community of developers that know the application framework
• Ability to add product functionality without installing a whole new product
• Provide the option for third party development
• Speed up development and deployment of new products

In general, the design was born from the desire to simplify what was a very large, complex, intertwined codebase in our legacy products that had become difficult to maintain. This was really an engineering driven effort (supported by our product manager), and has accomplished almost all of the objectives above.
With the migration of JetPlanner/MilPlanner to the framework in progress, one thing we have done is build all new dialogs/controls launched within the framework from plug-ins in C#/WPF instead of the framework's native C++/MFC. This has been a great challenge, but has actually sped up development of new GUIs and has provided the option in the future to go to all C# without absorbing that total cost right now.
There are currently a number of products built and deployed in this framework, including:

• e-Link for Windows
• JeppView
• eCharts
• Advanced Air Refueling Application
• Jeppesen Enroute (EAA)
• Boeing Enroute (BEA)
• Military Moving Map
• JetPlanner (moving to the framework)
• MilPlanner (moving to the framework)
• Sensor Control (product was deployed then shelved)

With all the products above built form the framework, we now have a library of well over two dozen unique plug-ins that are used in the many products built from the framework.
The goal of being able to build new products quickly was proven possible by building, testing, and deploying a product for use in the cockpit in a matter of months. This product, without the benefit of this framework and leveraging existing plug-ins, would have taken at least a year to develop (a comparable product within the company built on another platform took a team well over a year to build with 3 times the team size).

Sensor Control

Sensor Control was an application for use onboard an aircraft that connected to the FLIR (or other) camera and could show the aircraft position and field of view of the camera with our Enroute chart as well as value added data such as high definition terrain and street/Point of interest data. It would allow the operator to control the camera and lock on a position and keep the camera pointed on that position while the aircraft continued moving. It did actually fly on an aircraft integrated with onboard systems (although I can't go into any more detail than that).
This project was used as the opportunity to invest in and build the framework, with the intent of extending it to many more products. Somewhat ironically, since it has since been shelved, SensorControl was actually the first product built in the new framework.

Background

I was originally hired by Jeppesen in 1997 to lead the design and development of a new marine product based on Jeppesen's aviation charting technology (FliteMap), then mnage the product once it launched. It was a very entrepreneurial startup environment where everyone wore many hats. My role included everything from project management, design, test, marketing, sales, and product management at one time or another.
As a project manager I took a product that was a concept with the technology capability to leverage into the market and lead the team through building a product that did well in a very competitive market (reaching the top 4-5 products in the market). The product did well enough that Jeppesen purchased the company with the #1 and #2 products in the market to go 'all in'.
There were a few product management achievements that I am proud of as well, the most significant was coming up with the concept of a paired down version of our MarineMap application called ViewPoint that could be upgraded to ViewPoint Plus by purchasing a product key. I then negotiated shipping 40,000 of them shrink-wrapped with Yachting and Saltwater Sportsman Magazines throughout the US. That both brought in revenue from upgrades and purchases of our chart region CDs as well as provided a significant amount of advertising exposure.

MarineMap

MarineMap Highlights

• Launched: 1998
• Type: Windows Desktop
• Market: Recreational Marine
• Languages: C++/MFC
• Distribution: CD
• # of Releases: 10+
• Avg Team Size: < 4

MarineMap was a PC based software navigation program that provided moving map capability for real-time navigation with a GPS and PC. MarineMap allowed the user to plan a trip with easy point and click routing, and then display their position on a chart while connected to a GPS. MarineMap included vector data (coastlines, navigation aids, world ports, cities, lakes, rivers, fathom lines, etc.) as well as the ability to display most raster chart formats, including Jeppesen's own RsaterPlus.

MarineMap offered navigation tools such as course/north up orientation, adjustable split screen for route viewing, autopilot connectivity, Tides and Currents displayed on the chart, GPS upload and download capability, chart and trip itinerary printing, seamless chart display, route calculator, navigation log, and convenient notebook. MarineMap provided continuous real-time information about the vessel's current position, next waypoint, and destination waypoint, as well as displaying the current position on the chart.

VewPoint

ViewPoint Plus was a product that provided the ability to display and print nautical charts, set routes with easy point and click routing. It was a free software application with low-resolution chart coverage for the US that could be upgraded to more high resolution charts by purchasing Jeppesen's RaserPlus chart region CDs. Upgrading ViewPoint to ViewPoint Plus added the ability to upload/download route/waypoint/markers to and from a GPS for use on the water.

ViewPoint Highlights

• Launched: 1999
• Type: Windows Desktop
• Market: Recreational Marine
• Languages: C++/MFC
• Distribution: CD
• # of Releases: 3
• Avg Team Size: < 2

Background

I have lead the development of moving map applications since the very beginning of my time at Jeppesen, starting with MarineMap in the 1990's, and since then numerous aviation applications that support navigation onboard the aircraft. Many of the applications in this portfolio include moving map capabilities; however those on this page were actually designed and built specifically for use in the cockpit for real-time navigation.

Military Moving Map (MMM)

Military Moving Map was the first product my team built for use within the Jeppesen Electronic Flight Bag (EFB) and is targeted at our military customer base. MMM was built from our application framework, and launches in a mode with an optimized UI for interaction in the cockpit environment.

Product Information

Military EFB Page
MMM Product page

MMM Highlights

• Launched: 11/2007
• Type: Windows Airborne
• Market: Military
• Languages: C++/MFC
• Distribution: Aircraft 'parts'
• # of Releases: 8+
• Avg Team Size: < 5

Enroute Application (EAA)

The Jeppesen Enroute Application runs under the Jeppesen Electronic Flight Bag (EFB). This product followed the MMM application to target the Commercial Airline market. Again, this application is built from our application framework. EAA is similar to the MMM application, utilizing many of the same plug-ins, however there is actually more functionality in the MMM application for our military customers than the commercial version.

EAA Highlights

• Launched: 4/2010
• Type: Windows Airborne
• Market: Commercial/Airlines
• Languages: C++/MFC
• Distribution: Aircraft 'parts'
• # of Releases: 10+
• Avg Team Size: < 5

EAA was the first application that provided a version of Enroute charting for the cockpit that was 'paper replacement' allowing pilots to stop carrying Enroute paper charts. This was a huge breakthrough in the market. In addition, it was the first to market with weather integration for the commercial cockpit within the EFB. My team received a Boeing Commercial Aviation Services (CAS) Service Excellence Award for this product!

Product Information

Article on Jeppesen Enroute
Jeppesen Enroute Press Release

Boeing Enroute Application (BEA)

BEA Highlights

• Launched: 7/2012
• Type: Windows Airborne
• Market: Commercial/Airlines
• Languages: C++/MFC
• Distribution: Aircraft 'parts'
• # of Releases: 5+
• Avg Team Size: < 5

There are actually multiple versions of the Boeing Enroute Application that run under different Boeing 'classes' of EFB. Similarly to the EAA application with the Jeppesen EFB, BEA is built to integrate into the Boeing EFB application. BEA also has some UI changes to better fit the Boeing EFB look and feel. Utilizing our application framework, BEA was built very quickly, taking advantage of so much reuse.

Product Information

Boeing Enroute Press Release
Boeing Enroute Fact Sheet

FiteMap/FliteDeck 3 (FD3)

FD3 Highlights

• Launched:
• Type: Windows Airborne
• Market: Business & General Aviation
• Languages: C++/MFC
• Distribution: CD and Electronic Updates
• # of Releases: 8+
• Avg Team Size: < 5

FliteDeck3 can still be purchased, but has largely been replaced by newer applications (mostly our Mobile FD iOS application). FD3 was the first Jeppesen application built with an optimized UI to run in the cockpit on a Windows OS.
My team is responsible for maintaining FliteDeck3 (FliteMap has been discontinued), however I wasn't responsible for the initial launch of FD3. Many of my team were, however, responsible for the initial FD3 development and launch.

Enroute Chart rendering Engine

The Enroute Chart Rendering engine is a central component of many Jeppesen applications including many of them in this portfolio, and the foundation of our moving map applications. The first version of the chart rendering engine was developed for the MarineMap and FliteStar applications in the late 1990s. There have been several generations we have developed since then, however the next generation rendering engine that was just released this year in the Enroute Application, and soon the Boeing Enroute Application, is a significant leap in design, performance, and functionality from all previous versions.

Enroute Highlights

• Generation 1 Launch: 1999
• Next Generation Launch: 8/2013
• Type: Embedded
• Market: All markets
• Languages: C++
• Distribution: Embedded
• # of Releases: lots
• Avg Team Size: < 10

I lead two teams that had worked historically on different versions of our rendering engine in an effort to collaboratively design and build the next generation version. After approximately a year and a half, the new version has launched in a product and will be coming out in JeppView/e-Link/eCharts products in the near future and in Mobile FD iOS in early 2014.
Of all the products in this Portfolio that I have been hands on involved in leading the development of, this one is probably one of them I am most proud of because the teams came together to truly build the foundation of the company’s chart rendering future and provide a path to get to a single chart rendering engine (replacing 3 generations currently deployed in products).

Web Charting Engine

We built a set of web services around our chart rendering engine to provide it as a component to the web applications in this Portfolio as well as the FlitePlan Online application (Business Aviation web flight planner that isn't built by my team). It is also used to render weather on the My Jeppesen.com website. This web adaptation of our core rendering engine currently supports Online ChartViewer and My FlitePlan Online (and supported the AOPA Internet Flight Planner - AIFP - until late 2012).

Jeppesen Weather Controller (JWC)

The Jeppesen Weather Controller serves up weather to many of the applications in this portfolio. We built this system to ingest different weather types and providers, normalize the data into a common format, and deliver it to our applicaitons. Since it's initial release, JWC has been moved to the cloud (S3), which has been a huge savings on bandwidth within Jeppesen for a commodity service (data download). JWC runs in two modes, as the server and on the client machines as a service. It is exactly the same application that serves up the data to the JWC instances installed with the client. This has been extremely efficient for our development and deployment. This is a great example of the innovation and architecting solutions intelligently to minimize work and maximize reuse.

e-Link Online (Portal)

The e-Link Portal is the launching point for our commercial and military customers to manage their users and access their electronic data and charting services, including the Online ChartViewer.
The e-Link Online Portal was developed (really redeveloped) by my team. When my team took over development of the e-Link Portal, it was in pretty bad shape. The initial development had been poorly designed and had not been maintained in a couple of years (even worse the team that had built it were long since gone from Jeppesen), it was on an outdated platform, and required very close to an entire rewrite. It was quite challenging since e-Link Online touches many internal systems and provides our customers the ability to interact with those systems and data. Since the e-Link Online rewrite, there have been many new features and enhancements to provide more value to our Commercial customers.

Product Information

e-Link Online Documentation

Flitestar For Macbook Air

Flitestar For Macbook Pro

Flitestar For Mac Os