DocBrowser Digital Document Distribution system provides a server platform for document hosting and multi-platform client software (Mac OS X, MS Windows, Linux, iOS) that synchronizes with the server to provide offline access to company manuals and documents. The server platform also presents manuals and documents and provides an administrative interface via any compatible web-browser. Additionally the system supports optional modules and associated iOS clients for offline Reports and Forms and interactive Destination Information.

The server platform is managed by the system provider and hosted in a redundant environment. The web-based interface is designed for compatibility with all major modern browsers such as Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Edge.

iDocBrowser client software requires a device capable of running iOS 9.0 or later.

iFlyThere client software requires a device capable of running iOS 9.0 or later.

iReForm client software requires an iPad capable of running iOS 9.0 or later.

The server platform hosts all documents in a structure defined by the system administrator. In addition the server platform contains a user database where users and approved software clients are registered.

The required document structure is maintained by the system administrator using a web-based graphical user interface. Documents are uploaded to the server directly from the administrative user interface.

Document access rights are defined by user roles. Each registered user is associated with any number of roles.

Each user may also be subject to usage tracking where every document’s download, read and confirmed status is tracked across the users client and registered on the server.

The Digital Document Distribution Server replies to synchronization requests sent from DocBrowser clients via a secure https/SSL connection. If the provided user and client information is registered on the server a response will be sent to the client with data of the current document structure. The client will modify the document structure as required, verify all local files and request missing documents from the server and/or delete obsolete local documents.

All document transfers are verified against the user/client data and performed using secure https/SSL. As all document transfers are logged the civil aviation authority’s requirement of sign-that-received is fulfilled. Each user account may have three different clients registered. Each client will be identified using hardware or software based unique ID’s. These ID’s must be registered on the server and associated with the respective user in order to allow synchronization.

An MDM system supporting Managed Application Configurations may be used to preconfigure iDocBrowser client settings and automate the device authentication.

