Tag Archives: Airport Dashboard

Aeriaa Airport Dashboard. Controlling airport facilities, Jetways

In the last post of the airport’s systems mock-ups, we created the first steps of a DCS system for our airport, after the AODB and BHS, now, we change the scope to the airport’s facilities, a little SCADA system for monitoring the airport’s jetways (also known as Boarding bridges, Jetties, Air Bridges) status on an iPad App, this system will be another event producer for the Dashboard, and itself is a nice tool for operations and maintenance departments. In the tech part of the article, we are going to show how reusability boosts a global architecture system’s plan. We are going to take advantage of previous Web Services we exposed, the integration with MongoDB collections, and the look&feel designed in web apps (AODB and BHS). But, we are going to introduce a new technology for the Web APP, AngularJS, a very interesting front end framework.

Jetways demo aeriaa

Jetway iPad app Monitoring Mock-up. Credit: www.aeriaa.com

 

THE JETWAY MONITORING SYSTEM

These are the features of our new airport’s system mock-up:

  • Show the status of the main jetways and stand modules. 
    • Docking Guidance System (DGS). This system helps the pilot for identifying its stand assigned and the correct aircraft’s alignment and final position on the stand. I also shows practical information data for the pilot as time milestones.

Visual Docking Guiding System in Action. Credit: http://www.sloveniacontrol.si

Visual Docking Guiding System in Action. Credit: http://www.sloveniacontrol.si

GDS showing TSAT time. Credit: Zurich Airport

DGS showing TSAT time. Credit: Zurich Airport

    • 400Hz: this system provides electrical energy to the aircraft when the engines and APU shut down, the frequency is due the size of the aircraft’s module, its size allow to be smaller and lighter.

Ground Power Unit providing energy

Ground Power Unit providing energy

    • Air Conditioning (AA): this system provides fresh conditioned air when the aircraft is stationed.

Air Conditioning provided to an aircraft. Credit: http://www.aircrafttowbar.eu

Air Conditioning provided to an aircraft. Credit: http://www.aircrafttowbar.eu

    • Signals simulator for triggering the events on-off of each subsystem.
  • Look up the flights assigned to each jetway.
  • In the next version these features are expected:
    • Provides information to the Airport’s Dashboard, about jetways availability and alerts for specific flights.
    • More integration with the AODB for the resource’s assignment and events that overcomes new estimated time to departure (ETA) due turnaround affections (TOBT) and in-off block expected times. (IBK/OBK). Enlazar con post de tiempos.
    • Integration with an airport’s maintenance system.

In this case, as DCS, we’ve chose again an iPad App for implementing the main functionalities mentioned above and a Web App for implementing the signals simulator for the DGS, 400Hz and AA modules, as well the main jetway’s general status/availability.

Jetways giving service to an A380. Credit: www.thyssenkrupp.com

Jetways giving service to an A380. Credit: www.thyssenkrupp.com

 

THE SIMULATOR

As my budget is “limited” for acquiring a full electric, modular and fieldbus components, connectors/actuators, etc. I developed a web app that throws the signals. The main use of this app is to change the values for each jetway, each of them, and its modules, is represented in a table’s row. let’s see the main interface.

Jetways Web App simulator.

Jetways Web App simulator. Credit: www.aeriaa.com

When we change any value, the web app and the backend executes the next actions:

  • Call a Web Service and report the new value in real time.
  • The backend receives the data and insert directly in a real time database.
  • So the data is served in real time and the iPad App can have the data updated at any time.

Let’s see the meat of this (techie part of the article), as we said above, I developed the web app using AngularJS, a great frontend framework that gives me a perfect modularity for creating web components and the glue for combining them. So, when I changed a value this part of the web app (named controller) reacts to the change.

Changing values in the simulator. Credit: www.aeriaa.com

Changing values in the simulator. Credit: www.aeriaa.com

Toggle Button component. Credit: www.aeriaa.com

Toggle Button component. Credit: www.aeriaa.com

App directive for the Toggle Button. Credit: www.aeriaa.com

App directive for the Toggle Button. Credit: www.aeriaa.com

With this event we directly call the Web Service and pass the data.

Calling the Web Service for updating the jetway data. Credit: www.aeriaa.com

Calling the Web Service for updating the jetway data. Credit: www.aeriaa.com

