Home page
Español
xList, el futuro empieza ahora.
El importante sitio que ocupa ya el Ipad en cabina, abre un mundo de posibilidades.
Dia tras dia los antiguos manuales en papel van siendo reemplazados por documentos electronicos, no solo por economia sino igualmente por eficiencia y parte importante en la seguridad.
Bajo la apariencia de una simple lista de chequeo se esconde todo un sistema integrado de información en tiempo real.
La lista de chequeo es uno de los documentos del avión mas usado durante el vuelo y precisamente por ello es ahi donde aunamos información de primer nivel de relevancia.
xList es el resultado de muchos años de experiencia en vuelo. No solo es la mejor solucion para el EFB sino que constituye un gran paso adelante en su uso.

Las listas de chequeo utilizan colores para indicar su estado, completado/no completado.
Solo permiten su uso sequencial, para evitar marcar accidentalmente un punto no comprobado.
El formato desplegable permite saber su estado en un rapido vistazo.
CM1/CM2 seleccionable en Ajustes y PF/PM en la propia lista, de esta forma cada piloto solo necesita cumplimentar las listas que le corresponden.
Modo noche para atenuar o aumentar el brillo con un solo boton.
Multiflota, permite su uso en las diversas flotas de una compañía.

Conecta directamente la cabina de vuelo con los diversos departamentos de la compañía. (vease Attention Crews)

Click or tap over the images for a bigger view.

XLIST

Los ejemplos mostrados aquí son del A340 300 y 500 pero xList sirve igual para cualquier avión y cualquier compañia








eChecklist

Each time Xlist is started:
- All the checklists are reset to initial state.
- A flight recorder file is stored in the Ipad (.txt type and current date as name).

The initial Xlist view consist of the normal checklist headers ordered by flight phase sequence and colored indicating the list type. Green normal, light green for “below the line” checklists.
That is Airbus Xlist design. Different airplanes may have different color codes for read, silent or read and do checklists.
Checking the list and the items can only be performed in strict order.
Once we have completed any checklist the list header turns grey with no further color changes posible for error avoidance.
Tapping over the list header, the checklist expands showing all its items. Tap again will collapse the list to the previous state.
Tapping over the correspondent list header, the checklist is expanded at the top of the view, the Ipad will read aloud the name of the checklist and a record will be written in the Xlist flight recorder with the name of the list tapped and the time.
Tapping over the next list item will dimm it and add a checkmark. Items can be unchecked but an item can only be checked if the previous is already checked.


When all items of any checklist are checked, the Ipad reads aloud the name of the checklist adding “Completed”. A record with the name of the checklist, the time and the GPS position, is then written in the flight recorder. The list header turns grey and the checklist collapses.


The checklist are part of the software code and can only be modified or manipulated through the source code of the App.



Menu

Located at the bottom of the checklists view there is a menu with 6 buttons.
Three are links to auxiliary documents views (Att. Crews, Utilities & N.Procs).
Two application auxiliary views (Updates & Flights).
One is for emergency (EMERG).


EMERGENCY

On a privileged position, color and size, there is a button link titled EMERG.

Jumps to an auxiliary view with two Airbus emergency procedures for immediate reaction.
Procedures included are Emergency evacuation and overweight landing for a quick turn back.

The documents are simple text docs, very light for ultra fast loading. Can be modified with any text processor software and for replacing them it is necessary the developer intervention.



Att.Crews.

Bajo la apariencia de una simple lista de chequeo se esconde todo un sistema integrado de información en tiempo real.

La lista de chequeo es uno de los documentos del avión mas usado durante el vuelo y precisamente por ello es ahi donde aunamos información de primer nivel de relevancia.

El documento Attention Crews pretende servir como fuente de información permanentemente actualizada donde mantenimiento, operaciones de vuelo y operaciones de tierra se comunican entre ellos y con la tripulación de vuelo.
Se trata de un documento Word único para cada avión. Esto se consigue seleccionando en los ajustes del iPad el nombre del documento que ese iPad descargará del servidor,
por ejemplo EC-INO.doc.
El documento EC-INO.doc está alojado en el servidor de la compañía fácilmente accesible desde cualquier departamento y dividido en tres (o mas) zonas, claramente diferenciadas por colores, de manera que cada departamento puede modificar el documento en su sección correspondiente.