Optional components consists of dynamic platforms for an interactive Destination Brief, electronic reports and forms and tracking and displaying of Key Performance Indicators (KPI's).

The destination brief functionality presents dynamically generated destination information in the web-interface or an iOS client based on locally stored database content.

The reports and forms functionality can be used to define custom reports and forms for offline use on any iPad device.

The Digital Document Distribution Server can also be accessed via a secure web-interface where all documents as well as DocBrowser clients are available for download. There is a possibility to either access the server via an embedded link from an Intranet or via a dedicated login web-page. Any user logging on the web-interface with administrative privileges will have access to different levels of administrative functions on the server. These functions include statistics retrieval, document administration, user and client management as well as optional EFB administrative functionality for document synchronization with any EFB administration server.

In this scenario a user typically named “webuser” is created and associated with a role associated with all document categories that shall be accessible via the webDocBrowser interface.

A hyperlink is created in the company intranet with embedded login-information for the “webuser”. By clicking this link the user will be directed to the webDocBrowser and have access to all available documents.

Optionally the webDocBrowser can be customized and fully embedded in an existing intranet setup.

All users that desire offline access to documents via client software are registered on the server with a maximum of three individual clients. Users will be assigned to any role giving access to the documents that is applicable to the individual user. Each client will feed back document read status to the server for follow up and statistics. Document read status will be shared between all clients used by a user.

In this scenario individual user accounts are created for all applicable staff. Each account is assigned to the role giving access to the applicable documents. Document access for each individual user will be logged by the system for follow up and statistics.

A hyperlink is dynamically created in the company intranet with embedded login-information for each individual user. By clicking this link the user will be directed to the webDocBrowser and have access to the documents applicable to his/her role. Optionally the user can be presented with a list of all unread documents. It is also possible to present this unread list or the number of unread documents in the company intranet environment by creating a custom request.

Optionally the webDocBrowser can be customized and fully embedded in an existing intranet setup. (Alternatively a hyperlink is created leading to the webDocBrowser login page.)

All users that desire offline access to documents via client software can be associated with a maximum of three individual clients. Each client will feed back document read status to the server for follow up and statistics. Document read status will be shared between all clients used by a user.

Optionally a common Web-Login to be used by generic users or to access documents not available in an individual user profile can be created also in this scenario.

A setup as described in the Common Web-login scenario except that no usage tracking is enabled on the individual user accounts. Each individual client software will track read/unread status locally without feeding back any information to the DocBrowser server.

The webDocBrowser is only used for server administration and all users access the available documents using the client software.

Various data can be retrieved from the DocBrowser server.

Data feeds will only be available if requested from domains specified in the Administration Settings page.

The number of unread required documents for users subject to document access tracking can be retrieved via the below link. This may be used to present the presence of new documents while logging on to an intranet.

https://SERVER/api/unreadstatus/USERNAME

The response is returned in JSON format containing the variable [unread] with an integer representing the number of unread required documents for the given user. 0 will be returned if any error occurs.

The web-based user interface is accessed via the url of your assigned server.

A link with embedded login information can also be created for integration in for example an intranet platform:
https://SERVER/login/GROUP/USERNAME/PASSWORD(/TAB)

• Replace SERVER with applicable document server.
• Replace GROUP with applicable three-letter company group code.
• Replace USERNAME with username for the desired user.
• Replace PASSWORD with password for the desired user.
• Optionally append a desired TAB. This tab will be displayed when the webDocBrowser is loaded (e.g. any category, Software, Destinations, Administration etc).

Direct links will only be allowed from domains specified in the Administration Settings page. All parameters such as username and password contained in direct-links are encrypted using SSL.

All manuals and documents are presented in an easy an intuitive way similar to the structure found in the DocBrowser clients and Electronic Flight Bag (Optional DocBrowser EFB software).

A tab presenting all unread required documents for the current user will be shown if the system administrator selects this option.

A tab presenting all recently published documents for the current user will be shown if the system administrator selects this option.

Under the “Software” tab in the web-based user interface instructions and links are provided for downloading and installing the DocBrowser client software.

In order to access the administrative functions the current user must have some level of administrative privileges. If the current user has administrative privileges the “Administration” tab will be shown. Under this tab functions for document administration, user administration, statistics, EFB synchronization (optional), reports and forms administration (optional), KPI administration (optional).

Any user session will expire after 60 minutes of inactivity.

Add and delete documents or edit document data.

The iDocBrowser iOS client fully supports PDF, Boeing FTID XML documents and various X/HTML formats. Additionally video playback is supported (MP4/MOV/MPV/3GP). MS Word, Excel and PowerPoint documents has limited support and Apple iBooks can be distributed via iDocBrowser and viewed in the Apple iBooks app.

Current documents are listed and can be filtered by name, categories and subcategories. The document list may be sorted by any column by clicking on the column header. Documents that have expired will show EXPIRED in red as valid to date.

Neither expired nor not yet valid documents will be visible in the webDocBrowser or any client software.

Documents can be uploaded and deleted as required and the document Meta data such as name and category can be edited when necessary.

Add a document by pressing the “Add Document” button.

View or Edit document data by marking a document and press the “Edit Document” button or double clicking a document in the list.

Delete documents by marking one or more documents in the document list and press the “Delete Document” button. Documents can also be deleted by pressing the “Delete” button while viewing the document data dialog.

Pressing the “Role Availability” button shows all roles and users that have access to the selected document.

The following fields are available in the Document Data dialog:

Optionally the server can be configured to accept upload of new documents via mail. A mail address for document upload will be assigned and the server will accept mails from any of the e-mail addresses predefined on the system settings page.

When uploading documents to the server the document can either be an attached file or a PDF-document can be generated based on the content of the mail. The uploaded mail shall contain XML-data describing the document properties as follows:

<?xml version='1.0' standalone='yes'?>
<DOCUMENT>
<NAME>Document Name</NAME>
<CATEGORY>Category</CATEGORY>
<SUBCATEGORY>SubCategory</SUBCATEGORY>
<TAGS>Tags (comma-separated, optional)</TAGS>
<WEIGHT>Weight (optional - defaults to 0)</WEIGHT>
<VALIDFROM>YYYY-MM-DD (optional - defaults to today)</VALIDFROM>
<VALIDTO>YYYY-MM-DD (optional - defaults to no expiry)</VALIDTO>
<RECEIPT>YES/NO (optional - defaults to no)</RECEIPT>
<RECEIPTDUE>YYYY-MM-DD (optional - defaults to no due date)</RECEIPTDUE>
<CONTENT><![CDATA[ Content of PDF to be generated ]]></CONTENT>
</DOCUMENT>

The CONTENT tag may include plain text or HTML. Any HTML code must be surrounded by tags. If no CONTENT tag is included the server will look for an attached document that will be uploaded to the server.

Alternatively basic document properties may be described in the mail subject and the complete mail body will be converted to a PDF-document and uploaded to the server. The mail subject should contain the following information separated by “|”:

Category|SubCategory|Document Title|Page Orientation (P/L)

Page orientation defaults to portrait but may be set to landscape by L. All other document properties will use the default values stated in the XML-syntax above.

The server will send a notification to the system-administrator following a successful or failed mail-upload.

There is also possibilities to use customised import scripts to fit specific mail formats.

Documents can be uploaded from external systems by submitting an HTTPS POST request to the following address: https://SERVER/api/upload

This request will accept the the following parameters of required and optional metadata:

The server will respond with an appropriate JSON formatted status message.

Optionally the server can be configured to automatically fetch and publish documents from external sources. A common usage scenario is when an external provider regularly publishes documents that shall be available to the DocBrowser users, a task that can be completely automated by the system.

The foundation of the document data is the structure. All documents are associated with Categories, Subcategories and Tags defined in the structure. The user access control also controls document access by associating roles with Structure elements.

Add a category by pressing the “Add” link in the “Add, remove or edit document categories, subcategories and tags”. Edit or delete a category by pressing respective button in the Edit Category Information dialog by clicking on a category in the category list.

Categories, Subcategories and Tags will be listed in the order defined by the given weight (any number between 0 and 32768).

Each category can accept PDF, MS Word (doc/docx/dot/dotx), MS Excel (xls,xlsx) ,MS Powerpoint (ppt/pptx/pps/ppsx), Videos (MP4/MOV/MPV/3GP), Boeing FTID XML or X/HTML packages (ZIP) and iBOOKS files as set in the Allowed FileType selection. Currently the Windows / OS X client software will only handle PDF files. MS Word files may be downloaded via the webDocBrowser interface but is not ideal for distribution of digital content. It may however be useful to store word document templates in restricted administrative categories for use by editors of digital content. iDocBrowser fully supports PDF and Boeing FTID XML and various X/HTML documents, playback Videos and implements basic functionality for displaying of Word and Powerpoint documents as well as possibility to distribute and open iBooks in Apple iBook.

Documents in each subcategory can be sorted in ascending or descending order according to document name or valid from date. Individual document weighs will always have sorting priority.

Every category must have at least one Subcategory. You may assign a color to subcategories that will be reflected in the client software user interface, a feature useful for color coding of operational notices.

When the “Automatically show All subcategories button” box is checked a Subcategory named “All” will be automatically shown in the client user interface. This Subcategory will list all documents within this Category. When the “Show document count in subcategory buttons” box is checked the total number of documents in each Subcategory will be shown in the client user interface.

When the “Default Require Receipt selection when adding documents” box is checked the Require Receipt box will be checked by default when adding documents to this category.

When the “Automatically permanently delete Expired Documents” box is checked expired documents in this category will be automatically deleted from the server.

When the “MDM Required” box is checked this category will only be visible to devices that are authenticated using a pushed managed application configuration controlled by an Mobile Device Management system. This can be useful to assure that certain categories of sensitive documents only are available on company controlled devices and not on personal devices.

Tags are used by administrators to control document and/or for users to filter documents based on relevance. When the “Show Tag Filtering in DocBrowser user interface” box is checked the user will have the possibility to filter documents based on tags in the client software.

Groups can be defined in the administrative user interface. Categories can be tied to groups and will be presented in the iDocBrowser user interface under a group menu based on their assigned group. Categories not belonging to any group will be displayed under General. If only one group is available to a user the group menu will not be visible.

Users of the system and their clients must be registered on the server.

The user list can be filtered by name and role. Clicking on respective column header will sort the list based on that column.

New users can be added by clicking on “Add User”. Existing users can be edited or deleted by marking respective user and click on the “Add User” or “Delete User”. Multiple users may be edited or deleted simultaneously. When editing multiple users editing is limited to non user unique options. The edit user dialog may be displayed by double-clicking any user in the list.

Different levels of administrative privileges may be given to any user.

The following fields are available in the User Edit dialog:

Note that when editing multiple users at the same time checkboxes in the user edit dialog will have three states: Checked, Unchecked and Mixed. Mixed mode will leave the present value unchanged and will be displayed when editing multiple users with different settings for the particular checkbox.

The administrator can create, edit or delete different roles. A minimum of one role is required.

Each role is assigned to the applicable categories, subcategories and tags. Typically one role is created for each group of staff (ie Flight Deck B737, Flight Deck B767, Cabin Crew, Technical, Admin Staff etc).

A role can have several levels of access to documents: No Access, Required, Reference, Decluttered, Wifi Download Only or Manual Download. Required documents are documents that is subject to highlighting, read compliance statistics and tracking for users in the specified role. Reference documents are available but not subject to highlighting or read compliance statistics. Decluttered documents are similar to reference documents but will be completely hidden in iDocBrowser decluttered mode. Wifi Download only documents are similar to decluttered documents but will not be automatically downloaded to the device unless a Wifi connection is available. Manual download documents will only be downloaded to iDocBrowser if so requested by the user. (Decluttered, Wifi Download Only and Manual Download feature require iDocBrowser 5.2 or later. On earlier versions these documents will be given reference access)

A user may be assigned to multiple roles and the role access will be merged where required categories has priority over reference categories.

The number of users associated with each role are shown in the roles list. By clicking on the number the users will be displayed.

Various system settings may be controlled by the assigned system administrator:

The Track Usage functionality is used to display reports over document read status, user read status and user activity. Automated reports can be created that are sent to specified e-mail recipients on a daily (01:30), weekly (Monday 01:30) or monthly (first day of month 01:30) schedule.

Comprehensive statistics and access history can be viewed on the Statistics page.

Diagram shows which type of web browsers that are used to access the webDocBrowser and the split between use of iOS or Windows/OS X client software. Additionally a graph representing daily access statistics for the last year is shown.

The DocBrowser server may be custom configured to remotely update other servers such as EFB data distribution systems.

The EFB Document Server will be synchronized according to the user role/document access rights of the user named EFBUSER. If this user is not present in the system a warning will be displayed.

The Windows and OS X versions of the DocBrowser and DestBrowser client software can be launched in an EFB mode with a touch friendly interface featuring full text document indexing and search and an integrated PDF-viewer.

Destination and hotel information can be stored in a database and presented in to users in the interactive iFlyThere iOS app, in the web interface or on the Windows EFB DestBrowser application. Destination and hotel information templates can be defined in the administrative interface. The templates define what information can be stored for a destination or a hotel and how this information is presented to the user. Information is structured in Categories that has a title. This title is presented as a section header to the user. Each Category may have any number of fields. A field can be a short unformatted text field typically used to store names, contact numbers etc or a large capacity rich text field that can store complex formatted text as well as inline images. Only fields containing information will be reflected to the system users.

Visibility of Destination and Hotel information can be controlled using roles. In Destination Settings the overall access to the Destinations functionality can be restricted to certain roles. Each destination and/or hotel can be restricted to certain roles. Each category of data within a destination and/or hotel template can be restricted to certain role.

If location information is provided the destination location will be visually plotted on maps. For destinations the location must be presented as latitude and longitude and for hotels the postal address is required. By pressing the LOOKUP button following entry of an airport IATA code general destination information will be retrieved from a database containing almost ten thousand airports around the world.

All changes will become immediately reflected to the applicable users in the Destinations tab, the iFlyThere iOS client and optionally the DestBrowser EFB application. All destination and hotel data updates require that a revision/change note is entered in order to maintain a revision history.

The iReForm administrative interface is used to manage available reports and forms, show usage activity and display, review and export forms data submitted to the server from the iReForm iOS application.

Add a form by pressing the “Add Form” button.

View or Edit a form by marking a form and press the “Edit Form” button or double clicking a form in the list.

Delete forms by marking one or more forms in the list and press the “Delete Form” button. Forms can also be deleted by pressing the “Delete” button while editing a form.

The following fields are available when editing a form:

When submitting a form directly from the app as an e-mail or if sending notifications when a form has been received by the server the e-mail addressee can depend on the content of a given form field. If only the field-id is given within brackets [FIELDID] the field is expected to contain one or several comma-separated e-mail addresses. Alternatively address-options may be contained within the brackets in the following format:

[FIELDID|OPTION;ADDRESS|OPTION1;OPTION2;OPTION3;ADDRESS]

FIELDID is the id of the form field where the OPTION should be retrieved. If the form field data matches the option the corresponding address or list of comma separated addresses will be used for sending the mail notification or when submitting the form, as applicable. (The support for submitting a form via mail using the [FORMID|OPTION;ADDRESS] format is supported in iReForm v3.6 and later versions)

By pressing the Review and Export received reports all forms submitted to the local DocBrowser server database can be reviewed, administered and exported either as individual PDF's, CSV or Excel lists.

Reports and Forms that has been posted to the server may be reviewed and exported by selecting the respective form in the list. A server database table will be created automatically the first time a new report is posted to the server. If an updated form with an existing form ID is posted to the server any new form fields will be merged into the existing database table.

By selecting a form table in the list box and press the List Reports button a dialog will be shown where selection criteria and data filtering can be applied. By default a list with all received reports for the selected form will be displayed. Columns can be rearranged as desired and reports can be filtered according to given criteria. The resulting reports list may be sorted by any column by clicking on the column header. Field data in the displayed report list will be truncated to maximum 20 characters and any images will not be displayed. By double-clicking on a report the report will be shown with all available data including images and the options to save the report as a PDF or delete the report will be available.

By pressing Delete Reports either all or the currently listed reports from the selected form can be deleted.

By pressing Export CSV the currently listed reports with the selected columns will be exported to a comma separated text-file (CSV).

By pressing Export XLS the currently listed reports with the selected columns will be exported to an Excel 2007+-file (XLSX).

By pressing the Activity Report button basic usage statistics is displayed.

By pressing the Force FTP Upload button FTP transfer of reports configured for FTP UPLOAD will be initiated manually.

The KPI administrative interface is used to manage Key Performance or Safety Performance Indicators. Indicators and their properties and accessibility can be defined using the administrative interface. The administrator updates and maintains the indicator data as required. The indicators are presented in a “KPI”-tab to users with roles that has access to Key Performance Indicators. If desired a user named KPIKIOSK may be registered on the server. When logging in with this user the available KPI's will be presented in a KPI-only view that never will timeout and automatically refresh the KPI data every eight hours. This mode can for example be used to present KPI/SPI's on large screen displays in a public office environment. Additionally a pocketKPI compatible JSON feed can be generated by the DocBrowser server using this format: https://SERVER/getPocketKPI.php?un=USERNAME&pw=PASSWORD

The username in the above URL must be prefixed with the applicable group-code, e.g. xxx.username

To provide offline access to company manuals and documents the (i)DocBrowser client software can be used.

Client software are available for the MS Windows, Mac OS X, Linux and iOS (iPod, iPhone, iPad) platforms.

Each DocBrowser client’s individual id-number must normally be registered on the server and associated to the current user in order to have access to any document. The system administrator can terminate access rights for any client as desired.

iOS client applications can be remotely configured with relevant server address and user credentials when the target device is enrolled in an Mobile Device Management solution that supports Managed App Configurations.

The following key and value pairs should be included in the Managed Application Configuration to enable remote configuration of the iDocBrowser application: