Tag Archives: JSON
In the previous article we started to develop the basic airport’s systems four our Airport Dashboard’s Project, the AODB mock-up, in this article we are going to build another airport’s system mock-up that has a relationship with the AODB, the Baggage Handling System (BHS), not the physical system but the Sort Allocation Computer (SAC). Please see this article for a introduction of the AODB & BHS relationship. To sum up, the BHS has the following main features.
- Transport, classify and deliver each baggage to its destination carrousel (departure and arrival flights).
- Process the baggages in the integrated security subsystem. As X-Ray machines that look for hazardous substances, material, drugs, explosives, etc.
- Store the baggages for early check-in flights.
What data do we want from BHS to our Dashboard?
- General process status and metrics. Bags per hour, first bag delivery time, luggage events per flight, bad reading tag ratio, system status, percentage of manual sorting in comparison to automatic sorting, percentage of bags that are wrongly sorted by the system (sent to a wrong carrousel), average time and standard deviation regarding the time to be sorted by the BHS, etc. Thanks Pablo Roux for some KPI’s suggestions.
What data does the BHS (SAC) need from the AODB?
- The flights scheduled for a time period (day, week, etc.). Where are they planned to be parked.
- Any flight’s relevant updating in real time, any new estimated time of arrival or departure (ETA, ETD), cancellation, stand reassignment, etc.
Are there other systems closely related to BHS?
- Yes, the Airlines Departure Control Systems from the BHS will be notified about the baggage checked, through SITA. (see the article mentioned before)
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.
- 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.
Following the Aeriaa Dashboard (see part I and part II), it’s time to talk about data sources, this includes systems that provide information for our Aeriaa Dashboard architecture. In the basic architecture diagram, shown in part II, you can see the Databases and Airport Systems components.
Let’s put in context a couple of systems that we are going to use in our Dashboard.