Professional Documents
Culture Documents
Administrator Guide
Jeppesen
55 Inverness Drive East
Englewood, Colorado 80112-5498
Contents
Introduction
Additional references .............................................................................................................. 1
Technical support ................................................................................................................... 1
Compatibility statement .......................................................................................................... 2
About the initial app download ................................................................................................ 2
Enterprise expiration dates ..................................................................................................... 3
About battery life ..................................................................................................................... 4
Deployment considerations
General considerations ........................................................................................................... 5
Considerations for updating to 4.2 .......................................................................................... 5
Connectivity considerations
System overview .................................................................................................................... 7
Accessing services - IP white-list ............................................................................................ 8
Connecting to an aircraft interface device (AID) ..................................................................... 8
Assigning content
Supported content types by version ..................................................................................... 11
Content types and file sizes .................................................................................................. 12
Managing options
Uploading company-specific data ......................................................................................... 13
Integrating with a flight planning system ............................................................................... 18
Displaying Airport Moving Map data ..................................................................................... 20
Managing enroute weather data downloads ......................................................................... 20
Working with the Customer Configuration file ....................................................................... 26
Troubleshooting
Escalation guidelines ............................................................................................................ 31
Error codes ........................................................................................................................... 32
Appendices
Appendix A: Global settings and customer configuration ..................................................... 45
Appendix B: Customer Configuration file template ............................................................... 53
Appendix C: Uploading company documents ....................................................................... 59
Introduction
Jeppesen FliteDeck Pro X is a mobile electronic flight bag (EFB) solution designed for commercial, business,
and military aviation pilots. This guide is a resource for anyone who supports the FliteDeck Pro X application.
Additional references
Jeppesen provides detailed, task-oriented training and product support on the
FliteDeck Pro X Customer Support Portal page. For more information related to this
release, see the FliteDeck Pro X 4.2.1 Release Notes.
You can also find detailed, task-oriented training and documentation for the following
applications that you use to support FliteDeck Pro X.
Technical support
Jeppesen provides technical support 24 hours a day, 7 days a week.
NOTE: Users can tap Settings > Help to view tech support contact information
from within the app. Many operators choose to provide their own
technical support from this setting. If that is the case with your operation,
use the Customer Configuration file to define this information. For more
information, see Working with the Customer Configuration file on
page 26.
Compatibility statement
Jeppesen FliteDeck Pro X 4.2.1 is compatible with iPadOS 13.3. The minimum
operating system is iPadOS 13.2. FliteDeck Pro X tests against, and supports, iOS
English (U.S.) language.
Devices supported
Jeppesen FliteDeck Pro X 4.2.1 is supported on the devices listed in the following
table.The iPad Air 2 and later models are recommended devices.
The variability in the storage capacity requirement is related to the size of the data
coverage area. Any additional data, Airport Moving Map (AMM), or tailored enroute
data, for example, also affects storage requirements. For information on file sizes, see
Content types and file sizes on page 12.
Expiration date
App version
(year-month-day)
After users download FliteDeck Pro X for the first time, they might need to confirm
Jeppesen Sanderson, Inc., is a trusted developer.
Refer to the Apple support article for more information on custom enterprise apps.
Guidelines for installing custom enterprise apps on iOS.
Deployment considerations
Jeppesen FliteDeck Pro X is released through available Apple distribution models.
General considerations
General administrator considerations include:
• FliteDeck Pro X requires an initial data download for use in the app. Jeppesen
Distribution Manager Pro (JDM Pro) is the web-based application that is used
exclusively to distribute data to devices.
• When updating the FliteDeck Pro X app, the existing version of the app is
overwritten and data registration information is automatically shared.
• With each new major and minor release, FliteDeck Pro X introduces new func-
tionality that may require the distribution of new or updated content types.
Always make sure that users have the necessary time and bandwidth to
perform the complete update.
• An operator might choose to use a Customer Configuration file to define
FliteDeck Pro X global settings and integrate optional functionality. This
configuration file may need to be updated to support any new functionality
introduced with the new release.
• FliteDeck Pro X supports aircraft interface devices (AIDs) from various vendors.
Due to differences in AIDs and their installations, different configuration
parameters might be needed. Your AID integrator can provide the needed
configuration information. Or for more information, contact your Jeppesen
account manager.
IMPORTANT: Make sure that users have the necessary time and bandwidth to perform
the complete update.
Updating to FliteDeck Pro X 4.2 requires the distribution of the following updated
content types:
If an operator subscribes to Airport Moving Map, a new content type must be distrib-
uted:
Finally, if an operator chooses to control the new global setting, Download Wx Only
Along the Route, or add support for a new aircraft interface device (AID), the
Customer Configuration file needs to be updated.
Connectivity considerations
This section provides a system overview of FliteDeck Pro X services, a list of required white-listed server
addresses and AID connectivity considerations.
System overview
NOTE: D-ATIS is available through FliteDeck Pro X at over 70 major airports. For the
most recent list of airports, go to the FliteDeck Pro X Customer Support Portal
page and access the FliteDeck Pro X D-ATIS Supported Airports knowledge
article.
If AID credentials are entered, and a connection is not established within 10 seconds,
the internal GPS for the mobile device is used instead of the AID. GPS source is
identified for users from the GPS Status button on the FliteDeck Pro X toolbar.
• Boeing ONS
• CMC Electronics PilotView®
• FreeFlight Systems RANGR devices outfitted with FWF-125 Serial WiFI
• Jeppesen Standard
• NavAero
• Rockwell Collins FOMAX
• Teledyne GroundLink® AID+
NOTE: Operators might be required to get added authorization to use this function-
ality. Any offset of the GPS antenna should be accounted for in determining
the total accuracy of the system.
Assigning content
You use the JDM Pro application to upload and distribute required data to recipient devices for use in FliteDeck
Pro X. For detailed instructions on managing and delivering content, log in to the JDM Pro Customer Support
Portal page and access the JDM Pro Application Administrator Guide.
As
Content Type Description Required On Disk Transmitted Provider
CICCHARTS Customer-inserted charts (CIC) terminal No variable variable Operator
charts
ECNPDF Enroute Chart Change Notices in PDF No 3 MB 2 MB Jeppesen
ETEXT Company manuals No variable variable Operator
FDPro_Customer_Config Customer configuration of global settings No < 1 MB < 1 MB Operator
J3n_ten_v02 Tailored enroute data No < 1 MB < 1 MB Jeppesen
j3n_v06 Enroute data with Smart Notes in J3N Yes 400 MB 71.5 MB Jeppesen
j3s_v06 Cultural data Yes 720 MB 540 MB Jeppesen
jawm_html_v01 Standard Jeppesen Airway Manual text No 320 MB 230 MB Jeppesen
(HTML)
jds_sma_v01 Airport Moving Map (Smart Airports) No variable variable Jeppesen
(475 MB (230 MB
worldwide) worldwide)
jpac_v02 Supplier configuration No < 1 MB < 1 MB Jeppesen
srtmterrain Terrain Yes 300 MB Jeppesen
terminal charts Terminal charts Yes variable variable Jeppesen
(792 MB
worldwide)
TABLE 5: FliteDeck Pro X content types and file sizes
Managing options
An operator can customize FliteDeck Pro X to meet operational needs and subscribe to various options that
can be integrated into FliteDeck Pro X.
Company manuals
Starting with FliteDeck Pro X, JDM Pro is used exclusively to upload and distribute
company manuals to FliteDeck Pro X. When you are uploading company manuals,
consider the following:
PDF titles
- FliteDeck Pro X displays the title of the document as it is identified in the
PDF Document Properties Title field.
File resolution
- Special consideration should be taken for large format documents, that is,
documents with page sizes larger than 11x17.
For more information on using JDM Pro to upload documents, see Appendix C:
Uploading company documents on page 59.
To learn more about the Ground Controls application, contact your Jeppesen account
manager, or access the Ground Controls Customer Support Portal page.
NOTE: If your operator subscribes to Tailored Enroute Services, tailored enroute data
must be updated (j3n_ten_v02) with the FliteDeck Pro X 4.2 release.
As another option, you can use the Jeppesen Tailored Maps application to interact
directly with tailored enroute data. Jeppesen Tailored Maps is a web-based
application that can be accessed as a stand-alone application or from within the
Jeppesen Ground Controls application. Tailored enroute data that is created with
Tailored Maps is content that is specific to your operation. This content is independent
of Jeppesen production or revision cycles. To learn more about the Tailored Maps
application, contact your Jeppesen account manager or access the Tailored Maps
Customer Support Portal page.
• Airports
- Show Only ETOPs Airports—If provided with tailored enroute data, users
can filter the map to show only ETOPs airports.
- Show Only Company Airports—If provided with tailored enroute data, users
can filter the map to show only airports with company services and they can
further filter the enroute map by available company services.
- Show Airports at all Scales—If this is enabled in the Customer Configuration
file, users can customize their view to show airports at all scales regardless
of the map zoom level.
• Airways
- Users can filter to Show Organized Tracks in both IFR themes whenever
Display Organized Track Systems (OTS) is set to ON in FliteDeck Pro X
global settings. Operators can control this setting with the Customer Config-
uration file.
• Waypoints
- Show Waypoints at all Scales—If this is enabled in the Customer Configura-
tion file, users can customize their view to Show Waypoints at all Scales
regardless of the map zoom level.
• Navaids
- Show Navaids at all Scales—If this is enabled in the Customer Configura-
tion file, users can customize their view to Show Navaids at all Scales
regardless of the map zoom level.
• Airspace
- If provided with tailored enroute data, users can filter to show or hide ETOPs
rings.
1. Identify the cycle that your Jeppesen tailored airway manual text or your tailored
(company-specific) terminal charts are distributed. Then, define your customized
grace period according to the follow criteria:
• If either are distributed on a weekly basis, use the weekly maximum grace
period.
• If either are not distributed on a weekly basis, use the biweekly maximum grace
period.
• If either are distributed on a monthly basis, use the monthly maximum grace
period.
2. Enter the update policy criteria into the Customer Configuration file. This image
shows a sample of update criteria for a bi-weekly update cycle.
<Updates>
<OperatorPolicyHours>23</OperatorPolicyHours>
<OperatorPolicyDays>7</OperatorPolicyDays>
<AirwayManual>TRUE</AirwayManual>
<TailoredText>TRUE</TailoredText>
<TailoredTextCycle>WEEKLY</TailoredTextCycle>
</Updates>
This diagram shows how the example scenario extends the maximum grace period
(represented by the amber bar in the FliteDeck Pro X data Updates screen) by 2 days,
12 hours.
About standard and tailored Airway Manual text and tailored cycles
In the Customer Configuration file, you define the settings for Airway Manual text,
tailored text, and the tailored text cycle as shown in this table.
No
No standard No standard
standard
Standard Standard and tailored and tailored
Standard and
and tailored and tailored on on
and tailored tailored on
Setting Standard on bi-weekly on bi-weekly bi-weekly bi-weekly
on weekly weekly
only even odd even odd
TailoredText-
Don't set BIWEEKLY_EVEN BIWEEKLY_ODD WEEKLY BIWEEKLY_EVEN BIWEEKLY_ODD WEEKLY
Cycle
TABLE 7: Standard and tailored Airway Manual text and tailored cycles
NOTE: The aircraft call sign or registration and origin ETD are two values that are
important for viewing the flight plan route in FliteDeck Pro X. The aircraft call
sign is the flight plan search criteria in FliteDeck Pro X. The origin ETD is
important because it must be no further than six hours into the future. If it is
further than six hours into the future, FliteDeck Pro X does not display the flight
plan route.
• Briefing solutions
Both Jeppesen briefing apps, such as Aviator, and non-Jeppesen briefing apps
that have agreements with Jeppesen, can implement app-to-app flight plan data
sharing.
When a flight plan is published, the full briefing reaches the server and is then
converted to ARINC 633 XML format so that it is received by the briefing solution
and the route made available to FliteDeck Pro X.
Non-Jeppesen flight planning systems use an API to send flight briefings to the
server where they are ingested by Aviator and the route made available to
FliteDeck Pro X. Non-Jeppesen flight briefing must be sent to the server in ARINC
633 XML format.
If your operator uses QR coding to encode route information, users can load a route
by tapping a specially formatted URL or focusing their device camera on a QR code
with the URL embedded. For more information, contact your Jeppesen account
manager.
NOTE: For operations that use AMM, FliteDeck Pro X 4.2 requires the download of
new AMM data (new content type: jds_sma_v01).
Airport Moving Map is not available for all airports. An operator can subscribe to as
many or few airports as required for their operation.
Available
Weather layer FliteDeck Pro X interaction coverage Update frequency
Turbulence - Displays • Touch and hold the altitude slider Global • New weather update -
turbulence intensity and drag up or down to view model output is updated
forecasts using the turbulence severity at different every six hours, for
following categories: altitudes. forecasts from six hours to
Light, Light to • Tap the Play button to animate the
36 hours at six-hour time
Moderate, Moderate, weather frame by frame.
steps.
and Moderate to • FliteDeck Pro X automati-
Severe. • Touch and hold the time slider and
cally checks every two
drag to left or right to view different
Turbulence forecasts minutes.
frames in the forecast.
are provided for the
• Tap the line on either side of the
following flight levels:
slider to advance one frame at a
110, 130, 150, 180,
time.
210, 240, 270, 300,
340, 390 and 430.
Echo Tops - Displays • Tap the Play button to animate the CONUS • New weather update
the maximum height weather frame by frame. only available every 10 minutes.
where ground-based • Touch and hold the time slider and • FliteDeck Pro X automati-
radar detects precipi- drag to left or right to view different cally checks every two
tation. Legend frames in the forecast. minutes.
provides 5000 ft
increments 5000– • Tap the line on either side of the
75,000 ft MSL. slider to advance one frame at a
time.
Winds & Temps Aloft • Touch and hold the altitude slider Global • New weather update -
- Displays forecast and drag up or down to view model output is updated
winds and tempera- forecast winds at different altitudes. every six hours, for
tures aloft for the forecasts from six hours to
• Tap a winds barb to view forecast
following flight levels: 36 hours at six-hour time
wind speed, direction, and
030, 060, 090, 120, steps.
temperature at the specified
150, 180, 210, 240,
altitude. Valid time is indicated, as • FliteDeck Pro X automati-
270, 300, 330, 360,
well. cally checks every 10
390, 420, 450, 480,
minutes.
480, 510 and 540.
Available
Weather layer FliteDeck Pro X interaction coverage Update frequency
Surface Conditions -- • Tap a surface condition icon on the Global • Updated as METAR reports
Displays graphical map to display the METAR. are updated.
METAR conditions from
airport observations and • FliteDeck Pro X automati-
color codes the airport cally checks every five
flight conditions using minutes.
the following scheme:
Green - VFR; Amber -
IFR; Red - LIFR.
Cloud cover is also
depicted based on the
sky conditions reported
in the METAR (OVC,
BKN, SCT, FEW CLR)
Lightning - Displays • Tap a lightning icon on the map to Global • New weather update every
cloud to ground and display time and strike count. 5 minutes showing the past
within cloud lightning 15 minutes of lightning
strikes. strikes.
• FliteDeck Pro X automati-
cally checks every five
minutes.
Lightning
Expired weather
When weather data reaches a certain age it expires, and the Weather bar displays an
amber expired flag next to the selected weather. The following table describes expired
weather rules in FliteDeck Pro X.
Echo Tops When the last image Slider displays six images.
received is 60 min- Remove all images when the
utes old last image received is two
hours old
* FORECAST LAYERS:
Model Run Every 6 hours (0000Z, 0600Z, 1200Z, 1800Z)
Model Run Time is the term used for one complete model calculation of
atmospheric conditions for a determined forecast range. The time of com-
pletion of the run is also called model update time.
.
Data Coverage Source
NEXRAD Level 2 US/Korea/Guam IRADS
Canada Canada IRADS
Germany Germany GWS (German Weather Service)
Nimrod UK UK Met Office
Euro Europe UK Met Office
Opera Europe+ Eumetnet (UK Met Office)
JMA (Japan Meteorological
Japan Japan
Agency)*
ABOM (Australian Bureau or
Australia Australia
Meteorology)
*WSI uses radar from Japan and South Korea to cover this region.
You can author different configurations for use with different user groups within your
operation. For example, pilots who fly domestic routes might have a different configu-
ration from pilots who fly international routes.
Each configuration is packaged separately, given a title, and uploaded to JDM Pro
where the configuration is assigned to the proper distribution groups. Only one
Customer Configuration file can be assigned to a device.
In addition, operations that use different versions of FliteDeck Pro, for example,
FliteDeck Pro X and FliteDeck Pro for Windows, can combine the configurations into
one file.
NOTE: Different versions of FliteDeck Pro X might not have the same configuration
options. Options that do not pertain to a version of FliteDeck Pro are ignored.
NOTE: The Customer Configuration file must be updated to control for the new setting
(Download Wx Only Along the Route) or to connect with a newly supported
aircraft interface device (AID).
For JDM Pro Premium operators, you can use the customer configuration tool to
create a customer configuration file within JDM Pro. You access this tool from the
Content page of JDM Pro by selecting Add Content > Create.
For JDM Pro Essential operators, you can follow the steps below to create an XML
Customer Configuration file manually and then upload it to JDM Pro.
1. Using a plain text editor such as Notepad or TextEdit, create a configuration file
from the template provided in Appendix B: Customer Configuration file template.
2. Validate the structure and settings of your configuration file.
• Aside from the version attribute, you can omit any item. Omitted items are
available on the device settings and remain under user control.
• Use either the word ON or OFF for bilevel elements. For example, a bilevel
element, such as <DisplayOwnshipApproach> is either switched ON or OFF.
• To tailor the configuration for different applications, you can associate any top-
level element with the version of the application. Top-level elements include
<ApplicationBehavior>, <Enroute>, <TerminalCharts>, <Weather>, and
<Services>. Non-associated elements are used for all versions.
• Operations that use different versions of FliteDeck Pro, for example, FliteDeck
Pro X and FliteDeck Pro for Windows, can combine the configurations into one
file. For more about the settings in this file, see Appendix A: Global settings and
customer configuration on page 45.
• The version attribute appears at the top of the configuration file. Changing this
number in your configuration file has no effect in FliteDeck Pro X. The number
is intended to indicate the version of the XML schema the file is using.
3. Save the XML file.
NOTE: For Mac users: macOS generates hidden resource files when creating a
.zip file, which might cause errors when you upload it to JDM Pro. Make
sure that you include only one file in each ZIP file. Instead of right-clicking
and using the Compress function, you can use the zip command at the
macOS Terminal command line.
If the file lacks the proper metadata, JDM Pro guides you through the process of
creating the metadata. The only specified selection is the Content Type, which must
be set to FDPro_Customer_Config.
NOTE: Jeppesen recommends that you use a browser that supports HTML5. If you
use a browser that does not support HTML5, JDM Pro cannot compute the
MD5 value for the file during the upload process and create the ADEL
metadata file.
JDM Pro uploads the file, runs a virus check on the content, and then displays the
Content Metadata box.
- If this is the first time that you are uploading this file, enter a name for the
content.
- If this is a new version of the file that you have already uploaded, make sure
to use the same title as the previous version. By doing this, the updated
document follows the existing distribution rule in JDM Pro.
8. Enter a version number for the document:
- If this is a new file, create a version number.
- If this is a new version of a file that you have already uploaded, create a
version number based on the previous one. JDM Pro indicates the previous
version number in the Content Metadata box.
9. If you want recipients to download and use the content when it becomes available,
select the Deliver Immediately check box.
NOTE: When you select Deliver Immediately for content that is delivered to
FliteDeck Pro X, FliteDeck Pro X notifies the user when the new content is
available.
10.Click Continue.
JDM Pro uploads the file and adds the content item to the Content list.
If you are uploading a document that you have not uploaded before, assign that
content to a distribution group. If you do not assign the content to a distribution
group, JDM Pro cannot send the document to recipients.
NOTE: For more information on managing and delivering content with JDM Pro, log in
to the JDM Pro Jeppesen Customer Support Portal and access the JDM Pro
Application Administrator Guide.
Troubleshooting
If users report specific error messages, see Error codes on page 32.
To review the most current knowledge articles on specific issues, go to the FliteDeck Pro X Customer Support
Portal page.
Escalation guidelines
If you are unable to resolve an issue by using the resources in this guide or in a
knowledge article on the FliteDeck Pro X Customer Support Portal page, escalate the
issue to Jeppesen technical support.
• Recipient name.
• Complete description of the issue, including a detailed work flow leading up to the
issue. Screenshots or videos of the issue are most helpful.
• Error code, if any.
• Log Files (see the following topic, Generating log files in FliteDeck Pro X).
• Type of device and model.
• Type of network used (Wi-Fi or cellular).
- If cellular, identify the network (3G, 4G, LTE).
- If Wi-Fi, describe the location from which accessing data. For example,
hotel, FBO, home.
• Device general settings.
• FliteDeck Pro X global settings.
Error codes
FliteDeck Pro X generates the following error codes when it encounters certain
conditions.
101 The registration failed. The mobile device is already If the device must be activated with a
The device is already registered and the user is different recipient, ask the user to
registered. Contact attempting to register it again. deactivate FliteDeck Pro, and then
technical support. reactivate it using a registration link
The Recipient state shows as sent to their device from JDM Pro.
“Active,” “In Configuration,” or
“Out of Configuration” in JDM If the device is already activated with
Pro. the correct recipient, verify whether the
user can retrieve any assigned data.
102 The registration is The application registration is Generate another registration email
invalid. Contact invalid. from JDM Pro.
technical support.
105 The application cannot FliteDeck Pro X cannot The user must request the file again.
process the updates. process the data update. Any temporary files are automatically
Try again later. If the removed from the device. Reattempt
issue persists, contact File processing failed due to a the data update.
technical support. mismatch of the stored and
calculated digest values.
Processing cannot continue.
106 The data update FliteDeck Pro X cannot The user must request the file again.
cannot be processed process the data update. Any temporary files are automatically
by the application. removed from the device.
Contact technical This error indicates a generic
support. unzip process failure.
Processing cannot continue.
107 The data update The data delta set update If the issue persists try deactivating
cannot be processed. cannot be processed. and reactivating the device.
The application will FliteDeck Pro X will
automatically attempt automatically attempt to If that does not resolve the issue, or
to download the full download the full version for this is happening on multiple devices
data set. the data. (Any temporary files at the same time, contact Jeppesen
are automatically removed technical support.
from the device).
109 The data update FliteDeck Pro X cannot Ensure that the device has adequate
cannot be processed process the data update. storage capacity and a reliable network
by the application. connection is established. Have the
Contact technical This error might indicate user try the download again.
support. several issues, ranging from
network or server issues to Up to 6 gigabytes (GB) of storage
storage limitations on the space may be required to install the
mobile device. application and all of the data.
113 The application cannot Advise the user to try the download again on a different network; or
download the data. once better internet connectivity is established.
Try again later. If the
issue persists, contact If the issue persists, contact Jeppesen technical support.
technical support.
120 The data update The data update cannot be Advise the user to free up storage
cannot be processed. processed by the application space on the device and try again.
The application will due to storage limitations on
automatically attempt the mobile device. Up to 6 GB may be required to install
to download the full the application and all of the data.
data set. Normally, FliteDeck Pro X
downloads the zip file, unzips If the issue persists, contact Jeppesen
the files, copies the unzipped Technical Support.
files to the data directory, and
then removes the unzipped
temp files.
127 The application cannot Network connectivity issue. Advise the user to wait one minute and
connect to the update try again on a different network, or
server. Try again later. once better connectivity is established.
133 Data required by the Data required by the Ensure that data is assigned in the
application is not application is not assigned to appropriate distribution group.
available for your the distribution group the
account. Contact recipient belongs to in JDM If the issue persists, contact Jeppesen
technical support. Pro. technical support.
134 The download process There is no more background If the issue persists, contact Jeppesen
has stopped. processing time available. technical support.
Reestablish
connectivity and try
again.
180 The data update The data delta set update If the issue persists, contact Jeppesen
cannot be processed. cannot be processed. technical support.
The application will FliteDeck Pro X will
automatically attempt automatically discard the delta
to download the full set and attempt to download
data set. the full dataset.
185 The data update The data delta set update If the issue persists, contact Jeppesen
cannot be processed. cannot be processed. technical support.
The application will FliteDeck Pro X will
automatically attempt automatically discard the delta
to download the full set and attempt to download
data set. the full dataset.
186 The data update The data delta set update If the issue persists, contact Jeppesen
cannot be processed. cannot be processed. technical support.
The application will FliteDeck Pro X will
automatically attempt automatically discard the delta
to download the full set and attempt to download
data set. the full dataset.
199 The next version of FliteDeck Pro X is expecting Ensure that the correct content items
[ContentId, the identified data to be are present for the distribution group
ContentName, available but it is not available and correctly added to the recipient
ContentVersion] is not yet. registered to the device.
yet available and
cannot be processed If the issue persists, contact Jeppesen
at this time. Please technical support.
wait and try again. If
problem persists,
please contact your
EFB administrator
[199]
1002 The URL that FliteDeck Pro X This is typically caused by a third-party
is using to register or update is email application corrupting the
invalid. registration link. Try another email
client or copying and pasting the link
from your email into Safari.
3001 Data required by the One or more required If the issue persists, contact Jeppesen
application is not databases are not assigned to technical support.
available to your the device.
account. Contact
technical support.
3116 A server error The expected configuration If the issue persists, contact Jeppesen
occurred. Contact reported from the server was technical support.
technical support. not in the correct format.
3117 The application cannot While getting an expected If the issue persists, contact Jeppesen
process the data. configuration from the server, technical support.
Contact technical an operating system error was
support. reported. An entry is added to
the CCDL log file showing the
error number.
3118 A server error The expected configuration is If the issue persists, contact Jeppesen
occurred. Contact complete, but contains no technical support.
technical support. content for the device, or the
device is missing from the
configuration.
3120 A server error Error 3120 indicates that JDM Pro does not recognize the device that
occurred. Contact the recipient originally registered.
technical support. All recipients will show Error 3120 for up to 5 minutes after the recipient
is created. This happens because it takes some time for JDM Pro to
calculate all the current versions of all content assigned. If you see this
error on a newly created recipient, you only need to wait a couple
minutes and try again.
If the error appears in any other scenario besides a brand new recipient,
the resolution is:
1) Ask the user to deactivate the device (in FliteDeck Pro global
settings); and
2) The user clicks the activation link in their registration email to re-
register the device and redownload content.
There are several different things that might cause this issue:
• FliteDeck Pro X is designed to work on a single device per recipient,
however, that recipient can register multiple times with the same link.
Each time the recipient registers a new device, the previously
registered device can no longer update and reports error 3120.
Sometimes, a recipient may forward their link to a personal device to
use as a back-up. It will appear to work, but when it comes time for
the next data update the first device will fail and report this error
code.
• FliteDeck Pro X uses the iOS Advertising Identifier to uniquely
identify a recipient's valid device to prevent unauthorized access of
aviation data. If the user changes the iOS Privacy feature Limit Ad
Tracking, it causes this identifier to change or be masked, which in
turn, appears to JDM Pro as an unauthorized device that causes the
Error 3120 to appear. This will not be apparent until it is time for a
content update so the recipient may not remember changing the
setting at the point the error appears. Changing the setting back to
its original value may not resolve the error.
• If a recipient changes their device or changes their iCloud settings or
iCloud account, this error might display.
• Improperly registering another app on the device, such as Aviator,
after FliteDeck Pro X is already activated. The recommended way to
activate more Jeppesen or Boeing apps after one is already
activated on the device is to use the Share Registration feature.
Registering subsequent apps using the registration link instead of
Share Registration causes this error in all Boeing or Jeppesen apps.
FIGURE 10: FliteDeck Pro X 4.2 global settings (continued on next page)
FIGURE 11: FliteDeck Pro X 4.2 global settings (continued from previous page)
Allow Device to To ensure that FD Pro remains active during flight, set to OFF. FD Pro X 4.0+ ON (default)
Sleep FD Pro (iOS) 2.5+ OFF
Switching this setting to OFF reduces device battery life. FD Pro (Win) 8.3+
(Sleep Mode)
Starting with FliteDeck Pro X 4.0, this setting was moved from iOS
global settings and renamed Allow Device to Sleep in the app
Settings. The setting remains controllable with this customer
configuration setting.
FLIGHT INFO
Allow Flight Sharing To share flight information between two devices actively running FD Pro X 4.0+ ON
FliteDeck Pro, set to ON. FD Pro (iOS) 2.5+ OFF (default)
Display ATC To retrieve and load recently cleared ATC routes, set to ON. FD Pro X 4.0+ ON
Clearances FD Pro (iOS) 2.7+ OFF (default)
FD Pro (Win) 8.3+
Display NOTAMs To retrieve and display NOTAMS, set to ON. FD Pro X 4.0+ ON
OFF (default)
Aviator Integration To enable Aviator integration with FliteDeck Pro, set to ON. FD Pro X 4.0+ ON
FD Pro (iOS) 3.1.4+ OFF (default)
Allow Plotting File To export plotting files from FliteDeck Pro, set to ON. FD Pro (Win) 9.2+ ON (default)
Export OFF
ENROUTE VIEW
Moving Map To track aircraft position, recenter the enroute map over aircraft FD Pro X 4.0+ ON
location and to view the enroute map in Track Up orientation, FD Pro (iOS) 2.5+ OFF (default)
set to ON. FD Pro (Win) 8.3+
Display Ownship To display aircraft position (ownship) on the enroute map, set to FD Pro X 4.0+ ON
ON. FD Pro (iOS) 2.5+ OFF (default)
FD Pro (Win) 8.3+
Display VFR Theme To display the VFR enroute map theme, set to ON. FD Pro X 4.0+ ON
FD Pro (iOS) 2.7+ OFF (default)
FD Pro (Win) 8.3+
Allow Show All To show all airports, navaids, and waypoints on the enroute map FD Pro X 4.0+ ON
Filters regardless of zoom scale, set to ON. FD Pro (iOS) 2.7.1+ OFF (default)
FD Pro (Win) 8.3.1+
Display Organized To retrieve and display Organized Track Systems (OTS) data on FD Pro X 4.0+ ON
Track Systems (OTS) the enroute map, set to ON FD Pro (iOS) 3.0+ OFF (default)
FD Pro (Win) 9.0+
Display OTS using To display OTS track labels using ARINC values, set to ON. FD Pro X 4.1+ ON (default)
ARINC Labels OFF
When this setting is set to OFF, the track labels display full
latitude and longitude coordinate values.
Display Ownship To display aircraft position (ownship) on approach charts, FD Pro X 4.0+ ON
on Approach set to ON. FD Pro (iOS) 2.7+ OFF (default)
Charts FD Pro (Win) 9.1+
Display Ownship To display aircraft position (ownship) on to-scale SID/ FD Pro X 4.0+ ON
on SID/STAR/REF STAR/REF charts, set to ON. FD Pro (iOS) 3.1+ OFF (default)
Charts FD Pro (Win) 9.1+
Display Ownship To display aircraft position (ownship) on taxi charts and FD Pro X 4.0+ ON
on Taxi Charts & Airport Moving Map (AMM), set to ON. FD Pro (iOS) 2.5+ OFF (default)
AMM Starting with FliteDeck Pro X 4.0, this setting was renamed FD Pro (Win) 8.3+
Display Ownship on Taxi Charts & AMM in iOS global
settings. This setting controls the appearance of ownship
on both taxi charts and Airport Moving Map (AMM).
Default Chart To set a preference for the default zoom level of terminal FD Pro (iOS) 2.5+ Fit Full Chart (default)
Zoom Level charts, make a selection. FD Pro (Win) 8.3+ Fit to Width
Set AMM as To switch to the Airport Moving Map (AMM) instead of the FD Pro X 4.0+ ON
Default on taxi chart when Show Taxi on Landing is engaged, set to FD Pro (iOS) 3.0+ OFF (default)
Landing ON. FD Pro (Win) 9.0+
Display METAR/ To display terminal weather, set to ON. FD Pro X 4.0+ ON (default)
TAF FD Pro (iOS) 2.5+ OFF
FD Pro (Win) 8.2+
Display Enroute To display enroute weather over the enroute map, set to FD Pro X 4.0+ ON
Wx ON. FD Pro (iOS) 2.5+ OFF (default)
FD Pro (Win) 8.2+
Download Wx To restrict the download of enroute weather to the current FD Pro X 4.2+ ON (default)
Only Along Route route of flight, set to ON. OFF
Temperature Unit To set a preference for displaying temperature, make a FD Pro (iOS) 2.5+ FAHRENHEIT (default)
selection. FD Pro (Win) 8.2+ CELSIUS
Company To display customer-uploaded documents sent from FD Pro (iOS) 2.5+ Alphanumeric characters
Manuals Jeppesen e-Link, enter e-Link credentials. 1–128 characters inclusive
(username) Starting with FD Pro X 4.0, this setting was removed from
iOS global settings and is no longer controlled by customer 8–512 characters inclusive
Company
configuration. With FD Pro X, uploading company
Manuals
documents is only supported with JDM Pro.
(password)
Flight Plans To import routes from a flight-planning system, enter the FD Pro X 4.0+ 1–512 characters inclusive
(URL) account URL. FD Pro (iOS) 2.5+
For more information, contact your Jeppesen account FD Pro (Win) 8.3+
manager.
Flight Plans To retrieve and import routes from a flight-planning system, Alphanumeric characters
(Username) enter the account username. _ underscore
. period
- dash
1–128 characters inclusive
Flight Plans To retrieve and import routes from a flight-planning system, 1–512 characters inclusive
(Password) enter the account password.
NMEA_COM
NMEA_UDP
TELEDYNE
Aircraft Interface To direct FliteDeck Pro X to connect to an AID, enter the IP Contact your 1–512 characters inclusive
Device (AID) address configured for the AID, if required. Jeppesen account 192.168.1.10 (Default)
manager.
Address
Aircraft Interface To direct FliteDeck Pro X to connect to an AID, enter the Contact your Numeric characters
Device (AID) network port, if required. Jeppesen account 0–65535 inclusive
manager.
Default: 50000
Network Port The default port for Teledyne is 50000, FreeFlight is 4000,
CMC is 8341, and FOMAX is 24000.
Aircraft Interface Some AIDs use a second port for data streams. To direct Contact your Numeric characters
Device (AID) FliteDeck Pro to request a specific port for this, enter the Jeppesen account 0-65535 inclusive
data stream port. manager.
Default: 51000
Data Stream Port
Aircraft Interface To direct FliteDeck Pro to connect to an AID, specify a FD Pro (Win) Valid values:
Device (AID) communication port, if required. 9.2.1+ COM1 through COM256
inclusive
COM Port This setting is only needed for NMEA_COM AIDs.
Default: COM10
Aircraft Interface To direct FliteDeck Pro X to connect to an AID, enter the Contact your Value is provided
Device (AID) access code, if required. Jeppesen account by AID vendor.
manager.
Access Code
GPS Antenna When provided by the AID, specify the antenna offsets to FD Pro (Win) 9.1+ 1–65,535
Offsets be applied to the AMM ownship. characters
inclusive
Operator Policy By default, users have a grace period of 23 hours to update FD Pro X 4.0+ 1–23 inclusive
(Hours) terminal charts and Airway Manuals. To extend this grace FD Pro (iOS 2.5+ Default: 23
period, set the maximum hours for the grace period. FD Pro (Win) 8.3+
Support By default, Jeppesen technical support contact information FD Pro X 4.0+ 1–128 characters inclusive
North America is listed in app settings.
FD Pro (iOS) 2.5+ 800-537-7225 (default)
Toll-Free To display customized technical support information, enter FD Pro (Win) 8.3+
a technical support North America Toll-Free phone number.
Support By default, Jeppesen technical support contact information 1–128 characters inclusive
United States is listed in app settings. 303-328-4170 (default)
Direct
(Domestic) To display customized technical support information, enter
a technical support United States direct phone number.
Support By default, Jeppesen technical support contact information 1–128 characters inclusive
International is listed in app settings. 49-6102-507004 (default)
Prevent To prevent users from deactivating FliteDeck Pro on their FD Pro (Win) 8.3+ TRUE
Deactivation devices, set to TRUE. FALSE (default)
Prevent Clear To prevent users from removing custom content (for FD Pro (Win) 8.3+ TRUE
Custom Content example, saved flights, current flight, user waypoints), set to FALSE (default)
TRUE.
NOTE: The XML declaration (<?xml version="1.0" encoding="utf-8"?>) must be the first line of the file, with no
proceeding white-space.
<?xml version="1.0" encoding="UTF-8"?>
-<CustomerConfiguration version="1.9">
<!--NOTE: Starting with FliteDeck Pro X, some settings are either removed or combined. Existing
customer configuration files will still continue to work with both older applications and FliteDeck
Pro X, but configuration for removed or combined settings will not have an effect in FliteDeck Pro X.
-->
-<ApplicationBehavior>
<SleepMode>ON</SleepMode>
<!--Values: ON (default) or OFF. To ensure FD Pro remains active during flight, set to OFF.
Switching this setting to OFF reduces device battery life. Starting with FliteDeck Pro X4.0, this
setting was moved from iOS global settings and renamed Allow Device to Sleep in the app Settings.
The setting remains controllable with this customer configuration setting.FD Pro X 4.0+, FD Pro
(iOS) 2.5+, FD Pro (Win) 8.3+. -->
<AllowFlightSharing>OFF</AllowFlightSharing>
<!--Values: ON or OFF (default). To share flight information between two devices actively running
FliteDeck Pro, set to ON.FD Pro X 4.0+, FD Pro (iOS) 2.5+. -->
<DisplayATCClearances>OFF</DisplayATCClearances>
<!--Values: ON or OFF (default). To display and load recently cleared ATC routes, set to ON. FD
Pro X 4.0+, FD Pro (iOS)2.7+, FD Pro (Win) 8.3+. -->
<DisplayNOTAMs>OFF</DisplayNOTAMs>
<!--Values: ON or OFF (default). To retrieve and display available state NOTAMS, set to ON.
Starting with FD Pro X 4.0, support for the display of available state NOTAMs was added. FD Pro
X4.0+. -->
<AviatorIntegration>OFF</AviatorIntegration>
<!--Values: ON or OFF (default). To enable Aviator integration with FliteDeck Pro, set to ON. FD
Pro X 4.0+, FD Pro (iOS)3.1.4+. -->
<AllowPlottingFileExport>ON</AllowPlottingFileExport>
<!--Values: ON (default) or OFF. To export plotting files from FliteDeck Pro, set to ON. Starting
with FD Pro (Win) 9.2, the export of plotting files was added. FD Pro (Win) 9.2+. -->
-</ApplicationBehavior>
-<Enroute>
<MovingMap>OFF</MovingMap>
<!--Values: ON or OFF (default). To track aircraft position, recenter the enroute map over
aircraft location, and view the enroute map in Track Up orientation, set to ON. FD Pro X 4.0+,FD
Pro (iOS) 2.5+, FD Pro (Win) 8.3+ -->
<DisplayOwnship>OFF</DisplayOwnship>
<!--Values: ON or OFF (default). To display aircraft position (ownship) on the enroute map, set
to ON. FD Pro X 4.0+, FD Pro(iOS) 2.5+, FD Pro (Win) 8.3+ -->
<DisplayVFRTheme>OFF</DisplayVFRTheme>
<!--Values: ON or OFF (default). To display the VFR enroute map theme, set to ON. FD Pro X 4.0+,
FD Pro (iOS) 2.7+, FD Pro (Win) 8.3+. -->
<AllowShowAllFilters>OFF</AllowShowAllFilters>
<!--Values: ON or OFF (default). To show all airports, navaids, and waypoints on the enroute map
regardless of zoom scale, set to ON. FD Pro X 4.0+, FD Pro (iOS) 2.7.1+, FD Pro (Win)8.3.1+. -->
<DisplayOTS>OFF</DisplayOTS>
<!--Values: ON or OFF (default). To retrieve and display Organized Track Systems (OTS) data on
the enroute map, set to ON. FD ProX 4.0+, FD Pro (iOS) 3.0+, FD Pro (Win) 9.0+. -->
<DisplayOTSUsingARINCLabels>ON</DisplayOTSUsingARINCLabels>
<!--Values: ON (default) or OFF. To display OTS track labels using ARINC values, set to ON. When
this setting is set to OFF, the full latitude/longitude coordinate values display. Starting with
FD Pro X 4.1, support for the display of ARINC values on OTS track labels was added. FD Pro X
4.1+. -->
</Enroute>
-<TerminalCharts>
<DisplayOwnshipApproach>OFF</DisplayOwnshipApproach>
<!--Values: ON or OFF (default). To display aircraft position (ownship) on approach charts, set
to ON. FD Pro X 4.0+, FD Pro (iOS) 2.7+, FD Pro (Win) 9.1+ -->
<DisplayOwnshipSIDSTAR>OFF</DisplayOwnshipSIDSTAR>
<!--Values: ON or OFF (default). To display aircraft position (ownship) on to-scale SID/STAR/REF
charts, set to ON. Starting with FD Pro X 4.1, support for the display of ownship on Class B/
Reference charts was added. FD Pro X 4.0+, FD Pro (iOS)3.1+, FD Pro (Win) 9.1+. -->
<DisplayOwnship>OFF</DisplayOwnship>
<!--Values: ON or OFF (default). To display aircraft position ownship) on taxi charts and Airport
Moving Map (AMM), set to ON. Starting with FliteDeck Pro X 4.0, this setting was renamed Display
Ownship on Taxi Charts & AMM in iOS global settings. This setting controls the display of ownship
on both taxi charts and Airport Moving Map (AMM) in FliteDeck Pro X.FD Pro X 4.0+, FD Pro (iOS)
2.5+, FD Pro (Win) 8.3+. -->
<DefaultZoomLevel>ZOOM_FIT_FULL</DefaultZoomLevel>
<!--Values: ZOOM_FIT_FULL (default) or ZOOM_FIT_WIDTH. To set a preference for the default zoom
level of terminal charts, make a selection. Starting with FliteDeck Pro X 4.0, this setting was
removed from iOS global settings and is no longer controlled by customer configuration. FD Pro
(iOS) 2.5,+ FD Pro (Win) 8.3+. -->
<SpeedThreshold>40</SpeedThreshold>
<!--Values: 30, 40 (default), 50, 60, 70, or 80 knots. To customize the speed threshold at which
the automatic switch to a taxi chart occurs, when Show Taxi on Landing is engaged, select a
speed. This is also the speed threshold at which ownship appears on the taxi chart and Airport
Moving Map (AMM), when enabled. FD Pro X 4.0+, FD Pro (iOS) 2.5+, FD Pro (Win) 8.3+. -->
</TerminalCharts>
-<AirportMovingMap>
<MovingMap>OFF</MovingMap>
<!--Values: ON or OFF (default). To track aircraft position, recenter Airport Moving Map over
aircraft location, and view the Airport Moving Map in Track Up orientation, set to ON. Starting
with FliteDeck Pro X 4.0, this setting was removed from iOS global settings and is no longer
controlled by customer configuration in FliteDeck Pro X. FD Pro (iOS) 3.0+,FD Pro (Win) 9.0+. -->
<DisplayOwnship>OFF</DisplayOwnship>
<!--Values: ON or OFF (default). To display aircraft position (ownship) on Airport Moving Map,
set to ON. Starting with FliteDeck Pro X 4.0, this setting was removed from iOS global settings.
The customer configuration setting Display Ownship under Terminal Charts & AMM controls both taxi
charts and AMM starting with FliteDeck Pro X. FD Pro (iOS) 3.0+, FD Pro (Win)9.0+. -->
<SetAsLandingDefault>OFF</SetAsLandingDefault>
<!--Values: ON or OFF (default). To switch to the Airport Moving Map (AMM) instead of the taxi
chart when Show Taxi on Landing is engaged, set to ON. Starting with FliteDeck Pro X 4.0, the
setting Set as Default on Landing was renamed Set AMM as Default on Landing in iOS global
settings. FD Pro X 4.0+, FD Pro (iOS) 3.0+, FD Pro (Win) 9.0+. -->
</AirportMovingMap>
-<Weather>
<METARAndTAF>ON</METARAndTAF>
<!--Values: ON (default) or OFF. To display terminal weather, set to ON. FD Pro X 4.0+, FD Pro
(iOS) 2.5+, FD Pro (Win) 8.2+. -->
<EnrouteWX>OFF</EnrouteWX>
<!--Values: ON or OFF (default). To display enroute weather over the enroute map, set to ON. FD
Pro X 4.0+, FD Pro (iOS) 2.5+,FD Pro (Win) 8.2+. -->
<DownloadRouteWxOnly>ON</DownloadRouteWxOnly>
<!--Values: ON (default) or OFF. To restrict the download of enroute weather to the current route
of flight, set to ON. FD Pro X 4.2+. -->
<TemperatureUnit>FAHRENHEIT</TemperatureUnit>
<!--Values: FAHRENHEIT (default) or CELSIUS. To set a preference for displaying temperature, make
a selection. Starting with FD Pro X 4.0, this setting was removed from iOS global settings and is
no longer controlled by customer configuration. FD Pro( iOS) 2.5+, FD Pro (Win) 8.2+. -->
<DefaultFormat>RAW</DefaultFormat>
<!--Values: RAW (default) or DECODED. To set a preference ford is playing terminal weather, make
a selection. Starting with FD Pro X 4.0, this setting was removed from iOS global settings and is
no longer controlled by customer configuration. FD Pro (iOS) 2.5+, FD Pro (Win) 8.2+. -->
</Weather>
-<Services>
-<CompanyManuals>
<!--To display customer-uploaded documents sent from Jeppesen e-Link, enter e-Link credentials.
Starting with FD Pro X 4.0, this setting was removed from iOS global settings and is no longer
controlled by customer configuration. Starting with FD Pro X 4.0, uploading company documents is
only supported with JDM Pro. FD Pro (iOS) 2.5+. -->
<Username>elink-user</Username>
<Password>elink-password</Password>
</CompanyManuals>
-<FlightPlanning>
<!--To display and import routes from a flight-planning system, enter the flight planning system
URL, system account username, and system account password. For more information, contact your
Jeppesen account manager. FD Pro X4.0+, FD Pro (iOS) 2.5+, FD Pro (Win) 8.3+. -->
<URL>https://myairlines.com/fp</URL>
<Username>corp-user</Username>
<Password>corp-password</Password>
</FlightPlanning>
-<AircraftIntegrationDevice>
<Provider>NONE</Provider>
<!--Values: NONE (default), AVIONICA, BOEING_ONS, CMC, FOMAX, FREE_FLIGHT, GOGO, JEPP_STD,
NAVAERO, NMEA_COM, NMEA_UDP, or TELEDYNE. To direct FliteDeck Pro to connect to an AID, select an
available AID provider. Not all AID providers maybe available to your version of FliteDeck Pro.
For more information, contact your Jeppesen account manager. -->
<NetworkPort>50000</NetworkPort>
<!--To direct FliteDeck Pro to connect to an AID, enter the network port, if required. The
default port for Teledyne is 50000, FreeFlight is 4000, and CMC is 8341. Contact your Jeppesen
account manager. -->
<DataStreamPort>51000</DataStreamPort>
<!--Some AIDs use a second port for data streams. To direct FliteDeck Pro to request a specific
port for this, enter the data stream port. The default value is 51000. Contact your Jeppesen
account manager. -->
<COMPort>COM10</COMPort>
<!--To direct FliteDeck Pro to connect to an AID, specify a communications port, if required.
This setting is currently only needed for NMEA_COM. FD Pro 9.2.1+ (Win). -->
<Address>192.168.1.10</Address>
<!--To direct FliteDeck Pro to connect to an AID, enter the IP address configured for the AID by
the operator, if required.This setting is currently only needed for CMC. Contact your Jeppesen
account manager. -->
<AccessCode>83224eb4-8a85-4ac0-90b0-f0899da87814</AccessCode>
<!--To direct FliteDeck Pro to connect to an AID, enter the access code, if required. Contact
your Jeppesen account manager. -->
</AircraftIntegrationDevice>
-<GPSAntennaOffsets>
<!--Specify antenna offsets to be applied to the display of ownship on AMM when provided by an
Aircraft Interface Device. Format is comma separated values where each line represents a single
offset. First value is 'T' for tail or 'R' for registration, depending on the second value.
Second value is the ICAO aircraft type or aircraft registration.Third value is the radial offset.
Fourth value is the lateral offset. Fifth value is the maximum bias error. FD Pro (Win) 9.1+. -->
T,B736,841,, T,B737,886,, T,B738,886,, T,B739,886,, T,B772,1200,-7,220 T,B773,1200,-7,220
R,N707JT,325,
</GPSAntennaOffsets>
<GPSAntennaOffsetPilotEntry>OFF</GPSAntennaOffsetPilotEntry>
<!--Values: ON or OFF (default). To enable pilot entry of the antenna offset in the app settings,
set to ON. FD Pro (Win)9.1+. -->
</Services>
-<Updates>
<!--Note: Operator policy settings are not accessible to application users. These settings control
how the application displays data currency. -->
<OperatorPolicyHours>23</OperatorPolicyHours>
<!--Values: 1-23 hours inclusive. By default, users have a grace period of 23 hours to update
terminal charts and airway manuals. To extend this grace period, set the maximum hours for the
grace period. If this element is omitted, or if the value exceeds the maximum grace period
threshold, the default maximum grace period threshold for hours (23 hrs) is used. For more infor-
mation, see the FD Pro Administrator Guide for customizing operator policy. FD Pro X 4.0+, FD Pro
(iOS) 2.5+,FD Pro (Win) 8.3+. -->
<OperatorPolicyDays>0</OperatorPolicyDays>
<!--Values: 0-7 days inclusive. By default, users have a grace period of 23 hours to update
terminal charts and airway manuals. To extend this grace period, set the maximum days for the
grace period. If this element is omitted, or if the value exceeds the maximum grace period
threshold, the default maximum grace period threshold for days (0 days) is used. For more infor-
mation, see the FD Pro Administrator Guide for customizing operator policy. FD Pro X 4.0+, FD Pro
(iOS) 2.5+,FD Pro (Win) 8.3+. -->
<TerminalChartsAvailable>FRI</TerminalChartsAvailable>
<!--Values: FRI or WED. For the limited number of operators who have arranged for early data
delivery, specify WED for expected availability. Omit this element if the operator does not
subscribe to early delivery. If this element is omitted, the default weekday availability (FRI)
is used. FD Pro X 4.0+,FD Pro (iOS) 3.1+, FD Pro (Win) 9.1+. -->
<AirwayManual>TRUE</AirwayManual>
<!--Values: TRUE (default) or FALSE. If the company receives standard Jeppesen Airway Manuals,
set to TRUE. If the company does not receive standard Jeppesen Airway Manuals, set to FALSE. FD
Pro X 4.0+, FD Pro (iOS) 2.5+, FD Pro (Win) 8.3+. -->
<TailoredText>FALSE</TailoredText>
<!--Values: TRUE or FALSE (default). If the company receives tailored Jeppesen Airway Manual
text, set to TRUE. If the device does not receive tailored Jeppesen Airway Manual text, set to
FALSE. FD Pro X 4.0+, FD Pro (iOS) 2.5+, FD Pro (Win)8.3+. -->
<TailoredTextCycle>WEEKLY</TailoredTextCycle>
<!--Values: BIWEEKLY_EVEN, BIWEEKLY_ODD, or WEEKLY (default). If the company receives tailored
text, choose the cycle that defines when the tailored text is published. FD Pro X 4.0+, FD Pro
(iOS) 2.5+, FD Pro (Win) 8.3+. -->
<AllowDriveLoading>FALSE</AllowDriveLoading>
<!--Values: TRUE or FALSE (default). To allow the updating of data on the device from an external
drive, set to TRUE. FD Pro (Win) 9.0+. -->
</Updates>
-<Support>
<!--By default, Jeppesen technical support contact information is listed in app Settings. FD Pro X
4.0+, FD Pro (iOS) 2.5+, FD Pro (Win) 8.3+. -->
<TollFreeNumber>888-555-1234</TollFreeNumber>
<!--To display customized technical support information, enter a technical support North America
Toll-Free phone number. -->
<DomesticNumber>206-555-2345</DomesticNumber>
<!--By default, Jeppesen technical support contact information is listed in app Settings. To
display customized technical support information, enter a technical support United States direct
phone number. -->
<InternationalNumber>+49-5555-345678</InternationalNumber>
<!--By default, Jeppesen technical support contact information is listed in app Settings. To
display customized technical support information, enter a technical support International phone
number. -->
<Email>lorem.ipsum@myairlines.com</Email>
<!--By default, Jeppesen technical support contact information is listed in app Settings. To
display customized technical support information, enter a technical support email address. -->
<Web>http://support.myairlines.com/efb</Web>
<!--By default, Jeppesen technical support contact information is listed in app settings. To
display customized technical support information, enter the URL to a technical support website. -
->
</Support>
-<Control>
<PreventDeactivation>FALSE</PreventDeactivation>
<!--Values: TRUE or FALSE (default). To prevent users from deactivating FliteDeck Pro on their
tablets, set to TRUE. FD Pro (Win) 8.3+. -->
<PreventClearingCustomContent>FALSE</PreventClearingCustomContent>
<!--Values: TRUE or FALSE (default). To prevent users from removing custom content they added
(for example, saved flights, current flight, user waypoints), set to TRUE. FD Pro (Win) 8.3+. -->
</Control>
</CustomerConfiguration>
FIGURE 12: Adobe Acrobat - File > Properties > Description tab
NOTE: FliteDeck Pro X displays the title as it is identified here in the PDF Document
Properties field.
FliteDeck Pro X does not display the title as identified in the JDM Pro
metadata. Since this title is not associated with the JDM Pro metadata or the
distribution rules associated with that data, you can enter any document title
here without concern for revising associated JDM Pro distribution rules.
NOTE: For Mac users, macOS generates hidden resource files when creating a .ZIP
file, which might cause errors when you upload it to JDM Pro. Make sure that
you include only one file in each .ZIP file.
NOTE: For Mac users, to ensure that you include only one file in each .ZIP file,
instead of right-clicking and using the Compress function, you can use the ZIP
command at the macOS Terminal command line.
If the .ZIP file that you want to import does not have the appropriate metadata, JDM
Pro guides you through the process of creating it. You can also use JDM Pro to modify
the metadata.
NOTE: Jeppesen recommends that you use a browser that supports HTML5. If you
use a browser that does not support HTML5, JDM Pro cannot compute the
MD5 digest value for the file that you upload. In this instance, enter an
appropriate MD5 value for the file during the upload process and create the
ADEL metadata file.
JDM Pro uploads the file, runs a virus check on the content, and then displays the
Content Metadata box.
6. Add metadata information in each field. The following fields are required:
• For Content Type, select the appropriate type from the drop-down menu. Since
you are uploading a company document, select ETEXT. (If you are uploading a
NOTE: If you select Deliver Immediately for content being delivered to FliteDeck Pro
X, FliteDeck Pro X notifies the user when the new content is available.
8. Select Continue.
JDM Pro uploads the file and adds the content item to the Content list.
If you are uploading a document that you have not uploaded before, assign that
content to a distribution group. If you do not assign the content to a distribution
group, JDM Pro cannot send the document to recipients.
NOTE: For more information on managing and delivering content using JDM Pro, log
in to the JDM Pro Customer Support Portal page to access the JDM Pro
Application Administrator Guide.