Por ejemplo, hay un huracán en la zona del próximo vuelo del EC-INO y despacho de vuelos quiere enviar a la tripulación la ultima imagen de satélite o un enlace a una página web donde encontrar información importante. Podría enviarlo al email del iPad y si la tripulación no lee los emails esta información pasará desapercibida, pero si la propia lista de chequeo avisa de que hay nueva información tendrá un nivel de eficacia muy elevado. No hace falta buscar en la lista de correos que nos afecta y que no.
Por ejemplo mantenimiento quiere informar que aunque el motor numero 4 adolece de EGT over limit, es preferible usar el arranque usual en lugar de manual start. O que debido a que el motor numero 3 está a punto de revision pero gasta mucho aceite, se ha provisto de una caja del propio aceite en el bulk por si fuera necesario rellenar en alguna escala.

El documento Attention Crews es el único de los documentos auxiliares que permite cualquiera de las capacidades propias de un navegador web, como por ejemplo navegar entre paginas web, introducir datos o visionar video y audio. Por ello este documento permite interactuar con la tripulación.

Por ejemplo remitimos a una pagina web donde el piloto debe pulsar sobre la casilla “mensaje recibido y entendido” o enviar un mensaje especifico. Un ejemplo practico sería una página donde el piloto y despacho de vuelos mantienen contacto directo sobre el retraso estimado de salida y los slots recibidos.


Utilities

Pilots we need to check many parameters and data from different documents and places
It takes vital time to us consult always the same tables and charts just in very short time.
This document reduces the stress and helps to accuracy by extracting the more frequent parameters into a single view.
It is a pdf format to permit maximum zoom quality with minimum document size for fast loading.
The document is stored in the company server and can be updated as frequent as needed.
It may content graphics, tables and images extracted from FCOM, airline policy as desired by ground OPS.
Requires technical acknowledge about the content but not to the form that can be created in our favorite text processor, even directly in the remote server copy.

A secondary utility view has some interactive areas for useful calculations like wind component, etc.

N.Procs (Normal Procedures)

Xlist is a powerful tool for pilots.
Aviation is now heading to the use of new technologies in pursuit of more advanced documentation, much more effective and precise. Interaction is now becoming a standard and manuals are updated more frequently than ever thanks to the economy and immediate of the electronic documents.
Company's training management can help to cockpit standardization through this document extracting the manufacturer manuals and incorporating the company policies into a graphic view for fast and frequent consultation of normal procedures.
We may figure it as an advanced QRH with much more effective normal procedures description using colors and graphics with an unprecendented realism.
The document loaded into the view is in pdf format allowing the use of high quality images, tables and zoom at a low size cost.
The document is downloaded from the company servers as frequently as needed through the updates view and is stored in the Ipad for offline use.





Updates

This is an auxiliary view to update and download the auxiliary documents from the company servers.
Every time the view is called the app connect with a remote XML file (array plist type) where the url pointers of the the XML file itself and the auxiliary documents are stored. That is made so to allow the temporal or permanent change of the storage server and the documents address.
At a first stage the App defaults to a convenient url. Later when the auxiliaries documents are builded and the servers location decided the webmaster must update the XML file pointing to the desired documents and addresses.
This view reads the original XML, connects to the remote XML, stores it into the Ipad for further requests and checks the server auxiliary documents against the Ipad stored version. When a change is detected it shows the new version data and a "UPDATE" button is presented. By pressing that button the auxiliary document is downloaded and stored into the Ipad. The replacing document version will then always be shown into its correspondent view until the next revision should be downloaded.
When no updates are available, a checkmark indicates it next to the document name and the date and size are shown below.


Flight recorder

Every time Xlist is launched a file named as the current date and time, is created.
When the correspondent checklist is expanded, a text line with the name of the list and the time is recorded.
When the checklist is completed a new text line is added with the time and the GPS position.
All these files are permanent stored in the Ipad and can be revised in this view.
There is a button to delete all the files except the current in use.
About FbW Contact