In the backend, developed with NodeJS and reusing the previous code’s snippets of the AODB, BHS and DCS mockups, we are listening a new call with this data and insert it directly in a MongoDB collection.

Web Services defined in NodeJS Backend. Credit: www.aeriaa.com

Web Services defined in NodeJS Backend. Credit: www.aeriaa.com

Jetway data on MongoDB collection. Credit: www.aeriaa.com

Jetway data on MongoDB collection. Credit: www.aeriaa.com

And that’s all.

REQUESTING INFORMATION FROM THE iPad APP

In this version, the app, retrieves information about the jetway’s status and the assigned flights to them. This how the app does it:

When the user clicks on any of the jetties, the app requests the info to a Web Service, in the same NodeJS’ backend where the simulator sends the data in real time. The data returned has the jetways status and the flights assigned to it.

When the user clicks on a jetway, the app request the data to the backend. Credit: www.aeriaa.com

When the user clicks on a jetway, the app request the data to the backend. Credit: www.aeriaa.com

Data returned after the user's action. Credit: www.aeriaa.com

Data returned after the user’s action. Credit: www.aeriaa.com

THE DEMO

One video worths one thousand words. Enjoy the full demo in the following video, remember that aeriaA has a Youtube channel, please visit it and its playlists. Disclaimer: the app design is very alpha, do not complaint about it :)

For better visualization, please, maximize the video or visualize it at youtube. It also has nice music.

For more info:

Docking Guidance System explanation by Zurich Airport (PDF): Aircraft Docking Guidance System

Docking Guidance System at Wikipedia: https://en.wikipedia.org/wiki/Stand_guidance_system

Please follow us at:

twitter. @aeriaablog

facebook: aeriaA at Facebook

LinkedIn: aeriaA at LinkedIn

Personal LinkedIn: es.linkedin.com/in/pedrogarciafernandez

Youtube: aeriaA at Youtube.

Aeriaa Airport Dashboard. Creating the AODB (I)

 

Following the aeriaA Airport Dashboard Project series, in this post we will build a little Airport Operational DataBase (AODB) system for our Dashboard’s architecture. This post is mixed oriented, it is a  little introduction of an AODB and a little introduction of the technologies used for building it.

The AODB is one of the central part of the whole project. We simplified a lot the AODB’s features, it is not the intention to build a real one, these are the main features:

  • Manage the Departures Flights of our Aeriaa International Airport.  We can create, update and delete departures flights (We will develop the arrivals flight later).
  • The frontend is a website application. We’ll try in the the future a smartphone app (step by step).
  • The flight’s attributes at the first data model are (alphabetically ordered):
    • AOBT. Actual Off-Blocks Time. It is the time when the fight is ready, doors closed, jetway decoupled, and the towbear available for the push-back.
    • ASAT. Actual Start-Up Approval Time. It is the real time when the flight has the approval for start the engines.
    • Aircraft. The aircraft model.
    • Company. The airline company.
    • Counter. The designated counters for the flight.
    • Destination.
    • ETD. Estimated Time for Departure.
    • Flight. It is the fight’s code.
    • Gate. The gate assigned for the flight.
    • ICAO. Company’s ICAO code.
    • STD. Scheduled Time for Departure.
    • TOBT. Target Off-Block Time. It is the target time for the Off-Blocks Time (see AOBT)
    • TSAT. Target Start Up ApprovalTime. See ASAT.
  • We included some time’s milestones (TOBT, TSAT, AOBT, ASAT) related to A-CDM philosophy in order to approach the AODB to this new work collaboration paradigm. There just a few of the huge times complexity of A-CDM. You can find a big list of time milestones here www.aeriaa.com/on-the-aeriaa-airport-dashboard-part-v-time-milestones/
  • Billing the services provided by the airport or ground handler that the airline must pay. The services could be the push-back service, the jetways, follow me car, baggage handling, counters, etc.

DSCF0047.JPG

Building our AODB System mock-up. Image Credit: Pedro Garcia

On the Aeriaa Airport Dashboard (part VI). Events Logger

Some days ago, a friend of mine, Ram, put me on the track of Splunk, I’ve never noticed it, so I downloaded it and at the first glance I knew it was perfect for the Logger component of the Dashboard’s architecture, let’s remember it (if you are new to this blog see the previous posts):

Aeriaa Dashboard Project - Logger

So, I put to test a little with it. Let see all after the jump.